CN116567616A - Communication processing method and device and related equipment - Google Patents

Abstract

The invention provides a communication processing method, device and related equipment. The communication processing method performed by the terminal includes: before initiating a registration request to the network side device, receiving slice configuration information sent by the network side device; according to the slice configuration information, determining a sending mode of a slice identifier of a network slice. The embodiment of the present invention can improve the security of slice identifier transmission.

Description

Communication processing method, device and related equipment

technical field

Embodiments of the present invention relate to the field of communication technologies, and in particular, to a communication processing method, device, and related equipment.

Background technique

The network slice identification is the identification information sent by the user to the network to identify the requested slice connection during the process of communicating with the network and requesting the use of the corresponding network slice for a specific service. Since the slice connection information can present the corresponding relationship between the user and the business service, and then reflect the user's behavior pattern and preference, it is a kind of private information.

Usually, in the process of wireless communication, the core network needs to send corresponding mode indication information for the network slice only after the terminal is registered successfully, so as to instruct the terminal to deliver the relevant slice identifier. However, during the registration process interaction before the registration process is successful, the terminal will pass the slice identifier to the network. At this time, the user's slice information may be intercepted or identified, leading to the risk of exposure of private information.

Contents of the invention

Embodiments of the present invention provide a communication processing method, device, and related equipment to solve the problem that user slice information may be intercepted and acquired or identified, resulting in the risk of exposure of private information.

In order to solve the above problems, the present invention is achieved in that:

In a first aspect, an embodiment of the present invention provides a communication processing method, which is executed by a terminal, and the method includes:

Before initiating a registration request to the network-side device, receiving slice configuration information sent by the network-side device;

According to the slice configuration information, a sending manner of the slice identifier of the network slice is determined.

In a second aspect, an embodiment of the present invention provides a communication processing method, which is executed by a network side device, and the method includes:

Before receiving the registration request initiated by the terminal, sending slice configuration information to the terminal;

Wherein, the slice configuration information is used to indicate how the terminal sends the slice identifier of the network slice.

In a third aspect, an embodiment of the present invention further provides a communication processing device, including:

The first transceiver is configured to: receive slice configuration information sent by the network side device before initiating a registration request to the network side device.

The first processor is configured to: determine, according to the slice configuration information, a sending manner of a slice identifier of a network slice.

In a fourth aspect, the embodiment of the present invention further provides a communication processing device, including:

The second transceiver is configured to: send slice configuration information to the terminal before receiving a registration request initiated by the terminal;

Wherein, the slice configuration information is used to indicate how the terminal sends the slice identifier of the network slice.

In the fifth aspect, the embodiment of the present invention also provides a communication device, including: a transceiver, a memory, a processor, and a program stored in the memory and operable on the processor; it is characterized in that the processing A device for reading the program in the memory to implement the steps in the method described in the aforementioned first aspect; or, the steps in the method described in the aforementioned second aspect.

In the sixth aspect, the embodiments of the present invention also provide a readable storage medium for storing a program, and when the program is executed by a processor, the steps in the method described in the aforementioned first aspect are realized, or, the steps in the method described in the aforementioned second aspect are realized. Steps in the methods described in the aspect.

In this embodiment of the application, the terminal can receive slice configuration information sent by the network-side device before initiating a registration request to the network-side device, so that during the registration process and subsequent communication between the terminal and the network-side device, the terminal can Instructions to determine whether to send the slice ID and the specific way of sending, so as to avoid leakage of the slice ID during the terminal registration process and subsequent communication process, and improve the security of information in the communication process.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments of the present invention. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 is a schematic structural diagram of an applicable network system in an embodiment of the present invention;

FIG. 2 is one of the schematic flowcharts of a communication processing method provided by an embodiment of the present invention;

FIG. 3 is the second schematic flow diagram of the communication processing method provided by the embodiment of the present invention;

FIG. 4 is a schematic flow diagram of an RRC connection provided by an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a wireless random access process provided by an embodiment of the present invention;

FIG. 6 is a schematic flowchart of sending system information provided by an embodiment of the present invention;

Fig. 7 is one of the structural schematic diagrams of the communication processing device provided by the implementation of the present invention;

Fig. 8 is the second structural diagram of the communication processing device provided by the implementation of the present invention;

FIG. 9 is a schematic structural diagram of a communication device provided by the implementation of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

The terms "first", "second" and the like in the embodiments of the present invention are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus. In addition, the use of "and/or" in this application means at least one of the connected objects, such as A and/or B and/or C, means that A alone, B alone, C alone, and both A and B exist, Both B and C exist, both A and C exist, and there are 7 situations where A, B, and C all exist.

Please refer to FIG. 1 . FIG. 1 is a structural diagram of an applicable network system according to an embodiment of the present invention. As shown in FIG. 1 , it includes a data sending device 11 and a data receiving device 12 .

Wherein, communication can be performed between the data sending device 11 and the data receiving device 12 . The data sending device 11 sends ciphertext information (Ciphertext Block) to the data receiving device 12 .

Among them, the data sending device 11 can be used to perform:

Before receiving the registration request initiated by the terminal, sending slice configuration information to the terminal;

Wherein, the slice configuration information is used to indicate how the terminal sends the slice identifier of the network slice.

The data receiving device 12 may be used to perform:

Before initiating a registration request to the network-side device, receiving slice configuration information sent by the network-side device;

According to the slice configuration information, a sending manner of the slice identifier of the network slice is determined.

In practical applications, the data sending device 11 may be a terminal (also called user equipment (User Equipment, UE)), and the data receiving device 12 may be a network-side device; or, the data sending device 11 may be a network-side device, and the data receiving Device 12 may be, but is not limited to, a terminal.

The terminal can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (LaptopComputer), a personal digital assistant (Personal Digital Assistant, PDA), a mobile Internet device (MobileInternet Device, MID), a wearable device (Wearable Device) or vehicle equipment, etc. The network side device may be a base station, an Access and Mobility Management Function (Access and Mobility Management Function, AMF), a relay, an access point, or other network elements.

The communication processing method provided by the embodiment of the present invention is described below.

Referring to FIG. 3 , FIG. 3 is one of schematic flowcharts of a communication processing method provided by an embodiment of the present invention. The communication processing method shown in FIG. 3 may be executed by a terminal.

As shown in Figure 3, the communication processing method may include the following steps:

Step 301. Before initiating a registration request to the network-side device, receive slice configuration information sent by the network-side device.

In this embodiment of the present application, the timing for the network side device to send the slice configuration information is before the terminal initiates a registration request, including but not limited to when the terminal enters the cell to which the network side device belongs (or the covered network area), when the terminal sends the slice configuration information to the network side. When the device initiates an RRC wireless connection establishment request, and when the terminal initiates a wireless random access request to the network side device, specific settings can be made based on actual scenarios.

The above slice configuration information can be understood as a transmission configuration information of the network slice identifier, which is used to instruct the terminal to send the network slice identifier according to service requirements. Exemplarily, the above slice configuration information may indicate whether the terminal needs to transmit the slice identifier in the subsequent communication process. At the same time, the above slice configuration information may also describe the network slice identifier, for example, indicating the value method of the network slice identifier, indicating the application message type etc. Of course, in some embodiments, in order to improve the security of the network slice identifier transfer, the above slice configuration information may also indicate the security policy when the network slice identifier is transferred, which will not be listed here.

It should be understood that the network side device may actively send the above information to the terminal, or may trigger sending in response to a request initiated by the terminal, and the above slice configuration information may also be transmitted in a carrier such as signaling, which is not limited here.

Step 302: Determine a sending mode of a slice identifier of a network slice according to the slice configuration information.

It can be seen from the above content that the above slice configuration information can be sent by the network side device to the terminal, therefore, after receiving the above slice configuration information, the terminal can determine the sending mode of the slice identifier of the network slice according to the indication of the slice configuration information. Exemplarily, whether to send the network slice, the type of the network slice to be sent, the sending policy, etc. can be determined through different field contents in the slice identifier.

It should be understood that the foregoing network slices may be one group or multiple groups, which may be specifically determined according to service or session scenarios. That is, the above slice configuration information may include information indicating a network slice identifier, a slice identifier used to inform the terminal of which network slice to deliver, or an information set of network slices that can be delivered to the terminal. Among them, the transmission method can be applied to any communication process after the terminal receives the above slice configuration information, such as initial registration, periodic registration, mobile registration and slice request process, etc., to indicate the way the wireless access layer should carry the slice identifier .

The above-mentioned slice identifier may be a slice identifier corresponding to a network slice, and the above-mentioned slice identifier may exist in the form of a numeric character string, an alphabetic character string, or a combined character string, and is used to identify a corresponding network slice. During the communication process with the network side device, the terminal may send the above slice identifier to indicate the service type of the terminal during the communication process.

In this embodiment of the application, the terminal can receive slice configuration information sent by the network-side device before initiating a registration request to the network-side device, so that during the registration process and subsequent communication between the terminal and the network-side device, the terminal can Instructions to determine whether to send the slice ID and the specific way of sending, so as to avoid leakage of the slice ID during the terminal registration process and subsequent communication process, and improve the security of information in the communication process.

Further, in the prior art, the core network controls and configures the mode indication of the slice identification, and the slice identification indication information is valid in the control area of the network element of the core network, and the user terminal follows the slice identification inclusion mode indication in this The area performs slice information transmission.

Since different network areas can be set to different slice identification modes, if the terminal moves from the source network area to the target network area, before the registration request is initiated and completed, the slice information of the user terminal is still issued by the source coverage area network The slice id contains a mode indication, possibly passing the slice id to the network. However, in the embodiment of the present application, by sending the slice configuration information to the terminal through the network side device before initiating a registration request, it can ensure that before the terminal registers in the current network area, the transmission method of the corresponding network slice identifier can be obtained, avoiding the occurrence of The leaking of slice identifiers when crossing regions further improves the security of information in the communication process.

Optionally, the above step 301 includes:

Initiate a wireless connection establishment request to the network side device;

receiving the first signaling sent by the network side device in response to the wireless connection establishment request, where the first signaling carries the slice configuration information.

In this embodiment of the present application, the terminal may receive the above slice configuration information during a radio resource control (Radio Resource Control, RRC) connection establishment request process. For the RRC connection establishment request, the terminal usually needs to first send the RRC wireless connection establishment request (RRC Setup Request) signaling to the network side device in the idle state, and the RRC wireless connection establishment request (RRC Setup Request) signaling can carry the user device ID and the reason for RRC establishment.

After receiving the above wireless connection establishment request, the network side device can send corresponding first signaling to the terminal according to the user's device ID and the reason for RRC establishment, such as wireless connection establishment (RRC Setup) signaling, the first signaling carries There is slice configuration information to indicate how to send subsequent slice IDs.

It should be understood that after receiving the first signaling above, the terminal may send subsequent messages to the network side device according to the indication of the slice configuration information, and determine whether to carry the slice identifier and the type of the slice identifier in the subsequent message.

In the embodiment of this application, the network side device can send the above slice configuration information during the RRC connection establishment request process, so that the terminal can determine the sending mode of the slice ID before the registration process, avoiding the risk of slice ID leakage, and improving the transfer of slice ID security.

Optionally, receiving slice configuration information sent by the network side device includes:

Initiate a wireless random access request to the network side device;

receiving second signaling sent by the network side device in response to the wireless random access request, where the second signaling carries the slice configuration information.

In this embodiment of the present application, the terminal may also receive the above slice configuration information during a wireless random access (Random Access) process.

Specifically, the terminal usually needs to first send a random access preamble (Random Access Preamble) signaling to the network side device in an idle state, so as to inform the network side device that there is a wireless random access request. In response to the foregoing wireless random access request, the network side device sends second signaling carrying slice configuration information to the terminal, such as random access response (Random Access Response, RAR) signaling.

After receiving the above-mentioned second signaling, the terminal may send subsequent messages to the network side device according to the indication of the slice configuration information, and determine whether to carry the slice identifier and the type of the slice identifier in the subsequent message.

In the embodiment of this application, the network side device can send the above slice configuration information during the wireless random access process, so that the terminal can determine the sending mode of the slice ID before the registration process, avoiding the risk of slice ID leakage, and improving the transfer of slice ID security.

Optionally, receiving slice configuration information sent by the network side device includes:

receiving a system message broadcast and sent by the network side device, where the system message carries the slice configuration information.

In this embodiment of the present application, the network side device may also actively send a system message (System Information) carrying slice configuration information to the terminal. It can be understood that the above system message may be sent to at least some terminals in the network coverage area in a broadcast manner. That is to say, there may be multiple terminals that receive the above-mentioned system message, and may send subsequent messages to the network side device according to the indication of the slice configuration information carried in the system message, and determine whether to carry the slice identifier and the slice identifier in the subsequent message. Types of identification, etc.

The network-side device can actively send the above slice configuration information to the terminal, so that the terminal can determine the sending mode of the slice ID before the registration process, avoiding the risk of slice ID leakage, and improving the security of slice ID transmission.

Optionally, the slice configuration information includes at least one of the following:

First information, where the first information is used to indicate whether the first message sent by the terminal (for example, RRCSETUP COMPLETE message or other messages) carries the slice identifier;

Second information, where the second information is used to indicate the value-taking mode of the slice identifier, or the second information is used to indicate the corresponding relationship between the value-taking mode of the slice identifier and the type of registration request initiated by the terminal;

The third information, the third information is used to indicate the encryption information of the slice identifier, wherein, when the third information is the first value, the slice identifier is not encrypted; when the third information is the second value, the slice ID is encrypted, and the encryption mode of the slice ID is the encryption mode corresponding to the second value.

In the embodiment of the present application, the above slice configuration information may be specifically used to indicate whether to send the slice ID, the way of obtaining the value of the slice ID, encryption information of the slice ID, and the like. That is, the slice configuration information may include at least one item of the above-mentioned first information, second information, and third information, so as to target transmission methods in different service scenarios.

In this way, the terminal can choose whether to carry the slice identifier in the first message sent subsequently according to the indication of the first information, so that the slice identifier sent by the terminal can be prevented from being intercepted when the network side device does not need the terminal to send the slice identifier. lead to information leakage.

Wherein, the first message may be an RRC SETUP COMPLETE message or other messages sent by the terminal based on the first signaling, which is not limited herein.

The terminal can determine the way to obtain the value of the slice identifier according to the indication of the second information (such as indicating which reference information the slice identifier parameter reported by the terminal should obtain from), and these reference information include the following parameters previously obtained and saved by the terminal: Allow The NSSAIs (Allowed Network Slice Selection AssistanceInformation), configured NSSAIs (configured Network Slice Selection AssistanceInformation), or the NSSAI used by the session connection.

It should be understood that the values of the above reference information may be all values, and the terminal determines at least part of the values required in the current service scenario from the above reference information. Of course, the network side device can also pre-refer to the first information in the information according to the device information and service scenarios of the terminal, or according to the type of message sent by the terminal (such as initial registration, mobility registration, periodic registration, service request message, etc.). The relationship between the message and the way to get the value is sent to the terminal, which is not further limited here.

Of course, in some embodiments, the above second information may also be used to indicate the correspondence between the way of obtaining the value of the slice identifier and the type of the registration request initiated by the terminal.

It should be understood that the above first message may be a signaling message sent by the terminal to the network side device during or after the registration process, including but not limited to initial registration, periodic registration, mobile registration, and slice request processes.

Furthermore, in order to ensure the security of information, certain encryption measures are often taken during the communication process. In this embodiment of the present application, the terminal may also determine the encryption information of the slice identifier according to the indication of the third information.

Specifically, the above third information may indicate whether to encrypt and an encryption method, and may contain different key information according to the actual encryption method. Wherein, when the third information is the first value, the slice identifier is not encrypted; when the third information is the second value, the slice identifier is encrypted, and the encryption method of the slice identifier is the The encryption method corresponding to the second value.

In this embodiment of the present application, the above-mentioned encrypted information may include an encrypted indication of the slice ID, and the above-mentioned third information is sent to the terminal by the network-side device. If the network-side device does not require the terminal to encrypt the slice ID, the network-side device can The third information is set to the first value "NULL (none)" or the third information is set to other character strings used to indicate that there is no encrypted information, or the network side device may not send the above third information directly.

If the terminal receives the third information indicating "NULL", or does not receive the third information, the terminal does not need to encrypt the slice identifier.

If the network-side device needs to encrypt the slice identifier for the terminal, the network-side device can set the third information as the second value, such as "1" or "2", or set the third information as the value used to indicate the existence of encrypted information. A character string, when the terminal receives the above third information, that is, when sending the above first message, the terminal may encrypt the slice identifier.

Further, the above third information may include the indicated encryption mode and key information corresponding to the encryption mode. It can be understood that the above-mentioned encryption method may be the previously preset encryption method of the terminal and the network-side device, that is, the above-mentioned third information may include an identification field (ie, the above-mentioned second value) indicating the encryption method, and the terminal identifies the identification field by Then you can know the corresponding default encryption method.

Exemplarily, the terminal may determine the encryption mode according to the specific value of the second value. In a specific implementation manner, when the second value of the above-mentioned third information is "1", the terminal may use the first encryption algorithm to encrypt the slice identifier; when the second value of the above-mentioned third information is "2" , the terminal may use the second encryption algorithm to encrypt the slice identifier, and so on.

Of course, in some embodiments, the above third information may also include a specific encryption instruction, so that after receiving the above third information, the terminal may encrypt the slice identifier according to the encryption instruction in the third information, which is not limited here. .

In the embodiment of the present application, by setting the third information, the terminal and the network side device can choose whether to encrypt the slice identifier according to the actual service scenario, thereby improving the flexibility of information processing in the communication process.

It can be understood that the above-mentioned encryption method can be a method and approach to achieve information confidentiality by hiding and transforming information, such as MD5 encryption, symmetric encryption, and asymmetric encryption. Correspondingly, the above-mentioned third information may also include a corresponding encryption key, and the third information is sent to the terminal through the network side device to indicate the specific encryption method of the terminal, which can further improve the security of slice identifier transmission.

Of course, in other optional embodiments, the sending of the slice identifier may also undergo information integrity protection or verification to improve the security of information sending, which is not limited here.

Referring to FIG. 4, FIG. 4 is the second flowchart of the communication processing method provided by the embodiment of the present invention. The communication processing method in the embodiment of the present invention may be executed by a network side device.

As shown in Figure 4, the communication processing method may include the following steps:

Step 401. Before receiving a registration request initiated by a terminal, send slice configuration information to the terminal.

Wherein, the slice configuration information is used to indicate how the terminal sends the slice identifier of the network slice.

Corresponding to the above-mentioned step 301, the time when the above-mentioned network-side device sends the slice configuration information is before the terminal initiates a registration request, including but not limited to when the terminal enters the cell to which the network-side device belongs (or the covered network area), when the terminal sends the slice configuration information to the network side. When the device initiates an RRC wireless connection establishment request, and when the terminal initiates a wireless random access request to the network side device, specific settings can be made based on actual scenarios.

The above slice configuration information can be understood as a transmission configuration information of the network slice identifier, which is used to instruct the terminal to send the network slice identifier according to service requirements. Exemplarily, the above slice configuration information may indicate whether the terminal needs to transmit the slice identifier in the subsequent communication process. At the same time, the above slice configuration information may also describe the network slice identifier, for example, indicating the value method of the network slice identifier, indicating the application message type etc. Of course, in some embodiments, in order to improve the security of the network slice identifier transfer, the above slice configuration information may also indicate the security policy when the network slice identifier is transferred, which will not be listed here.

It should be understood that the network side device may actively send the above information to the terminal, or may trigger sending in response to a request initiated by the terminal, and the above slice configuration information may also be transmitted in a carrier such as signaling, which is not limited here.

In the communication processing method of this embodiment, the network side device sends slice configuration information to the terminal to indicate how the terminal sends the slice identifier of the network slice, and the terminal can receive the network side device before initiating a registration request to the network side device. slice configuration information, so that during the registration process between the terminal and the network-side device and the subsequent communication process, the terminal can determine whether to send the slice identifier and the specific method of sending it according to the indication of the slice configuration information, so as to avoid the terminal from registering. And the leakage of slice identification in the subsequent communication process improves the security of information in the communication process.

Further, in the prior art, the core network controls and configures the mode indication of the slice identification, and the slice identification indication information is valid in the control area of the network element of the core network, and the user terminal follows the slice identification inclusion mode indication in this The area performs slice information transmission.

Since different network areas can be set to different slice identification modes, if the terminal moves from the source network area to the target network area, before the registration request is initiated and completed, the slice information of the user terminal is still issued by the source coverage area network The slice id contains a mode indication, possibly passing the slice id to the network.

However, in the embodiment of the present application, by sending the slice configuration information to the terminal through the network side device before initiating a registration request, it can ensure that before the terminal registers in the current network area, the transmission method of the corresponding network slice identifier can be obtained, avoiding the occurrence of The leaking of slice identifiers when crossing regions further improves the security of information in the communication process.

Optionally, sending slice configuration information to the terminal, including:

receiving a wireless connection establishment request initiated by the terminal;

In response to the wireless connection establishment request, send first signaling to the terminal, where the first signaling carries the slice configuration information.

Optionally, sending slice configuration information to the terminal, including:

receiving a wireless random access request initiated by the terminal;

In response to the wireless random access request, send second signaling to the terminal, where the second signaling carries the slice configuration information.

Optionally, sending slice configuration information to the terminal, including:

Sending a system message by broadcast, where the system message carries the slice configuration information.

Optionally, the slice configuration information includes at least one of the following:

The first information is used to indicate whether the terminal transmits the slice identifier;

Second information, where the second information is used to indicate the value-taking mode of the slice identifier, or the second information is used to indicate the corresponding relationship between the value-taking mode of the slice identifier and the type of registration request initiated by the terminal;

The third information, the third information is used to indicate the encryption information of the slice identifier, wherein, when the third information is the first value, the slice identifier is not encrypted; when the third information is the second value, the slice ID is encrypted, and the encryption mode of the slice ID is the encryption mode corresponding to the second value.

For the specific implementation manner of the above-mentioned embodiment of the method executed by the network side device, reference may be made to the explanation in the above-mentioned embodiment of the method executed by the terminal, and details are not repeated here to avoid repetition.

It should be noted that this embodiment is an implementation manner of the network side device corresponding to the above method embodiment, therefore, reference may be made to relevant descriptions in the above method embodiment, and the same beneficial effects may be achieved. In order to avoid repeated description, details are not repeated here.

The various optional implementation manners introduced in the embodiments of the present invention may be implemented in combination with each other if they do not conflict with each other, or may be implemented independently, which is not limited by the embodiments of the present invention.

For ease of understanding, the examples are as follows:

Embodiment one:

Referring to FIG. 4 , during the RRC connection establishment request process, the base station sends slice configuration information to the terminal in the first signaling (connection request response message). The above-mentioned communication processing method may include the following steps:

When the terminal is in the idle state, when it is necessary to initiate the establishment of a wireless connection, the terminal initiates a wireless connection establishment request to the network side device;

After receiving the terminal's wireless connection request, the network side device sends a wireless connection establishment response message to the terminal, and sets the newly added "wireless slice identifier transfer configuration information (that is, the above slice configuration information, including There is first information, or second information, or third information)".

The terminal receives the first signaling (wireless connection establishment response message) of the network-side device's response, obtains the "wireless slice ID transfer configuration information" therein, and decides how to transfer the wireless slice ID in subsequent wireless connection request messages.

Embodiment two:

Referring to FIG. 5 , in the initial random access process, the base station sends a wireless slice identifier transfer instruction to the terminal through the second signaling (in the response message of the random access request). The above-mentioned communication processing method may include the following steps:

When the terminal is in an idle state, when it is necessary to establish a wireless connection, the terminal initiates a wireless random access request to the wireless network side device.

After receiving the wireless random slicing request from the terminal, the network side device sends the second signaling (response message for wireless random access) to the terminal, and sets the newly added "slicing configuration information" in the second signaling (response message). (contains the first information, or the second information, or the third information)".

The terminal receives the second signaling (wireless random access response message) from the network-side device, obtains the "wireless slice identifier transfer configuration information" therein, and initiates a signaling message of a wireless connection request to the network-side device.

Embodiment three:

The base station broadcasts and issues the third signaling to the terminals in all the cells through the third signaling (system broadcast message mode). Referring to FIG. 6, the communication processing method described above may include the following steps:

The network side device adds "wireless slice identifier transfer configuration information (including the first information, or the second information, or the third information)" in the first signaling (system broadcast message), and sends the system broadcast message to all The terminal performs broadcast delivery.

When the terminal is in an idle state, the receiving network side device obtains the "slicing configuration information" through the third signaling (system broadcast message).

In the signaling message for initiating a wireless connection request to the network side device, the terminal decides how to transmit the slice identifier in the wireless connection request information according to the "slice configuration information".

From the above content, we can see that the slice configuration information is sent by the network side device to the terminal, and the content mainly includes:

The first information indicates whether/whether the terminal needs to carry the slice identifier in the wireless message sent.

Alternatively, the second information may also be included, indicating:

The value source of the slice identifier carried by the terminal in the wireless message sent (for example, all or part of the value is obtained from ConfigurationNSSAI, Allowed NSSAI, or the NSSAI used by the session);

According to the type of message sent by the UE (such as initial registration, mobility registration, periodic registration, service request message, etc.) to indicate which source of the slice identifier is carried

Alternatively, a third message may also be included, indicating:

Whether to encrypt the slice ID,

If the slice identifier is encrypted, the encryption method used by the terminal and the network.

Accordingly, the following examples are provided:

Embodiment four:

The network side device instructs the terminal not to carry the slice identifier:

First information (slice identifier carrying indication): "No". Issued by the network side device to the terminal, it means that the network side device requires the terminal not to carry any slice identifier in the wireless message, and the terminal does not need to check the second information (the value source of the slice identifier) and the third information (the encryption indication of the slice identifier) .

Embodiment five:

The network-side device instructs the terminal to carry the slice identifier, but slice information encryption is not required

The first information (slice identifier carrying indication): "yes". Issued by the network side device to the terminal, it indicates that the network side device requires the UE to carry the slice identifier in the wireless message.

The second information (the value source of the slice identifier): sent by the network-side device to the terminal, indicating which reference information the network-side device instructs the terminal to obtain the reported slice identifier parameter from. These reference information include the following parameters previously obtained and saved by the terminal: Allowed NSSAIs, or configured NSSAIs, or NSSAI used for session connection.

The third information (slice identification encryption indication): sent by the network side device to the terminal, if the network side device does not require the terminal to encrypt the slice, the network side device can set "none" in the third information, or the network side device can The third information is not sent; if the terminal receives the third information as "none" or does not receive the third information, the terminal does not need to encrypt the slice identifier.

Embodiment six:

The network-side device instructs the terminal to carry the slice identifier and encrypt slice information

The first information (slice identifier carrying indication): "yes". Issued by the network side device to the terminal, it indicates that the network side device requires the UE to carry the slice identifier in the wireless message.

The second information (the value source of the slice identifier): sent by the network-side device to the terminal, indicating which reference information the network-side device instructs the terminal to obtain the reported slice identifier parameter from. These reference information include the following parameters previously obtained and saved by the terminal: Allowed NSSAIs, or configured NSSAIs, or NSSAI used for session connection.

The third information (slice identification encryption instruction): sent by the network side device to the terminal, if the network side device requires the terminal to encrypt the slice, the network side device should set "encryption method" in the third information, indicating that the network side device requires The terminal encrypts the slice identifier using the specified encryption method. If the terminal receives the third information as "encryption method", the terminal needs to encrypt the slice identifier. The encryption method may be a certain encryption method pre-configured between network-side device terminals.

Further, during the cross-cell communication, the terminal may perform cell handover after the terminal enters the second cell from the first cell. It should be understood that the network side device may issue the above slice configuration information in response to the handover request sent by the terminal, so as to prevent the terminal from sending the slice identifier corresponding to the original first cell during the registration process of the second cell.

Of course, in other optional embodiments, during the process of cross-cell communication between terminals, the network side device can also implement the delivery of slice configuration information through the above embodiments, which can be set according to actual scenarios, and will not be repeated here. List them all.

Referring to FIG. 7, FIG. 7 is one of structural diagrams of a communication processing device provided by an embodiment of the present invention. As shown in Figure 7, the communication processing device 700 includes:

The first transceiver 701 is configured to: before initiating a registration request to the network side device, receive slice configuration information sent by the network side device.

The first processor 702 is configured to: according to the slice configuration information, determine a sending manner of a slice identifier of a network slice.

In this embodiment of the application, the terminal may receive the slice configuration information sent by the network-side device through the first transceiver before initiating a registration request to the network-side device, so that during the registration process and subsequent communication process between the terminal and the network-side device, the terminal The first processor can determine whether to send the slice identifier and the specific way of sending it according to the indication of the slice configuration information, so as to avoid the leakage of the slice identifier during the registration process and the subsequent communication process of the terminal, and improve the security of information in the communication process. safety.

Optionally, the first transceiver 701 includes:

a first wireless connection unit, configured to initiate a wireless connection establishment request to the network side device;

The first receiving unit is configured to receive the first signaling sent by the network side device in response to the wireless connection establishment request, where the first signaling carries the slice configuration information.

Optionally, the first transceiver 701 includes:

a second wireless connection unit, configured to initiate a wireless random access request to the network side device;

The second receiving unit is configured to receive the second signaling sent by the network side device in response to the wireless random access request, where the second signaling carries the slice configuration information.

Optionally, the first transceiver 701 includes:

The third receiving unit is configured to receive a system message broadcast and sent by the network side device, where the system message carries the slice configuration information.

Optionally, the slice configuration information includes at least one of the following:

first information, where the first information is used to indicate whether the first message sent by the terminal carries the slice identifier;

Second information, where the second information is used to indicate the value-taking mode of the slice identifier, or the second information is used to indicate the corresponding relationship between the value-taking mode of the slice identifier and the type of registration request initiated by the terminal;

The third information, the third information is used to indicate the encryption information of the slice identifier, wherein, when the third information is the first value, the slice identifier is not encrypted; when the third information is the second value, the slice ID is encrypted, and the encryption mode of the slice ID is the encryption mode corresponding to the second value. The communication processing device 700 can implement each process of the method embodiment in FIG. 3 in the embodiment of the present invention, and achieve the same beneficial effect. To avoid repetition, details are not repeated here.

Referring to FIG. 8 , FIG. 8 is a second structural diagram of a communication processing device provided by an embodiment of the present invention. As shown in FIG. 8, the communication processing device 800 includes:

The second transceiver 801 is configured to send slice configuration information to the terminal before receiving a registration request initiated by the terminal;

Wherein, the slice configuration information is used to indicate how the terminal sends the slice identifier of the network slice.

In the communication processing method of this embodiment, the network-side device may send slice configuration information to the terminal through the second transceiver to indicate how the terminal sends the slice identifier of the network slice, and the terminal may, before initiating a registration request to the network-side device, Receive the slice configuration information sent by the network-side device, so that in the registration process and subsequent communication process between the terminal and the network-side device, the terminal can determine whether to send the slice identifier and the specific way of sending it according to the indication of the slice configuration information, so that it can It avoids the disclosure of slice identifiers during the registration process of the terminal and the subsequent communication process, and improves the security of information during the communication process.

Optionally, the second transceiver 801 includes:

a fourth receiving unit, configured to receive a wireless connection establishment request initiated by the terminal;

A first sending unit, configured to send first signaling to the terminal in response to the wireless connection establishment request, where the first signaling carries the slice configuration information.

Optionally, the second transceiver 801 includes:

a fifth receiving unit, configured to receive a wireless random access request initiated by the terminal;

The second sending unit is configured to send second signaling to the terminal in response to the wireless random access request, where the second signaling carries the slice configuration information.

Optionally, the second transceiver 801 includes:

The third sending unit broadcasts and sends a system message, where the system message carries the slice configuration information.

Optionally, the slice configuration information includes at least one of the following:

The first information is used to indicate whether the terminal transmits the slice identifier;

Second information, where the second information is used to indicate the value-taking mode of the slice identifier, or the second information is used to indicate the corresponding relationship between the value-taking mode of the slice identifier and the type of registration request initiated by the terminal;

The third information, the third information is used to indicate the encryption information of the slice identifier, wherein, when the third information is the first value, the slice identifier is not encrypted; when the third information is the second value, the slice ID is encrypted, and the encryption mode of the slice ID is the encryption mode corresponding to the second value.

The communication processing device 800 can implement each process of the method embodiment in FIG. 4 in the embodiment of the present invention, and achieve the same beneficial effect. To avoid repetition, details are not repeated here.

The embodiment of the present invention also provides a communication device. Referring to FIG. 9 , the communication device may include a processor 901 , a memory 902 and a program 9021 stored in the memory 902 and executable on the processor 901 .

In the case where the communication device is a terminal, when the program 9021 is executed by the processor 901, any steps in the method embodiment corresponding to FIG. 3 can be implemented and the same beneficial effect can be achieved, and details are not repeated here.

In the case where the communication device is a network-side device, when the program 9021 is executed by the processor 901, any steps in the method embodiment corresponding to FIG. 4 can be implemented and the same beneficial effect can be achieved, which will not be repeated here.

Those skilled in the art can understand that all or part of the steps for implementing the methods of the above embodiments can be completed by program instructions related hardware, and the program can be stored in a readable medium. An embodiment of the present invention also provides a readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any of the above method embodiments corresponding to FIG. 3 or FIG. 4 can be implemented. Steps, and can achieve the same technical effect, in order to avoid repetition, no more details here.

The storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

The above are preferred implementations of the embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principle of the present invention, some improvements and modifications can also be made. These improvements and Retouching should also be regarded as the protection scope of the present invention.

Claims (14)

1. A communication processing method performed by a terminal, the method comprising:

before a registration request is initiated to a network side device, receiving slice configuration information sent by the network side device;

And determining the transmission mode of the slice identifier of the network slice according to the slice configuration information.

2. The method of claim 1, wherein receiving slice configuration information sent by the network side device comprises:

initiating a wireless connection establishment request to the network side equipment;

and receiving a first signaling sent by the network side equipment in response to the wireless connection establishment request, wherein the first signaling carries the slice configuration information.

3. The method of claim 1, wherein receiving slice configuration information sent by the network side device comprises:

initiating a wireless random access request to the network side equipment;

and receiving a second signaling sent by the network side equipment in response to the wireless random access request, wherein the second signaling carries the slice configuration information.

4. The method of claim 1, wherein receiving slice configuration information sent by the network side device comprises:

and receiving a system message sent by the network side equipment in a broadcasting way, wherein the system message carries the slice configuration information.

5. The method of any of claims 1-4, wherein the slice configuration information comprises at least one of:

The first information is used for indicating whether the terminal carries the slice identifier in a sent first message or not;

the second information is used for indicating the value-taking mode of the slice identifier or indicating the corresponding relation between the value-taking mode of the slice identifier and the type of the registration request initiated by the terminal;

third information, wherein the third information is used for indicating encryption information of the slice identifier, and the slice identifier is not encrypted when the third information is a first value; and when the third information is the second value, the slice identifier is encrypted, and the encryption mode of the slice identifier is the encryption mode corresponding to the second value.

6. A communication processing method performed by a network-side device, the method comprising:

before receiving a registration request initiated by a terminal, transmitting slice configuration information to the terminal;

the slice configuration information is used for indicating a sending mode of the terminal to the slice identifier of the network slice.

7. The method of claim 6, wherein transmitting slice configuration information to the terminal comprises:

receiving a wireless connection establishment request initiated by the terminal;

And responding to the wireless connection establishment request, and sending a first signaling to the terminal, wherein the first signaling carries the slice configuration information.

8. The method of claim 6, wherein transmitting slice configuration information to the terminal comprises:

receiving a wireless random access request initiated by the terminal;

and responding to the wireless random access request, and sending a second signaling to the terminal, wherein the second signaling carries the slice configuration information.

9. The method of claim 6, wherein transmitting slice configuration information to the terminal comprises:

and broadcasting and sending a system message, wherein the system message carries the slice configuration information.

10. The method of any of claims 6-9, wherein the slice configuration information comprises at least one of:

the first information is used for indicating whether the terminal transmits the slice identifier or not;

the second information is used for indicating the value mode of the slice identifier or indicating the corresponding relation between the value mode of the slice identifier and the type of the registration request initiated by the terminal;

third information, which is used for indicating encryption information of the slice identifier, wherein the slice identifier is not encrypted when the third information is a first value; and when the third information is the second value, the slice identifier is encrypted, and the encryption mode of the slice identifier is the encryption mode corresponding to the second value.

11. A communication processing apparatus, comprising:

a first transceiver for: before a registration request is initiated to a network side device, receiving slice configuration information sent by the network side device;

a first processor for: and determining the transmission mode of the slice identifier of the network slice according to the slice configuration information.

12. A communication processing apparatus, comprising:

a second transceiver for: before receiving a registration request initiated by a terminal, transmitting slice configuration information to the terminal;

the slice configuration information is used for indicating a sending mode of the terminal to the slice identifier of the network slice.

13. A communication device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; -characterized in that the processor is configured to read a program in a memory to implement the steps in the communication processing method according to any one of claims 1 to 5; or, a step in a communication processing method according to any one of claims 6 to 10.

14. A readable storage medium storing a program, wherein the program when executed by a processor implements the steps in the communication processing method according to any one of claims 1 to 5; or, the steps in a communication processing method according to any one of claims 6 to 10 are implemented.