Session identifier allocation methods, and device
By allocating and mapping session identifiers between terminal devices and network elements, the ambiguity in 6G PDU session establishment and session migration between 6GS and 5GS is resolved, thereby improving the efficiency of cross-system session migration and network interoperability.
Patent Information
- Application Number
- PCT/CN2025/094985
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-19
AI Technical Summary
In the existing technology, it is unclear how to perform session migration between different communication systems, especially the establishment of 6G PDU sessions and session migration between 6GS and 5GS.
Through collaboration between terminal devices and network elements, session identifiers are allocated and mapped, including first system session identifiers and second system session identifiers, and the mapping of QoS flows and QoS parameters is maintained during session migration to achieve cross-system session migration.
It enables smooth session migration between different communication systems, simplifies the session establishment process, and improves the efficiency of network interoperability between systems.
Smart Images

Figure CN2025094985_19112026_PF_FP_ABST
Abstract
Description
Session ID allocation method and device Technical Field
[0001] This application relates to the field of communications, and more specifically, to a method and apparatus for assigning session identifiers. Background Technology
[0002] Currently, the methods for session migration between different communication systems are unclear. When user equipment (UE) moves from one communication system to another, it is necessary to address session establishment in the new communication system and session migration between different communication systems. For example, in current technology, how to establish a 6-Generation Protocol Data Unit (6G PDU) session in a 6G mobile communication network, and how to perform session migration between a 6G system (6GS) and a 5G system (5GS), remain unclear. Summary of the Invention
[0003] This application provides a method and apparatus for assigning session identifiers.
[0004] This application provides a session identifier allocation method, including:
[0005] The terminal device sends a session request message to the first network element, and the session request message carries the first system session identifier of the session.
[0006] The terminal device receives a first session acceptance message sent by the first network element, and the first session acceptance message carries the second system session identifier of the session.
[0007] This application provides a session identifier allocation method, including:
[0008] The second network element receives the first message, which carries the first system session identifier of the session;
[0009] The second network element assigns a second system session identifier to the session;
[0010] The second network element sends a second message, which carries the second system session identifier of the session.
[0011] This application provides a session identifier allocation method, including:
[0012] The third network element receives a second session request message, which carries the first system session identifier of the session or indication information to indicate support for cross-system migration.
[0013] The third network element generates one or more of the following for the session: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0014] The third network element sends a second session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0015] This application provides a session identifier allocation method, including:
[0016] The terminal device sends a third session request message to the fourth network element, and the third session request message carries the first system session identifier of the session.
[0017] The terminal device receives a third session acceptance message sent by the fourth network element, which carries the first system session identifier and the second system session identifier.
[0018] This application provides a session identifier allocation method, including:
[0019] The fourth network element receives the third message, which carries the first system session identifier of the session;
[0020] The fourth network element assigns a second system session identifier to the session and associates the first system session identifier with the second system session identifier.
[0021] The fourth network element sends a fourth message, which carries the first system session identifier and the second system session identifier.
[0022] This application provides a session identifier allocation method, including:
[0023] The sixth network element receives a fifth session request message, which carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration.
[0024] The sixth network element generates one or more of the following for the session: the first system QoS flow identifier, the first system QoS parameter, the second system QoS flow identifier, and the second system QoS parameter;
[0025] The sixth network element sends a fifth session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the first system QoS flow identifier, the first system QoS parameters, the second system QoS flow identifier, and the second system QoS parameters.
[0026] This application provides a terminal device, including:
[0027] The first transceiver module is used to send a first session request message to a first network element, the first session request message carrying a first system session identifier of the session; and to receive a first session acceptance message sent by the first network element, the first session acceptance message carrying a second system session identifier of the session.
[0028] This application provides a second network element, including:
[0029] The second transceiver module is used to receive a first message, which carries a first system session identifier of the session; and to send a second message, which carries a second system session identifier of the session.
[0030] The second processing module is used to assign a second system session identifier to the session.
[0031] This application provides a third network element, including:
[0032] The third transceiver module is used to receive a second session request message, which carries a first system session identifier of the session or indication information for supporting cross-system migration; and to send a second session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0033] The third processing module is used to generate one or more of the following for the session: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0034] This application provides a terminal device, including:
[0035] The fourth transceiver module is used to send a third session request message to the fourth network element, the third session request message carrying the first system session identifier of the session; and to receive a session acceptance message sent by the fourth network element, the session acceptance message carrying the first system session identifier and the second system session identifier.
[0036] This application provides a fourth network element, including:
[0037] The fifth transceiver module is used to receive a third message, which carries a first system session identifier of the session; and to send a fourth message, which carries the first system session identifier and the second system session identifier.
[0038] The fifth processing module is used to assign a second system session identifier to the session and associate the first system session identifier with the second system session identifier.
[0039] This application provides a sixth network element, including:
[0040] The sixth transceiver module is used to receive a fifth session request message, which carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration; and to send a session acceptance message, which carries one or more of the following: a first system session identifier, a second system session identifier, a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
[0041] The sixth processing module is used to generate one or more of the following for the session: the first system QoS flow identifier, the first system QoS parameters, the second system QoS flow identifier, and the second system QoS parameters.
[0042] This application provides a terminal device, 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 device to perform the session identifier allocation method described above.
[0043] This application provides a network device, 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 network device to perform the session identifier allocation method described above.
[0044] This application provides a chip for implementing the session identifier allocation method described above.
[0045] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the session identifier allocation method described above.
[0046] This application provides a computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the aforementioned session identifier allocation method.
[0047] This application provides a computer program product, including computer program instructions that cause a computer to execute the session identifier allocation method described above.
[0048] This application provides a computer program that, when run on a computer, causes the computer to execute the aforementioned session identifier allocation method. Attached Figure Description
[0049] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application.
[0050] Figure 2 is a schematic diagram of the 5G network architecture.
[0051] Figure 3 is a schematic flowchart of a session identifier allocation method 300 according to an embodiment of this application.
[0052] Figure 4 is a schematic flowchart of a session identifier allocation method 400 according to an embodiment of this application.
[0053] Figure 5 is a schematic flowchart of a session identifier allocation method 500 according to an embodiment of this application.
[0054] Figure 6 is a flowchart of the implementation according to Embodiment 1 of this application.
[0055] Figure 7 is a flowchart of the implementation according to Embodiment 2 of this application.
[0056] Figure 8 is a flowchart of the implementation according to Embodiment 3 of this application.
[0057] Figure 9 is a schematic flowchart of a session identifier allocation method 900 according to an embodiment of this application.
[0058] Figure 10 is a schematic flowchart of a session identifier allocation method 1000 according to an embodiment of this application.
[0059] Figure 11 is a schematic flowchart of a session identifier allocation method 1100 according to an embodiment of this application.
[0060] Figure 12 is a flowchart of the implementation according to Embodiment 4 of this application.
[0061] Figure 13 is a flowchart of the implementation according to Embodiment 5 of this application.
[0062] Figure 14 is a flowchart of the implementation according to Embodiment Six of this application.
[0063] Figure 15 is a flowchart of the implementation according to Embodiment 7 of this application.
[0064] Figure 16A is a schematic diagram of the contents of a 5G session ID according to Embodiment 8 of this application.
[0065] Figure 16B is a schematic diagram of the contents of a 6G session ID according to Embodiment 8 of this application.
[0066] Figure 16C is a schematic diagram of another 6G session ID according to Embodiment 8 of this application.
[0067] Figure 17 is a schematic block diagram of a terminal device 1700 according to an embodiment of this application.
[0068] Figure 18 is a schematic block diagram of a terminal device 1800 according to an embodiment of the present application.
[0069] Figure 19 is a schematic block diagram of a second network element 1900 according to an embodiment of this application.
[0070] Figure 20 is a schematic block diagram of a third network element 2000 according to an embodiment of this application.
[0071] Figure 21 is a schematic block diagram of a terminal device 2100 according to an embodiment of the present application.
[0072] Figure 22 is a schematic block diagram of a terminal device 2200 according to an embodiment of the present application.
[0073] Figure 23 is a schematic block diagram of a fourth network element 2300 according to an embodiment of this application.
[0074] Figure 24 is a schematic block diagram of a sixth network element 2400 according to an embodiment of this application.
[0075] Figure 25 is a schematic structural diagram of a communication device 2500 according to an embodiment of this application.
[0076] Figure 26 is a schematic structural diagram of a chip 2600 according to an embodiment of this application. Detailed Implementation
[0077] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.
[0078] The technical solutions of this application embodiment can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Non-Terrestrial Networks (NTN) systems, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) systems, or other communication systems.
[0079] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.
[0080] In one implementation, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.
[0081] In one embodiment, the communication system in this application can be applied to unlicensed spectrum, wherein the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application can also be applied to licensed spectrum, wherein the licensed spectrum can also be considered as non-shared spectrum.
[0082] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.
[0083] Terminal devices can be stations (STAION, ST) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.
[0084] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).
[0085] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0086] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0087] In the embodiments of this application, the network device can be a device for communicating with mobile devices, such as an access point (AP) in a WLAN, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or an NTN network, etc.
[0088] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station located on land, water, or other similar locations.
[0089] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.
[0090] Figure 1 illustrates an exemplary communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and the coverage area of each network device 110 may include other numbers of terminal devices 120; this embodiment does not limit the scope of the present application.
[0091] In one embodiment, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which are not limited in this application.
[0092] Network equipment can be further divided into access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with the access network equipment. Access network equipment can be evolved Node Bs (eNBs or e-NodeBs) in Long-Term Evolution (LTE), Next-Generation Radio (NR) (mobile communication system), or Authorized Auxiliary Access Long-Term Evolution (LAA-LTE) systems, such as macro base stations, micro base stations (also called "small base stations"), pico base stations, access points (APs), transmission points (TPs), or new generation Node Bs (gNodeBs).
[0093] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system shown in Figure 1 as an example, the communication device may include network devices and terminal devices with communication functions. The network devices and terminal devices can be specific devices in this application embodiment, which will not be described in detail here. The communication device may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.
[0094] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0095] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0096] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.
[0097] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant 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.
[0098] I. 5G System Architecture:
[0099] Figure 2 is a schematic diagram of the 5G network architecture. The UE connects to the Access Network (AN) via the Uu interface to establish an access layer connection, exchanging access layer messages and radio data. The UE connects to the Access and Mobility Management Function (AMF) via the N1 interface to establish a non-access layer (NAS) connection, exchanging NAS messages. The AMF is the mobility management function in the core network, and the SMF is the session management function in the core network. In addition to managing the UE's mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF is the policy control function in the core network, responsible for formulating policies related to UE mobility management, session management, and charging. The UPF is the user plane function in the core network, transmitting data with the external data network via the N6 interface and with the AN via the N3 interface.
[0100] II. Evolved Packet System (EPS) in 4GS:
[0101] EPS provides connectivity between the UE and external packet data networks such as the Public Land Mobile Network (PLMN). This is known as Public Data Network (PDN) connectivity service.
[0102] For Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) accessing the Evolved Packet Core (EPC), PDN connectivity services are provided by EPS bearers using the S5 / S8 interface based on the General Packet Radio Service (GPRS) Tunneling Protocol (GTP). The EPS bearer represents the finest-grained level of Quality of Service (QoS) control in the EPC / E-UTRAN. This means that all traffic mapped to the same EPS bearer receives the same bearer-level packet forwarding processing (e.g., scheduling policies, queue management policies, rate shaping policies, Radio Link Control (RLC) configuration, etc.). Providing different bearer-level packet forwarding processing requires separate EPS bearers.
[0103] The EPS bearer identifier uniquely identifies the EPS bearer of a UE accessing via E-UTRAN. The EPS bearer identifier is assigned by the MME. When using EPS radio bearers, there is a one-to-one mapping between EPS resource blocks (RBs) and EPS bearers; the mapping between EPS RB identifiers and EPS bearer identifiers is handled by E-UTRAN. The E-RAB ID value used to identify Evolved Radio Access Bearers (E-RABs) on the S1 and X2 interfaces is the same as the EPS bearer ID value used to identify the associated EPS bearer. When using Control Plane Cellular Internet of Things (CIoT) EPS optimization for PDN connectivity services, the MME (for uplink) and UE (for downlink) use the EPS bearer identifier contained in the NAS Protocol Data Unit (PDU) to identify the associated EPS bearer.
[0104] III. PDU Sessions in 5GS:
[0105] 5GC supports PDU connection service, which provides PDU exchange between the UE and the data network identified by the Data Network Name (DNN). PDU connection service is supported through PDU sessions established according to the UE's request.
[0106] In the PDU session establishment request message sent to the network, the UE should provide a PDU session identifier (ID). The PDU session ID is unique for each UE and is an identifier used to uniquely identify a PDU session of the UE.
[0107] In 5GS, a QoS flow is the finest-grained level of end-to-end QoS control within a PDU session. Each QoS flow is identified by a QoS flow identifier (QFI), which is unique within a PDU session. Within a PDU session, user plane packets with the same QFI are processed and scheduled in the same way during transmission.
[0108] IV. Session migration in the network interworking process:
[0109] If the UE supports 5G Core Network (5GC) NAS, when establishing a PDN connection in the EPC, the UE can assign a PDU session ID and send it to the SMF+ Packet Data Network Gateway Control Plane (PGW-C) via the Protocol Configuration Option (PCO). If the SMF+PGW-C receives the PDU session ID from the UE via the Protocol Configuration Option (PCO) and knows that 5GC is not limited by the user's subscribed PDN connections, the SMF+PGW-C will send the mapped QoS parameters and QoS rules to the UE. When moving from EPS to 5GS, the UE sets the SSC mode of the mapped PDU session to Spread Spectrum Communication (SSC) mode 1. The UE and SMF+PGW-C store the association between the EPS bearer and the corresponding 5G QoS rules and QoS flow level QoS parameters (if the QoS flow associated with the QoS rule requires it). When an EPS bearer is deleted (e.g., due to EPS bearer state synchronization or bearer deactivation), the UE and SMF+PGW-C delete any existing 5G QoS rules and QoS flow level QoS parameters (if any) associated with the QoS rules associated with the deleted EPS bearer.
[0110] Similarly, during PDU session establishment, PDU session modification, or service request procedures, the 5G core network needs to allocate EPS bearer IDs for EPS bearers mapped from QoS flows and provide these EPS bearer IDs to the Next Generation Radio Access Network (NG-RAN). If the SMF determines that an EPS bearer ID needs to be allocated for a QoS flow, the serving AMF requested by the SMF allocates the EPS bearer ID. For each PDU session, the EPS bearer ID is allocated to the default EPS bearer and dedicated bearers. The SMF should be able to determine the QoS flows that require EPS bearer IDs based on the QoS profile and operator policies. In scenarios where the UE moves from 5GS to EPS, the AMF needs to determine whether one or more EPS bearer IDs corresponding to a PDU session need to be migrated to EPS, and obtain the EPS bearer context from the SMF+PGW-C corresponding to the EPS bearer ID that needs to be migrated. If the QoS flow associated with the default QoS rule in the PDU session is not allocated an EPS bearer ID, the UE locally deletes the PDU session. If an EPS bearer ID has been assigned to a QoS flow associated with the default QoS rule, the UE retains the PDU session (PDN connection). For the remaining QoS flows without assigned EPS bearer IDs, the UE locally deletes the QoS rules and QoS flow-level QoS parameters (if any) associated with these QoS flows and notifies the affected application-specific QoS resources that have been released. Additionally, the AMF also needs to request the release of PDU sessions that have not acquired an SM context (due to the lack of an assigned EPS bearer ID or failure to acquire the Session Management context (SM context)). If there are QoS flows without assigned EPS bearer IDs in the PDU session (PDN connection), or if the mapped EPS bearer is not included in the QoS flows in the bearer modification request, the SMF+PGW-C will delete the Policy and Charging Control (PCC) rules associated with these QoS flows and notify the PCF of the deleted PCC rules. If any QoS flows with PCC rules have not been assigned Traffic Flow Template (TFT) packet filters, the SMF+PGW-C will delete these PCC rules and notify the PCF of the deleted PCC rules. If the SMF determines that it no longer needs to maintain User Plane (UP) resources for data forwarding, it can also delete the corresponding SM context locally and release the UP resources.
[0111] To support session migration during network interconnection, the UE needs to allocate a PDU session ID for the PDN when requesting to establish a PDN connection. The SMF+PGW-C needs to allocate the corresponding EPS QoS along with the PDN QoS and provide it to the UE. The AMF stores the association between the PDU session ID, the SMF ID, Single Network Slice Selection Assistance Information (S-NSSAI), and the allocated EPS Bearer Identity (EBI) associated with the PDU session ID. Similarly, when the UE requests to establish a PDU session, the SMF also needs to request the AMF to allocate the corresponding EPS bearer ID, 5GS QoS, and corresponding EPS QoS for the UE and provide it to the UE.
[0112] It can be seen that in the existing network interoperability mechanism between EPS and 5GS, when a UE establishes a user plane connection, the network side needs to establish two sets of contexts, including two sets of identification information and QoS parameters. Furthermore, during the network interoperability process, the network also needs to complete the mapping between QoS flow and EPS bearer, as well as the synchronization between session state, QoS flow state, and EPS bearer state.
[0113] The complexity of session migration during network interoperability between EPS and 5GS is mainly due to the different QoS models of EPS and 5GS. Since the 6G QoS model may further utilize the QoS model from 5GS, session migration during 5GS network interoperability may be simpler. However, the methods for establishing 6G PDU sessions and for performing session migration between 6GS and 5GS remain unclear.
[0114] To address the aforementioned issues, this application proposes a session identifier (ID) allocation method to support the establishment of 6G sessions and session migration between 6GS and 5GS.
[0115] Figure 3 is a schematic flowchart of a session identifier allocation method 300 according to an embodiment of this application. This method can optionally be applied to the system shown in Figure 1 or Figure 2, but is not limited thereto. The method includes at least a portion of the following:
[0116] S310. The terminal device sends a first session request message to the first network element, and the first session request message carries the first system session identifier of the session.
[0117] S320. The terminal device receives a first session acceptance message sent by the first network element, wherein the first session acceptance message carries a second system session identifier of the session.
[0118] In one example, the first session acceptance message may also carry the first system session identifier.
[0119] In some implementations, the first system includes a 5GS, and the second system includes a 6GS. The first session request message can be a session establishment request or a session modification request, etc.
[0120] Taking the above example, during the establishment or modification of a 6G session, the UE sends a session request message to the network side. This message carries the 5G session ID assigned by the UE to the session. The network side assigns a 6G session ID to the session and sends a session acceptance message to the UE, which also carries the 6G session ID. The 6G session ID uniquely identifies a UE's 6G session, which can be used for data transmission (or data packet exchange) between the data network (application server) and the UE. Simultaneously, the core network associates the 5G session ID with the 6G session ID. Through this process, the establishment of a 6G PDU session (referred to as a 6G session) is achieved.
[0121] In some implementations, when the terminal device moves from the second system to the first system, the terminal device uses the first system session identifier of the session to perform session migration.
[0122] In one example, session migration refers to the migration of one or more QoS flow IDs corresponding to the original UE's sessions in the original system to the new system when the UE moves from one system to another.
[0123] After a UE establishes a 6G session, when the UE needs to move from 6GS to 5GS, it can directly use the 5G session ID assigned to this 6G session to migrate the 6G session to 5GS. For example, when initiating a session establishment request in 5GS, the 5G session ID can be carried along, indicating that the session establishment request type is an existing session.
[0124] Through the above process, session transfer can be achieved in the interworking process between different systems (such as 6GS to 5GS).
[0125] In some implementations, the session acceptance message may also carry the session context of the first system and the session context of the second system, such as carrying the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters of the session; wherein there is a mapping relationship between the second system QoS flow identifier and the first system QoS flow identifier, and there is a mapping relationship between the second system QoS parameters and the first system QoS parameters.
[0126] The session contexts for the first and second systems are allocated by the network side. For example, when the network side establishes a 6G session for the UE, it establishes a corresponding 6G session context. At the same time, the network side can map the 6G session context to a 5G session context, including mapping the 6G QoS flow identifier to a 5G QoS flow identifier and mapping the 6G QoS parameters to 5G QoS parameters. The network side provides the 6G session context mapping and the 5G session context to the UE for use in 6GS and subsequently when moving to a 5GS system (if applicable).
[0127] In some implementations, the first network element includes a mobility management element (MM). In one example, the mobility management element assigns a 6G session ID to the UE and associates the 5G session ID sent by the UE with the 6G session ID.
[0128] In some embodiments, the first system session identifier of the session includes a first information element, and / or the second system session identifier includes a first information element;
[0129] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0130] The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
[0131] For example, both 6G session ID and 5G session ID contain a first information element. When the value of this first information element in a PDU session ID is 0, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 1, it indicates that the PDU session ID is a 6G session ID. Alternatively, when the value of the first information element in a PDU session ID is 1, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 0, it indicates that the PDU session ID is a 6G session ID.
[0132] This application also proposes another session identifier allocation method. Figure 4 is a schematic flowchart of a session identifier allocation method 400 according to an embodiment of this application. This method can optionally be applied to the system shown in Figure 1 or Figure 2, but is not limited thereto. The method includes at least a portion of the following:
[0133] S410, the second network element receives the first message, which carries the first system session identifier of the session;
[0134] S420, The second network element assigns a second system session identifier to the session;
[0135] S430, the second network element sends a second message, which carries the second system session identifier of the session.
[0136] The second network element may include a mobility management element (MM), a session management element (SM), or a user data management element (UDM). The second network element can receive the first message from the UE or other network elements and return a second message to the UE or the other network element.
[0137] For example, the second network element (such as MM) receives the first message (such as session request message, session establishment request message or session modification request) sent by the UE. After the second network element allocates the second system session identifier, it sends the second message (such as session acceptance message, session establishment acceptance message or session modification acceptance message) to the UE.
[0138] For example, a second network element (such as a UDM) receives a first message (such as a session registration message) sent by an SM. After allocating a second system session identifier, the second network element sends a second message to the SM.
[0139] For example, the second network element (such as the anchor session management network element (anchor SM) receives the first message (such as a session establishment request message) sent by the MM. After the second network element allocates the second system session identifier, it sends a second message (such as a session establishment acceptance message) to the MM.
[0140] While assigning a second system session identifier to the session, the second network element can further associate the first system session identifier of the session with the second system session identifier. Subsequently, when the UE moves from the second system to the first system, it can use the first system session identifier to achieve session migration.
[0141] In some implementations, the first system includes a 5GS and the second system includes a 6GS.
[0142] Taking the MM (Multi-Node Component) as the second network element, during the establishment or modification of a 6G session by the UE, a session request message is sent to the MM. This message carries the 5G session ID assigned by the UE to the session. The MM assigns a 6G session ID to the session and sends a session acceptance message to the UE, which also carries the 6G session ID. The 6G session ID uniquely identifies a UE's 6G session, which can be used for data transmission (or data packet exchange) between the data network (application server) and the UE. Simultaneously, the MM associates the 5G session ID with the 6G session ID.
[0143] Furthermore, the second network element can also obtain the session context of the first system and the session context of the second system from the third network element, and further carry the session context of the first system and the session context of the second system in the second message. In one example, after the second network element assigns a second system session identifier to the session, and before the second network element sends the second message, it also includes:
[0144] The second network element sends a second session request message to the third network element. The second session request message carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration.
[0145] The second network element receives a second session acceptance message sent by the third network element. The second session acceptance message carries one or more of the following: a first system session identifier, a second system session identifier, a second system QoS flow identifier of the session, a second system QoS parameter of the session, a first system QoS flow identifier of the session, and a first system QoS parameter of the session.
[0146] The second session request message may be the same as or different from the first session request message, and the second session acceptance message may be the same as or different from the first session acceptance message.
[0147] The second system QoS flow identifier and the second system QoS parameters of the session can be established by a third network element, and the second system QoS flow identifier and the second system QoS parameters can be mapped to the first system QoS flow identifier and the first system QoS parameters, respectively.
[0148] Correspondingly, the second message sent by the second network element may also carry one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
[0149] In one example, the third network element includes a session management network element co-located in the first system and the second system. The co-located session management network element can refer to a network element that has session management functions in both the first system and the second system.
[0150] For example, the SM generates a 6G session context for a 6G session and maps the 6G session context to a 5G session context, including mapping the 6G QoS flow identifier to the 5G QoS flow identifier and the 6G QoS parameters to the 5G QoS parameters. The SM provides the 6G session context mapping and the 5G session context to the UE for use in 6GS and subsequently when moving to a 5GS system (if applicable).
[0151] In some embodiments, the first system session identifier of the session includes a first information element, and / or the second system session identifier includes a first information element;
[0152] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0153] The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
[0154] For example, both 6G session ID and 5G session ID contain a first information element. When the value of this first information element in a PDU session ID is 0, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 1, it indicates that the PDU session ID is a 6G session ID. Alternatively, when the value of the first information element in a PDU session ID is 1, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 0, it indicates that the PDU session ID is a 6G session ID.
[0155] This application also proposes another session identifier allocation method. Figure 5 is a schematic flowchart of a session identifier allocation method 500 according to an embodiment of this application. This method can optionally be applied to the system shown in Figure 1 or Figure 2, but is not limited thereto. The method includes at least a portion of the following:
[0156] S510, the third network element receives a second session request message, which carries the first system session identifier of the session or indication information for indicating support for cross-system migration;
[0157] S520, The third network element generates one or more of the following for the session: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters;
[0158] S530. The third network element sends a second session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0159] The second session request message may be the same as or different from the first session request message, and the second session acceptance message may be the same as or different from the first session acceptance message.
[0160] In some implementations, the third network element includes a session management network element (SM or SMF).
[0161] The aforementioned indication information used to indicate support for cross-system migration can have two possibilities: One is a session-level indication, where the MM determines whether the current session supports cross-system migration based on the session request's DNN and / or slice identifier S-NSSAI, as well as whether the network and UE support interworking, and then indicates this to the SM. The other is a UE-level indication, where the MM determines whether interworking is supported based on UE and network capabilities. If supported, it informs the SM that the UE supports interworking; the SM then determines, based on operator configuration and UE capabilities, whether to allocate a session context in the target system for the current session, including the corresponding QoS flow identifier and QoS parameters.
[0162] In some implementations, the first system includes 5GS and the second system includes 6GS. The session request message can be a session establishment request or a session modification request, etc. For example, when the network side establishes a 6G session for the UE, the SM establishes a corresponding 6G session context for the session; at the same time, the SM can map the 6G session context to a 5G session context, including mapping the 6G QoS flow identifier to a 5G QoS flow identifier and mapping the 6G QoS parameters to 5G QoS parameters; the SM provides the 6G session context mapping and the 5G session context to the UE for use in 6GS and subsequently when moving to a 5GS system (if applicable).
[0163] In some embodiments, the first system session identifier of the session includes a first information element, and / or the second system session identifier includes a first information element;
[0164] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0165] The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
[0166] For example, both 6G session ID and 5G session ID contain a first information element. When the value of this first information element in a PDU session ID is 0, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 1, it indicates that the PDU session ID is a 6G session ID. Alternatively, when the value of the first information element in a PDU session ID is 1, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 0, it indicates that the PDU session ID is a 6G session ID.
[0167] The following detailed description, in conjunction with the accompanying drawings, provides specific embodiments.
[0168] In the various embodiments described below, when establishing or modifying a 6G PDU session (hereinafter referred to as a 6G session) in 6GS, the 6G PDU session ID (hereinafter referred to as the 6G session ID) is mainly allocated by the network side. The allocated 6G session ID can be unique within the network or unique within the UE. The 6G session ID is mainly used to identify a 6G session, which is mainly used for data transmission (or data packet exchange) between the data network (application server) and the UE. To ensure that the 6G session ID can uniquely identify a 6G session for a UE, the 6G session ID can be allocated by the mobility management network element, the unified data management network element (the network element that manages user subscription information and other related data), or a new network element used for ID allocation.
[0169] To support interoperability between 5GS and 6GS, when a UE requests to establish or modify a 6G session, it can carry the 5G PDU session ID (referred to as 5G session ID) in the 6G session request (such as a session establishment request or a session modification request). When the core network element assigns the 6G session ID to the session, it also associates the 5G session ID with the 6G session ID. In addition to assigning 6G QoS parameters, the session management network element also needs to assign the corresponding 5G QoS parameters to the UE.
[0170] Example 1:
[0171] In this embodiment, when a UE requests to establish a 6G session, the Mobility Management Element (MM) can assign it a 6G session ID and select the corresponding Session Management Element (SM). Furthermore, if the UE supports 5GS NAS, the UE can also assign a corresponding 5G session ID for this session, used for session migration when the UE moves from 6GS to 5GS.
[0172] Figure 6 is a flowchart of the implementation according to Embodiment 1 of this application, including the following steps:
[0173] S601. The UE sends a first session request message to a first network element or a second network element through the access network equipment, such as sending a session establishment request to the mobility management network element (MM). The session establishment request includes one or more of the following parameters:
[0174] (1) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0175] (2) Slice identifier, used to indicate which network slice the session is established on;
[0176] (3) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0177] (4) 5G Session ID: If the UE supports 5G NAS, the UE can assign a 5G session ID to the 6G session and send it to the core network for cross-system session migration during 5GS and 6GS interoperation.
[0178] S602. After receiving the session establishment request, the MM selects a suitable session management network element (SM) based on the UE's capabilities, UE's subscription data, the requested DNN, slice identifier, UE location, and access type. If the UE supports 5G NAS (e.g., indicated in the UE's capabilities or carried in the session establishment request message with a 5G session ID), the MM selects a network element that combines 5G SMF and 6G SM (SMF+6GSM). Alternatively, it selects a session management network element that can be used for both 5GS and 6GS. Furthermore, the MM assigns a 6G session ID to the UE, which uniquely identifies a 6G session of the UE.
[0179] S603 and MM send a second session request message to the third network element, for example, a session establishment request to SM. The session establishment request includes the following:
[0180] (1) UE identification information, such as subscription permanent identifier (SUPI);
[0181] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0182] (3) Slice identifier, used to indicate which network slice the session is established on;
[0183] (4) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0184] (5) Indication information for indicating support interworking with 5GS: MM determines based on UE capabilities (e.g., whether it supports 5G NAS) and / or UE subscription data (e.g., core network type restrictions on 5GC, support for interworking with 5GS on some DNNs, slices).
[0185] (6) Indication information for indicating the type of network interworking: The AMF indicates whether the network supports network interworking with an interface between the AMF and the 6G MM or network interworking without an interface between the AMF and the 6G MM based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM).
[0186] (7) 5G Session ID: If the UE provides this parameter, and the MM determines that network interoperability between 5GS and 6GS is supported, then this parameter will be included. The MM will store the mapping between 5G session IDs and 6G session IDs locally.
[0187] (8) 6G Session ID: Identification information assigned by MM for this 6G session.
[0188] If the UE's subscription message changes and the session no longer supports network interoperability with the 5GS, the MM needs to notify the SM.
[0189] After receiving a session establishment request, S604 and SM retrieve session-related subscription data from UDM or local storage, and establish the corresponding session context, including establishing multiple 6G QoS flow IDs and 6G QoS parameters. SM formulates 6G QoS parameters and rules for controlling UPF functions based on the UE subscription message and policy and charging control rules obtained from policy-associated network elements. If the session establishment request received from MM contains a 5G session ID and / or indication information indicating support for interworking with 5GS, then SM needs to map multiple 6G QoS flow IDs to 5G QoS flow IDs and map 6G QoS parameters to 5G QoS parameters, including session-level QoS parameters and QoS flow-level parameters. SM registers session-related information in UDM, which mainly includes:
[0190] (1) UE identification information;
[0191] (2) Serving SM ID and / or Fully Qualified Domain Name (FQDN);
[0192] (3) The core network type (CN type) corresponding to the service SM indicates that the service SM is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0193] (4) UE address information assigned to the UE for this 6G session, such as the UE IP address;
[0194] (5) 5G Session ID;
[0195] (6) 6G Session ID.
[0196] S605 and SM select a suitable UPF to establish a user plane data transmission channel and establish rules related to session management to control the functions of the UPF and obtain reports on the current status of the UPF. These rules include packet detection rules, forwarding action rules, multi-access rules, usage reporting rules, QoS enforcement rules, and session reporting rules.
[0197] S606. If the session is successfully established, the SM sends a second session acceptance message to the MM, such as a 6G session establishment acceptance message. This session establishment acceptance message contains one or more of the following parameters:
[0198] (1) 6G Session ID;
[0199] (2) 5G Session ID, which is included if interoperability with 5GS networks is supported;
[0200] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include one or more of the following: 6G session ID, 6G QoS flow ID, QoS profiles, and QoS profiles containing 6G QoS parameters.
[0201] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0202] a. 6G Session ID;
[0203] b. 6G QoS parameters;
[0204] c. Mapped 5G QoS parameters (or 5G QoS parameters), including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR;
[0205] d. Multiple 6G QoS flow IDs included in a 6G session;
[0206] e. Multiple 5G QoS flow IDs (or mapped 5G QoS flow IDs);
[0207] f. UE address information, such as IP address;
[0208] g. Indication information used to indicate support for interworking with 5GS: This indicates support for interoperability with 5GS in the current session, or support for migrating the current session to 5GS. Alternatively, it indicates that the UE supports interoperability with 5GS.
[0209] h. Indication information for indicating the type of network interoperability: For example, indication information for indicating that the network supports network interoperability with an interface between AMF and 6G MM, or indication information for indicating that the network supports network interoperability without an interface between AMF and 6G MM.
[0210] In step S607, the MM sends the SM container containing the information sent to the access network device in step S606 to the access network device, and sends the SM container containing the information sent to the UE to the UE via a session establishment acceptance message (such as a first session acceptance message) through the access network device. The UE can determine the network capability based on the received mapped 5G QoS parameters (or 5G QoS parameters), which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 5GS, which indicates that the network supports 5GS and 6GS interworking.
[0211] Optionally, when a UE moves from 6GS to 5GS, it can directly use the 5G session ID assigned to the 6G session to migrate the 6G session to 5GS. For example, a session establishment request can be initiated in 5GS carrying the 5G session ID, and indicating that the session establishment request type is an existing session.
[0212] Example 2:
[0213] In this embodiment, the 6G session ID can be allocated by the UDM or other core network elements. This UDM or other core network element is unique to a specific UE within the 6G system, thus ensuring that the allocated 6G session ID can uniquely identify a UE's session. In one example, after receiving a session establishment request message, the SM requests the UDM to allocate a 6G session ID.
[0214] Figure 7 is a flowchart of the implementation according to Embodiment 2 of this application, including the following steps:
[0215] S701. The UE sends a first session request message to a first network element or a second network element through the access network equipment, such as sending a session establishment request to the mobility management network element (MM). The session establishment request includes one or more of the following parameters:
[0216] (1) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0217] (2) Slice identifier, used to indicate which network slice the session is established on;
[0218] (3) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0219] (4) 5G Session ID: If the UE supports 5G NAS, the UE can assign a 5G session ID to the 6G session and send it to the core network for cross-system session migration during 5GS and 6GS interoperation.
[0220] The S702 and 6G MM select the appropriate session management network element (6G SM) based on UE capabilities, UE subscription data, requested DNN, slice identifier, UE location, and access type, and forward the session establishment request message to the 6G SM. If the UE supports 5GNAS (e.g., indicated in the UE capabilities or carried in the session establishment request message), the MM selects a network element that combines 5G SMF and 6G SM (SMF+6G SM). Alternatively, it selects a session management network element that can be used for both 5GS and 6GS. The MM sends a second session request message to a third network element, such as a session establishment request to the SM, which includes the following:
[0221] (1) UE identification information, such as SUPI;
[0222] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0223] (3) Slice identifier, used to indicate which network slice the session is established on;
[0224] (4) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0225] (5) Indication information for indicating support interworking with 5GS: MM determines based on UE capabilities (e.g., whether it supports 5G NAS) and / or UE subscription data (e.g., core network type restrictions on 5GC, support for interworking with 5GS on some DNNs, slices).
[0226] (6) Indication information for indicating the type of network interoperability: 6G MM indicates whether the network supports network interoperability with an interface between AMF and 6G MM or network interoperability without an interface between AMF and 6G MM based on network configuration (e.g., whether there is an interface between AMF and 6G MM).
[0227] (7) 5G Session ID: If the UE provides this parameter, and the MM determines that network interoperability between 5GS and 6GS is supported, then this parameter will be included. The MM will store the mapping between 5G session IDs and 6G session IDs locally.
[0228] The S703 and 6G SM determine whether to accept the UE's session establishment request based on the UE's subscription data and network configuration. The 6G SM establishes a 6G session context for this session (including establishing multiple 6G QoS flow IDs and 6G QoS parameters). If the session establishment request includes a 5G session ID and / or indications of support interworking with 5GS, the 6G SM will also include the mapped 5G session context (including the mapped 5G QoS flow ID and 5G QoS parameters) in the session establishment acceptance message. The SM registers the session-related information in the UDM, which mainly includes:
[0229] (1) UE identification information;
[0230] (2) Serving SM ID and / or FQDN;
[0231] (3) The core network type (CN type) corresponding to the service SM indicates that the service SM is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0232] (4) UE address information assigned to the UE for this 6G session, such as the UE IP address;
[0233] (5) 5G Session ID.
[0234] In addition, the 6G SM will request the UDM or other core network elements to allocate a 6G session ID for the session; or, the session registration message can be used to request the UDM to allocate a 6G session ID.
[0235] S704: The UDM stores the UE session context and assigns a 6G session ID to the session. The UDM then sends the 6G session ID to the 6GSM. The 6G SM stores the received 6G session ID in its local session context. If a 5G session ID is received in the session establishment request, it will be associated with the 6G session ID.
[0236] The S705 and SM select a suitable UPF to establish a user plane data transmission channel and establish rules related to session management to control the functions of the UPF and obtain reports on the current status of the UPF. These rules include packet detection rules, forwarding action rules, multi-access rules, usage reporting rules, QoS enforcement rules, and session reporting rules.
[0237] S706. If the session is successfully established, the SM sends a second session acceptance message to the MM, such as a 6G session establishment acceptance message. This session establishment acceptance message contains one or more of the following parameters:
[0238] (1) 6G Session ID;
[0239] (2) 5G session ID, if it supports interoperability with 5GS networks;
[0240] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include: 6G session ID, 6G QoS flow ID, and QoS profiles, which contain 6G QoS parameters.
[0241] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0242] a. 6G Session ID;
[0243] b. 6G QoS parameters;
[0244] c. Mapped 5G QoS parameters (or 5G QoS parameters), including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR;
[0245] d. Multiple 6G QoS flow IDs included in a 6G session;
[0246] e. Multiple 5G QoS flow IDs (or mapped 5G QoS flow IDs);
[0247] f. UE address information, such as IP address;
[0248] g. Indication information used to indicate support for interworking with 5GS: This indicates support for interoperability with 5GS in the current session, or support for migrating the current session to 5GS. Alternatively, it indicates that the UE supports interoperability with 5GS.
[0249] h. Indication information for indicating the type of network interoperability: For example, indication information for indicating that the network supports network interoperability with an interface between AMF and 6G MM, or indication information for indicating that the network supports network interoperability without an interface between AMF and 6G MM.
[0250] The MM needs to record the association between the 6G session ID and the corresponding SMF. If the UE includes the 5G session ID in the session establishment request message, the 6G MM also needs to associate the 5G session ID with the 6G session ID.
[0251] In step S707, the MM sends the SM container containing the information sent to the access network device from step S706 to the access network device, and sends the SM container containing the information sent to the UE to the UE via a session establishment acceptance message (such as a first session acceptance message) through the access network device. The UE can determine the network capability based on the received mapped 5G QoS parameters (or 5G QoS parameters), which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 5GS, which indicates that the network supports 5GS and 6GS interworking.
[0252] Optionally, when a UE moves from 6GS to 5GS, it can directly use the 5G session ID assigned to the 6G session to migrate the 6G session to 5GS. For example, a session establishment request can be initiated in 5GS carrying the 5G session ID, and indicating that the session establishment request type is an existing session.
[0253] Example 3:
[0254] In this embodiment, each UE may have only one anchor session management network element. This network element is unrelated to the DNN and is only related to the location of the access network device and the UE. Other session management network elements (SMs) are related to the DNN and can configure rules for managing the UPF function for 6G sessions (similar to N4 rules in 5GS). As shown in Figure 8, the process by which this SM assigns a 6G session ID to the UE is as follows:
[0255] S801. The UE sends a first session request message to a first network element or a second network element through the access network equipment, such as sending a session establishment request to the mobility management network element (MM). The session establishment request includes one or more of the following parameters:
[0256] (1) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0257] (2) Slice identifier, used to indicate which network slice the session is established on;
[0258] (3) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0259] (4) 5G Session ID: If the UE supports 5G NAS, the UE can assign a 5G session ID to the 6G session and send it to the core network for cross-system session migration during 5GS and 6GS interoperation.
[0260] The S802 and 6G MM select the appropriate session management network element (anchor SM) based on UE capabilities, UE subscription data, requested DNN, slice identifier, UE location, and access type, and forward the session establishment request message to the anchor SM. If the UE supports 5G NAS (e.g., indicated in the UE capabilities or carried in the session establishment request message), the MM selects a network element that combines 5G SMF and 6G SM (SMF+6G SM). Alternatively, it selects a session management network element that can be used for both 5GS and 6GS. The MM sends a session establishment request to the anchor SM, which includes the following:
[0261] (1) UE identification information, such as SUPI;
[0262] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0263] (3) Slice identifier, used to indicate which network slice the session is established on;
[0264] (4) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0265] (5) Indication information for indicating support interworking with 5GS: MM determines based on UE capabilities (e.g., whether it supports 5G NAS) and / or UE subscription data (e.g., core network type restrictions on 5GC, support for interworking with 5GS on some DNNs, slices).
[0266] Furthermore, based on network configuration (e.g., whether there is an interface between AMF and 6G MM), it can further indicate whether the UE network supports network interworking with an interface or network interworking without an interface.
[0267] (6) Indication information for indicating the type of network interworking: The AMF indicates whether the network supports network interworking with an interface between the AMF and the 6G MM or network interworking without an interface between the AMF and the 6G MM based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM).
[0268] (7) 5G Session ID: If the UE provides this parameter, and the MM determines that network interoperability between 5GS and 6GS is supported, then this parameter will be included. The MM will store the mapping between 5G session IDs and 6G session IDs locally.
[0269] In step S803, the Anchor SM assigns a 6G session ID to the session requested by the UE. The Anchor SM selects a suitable 6G SM based on information such as the requested DNN, slice type, and UE location. If the session establishment request includes a 5G session ID and / or indication information indicating support for interworking with 5GS, the Anchor SM can associate the 6G session ID with the 5G session ID and select a 6G SM co-located with the 5G SMF (if the 6G MM did not select an anchor SM co-located with the 5G SMF in step S802).
[0270] The S804 and Anchor SM send a second session request to a third network element, for example, by sending a session establishment request to the 6G SM. This session establishment request includes one or more of the following parameters:
[0271] (1) UE identification information, such as SUPI;
[0272] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0273] (3) Slice identifier, used to indicate which network slice the session is established on;
[0274] (4) Requested Data Network Name (DNN) indicates the data network that the UE requests to interact with, or in other words, the application server that the UE requests to provide data services.
[0275] (5) Indication information for indicating support interworking with 5GS: MM determines based on UE capabilities (e.g., whether it supports 5G NAS) and / or UE subscription data (e.g., core network type restrictions on 5GC, support for interworking with 5GS on some DNNs, slices).
[0276] (6) Indication information for indicating the type of network interoperability: The MM indicates, based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM), whether the network supports network interoperability with an interface (Interworking with an interface between the AMF and the 6G MM) or network interoperability without an interface (Interworking without an interface between the AMF and the 6G MM).
[0277] (7) 5G Session ID: If the UE provides this parameter, and the MM determines that network interoperability between 5GS and 6GS is supported, then this parameter will be included. The MM will store the mapping between 5G session IDs and 6G session IDs locally;
[0278] (8) 6G Session ID, used to uniquely identify a UE's 6G session.
[0279] After receiving a session establishment request, the S805 and SM retrieve session-related subscription data from the UDM or local storage, and establish the corresponding session context, including establishing multiple 6G QoS flow IDs and 6G QoS parameters. The SM formulates 6G QoS parameters and rules for controlling UPF functions based on the UE subscription message and policy and charging control rules obtained from policy-associated network elements. If the session establishment request received from the MM contains a 5G session ID and / or indications supporting interworking with 5GS, the SM needs to map the 6G QoS parameters to 5G QoS parameters, including session-level QoS parameters and QoS flow-level parameters. The SM registers session-related information in the UDM, which mainly includes:
[0280] (1) UE identification information;
[0281] (2) Serving SM ID and / or FQDN;
[0282] (3) The core network type (CN type) corresponding to the service SM indicates that the service SM is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0283] (4) UE address information assigned to the UE for this 6G session, such as the UE IP address;
[0284] (5) 5G Session ID;
[0285] (6) 6G Session ID.
[0286] S806 and SM select a suitable UPF to establish a user plane data transmission channel and establish rules related to session management to control the functions of the UPF and obtain reports on the current status of the UPF. These rules include packet detection rules, forwarding action rules, multi-access rules, usage reporting rules, QoS enforcement rules, and session reporting rules.
[0287] S807. If the session is successfully established, the SM sends a second session acceptance message to the anchor SM, such as a 6G session establishment acceptance message. This session establishment acceptance message contains one or more of the following parameters:
[0288] (1) 6G Session ID;
[0289] (2) 5G session ID, if it supports interoperability with 5GS networks;
[0290] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include: 6G session ID, 6G QoS flow ID, and QoS profiles, which contain 6G QoS parameters.
[0291] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0292] a. 6G Session ID;
[0293] b. 6G QoS parameters;
[0294] c. Mapped 5G QoS parameters (or 5G QoS parameters), including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR;
[0295] d. Multiple 6G QoS flow IDs included in a 6G session;
[0296] e. Multiple 5G QoS flow IDs (or mapped 5G QoS flow IDs);
[0297] f. UE address information, such as IP address;
[0298] g. Indication information used to indicate support for interworking with 5GS: This indicates support for interoperability with 5GS in the current session, or support for migrating the current session to 5GS. Alternatively, it indicates that the UE supports interoperability with 5GS.
[0299] h. Indication information used to indicate that the network supports interworking with an interface between AMF and 6G MM, or indication information used to indicate that the network supports interworking without an interface between AMF and 6G MM.
[0300] The S808 and anchor SM send a 6G session establishment accept message to the MM. The MM sends an SM container containing information destined for the access network device to the access network device, and sends an SM container containing information destined for the UE to the UE via the session establishment accept message through the access network device. The UE can determine the network capability based on the received mapped 5G QoS parameters (or 5G QoS parameters), which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 5GS, which indicates that the network supports 5GS and 6GS interworking.
[0301] Optionally, when a UE moves from 6GS to 5GS, it can directly use the 5G session ID assigned to the 6G session to migrate the 6G session to 5GS. For example, a session establishment request can be initiated in 5GS carrying the 5G session ID, and indicating that the session establishment request type is an existing session.
[0302] This application also proposes a session identifier (ID) allocation method, which allocates a corresponding 6G session ID based on the UE's capabilities during the establishment or modification of a 5G session, so that the UE can use it when it needs to move from 5GS to 6GS, thereby realizing session migration.
[0303] Figure 9 is a schematic flowchart of a session identifier allocation method 900 according to an embodiment of this application. This method can optionally be applied to the system shown in Figure 1 or Figure 2, but is not limited thereto. The method includes at least a portion of the following:
[0304] S910, The terminal device sends a third session request message to the fourth network element, and the third session request message carries the first system session identifier of the session.
[0305] S920. The terminal device receives a third session acceptance message sent by the fourth network element, the third session acceptance message carrying the first system session identifier and the second system session identifier.
[0306] The third session request message may be the same as or different from the aforementioned first session request message or second session request message, and the third session acceptance message may be the same as or different from the aforementioned first session acceptance message or second session acceptance message.
[0307] In some implementations, the first system includes a 5GS, and the second system includes a 6GS. The third session request message can be a session establishment request or a session modification request, etc.
[0308] Taking the above example, during the process of establishing or modifying a 5G session, the UE sends a session request message to the network side. The session request message carries the 5G session ID assigned by the UE for the session. The network side assigns a 6G session ID to the session based on the UE's capabilities and / or other information, and returns the 6G session ID to the UE.
[0309] In some implementations, when the UE moves from the first system to the second system, the terminal device uses the second system session identifier of the session to perform session migration.
[0310] For example, after a UE establishes a 5G session, when the UE needs to move from 5GS to 6GS, it can directly use the 6G session ID assigned to this session by the fourth network element to migrate this session to 6GS.
[0311] Through the above process, session transfer can be achieved in the interworking process between different systems (such as 5GS to 6GS).
[0312] In some implementations, the third session acceptance message may also carry the session context of the first system and the session context of the second system, such as carrying the first system QoS flow identifier, the first system QoS parameters, the second system QoS flow identifier, and the first system QoS parameters of the session; wherein there is a mapping relationship between the first system QoS flow identifier and the second system QoS flow identifier, and there is a mapping relationship between the first system QoS parameters and the second system QoS parameters.
[0313] The session contexts for the first and second systems are allocated by the network side. For example, when the network side establishes a 5G session for the UE, it establishes the corresponding 5G session context. At the same time, the network side can map the 5G session context to a 6G session context, including mapping the 5G QoS flow identifier to a 6G QoS flow identifier and mapping the 5G QoS parameters to 6G QoS parameters. The network side provides the 5G session context mapping and the 6G session context to the UE for use in 5GS and subsequently when moving to a 6GS system (if applicable).
[0314] In some implementations, the fourth network element includes a mobility management network element, such as an Access and Mobility Management Function (AMF) or a MM. In one example, the AMF assigns a 6G session ID to the UE and associates the 5G session ID sent by the UE with the 6G session ID.
[0315] In some embodiments, the first system session identifier of the session includes a first information element, and / or the second system session identifier includes a first information element;
[0316] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0317] The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
[0318] For example, both 6G session ID and 5G session ID contain a first information element. When the value of this first information element in a PDU session ID is 0, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 1, it indicates that the PDU session ID is a 6G session ID. Alternatively, when the value of the first information element in a PDU session ID is 1, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 0, it indicates that the PDU session ID is a 6G session ID.
[0319] This application also proposes another session identifier allocation method. Figure 10 is a schematic flowchart of a session identifier allocation method 1000 according to an embodiment of this application. This method can optionally be applied to the system shown in Figure 1 or Figure 2, but is not limited thereto. The method includes at least a portion of the following:
[0320] S1010, the fourth network element receives the third message, which carries the first system session identifier of the session;
[0321] S1020. The fourth network element assigns a second system session identifier to the session and associates the first system session identifier with the second system session identifier.
[0322] S1030, the fourth network element sends a fourth message, which carries the first system session identifier and the second system session identifier.
[0323] The second network element may include a mobility management network element (AMF), a session management network element (SMF), or a user data management network element (UDM). The fourth network element may receive a third message from the UE or other network elements and return a fourth message to the UE or the other network element.
[0324] For example, after the fourth network element (such as AMF) receives the third message (such as session establishment request message or session modification request) sent by the UE, the second network element allocates the second system session identifier and then sends the fourth message (such as session establishment acceptance message or session modification acceptance message) to the UE.
[0325] For example, the fourth network element (such as MM or UDM) receives the third message (such as session registration message or session ID allocation request) sent by the SMF. After the fourth network element allocates the second system session identifier, it sends the fourth message to the SMF.
[0326] For example, when the fourth network element (such as SMF) receives the third message (such as a session establishment request message) sent by the AMF, after the fourth network element allocates the second system session identifier, it sends a fourth message (such as a session establishment acceptance message) to the SMF.
[0327] After the second network element assigns a second system session identifier to the session, it can further associate the first system session identifier of the session with the second system session identifier. In subsequent processes, when the UE moves from the first system to the second system, the second system session identifier can be used to achieve session migration.
[0328] In some implementations, the first system includes a 5GS and the second system includes a 6GS.
[0329] Taking the AMF (Application Management Function) as the fourth network element, during the establishment or modification of a 5G session, the UE sends a session request message to the AMF. This message carries the 5G session ID assigned by the UE for the session. The AMF assigns a 6G session ID to the session and sends a session acceptance message to the UE, which also carries the 6G session ID. The 6G session ID uniquely identifies a UE's 6G session, which can be used for data transmission (or data packet exchange) between the data network (application server) and the UE. Simultaneously, the AMF associates the 5G session ID with the 6G session ID when assigning the 6G session ID.
[0330] Furthermore, the fourth network element can also obtain the session context of the first system and the session context of the second system from the fifth network element, and further carry the session context of the first system and the session context of the second system in the fourth message. In one example, after the fourth network element assigns the second system session identifier to the session, and before the fourth network element sends the fourth message, it also includes:
[0331] The fourth network element sends a fourth session request message to the fifth network element. The fourth session request message carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration.
[0332] The fourth network element receives the fourth session acceptance message sent by the fifth network element. The fourth session acceptance message carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
[0333] The fourth session request message may be the same as or different from the aforementioned first session request message, second session request message, or third session request message, and the fourth session acceptance message may be the same as or different from the aforementioned first session acceptance message, second session acceptance message, or third session acceptance message.
[0334] The first system QoS flow identifier and the first system QoS parameters of the session can be established by the fifth network element, and the first system QoS flow identifier and the first system QoS parameters can be mapped to the second system QoS flow identifier and the second system QoS parameters, respectively.
[0335] Correspondingly, the fourth message sent by the fourth network element may also carry one or more of the following: the first system QoS flow identifier of the session, the first system QoS parameters of the session, the second system QoS flow identifier of the session, and the second system QoS parameters of the session.
[0336] In one example, the fifth network element includes an SMF. For instance, the SMF generates a 5G session context for a 5G session and maps the 5G session context to a 6G session context, including mapping 5G QoS flow identifiers to 6G QoS flow identifiers and mapping 5G QoS parameters to 6G QoS parameters; the SMF provides the 5G session context and 6G session context to the UE for use in 5GS and subsequently when moving to a 6GS system (if applicable).
[0337] Alternatively, in other implementations, the fourth network element can generate a session context for the first system and a session context for the second system for the session, and further carry the session contexts of the first system and the second system in the fourth message. For example, the fourth network element establishes a first system QoS flow identifier and a first system QoS parameter for the session, and maps the first system QoS flow identifier and the first system QoS parameter to a second system QoS flow identifier and the second system QoS parameter, respectively.
[0338] In some embodiments, the first system session identifier of the session includes a first information element, and / or the second system session identifier includes a first information element;
[0339] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0340] The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
[0341] For example, both 6G session ID and 5G session ID contain a first information element. When the value of this first information element in a PDU session ID is 0, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 1, it indicates that the PDU session ID is a 6G session ID. Alternatively, when the value of the first information element in a PDU session ID is 1, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 0, it indicates that the PDU session ID is a 6G session ID.
[0342] This application also proposes another session identifier allocation method. FIG11 is a schematic flowchart of a session identifier allocation method 1100 according to an embodiment of this application. This method can optionally be applied to the system shown in FIG1 or FIG2, but is not limited thereto. The method includes at least some of the following.
[0343] S1110, the sixth network element receives the fifth session request message, which carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration;
[0344] S1120, The sixth network element generates one or more of the following in the session: first system QoS flow identifier, first system QoS parameter, second system QoS flow identifier, and second system QoS parameter;
[0345] S1130. The sixth network element sends a fifth session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the first system QoS flow identifier, the first system QoS parameter, the second system QoS flow identifier, and the second system QoS parameter.
[0346] The fifth session request message may be the same as or different from the aforementioned first, second, third, or fourth session request messages, and the fifth session acceptance message may be the same as or different from the aforementioned first, second, third, or fourth session request messages.
[0347] In some implementations, the sixth network element includes a Session Management Network Element (SMF).
[0348] The aforementioned indication information used to indicate support for cross-system migration can have two possibilities: One is a session-level indication, where the AMF determines whether the current session supports cross-system migration based on the session request's DNN and / or slice identifier S-NSSAI, as well as whether the network and UE support interworking, and then indicates this to the SMF. The other is a UE-level indication, where the AMF determines whether interworking is supported based on UE and network capabilities. If supported, the AMF informs the SMF that the UE supports interworking; the SMF then determines, based on operator configuration and UE capabilities, whether to allocate a session context in the target system for the current session, including the corresponding QoS flow identifier and QoS parameters.
[0349] In some implementations, the first system includes 5GS, and the second system includes 6GS. The session request message can be a session establishment request or a session modification request, etc. For example, when the network side establishes a 5G session for the UE, the SMF establishes a corresponding 5G session context for the session; at the same time, the SMF can map the 5G session context to a 6G session context, including mapping the 5G QoS flow identifier to a 6G QoS flow identifier and mapping the 5G QoS parameters to 6G QoS parameters; the network side provides the 5G session context mapping and the 6G session context to the UE for use in 5GS and subsequently when moving to a 6GS system (if applicable).
[0350] The sixth network element can further register session-related information, which includes the first system session identifier and the second system session identifier. For example, the sixth network element registers this session-related information with the UDM.
[0351] In some embodiments, the first system session identifier of the session includes a first information element, and / or the second system session identifier includes a first information element;
[0352] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0353] The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
[0354] For example, both 6G session ID and 5G session ID contain a first information element. When the value of this first information element in a PDU session ID is 0, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 1, it indicates that the PDU session ID is a 6G session ID. Alternatively, when the value of the first information element in a PDU session ID is 1, it indicates that the PDU session ID is a 5G session ID; when the value of the first information element is 0, it indicates that the PDU session ID is a 6G session ID.
[0355] The following detailed description, in conjunction with the accompanying drawings, provides specific embodiments.
[0356] In the various embodiments described below, when a UE requests to establish or modify a 5G PDU session (hereinafter referred to as a 5G session), the core network can determine whether it is necessary to allocate a corresponding 6G PDU session ID (hereinafter referred to as a 6G session ID) and the corresponding 6G QoS parameters for this session based on information such as UE capabilities (e.g., whether it supports 6GS and 5GS interoperability), QoS profile, and operator policies. The core network element allocates the 6G session ID for the session and associates the 5G session ID with the 6G session ID.
[0357] The 6G session ID assigned by the core network can be unique within the network or unique within the UE. The 6G session ID is primarily used to identify a 6G session, which is mainly used for data transmission (or packet exchange) between the data network (application server) and the UE. To ensure that the 6G session ID can uniquely identify a UE's 6G session, it can be assigned by the mobility management network element, the unified data management network element (the network element that manages user subscription information and related data), or a new network element used for ID allocation.
[0358] Example 4:
[0359] In this embodiment, in order to support network interoperability between 5GS and 6GS, during the process of establishing or modifying a 5G session, the AMF can assign a 6G session ID to the UE based on the UE's capabilities, so that the UE can quickly migrate the session when it moves from 5GS to 6GS.
[0360] Figure 12 is a flowchart of the implementation according to Embodiment 4 of this application, including the following steps:
[0361] S1201, The UE requests to establish a 5G session by sending a third session request message to a fourth network element, such as a session establishment request to the core network mobility management element (AMF). This session establishment request includes one or more of the following parameters:
[0362] (1) 5G Session ID;
[0363] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0364] (3) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0365] (4) Interworking with 6GS indication: This indicates that the session needs to support session continuity across systems (5GS and 6GS). This indication can be found in the NAS message, specifically in the corresponding AMF.
[0366] S1202, the AMF selects a suitable SMF based on the UE's capabilities, UE's subscription data, requested DNN, slice identifier, UE location, and access type. If the UE's capabilities indicate support for 6G NAS, or if the UE includes an "Interworking with 6GS" indication in its session establishment request, the AMF selects a network element that combines 5G SMF and 6G SM (SMF+6G SM), or in other words, a session management network element that can be used for both 5GS and 6GS. Furthermore, the AMF assigns a 6G session ID to the 5G session requested by the UE and associates this 6G session ID with the 5G session ID.
[0367] S1203, AMF sends a fourth session request message to the fifth network element, for example, sending a session establishment request to SMF. The session establishment request includes one or more of the following parameters:
[0368] (1) UE identification information, such as SUPI;
[0369] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0370] (3) Slice identifier: used to indicate which network slice the session is established on;
[0371] (4) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0372] (5) Indication information for indicating support interworking with 6GS: The AMF determines this based on one or more of the UE’s capabilities (e.g., whether it supports 6G NAS) and UE subscription data (e.g., core network type restrictions on 6GC, support for interworking with 6GS on some DNNs, slices).
[0373] (6) Indication information for indicating the type of network interworking: The AMF indicates whether the network supports network interworking with an interface between the AMF and the 6G MM or network interworking without an interface between the AMF and the 6G MM based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM).
[0374] (7) 5G Session ID;
[0375] (8) 6G Session ID: Identification information assigned by 6G MM to this 6G session.
[0376] If the UE's subscription message changes and the session no longer supports interworking with 6GS, the AMF needs to notify the SMF.
[0377] After receiving the session establishment request, S1204, the SMF retrieves session-related subscription data from the UDM or local storage to establish a 5G session context, including establishing multiple 5G QoS flow IDs and 5G QoS parameters. If the session request message received from the AMF contains a 6G session ID and / or indications supporting interworking with 6GS, the SMF needs to map the 5G QoS parameters to 6G QoS parameters, including session-level QoS parameters and QoS flow-level parameters. The SMF registers session-related information with the UDM, which mainly includes one or more of the following:
[0378] (1) UE identification information;
[0379] (2) Serving SMF ID and / or FQDN;
[0380] (3) The core network type (CN type) corresponding to the service SMF indicates that the service SMF is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0381] (4) UE address information assigned to the UE for this 5G session, such as the UE IP address;
[0382] (5) 5G Session ID;
[0383] (6) 6G Session ID.
[0384] S1205, SMF selects a suitable UPF to establish an N4 session and configures N4 rules for the UPF.
[0385] S1206. SMF sends a fourth session accept message to AMF, for example, a session establishment accept message to AMF, which contains one or more of the following parameters:
[0386] (1) 6G Session ID, which is included if interoperability with 6GS networks is supported;
[0387] (2) 5G Session ID;
[0388] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include: 5G session ID, 6G session ID, QoS flow ID, QoS profiles, and QoS profiles containing 5G QoS parameters.
[0389] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0390] a) 5G Session ID;
[0391] b. 6G Session ID;
[0392] c. 5G QoS parameters, including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR;
[0393] d. 6G QoS parameters or mapped 6G QoS parameters;
[0394] e. Multiple 5G QoS flow IDs included in a 5G session;
[0395] f. Multiple 6G QoS flow IDs (or mapped 6G QoS flow IDs);
[0396] g. UE address information, such as IP address;
[0397] h. Indication information used to indicate support for interworking with 6GS: This indicates support for interoperability with 6GS in the current session, or support for migrating the current session to 6GS. Alternatively, it indicates that the UE supports interoperability with 6GS.
[0398] i. Indication information used to indicate that the network supports interworking with an interface between AMF and 6G MM, or indication information used to indicate that the network supports interworking without an interface between AMF and 6G MM.
[0399] In step S1207, the AMF sends the SM container containing the information sent to the access network device (as included in step S1206) to the access network device, and also sends the SM container containing the information sent to the UE to the UE via a session establishment acceptance message through the access network device. The UE can determine the network capability based on the received 6G QoS parameters or the mapped 6G QoS parameters, which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 6GS, which indicates that the network supports 5GS and 6GS interworking.
[0400] Optionally, when a UE moves from 5GS to 6GS, the 6G session ID assigned to this PDU session by the core network can be directly used to migrate this PDU session to 6GS. For example, a session establishment request can be initiated in 6GS carrying the 6G session ID, and indicating that the session establishment request type is an existing session.
[0401] Example 5:
[0402] In this embodiment, in order to support network interoperability between 5GS and 6GS, during the process of establishing a modified 5G session, the SMF can determine the request AMF (or 6G MM) to allocate a 6G session ID for the UE based on the UE's capabilities and / or session-related subscription messages, so that the UE can quickly perform session migration when it moves from 5GS to 6GS.
[0403] Figure 13 is a flowchart of the implementation according to Embodiment 5 of this application, including the following steps:
[0404] S1301, The UE requests to establish a 5G session by sending a third session request message to the fourth network element, such as sending a session establishment request to the core network AMF. This session establishment request includes one or more of the following parameters:
[0405] (1) 5G Session ID;
[0406] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0407] (3) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0408] (4) Interworking with 6GS indication: This indicates that the session needs to support session continuity across systems (5GS and 6GS). This indication can be found in the NAS message, specifically in the corresponding AMF.
[0409] Among the parameters mentioned above, the indication information used to indicate that the session needs to support network interworking with 6GS can be contained in the N1 SM container, which is transparent to the AMF.
[0410] S1302. The AMF selects a suitable SMF based on UE capabilities, UE subscription data, requested DNN, slice identifier, UE location, and access type. If the UE capability indicates support for 6G NAS, or if the UE includes an "Interworking with 6GS" indication in the session establishment request, the AMF selects a network element that combines 5G SMF and 6G SM (SMF+6G SM), or in other words, a session management network element that can be used for both 5GS and 6GS. The AMF sends a fourth session request message to the fifth network element, for example, a session establishment request to the SMF, which includes one or more of the following parameters:
[0411] (1) UE identification information, such as SUPI;
[0412] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0413] (3) Slice identifier: used to indicate which network slice the session is established on;
[0414] (4) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0415] (5) Indication information for indicating support interworking with 6GS: The AMF determines this based on one or more of the UE’s capabilities (e.g., whether it supports 6G NAS) and UE subscription data (e.g., core network type restrictions on 6GC, support for interworking with 6GS on some DNNs, slices).
[0416] (6) Indication information for indicating the type of network interworking: The AMF indicates whether the network supports network interworking with an interface between the AMF and the 6G MM or network interworking without an interface between the AMF and the 6G MM based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM).
[0417] (7) 5G Session ID.
[0418] S1303, the SMF determines whether to accept the UE's session establishment request based on the UE's subscription data and network configuration. The SMF can determine whether to allocate a corresponding 6G session ID to the UE based on the AMF's indication (Support Interworking with 6GS), the UE's indication (Interworking with 6GS indication), the UE's subscription data (whether the current data network DNN and network slice S-NSSAI support interworking with 6GS), and operator policies. The SMF establishes a 5G session context, including establishing multiple 5G QoS flow IDs and 5G QoS parameters; and maps the 5G session context to a 6G session context, including mapping 5G QoS flow IDs to 6G QoS flow IDs and 5G QoS parameters to 6G QoS parameters. The SMF can request the Mobility Management Element (MM) to allocate a corresponding 6G session ID for the currently requested 5G session. This MM can be the AMF in step S1301, a 6G MM, or other network elements capable of allocating session identification information to the UE. This session ID allocation request includes the following information:
[0419] (1) List of PDU session IDs: Contains one or more 5G session IDs;
[0420] (2) UE identification information;
[0421] (3) Serving SMF ID and / or FQDN;
[0422] (4) Interworking with 6GS indication: This is used to instruct the MM to assign the 6G session ID corresponding to the 5G session.
[0423] S1304, MM assigns a 6G session ID to the 5G session provided by SMF. Specifically, the 6G session ID allocation response message includes the following:
[0424] (1) UE identification information;
[0425] (2) 5G Session ID;
[0426] (3) The corresponding 6G session ID; This response message may contain multiple pairs of 5G session IDs and their corresponding 6G session IDs;
[0427] After receiving the session establishment request, S1305 and SMF retrieve session-related subscription data from UDM or locally to establish a 5G session context. If the session request message received from AMF contains a 6G session ID and / or indications of support for interworking with 6GS, then SMF needs to map 5G QoS parameters to 6G QoS parameters, including session-level QoS parameters and QoS flow-level parameters. SMF registers session-related information with UDM, which mainly includes:
[0428] (1) UE identification information;
[0429] (2) Serving SMF ID and / or FQDN;
[0430] (3) The core network type (CN type) corresponding to the service SMF indicates that the service SMF is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0431] (4) UE address information assigned to the UE for this 5G session, such as the UE IP address;
[0432] (5) 5G Session ID;
[0433] (6) 6G Session ID.
[0434] S1306. SMF selects a suitable UPF to establish an N4 session and configures N4 rules for the UPF.
[0435] S1307. SMF sends a Session 4 Accept message to AMF, for example, sending a Session Establish Accept message to AMF. This Session Establish Accept message contains one or more of the following parameters:
[0436] (1) 6G Session ID, which is included if interoperability with 6GS networks is supported;
[0437] (2) 5G Session ID;
[0438] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include: 5G session ID, 6G session ID, 5G QoS flow ID, and QoS profiles, which contain 5G QoS parameters.
[0439] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0440] a) 5G Session ID;
[0441] b. 6G Session ID;
[0442] c. 5G QoS parameters, including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR.
[0443] d. 6G QoS parameters or mapped 6G QoS parameters;
[0444] e. Multiple 5G QoS flow IDs included in a 5G session;
[0445] f. Multiple 6G QoS flow IDs (or mapped 6G QoS flow IDs);
[0446] g. UE address information, such as IP address;
[0447] h. Indication information used to indicate support for interworking with 6GS: This indicates support for interoperability with 6GS in the current session, or support for migrating the current session to 6GS. Alternatively, it indicates that the UE supports interoperability with 6GS.
[0448] i. Indication information used to indicate the type of network interoperability: for example, indication information used to indicate that the network supports network interoperability with an interface between AMF and 6G MM, or indication information used to indicate that the network supports network interoperability without an interface between AMF and 6G MM.
[0449] In step S1308, the AMF sends the SM container containing the information sent to the access network device (as included in step S1307) to the access network device, and also sends the SM container containing the information sent to the UE to the UE via a session establishment acceptance message through the access network device. The UE can determine the network capability based on the received 6G QoS parameters or the mapped 6G QoS parameters, which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 6GS, which indicates that the network supports 5GS and 6GS interworking.
[0450] Optionally, when a UE moves from 5GS to 6GS, the 6G session ID assigned to this PDU session by the core network can be directly used to migrate this PDU session to 6GS. For example, a session establishment request can be initiated in 6GS carrying the 6G session ID, and indicating that the session establishment request type is an existing session.
[0451] Example 6:
[0452] In this embodiment, in order to support network interoperability between 5GS and 6GS, during the process of establishing a 5G connection, the SMF can determine the request UDM (or the network element used for UE subscription data management in 6G) to allocate a 6G session ID to the UE based on the UE's capabilities and / or session-related subscription messages. This facilitates session migration when the UE moves from 5GS to 6GS, thereby ensuring session continuity across systems.
[0453] Figure 14 is a flowchart of the implementation according to Embodiment Six of this application, including the following steps:
[0454] S1401, The UE requests to establish a 5G session by sending a third session request message to the fourth network element, such as sending a session establishment request to the core network AMF. This session establishment request includes one or more of the following parameters:
[0455] (1) 5G Session ID;
[0456] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0457] (3) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0458] (4) Interworking with 6GS indication: This indicates that the session needs to support session continuity across systems (5GS and 6GS). This indication can be found in the NAS message, specifically in the corresponding AMF.
[0459] Among the parameters mentioned above, the indication information used to indicate that the session needs to support network interworking with 6GS can be contained in the N1 SM container, which is transparent to the AMF.
[0460] S1402, the AMF selects a suitable SMF based on UE capabilities, UE subscription data, requested DNN, slice identifier, UE location, and access type. If the UE capability indicates support for 6G NAS, or if the UE includes an "Interworking with 6GS" indication in its session establishment request, the AMF selects a network element that combines 5G SMF and 6G SM (SMF+6G SM), or in other words, a session management network element that can be used for both 5GS and 6GS. The AMF sends a fourth session request message to the fifth network element, for example, a session establishment request to the SMF, which includes one or more of the following parameters:
[0461] (1) UE identification information, such as SUPI;
[0462] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0463] (3) Slice identifier: used to indicate which network slice the session is established on;
[0464] (4) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0465] (5) Indication information for indicating support interworking with 6GS: AMF determines this based on the UE’s capabilities (e.g., whether it supports 6G NAS) and / or the UE’s subscription data (e.g., core network type restrictions on 6GC, support for interworking with 6GS on some DNNs, slices).
[0466] (6) Indication information for indicating the type of network interworking: The AMF indicates whether the network supports network interworking with an interface between the AMF and the 6G MM or network interworking without an interface between the AMF and the 6G MM based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM).
[0467] (7) 5G Session ID.
[0468] After receiving the session establishment request, S1403, the SMF retrieves session-related subscription data from the UDM or local storage to establish a 5G session context, including multiple 5G QoS flow IDs and 5G QoS parameters. The SMF can determine whether to allocate a corresponding 6G session ID to the UE based on the AMF's indication (Support Interworking with 6GS), the UE's indication (Interworking with 6GS indication), the UE's subscription data (whether the current data network DNN and network slice S-NSSAI support interworking with 6GS), and operator policies. If necessary, the SMF maps the 5G session context to a 6G session context, including mapping 5G QoS flow IDs to 6G QoS flow IDs and 5G QoS parameters to 6G QoS parameters, including session-level QoS parameters and QoS flow-level parameters. Furthermore, the SMF needs to request the UDM to allocate a 6G session ID. The SMF registers session-related information with the UDM, which mainly includes:
[0469] (1) UE identification information;
[0470] (2) Serving SMF ID and / or FQDN;
[0471] (3) The core network type (CN type) corresponding to the service SMF indicates that the service SMF is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0472] (4) UE address information assigned to the UE for this 5G session, such as the UE IP address;
[0473] (5) 5G Session ID;
[0474] (6) Interworking with 6GS indication: This indicates that the network needs to assign a corresponding 6G session ID to this PDU session.
[0475] S1404 and UDM assign a 6G session ID to the 5G session and send the assigned 6G session ID to SMF.
[0476] S1405. SMF selects a suitable UPF to establish an N4 session and configures N4 rules for the UPF.
[0477] S1406. SMF sends a fourth session accept message to AMF, for example, a session establishment accept message to AMF, which contains one or more of the following parameters:
[0478] (1) 6G Session ID, which is included if interoperability with 6GS networks is supported;
[0479] (2) 5G Session ID;
[0480] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include: 5G session ID, 6G session ID, 5G QoS flow ID, and QoS profiles, which contain 5G QoS parameters.
[0481] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0482] a) 5G Session ID;
[0483] b. 6G Session ID;
[0484] c. 5G QoS parameters, including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR.
[0485] d. 6G QoS parameters or mapped 6G QoS parameters;
[0486] e. Multiple 5G QoS flow IDs included in a 5G session;
[0487] f. Multiple 6G QoS flow IDs (or mapped 6G QoS flow IDs);
[0488] g. UE address information, such as IP address;
[0489] h. Indication information used to indicate support for interworking with 6GS: This indicates support for interoperability with 6GS in the current session, or support for migrating the current session to 6GS. Alternatively, it indicates that the UE supports interoperability with 6GS.
[0490] i. Indication information used to indicate the type of network interoperability: for example, indication information used to indicate that the network supports network interoperability with an interface between AMF and 6G MM, or indication information used to indicate that the network supports network interoperability without an interface between AMF and 6G MM.
[0491] In step S1407, the AMF sends the SM container containing the information sent to the access network device, which was included in step S1206, to the access network device, and also sends the SM container containing the information sent to the UE to the UE via a session establishment acceptance message through the access network device. The UE can determine the network capability based on the received 6G QoS parameters or the mapped 6G QoS parameters, which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 6GS, which indicates that the network supports 5GS and 6GS interworking.
[0492] Optionally, when a UE moves from 5GS to 6GS, the 6G session ID assigned to this PDU session by the core network can be directly used to migrate this PDU session to 6GS. For example, a session establishment request can be initiated in 6GS carrying the 6G session ID, and indicating that the session establishment request type is an existing session.
[0493] Example 7:
[0494] In this embodiment, during the establishment or modification of a 5G session, the SMF can assign a corresponding 6G session ID to the 5G session. At this time, the SMF can map the 5G session ID to a 6G session ID using a certain mapping rule, thereby ensuring that the 6G session ID is unique within the UE. For example, this can be achieved by adding specific bits, as described in Embodiment 8.
[0495] Figure 15 is a flowchart of the implementation according to Embodiment 7 of this application. As shown in Figure 15, the process by which the SMF allocates the corresponding 6G session ID for the 5G session is as follows:
[0496] S1501, The UE requests to establish a 5G session by sending a third session request message to the fourth network element, such as sending a session establishment request to the core network AMF. This session establishment request includes one or more of the following parameters:
[0497] (1) 5G Session ID;
[0498] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0499] (3) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0500] (4) Interworking with 6GS indication: This indicates that the session needs to support session continuity across systems (5GS and 6GS). This indication can be found in the NAS message, specifically in the corresponding AMF.
[0501] Among the parameters mentioned above, the indication information used to indicate that the session needs to support network interworking with 6GS can be contained in the N1 SM container, which is transparent to the AMF.
[0502] S1502, the AMF selects a suitable SMF based on UE capabilities, UE subscription data, requested DNN, slice identifier, UE location, and access type. If the UE capability indicates support for 6G NAS, or if the UE includes an "Interworking with 6GS" indication in the session establishment request, the AMF selects a network element that combines 5G SMF and 6G SM (SMF+6G SM), or in other words, a session management network element that can be used for both 5GS and 6GS. The AMF sends a fourth session request message to the fifth network element, for example, a session establishment request to the SMF, which includes one or more of the following parameters:
[0503] (1) UE identification information, such as SUPI;
[0504] (2) Type of session request: For example, indicating whether the session request is an initial request, an existing session, an urgent session, etc.;
[0505] (3) Slice identifier: used to indicate which network slice the session is established on;
[0506] (4) Requesting DNN: Instructs the UE to request the data network with which it interacts with data, or in other words, instructs the UE to request the application server that provides data services to it.
[0507] (5) Indication information for indicating support interworking with 6GS: AMF determines this based on the UE’s capabilities (e.g., whether it supports 6G NAS) and / or the UE’s subscription data (e.g., core network type restrictions on 6GC, support for interworking with 6GS on some DNNs, slices).
[0508] (6) Indication information for indicating the type of network interworking: The AMF indicates whether the network supports network interworking with an interface between the AMF and the 6G MM or network interworking without an interface between the AMF and the 6G MM based on the network configuration (e.g., whether there is an interface between the AMF and the 6G MM).
[0509] (7) 5G Session ID.
[0510] After receiving a session establishment request, S1503 and SMF retrieve session-related subscription data from UDM or local storage, and establish a 5G session context, including establishing multiple 5G QoS flow IDs and 5G QoS parameters. Based on AMF's indication (Support Interworking with 6GS), and / or UE's indication (Interworking with 6GS indication), and / or UE's subscription data (whether the current data network DNN and network slice S-NSSAI support interworking with 6GS), and / or operator policies, SMF determines whether to allocate a corresponding 6G session ID for the 5G session. If necessary, SMF allocates a corresponding 6G session ID and a mapped 6G session context (including mapped 6G QoS flow IDs and mapped 6G QoS parameters) for the currently requested 5G session.
[0511] S1504 and SMF register session-related information with UDM. This session-related information mainly includes:
[0512] (1) UE identification information;
[0513] (2) Serving SMF ID and / or FQDN;
[0514] (3) The core network type (CN type) corresponding to the service SMF indicates that the service SMF is the session management network element corresponding to the UE in 6GS and / or 5GS;
[0515] (4) UE address information assigned to the UE for this 5G session, such as the UE IP address;
[0516] (5) 5G Session ID;
[0517] (6) 6G Session ID.
[0518] S1505, SMF selects a suitable UPF to establish an N4 session and configures N4 rules for the UPF.
[0519] S1506. SMF sends a fourth session accept message to AMF, for example, a session establishment accept message to AMF, which contains one or more of the following parameters:
[0520] (1) 6G Session ID, which is included if interoperability with 6GS networks is supported;
[0521] (2) 5G Session ID;
[0522] (3) Information sent to the access network device, such as information that can be placed in an SM container, which may include: 5G session ID, 6G session ID, 5G QoS flow ID, and QoS profiles, which contain 5G QoS parameters.
[0523] (4) Information sent to the UE, such as information that can be placed in an SM container, which may include one or more of the following:
[0524] a) 5G Session ID;
[0525] b. 6G Session ID;
[0526] c. 5G QoS parameters, including QoS flow-level QoS parameters such as PDB, PER, GFBR, etc.; and also session-level QoS parameters such as Session-AMBR;
[0527] d. 6G QoS parameters or mapped 6G QoS parameters;
[0528] e. Multiple 5G QoS flow IDs included in a 5G session;
[0529] f. Multiple 6G QoS flow IDs (or mapped 6G QoS flow IDs);
[0530] g. UE address information, such as IP address;
[0531] h. Indication information used to indicate support for interworking with 6GS: This indicates support for interoperability with 6GS in the current session, or support for migrating the current session to 6GS. Alternatively, it indicates that the UE supports interoperability with 6GS.
[0532] i. Indication information used to indicate the type of network interoperability: for example, indication information used to indicate that the network supports network interoperability with an interface between AMF and 6G MM, or indication information used to indicate that the network supports network interoperability without an interface between AMF and 6G MM.
[0533] In step S1507, the AMF sends the SM container containing the information sent to the access network device (as included in step S1206) to the access network device, and also sends the SM container containing the information sent to the UE to the UE via a session establishment acceptance message through the access network device. The UE can determine the network capability based on the received 6G QoS parameters or the mapped 6G QoS parameters, which indicates that the network supports 5GS and 6GS interworking; or the UE can confirm the network capability through indication information such as support interworking with 6GS, which indicates that the network supports 5GS and 6GS interworking.
[0534] Optionally, when a UE moves from 5GS to 6GS, the 6G session ID assigned to this PDU session by the core network can be directly used to migrate this PDU session to 6GS. For example, a session establishment request can be initiated in 6GS carrying the 6G session ID, and indicating that the session establishment request type is an existing session.
[0535] Example 8:
[0536] This embodiment describes the mapping method from 5G session ID to 6G session ID, which is applicable to embodiments one through seven above.
[0537] Figure 16A is a schematic diagram of a 5G session ID according to Embodiment 8 of this application. As shown in Figure 16A, the 5G session ID consists of two parts: the first part is the IE identifier, which indicates that this IE is a 5G session ID; the second part is the IE value. Figure 16B is a schematic diagram of a 6G session ID according to Embodiment 8 of this application. As shown in Figure 16B, when mapping a 5G session ID to a 6G session ID, the IE identifier (i.e., the first part mentioned above) can be changed to indicate that the IE is a 6G session ID.
[0538] Figure 16C is a schematic diagram of another 6G session ID according to Embodiment 8 of this application. As shown in Figure 16C, when mapping a 5G session ID to a 6G session ID, a new bit (new IE) can be added to indicate that the current ID is a 6G session ID. For example, when the session ID is used in 5GS, the value of the new IE can be set to 0; when mapped to a 6G session ID, the value of the new IE can be set to 1. Alternatively, when the session ID is used in 5GS, the value of the new IE can be set to 1; when mapped to a 6G session ID, the value of the new IE can be set to 0.
[0539] Figure 17 is a schematic block diagram of a terminal device 1700 according to an embodiment of the present application. The terminal device 1700 may include:
[0540] The first transceiver module 1710 is used to send a first session request message to a first network element, the first session request message carrying a first system session identifier of the session; and to receive a first session acceptance message sent by the first network element, the first session acceptance message carrying a second system session identifier of the session.
[0541] In some implementations, the first session receive message also carries the second system QoS flow identifier, second system QoS parameters, and...
[0542] The first system QoS flow identifier and the first system QoS parameters; where...
[0543] There is a mapping relationship between the QoS flow identifier of the second system and the QoS flow identifier of the first system;
[0544] There is a mapping relationship between the QoS parameters of the second system and the QoS parameters of the first system.
[0545] Figure 18 is a schematic block diagram of a terminal device 1800 according to an embodiment of the present application. The terminal device 1800 further includes a first processing module 1820, used to perform session migration using a first system session identifier when the terminal device moves from a second system to a first system.
[0546] In some implementations, the first network element includes a mobility management network element.
[0547] In some implementations, the first system session identifier of the session contains a first information element, and / or, the second system session identifier contains a first information element;
[0548] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0549] The first information unit of the second system session identifier takes the second value, which is used to identify the second system session identifier.
[0550] Terminal devices 1700 and 1800 in this application embodiment can implement the corresponding functions of the terminal devices in the aforementioned method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in terminal devices 1700 and 1800 can be found in the corresponding descriptions in the above 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 terminal devices 1700 and 1800 in 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.).
[0551] Figure 19 is a schematic block diagram of a second network element 1900 according to an embodiment of the present application. The second network element 1900 may include:
[0552] The second transceiver module 1910 is used to receive a first message, which carries a first system session identifier of the session; and to send a second message, which carries a second system session identifier of the session.
[0553] The second processing module 1920 is used to assign a second system session identifier to the session.
[0554] In some implementations, the second transceiver module 1910 is further configured to:
[0555] Send a second session request message to the third network element. The second session request message carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration.
[0556] The system receives a second session acceptance message sent by a third network element. The second session acceptance message carries one or more of the following: a first system session identifier, a second system session identifier, a second system QoS flow identifier for the session, a second system QoS parameter for the session, a first system QoS flow identifier for the session, and a first system QoS parameter for the session.
[0557] In some implementations, the second message also carries one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
[0558] In some implementations, the second processing module 1920 is also configured to associate the first system session identifier with the second system session identifier.
[0559] In some implementations, the second network element includes a mobility management network element, a session management network element, or a user data management network element.
[0560] In some implementations, the third network element includes a session management network element co-located in the first and second systems.
[0561] In some implementations, the first system session identifier of the session contains a first information element, and / or, the second system session identifier contains a first information element;
[0562] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0563] The first information unit of the second system session identifier takes the second value, which is used to identify the second system session identifier.
[0564] The second network element 1900 in this application embodiment can realize the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the second network element 1900 can be found in the corresponding descriptions in the above 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 second network element 1900 of the 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.).
[0565] Figure 20 is a schematic block diagram of a third network element 2000 according to an embodiment of the present application. The third network element 2000 may include:
[0566] The third transceiver module 2010 is used to receive a second session request message, which carries a first system session identifier of the session or indication information for indicating support for cross-system migration; and to send a second session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0567] The third processing module 2020 is used to generate one or more of the following for the session: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
[0568] In some implementations, the third processing module 2020 is also used to register session-related information, which includes a first system session identifier and a second system session identifier.
[0569] In some implementations, the third network element includes a session management network element co-located in the first and second systems.
[0570] In some implementations, the first system session identifier of the session contains a first information element, and / or, the second system session identifier contains a first information element;
[0571] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0572] The first information unit of the second system session identifier takes the second value, which is used to identify the second system session identifier.
[0573] The third network element 2000 in this application embodiment can realize the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the third network element 2000 can be found in the corresponding descriptions in the above 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 third network element 2000 of the 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.).
[0574] Figure 21 is a schematic block diagram of a terminal device 2100 according to an embodiment of the present application. The terminal device 2100 may include:
[0575] The fourth transceiver module 2110 is used to send a third session request message to the fourth network element, the third session request message carrying the first system session identifier of the session; and to receive a third session acceptance message sent by the fourth network element, the third session acceptance message carrying the first system session identifier and the second system session identifier.
[0576] In some implementations, the third session acceptance message also carries the session's first system QoS flow identifier, first system QoS parameters, second system QoS flow identifier, and second system QoS parameters; wherein,
[0577] There is a mapping relationship between the QoS flow identifier of the first system and the QoS flow identifier of the second system;
[0578] There is a mapping relationship between the QoS parameters of the first system and the QoS parameters of the second system.
[0579] Figure 22 is a schematic block diagram of a terminal device 2200 according to an embodiment of the present application. The terminal device 2200 further includes a fourth processing module 2220, used to perform session migration using a second system session identifier when the terminal device moves from a first system to a second system.
[0580] In some implementations, the third session request message also carries indication information to indicate support for cross-system migration.
[0581] In some implementations, the fourth network element includes a session management network element.
[0582] In some implementations, the first system session identifier of the session contains a first information element, and / or, the second system session identifier contains a first information element;
[0583] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0584] The first information unit of the second system session identifier takes the second value, which is used to identify the second system session identifier.
[0585] The terminal devices 2100 and 2200 of this application embodiment can implement the corresponding functions of the terminal devices in the foregoing method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in terminal devices 2100 and 2200 can be found in the corresponding descriptions in the above 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 terminal devices 2100 and 2200 of the application embodiments can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).
[0586] Figure 23 is a schematic block diagram of a fourth network element 2300 according to an embodiment of the present application. The fourth network element 2300 may include:
[0587] The fifth transceiver module 2310 is used to receive a third message, which carries a first system session identifier of the session; and to send a fourth message, which carries the first system session identifier and the second system session identifier.
[0588] The fifth processing module 2320 is used to assign a second system session identifier to the session and associate the first system session identifier with the second system session identifier.
[0589] In some implementations, the fifth transceiver module 2310 is further configured to:
[0590] Send a fourth session request message to the fifth network element. The fourth session request message carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration.
[0591] The system receives a fourth session accept message sent by the fifth network element. The fourth session accept message carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
[0592] In some embodiments, the fifth processing module 2320 is further configured to:
[0593] One or more of the following: the first system QoS flow identifier, the first system QoS parameter, the second system QoS flow identifier, and the second system QoS parameter.
[0594] In some implementations, the fourth message also carries one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
[0595] In some implementations, the fifth processing module 2320 is also used to associate the first system session identifier with the second system session identifier.
[0596] In some implementations, the third message also carries indication information for supporting cross-system migration.
[0597] In some implementations, the fourth network element includes a mobility management network element, a session management network element, or a user data management network element.
[0598] In some implementations, the fifth network element includes a session management network element.
[0599] In some implementations, the first system session identifier of the session contains a first information element, and / or, the second system session identifier contains a first information element;
[0600] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0601] The first information unit of the second system session identifier takes the second value, which is used to identify the second system session identifier.
[0602] The fourth network element 2300 in this application embodiment can realize the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the fourth network element 2300 can be found in the corresponding descriptions in the above 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 fourth network element 2300 of the 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.).
[0603] Figure 24 is a schematic block diagram of a sixth network element 2400 according to an embodiment of the present application. The sixth network element 2400 may include:
[0604] The sixth transceiver module 2410 is configured to receive a fifth session request message, which carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration; and to send a fifth session acceptance message, which carries one or more of the following: a first system session identifier, a second system session identifier, a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
[0605] The sixth processing module 2420 is used to generate one or more of the following for a session: a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
[0606] In some implementations, the sixth processing module 2420 is also used to register session-related information, which includes a first system session identifier and a second system session identifier.
[0607] In some implementations, the sixth network element is the session management network element.
[0608] In some implementations, the first system session identifier of the session contains a first information element, and / or, the second system session identifier contains a first information element;
[0609] The first information unit of the first system session identifier takes the first value, which is used to identify the first system session identifier;
[0610] The first information unit of the second system session identifier takes the second value, which is used to identify the second system session identifier.
[0611] The sixth network element 2400 in this application embodiment can realize the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the sixth network element 2400 can be found in the corresponding descriptions in the above 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 sixth network element 2400 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.).
[0612] Figure 25 is a schematic structural diagram of a communication device 2500 according to an embodiment of this application. The communication device 2500 includes a processor 2510, which can call and run computer programs from memory to enable the communication device 2500 to implement the methods in the embodiments of this application.
[0613] In one embodiment, the communication device 2500 may further include a memory 2520. The processor 2510 can retrieve and run computer programs from the memory 2520 to enable the communication device 2500 to implement the methods described in the embodiments of this application.
[0614] The memory 2520 can be a separate device independent of the processor 2510, or it can be integrated into the processor 2510.
[0615] In one embodiment, the communication device 2500 may further include a transceiver 2530, and the processor 2510 may control the transceiver 2530 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.
[0616] The transceiver 2530 may include a transmitter and a receiver. The transceiver 2530 may further include an antenna, which may be one or more.
[0617] In one embodiment, the communication device 2500 may be a network device in the embodiments of this application, and the communication device 2500 may implement the corresponding processes implemented by the core network elements in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0618] In one embodiment, the communication device 2500 may be a terminal device in the embodiments of this application, and the communication device 2500 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0619] Figure 26 is a schematic structural diagram of a chip 2600 according to an embodiment of this application. The chip 2600 includes a processor 2610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0620] In one embodiment, chip 2600 may further include memory 2620. Processor 2610 can retrieve and run computer programs from memory 2620 to implement the methods executed by the terminal device or network device in this embodiment.
[0621] The memory 2620 can be a separate device independent of the processor 2610, or it can be integrated into the processor 2610.
[0622] In one embodiment, the chip 2600 may further include an input interface 2630. The processor 2610 can control the input interface 2630 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.
[0623] In one embodiment, the chip 2600 may further include an output interface 2640. The processor 2610 can control the output interface 2640 to communicate with other devices or chips; specifically, it can output information or data to other devices or chips.
[0624] In one implementation, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0625] In one implementation, the chip can be applied to the terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0626] The chips used in network equipment and terminal equipment can be the same chip or different chips.
[0627] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0628] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.
[0629] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).
[0630] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.
[0631] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
[0632] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes 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.
[0633] Those skilled in the art will 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.
[0634] The above description is merely a specific embodiment 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 scope of the technology 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
1. A session identifier allocation method, comprising: The terminal device sends a first session request message to the first network element, and the first session request message carries the first system session identifier of the session. The terminal device receives a first session acceptance message sent by the first network element, wherein the first session acceptance message carries a second system session identifier of the session.
2. The method of claim 1, wherein, The first session acceptance message also carries one or more of the following: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters; wherein, There is a mapping relationship between the second system QoS flow identifier and the first system QoS flow identifier; There is a mapping relationship between the QoS parameters of the second system and the QoS parameters of the first system.
3. The method according to claim 1 or 2 further includes, when the terminal device moves from the second system to the first system, the terminal device uses the first system session identifier of the session to perform session migration.
4. The method of any one of claims 1-3, wherein, The first network element includes a mobility management network element.
5. The method according to any one of claims 1-4, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
6. A session identifier allocation method, comprising: The second network element receives the first message, which carries the first system session identifier of the session. The second network element assigns a second system session identifier to the session; The second network element sends a second message, which carries the second system session identifier of the session.
7. The method according to claim 6, wherein after the second network element assigns a second system session identifier to the session, and before the second network element sends the second message, it further includes: The second network element sends a second session request message to the third network element. The second session request message carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration. The second network element receives a second session acceptance message sent by the third network element. The second session acceptance message carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
8. The method of claim 7, wherein, The second message also carries one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
9. The method according to any one of claims 6-8, further comprising: the second network element associating the first system session identifier with the second system session identifier.
10. The method of any one of claims 6-9, wherein, The second network element includes a mobility management network element, a session management network element, or a user data management network element.
11. The method of claim 7 or 8, wherein, The third network element includes the session management network element co-located in the first and second systems.
12. The method according to any one of claims 6-11, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
13. A session identifier allocation method, comprising: The third network element receives a second session request message, which carries a first system session identifier or indication information indicating support for cross-system migration. The third network element generates one or more of the following for the session: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters. The third network element sends a second session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
14. The method according to claim 13 further includes the third network element registering session-related information, wherein the session-related information includes the first system session identifier and the second system session identifier.
15. The method of claim 13 or 14, wherein, The third network element includes the session management network element co-located in the first and second systems.
16. The method according to any one of claims 13-15, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
17. A session identifier allocation method, comprising: The terminal device sends a third session request message to the fourth network element, the third session request message carrying the first system session identifier of the session; The terminal device receives a third session acceptance message sent by the fourth network element, the third session acceptance message carrying the first system session identifier and the second system session identifier.
18. The method of claim 17, wherein, The third session acceptance message also carries the first system QoS flow identifier, the first system QoS parameters, the second system QoS flow identifier, and the second system QoS parameters of the session; wherein... There is a mapping relationship between the first system QoS flow identifier and the second system QoS flow identifier; There is a mapping relationship between the QoS parameters of the first system and the QoS parameters of the second system.
19. The method according to claim 17 or 18, further comprising, when the terminal device moves from the first system to the second system, the terminal device using the second system session identifier of the session to perform session migration.
20. The method according to any one of claims 17-19, wherein, The third session request message also carries indication information to indicate support for cross-system migration.
21. The method according to any one of claims 17-20, wherein, The fourth network element includes the session management network element.
22. The method according to any one of claims 17-21, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
23. A session identifier allocation method, comprising: The fourth network element receives a third message, which carries the first system session identifier of the session; The fourth network element assigns a second system session identifier to the session and associates the first system session identifier with the second system session identifier; The fourth network element sends a fourth message, which carries the first system session identifier and the second system session identifier.
24. The method according to claim 23, wherein after the fourth network element assigns a second system session identifier to the session, and before the fourth network element sends the fourth message, it further includes: The fourth network element sends a fourth session request message to the fifth network element. The fourth session request message carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration. The fourth network element receives a fourth session acceptance message sent by the fifth network element. The fourth session acceptance message carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
25. The method according to claim 23, wherein after the fourth network element assigns a second system session identifier to the session, and before the fourth network element sends the fourth message, it further comprises: The fourth network element generates one or more of the following for the session: a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
26. The method according to any one of claims 23-25, wherein, The fourth message also carries one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
27. The method according to any one of claims 23-26, further comprising the fourth network element associating the first system session identifier with the second system session identifier.
28. The method according to any one of claims 23-27, wherein, The third message also carries indication information for supporting cross-system migration.
29. The method according to any one of claims 23-28, wherein, The fourth network element includes a mobility management network element, a session management network element, or a user data management network element.
30. The method according to claim 24, wherein, The fifth network element includes the session management network element co-located in the first and second systems.
31. The method according to any one of claims 23-30, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
32. A session identifier allocation method, comprising: The sixth network element receives a fifth session request message, which carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration. The sixth network element generates one or more of the following for the session: the first system QoS flow identifier, the first system QoS parameter, the second system QoS flow identifier, and the second system QoS parameter; The sixth network element sends a fifth session acceptance message, which carries one or more of the following: a first system session identifier, a second system session identifier, a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
33. The method according to claim 32 further includes the sixth network element registration session-related information, wherein the session-related information includes the first system session identifier and the second system session identifier.
34. The method according to claim 32 or 33, wherein, The sixth network element includes the session management network element co-located in the first and second systems.
35. The method according to any one of claims 32-34, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
36. A terminal device, comprising: The first transceiver module is used to send a first session request message to the first network element, wherein the first session request message carries the first system session identifier of the session. The system receives a first session acceptance message sent by the first network element, wherein the first session acceptance message carries a second system session identifier of the session.
37. The terminal device according to claim 36, wherein, The first session acceptance message also carries the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters of the session; wherein, There is a mapping relationship between the second system QoS flow identifier and the first system QoS flow identifier; There is a mapping relationship between the QoS parameters of the second system and the QoS parameters of the first system.
38. The terminal device according to claim 36 or 37 further includes a first processing module, configured to perform session migration using the first system session identifier of the session when the terminal device moves from the second system to the first system.
39. The terminal device according to any one of claims 36-38, wherein, The first network element includes a mobility management network element.
40. The terminal device according to any one of claims 36-39, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
41. A second network element, comprising: The second transceiver module is used to receive a first message, wherein the first message carries a first system session identifier of the session. Send a second message, which carries the second system session identifier of the session. The second processing module is used to assign a second system session identifier to the session.
42. The second network element according to claim 41, the second transceiver module, is further configured to: Send a second session request message to the third network element. The second session request message carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration. The system receives a second session acceptance message sent by the third network element. The second session acceptance message carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
43. The second network element according to claim 42, wherein, The second message also carries one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
44. The second network element according to any one of claims 41-43, wherein the second processing module is further configured to associate the first system session identifier with the second system session identifier.
45. The second network element according to any one of claims 41-44, wherein, The second network element includes a mobility management network element, a session management network element, or a user data management network element.
46. The second network element according to claim 42 or 43, wherein, The third network element includes the session management network element co-located in the first and second systems.
47. The second network element according to any one of claims 41-46, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
48. A third network element, comprising: The third transceiver module is used to receive a second session request message, which carries a first system session identifier for the session or indication information indicating support for cross-system migration. Send a second session acceptance message, which carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters; The third processing module is used to generate one or more of the following for the session: the second system QoS flow identifier, the second system QoS parameters, the first system QoS flow identifier, and the first system QoS parameters.
49. The third network element according to claim 48, wherein the third processing module is further configured to register session-related information, wherein the session-related information includes the first system session identifier and the second system session identifier.
50. The third network element according to claim 48 or 49, wherein, The third network element includes the session management network element co-located in the first and second systems.
51. The third network element according to any one of claims 48-50, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
52. A terminal device, comprising: The fourth transceiver module is used to send a third session request message to the fourth network element, wherein the third session request message carries the first system session identifier of the session; The system receives a third session acceptance message sent by the fourth network element, the third session acceptance message carrying the first system session identifier and the second system session identifier.
53. The terminal device according to claim 52, wherein, The third session acceptance message also carries the first system QoS flow identifier, the first system QoS parameters, the second system QoS flow identifier, and the second system QoS parameters of the session; wherein... There is a mapping relationship between the first system QoS flow identifier and the second system QoS flow identifier; There is a mapping relationship between the QoS parameters of the first system and the QoS parameters of the second system.
54. The terminal device according to claim 52 or 53 further includes a fourth processing module, configured to perform session migration using the second system session identifier of the session when the terminal device moves from the first system to the second system.
55. The terminal device according to any one of claims 52-54, wherein, The third session request message also carries indication information to indicate support for cross-system migration.
56. The terminal device according to any one of claims 52-55, wherein, The fourth network element includes the session management network element.
57. The terminal device according to any one of claims 52-56, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
58. A fourth network element, comprising: The fifth transceiver module is used to receive a third message, wherein the third message carries a first system session identifier of the session; Send a fourth message, the fourth message carrying the first system session identifier and the second system session identifier; The fifth processing module is used to assign a second system session identifier to the session and associate the first system session identifier with the second system session identifier.
59. The fourth network element according to claim 58, wherein the fifth transceiver module is further configured to: Send a fourth session request message to the fifth network element. The fourth session request message carries one or more of the following: the first system session identifier, the second system session identifier, and indication information for indicating support for cross-system migration. The system receives a fourth session acceptance message sent by the fifth network element. The fourth session acceptance message carries one or more of the following: the first system session identifier, the second system session identifier, the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
60. The fourth network element according to claim 58, wherein the fifth processing module is further configured to: The session is generated by one or more of the following: a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
61. The fourth network element according to any one of claims 58-60, wherein, The fourth message also carries one or more of the following: the second system QoS flow identifier of the session, the second system QoS parameters of the session, the first system QoS flow identifier of the session, and the first system QoS parameters of the session.
62. The fourth network element according to any one of claims 58-61, wherein the fifth processing module is further configured to associate the first system session identifier with the second system session identifier.
63. The fourth network element according to any one of claims 58-62, wherein, The third message also carries indication information for supporting cross-system migration.
64. The fourth network element according to any one of claims 58-63, wherein, The fourth network element includes a mobility management network element, a session management network element, or a user data management network element.
65. The fourth network element according to claim 59, wherein, The fifth network element includes the session management network element.
66. The fourth network element according to any one of claims 58-65, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
67. A sixth network element, comprising: The sixth transceiver module is used to receive a fifth session request message, wherein the fifth session request message carries one or more of the following: a first system session identifier, a second system session identifier, and indication information for indicating support for cross-system migration; and to send a fifth session acceptance message, wherein the fifth session acceptance message carries one or more of the following: a first system session identifier, a second system session identifier, a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter. The sixth processing module is used to generate one or more of the following for the session: a first system QoS flow identifier, a first system QoS parameter, a second system QoS flow identifier, and a second system QoS parameter.
68. The sixth network element according to claim 67, wherein the sixth processing module is further configured to register session-related information, wherein the session-related information includes the first system session identifier and the second system session identifier.
69. The sixth network element according to claim 67 or 68, wherein, The sixth network element is the session management network element.
70. The sixth network element according to any one of claims 67-69, wherein, Both the first system session identifier and the second system session identifier of the session contain a first information element; The first information unit of the first system session identifier takes the value of a first value, which is used to identify the first system session identifier; The first information unit of the second system session identifier takes the value of the second value, which is used to identify the second system session identifier.
71. A terminal device, comprising: A transceiver, a processor, and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to invoke and run the computer program stored in the memory to cause the terminal device to perform the method as described in any one of claims 1 to 5, 17 to 22.
72. A network device, comprising: A transceiver, a processor, and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to invoke and run the computer program stored in the memory to cause the network device to perform the method as described in any one of claims 6 to 16, 23 to 35.
73. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 35.
74. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as claimed in any one of claims 1 to 35.
75. A computer program product comprising computer program instructions that cause a computer to perform the method as claimed in any one of claims 1 to 35.
76. A computer program that causes a computer to perform the method as claimed in any one of claims 1 to 35.
