Communication method, and device

Abstract

The present application relates to a communication method, and a device. The method comprises: a terminal receiving a first message from a first core network network element, wherein the first message is used by the terminal to determine whether to establish a session.

Description

Communication methods and devices Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0002] In related technologies, terminals typically initiate session establishment after completing registration. For example, the terminal first sends a registration request to the core network. Upon receiving the registration request, the core network triggers an authentication process for the terminal. After authentication, the core network and the terminal negotiate security capabilities, and then the core network sends a registration acceptance message to the terminal. Finally, the terminal sends a registration completion message to the core network. Only after completing this series of processes will the terminal initiate a session establishment request based on the actual situation. However, this approach limits the scenarios in which the terminal can trigger session establishment. Therefore, how to increase the ways to trigger terminal session establishment, making the scenarios for terminal session establishment more diverse and flexible, becomes a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and device.

[0004] This application provides a communication method, including:

[0005] The terminal receives a first message from a first core network element, wherein the first message is used by the terminal to determine whether to establish a session.

[0006] This application provides a communication method, including:

[0007] The first core network element sends a first message to the terminal, wherein the first message is used by the terminal to determine whether to establish a session.

[0008] This application provides a communication method, including:

[0009] The terminal sends a sixth message to the first core network element, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message.

[0010] This application provides a communication method, including:

[0011] The first core network element receives a sixth message from the terminal, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message.

[0012] This application provides a terminal, including:

[0013] The first communication unit is used to receive a first message from a first core network element, wherein the first message is used by the terminal to determine whether to establish a session.

[0014] This application embodiment provides a first core network element, including:

[0015] The second communication unit is used to send a first message to the terminal, wherein the first message is used by the terminal to determine whether to establish a session.

[0016] This application provides a terminal, including:

[0017] The first communication unit is used to send a sixth message to the first core network element, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message.

[0018] This application embodiment provides a first core network element, including:

[0019] The second communication unit is used to receive a sixth message from the terminal, wherein the sixth message is used to request the establishment of a third session, and the sixth message is carried by the initial NAS message.

[0020] This application provides a terminal, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the terminal to perform the methods described above.

[0021] This application provides a first core network element, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the first core network element to perform the aforementioned method.

[0022] This application provides a chip for implementing the above-described method. Specifically, the chip includes a processor for retrieving and running a computer program from a memory, causing a device equipped with the chip to perform the above-described method.

[0023] By adopting the above approach, the terminal can determine whether to establish a session based on the first message from the network side. This increases the number of ways the network side can trigger the terminal to establish a session, making the scenarios for terminal session establishment more diverse and flexible. Attached Figure Description

[0024] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application.

[0025] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application.

[0026] Figure 3 is a schematic flowchart of a communication method according to another embodiment of this application.

[0027] Figures 4 to 8 are various schematic flowcharts of a communication method according to an embodiment of this application.

[0028] Figure 9 is a schematic flowchart of a communication method according to another embodiment of this application.

[0029] Figure 10 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0030] Figure 11 is another schematic flowchart of a communication method according to an embodiment of this application.

[0031] Figure 12 is a schematic block diagram of a terminal according to an embodiment of this application.

[0032] Figure 13 is a schematic block diagram of a first core network element according to an embodiment of the present application.

[0033] Figure 14 is a schematic block diagram of a communication device according to an embodiment of this application.

[0034] Figure 15 is a schematic block diagram of a chip according to an embodiment of this application. Detailed Implementation

[0035] The technical solutions of this application embodiment can be applied to various communication systems, such as: LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), NR (New Radio), evolution of NR, WLAN (Wireless Local Area Network), WiFi (Wireless Fidelity), or other communication systems.

[0036] This application describes various embodiments in conjunction with network devices and terminals. The terminal can be mobile or fixed, and may also be referred to as a mobile station, user unit, etc. The terminal can be a station in a WLAN, or a smart terminal, wireless modem, laptop, tablet, etc. In this application embodiment, the terminal can be a VR (Virtual Reality) terminal / AR (Augmented Reality) terminal, industrial control terminal, autonomous driving terminal, telemedicine terminal, smart grid terminal, transportation safety terminal, smart city terminal, or smart home wireless terminal, etc. By way of example and not limitation, in this application embodiment, the terminal can also be a wearable device.

[0037] In this embodiment, the network device can be a device for communicating with a terminal. The network device can be an access point in a WLAN, an evolved base station in LTE, a relay station, a vehicle-mounted device, a wearable device, a network device in an NR network (gNB, the next generation Node B), a network device in a future PLMN network, or a network device in a non-terrestrial network, etc. By way of example and not limitation, in this embodiment, the network device can have mobility characteristics; for example, the network device can be a mobile device.

[0038] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies and basic concepts involved in the embodiments of this application are described below. The following related technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0039] Figure 1 exemplarily illustrates a communication system 100. The communication system includes network devices 110 and terminals 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include one or more terminals 120; this embodiment does not limit this. In another possible implementation, the communication system 100 may also include other network entities such as mobility management entities and access and mobility management functions; this embodiment does not limit this. The network devices may further include access network devices and first core network devices. That is, the communication system may also include multiple core networks for communicating with the access network devices. The access network devices may be base stations of LTE, LTE-A, or NR systems. Taking the communication system shown in Figure 1 as an example, the communication devices may include network devices and terminals with communication functions. The communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities; this embodiment does not limit this.

[0040] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0041] S210. The terminal receives a first message from a first core network element, wherein the first message is used by the terminal to determine whether to establish a session.

[0042] Figure 3 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0043] S310. The first core network element sends a first message to the terminal, wherein the first message is used by the terminal to determine whether to establish a session.

[0044] In this embodiment of the application, the first core network element can be any control plane network element on the core network side. For example, the control plane network element can be a network element with mobility management function. The network element with mobility management function may include AMF (Access and Mobility Management Function), etc. The AMF may be 5G-AMF (AMF in 5G system architecture) or 6G-AMF (AMF in 6G system), etc., and is not limited or exhaustively listed here.

[0045] The sessions involved in the embodiments of this application may refer to PDU (Protocol Data Unit) sessions, which will not be repeated below.

[0046] The first message carries one of the following: a security mode command, a registration acceptance message, or a service acceptance message.

[0047] In some possible implementations, before the terminal receives the first message from the first core network element, the process may further include: the terminal sending a registration request message to the first core network element. Before the first core network element sends the first message to the terminal, the process may further include: the first core network element receiving the registration request message from the terminal.

[0048] The registration request message may carry at least one of the following: the terminal's identifier, the registration type, or the terminal's capability information.

[0049] The terminal's identifier may include at least one of the terminal's SUCI (Subscription Concealed Identifier) ​​and GUTI (Globally Unique Temporary UE Identity). For example, the GUTI may be a 6G-GUTI.

[0050] The registration type can be any of the following: initial registration, mobility update management (or mobility registration, or mobility registration update management). Preferably, in this embodiment, the registration type can be initial registration, and the registration request message can be an initial registration request message.

[0051] The terminal's capability information may include at least the terminal's security capabilities. This embodiment does not limit the specific content included in the terminal's capability information or security capabilities.

[0052] It should be noted that, in addition to carrying at least one of the above-mentioned terminal identifier, registration type, and terminal capability information, the registration request message may also carry other content stipulated in the relevant agreement, which will not be limited or exhaustively listed here.

[0053] After receiving a registration request message from the terminal, the first core network element can also trigger an authentication process. This authentication process can be a one-way authentication process or a two-way authentication process performed between the core network side and the terminal. The core network side can refer to any network element on the core network side that participates in the authentication process, such as the first core network element on the core network side, authentication network elements (such as AUSF (Authentication Server Function)), etc., at least one of them. Here, we do not limit or exhaustively list any network elements on the core network side that participate in the authentication process, nor do we limit the processing of this authentication process.

[0054] The first core network element may send a first message during the authentication process and the terminal registration process. This first message carries first information, which is used by the terminal to determine whether to establish a session. The first message may carry implicit or explicit indications to enable the terminal to determine whether to initiate session establishment processing.

[0055] After receiving the first message from the first core network element, the terminal may send a second message to the first core network element requesting the establishment of a first session. The second message may carry one of the following: a security mode completion message, a registration completion message, a service completion message, or an uplink NAS (Non-Access Stratum) transport message.

[0056] The specific content and transmission method of the first message, the specific content and transmission method of the second message, will be described in detail below with reference to various embodiments.

[0057] In some possible embodiments, the first message may carry first information, wherein the first information is used to indicate whether the terminal should establish a session. The first information may be called session establishment indication information or PDU session establishment indication information. The first information may be an explicit indication, the function of which is to enable the terminal to determine whether a session needs to be established, and if it determines that a session needs to be established, to initiate a message to request session establishment.

[0058] Here, whether the terminal establishes a session can refer to whether the network side requires the terminal to establish a session. In other words, the first information can be used to indicate whether the terminal needs to establish a session, or whether the network side requires the terminal to establish a session. The network side can at least include the first core network element on the core network side.

[0059] Furthermore, establishing a session can include establishing a session during the registration process; that is, whether the terminal establishes a session during the registration process refers to whether the network side requires the terminal to establish a session during the registration process. In other words, the first information can be used to indicate whether the terminal needs to establish a session during the registration process, or whether the network side requires the terminal to establish a session during the registration process.

[0060] In this embodiment, the first core network element may send a first message carrying first information (or session establishment indication information) after determining whether the terminal needs to establish a session or whether the terminal establishes a session during the registration process.

[0061] In one scenario, the first core network element may determine whether a terminal needs to establish a session based on a pre-configured policy.

[0062] For example, the pre-configured policies of the first core network element may include triggering the establishment of a session when any terminal initiates registration. That is, as long as the first core network element receives a registration request message from a terminal, it determines that the terminal needs to establish a session or needs to establish a session during the registration process.

[0063] For example, the first core network element is pre-configured with a policy that triggers the establishment of a session when a terminal initiating registration is located within a specified area. The specified area can be configured according to actual conditions, and this embodiment does not impose any limitations. That is, after receiving the terminal's registration request message, the first core network element, if it determines that the terminal is located within the specified area, determines whether the terminal needs to establish a session or needs to establish a session during the registration process.

[0064] In one scenario, the first core network element may combine relevant terminal information and pre-configured policies to jointly determine whether the terminal needs to establish a session.

[0065] The relevant information of the terminal may include at least one of the following: terminal capability information, terminal subscription information, etc. The terminal capability information may be carried in the registration request message, and the terminal subscription information may be obtained by the first core network element from the UDM.

[0066] The pre-configured strategies of the first core network element may include at least one of the following: triggering the terminal to establish a session or to establish a session during the registration process when the terminal supports establishing a session during the registration process; triggering the terminal to establish a session or to establish a session during the registration process when the terminal supports establishing a session during the registration process and the terminal is located in a specified area.

[0067] For example, the pre-configured policy of the first core network element includes triggering the terminal to establish a session or to establish a session during the registration process if the terminal supports establishing a session during registration and is located within a designated area. Correspondingly, after receiving the terminal's registration request message, the first core network element determines whether the terminal supports or is allowed to establish a session during registration based on the terminal's relevant information. If it does, it determines whether the terminal is located within a designated area. If it is located within a designated area, it can determine, based on the pre-configured policy, that the terminal needs to establish a session or needs to establish a session during registration.

[0068] The determination of whether a terminal supports or allows the establishment of a session during the registration process based on relevant terminal information may include: determining whether a terminal supports the establishment of a session during the registration process based on the terminal's capability information, and / or determining whether a terminal allows the establishment of a session during the registration process based on the terminal's subscription information, etc., which are not limited here.

[0069] In one scenario, the first core network element may determine whether the terminal needs to establish a session (or whether the terminal needs to establish a session during the registration process) based on instruction information related to session establishment.

[0070] The session establishment-related indication information may come from a second core network element (such as an SMF) or other core network elements or an AF (Application Function). This session establishment-related indication information may include the identifiers and / or types of one or more terminals that need to establish a session (or need to establish a session during the registration process). The second core network element or other core network element or AF may determine whether a session needs to be established or whether a session needs to be established during the registration process based on relevant terminal information and / or pre-configured policies, etc., without limitation or exhaustive list.

[0071] The timing or processing of receiving instruction information related to session establishment may be as follows: After the first core network element receives a registration request message from the terminal, it sends a message to the second core network element or other core network elements inquiring whether the terminal needs to establish a session, and then receives instruction information related to session establishment from the second core network element or other core network elements. It should be noted that this is merely an illustrative example; in actual processing, the timing or process by which the first core network element receives instruction information related to session establishment includes, but is not limited to, the methods described in the above example, and is not limited or exhaustive here.

[0072] For example, after receiving instruction information related to session establishment and a registration request message from a terminal, the first core network element may first determine whether the terminal's identifier is included in the identifiers of one or more terminals that need to establish a session (or need to establish a session during the registration process) in the instruction information related to session establishment, and / or determine whether the terminal's type is included in the types of one or more terminals that need to establish a session (or need to establish a session during the registration process) in the instruction information related to session establishment. If it is included, then it is determined that the terminal needs to establish a session or needs to establish a session during the registration process.

[0073] In one embodiment, when a terminal needs to establish a session, the first core network element sends a first message carrying first information, which is used to instruct the terminal to establish a session.

[0074] In other words, as long as the first message carries the first information, it is used to instruct the terminal to establish a session. Specifically, the first information used to instruct the terminal to establish a session can mean that the first information is used to instruct (the network side) that the terminal needs to establish a session, or to instruct (the network side) that the terminal needs to establish a session during the registration process.

[0075] In this embodiment, the specific components of the first information can be configured according to actual conditions. For example, the first information may be descriptive information, such as "establish" or "yes," etc., and its specific content is not limited or exhaustively listed here. Alternatively, the first information may be a specified value, the length of which can be 1 bit, and the specified value may be 1 or 0; this is not limited here.

[0076] In one embodiment, the first core network element can send a first message carrying first information whether or not the terminal needs to establish a session. That is, the first information is used to instruct the terminal to establish a session or not. Specifically, the first information instructing the terminal to establish a session or not can mean that the first information can be used to instruct (on the network side) whether the terminal needs to establish a session or not; or that the first information can be used to instruct (on the network side) whether the terminal needs to establish a session during the registration process or not.

[0077] In this example, the specific components of the first piece of information can also be configured according to the actual situation.

[0078] For example, the first information may include an indicator bit, which is used to instruct the terminal to establish a session when the indicator bit has a first value, and to instruct the terminal not to establish a session when the indicator bit has a second value.

[0079] For example, the first information may include either first descriptive information or second descriptive information. When the first information includes the first descriptive information, it is used to instruct the terminal to establish a session; when the first information includes the second descriptive information, it is used to instruct the terminal not to establish a session. The specific content of the first and second descriptive information can be configured according to the actual situation. For example, the first descriptive information may include any one of "establish" or "yes," and the second descriptive information may include any one of "do not establish" or "No." This is not limited or exhaustive.

[0080] In one embodiment, the first message may be carried by a Security Mode Command (SMC).

[0081] In this example, the first core network element sending the first message to the terminal could be as follows: after completing the authentication process, the first core network element sends a security mode command to the terminal, which carries the first message. Correspondingly, the terminal receiving the first message from the first core network element could be as follows: the terminal receives a security mode command carrying the first message from the first core network element.

[0082] The first message may only carry the first information. In this embodiment, the first message can be equivalent to the first information. In other words, the first information can be carried by the safe mode command.

[0083] Specifically, the first information can be carried by the first IE (Information Elements) in the safe mode command.

[0084] Optionally, the first IE can be a new IE type in the safe mode command, that is, an IE type specifically designed to carry the first information.

[0085] For example, the first information is used to instruct the terminal to establish a session. This first information might be descriptive information or a specified value of 1 bit length, which can be carried by the first IE added in the safe mode command.

[0086] For example, the first information is used to instruct the terminal whether to establish a session or not. For instance, the first information may include an indicator bit, the specific value of which (e.g., a first value or a second value) can be carried by the first IE added in the safe mode command. Alternatively, the first information may include first or second descriptive information, which can also be carried by the first IE added in the safe mode command.

[0087] Optionally, the first IE can be an existing IE type in the safe mode command. That is, one or more bits can be added to an existing IE in the safe mode command to carry the first information, or one or more specified bits in an existing IE can be used to carry the first information.

[0088] The position of one or more bits in the first IE can be configured according to the actual situation. For example, it can be at the end of the first IE, the beginning of the first IE, or any specified position of the first IE, etc. This embodiment does not limit this. One or more specified bits can be one or more reserved bits or one or more other bits among all bits in the existing IE. This embodiment does not limit the position occupied by each specified bit in the existing IE.

[0089] For example, the first information is used to instruct the terminal to establish a session. This first information might be descriptive information, which can be added to one or more bits in an existing first IE (Initial Context) in the safe mode command, or carried in one or more specified bits within that first IE. The specific number of these bits is related to the length of the descriptive information and is not limited here. Alternatively, the first information could be a specified value of 1 bit length, which can be added to an existing first IE in the safe mode command, or carried in a specified bit within that first IE.

[0090] For example, the first information is used to instruct the terminal to establish a session or not. For instance, the first information may include an indicator bit, which can be added to an existing first IE in the safe mode command, or the specific value of the indicator bit (such as a first value or a second value) can be carried in a specified bit within the first IE. Alternatively, the first information may include first or second descriptive information, which can be added to an existing first IE in the safe mode command, or the first or second descriptive information can be carried in one or more specified bits within the first IE.

[0091] It should be noted that, in addition to carrying the first message (i.e., the first information), the secure mode command may also carry at least one of the following: KSI (Key Service Indicator), replay terminal security capabilities, integrity algorithm, ciphering algorithm, initial NAS message request indication, etc. Specifically, the KSI can be 6G KSI or 5G KSI, etc., and is not limited here. This embodiment also does not limit which Internet Explorers (IEs) carry the above content. It should also be understood that in actual processing, the secure mode command may carry various possible contents specified by relevant protocols, and this embodiment does not limit or exhaustively list them.

[0092] In one embodiment, the first message may be carried by a registration acceptance message.

[0093] In this example, the sending of the first message from the first core network element to the terminal may include: the first core network element sending a registration acceptance message to the terminal, the registration acceptance message carrying the first message. Correspondingly, the terminal receiving the first message from the first core network element may be: the terminal receiving a registration acceptance message carrying the first message from the first core network element.

[0094] The first message can also carry only the first information, that is, the first message can be equivalent to the first information. In other words, the first information can be carried by the registered message.

[0095] Specifically, the first piece of information can be carried by the second IE in the registration and acceptance message.

[0096] Optionally, the second IE can be a newly added IE type in the registration acceptance message, that is, an IE type specifically designed to carry the first information.

[0097] For example, the first information is used to instruct the terminal to establish a session. This first information could be a descriptive message or a specified value of 1 bit length, which could be carried by a second IE added to the registration acceptance message.

[0098] For example, the first information is used to instruct the terminal to establish a session or not. For instance, the first information may include an indication bit, the specific value of which (e.g., a first value or a second value) can be carried by a second IE added to the registration acceptance message. Alternatively, the first information may include first or second description information, which can be carried by a second IE added to the registration acceptance message.

[0099] Optionally, the second IE can be an existing IE type in the registration acceptance message. That is, one or more bits can be added to an existing IE in the registration acceptance message to carry the first information, or one or more specified bits in an existing IE can be dedicated to carrying the first information.

[0100] The position of one or more bits in the second IE can be configured according to the actual situation, and this embodiment does not limit it. One or more specified bits can be one or more reserved bits or one or more other bits among all bits in the existing IE. This embodiment does not limit the position occupied by each specified bit in the existing IE.

[0101] For example, the first information is used to instruct the terminal to establish a session. This first information might be descriptive information, which can be added to one or more bits in an existing second IE within the registration acceptance message, or carried in one or more specified bits within that second IE. The specific number of these bits is related to the length of the descriptive information and is not limited here. Alternatively, the first information could be a specified value of 1 bit length, which can be added to an existing second IE within the registration acceptance message, or carried in a specified bit within that second IE.

[0102] For example, the first information is used to instruct the terminal to establish a session or not. For instance, the first information may include an indication bit, which can be added to an existing second IE in the registration acceptance message, or the specific value of the indication bit (such as a first value or a second value) can be carried in a designated bit within the second IE. For instance, the first information may include first or second description information, which can be added to an existing second IE in the registration acceptance message, or the first or second description information can be carried in one or more designated bits within the second IE.

[0103] It should be noted that, in addition to carrying the first message (i.e., the first information), the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, the registration area, where the new GUTI can be a new 6G-GUTI or a new 5GUTI, etc. This embodiment does not limit which Internet Explorers (IEs) carry the above content in the registration acceptance message. In actual processing, the registration acceptance message may also carry various possible contents specified by relevant protocols, which this embodiment does not limit or exhaustively list.

[0104] In addition, the processing before the first core network element sends the registration acceptance message to the terminal may also include: the first core network element sending a security mode command to the terminal and receiving a security mode completion (or security mode confirmation) message from the terminal. The processing before the terminal receives the registration acceptance message carrying the first message from the first core network element may include: the terminal receiving the security mode command from the first core network element and sending a security mode completion message to the first core network element. The security mode command may also carry various possible contents specified by relevant protocols. For example, the security mode command may carry at least one of the following: KSI, terminal security capabilities for replay, integrity protection algorithm, encryption algorithm, complete initial message request indication, etc. Specifically, the KSI may be a 6G KSI or a 5G KSI, etc. The possible contents carried by the security mode command are not limited or exhaustively listed here.

[0105] In one embodiment, after the terminal receives a first message from a first core network element, the method further includes: if the first message is used to instruct the terminal to establish a session, the terminal sends a second message to the first core network element, wherein the second message is used to request the establishment of the first session. After the first core network element sends the first message to the terminal, the method further includes: if the first message is used to instruct the terminal to establish a session, the first core network element receives a second message from the terminal, wherein the second message is used to request the establishment of the first session.

[0106] In one scenario, where the first information is used to instruct the terminal to establish a session, the terminal can directly determine that a session needs to be established based on the first information, or determine that a session needs to be established during the registration process.

[0107] In another scenario, when the first information is used to instruct the terminal to establish a session or not to establish a session, the terminal can determine whether to establish a session based on the specific content of the first information. For example, if the first information includes an indication bit, the terminal can determine to establish a session (or determine that a session needs to be established during the registration process) if the value of the indication bit is a first value; and determine not to establish a session (or determine that a session does not need to be established during the registration process) if the value of the indication bit is a second value.

[0108] The second message can also be called a session establishment request message.

[0109] The second message may carry at least one of the following: the identifier of the first session, the first attribute information of the first session, etc. The identifier of the first session may be generated by the terminal, and the specific generation method is not limited in this embodiment. The first attribute information of the first session may include at least one of the following: the type of the first session, the S-NSSAI (Single-Network Slice Selection Assistance Information) corresponding to the first session, the DNN (Data Network Name) corresponding to the first session, etc. In this embodiment, the specific method by which the terminal determines the first attribute information of the first session is not limited.

[0110] The type of the first session can be used to indicate the type of the first session requested by the terminal. For example, the type of the first session can include one of the following: IPv4 (Internet Protocol Version 4), IPv6 (Internet Protocol Version 6), IPv4v6 (Internet Protocol Version 4 and 6), Ethernet, and Unstructured data.

[0111] Optionally, if the first message is carried by the security mode command, the second message may be carried by one of the following: a security mode complete message or a registration complete message.

[0112] Optionally, if the first message is carried by the registration acceptance message, the second message may be carried by one of the following: a registration completion message or an uplink NAS transmission message.

[0113] In some possible embodiments, the first message carries first information, wherein the first information is used by the terminal to determine the establishment of a first session, and the first information includes relevant information about the first session. In this embodiment, the first information can be an implicit indication, through which the terminal determines that the network side needs the terminal to establish a session, and the terminal side determines the specific relevant information of the first session that needs to be established. That is, the relevant information about the first session included in the first information can be used to trigger the terminal to initiate a message to request the establishment of a first session.

[0114] Here, "the terminal establishing the first session" can refer to the network side requiring the terminal to establish the first session. The network side can at least include the first core network element on the core network side.

[0115] Furthermore, establishing the first session includes establishing the first session during the registration process; the terminal determining to establish the first session means that the terminal determines that the network side requires the terminal to establish the first session during the registration process.

[0116] The relevant information of the first session includes at least one of the following: the second attribute information of the first session, and the relevant information of the destination network element associated with the first session.

[0117] The second attribute information of the first session can refer to at least some attribute information of the first session that the network side needs to establish with the terminal. The second attribute information of the first session can include at least one of the following: the type of the first session, the S-NSSAI corresponding to the first session, the DNN corresponding to the first session, and the SSC (Session and Service Continuity) mode corresponding to the first session.

[0118] The destination network element associated with the first session can refer to the destination network element that the terminal can connect to in the first session established by the network side. The relevant information of the destination network element may include at least one of the following: the IP (Internet Protocol) address of the destination network element, the FQDN (Fully Qualified Domain Name) of the destination network element, the type of the destination network element, etc. The type of the destination network element may include control plane network elements on the network control side, such as location management network elements.

[0119] The difference between this embodiment and the previous embodiment is that the first core network element can, when it is determined that the terminal needs to establish a session (or that the terminal needs to establish a session during the registration process) and the relevant information of the first session is determined, implicitly instruct the terminal to establish the first session (or to establish the first session during the registration process) by sending a first message carrying the first information (specifically the relevant information of the first session).

[0120] In one scenario, if the first core network element determines that the terminal needs to establish a session (or determines that the terminal needs to establish a session during the registration process) based on a pre-configured policy, the first core network element may determine the first session that the terminal needs to establish based on the terminal's relevant information, and then determine the relevant information of the first session.

[0121] The specific details of the policies pre-configured for the first core network elements are the same as those in the previous example and will not be repeated here.

[0122] The relevant information about the terminal may include the terminal's capability information and / or the terminal's contract information.

[0123] For example, the terminal's subscription information includes the terminal's permission to establish a session under the first service or first business during the registration process. The first core network element can determine, based on the terminal's subscription information, that the terminal needs to establish the first session under the first service or first business (during the registration process).

[0124] For example, the terminal's capability information includes that the terminal supports establishing a session under the first service or first business during the registration process. The first core network element can determine, based on the terminal's capability information, that the terminal needs to establish the first session under the first service or first business during the registration process.

[0125] In one scenario, the first core network element may determine the first session that the terminal needs to establish, based on instruction information related to session establishment, whether the terminal needs to establish a session (or whether the terminal needs to establish a session during the registration process).

[0126] The instruction information related to session establishment may come from a second core network element (such as SMF) or other core network elements or AF. This instruction information related to session establishment may include the identifier and / or type of one or more terminals that need to establish a session (or need to establish a session during the registration process), and the identifier of the first service or first service.

[0127] The second core network element or other core network elements or AF may determine whether a session needs to be established or whether a session needs to be established during the registration process based on relevant terminal information and / or pre-configured policies, and determine which service(s) or business(s) require the terminal to establish a session. This is not limited or exhaustive. The timing of receiving or processing instructions related to session establishment are similar to those in the aforementioned embodiments and will not be repeated.

[0128] After receiving instruction information related to session establishment and a registration request message from a terminal, the first core network element may first determine whether the terminal's identifier is included in the identifiers of one or more terminals that need to establish a session (or need to establish a session during the registration process) in the instruction information related to session establishment, and / or determine whether the terminal's type is included in the types of one or more terminals that need to establish a session (or need to establish a session during the registration process) in the instruction information related to session establishment. If it is included, then based on the identifier of the first service or first service in the instruction information related to session establishment, it determines that the terminal needs to establish a first session under the first service or first service.

[0129] Furthermore, after determining that the terminal needs to establish a first session, the first core network element can determine the relevant information of the first session.

[0130] For example, the first core network element may have pre-configured relevant attribute parameters for a session under the first service or service. Then, the first core network element directly generates relevant information for the first session based on the locally configured relevant attribute parameters for the session under the first service or service. These relevant attribute parameters may include at least one of the following: the session type, S-NSSAI, DNN, SSC mode, associated destination network element, and relevant information of the destination network element.

[0131] It should be noted that this is only an illustrative example. In actual processing, other methods can be used to determine whether the terminal needs to establish a session, as well as other methods to determine the specific first session and related information that the terminal needs to establish. However, this embodiment does not limit or exhaustively list them.

[0132] In one embodiment, the first message may be carried by a safe mode command.

[0133] The first core network element sending the first message to the terminal can be as follows: after completing the authentication process, the first core network element sends a security mode command to the terminal, which carries the first message. Correspondingly, the terminal receiving the first message from the first core network element can be as follows: the terminal receives a security mode command carrying the first message from the first core network element.

[0134] The first message may only carry the first information. In this embodiment, the first message can be equivalent to the first information. In other words, the first information can be carried by the safe mode command.

[0135] Specifically, the first information can be carried by the first IE (Information Elements) in the safe mode command.

[0136] Optionally, the first IE can be a new IE type in the safe mode command, that is, an IE type specifically designed to carry the first information.

[0137] Optionally, the first IE can be an existing IE type in the safe mode command. That is, one or more bits can be added to an existing IE in the safe mode command to carry the first information, or one or more specified bits in an existing IE can be used to carry the first information.

[0138] It should be noted that, in addition to carrying the first message (i.e., the first information), the safe mode command can also carry other parameters or content. The relevant descriptions are the same as those in the foregoing embodiments and will not be repeated.

[0139] In one embodiment, the first message may be carried by a registration acceptance message.

[0140] Sending a first message from the first core network element to the terminal may include: the first core network element sending a registration acceptance message to the terminal, the registration acceptance message carrying the first message. Correspondingly, the terminal receiving the first message from the first core network element may be: the terminal receiving a registration acceptance message carrying the first message from the first core network element.

[0141] The first message can also carry only the first information, that is, the first message can be equivalent to the first information. In other words, the first information can be carried by the registered message.

[0142] Specifically, the first piece of information can be carried by the second IE in the registration and acceptance message.

[0143] Optionally, the second IE can be a newly added IE type in the registration acceptance message, that is, an IE type specifically designed to carry the first information.

[0144] Optionally, the second IE can be an existing IE type in the registration acceptance message. That is, one or more bits can be added to an existing IE in the registration acceptance message to carry the first information, or one or more specified bits in an existing IE can be dedicated to carrying the first information.

[0145] It should be noted that, in addition to carrying the first message (i.e., the first information), the registration acceptance message can also carry relevant descriptions of the content or parameters, which is the same as in the aforementioned embodiments and will not be repeated here. Furthermore, the relevant descriptions of the processing before the first core network element sends the registration acceptance message to the terminal are also the same as in the aforementioned embodiments and will not be repeated here.

[0146] In one embodiment, after the terminal receives a first message from a first core network element, the method further includes: the terminal sending a second message to the first core network element, wherein the second message is used to request the establishment of the first session, the second message carries first attribute information of the first session, and the first attribute information of the first session is determined based on relevant information of the first session. After the first core network element sends the first message to the terminal, the method further includes: the first core network element receiving a second message from the terminal, wherein the second message is used to request the establishment of the first session, the second message carries first attribute information of the first session, and the first attribute information of the first session is determined based on relevant information of the first session.

[0147] In this embodiment, as long as the terminal receives the first message carrying the first information (i.e., the relevant information of the first session), it can directly determine the establishment of a session and determine the first attribute information of the first session based on the relevant information of the first session.

[0148] The second message can also be called a session establishment request message.

[0149] The first attribute information of the first session carried in the second message can refer to all attribute information of the first session requested by the terminal. In this embodiment, in order to distinguish between the attribute information of the first session indicated by the first core network element and the attribute information of the first session requested by the terminal, the attribute information of the first session indicated by the first core network element is referred to as the second attribute information of the first session, and the attribute information of the first session requested by the terminal is referred to as the first attribute information of the first session.

[0150] Optionally, the relevant information for the first session may only include the second attribute information of the first session.

[0151] In one scenario, the second attribute information of the first session may include all the attribute information of the first session. Correspondingly, the first attribute information of the first session can be the same as the second attribute information of the first session. That is, the terminal can directly use all the attribute information of the first session that the network side needs to use as the total attribute information of the first session requested by the terminal.

[0152] In one scenario, the second attribute information of the first session may include some attribute information of the first session. Correspondingly, the first attribute information of the first session may include the second attribute information of the first session and other attribute information of the first session, which may be determined by the terminal.

[0153] For example, the second attribute information of the first session may only include the type of the first session; the process by which the terminal determines the first attribute information of the first session may include: the terminal directly adding the type of the first session to the first attribute information of the first session; and the terminal may determine other attribute information of the first session itself and add the other attribute information of the first session to the first attribute information of the first session as well. The other attribute information of the first session may include at least one of the following: S-NSSAI corresponding to the first session, DNN corresponding to the first session, etc. The terminal may determine the other attribute information of the first session based on local configuration and / or relevant policies. It should be understood that this is only an illustrative example, and all attribute information of the first session may include, but is not limited to, the parameters in the above example. There may also be other ways for the terminal to determine all possible attribute information (or attribute parameters) of the first session, which this example does not limit or exhaustively list.

[0154] Optionally, the relevant information for the first session may only include information about the destination network element associated with the first session.

[0155] The terminal can determine the first attribute information of the first session based on the relevant information of the destination network element associated with the first session. Here, there are no restrictions on the method by which the terminal determines the first attribute information of the first session or on the parameters that the first attribute information of the first session may contain.

[0156] Optionally, the relevant information of the first session may include: the second attribute information of the first session, and the relevant information of the destination network element associated with the first session.

[0157] The second attribute information of the first session may include some attribute information of the first session. Correspondingly, the first attribute information of the first session may include the second attribute information of the first session and other attribute information of the first session, which can be determined by the terminal based on the relevant information of the destination network element associated with the first session.

[0158] For example, the second attribute information of the first session may only include the DNN corresponding to the first session. The terminal's process of determining the first attribute information of the first session may include: the terminal directly adding the DNN corresponding to the first session to the first attribute information of the first session; and the terminal may determine other attribute information of the first session based on the relevant information of the destination network element associated with the first session, and add the other attribute information of the first session to the first attribute information of the first session as well. The other attribute information of the first session may include at least one of the following: the S-NSSAI corresponding to the first session, the type of the first session, etc. The terminal may determine the other attribute information of the first session based on the relevant information of the destination network element associated with the first session, combined with local configuration and / or relevant policies. It should be understood that this is only an illustrative example, and all attribute information of the first session may include, but is not limited to, the parameters in the above example. The terminal may also determine all possible attribute information (or attribute parameters) of the first session in other ways, which are not limited or exhaustive in this example.

[0159] It should be noted that, in addition to carrying the first attribute information of the first session, the second message can also carry the identifier of the first session. The identifier of the first session can be generated by the terminal, and the specific generation method is not limited in this embodiment.

[0160] Optionally, if the first message is carried by a safe mode command, the second message may be carried by at least one of the following: a safe mode completion message, a registration completion message, or an uplink NAS transmission message.

[0161] Optionally, if the first message is carried by the registration acceptance message, the second message may be carried by at least one of the following: a registration completion message, or an uplink NAS transmission message.

[0162] In some possible embodiments, the method of transmitting the second message is described.

[0163] In one embodiment, the second message is carried by a safe mode completion message. This safe mode completion message can also be called a safe mode confirmation message.

[0164] In this embodiment, the terminal sending the second message to the first core network element may include: the terminal sending a security mode completion message to the first core network element, the security mode completion message carrying the second message. Correspondingly, the first core network element receiving the second message from the terminal may be: the first core network element receiving a security mode completion message from the terminal, the security mode completion message carrying the second message.

[0165] In addition, before the terminal sends the registration completion message to the first core network element, it may include: the terminal may receive a security mode command carrying a first message. The security mode command may carry the aforementioned first message. The specific way of carrying the first message is the same as in the previous embodiment and will not be described again.

[0166] In one example, the second message can be carried by the first SM (Session Management) container. Furthermore, the second message is carried using secure mode. That is, the second message can be carried by the first SM container within the secure mode message.

[0167] Optionally, the safe mode completion message carries a first SM container, which in turn carries a second message.

[0168] In addition to carrying the first SM container, the safe mode completion message can also carry a complete registration request message. This complete registration request may include at least one of the contents carried in the registration request message, the requested slice information, or the terminal's capability information.

[0169] The content carried in the registration request message has been described in detail in the aforementioned embodiments and will not be repeated here.

[0170] The requested slice information may include one or more slice information requested by the terminal. The one or more slice information requested by the terminal may include the S-NSSAI corresponding to the first session. There are no restrictions on other slice information included in the one or more slice information requested by the terminal.

[0171] The description of the terminal's capabilities is the same as in the aforementioned embodiments and will not be repeated here. It should be noted that the security mode completion message may also carry other content specified in the relevant protocols, which will not be limited or exhaustively listed here.

[0172] Furthermore, in addition to carrying the first SM container and the complete registration request message, the security mode completion message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session. Here, at least one of the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session carried in the security mode completion message outside the first SM container can be used by the first core network element to identify the first session.

[0173] For example, a safe mode completion message can carry a first SM container (carrying a second message), a complete registration request message (such as the content carried in the registration request message, the requested slice information, and the terminal's capability information), the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0174] Optionally, the security mode completion message carries a complete registration request message, which carries a first SM container, and the first SM container carries a second message.

[0175] In addition to carrying the first SM container, the complete registration request message may also include at least one of the following: the content carried in the registration request message, the requested slice information, and the terminal's capability information.

[0176] Furthermore, in addition to carrying the first SM container and the complete registration request message, the complete registration request message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0177] For example, a safe mode completion message can carry a complete registration request message, which includes a first SM container (carrying a second message), the content carried in the registration request message, the requested slice information, the terminal's capability information, the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0178] In one example, the second message can be carried by the first SM container. Furthermore, the second message is carried by a safe mode completion message and an uplink NAS transmission message.

[0179] Optionally, the safe mode completion message carries an uplink NAS transmission message, which carries a first SM container, and the first SM container carries a second message.

[0180] In addition to carrying the first SM container, the uplink NAS transmission message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session. Here, at least one of the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session carried in the uplink NAS transmission message outside the first SM container can be used by the first core network element to identify the first session.

[0181] In addition to carrying uplink NAS transmission messages, the security mode completion message can also carry a complete registration request message. This complete registration request may include at least one of the contents carried in the registration request message, the requested slice information, or the terminal's capability information.

[0182] For example, the security mode completion message can carry a complete registration request message (such as the content carried in the registration request message, the requested slice information, and the terminal's capability information), an uplink NAS transmission message, which can carry a first SM container (carrying a second message), and the uplink NAS transmission message can also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0183] Optionally, the security mode completion message carries a complete registration request message, which in turn carries an uplink NAS transmission message, which carries a first SM container, and the first SM container carries a second message.

[0184] In addition to carrying the first SM container, the uplink NAS transmission message can also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0185] In addition to carrying uplink NAS transmission messages, the complete registration request message may also include at least one of the following: the content carried in the registration request message, the requested slice information, and the terminal's capability information.

[0186] For example, the security mode completion message can carry a complete registration request message, which includes the content carried in the registration request message, the requested slice information, the terminal's capability information, and the uplink NAS transmission message. The uplink NAS transmission message can carry a first SM container (carrying a second message), and the uplink NAS transmission message can also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0187] In one example, the second message can be carried directly by the safe mode. That is, the second message does not need to be encapsulated in an SM container, but can be carried directly by the safe mode.

[0188] Optionally, in addition to carrying the second message, the safe mode completion message may also carry a complete registration request message. This complete registration request may include at least one of the contents carried in the registration request message, requested slice information, or terminal capability information.

[0189] Furthermore, in addition to carrying the second message and the complete registration request message, the security mode completion message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session. Here, at least one of the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session carried in the security mode completion message outside the first SM container can be used by the first core network element to identify the first session.

[0190] For example, the safe mode completion message can carry a second message, a complete registration request message (such as the content carried in the registration request message, the requested slice information, and the terminal's capability information), the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0191] Optionally, the security mode completion message carries a complete registration request message, which in turn carries a second message.

[0192] In addition to carrying the second message, the complete registration request message may also carry at least one of the following: the content carried in the registration request message, the requested slice information, the terminal's capability information, etc.

[0193] Furthermore, the complete registration request message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0194] For example, a safe mode completion message can carry a complete registration request message, which includes a second message, the content carried in the registration request message, the requested slice information, the terminal's capability information, the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0195] In one example, the second message can be carried by both the safe mode completion message and the uplink NAS transmission message. That is, the second message does not need to be encapsulated in the SM container.

[0196] Optionally, the safe mode completion message carries an uplink NAS transmission message, which in turn carries a second message.

[0197] In addition to carrying a second message, the uplink NAS transmission message can also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0198] In addition to carrying uplink NAS transmission messages, the security mode completion message can also carry a complete registration request message. This complete registration request may include at least one of the contents carried in the registration request message, the requested slice information, or the terminal's capability information.

[0199] Optionally, the security mode completion message carries a complete registration request message, which in turn carries an uplink NAS transmission message, and the uplink NAS transmission message carries a second message.

[0200] In addition to carrying a second message, the uplink NAS transmission message can also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0201] In addition to carrying uplink NAS transmission messages, the complete registration request message may also include at least one of the following: the content carried in the registration request message, the requested slice information, and the terminal's capability information.

[0202] In one embodiment, the second message is carried by the registration completion message.

[0203] In this embodiment, the terminal sending the second message to the first core network element may include: the terminal sending a registration completion message to the first core network element, the registration completion message carrying the second message. Correspondingly, the first core network element receiving the second message from the terminal may involve: the first core network element receiving the registration completion message from the terminal, the registration completion message carrying the second message.

[0204] The registration completion message can be used to confirm that the new GUTI has taken effect. This new GUTI can be sent via a registration acceptance message. For example, the new GUTI can be a new 6G GUTI, a new 5G GUTI, or so on.

[0205] In addition, before the terminal sends the registration completion message to the first core network element, it may include: after receiving a security mode command carrying a first message, the terminal may send a security mode completion message to the first core network element, and then receive a registration acceptance message from the first core network element. The security mode command or registration acceptance message may carry the aforementioned first message. The specific method of carrying the first message and related explanations are the same as in the previous embodiments and will not be repeated here. Besides the first message, the content that may be carried in the security mode command and registration acceptance message can be consistent with the relevant protocol provisions and is not limited here.

[0206] Optionally, the second message can be carried by the first SM container. Furthermore, the second message can be carried by the registration completion message.

[0207] Specifically, the registration completion message carries a first SM container, which in turn carries a second message. In addition to the first SM container, the registration completion message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, or the DNN corresponding to the first session.

[0208] Optionally, the second message can be carried by the first SM container. Furthermore, the second message is carried by both a registration completion message and an uplink NAS transmission message.

[0209] Specifically, the registration completion message carries an uplink NAS transmission message, which carries a first SM container, and the first SM container carries a second message. In addition to carrying the first SM container, the uplink NAS transmission message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0210] Optionally, the second message can be carried in the registration completion message. That is, the second message is no longer encapsulated in the SM container.

[0211] Specifically, the registration completion message carries a second message. In addition to the second message, the registration completion message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0212] Optionally, the second message is carried by the registration completion message and the uplink NAS transmission message.

[0213] Specifically, the registration completion message carries an uplink NAS transmission message, which in turn carries a second message. In addition to the second message, the uplink NAS transmission message may also carry at least one of the following: the identifier of the first session, the S-NSSAI corresponding to the first session, and the DNN corresponding to the first session.

[0214] In some possible embodiments, after the first core network element receives the second message from the terminal, the method further includes: the first core network element sending a fourth message to the second core network element, wherein the fourth message is used to request the establishment of the first session; and the first core network element receiving a fifth message from the second core network element, wherein the fifth message is used to indicate acceptance of the establishment of the first session.

[0215] The second core network element can be a control plane element of the core network. For example, the second core network element can be an SMF (Session Management Function).

[0216] The fourth message can be a PDU session establishment - session management context request (Nsmf_PDU session_CreateSMContext_Request) message. The fourth message can carry the identifier of the first session, the attribute information of the first session, and a second message (which can be carried by the first SM container).

[0217] The fifth message can be a PDU session establishment - session management context response (Nsmf_PDU session_CreateSMContext_Response) message, which indicates that the second core network element accepts the establishment of the first session. This fifth message may carry at least one of the following: the identifier of the first session, the authorized QoS (Quality of Service) rules corresponding to the first session, the network address assigned to the terminal, and the S-NSSAI corresponding to the first session. The network address can refer to an IP address, etc., and is not limited here.

[0218] After the first core network element receives the fifth message from the second core network element, the method further includes: the first core network element sending a third message to the terminal, wherein the third message is used to indicate acceptance of establishing the first session. Correspondingly, after the terminal sends the second message to the first core network element, the method further includes: the terminal receiving a third message from the first core network element, wherein the third message is used to indicate acceptance of establishing the first session.

[0219] This third message can be the acceptance message for establishing a session. The third message can carry the content carried by the fifth message. For example, the third message can carry at least one of the following: the identifier of the first session, the authorized QoS rules corresponding to the first session, the network address assigned to the terminal, the S-NSSAI corresponding to the first session, etc.

[0220] The third message is carried by the second SM container; and / or, the third message is carried by one of the following: the registration acceptance message, or the downlink NAS transmission message.

[0221] In one embodiment, the second message can be carried by the secure mode; correspondingly, the third message is carried by the registration and acceptance message.

[0222] The specific carrying methods for the first and second messages are the same as in the aforementioned embodiments and will not be repeated here.

[0223] Optionally, the third message is carried by both the second SM container and the registration acceptance message. That is, the registration acceptance message carries the second SM container, which in turn carries the third message.

[0224] In addition to carrying the second SM container, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, the registration area, and the identifier of the first session.

[0225] Alternatively, the registration acceptance message may carry a downlink NAS transmission message, which carries a second SM container, and the second SM container carries the third message. In addition to carrying the downlink NAS transmission message, the registration acceptance message may also carry at least one of the terminal's new GUTI and registration regions. In addition to carrying the second SM container, the downlink NAS transmission message may also carry the identifier of the first session.

[0226] Optionally, the third message is carried by the registration acceptance message; that is, the registration acceptance message carries the third message, but this third message is not encapsulated in the SM container. In addition to carrying the third message, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, the registration region, and the identifier of the first session.

[0227] Optionally, the registration acceptance message carries a downlink NAS transmission message, which in turn carries a third message. In addition to carrying the downlink NAS transmission message, the registration acceptance message may also carry at least one of the terminal's new GUTI and registration area. Furthermore, in addition to carrying the third message, the downlink NAS transmission message may also carry an identifier of the first session.

[0228] It should be noted that the registration acceptance message may also carry other content stipulated in the relevant agreement, which will not be limited or exhaustively listed here.

[0229] In this scenario, after receiving the registration acceptance message, the terminal can also send a registration completion message to the first core network element. This registration completion message can be used to confirm that the new GUTI has taken effect. It should be noted that the registration completion message may carry content specified in relevant protocols; however, this is not limited or exhaustive.

[0230] In one embodiment, the second message may be carried by a registration completion message, or the second message may be carried by a secure mode completion message. Correspondingly, the third message is carried by a downlink NAS transmission message.

[0231] Optionally, the third message is carried by the second SM container and by a downlink NAS transmission message. The transmission of this downlink NAS transmission message is later than the registration accept message.

[0232] Specifically, the downlink NAS transmission message carries a second SM container, and the second SM container carries a third message. In addition, besides carrying the second SM container, the downlink NAS transmission message may also carry the identifier of the first session.

[0233] In one scenario, the second message is carried out in secure mode. In this case, after receiving the fifth message from the second core network element, the first core network element can send a registration acceptance message to the terminal. This registration acceptance message can carry the terminal's new GUTI and at least one of the registered regions. Then, the first core network element sends a downlink NAS transmission message to the terminal. This downlink NAS transmission message carries a second SM container, and the second SM container carries a third message. The terminal receiving the third message from the first core network element can be as follows: the terminal receives the registration acceptance message from the first core network element, sends a registration completion message to the first core network element, which can be used to confirm that the new GUTI has taken effect, and the terminal receives a downlink NAS transmission message from the first core network element. This downlink NAS transmission message carries a second SM container, and the second SM container carries the third message.

[0234] In one scenario, the second message is carried by the registration completion message. In this case, after the first core network element receives the fifth message from the second core network element, it sends a downlink NAS transmission message to the terminal. This downlink NAS transmission message carries a second SM container, and the second SM container carries a third message. The terminal receiving the third message from the first core network element can be as follows: the terminal receives a downlink NAS transmission message from the first core network element, the downlink NAS transmission message carries the second SM container, and the second SM container carries the third message.

[0235] Optionally, the third message is carried by a downlink NAS transmission message. This downlink NAS transmission message is transmitted later than the registration accept message.

[0236] Specifically, the downlink NAS transmission message carries a third message. Additionally, the downlink NAS transmission message may also carry an identifier for the first session.

[0237] In one scenario, the second message is carried out in secure mode. In this case, after receiving the fifth message from the second core network element, the first core network element can send a registration acceptance message to the terminal. This registration acceptance message may carry the terminal's new GUTI and at least one of the registered regions. Then, the first core network element sends a downlink NAS transmission message to the terminal, which carries the third message. The terminal receiving the third message from the first core network element can be as follows: the terminal receives the registration acceptance message from the first core network element, sends a registration completion message to the first core network element, which can be used to confirm that the new GUTI has taken effect, and the terminal receives a downlink NAS transmission message from the first core network element, which carries the third message.

[0238] In one scenario, the second message is carried by the registration completion message. In this case, after the first core network element receives the fifth message from the second core network element, the first core network element sends a downlink NAS transmission message to the terminal, which carries the third message. The terminal receiving the third message from the first core network element can be as follows: the terminal receives a downlink NAS transmission message from the first core network element, and the downlink NAS transmission message carries the third message.

[0239] In this embodiment, the content carried by the registration acceptance message and the registration completion message can be the same as that specified in the relevant protocol, and is not limited.

[0240] The communication method provided in this application embodiment will be described below with reference to Figure 4:

[0241] Step 401: The UE (terminal in the aforementioned embodiment) sends a registration request message to the network side 6G-AMF (first core network element in the aforementioned embodiment). The registration request message carries the UE ID (identifier of the terminal), registration type, and UE security capabilities. The UE ID can be SUCI or 6G-GUTI, and the registration type can be initial registration or mobility update registration.

[0242] Step 402: After receiving the registration request, the 6G-AMF triggers the authentication process. As shown in Figure 4, network elements such as 6G-AMF, 6G-AUSF, and UDM may participate in this authentication process. The specific handling of the authentication process is not limited here.

[0243] Step 403: The 6G-AMF sends a Security Mode Command to the UE. This command carries 6gKSI, the replayed UE security capabilities, the integrity algorithm, the ciphering algorithm, an Initial NAS message request indication, and PDU session establishment indication information (the first information carried in the first message in the aforementioned embodiment to indicate whether the terminal should establish a session). The PDU session establishment indication information includes an indication that a PDU session needs to be established during registration. This information can be carried in a separate IE (the first IE in the aforementioned embodiment) or represented by a single bit reused in an IE (such as the first IE). Alternatively, the PDU session establishment indication information includes an indication of whether a PDU session needs to be established during registration. This information can also be carried in a separate IE (such as the first IE) or represented by a single bit reused in an IE (such as the first IE). For example, a single bit can be 0 or 1 to indicate whether a PDU session needs to be established during registration.

[0244] Step 404: The UE returns a Security Mode Complete message to the 6G-AMF. The Security Mode Complete message carries a complete registration request message. In addition to the content in step 401, the complete registration request may also include the requested slice information, UE capability information, etc.

[0245] Optionally, the complete registration request message or security mode completion message also carries S-NSSAI, PDU session ID (the identifier of the first session in the aforementioned embodiments), DNN, and SM container (the first SM container in the aforementioned embodiments). The SM container is used to carry the PDU session establishment request (message) (the second message in the aforementioned embodiments). The PDU session establishment request (message) may carry the PDU session ID, the type of PDU session establishment, S-NSSAI, DNN, etc.

[0246] Optionally, the complete registration request message or security mode completion message carries a UL NAS TRANSPORT message. The UL NAS TRANSPORT message carries S-NSSAI, PDU session ID (identifier of the first session), DNN and SM container. The SM container is used to carry the PDU session establishment request (message). The PDU session establishment request (message) can carry PDU session ID, PDU session establishment type, S-NSSAI, DNN, etc.

[0247] Step 405: The 6G-AMF sends a fourth message (such as the Nsmf_PDU session_CreateSMContext_Request message) to the 6G-SMF (the second core network element in the aforementioned embodiment). The fourth message carries the PDU session ID, S-NSSAI, and SM container (which can also be the first SM container). The SM container carries the PDU session establishment request (the second message in the aforementioned embodiment).

[0248] Step 406: The 6G-SMF returns a fifth message (such as the Nsmf_PDU session_CreateSMContext_Response message) to the 6G-AMF. The message carries the SM container and PDU session ID. The SM container carries the PDU session establishment acceptance, and the PDU session establishment acceptance carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0249] Step 407: The 6G-AMF returns a registration acceptance message to the UE, which carries the new 6G-GUTI and the registration area.

[0250] Optionally, the registration acceptance message also carries the SM container (the second SM container in the aforementioned embodiments) and the PDU session ID. The SM container carries the PDU session establishment acceptance (message) (the third message in the aforementioned embodiments). The PDU session establishment acceptance (message) carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0251] Optionally, the registration acceptance message also carries a DL NAS TRANSPORT message. The DL NAS TRANSPORT message carries the SM container (second SM container) and PDU session ID. The SM container carries the PDU session establishment acceptance (message). The PDU session establishment acceptance (message) carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0252] Optionally, the 6G-AMF returns a registration acceptance message to the UE, carrying the new 6G-GUTI and the registration area. Then, the 6G-AMF sends a DL NAS TRANSPORT message to the UE, carrying the SM container (second SM container) and PDU session ID. The SM container carries the PDU session establishment acceptance message, and the PDU session establishment acceptance message carries the PDU session ID, authorized QoS rules, the UE's IP address, S-NSSAI, and other information.

[0253] Step 408: The UE returns a registration completion message to the 6G-AMF to confirm that the new 6G-GUTI has taken effect.

[0254] In an alternative scheme, steps 401 to 402 remain unchanged; the security mode command in step 403 may not carry PDU session establishment indication information; step 404 remains unchanged, that is, it can be replaced by a PDU session establishment request message initiated by the UE registration, and the specific way of carrying the PDU session establishment request message is the same as the above example, and will not be repeated; steps 405 to 408 remain unchanged.

[0255] The communication method provided in this application embodiment will be described again below with reference to Figure 5:

[0256] Steps 501 to 502 are the same as steps 401 to 402 in the previous example, and will not be repeated.

[0257] Step 503: The 6G-AMF sends a security mode command to the UE. The security mode command carries 6gKSI, the replayed UE security capabilities, integrity protection algorithm, encryption algorithm, complete initial message request indication, and PDU session attribute information (the first information in the first message in the aforementioned embodiment, specifically the relevant information of the first session).

[0258] Optionally, the PDU session attribute information includes attributes that need to be established during the registration process (the second attribute information of the first session in the aforementioned embodiments), including one of the following: S-NSSAI, DNN, SSC mode, PDU type (the type of the first session), etc. Optionally, the PDU session attribute information may also include the address or type of the destination network element (related information of the destination network element associated with the first session in the aforementioned embodiments), indicating the address or type of the destination network element that the established PDU session can connect to. Optionally, the PDU session attribute information includes attributes that need to be established during the registration process, and the address or type of the destination network element.

[0259] Step 504 is the same as step 404 in the previous example. It should be noted that the PDU session attribute information (the first attribute information of the first session in the previous embodiment) contained in the PDU session establishment request message in step 504 can be determined based on the PDU session attribute information (the relevant information of the first session in the previous embodiment) in step 503. The specific implementation method is the same as in the previous embodiment and will not be described again.

[0260] Steps 505 to 508 are the same as steps 405 to 408 in the previous example, and will not be repeated.

[0261] The communication method provided in this application embodiment will be further illustrated below with reference to Figure 6:

[0262] Steps 601 to 602 are the same as steps 401 to 402 in the previous example, and will not be repeated.

[0263] Step 603: The 6G-AMF sends a security mode command to the UE. The security mode command carries the 6gKSI, the UE security capabilities for replay, the integrity protection algorithm, the encryption algorithm, and the complete initial message request indication.

[0264] Step 604: The UE (terminal) returns a Security Mode Complete message to the 6G-AMF (first core network element). The message carries a complete registration request message. In addition to the content in step 601, the complete registration request may also include the requested slice information, UE capability information, etc.

[0265] Step 605: The 6G-AMF returns a registration acceptance message to the UE, which carries the new 6G-GUTI and the registration area.

[0266] The registration acceptance message carries PDU session establishment indication information (the first information carried in the first message in the aforementioned embodiment to indicate whether the terminal has established a session) or PDU session attribute information (the first information in the first message in the aforementioned embodiment, specifically the relevant information of the first session). The relevant descriptions regarding the PDU session establishment indication are the same as those regarding the PDU session establishment indication information in step 403 of the aforementioned example, and the relevant descriptions regarding the PDU session attribute information are the same as those regarding the PDU session attribute information in step 503 of the aforementioned example, and will not be repeated here.

[0267] Step 606: The UE returns a registration completion message to the 6G-AMF to confirm that the new 6G-GUTI has taken effect.

[0268] The registration process also includes S-NSSAI, PDU session ID, DNN, and SM container (the first SM container in the aforementioned embodiments). The SM container is used to carry the PDU session establishment request message (the second message in the aforementioned embodiments). The PDU session establishment request message may carry the PDU session ID, the type of PDU session, S-NSSAI, DNN, etc.

[0269] Alternatively, the registration completion message may carry a UL NAS TRANSPORT message, which may include S-NSSAI, PDU session ID, DNN, and SM container (the first SM container in the aforementioned embodiments). The SM container may carry a PDU session establishment request message (the second message in the aforementioned embodiments), which may include the PDU session ID, the type of PDU session, S-NSSAI, DNN, etc.

[0270] Step 607: The 6G-AMF sends a fourth message (such as the Nsmf_PDU session_Create SMContext_Request message) to the 6G-SMF (second core network element), carrying the PDU session ID, S-NSSAI, and the SM container carrying the PDU session establishment request message.

[0271] Step 608: The 6G-SMF returns the fifth message (Nsmf_PDU session_CreateSMContext_Response message) to the 6G-AMF, carrying the SM container and PDU session ID. The SM container carries the PDU session establishment acceptance (message), and the PDU session establishment acceptance carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0272] Step 609: The 6G-AMF sends a DL NAS TRANSPORT message (downlink NAS transmission message) to the UE, carrying the SM container (second SM container) and PDU session ID; the SM container carries the PDU session establishment acceptance (message) (the third message in the aforementioned embodiment), and the PDU session establishment acceptance (message) carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0273] In some possible implementations, the first message is used to request the terminal to establish a second session. This implementation differs from the previous implementations in that, in this implementation, the first core network element can directly notify the terminal that the current network side needs to initiate or accept the establishment of a second session by sending a first message requesting the terminal to establish a second session. In other words, the initiation of the second session is initiated by the core network side. Specifically, in this implementation, the function of the first message is to request the terminal to establish a second session. After receiving the first message, the terminal does not need to initiate a session establishment request again, but directly performs the process of establishing a second session based on the first message.

[0274] The difference between this embodiment and the previous embodiment is that, when the first core network element determines that the terminal needs to establish a session (or determines that the terminal needs to establish a session during the registration process), it first initiates a second session establishment request to the second core network element. After receiving a message from the second core network element accepting the establishment of the second session, it then sends a first message to the terminal requesting the terminal to establish the second session. At this time, the network side has already allocated at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address allocated to the terminal, and the attribute information of the second session, and sends it to the terminal through the first message. The terminal does not need to send a request to establish the session again. The terminal can directly perform session establishment processing based on the content of the received first message.

[0275] Before the first core network element sends the first message to the terminal, the method further includes: the first core network element sending a fourth message to the second core network element, wherein the fourth message is used to request the establishment of the second session; the first core network element receiving a fifth message from the second core network element, wherein the fifth message is used to indicate acceptance of the establishment of the second session.

[0276] The fourth message carries the first identifier of the second session allocated by the first core network element.

[0277] The first core network element may allocate the first identifier of the second session in one of the following ways: the first core network element uses a default identifier as the first identifier of the second session; or the first core network element generates the first identifier of the second session using pre-configured rules. The default identifier can be all zeros or other values; this is not limited here. The pre-configured rules can be configured according to actual conditions; this is not limited here.

[0278] In addition to carrying the first identifier of the second session, the fourth message may also carry at least one of the following: the S-NSSAI corresponding to the second session, or the terminal's identification information. The terminal's identification information may include any one of the terminal's GUTI, SUCI, SUPI, temporary identifier, or permanent identifier.

[0279] In addition, the fourth message can also carry a session establishment request. For example, the session establishment request can be carried in the fourth message using an SM container.

[0280] The fourth message can be a PDU session establishment - session management context request (Nsmf_PDU session_CreateSMContext_Request) message.

[0281] The first core network element determines whether the terminal needs to establish a second session, or determines the method by which the terminal needs to establish a second session during the registration process, and can configure it according to the actual situation.

[0282] For example, the first core network element can determine whether a terminal needs to establish a session based on a pre-configured policy. If it is determined that the terminal needs to establish a session, it may not be certain which service or business the terminal will establish as the second session. However, the first core network element can pre-generate a first identifier for this second session, enabling the second core network element to identify the second session corresponding to the terminal currently being requested by the first core network element. The specific processing method by which the first core network element determines whether a terminal needs to establish a session based on a pre-configured policy is the same as in the aforementioned embodiments and will not be repeated.

[0283] For another example, the first core network element can combine relevant terminal information and pre-configured policies to determine whether the terminal needs to establish a session. If it is determined that the terminal needs to establish a session, it may not be clear which specific service or business the terminal is establishing. However, the first core network element can pre-generate a first identifier for this second session, enabling the second core network element to identify the second session corresponding to the terminal currently being requested by the first core network element. The specific processing method for the first core network element to determine whether the terminal needs to establish a session by combining relevant terminal information and pre-configured policies is the same as in the aforementioned embodiments and will not be repeated.

[0284] It should be noted that this is merely an illustrative example, and it does not limit or exhaust all possible ways in which the first core network element determines that the terminal needs to establish a second session, or determines that the terminal needs to establish a second session during the registration process.

[0285] The fifth message carries at least one of the following: a first identifier of the second session, the Quality of Service (QoS) rules used by the terminal to establish the second session, a network address assigned to the terminal, and attribute information of the second session.

[0286] The network address can be an IP address.

[0287] The attribute information of the second session may include at least one of the following: the S-NSSAI corresponding to the second session, the DNN corresponding to the second session, the SSC mode corresponding to the second session, the type of the second session, etc. The type of the second session can be used to indicate the type of second session requested or instructed by the network side to be established by the terminal. The relevant descriptions of the several possible cases included in the type of the second session are similar to those of the first session type in the aforementioned embodiments, and will not be repeated here. Furthermore, this is only an illustrative example; in actual processing, the attribute information of the second session may be the same as the attribute information or parameters of the session specified in the relevant protocol, and is not limited or exhaustively listed here.

[0288] The second core network element can be configured in a way that includes at least one of the following: allocating the QoS rules used by the terminal to establish the second session, the network address allocated to the terminal, and the attribute information of the second session.

[0289] For example, the second core network element may determine, based on relevant terminal information (such as terminal capability information and / or subscription information), whether the terminal allows or supports a second service for which a session is requested to be established by the network side. Based on the second service, it may determine at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address allocated to the terminal, and the attribute information of the second session.

[0290] For example, a second core network element may determine, based on relevant terminal information (such as terminal capability information and / or subscription information), whether the terminal allows or supports a second service for which a session is requested by the network side. Based on the session configuration parameters corresponding to the second service, it may generate at least one of the following: QoS rules used by the terminal to establish the second session, a network address allocated to the terminal, and attribute information of the second session. The session configuration parameters corresponding to the second service may include at least one of the following: attribute information of the session corresponding to the second service, configuration related to generating QoS rules, configuration related to allocating a network address, etc.

[0291] The above is merely an exemplary description of at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address allocated to the terminal, and the attribute information of the second session. In actual processing, there may be other processing methods, which are not limited or exhaustive in this embodiment.

[0292] After receiving the fifth message from the second core network element, the first core network element sends a first message to the terminal requesting the terminal to establish a second session.

[0293] The first message can carry the same content as the fifth message. This first message can be a session establishment request.

[0294] Specifically, the first message carries a first identifier of the second session. The first message also carries at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address assigned to the terminal, and the attribute information of the second session.

[0295] In some possible embodiments, before the first core network element sends the fourth message to the second core network element, the process may further include: the first core network element receiving a registration request message from the terminal. Before the terminal receives the first message from the first core network element, the process may include: the terminal sending a registration request message to the first core network element.

[0296] The registration request message may carry at least one of the following: the terminal's identifier, the registration type, and the terminal's capability information. The descriptions of the terminal's identifier, registration type, and capability information are the same as in the previous embodiments and will not be repeated.

[0297] In one embodiment, the registration request message is an initial registration request message, or the registration type carried in the registration request message is initial registration.

[0298] After receiving a registration request message from the terminal, the first core network element can also trigger an authentication process. This authentication process can be a one-way authentication process or a two-way authentication process performed between the core network side and the terminal. The core network side can refer to any network element on the core network side that participates in the authentication process, such as the first core network element on the core network side, authentication network elements (such as AUSF (Authentication Server Function)), UDM (Unified Data Management), etc., at least one of them. Here, we do not limit or exhaustively list any network elements on the core network side that participate in the authentication process, nor do we limit the processing of this authentication process.

[0299] The first core network element may perform the aforementioned process of sending the fourth message to the second core network element and receiving the fifth message from the second core network element during the authentication process and the terminal registration process, which will not be repeated here.

[0300] After receiving the fifth message from the second core network element, the first core network element sends a first message to the terminal requesting the terminal to establish a second session.

[0301] In one example, the first message can be carried by the registration accept message.

[0302] Sending a first message from the first core network element to the terminal may include: the first core network element sending a registration acceptance message to the terminal, which carries the first message. Correspondingly, the terminal receiving the first message from the first core network element may involve the terminal receiving a registration acceptance message carrying the first message from the first core network element. Before sending the registration acceptance message, the first core network element may also send a security mode command to the terminal and receive a security mode completion message from the terminal; similarly, before receiving the registration acceptance message, the terminal may receive a security mode command from the first core network element and send a security mode completion message to the first core network element. The content carried by the security mode command and the security mode completion message may be the same as specified in the protocol and will not be elaborated further.

[0303] Optionally, the first message is carried by a third SM container. Specifically, the registration acceptance message carries the third SM container, and the third SM container carries the first message.

[0304] In addition to carrying a third SM container, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, or the registration area.

[0305] Optionally, the first message may be carried directly by the registration acceptance message. In addition to carrying the first message, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, or the registration region.

[0306] In one example, the first message may be carried by a registration acceptance message and a downlink NAS transmission message.

[0307] Optionally, the first message is carried by the third SM container. Specifically, the registration acceptance message carries a downlink NAS transmission message, the downlink NAS transmission message carries the third SM container, and the third SM container carries the first message.

[0308] In addition to downlink NAS transmission messages, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, and the registration area. The downlink NAS transmission message may also carry the first identifier of the second session, in addition to the third SM container.

[0309] Optionally, the registration acceptance message carries a downlink NAS transmission message, and the downlink NAS transmission message carries a first message.

[0310] In addition to carrying downlink NAS transmission messages, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, and the registration area. Besides carrying the first message, the downlink NAS transmission message may also carry the first identifier of the second session.

[0311] Optionally, the second IE can be an existing IE type in the registration acceptance message. That is, one or more bits can be added to an existing IE in the registration acceptance message to carry the first information, or one or more specified bits in an existing IE can be dedicated to carrying the first information.

[0312] It should be noted that, in addition to carrying the first message (i.e., the first information), the registration acceptance message can also carry relevant descriptions of the content or parameters, which is the same as in the aforementioned embodiments and will not be repeated here. Furthermore, the relevant descriptions of the processing before the first core network element sends the registration acceptance message to the terminal are also the same as in the aforementioned embodiments and will not be repeated here.

[0313] In some possible examples, the first message can also be carried by a safe mode command. For example, a safe mode command can directly carry the first message; or a safe mode command can carry a third SM container, which carries the first message.

[0314] In one embodiment, the registration request message may be a mobility update management registration request message, or the registration type carried by the registration request message may be mobility update management.

[0315] After receiving the registration request message from the terminal, the first core network element performs the aforementioned processes of sending the fourth message to the second core network element and receiving the fifth message from the second core network element. After receiving the fifth message from the second core network element, the first core network element sends a first message to the terminal requesting the terminal to establish a second session.

[0316] The first message can be carried by the registration accept message. Optionally, the first message can be carried by a third SM container, meaning the registration accept message can carry the third SM container, and the third SM container carries the first message. Optionally, the first message can be carried directly by the registration accept message.

[0317] In some possible embodiments, before the first core network element sends the fourth message to the second core network element, the process may further include: the first core network element receiving a service request message from the terminal. Before the terminal receives the first message from the first core network element, the process may include: the terminal sending a service request message to the first core network element.

[0318] After receiving the service request message from the terminal, the first core network element performs the aforementioned processing of sending the fourth message to the second core network element and receiving the fifth message from the second core network element. After receiving the fifth message from the second core network element, the first core network element sends a first message to the terminal requesting the terminal to establish a second session.

[0319] The first message can be carried by the business acceptance message. Optionally, the first message can be carried by a third SM container, meaning the business acceptance message can carry the third SM container, and the third SM container carries the first message. Optionally, the first message can be carried directly by the business acceptance message.

[0320] In some possible embodiments, after the terminal receives the first message from the first core network element, the method further includes: the terminal sending a second message to the first core network element, wherein the second message is used to indicate the completion of establishing the second session, and the second message carries a second identifier of the second session, which is generated by the terminal. After the first core network element sends the first message to the terminal, the method further includes: the first core network element receiving a second message from the terminal, wherein the second message is used to indicate the completion of establishing the second session, and the second message carries a second identifier of the second session, which is generated by the terminal. The second message may carry one of the following: a security mode completion message, a registration completion message, a service completion message, or an uplink non-access stratum (NAS) transmission message.

[0321] In this embodiment, the first message received by the terminal is directly used to request the terminal to establish a second session. After receiving the first message, the terminal can start establishing the second session based on at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address allocated to the terminal, and the attribute information of the second session carried in the first message. When it is determined that the establishment of the second session is completed, the terminal sends a second message.

[0322] This second message can also be called a session completion message or a session establishment completion message.

[0323] The second message may carry a second identifier for the second session. This second identifier is generated by the terminal and may differ from the first identifier of the second session. This embodiment does not limit the specific method by which the terminal generates the second identifier. It should be understood that the second message may also carry other parameters besides the second identifier of the second session; these are not limited here.

[0324] In one example, the second message is carried by the registration complete message. In this example, the first message could be carried by the safe mode command or the registration accept message.

[0325] The terminal sending the second message to the first core network element may include: the terminal sending a registration completion message to the first core network element, the registration completion message carrying the second message. Correspondingly, the first core network element receiving the second message from the terminal may involve: the first core network element receiving a registration completion message from the terminal, the registration completion message carrying the second message.

[0326] Optionally, the registration completion message may carry a second identifier and a second message for the second session.

[0327] Optionally, the second message is carried by the registration completion message and the uplink NAS transmission message. For example, the registration completion message carries the uplink NAS transmission message, and the uplink NAS transmission message carries the second message. Alternatively, the registration completion message carries the second identifier of the second session and the uplink NAS transmission message, and the uplink NAS transmission message carries the second message.

[0328] It should be noted that the registration completion message may also carry other parameters or content stipulated in the relevant agreement, which will not be limited or exhaustively listed here.

[0329] In one example, the second message is carried by an uplink NAS transmission message. In this example, the first message can be carried by a service acceptance message.

[0330] In one example, the second message is carried by a safe mode message. In this example, the first message can be carried by a safe mode command.

[0331] The terminal sending the second message to the first core network element may include: the terminal sending a security mode completion message to the first core network element, the security mode completion message carrying the second message. Correspondingly, the first core network element receiving the second message from the terminal may be: the first core network element receiving a security mode completion message from the terminal, the security mode completion message carrying the second message.

[0332] In this case, the safe mode completion message may carry a second identifier and a second message for the second session.

[0333] It should be noted that, since the second message sent by the terminal carries the second identifier of the updated second session, the first core network element can also perform the following processing after receiving the second message: the first core network element sends the second identifier of the second session to the second core network element and receives a response message from the second core network element. Specifically, the first core network element can send the second identifier of the second session to the second core network element via an Nsmf_PDU session_UpdateSMContext_Request message; the response from the second core network element can be an Nsmf_PDU session_UpdateSM Context_Response message.

[0334] The communication method provided in this application embodiment will be described below with reference to Figure 7:

[0335] Steps 701 to 704 are the same as steps 601 to 604 in the previous example, and will not be repeated.

[0336] In step 705, the 6G-AMF (i.e., the first core network element) sends a fourth message (such as the NSM f_PDU session_CreateSMContext_Request message) to the 6G-SMF (the second core network element). This message carries the PDU session ID (the first identifier of the second session in the aforementioned embodiment), S-NSSAI, UE identification information, and the SM container. The SM container carries the PDU session establishment request message. The PDU session ID can be set to all zeros, or the 6G-AMF can assign a PDU session ID to the PDU session.

[0337] In step 706, the 6G-SMF returns a fifth message (Nsmf_PDU session_CreateSMContext_Response message) to the 6G-AMF, carrying the SM container and PDU session ID (from step 705). The SM container carries the PDU session establishment acceptance message, which carries the PDU session ID (i.e., the first identifier of the second session), the authorized QoS rules (i.e., the QoS rules used by the terminal to establish the second session), the UE's IP address, S-NSSAI, and other information.

[0338] In step 707, the 6G-AMF returns a registration acceptance message to the UE, carrying the new 6G-GUTI and the registration area.

[0339] The registration acceptance message carries the SM container (the third SM container in the aforementioned embodiment) and the PDU session ID (i.e., the first identifier of the second session); wherein, the SM container carries the PDU session establishment request message (the first message in the aforementioned embodiment), and the PDU session establishment request message carries the PDU session ID (the value in step 705), the requested QoS rules (i.e., the quality of service QoS rules used by the terminal to establish the second session), the UE's IP address, S-NSSAI and other information.

[0340] Alternatively, the registration acceptance message may include a DL NAS TRANSPORT message. The DL NAS TRANSPORT message carries the SM container (third SM container) and the PDU session ID (the value in step 705). The SM container carries a PDU session establishment request message (the first message in the aforementioned embodiment). The PDU session establishment request message carries the PDU session ID (the value in step 705), the requested QoS rules (i.e., the QoS rules used by the terminal to establish the second session), the UE's IP address, S-NSSAI, and other information.

[0341] In step 708, the UE returns a registration completion message to the 6G-AMF to confirm that the new 6G-GUTI has taken effect.

[0342] The registration completion message carries the PDU session ID (the second identifier of the first session in the aforementioned embodiment) (instead of the PDU session ID in step 705) and the PDU session completion message (the second message in the aforementioned embodiment).

[0343] Alternatively, the registration completion message may carry a UL NAS TRANSPORT message, which in turn carries a PDU session completion message (the second message in the aforementioned embodiments), and the PDU session completion message carries a PDU session ID (the second identifier of the first session).

[0344] After step 708 is completed, it may also include: the 6G-AMF may send an Nsmf_PDUsession_UpdateSMContext_Request message to the 6G-SMF, which carries the PDU session ID and is used to update the PDU session ID; the 6G-SMF returns a response message to the 6G-AMF.

[0345] The communication method provided in this application embodiment will be further illustrated below with reference to Figure 8:

[0346] Step 801: The UE (terminal in the aforementioned embodiment) sends a registration request message or a service request message to the network side 6G-AMF (the first core network element in the aforementioned embodiment). The registration request message is a mobility update registration request message.

[0347] Steps 802 to 803 are the same as steps 705 to 706 in the previous example, and will not be repeated.

[0348] Step 804: The 6G-AMF returns a registration acceptance message or a service acceptance message to the UE; if it is a registration acceptance message, it can carry a new 6G-GUTI and the registration area.

[0349] The registration acceptance message or service acceptance message carries an SM container (the third SM container in the aforementioned embodiments) and a PDU session ID (i.e., the first identifier of the second session); wherein, the SM container carries a PDU session establishment request message (the first message in the aforementioned embodiments), and the PDU session establishment request message carries the PDU session ID, the requested QoS rules (i.e., the quality of service QoS rules used by the terminal to establish the second session), the UE's IP address, S-NSSAI and other information.

[0350] Alternatively, the registration acceptance message or service acceptance message may carry a DL NAS TRANSPORT message. The DL NAS TRANSPORT message carries an SM container (third SM container) and a PDU session ID. The SM container carries a PDU session establishment request message (the first message in the aforementioned embodiment). The PDU session establishment request message carries the PDU session ID (i.e., the first identifier of the second session), the requested QoS rules (i.e., the quality of service QoS rules used by the terminal to establish the second session), the UE's IP address, S-NSSAI, and other information.

[0351] Step 805: The UE sends a registration completion message or an uplink NAS transmission message to the 6G-AMF.

[0352] Optionally, the registration completion message or uplink NAS transmission message carries a PDU session ID (the second identifier of the first session in the aforementioned embodiments) (instead of the PDU session ID in step 705) and a PDU session establishment completion message (the second message in the aforementioned embodiments). Optionally, the registration completion message or uplink NAS transmission message carries a UL NAS TRANSPORT message, the UL NAS TRANSPORT message carries a PDU session completion message (the second message in the aforementioned embodiments), and the PDU session completion message carries the PDU session ID (the second identifier of the first session).

[0353] If step 804 is a service acceptance message, step 805 can carry a PDU session establishment completion message via a UL NAS TRANSPORT message. If step 804 is a registration acceptance message, step 805 can carry a PDU session establishment completion message via a registration completion message.

[0354] By adopting the above scheme, the terminal can determine whether to establish a session based on the first message from the network side. This increases the ways in which the network side can trigger the terminal to establish a session, making the scenarios for terminal session establishment more diverse and flexible. Furthermore, the network side can send the first message through any of the following methods: a secure mode command, a registration acceptance message, etc., allowing the terminal to establish a session during the registration process. This avoids the problems of longer session establishment latency, more signaling, and wasted resources that occur in related technologies where the terminal establishes a session after registration is complete.

[0355] Figure 9 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0356] S910, The terminal sends a sixth message to the first core network element, wherein the sixth message is used to request the establishment of a third session, and the sixth message is carried by the initial NAS message.

[0357] Figure 10 is a schematic flowchart of a communication method according to an embodiment of this application. The method includes at least a portion of the following.

[0358] S1010, the first core network element receives a sixth message from the terminal, wherein the sixth message is used to request the establishment of a third session, and the sixth message is carried by the initial NAS message.

[0359] In this embodiment of the application, the first core network element can be any control plane network element on the core network side, such as AMF, without limiting or exhaustively listing them here.

[0360] In some possible implementations, the sixth message may also be referred to as a session establishment request message.

[0361] The sixth message may carry at least one of the following: the identifier of the third session, the attribute information of the third session, etc. The identifier of the third session may be generated by the terminal, and the specific generation method is not limited in this embodiment. The attribute information of the third session may include at least one of the following: the type of the third session, the S-NSSAI corresponding to the third session, the DNN corresponding to the third session, etc. The description of the session's attribute information is similar to the description of the first attribute information of the first session in the aforementioned embodiment, and will not be repeated here. The specific method by which the terminal determines the attribute information of the third session is not limited in this embodiment.

[0362] The initial NAS message includes one of the following: a registration request message or a service request message.

[0363] In one embodiment, the initial NAS message includes a registration request message. The registration request message is a mobility update management registration request message; or the registration type carried by the registration request message is mobility update management.

[0364] In other words, the registration request message can specifically be a mobility management registration request message.

[0365] In one example, the sixth message is carried by the fourth SM container in the initial NAS message.

[0366] Optionally, the mobility management registration request message carries a fourth SM container, which carries a sixth message.

[0367] In addition to carrying the fourth SM container, the mobility management registration request message may also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session.

[0368] Optionally, the mobility management registration request message carries an uplink NAS transmission message, which carries a fourth SM container, and the fourth SM container carries a sixth message.

[0369] In addition to carrying the fourth SM container, the uplink NAS transmission message may also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session. Here, at least one of the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session carried in the uplink NAS transmission message can be used by the first core network element to identify the third session.

[0370] In one example, the sixth message is carried directly by the initial NAS message.

[0371] Optionally, the mobility management registration request message may include a sixth message.

[0372] In addition to carrying a sixth message, the mobility management registration request message may also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session.

[0373] Optionally, the mobility management registration request message carries an uplink NAS transmission message, which carries a sixth message.

[0374] In addition to carrying the sixth message, the uplink NAS transmission message can also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session.

[0375] In addition, mobility management registration requests may also carry various possible parameters specified in the relevant agreements, which will not be limited or exhaustively listed here.

[0376] In one embodiment, the initial NAS message includes a service request message.

[0377] In one example, the sixth message is carried by the fourth SM container in the initial NAS message.

[0378] Optionally, the service request message carries a fourth SM container, which carries a sixth message.

[0379] In addition to carrying the fourth SM container, the business request message can also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session.

[0380] Optionally, the service request message carries an uplink NAS transmission message, which carries a fourth SM container, and the fourth SM container carries a sixth message.

[0381] In addition to carrying the fourth SM container, the service request message may also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session. Here, at least one of the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session carried in the service request message can be used by the first core network element to identify the third session.

[0382] In one example, the sixth message is carried directly by the initial NAS message.

[0383] Optionally, the business request message may carry a sixth message.

[0384] In addition to carrying a sixth message, a business request message may also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, or the DNN corresponding to the third session.

[0385] Optionally, the service request message carries an uplink NAS transmission message, which in turn carries a sixth message.

[0386] In addition to carrying the sixth message, the uplink NAS transmission message can also carry at least one of the following: the identifier of the third session, the S-NSSAI corresponding to the third session, and the DNN corresponding to the third session.

[0387] In addition, business request messages may also carry various possible parameters specified in the relevant protocols, which will not be limited or exhaustively listed here.

[0388] In some possible implementations, after the first core network element receives the sixth message from the terminal, the method further includes: the first core network element sending an eighth message to the second core network element, wherein the eighth message is used to request the establishment of the third session; and the first core network element receiving a ninth message from the second core network element, wherein the ninth message is used to indicate acceptance of the establishment of the third session.

[0389] The second core network element can be a control plane element of the core network. For example, the second core network element can be an SMF.

[0390] The eighth message can be a PDU session establishment - session management context request (Nsmf_PDU session_CreateSMContext_Request) message. The eighth message can carry the content contained in the sixth message, which will not be repeated here.

[0391] The ninth message can be a PDU session establishment - session management context response (Nsmf_PDU session_CreateSMContext_Response) message, which can be used to indicate that the second core network element accepts the establishment of a third session. This ninth message can carry at least one of the following: the identifier of the third session, the authorized QoS rules corresponding to the third session, the network address assigned to the terminal, and the S-NSSAI corresponding to the third session.

[0392] After the first core network element receives the ninth message from the second core network element, the method further includes: the first core network element sending a seventh message to the terminal, wherein the seventh message is used to indicate acceptance of establishing the third session. Correspondingly, after the terminal sends the sixth message to the first core network element, the method further includes: the terminal receiving a seventh message from the first core network element, wherein the seventh message is used to indicate acceptance of establishing the third session.

[0393] The seventh message can be used to establish the acceptance message for the session. The seventh message can carry the content carried by the ninth message, which will not be repeated here.

[0394] The seventh message is carried by the fifth SM container. And / or, the seventh message is carried by one of the following: a registration acceptance message, a service acceptance message.

[0395] In one embodiment, the sixth message may be carried by the mobility update management registration request message; correspondingly, the seventh message may be carried by the registration acceptance message.

[0396] Optionally, the seventh message is carried by the fifth SM container and also by the registration accept message. That is, the registration accept message carries the fifth SM container, which in turn carries the seventh message.

[0397] In addition to carrying the fifth SM container, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, the registration area, or the identifier of the third session.

[0398] Alternatively, the registration acceptance message may carry a downlink NAS transmission message, which carries a fifth SM container, and the fifth SM container carries the seventh message. In addition to carrying the downlink NAS transmission message, the registration acceptance message may also carry at least one of the terminal's new GUTI and registration area. In addition to carrying the fifth SM container, the downlink NAS transmission message may also carry the identifier of the third session.

[0399] Optionally, the seventh message is carried by the registration acceptance message; that is, the registration acceptance message carries the seventh message, but this seventh message is not encapsulated in the SM container. In addition to carrying the seventh message, the registration acceptance message may also carry at least one of the following: the terminal's new GUTI, the registration region, and the identifier of the first session.

[0400] Optionally, the registration acceptance message carries a downlink NAS transmission message, which in turn carries a seventh message. In addition to carrying the downlink NAS transmission message, the registration acceptance message may also carry at least one of the terminal's new GUTI and registration area. Furthermore, in addition to carrying the seventh message, the downlink NAS transmission message may also carry an identifier for the third session.

[0401] It should be noted that the registration acceptance message may also carry other content stipulated in the relevant agreement, which will not be limited or exhaustively listed here.

[0402] In this scenario, after the terminal receives the registration acceptance message, if the registration acceptance message includes the terminal's new GUTI, the terminal can also send a registration completion message to the first core network element. This registration completion message can be used to confirm that the new GUTI has taken effect. It should be noted that the registration completion message may carry content specified in relevant protocols; however, this is not limited or exhaustive.

[0403] In one embodiment, the sixth message may be carried by a service request message. Correspondingly, the seventh message may be carried by a service acceptance message.

[0404] Optionally, the seventh message is carried by the fifth SM container and also by the service acceptance message. That is, the service acceptance message carries the fifth SM container, which in turn carries the seventh message.

[0405] In addition to carrying the fifth SM container, the service acceptance message can also carry the identifier of the third session.

[0406] Alternatively, the service acceptance message carries a downlink NAS transmission message, which carries a fifth SM container, and the fifth SM container carries the seventh message. In addition to carrying the fifth SM container, the downlink NAS transmission message may also carry an identifier of the third session.

[0407] Optionally, the seventh message is carried by the service acceptance message; that is, the service acceptance message carries the seventh message, but this seventh message is not encapsulated in the SM container. In addition to carrying the seventh message, the service acceptance message may also carry the identifier of the third session.

[0408] Optionally, the service acceptance message carries a downlink NAS transmission message, which carries a seventh message. In addition to carrying the seventh message, the downlink NAS transmission message may also carry an identifier for the third session.

[0409] It should be noted that the business acceptance message may also carry other content stipulated in the relevant agreement, which will not be limited or exhaustively listed here.

[0410] The communication method provided in this application embodiment will be described again below with reference to Figure 11:

[0411] Step 1101: The UE initiates a mobility update management registration request message or a service request message to the 6G-AMF (first core network element). The message also carries S-NSSAI, PDU session ID, DNN, and SM container (the fourth SM container in the aforementioned embodiments). The SM container carries a PDU session establishment request message (the sixth message in the aforementioned embodiments). The PDU session establishment request message may carry the PDU session ID (identifier of the third session), the type of PDU session establishment, S-NSSAI, DNN, etc. Alternatively, the message carries a UL NAS TRANSPORT message. The UL NAS TRANSPORT message carries S-NSSAI, PDU session ID, DNN, and SM container. The SM container carries the PDU session establishment request message, which carries the PDU session ID, the type of PDU session, S-NSSAI, DNN, etc.

[0412] Step 1102: The 6G-AMF sends the eighth message to the 6G-SMF (second core network element), such as the Nsmf_PDU session_CreateSMContext_Request message. The message carries the PDU session ID, S-NSSAI, and SM container. The SM container carries the PDU session establishment request message.

[0413] Step 1103: The 6G-SMF returns a ninth message to the 6G-AMF, such as the Nsmf_PDUsession_CreateSMContext_Response message, which carries the SM container and PDU session ID. The SM container carries the PDU session establishment acceptance message, which carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0414] Step 1104: The 6G-AMF sends a registration acceptance message or a service acceptance message to the UE.

[0415] The registration acceptance message or service acceptance message also carries the 6G-GUTI and the registration area. The registration acceptance message or service acceptance message carries the SM container (fifth container) and PDU session ID. The SM container carries the PDU session establishment acceptance message (seventh message). The PDU session establishment acceptance message carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI and other information.

[0416] Alternatively, the registration acceptance message or service acceptance message may carry a DL NAS TRANSPORT message. The DL NAS TRANSPORT message carries the SM container and PDU session ID. The SM container carries a PDU session establishment acceptance message, which carries the PDU session ID, authorized QoS rules, UE IP address, S-NSSAI, and other information.

[0417] Optionally, in step 1105, if a registration acceptance message was received and a new 6G-GUTI was assigned in step 1104, the UE needs to return a registration completion message to the 6G-AMF.

[0418] By adopting the above scheme, the terminal can request to establish a session through the initial NAS message. This allows the terminal to establish a session earlier, avoiding problems such as session latency, excessive signaling, and resource waste.

[0419] Figure 12 is a schematic diagram of the composition structure of a terminal according to an embodiment of this application, including:

[0420] The first communication unit 1201 is used to receive a first message from a first core network element, wherein the first message is used by the terminal to determine whether to establish a session.

[0421] The first information is used by the terminal to determine whether to establish a session.

[0422] The first information is used to indicate whether the terminal establishes a session.

[0423] The establishment of a session includes: establishing a session during the registration process.

[0424] The first communication unit is configured to send a second message to the first core network element when the first information is used to instruct the terminal to establish a session, wherein the second message is used to request the establishment of a first session.

[0425] The first information is used by the terminal to determine the establishment of a first session, and the first information includes relevant information about the first session.

[0426] Establishing the first session includes establishing the first session during the registration process.

[0427] The first communication unit is configured to send a second message to the first core network element, wherein the second message is configured to request the establishment of the first session, and the second message carries first attribute information of the first session, the first attribute information of the first session being determined based on relevant information of the first session.

[0428] The relevant information of the first session includes at least one of the following: the second attribute information of the first session, and the relevant information of the destination network element associated with the first session.

[0429] The second message is carried by the first SM container.

[0430] The first communication unit is configured to receive a third message from the first core network element, wherein the third message is configured to indicate acceptance of establishing the first session.

[0431] The third message is carried by the second SM container.

[0432] The third message is carried by one of the following: a registration acceptance message, or a downlink non-access stratum (NAS) transmission message.

[0433] The first message is used to request the terminal to establish a second session.

[0434] The first message carries the first identifier of the second session.

[0435] The first message also carries at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address assigned to the terminal, and the attribute information of the second session.

[0436] The first message is carried by the third SM container.

[0437] The first communication unit is used to send a second message to the first core network element, wherein the second message is used to indicate the completion of the establishment of the second session, and the second message carries a second identifier of the second session, which is generated by the terminal.

[0438] The second message carries one of the following: security mode completion message, registration completion message, service completion message, or uplink non-access stratum (NAS) transmission message.

[0439] The first message carries one of the following: a security mode command, a registration acceptance message, or a service acceptance message.

[0440] Figure 13 is a schematic diagram of the composition structure of a first core network element according to an embodiment of this application, including:

[0441] The second communication unit 1301 is used to send a first message to the terminal, wherein the first message is used by the terminal to determine whether to establish a session.

[0442] The first message carries first information, wherein the first information is used by the terminal to determine whether to establish a session.

[0443] The first information is used to indicate whether the terminal establishes a session.

[0444] The establishment of a session includes: establishing a session during the registration process.

[0445] The second communication unit is configured to receive a second message from the terminal when the first information is used to instruct the terminal to establish a session, wherein the second message is used to request the establishment of a first session.

[0446] The first information is used by the terminal to determine the establishment of a first session, and the first information includes relevant information about the first session.

[0447] Establishing the first session includes establishing the first session during the registration process.

[0448] The second communication unit is configured to receive a second message from the terminal, wherein the second message is configured to request the establishment of the first session, and the second message carries first attribute information of the first session, the first attribute information of the first session being determined based on relevant information of the first session.

[0449] The relevant information of the first session includes at least one of the following: the second attribute information of the first session, and the relevant information of the destination network element associated with the first session.

[0450] The second message is carried by the first SM container.

[0451] The second communication unit is configured to send a fourth message to a second core network element, wherein the fourth message is used to request the establishment of the first session; and to receive a fifth message from the second core network element, wherein the fifth message is used to indicate acceptance of the establishment of the first session.

[0452] The second communication unit is configured to send a third message to the terminal, wherein the third message is configured to indicate acceptance of establishing the first session.

[0453] The third message is carried by the second SM container.

[0454] The third message is carried by one of the following: a registration acceptance message, or a downlink non-access stratum (NAS) transmission message.

[0455] The first message is used to request the terminal to establish a second session.

[0456] The first message carries the first identifier of the second session.

[0457] The first message also carries at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address assigned to the terminal, and the attribute information of the second session.

[0458] The first message is carried by the third SM container.

[0459] The second communication unit is configured to send a fourth message to the second core network element, wherein the fourth message is used to request the establishment of the second session; and to receive a fifth message from the second core network element, wherein the fifth message is used to indicate acceptance of the establishment of the second session.

[0460] The fourth message carries the first identifier of the second session allocated by the first core network element.

[0461] The fifth message carries at least one of the following: a first identifier of the second session, the Quality of Service (QoS) rules used by the terminal to establish the second session, a network address assigned to the terminal, and attribute information of the second session.

[0462] The second communication unit is configured to receive a second message from the terminal, wherein the second message is configured to indicate the completion of the establishment of the second session, and the second message carries a second identifier of the second session, which is generated by the terminal.

[0463] The second message carries one of the following: security mode completion message, registration completion message, service completion message, or uplink non-access stratum (NAS) transmission message.

[0464] The first message carries one of the following: a security mode command, a registration acceptance message, or a service acceptance message.

[0465] In one embodiment, the terminal includes:

[0466] The first communication unit is used to send a sixth message to the first core network element, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message.

[0467] The sixth message is carried by the fourth SM container in the initial NAS message.

[0468] The initial NAS message includes one of the following: a registration request message or a service request message.

[0469] The registration request message is a mobility update management registration request message; or the registration type carried by the registration request message is mobility update management.

[0470] The first communication unit is configured to receive a seventh message from the first core network element, wherein the seventh message is configured to indicate acceptance of establishing the third session.

[0471] The seventh message is carried by the fifth SM container.

[0472] The seventh message is carried by one of the following: registration acceptance message, business acceptance message.

[0473] In one embodiment, the first core network element includes:

[0474] The second communication unit is used to receive a sixth message from the terminal, wherein the sixth message is used to request the establishment of a third session, and the sixth message is carried by the initial NAS message.

[0475] The sixth message is carried by the fourth SM container in the initial NAS message.

[0476] The initial NAS message includes one of the following: a registration request message or a service request message.

[0477] The registration request message is a mobility update management registration request message; or the registration type carried by the registration request message is mobility update management.

[0478] The second communication unit is configured to send an eighth message to the second core network element, wherein the eighth message is used to request the establishment of the third session; and to receive a ninth message from the second core network element, wherein the ninth message is used to indicate acceptance of the establishment of the third session.

[0479] The second communication unit is configured to send a seventh message to the terminal, wherein the seventh message is configured to indicate acceptance of establishing the third session.

[0480] The seventh message is carried by the fifth SM container.

[0481] The seventh message is carried by one of the following: registration acceptance message, business acceptance message.

[0482] The device in this application embodiment can realize the corresponding functions of the devices in the aforementioned communication method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in this device can be found in the corresponding descriptions in the aforementioned method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the device of this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.). Furthermore, the terminal provided in this application embodiment may also be equipped with a first processing unit, which can be used to execute various processes executed by the terminal in the aforementioned communication method, and will not be repeated here. The first core network element may also be equipped with a second processing unit, which can be used to execute various processes executed internally by the first core network element in the aforementioned communication method, and will not be repeated here.

[0483] Figure 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of this application. The communication device 1400 includes a processor 1410, which can call and run computer programs from a memory to enable the communication device 1400 to implement the methods in the embodiments of this application. In one possible implementation, the communication device 1400 may further include a memory 1420. The processor 1410 can call and run computer programs from the memory 1420 to enable the communication device 1400 to implement the methods in the embodiments of this application. The memory 1420 may be a separate device independent of the processor 1410, or it may be integrated into the processor 1410. In one possible implementation, the communication device 1400 may further include a transceiver 1430, which the processor 1410 can control to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. The transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include antennas, and the number of antennas may be one or more.

[0484] In one possible implementation, the communication device 1400 may be a terminal or a first core network element in the embodiments of this application, and the communication device 1400 may implement the corresponding processes implemented by the terminal or the first core network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0485] Figure 15 is a schematic structural diagram of a chip 1500 according to an embodiment of this application. The chip 1500 includes a processor 1510, which can call and run computer programs from memory to implement the methods in the embodiments of this application. In one possible implementation, the chip 1500 may further include a memory 1520. The processor 1510 can call and run computer programs from the memory 1520 to implement the methods executed by a first data control node, a first participating node, a second data control node, or a terminal in the embodiments of this application. The memory 1520 may be a separate device independent of the processor 1510, or it may be integrated into the processor 1510. In one possible implementation, the chip 1500 may further include an input interface 1530. The processor 1510 can control the input interface 1530 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips. In one possible implementation, the chip 1500 may further include an output interface 1540. The processor 1510 can control the output interface 1540 to communicate with other devices or chips, specifically, it can output information or data to other devices or chips.

[0486] In one possible implementation, the chip can be applied to the terminal or the first core network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal or the first core network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0487] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. The above descriptions are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A communication method, comprising: The terminal receives a first message from a first core network element, wherein the first message is used by the terminal to determine whether to establish a session. According to the method of claim 1, wherein, The first message carries first information, wherein the first information is used by the terminal to determine whether to establish a session. The method according to claim 2, wherein, The first information is used to indicate whether the terminal establishes a session. The method according to claim 3, wherein, The establishment of a session includes: establishing a session during the registration process. The method according to claim 3 or 4, wherein, After the terminal receives the first message from the first core network element, it also includes: When the first information is used to instruct the terminal to establish a session, the terminal sends a second message to the first core network element, wherein the second message is used to request the establishment of a first session. The method according to claim 2, wherein, The first information is used by the terminal to determine the establishment of a first session, and the first information includes relevant information about the first session. The method according to claim 6, wherein, Establishing the first session includes establishing the first session during the registration process. The method according to claim 6 or 7, wherein, After the terminal receives the first message from the first core network element, it also includes: The terminal sends a second message to the first core network element, wherein the second message is used to request the establishment of the first session, and the second message carries the first attribute information of the first session, which is determined based on the relevant information of the first session. The method according to any one of claims 6-8, wherein, The relevant information of the first session includes at least one of the following: the second attribute information of the first session, and the relevant information of the destination network element associated with the first session. The method according to claim 5 or 8, wherein, The second message is carried by the first session management SM container. The method according to any one of claims 5, 8, and 10, wherein, After the terminal sends the second message to the first core network element, it also includes: The terminal receives a third message from the first core network element, wherein the third message is used to indicate acceptance of establishing the first session. The method according to claim 11, wherein, The third message is carried by the second SM container. The method according to claim 11 or 12, wherein, The third message is carried by one of the following: a registration acceptance message, or a downlink non-access stratum (NAS) transmission message. According to the method of claim 1, wherein, The first message is used to request the terminal to establish a second session. The method according to claim 14, wherein, The first message carries the first identifier of the second session. The method according to claim 15, wherein, The first message also carries at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address assigned to the terminal, and the attribute information of the second session. The method according to any one of claims 14-16, wherein, The first message is carried by the third SM container. The method according to any one of claims 14-17, wherein, After the terminal receives the first message from the first core network element, it also includes: The terminal sends a second message to the first core network element, wherein the second message is used to indicate the completion of the establishment of the second session, and the second message carries a second identifier of the second session, which is generated by the terminal. The method according to any one of claims 5, 8, 10, and 18, wherein, The second message carries one of the following: security mode completion message, registration completion message, service completion message, or uplink non-access stratum (NAS) transmission message. The method according to any one of claims 1-19, wherein, The first message carries one of the following: a security mode command, a registration acceptance message, or a service acceptance message. A communication method, comprising: The first core network element sends a first message to the terminal, wherein the first message is used by the terminal to determine whether to establish a session. The method according to claim 21, wherein, The first message carries first information, wherein the first information is used by the terminal to determine whether to establish a session. The method according to claim 22, wherein, The first information is used to indicate whether the terminal establishes a session. The method according to claim 23, wherein, The establishment of a session includes: establishing a session during the registration process. The method according to claim 23 or 24, wherein, After the first core network element sends the first message to the terminal, it also includes: When the first information is used to instruct the terminal to establish a session, the first core network element receives a second message from the terminal, wherein the second message is used to request the establishment of a first session. The method according to claim 22, wherein, The first information is used by the terminal to determine the establishment of a first session, and the first information includes relevant information about the first session. The method according to claim 26, wherein, Establishing the first session includes establishing the first session during the registration process. The method according to claim 26 or 27, wherein, After the first core network element sends the first message to the terminal, it also includes: The first core network element receives a second message from the terminal, wherein the second message is used to request the establishment of the first session, and the second message carries first attribute information of the first session, which is determined based on relevant information of the first session. The method according to any one of claims 26-28, wherein, The relevant information of the first session includes at least one of the following: the second attribute information of the first session, and the relevant information of the destination network element associated with the first session. The method according to claim 25 or 28, wherein, The second message is carried by the first SM container. The method according to any one of claims 25, 28, and 30, wherein, After the first core network element receives the second message from the terminal, it further includes: The first core network element sends a fourth message to the second core network element, wherein the fourth message is used to request the establishment of the first session; The first core network element receives a fifth message from the second core network element, wherein the fifth message is used to indicate acceptance of establishing the first session. The method according to claim 31, wherein, After the first core network element receives the fifth message from the second core network element, it also includes: The first core network element sends a third message to the terminal, wherein the third message is used to indicate acceptance of establishing the first session. The method according to claim 32, wherein, The third message is carried by the second SM container. The method according to claim 32 or 33, wherein, The third message is carried by one of the following: a registration acceptance message, or a downlink non-access stratum (NAS) transmission message. The method according to claim 21, wherein, The first message is used to request the terminal to establish a second session. The method according to claim 35, wherein, The first message carries the first identifier of the second session. The method according to claim 36, wherein, The first message also carries at least one of the following: the Quality of Service (QoS) rules used by the terminal to establish the second session, the network address assigned to the terminal, and the attribute information of the second session. The method according to any one of claims 35-37, wherein, The first message is carried by the third SM container. The method according to any one of claims 35-38, wherein, Before the first core network element sends the first message to the terminal, it also includes: The first core network element sends a fourth message to the second core network element, wherein the fourth message is used to request the establishment of the second session; The first core network element receives a fifth message from the second core network element, wherein the fifth message is used to indicate acceptance of establishing the second session. The method according to claim 39, wherein, The fourth message carries the first identifier of the second session allocated by the first core network element. The method according to claim 40, wherein, The fifth message carries at least one of the following: a first identifier of the second session, the Quality of Service (QoS) rules used by the terminal to establish the second session, a network address assigned to the terminal, and attribute information of the second session. The method according to any one of claims 35-41, wherein, After the first core network element sends the first message to the terminal, it also includes: The first core network element receives a second message from the terminal, wherein the second message is used to indicate the completion of the establishment of the second session, and the second message carries a second identifier of the second session, which is generated by the terminal. The method according to any one of claims 25, 28, 30, and 42, wherein, The second message carries one of the following: security mode completion message, registration completion message, service completion message, or uplink non-access stratum (NAS) transmission message. The method according to any one of claims 21-43, wherein, The first message carries one of the following: a security mode command, a registration acceptance message, or a service acceptance message. A communication method, comprising: The terminal sends a sixth message to the first core network element, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message. The method according to claim 45, wherein, The sixth message is carried by the fourth SM container in the initial NAS message. The method according to claim 45 or 46, wherein, The initial NAS message includes one of the following: a registration request message or a service request message. The method according to claim 47, wherein, The registration request message is a mobility update management registration request message; or the registration type carried by the registration request message is mobility update management. The method according to any one of claims 45-48, wherein, After the terminal sends the sixth message to the first core network element, it also includes: The terminal receives a seventh message from the first core network element, wherein the seventh message is used to indicate acceptance of establishing the third session. The method according to claim 49, wherein, The seventh message is carried by the fifth SM container. The method according to claim 49 or 50, wherein, The seventh message is carried by one of the following: registration acceptance message, business acceptance message. A communication method, comprising: The first core network element receives a sixth message from the terminal, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message. The method according to claim 52, wherein, The sixth message is carried by the fourth SM container in the initial NAS message. The method according to claim 52 or 53, wherein, The initial NAS message includes one of the following: a registration request message or a service request message. The method according to claim 54, wherein, The registration request message is a mobility update management registration request message; or the registration type carried by the registration request message is mobility update management. The method according to any one of claims 52-55, wherein, After the first core network element receives the sixth message from the terminal, it also includes: The first core network element sends an eighth message to the second core network element, wherein the eighth message is used to request the establishment of the third session; The first core network element receives a ninth message from the second core network element, wherein the ninth message is used to indicate acceptance of establishing the third session. The method according to claim 56, wherein, After the first core network element receives the ninth message from the second core network element, it also includes: The first core network element sends a seventh message to the terminal, wherein the seventh message is used to indicate acceptance of establishing the third session. The method according to claim 57, wherein, The seventh message is carried by the fifth SM container. The method according to claim 57 or 58, wherein, The seventh message is carried by one of the following: registration acceptance message, business acceptance message. A terminal, comprising: The first communication unit is used to receive a first message from a first core network element, wherein the first message is used by the terminal to determine whether to establish a session. A first core network element includes: The second communication unit is used to send a first message to the terminal, wherein the first message is used by the terminal to determine whether to establish a session. A terminal, comprising: The first communication unit is used to send a sixth message to the first core network element, wherein the sixth message is used to request the establishment of a third session and is carried by the initial NAS message. A first core network element includes: The second communication unit is used to receive a sixth message from the terminal, wherein the sixth message is used to request the establishment of a third session, and the sixth message is carried by the initial NAS message. A terminal, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the terminal to perform the method as claimed in any one of claims 1 to 20 or 45 to 51. A first core network element includes: A transceiver, a processor, and a memory for storing computer programs, the transceiver for communicating with other devices, and the processor for calling and running the computer programs stored in the memory to cause the first core network element to perform the method as described in any one of claims 21 to 44 or 52 to 59. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as described in any one of claims 1 to 20, 21 to 44, 45 to 51, or 52 to 59.

Images