Inter-system mobility management method, first network element, second network element and ran

Abstract

This application discloses an inter-system mobility management method, a first network element, a second network element, and a RAN, belonging to the field of communication technology. The inter-system mobility management method of this application includes: the first network element obtaining first indication information, the first indication information being used to indicate inter-system handover or inter-system mobility; the first network element performing PDU session management operation based on the first indication information.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an inter-system mobility management method, a first network element, a second network element, and a RAN. Background Technology

[0002] In 5G mobile communication technology systems, there are scenarios where terminals need to perform inter-RAT handover or Mobility Registration Update (MRU).

[0003] In both mobility management scenarios mentioned above, the terminal needs to perform multiple signaling interactions between the Mobility Management Entity (MME) and the Access & Mobility Management Function (AMF) via the N26 interface to transmit or process mobility management-related information to complete inter-system handover or mobility registration updates. This includes mobility management-related information such as the Mobility Management context (MM context) and the Session Management context (SM context).

[0004] Thus, because the terminal needs to perform multiple signaling interactions between different network elements, the latency and network processing complexity of the terminal's inter-system handover or mobility registration update are increased. Summary of the Invention

[0005] This application provides an inter-system mobility management method, a first network element, a second network element, and a RAN, which can reduce the latency and network processing complexity of terminals performing inter-system handover or mobility registration updates.

[0006] In a first aspect, an inter-system mobility management method is provided, which is executed by a first network element. The method includes: the first network element obtaining first indication information, which is used to indicate inter-system handover or inter-system mobility; and the first network element performing PDU session management operations based on the first indication information.

[0007] Secondly, an inter-system mobility management method is provided, executed by a second network element, the method comprising: the second network element sending first indication information, the first indication information being used to instruct the execution of PDU session management.

[0008] Thirdly, an inter-system mobility management device is provided, the device comprising: an acquisition module and a processing module; the acquisition module is configured to acquire first indication information, the first indication information being used to indicate inter-system handover or inter-system mobility; the processing module is configured to perform PDU session management operations based on the aforementioned first indication information.

[0009] Fourthly, an inter-system mobility management device is provided, the device comprising: a sending module, the sending module being configured to send first indication information, the first indication information being configured to instruct the execution of PDU session management.

[0010] Fifthly, an inter-system mobility management apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0011] In a sixth aspect, a first network element is provided, the first network element including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0012] In a seventh aspect, a first network element is provided, including a processor and a communication interface, wherein the communication interface is used to acquire first indication information, the first indication information being used to indicate inter-system handover or inter-system movement, and the processor is used to perform PDU session management operations based on the aforementioned first indication information.

[0013] Eighthly, a second network element is provided, the second network element including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0014] In a ninth aspect, a second network element is provided, including a processor and a communication interface, wherein the communication interface is used to send first indication information, the first indication information being used to instruct the execution of PDU session management.

[0015] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0016] Eleventhly, a wireless communication system is provided, comprising: a first network element, a second network element, a terminal, and a network-side device, wherein the first network element can be used to perform the steps of the method described in the first aspect, and the second network element can be used to perform the steps of the method described in the second aspect.

[0017] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0018] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0019] In this embodiment, the first network element obtains first indication information, which is used to indicate inter-system handover or inter-system movement. Based on the first indication information, the first network element performs PDU session management operations. In this solution, the first network element can perform corresponding PDU session management operations through the content indicated in the first indication information, namely, inter-system handover or inter-system movement. This reduces the number of signaling interactions caused by multiple messages such as creating new PDU sessions, deleting or releasing old PDU sessions in the prior art, thereby reducing the latency and network processing complexity of the terminal performing inter-system handover or mobility registration updates. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the architecture of a communication system provided by some embodiments of this application;

[0021] Figure 2 This is a flowchart illustrating an inter-system mobility management method provided in some embodiments of this application;

[0022] Figure 3 This is a flowchart illustrating an inter-system mobility management method provided in some embodiments of this application;

[0023] Figure 4 This is a flowchart illustrating an inter-system mobility management method provided in some embodiments of this application;

[0024] Figure 5 This is a schematic diagram of signaling interaction for an inter-system mobility management method provided in some embodiments of this application;

[0025] Figure 6 This is a schematic diagram of signaling interaction for an inter-system mobility management method provided in some embodiments of this application;

[0026] Figure 7 These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0027] Figure 8These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0028] Figure 9 These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0029] Figure 10 These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0030] Figure 11 These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0031] Figure 12 These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0032] Figure 13 These are schematic diagrams of an inter-system mobility management device provided in some embodiments of this application;

[0033] Figure 14 These are schematic diagrams of the structure of a communication device provided in some embodiments of this application;

[0034] Figure 15 These are schematic diagrams of the hardware structure of a terminal provided in some embodiments of this application;

[0035] Figure 16 These are schematic diagrams of the network-side devices provided in some embodiments of this application. Detailed Implementation

[0036] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0037] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0038] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0039] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0040] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0041] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Functions (BSF), Application Functions (AF), Location Management Functions (LMF), Gateway Mobile Location Centres (GMLC), and Network Data Analytics Functions (NWDAF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0042] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0043] When the N26 interface is deployed, during inter-system handover or mobility registration update processes, multiple signaling interactions are required between the MME and AMF via the N26 interface to transmit or process mobility management-related information, such as MM context and SM context information. SM context information also needs to be transmitted or processed between the MME, AMF, and SMF+ Packet Data Network Gateway-Control plane (PGW-C). During handover from Evolved Packet System (EPS) to 5th generation System (5GS), a new PDU session and 5G SM context need to be established in the 5G network, followed by the deletion or release of 4G Public Data Network (PDN) connections and 4G EPS bearer contexts. During handover from 5GS to EPS, a new PDN connection and 4G EPS bearer context need to be established in 4G, followed by the deletion or release of 5G PDU sessions and 5G SM contexts. These processes increase latency and network processing complexity.

[0044] The following description, in conjunction with the accompanying drawings, details the inter-system mobility management method, the first network element, the second network element, and the RAN provided in this application through specific embodiments and application scenarios.

[0045] The inter-system mobility management method provided in this application can be applied to inter-system handover or inter-system mobility scenarios. One specific application scenario is handover between a 6G system (6GS) and a 5G system (5GS), and another specific application scenario is mobility between 6GS and 5GS systems. It is understood that the mobility management method provided in this application can also be applied to mobility within a 6GS system or within a 5GS system.

[0046] It is understood that the aforementioned 6GS can be a 6G system, and the aforementioned 5GS can be a 5G system; this application does not impose any restrictions.

[0047] The execution subject of the inter-system mobility management method provided in this application embodiment can be an inter-system mobility management device. Exemplarily, this inter-system mobility management device can be a communication device, or a functional component or entity within that communication device. In this application embodiment, the communication device can be a first network element, such as an SMF. The following will use the first network element as an example to executor the inter-system mobility management method provided in this application embodiment.

[0048] Figure 2 This is a flowchart illustrating an inter-system mobility management method provided in some embodiments of this application, such as... Figure 2 As shown, some embodiments of this application provide an inter-system mobility management method that may include steps 201 and 202.

[0049] Step 201: The first network element obtains the first instruction information.

[0050] In some embodiments of this application, the first indication information described above is used to indicate inter-system switching or inter-system movement.

[0051] For example, the aforementioned first instruction information may also be referred to as mobility management instruction information.

[0052] In some embodiments of this application, the first indication information mentioned above includes any one of the following: switching type indication information, movement type indication information.

[0053] In some embodiments of this application, the aforementioned switching type indication information is used to indicate that the terminal switches from the first system to the second system.

[0054] In some embodiments of this application, the aforementioned movement type indication information is used to indicate that the terminal moves from the first system to the second system.

[0055] In some embodiments of this application, the first system described above includes at least one of the following: a first radio access technology (RAT) and a first core network.

[0056] For example, the first RAT mentioned above can be 4GS, or 5GS, or 6GS.

[0057] For example, the first core network mentioned above can be 4GC, or 5GC, or 6GC.

[0058] In some embodiments of this application, the second system described above includes at least one of the following: a second RAT and a second core network.

[0059] For example, the second RAT mentioned above can be 4GS, or 5GS, or 6GS.

[0060] For example, the second core network mentioned above can be 4GC, or 5GC, or 6GC.

[0061] In some embodiments of this application, the aforementioned switching type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network.

[0062] In some embodiments of this application, the aforementioned mobility type indication information includes at least one of the following: information of a first RAT, information of a second RAT, information of a first core network, and information of a second core network.

[0063] It is understandable that the first RAT mentioned above is the source RAT, that is, the RAT currently connected to the terminal, and the second RAT mentioned above is the target RAT, that is, the terminal is about to switch to or move to the target RAT. Similarly, the first core network is the source core network, and the second core network is the target core network.

[0064] In some embodiments of this application, the first indication information mentioned above may be the information carried in the PDU session update SM context request message.

[0065] In some embodiments of this application, the aforementioned PDU session update SM context request message is a message received by the first network element from the second network element.

[0066] Optionally, in some embodiments of this application, step 201a is included before step 201 above, and step 201 can be specifically implemented by step 201b below.

[0067] Step 201a: The second network element sends the first message to the first network element.

[0068] Step 201b: The first network element receives the first message from the second network element.

[0069] In some embodiments of this application, the first message mentioned above includes the first instruction information mentioned above.

[0070] For example, the first message mentioned above is a PDU session update SM context request message.

[0071] For example, the PDU session update SM context request message may also include at least one of the following: terminal identifier, Single Network Slice Selection Assistance Information (S-NSSAI), PDU session identifier (ID), AMF ID, SMF ID, target radio access network (RAN) ID, and handover preparation indication.

[0072] For example, the terminal identifier mentioned above can be a Subscription Permanent Identifier (SUPI).

[0073] For example, the target access network mentioned above is the target RAT, or the access network corresponding to the target core network.

[0074] In one example, the aforementioned PDU session update SM context request message may also include AMF system type indication information, which indicates that the PDU session update SM context request message corresponds to the AMF system type.

[0075] For example, the first network element is SMF and the second network element is AMF.

[0076] For example, the first instruction information mentioned above can be transmitted through the Service-Based Interface (SBI) between the SMF and AMF.

[0077] In this way, the SMF can receive the first indication information sent by the AMF and perform PDU session management based on the first indication information in the case of inter-system handover or inter-system movement, thereby reducing signaling overhead or reducing processing complexity.

[0078] Step 202: The first network element performs PDU session management operations based on the first instruction information.

[0079] In some embodiments of this application, the above-described PDU session management operation includes at least one of the following:

[0080] Modify SM context information;

[0081] Select SM context information.

[0082] In some embodiments of this application, the first network element performs PDU session management operations according to the content indicated by the first instruction information, thereby completing inter-system handover or inter-system movement.

[0083] For example, the first instruction information described above can be specifically used to instruct the SMF to modify the SM context information or select the SM context information.

[0084] For example, taking the switch from 6GS to 5GS as an example, the above-mentioned modification of SM context information includes allocating 5G PDU session ID, 5G CN tunnel information, and associating 5G QoS information, etc.

[0085] In one possible example, after the first network element selects SM context information according to the first indication information, it can further modify the selected SM context information based on the first indication information. For example, it can modify, delete, or add parameter information in the SM context, or delete all SM contexts corresponding to a certain 5G PDU session ID in the SM context, or add a new 5G PDU session ID and its corresponding SM context, so as to ensure the accuracy of capability information after system handover.

[0086] The 6GC network element is upgraded from the 5GC network element, possessing both 6G and 5G capabilities. This allows the SMF to perform 6GPDU session management and 5G PDU session management locally. Therefore, the SMF can execute corresponding system PDU session management operations based on the information indicated by the first instruction.

[0087] In the inter-system mobility management method provided in this application embodiment, a first network element obtains first indication information, which is used to indicate inter-system handover or inter-system mobility; the first network element performs PDU session management operations based on the first indication information. In this solution, the first network element can perform corresponding PDU session management operations through the content indicated in the first indication information, namely inter-system handover or inter-system mobility, thereby reducing the number of signaling interactions caused by multiple messages such as creating new PDU sessions, deleting or releasing old PDU sessions in the prior art, and thus reducing the latency and network processing complexity of the terminal performing inter-system handover or mobility registration update.

[0088] Optionally, in some embodiments of this application, the inter-system mobility management method provided in this application embodiment further includes steps 301 and 302, or steps 301 and 303.

[0089] Step 301: The first network element obtains at least one of the following SM context information: first SM context information, second SM context information.

[0090] In some embodiments of this application, the first SM context and the second SM context information mentioned above are SM context information of different systems.

[0091] In some embodiments of this application, the first SM context and the second SM context information mentioned above are both SM context information stored in the first network element.

[0092] For example, the SM context mentioned above includes at least one of the following: SMF address, UPF address, 6G PDU session ID, and core network tunnel information.

[0093] For example, the SMF obtains the 6G SM context locally based on the terminal identifier and PDU session ID information in the PDU session update SM context request message.

[0094] Step 302: The first network element modifies the first SM context information to the third SM context information.

[0095] In some embodiments of this application, the aforementioned first SM context information corresponds to the first system.

[0096] In some embodiments of this application, the aforementioned third SM context information corresponds to the second system.

[0097] In one example, after receiving the first indication information, such as the switching type indication information, the SMF will obtain the SM context information corresponding to the 6G network from the local machine, i.e., the first SM context information. The SMF will modify the obtained SM context information according to the switching type indication information to obtain the SM context information corresponding to the 5G network, i.e., the third SM context information.

[0098] Step 303: The first network element selects either the first SM context information or the second SM context information.

[0099] In some embodiments of this application, the first SM context described above corresponds to the first system.

[0100] In some embodiments of this application, the second SM context described above corresponds to the second system.

[0101] In another example, after receiving the first indication information, such as the mobility type indication information, the SMF will obtain the SM context information corresponding to at least two systems locally, such as the SM context information corresponding to the 6G network and the SM context information corresponding to the 5G network, namely the first SM context information and the second SM context information mentioned above, and then select the required SM context information according to the mobility type indication information.

[0102] Understandably, in step 301, the SMF typically obtains the SM context information corresponding to the source system.

[0103] In this way, the first network element can obtain and modify the SM context information from the local SMF based on the first indication information and other information in the PDU session update context information request information. In contrast, existing technologies require the use of multiple messages such as creating a new PDU session, deleting or releasing an old PDU session, thereby reducing signaling overhead, latency and network processing complexity.

[0104] First possible implementation:

[0105] Optionally, in some embodiments of this application, when the first indication information includes switching type indication information, the inter-system mobility management method provided in this application further includes at least one of the following operations:

[0106] Operation 1: The first network element switches the RAT corresponding to the PDU session from the first RAT to the second RAT.

[0107] Operation 2: The first network element switches the core network corresponding to the PDU session from the first core network to the second core network.

[0108] For example, taking the handover type indication information as an example of indicating a handover between 6GS and 5GS systems, after receiving the handover indication information, the first network element modifies or selects the SM context information of the PDU session to switch the RAT corresponding to the PDU session from 6GS to 5GS.

[0109] For example, taking the handover type indication information as an example of indicating a handover between 6GC and 5GC systems, after receiving the handover indication information, the first network element modifies or selects the SM context information of the PDU session to switch the core network corresponding to the PDU session from 6GC to 5GC.

[0110] It is understandable that in other application scenarios, the handover type indication information can also indicate handover within 6GS or 5GS. In this case, the indication information of the source system and the target system is the same, or it can directly indicate handover or movement within the system.

[0111] In this way, SMF can use the PDU session update SM context request message to perform PDU session switching for different switching types, and perform different processing according to different switching types. This solves the problems of high latency and network processing complexity caused by the existing technology that requires the creation of a new SM context for the PDU session and the deletion of the SM context for the old PDU session when switching between systems.

[0112] The second possible implementation:

[0113] Optionally, in some embodiments of this application, when the first indication information includes switching type indication information, the inter-system mobility management method provided in this application embodiment further includes the following operation 3.

[0114] Operation 3: The first network element performs PDU session management according to the first instruction information.

[0115] Specifically, the first instruction information instructs the terminal to move to the second system, and the first network element modifies the PDU session context corresponding to the second system according to the first instruction information, or activates the PDU session corresponding to the second system and modifies the SM context.

[0116] For example, the aforementioned movement type indication information can be specifically used to indicate the MRU when moving between different systems, or when moving within a system. For example, the MRU between 6GS and 5GS systems, the MRU within the 6GS system, or the MRU within the 5GS system.

[0117] In this way, SMF can use PDU session update SM context request messages to modify and / or activate PDU sessions for different mobility types, and perform different processing according to different mobility types. This solves the problems of high latency and network processing complexity caused by the existing technology, which requires the creation of new SM contexts for PDU sessions and the deletion of SM contexts for old PDU sessions when moving between systems.

[0118] Optionally, in some embodiments of this application, the inter-system mobility management method provided in this application embodiment further includes step 401.

[0119] Step 401: The first network element sends a second message to the second network element.

[0120] In some embodiments of this application, the second message described above is used to indicate relevant information used in processing the second message.

[0121] For example, the aforementioned relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

[0122] In some embodiments of this application, the second message mentioned above includes system type indication information.

[0123] In some embodiments of this application, system type indication information is used to indicate the system type used by the second network element.

[0124] It is understandable that the first network element informs the second network element of the required system type, such as 6G or 5G, through the second message, so that the second network element can process the second message using the corresponding system type and capability information.

[0125] For example, the second message mentioned above can be a PDU session update SM context response message.

[0126] For example, the PDU session update SM context response message may also include at least one of the following: terminal identifier, S-NSSAI, PDU session ID, and N2 SM information.

[0127] For example, the N2 SM information mentioned above includes at least one of the following: QoS profile, mapping between 6G QFI and 5G QFI, and CN tunnel information.

[0128] It should be noted that since the SMF locally stores the AMF identifier, AMF system type indication information, and corresponding capability information, such as the AMF identifier, the AMF's 6G system type, 6G access and mobility management capabilities, and 5G system type, 5G access and mobility management capabilities, it can send a PDU session update SM context response message containing system type indication information to the AMF, i.e., the second message mentioned above.

[0129] Optionally, in some embodiments of this application, step 401 can be specifically implemented by step 401a, and step 401b is included after step 401.

[0130] Step 401a: The first network element sends a second message to the second network element.

[0131] Step 401b: The second network element receives the second message from the first network element.

[0132] For example, the first message mentioned above can be transmitted through the SBI interface between the SMF and AMF.

[0133] In this way, the SMF can send a PDU session update SM context response message to the AMF based on the AMF's system type information and the association information between the PDU session ID and the AMF ID, instructing the AMF to process the PDU session update SM context response message using the corresponding system type and capabilities.

[0134] The execution subject of the inter-system mobility management method provided in this application embodiment can be an inter-system mobility management device. Exemplarily, this inter-system mobility management device can be a communication device, or a functional component or entity within that communication device. In this application embodiment, the communication device can be a second network element, such as an AMF. The following will use the example of an execution subject being a second network element to executor the inter-system mobility management method provided in this application embodiment.

[0135] Figure 3 This is a flowchart illustrating an inter-system mobility management method provided in some embodiments of this application, such as... Figure 3 As shown, some embodiments of this application provide an inter-system mobility management method that may include the following step 501.

[0136] Step 501: The second network element sends the first instruction information.

[0137] In some embodiments of this application, the first indication information described above is used to indicate inter-system switching or inter-system movement.

[0138] In some embodiments of this application, the first indication information mentioned above includes any one of the following: switching type indication information, movement type indication information.

[0139] In some embodiments of this application, the aforementioned switching type indication information is used to indicate that the terminal switches from the first system to the second system.

[0140] In some embodiments of this application, the aforementioned movement type indication information is used to indicate that the terminal moves from the first system to the second system.

[0141] In some embodiments of this application, the first system described above includes at least one of the following: a first radio access technology (RAT) and a first core network.

[0142] For example, the first RAT mentioned above can be 4GS, or 5GS, or 6GS.

[0143] For example, the first core network mentioned above can be 4GC, or 5GC, or 6GC.

[0144] In some embodiments of this application, the second system described above includes at least one of the following: a second RAT and a second core network.

[0145] For example, the second RAT mentioned above can be 4GS, or 5GS, or 6GS.

[0146] For example, the second core network mentioned above can be 4GC, or 5GC, or 6GC.

[0147] In some embodiments of this application, the aforementioned switching type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network.

[0148] In some embodiments of this application, the aforementioned mobility type indication information includes at least one of the following: information of a first RAT, information of a second RAT, information of a first core network, and information of a second core network.

[0149] It is understandable that the first RAT mentioned above is the source RAT, that is, the RAT currently connected to the terminal, and the second RAT mentioned above is the target RAT, that is, the terminal is about to switch to or move to the target RAT. Similarly, the first core network is the source core network, and the second core network is the target core network.

[0150] In some embodiments of this application, the first indication information mentioned above may be the information carried in the PDU session update SM context request message.

[0151] In some embodiments of this application, the aforementioned PDU session update SM context request message is a message received by the first network element from the second network element.

[0152] In some embodiments of this application, the PDU session update SM context request message further includes at least one of the following: terminal identifier, Single Network Slice Selection Assistance Information (S-NSSAI), PDU session identifier (ID), AMF ID, SMF ID, target Radio Access Network (RAN) ID, and handover preparation indication.

[0153] For example, the terminal identifier mentioned above can be a Subscription Permanent Identifier (SUPI).

[0154] For example, the target access network mentioned above is the target RAT, or the access network corresponding to the target core network.

[0155] For example, the AMF locally stores the system type information and corresponding capability information of the SMF.

[0156] For example, the system type information and corresponding capability information of the SMF mentioned above include at least one of the following: the 6G system type and 6G session management capability of the SMF, and the 5G system type and 5G session management capability information.

[0157] In this way, the AMF can send a PDU session update SM context request message to the SMF based on the SMF's system type information and the association information between the PDU session ID and the SMF ID, instructing the SMF to use the corresponding system type and capabilities to process the PDU session update SM context request message.

[0158] In one example, the aforementioned PDU session update SM context request message may also include AMF system type indication information, which indicates that the PDU session update SM context request message corresponds to the AMF system type.

[0159] Optionally, in some embodiments of this application, step 501 can be specifically implemented by step 501a, and step 501b is included after step 501.

[0160] Step 501a: The second network element sends the first instruction information to the first network element.

[0161] Step 501b: The first network element receives the first instruction information from the second network element.

[0162] For example, the first network element is SMF and the second network element is AMF.

[0163] In some embodiments of this application, the aforementioned first instruction information is included in the first message.

[0164] For example, the first message mentioned above is a PDU session update SM context message. It should be noted that the specific description of the first message can be found in steps 201a and 201b above, and will not be repeated here.

[0165] For example, the first instruction information mentioned above can be transmitted through the SBI interface between the SMF and AMF.

[0166] In this way, the SMF can perform inter-system handover or inter-system movement by receiving the first instruction information sent by the AMF, thereby reducing signaling overhead.

[0167] In the inter-system mobility management method provided in this application embodiment, the second network element instructs other network elements to perform PDU session management by sending only the first instruction information to perform inter-system handover or inter-system mobility. Since it does not require multiple signaling interactions to transmit information, it reduces signaling overhead and network processing complexity, and lowers the latency for the terminal to perform inter-system handover or mobility registration update.

[0168] Optionally, in some embodiments of this application, before step 501 above, the inter-system mobility management method provided in the embodiments of this application may further include steps S101 and S102.

[0169] Step S101: The second network element obtains the context of the first terminal.

[0170] In some embodiments of this application, the first terminal context is the terminal context stored in the second network element.

[0171] In some embodiments of this application, the first terminal context mentioned above includes: a first MM context.

[0172] For example, the MM context includes at least one of the following: SUPI, RAT type, terminal security context, terminal radio capability ID, registration area, and terminal location.

[0173] It should be noted that the aforementioned AMF also contains associated information about the 6G PDU session ID, S-NSSAI, and SMF ID.

[0174] Step S102: The second network element modifies the first MM context to the second MM context.

[0175] In some embodiments of this application, the first MM context corresponds to the first RAT, and the second MM context corresponds to the second RAT.

[0176] For example, the first network element maps or modifies the first MM context to the second MM context, including at least one of the following operations:

[0177] Map the 6G security context to the 5G security context;

[0178] Change the existing RAT type from 6G RAT to 5G RAT;

[0179] Map or modify 6G TAI information to 5G TAI information;

[0180] Map or modify 6G registration area information to 5G registration area information;

[0181] Mapping or modifying 6G terminal location information to 5G terminal location information, etc.

[0182] In this way, the second network element can obtain the terminal context information from the AMF in advance, modify it, and then send the obtained terminal context information and the modified MM context information to the SMF using the PDU session update context information request information. This eliminates the need for the SMF to request and obtain the information before sending it, thereby reducing signaling overhead.

[0183] Optionally, in some embodiments of this application, the inter-system mobility management method provided in this application further includes: a second network element receiving a second message sent from a first network element. Specifically, refer to the description in step 401 above, which will not be repeated here.

[0184] Optionally, in some embodiments of this application, before the second network element sends the first indication information to the first network element, the second network element receives a handover required message from the RAN corresponding to the second network element.

[0185] In some embodiments of this application, the aforementioned handover message is used to trigger the AMF to perform inter-system handover or inter-system movement.

[0186] In some embodiments of this application, the aforementioned Handover required message includes at least one of the following: target RAN ID, source-to-target transparent container SM N2 information list, PDU session IDs, and handover type indication information.

[0187] For example, the aforementioned source-to-target transparent container contains information related to the radio bearer sent by the source RAN to the target RAN, such as QoS information and data forwarding information.

[0188] For example, the SM N2 information list mentioned above includes data forwarding information.

[0189] It should be noted that the contents of the above source-to-target transparent container are not visible to AMF.

[0190] Optionally, in some embodiments of this application, before the second network element sends the first indication information, the inter-system mobility management method provided in this application embodiment further includes the following step S201.

[0191] Step S201: The second network element sends auxiliary information to the first radio access network (RAN).

[0192] In some embodiments of this application, the aforementioned auxiliary information is used to assist in selecting the system to which the terminal wants to switch, or the RAN corresponding to the system it moves to. In some embodiments of this application, the aforementioned configuration information is used to assist the RAN in selecting a target RAN that is connected to the same AMF.

[0193] In some embodiments of this application, the aforementioned auxiliary information includes network element information of the second network element and at least one second RAN connecting the second network element.

[0194] For example, the second RAN is the RAN adjacent to the first RAN.

[0195] For example, the second network element obtains all RANs corresponding to the target system connected to it, and then determines the RAN adjacent to the first RAN, i.e. the aforementioned second RAN, based on the location of the first RAN. It sends the information of these RANs to the first RAN, so that the terminal can quickly access the corresponding RAN when the system is switched or moved, i.e. when the first RAN is switched or moved to the RAN corresponding to the target system.

[0196] In this way, when the second network element receives the handover information, it can use different networks of the same network element to perform subsequent inter-system handover or inter-system movement.

[0197] The inter-system mobility management method provided in this application can be implemented by an inter-system mobility management device. Exemplarily, this inter-system mobility management device can be a network-side device, or a functional component or entity within that network-side device. In this application embodiment, the network-side device can be a RAN (Radio Area Network). The following will use the RAN as an example to illustrate the inter-system mobility management method provided in this application embodiment.

[0198] Figure 4 This is a flowchart illustrating an inter-system mobility management method provided in some embodiments of this application, such as... Figure 4 As shown, some embodiments of this application provide an inter-system mobility management method that may include the following steps S301 and S302.

[0199] Step S301: The first RAN acquires auxiliary information.

[0200] In some embodiments of this application, the aforementioned auxiliary information includes network element information of the second network element and at least one second RAN connecting the second network element.

[0201] For example, the second RAN is the RAN adjacent to the first RAN.

[0202] In some embodiments of this application, the first RAN is the same as the second network element connected to the second RAN.

[0203] In one example, the aforementioned auxiliary information may be obtained by the first RAN from the AMF, i.e., the aforementioned second network element.

[0204] In another example, the aforementioned auxiliary information may be obtained by the first RAN from the operation management system.

[0205] Step S302: The first RAN determines the third RAN from at least one second RAN.

[0206] In some embodiments of this application, the third RAN is the system to which the terminal is to switch or the RAN corresponding to the system it moves to; in other words, it is the RAN corresponding to the target RAT or the target core network.

[0207] Optionally, in some embodiments of this application, the above step S301 is specifically implemented by the following step S301a.

[0208] Step S301a: The first RAN receives auxiliary information from the second network element.

[0209] For example, the second network element mentioned above is an AMF.

[0210] For example, the first RAN mentioned above can be a 6G RAN or a 5G RAN.

[0211] In the inter-system mobility management method provided in this application embodiment, since the 6G RAN can receive AMF information of the 5G RAN corresponding to its 5G neighbor cell with N2 interface, it helps the 6G RAN to quickly select the target 5G RAN connected to the same AMF, so that the AMF can obtain the terminal context locally and modify it.

[0212] The following example of inter-system handover from 6GS to 5GS illustrates the mobility management method provided in this application embodiment, specifically in the case of modifying the SM context during inter-system handover.

[0213] Example 1: As Figure 5As shown, the mobility management method may include the following steps A0 to A12.

[0214] Step A0. The terminal has already established a PDU session and a Quality of Service (QoS) flow in 6GS and is in the connected state (CM_Connected).

[0215] Step A1.6: The RAN triggers this process based on the terminal's measurement report and decides to initiate an inter-system handover.

[0216] Step A2.6G RAN sends a Handover Required message to AMF, requesting AMF to prepare for handover and initiating a handover initiation.

[0217] Step A3. Based on the source 6G RAN and target 5G RAN information included in the handover type indication information, the AMF determines that the terminal needs to complete an inter-system handover from 6GS to 5GS. Then, the AMF obtains the 6G terminal context locally, including the MM context and part of the SM context. Next, the AMF maps or modifies the 6G MM to the 5G MM context locally.

[0218] Step A4. The AMF sends a PDU session update SM context request message (Nsmf_PDUSession_UpdateSMContext Request) to the SMF based on the SMF's system type information, the PDU session ID, and the association information between the PDU and the SMF. This PDU session update SM context request message contains handover type indication information.

[0219] For example, the above-mentioned handover type indication information is used to instruct the SMF to switch the PDU session from 6GS to 5GS.

[0220] Step A4a. The SMF prepares the SM context. The SMF obtains the 6GSM context locally based on the terminal identifier and PDU session ID information, and maps or modifies it to the 5G SM context, including allocating 5G PDU session ID, 5G CN tunnel information, and associating 5G QoS information.

[0221] Step A5. If the Policy Notification Function (PCF) has deployed a dynamic PCC, the SMF may initiate an SM policy modification to the PCF to map or modify the 6G SM policy to a 5G SM policy.

[0222] Step A6. SMF and UPF perform N4 session modification, and UPF allocates CN tunnel information for 5G PDU session.

[0223] Step A7. The SMF sends a PDU session update SM context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF. This message instructs the AMF to process the PDU session update SM context response message using the appropriate system type and capability, i.e., the appropriate system type is the system type of the first system mentioned above.

[0224] Optionally, the PDU session update SM context response message also includes SMF system type indication information, indicating that the message corresponds to the 5G system type of the SMF.

[0225] Step A8. The AMF sends a handover request message to the 5G RAN, requesting the 5G RAN to reserve handover resources.

[0226] Step A9.5G RAN sends a Handover request ACK message to AMF.

[0227] For example, the aforementioned handover request confirmation message includes at least one of the following: target-to-source transparent container, N2 SM response information, and a list of PDU sessions that failed to be established.

[0228] For example, the aforementioned target-to-source transparent container contains target cell radio resource configuration information, etc.

[0229] For example, the N2 SM response information mentioned above includes at least one of the following: PDU session ID, accepted QFI list, and AN tunnel information.

[0230] Step A10. The AMF sends a PDU session update SM context request message (Nsmf_PDUSession_UpdateSMContext Request) to the SMF, which includes the 5G PDU session ID and the N2SM response information received from the 5G RAN, in order to update the N3 tunnel information.

[0231] Step A11. If the 5G RAN accepts the handover, the SMF indicates the N3 UP address and tunnel ID of the 5G RAN to the UPF to prepare for the handover.

[0232] Step A12. The SMF sends a PDU session update SM context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF, which includes 5G PDU session ID information, etc.

[0233] It should be noted that steps A0 to A12 above constitute the handover preparation process before inter-system handover. In this embodiment 1, after the handover preparation is completed, the terminal then proceeds with the inter-system handover process. Specifically, this includes the following steps B1 to B11.

[0234] Step B1. The AMF sends a handover command to the 6G RAN, which includes the target to source transparent container, the 6G PDU session ID to be forwarded, and the 6G PDU session ID to be released.

[0235] Step B2. The 6G RAN sends a handover command to the terminal, instructing the terminal to switch from the 6G RAN.

[0236] Step B3. The terminal successfully synchronizes with the 5G RAN, sends a handover confirmation message, and switches to the 5G RAN.

[0237] Step B4. The 5G RAN sends a Handover Notify to the AMF, indicating that the terminal has switched to the 5G RAN.

[0238] Step B5. The AMF completes the handover process (HO Complete). The terminal has successfully switched to the 5G RAN, and the AMF saves the context information of the successfully switched 5G terminal.

[0239] Step B6. The AMF sends a PDU session update SM context request message (Nsmf_PDUSession_UpdateSMContext Request) to the SMF, which includes a handover completion indication of the PDU session ID.

[0240] Step B7. Perform an N4 session update between SMF and UPF to update the downlink user plane forwarding channel and switch the user plane path to 5G.

[0241] Step B8. If PCC is used, SMF initiates SM policy association modification, notifying PCF of information such as changes in RAT type and terminal location. PCF then sends the updated SM policy to SMF.

[0242] Step B9. The SMF sends a PDU session update SM context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF to confirm the handover is complete.

[0243] Step B10. Modify the N4 session between SMF and UPF.

[0244] Step B11. If the MRU process triggering conditions are met, the terminal initiates the mobile registration update process in 5GS.

[0245] Thus, this embodiment solves the problems of high latency and network processing complexity caused by the numerous signaling interactions between network elements and the need to create new SM contexts and delete old SM contexts in the prior art, and achieves the gain of reducing latency and network processing complexity.

[0246] The following examples illustrate the mobility management method provided in this application embodiment, specifically addressing the selection of the SM context during inter-system handover.

[0247] Example 2: The mobility management method may include the following steps C0 to C12.

[0248] It should be noted that the specific process of Example 2 can be referred to in Example 1. Figure 5 The processes are the same, with the only difference being the behavior and message content of AMF and SMF in some steps.

[0249] Steps C0 to C2 are the same as steps A0 to A2 in the above embodiment 1.

[0250] Step C 3. Based on the source 6G RAN and target 5G RAN information and the handover type indication information, the AMF determines that it is a system handover from 6GS to 5GS, obtains the 6G terminal context and 5G terminal context from the local machine, and modifies the 5G MM context information according to the Handover required message and 6G MM context information.

[0251] Step C4 is the same as step A4 in Example 1 above.

[0252] Step C4a.SMF obtains the 6G SM context and 5G SM context locally based on the terminal identifier and PDU session ID information, and modifies the 5G SM context according to message 4 and the 6G SM context, including modifying the 5G PDU session ID, 5G CN tunnel information, and associated 5G QoS information.

[0253] Steps C5 to C12 are the same as steps A5 to A12 in the above embodiment 1.

[0254] It should be noted that steps C0 to C12 above are the handover preparation process before the inter-system handover. In this embodiment 2, after the handover preparation is completed, the terminal then performs the inter-system handover execution process, and the specific handover execution process is the same as in embodiment 1.

[0255] Thus, in this embodiment, the SMF selects the terminal context based on the handover type indication information sent by the AMF, modifies the terminal context according to the target RAT information, and performs PDU session handover. This solves the problems of high latency and network processing complexity caused by numerous signaling interactions between network elements and the need to create new SM contexts and delete old SM contexts in the prior art, achieving gains in reducing latency and network processing complexity.

[0256] The following examples illustrate the mobility management method provided in this application by providing specific examples of modifying the SM context during mobile registration updates.

[0257] Example 3: As Figure 6 As shown, the mobility management method may include steps D1 to D18 as described below.

[0258] Step D1. The terminal triggers the registration process.

[0259] For example, if the terminal has already completed the initial registration process in 6G and established an associated PDU session, and the terminal enters an idle state without generating traffic, and the terminal moves from the 6G coverage area to the 5G coverage area due to mobility or changes in wireless conditions, and the registration area changes, then this process is triggered.

[0260] Step D2. The terminal sends a registration request to the 5G RAN, setting the registration type to "mobile registration update".

[0261] For example, the registration request includes a 5G-GUTI mapped from the 6G globally unique temporary UE identity (GUTI) as the old GUTI, an original 5G-GUTI (if available) as the additional GUTI, and instructs the terminal to migrate from 6GS.

[0262] For example, the aforementioned additional 5G-GUTI enables the AMF to retrieve the terminal's MM context from the legacy AMF. If the terminal holds the local 5G-GUTI of this PLMN, the terminal also includes the GUAMI portion of the local 5G-GUTI in the RRC so that the 5GRAN can route the registration request to the same AMF; otherwise, the terminal provides the GUAMI mapped from the 6G-GUTI in the RRC and indicates it as "mapped from 6G".

[0263] Step D3.5G RAN selects AMF based on GUAMI or the terminal's original 5G GUTI information.

[0264] Preferably, the 5G RAN routes the registration request to the same AMF based on the original 5G-GUTI. This AMF is the AMF the terminal registered with during 6G.

[0265] Step D4.5G RAN sends a Registration Request message to AMF, which contains indication information for the terminal to migrate from 6G.

[0266] Step D5. The AMF derives the 6G AMF address and 6G-GUTI based on the old 5G-GUTI mapped by the 6G-GUTI, determines that the 6G AMF is the local AMF, obtains the 6G terminal context from the local machine, which includes the 6G MM context information, and maps or modifies the 6G MM context to the 5G MM context.

[0267] Step D6. Optional, authentication and security related procedures. This procedure is triggered, for example, when the AMF cannot obtain the terminal MM context from this AMF or another AMF, or for other reasons.

[0268] Step D7. Optional, perform the identification request / response process, the 5G EIR device identification check process, where the AMF requests the terminal to provide the IMEI and performs an IMEI check.

[0269] Step D8. Optionally, if the AMF ID or AMF IP address is different from the AMF registered by the terminal in 6G, register its AMF ID or AMF IP address and other information with the UDM through Terminal Connection Management_Registration (Nudm_UECM_Registration). This includes the relevant processes of selecting the UDM, registering, obtaining subscription data, and subscribing to subscription data.

[0270] Step D9. If the 5G AM policy is different from the 6G AM policy, associate or modify the 6G AM policy to the 5G AM policy.

[0271] Step D10. If the registration request in step D1 contains a list of PDU sessions to be activated, the AMF sends a PDU session update SM context request message (Nsmf_PDUSession_UpdateSMContextRequest) to the SMF associated with the PDU session.

[0272] For example, the PDU session update SM context request message includes mobility type indication information. This mobility type indication information is used to activate the user plane connection of PDU sessions in the list of PDU sessions to be activated, and to instruct the SMF to modify the SM context according to the mobility type indication information.

[0273] In Example 3, the target RAT is 5G and the source RAT is 6G, representing the inter-system MRU from 6GS to 5GS.

[0274] It is understandable that in other application scenarios, the mobility type indication information can also indicate the MRU within 6GS or 5GS.

[0275] Optionally, the PDU session update SM context request message may also include AMF system type indication information, indicating that the message corresponds to the AMF's 6G system type.

[0276] Step D11. SMF prepares SM context information.

[0277] For example, the SMF locally obtains the 6G SM context information and maps or modifies it to the 5G SM context. For 6G PDU sessions that support session continuity from 6GS to 5GS and require activation, the SMF obtains the 6G SM context information locally (when the SMF remains unchanged) and maps or modifies the 5G SM context.

[0278] Step D12. SMF and UPF perform N4 session modification.

[0279] For example, if the PDU session supports session continuity from 6GS to 5GS, the SMF looks up the corresponding 6G PDU session based on the 6G SM context, the SMF initiates the N4 session modification process, and the UPF establishes a CN tunnel for the 5G PDU session.

[0280] Step D13. The SMF sends a PDU session update SM context response message (Nsmf_PDUSession_UpdateSMContext Response) to the AMF.

[0281] Step D14. If the 5G SM policy is different from the 6G SM policy, associate or modify the 6G SM policy to the 5G SM policy.

[0282] Step D15. Optional, steps 18-19 of the general registration process. When the new AMF is different from the old AMF, the new AMF and N3IWF / TNGF / W-AGF exchange terminal context modification requests / responses.

[0283] Step D16. AMF sends a Registration Accept message to the terminal and assigns parameters such as 5G-GUTI and registration area.

[0284] Step D17. Perform the terminal policy association establishment process.

[0285] Step D18. The terminal sends a Registration Complete message to the AMF for confirmation.

[0286] Thus, in this embodiment, the SMF determines whether it is an MRU process from 6GS to 5GS or from 5GS to 6GS based on the migration type indication information sent by the AMF. The SMF obtains the SM context of the existing PDU session locally, modifies the SM context according to the migration type indication information, and performs PDU session modification and / or activation. This third embodiment solves the problems of high latency and network processing complexity caused by numerous signaling interactions between network elements and the need to create new SM contexts for PDU sessions and delete the SM contexts of old PDU sessions in the prior art, achieving gains in reducing latency and network processing complexity.

[0287] The following example illustrates the mobility management method provided in this application embodiment, specifically for the case of selecting the SM context in a mobile registration update scenario.

[0288] Example 4: The mobility management method may include the following steps E1 to E18.

[0289] It should be noted that the specific process of Example 4 can be referred to in Example 3. Figure 6 The processes are the same, with the only difference being the behavior and message content of AMF and SMF in some steps.

[0290] Step E5. The AMF derives the 6G AMF address and 6G-GUTI based on the old 5G-GUTI mapped by the 6G-GUTI, determines that the 6G AMF is the local AMF, obtains the 6G terminal context and 5G terminal context from the local machine, including the 6G MM context information and the 5G MM context information, and maps or modifies the 5G MM context according to the 6G MM context.

[0291] Steps E6 to E10 are the same as steps D6 to D10 in the above embodiment 3.

[0292] Step E11. For 6G PDU sessions that support session continuity from 6GS to 5GS and require activation, the SMF locally obtains the 6G SM context information and the 5G SM context information, and maps or modifies the 5G SM context according to the 6G SM context information.

[0293] Steps E12 to E18 are the same as steps D12 to D18 in the above embodiment 3.

[0294] In this way, the SMF determines the MRU process from 6G to 5G or from 5G to 6G based on the migration type indication information sent by the AMF. The SMF selects the terminal context locally, modifies the terminal context according to the migration type indication information, and performs PDU session modification and / or activation. This solves the problems of high latency and network processing complexity caused by multiple signaling interactions between network elements and the need to create new SM contexts and delete old SM contexts in the existing technology, achieving a gain in reducing latency and network processing complexity.

[0295] It should be noted that in existing technologies, handover types only exist between the Source RAN and the AMF. When the 6G AMF and SMF are upgraded from 5G functions, it is difficult to distinguish different scenarios and process them accordingly in the PDU session update SM context request message. Introducing mobility type indication information, which includes the handover type of the handover scenario and different migration types in the MRU, ensures consistent processing of various scenarios for updating the SM context between the AMF and SMF, enabling the AMF and SMF to distinguish whether to use the corresponding 6G or 5G functions to process the corresponding messages. The AMF and SMF respectively store the PDU session ID, the corresponding network element identifier of the other party, system type, and system capability association information.

[0296] Optionally, in some embodiments of this application, this embodiment also provides a network architecture, such as... Figure 7 As shown.

[0297] For example, in the 6G phase, the 6GC AMF can be implemented by upgrading the 5GC AMF, and the 6GC SMF can be implemented by upgrading the 5GC SMF. The 5G RAN connects to the 5G access and mobility management functions of the AMF, and the 6G RAN connects to the 6G access and mobility management functions of the AMF. The 6G functions of the AMF and the 6G functions of the SMF interact with each other for 6G PDU session management-related signaling, and the 5G functions of the AMF and the 5G functions of the SMF interact with each other for 5G PDU session management-related signaling.

[0298] It should be noted that the above Figure 7 This can be applied to Examples 1 to 4 above.

[0299] The inter-system mobility management method provided in this application can be implemented by an inter-system mobility management device. This application uses the example of an inter-system mobility management device executing the inter-system mobility management method to illustrate the inter-system mobility management device provided in this application.

[0300] This application provides an inter-system mobility management device. As an example, the inter-system mobility management device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0301] The inter-system mobility management device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0302] For details, see Figure 8 When the inter-system mobility management device is a first network element or a component of the first network element, the inter-system mobility management device 600 includes: an acquisition module 601 and a processing module 602.

[0303] The acquisition module 601 is used to acquire first indication information, which is used to indicate inter-system switching or inter-system movement; the processing module 602 is used to perform PDU session management operations based on the first indication information.

[0304] Optionally, in some embodiments of this application, the first indication information includes any one of the following: switching type indication information and movement type indication information; wherein, the switching type indication information is used to indicate that the terminal switches from the first system to the second system; and the movement type indication information is used to indicate that the terminal moves from the first system to the second system.

[0305] Optionally, in some embodiments of this application, the acquisition module 601 described above is specifically used to receive first indication information from the second network element.

[0306] Optionally, in some embodiments of this application, the above-mentioned PDU session management operation includes at least one of the following:

[0307] Modify Session Management (SM) context information;

[0308] Select SM context information.

[0309] Optionally, in some embodiments of this application, the above-mentioned acquisition module 601 is further used to acquire at least one of the following SM context information;

[0310] First SM context information,

[0311] Second SM context information;

[0312] The first SM context information and the second SM context information are both SM context information stored in the first network element, and the first SM context information and the second SM context information are SM context information from different systems.

[0313] Optionally, in some embodiments of this application, the processing module 602 is further configured to modify the first SM context information to the third SM context information after the acquisition module 601 acquires the first SM context information, wherein the first SM context has a corresponding relationship with the first system and the third SM context has a corresponding relationship with the second system.

[0314] Optionally, in some embodiments of this application, the processing module 602 is further configured to select either the first SM context information or the second SM context information after the first SM context information and the second SM context information are obtained by the acquisition module 601, wherein the first SM context has a corresponding relationship with the first system and the second SM context has a corresponding relationship with the second system.

[0315] Optionally, in some embodiments of this application, the first system includes at least one of the following: a first radio access technology (RAT) and a first core network; the second system includes at least one of the following: a second RAT and a second core network.

[0316] Optionally, in some embodiments of this application, the aforementioned handover type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network; or, the mobility type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network.

[0317] Optionally, in some embodiments of this application, the first indication information mentioned above includes switching type indication information; the processing module 602 is further configured to perform at least one of the following:

[0318] Switch the RAT corresponding to the Protocol Data Unit (PDU) session from the first RAT to the second RAT;

[0319] Switch the core network corresponding to the PDU session from the first core network to the second core network.

[0320] Optionally, in some embodiments of this application, the first indication information includes mobility type indication information; the processing module 602 is further configured to modify the SM context information of the PDU session corresponding to the second system according to the first indication information, and to activate the PDU session corresponding to the second system and modify the SM context information.

[0321] Optionally, in some embodiments of this application, combined with Figure 8 ,like Figure 9 As shown, the above-mentioned device 600 further includes: a sending module 603; the sending module 603 is used to send a second message to the second network element, the second message being used to indicate relevant information used in processing the first message; wherein, the relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

[0322] Optionally, in some embodiments of this application, the second message mentioned above includes system type indication information, which is used to indicate the system type used by the second network element.

[0323] Optionally, in some embodiments of this application, the first message mentioned above is a PDU session update SM context response message.

[0324] In the inter-system mobility management device provided in this application embodiment, the inter-system mobility management device obtains first indication information, which is used to indicate inter-system handover or inter-system movement; based on the first indication information, the inter-system mobility management device performs PDU session management operations. In this solution, the first network element can perform the corresponding PDU session management operation through the content indicated in the first indication information, namely inter-system handover or inter-system movement, thereby reducing the number of signaling interactions caused by multiple messages such as creating a new PDU session, deleting or releasing an old PDU session in the prior art, and thus reducing the latency and network processing complexity of the terminal performing inter-system handover or mobility registration update.

[0325] See Figure 10 When the inter-system mobility management device is a second network element or a component of a second network element, the inter-system mobility management device 700 includes: a transmission module 701.

[0326] The aforementioned sending module 701 is used to send first indication information, which is used to instruct the execution of PDU session management.

[0327] Optionally, in some embodiments of this application, the first indication information is any one of the following: switching type indication information, mobility type indication information; wherein, the switching type indication information is used to indicate that the terminal switches from the first system to the second system; the mobility type indication information is used to indicate that the terminal migrates from the first system to the second system.

[0328] Optionally, in some embodiments of this application, combined with Figure 10 ,like Figure 11 As shown, the above-mentioned device 700 further includes: an acquisition module 702 and a processing module 703; the acquisition module 702 is used to acquire a first terminal context before the above-mentioned sending module 701 sends the first indication information. The first terminal context is the terminal context stored in the second network element. The first terminal context includes: a first mobility management (MM) context.

[0329] The aforementioned processing module 703 is used to modify the first MM context to the second MM context;

[0330] The first MM context corresponds to the first RAT, and the second MM context corresponds to the second RAT.

[0331] Optionally, in some embodiments of this application, the first system includes at least one of the following: a first RAT and a first core network; the second system includes at least one of the following: a second RAT and a second core network.

[0332] Optionally, in some embodiments of this application, the aforementioned handover type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network; or, the mobility type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network.

[0333] Optionally, in some embodiments of this application, the sending module 701 is specifically used to send first indication information to the first network element. The first indication information is included in a first message, which is a PDU session update SM context request message.

[0334] Optionally, in some embodiments of this application, combined with Figure 10 ,like Figure 12As shown, the above-mentioned device 700 further includes: a receiving module 704; the receiving module 704 is used to receive a second message sent from the first network element, the second message being used to instruct the second network element to process the relevant information used in the first message; wherein, the relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

[0335] Optionally, in some embodiments of this application, the second message mentioned above includes system type indication information, which is used to indicate the system type used by the second network element.

[0336] Optionally, in some embodiments of this application, the second message is a PDU session update SM context response message.

[0337] In the inter-system mobility management device provided in this application embodiment, the inter-system mobility management device performs inter-system handover or inter-system mobility by sending only the first instruction information to instruct other network elements to perform PDU session management. Since it does not require multiple signaling interactions to transmit information, it reduces signaling overhead and network processing complexity, and lowers the latency for terminals to perform inter-system handover or mobility registration updates.

[0338] See Figure 13 When the inter-system mobility management device is a second network element or a component of a second network element, the inter-system mobility management device 80 includes: an acquisition module 81 and a processing module 82;

[0339] The acquisition module 81 is used to acquire auxiliary information, including network element information of the second network element and at least one second RAN connected to the second network element; the processing module 82 determines a third RAN from the second RAN, the third RAN being the system to which the terminal wants to switch or the RAN corresponding to the system to which it moves; wherein the first RAN is the same as the second network element connected to the second RAN.

[0340] Optionally, in some embodiments of this application, the above-mentioned acquisition module is specifically used to receive auxiliary information from the second network element.

[0341] In the inter-system mobility management method provided in this application embodiment, since the 6G RAN can receive AMF information of the 5G RAN corresponding to its 5G neighbor cell with N2 interface, it helps the 6G RAN to quickly select the target 5G RAN connected to the same AMF, so that the AMF can obtain the terminal context locally and modify it.

[0342] The inter-system mobility management device provided in this application embodiment can realize the various processes implemented in the inter-system mobility management method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0343] like Figure 14 As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps of the above-described inter-system mobility management method embodiment and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various steps of the above-described inter-system mobility management method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0344] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the inter-system mobility management method embodiment. This terminal embodiment corresponds to the above-described terminal-side method embodiment; all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effects. Specifically, Figure 15 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0345] The terminal 100 includes, but is not limited to, at least some of the following components: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0346] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 15 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0347] It should be understood that, in this embodiment, the input unit 104 may include a graphics processor 1041 and a microphone 1042. The graphics processor 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0348] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 101 can transmit it to the processor 110 for processing; in addition, the radio frequency unit 101 can send uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0349] The memory 109 can be used to store software programs or instructions, as well as various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory. The non-volatile memory may 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), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0350] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0351] This application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the inter-system mobility management method embodiment. This network-side device embodiment corresponds to the above-described network-side device method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0352] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 16 The system mobility management device shown. For example... Figure 16 As shown, the network-side device 900 includes a processor 901, a network interface 902, and a memory 903. This network-side device can be an inter-system mobility management device within an inter-system mobility management method. The network interface 902 is, for example, a Common Public Radio Interface (CPRI).

[0353] Specifically, the network-side device 900 in this application embodiment further includes: instructions or programs stored in memory 903 and executable on processor 901, wherein processor 901 calls the instructions or programs in memory 903 to execute. Figures 8 to 12 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0354] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described inter-system mobility management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0355] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0356] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described inter-system mobility management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0357] 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.

[0358] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described inter-system mobility management method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0359] This application also provides a communication system, including: a first network element, a second network element terminal, and a network-side device. The terminal can be used to execute the steps of the inter-system mobility management method described above, and the network-side device can be used to execute the steps of the inter-system mobility management method described above.

[0360] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0361] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0362] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for managing inter-system mobility, characterized in that, include: The first network element obtains the first instruction information, which is used to indicate inter-system handover or inter-system movement. The first network element performs Protocol Data Unit (PDU) session management operations based on the first indication information.

2. The method according to claim 1, characterized in that, The first indication information includes any one of the following: switching type indication information, movement type indication information; The switching type indication information is used to indicate that the terminal switches from the first system to the second system; the movement type indication information is used to indicate that the terminal moves from the first system to the second system.

3. The method according to claim 1 or 2, characterized in that, The PDU session management operation includes at least one of the following: Modify Session Management (SM) context information; Select SM context information.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first network element obtains at least one of the following SM context information: First SM context information, Second SM context information; Wherein, the first SM context information and the second SM context information are both SM context information stored in the first network element, and the first SM context information and the second SM context information are SM context information from different systems.

5. The method according to claim 4, characterized in that, After the first network element obtains the first SM context information, the method further includes: The first network element modifies the first SM context information to the third SM context information, wherein the first SM context information corresponds to the first system, and the third SM context information corresponds to the second system.

6. The method according to claim 4, characterized in that, After the first network element obtains the first SM context information and the second SM context information, the method further includes: The first network element selects either the first SM context information or the second SM context information, wherein the first SM context information corresponds to the first system, and the second SM context information corresponds to the second system.

7. The method according to claim 2, characterized in that, The first system includes at least one of the following: a first radio access technology (RAT) and a first core network; The second system includes at least one of the following: a second RAT, a second core network.

8. The method according to claim 2 or 7, characterized in that, The handover type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network; Alternatively, the mobility type indication information may include at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network.

9. The method according to any one of claims 2 to 8, characterized in that, The first indication information includes switching type indication information; the method further includes at least one of the following: The first network element switches the RAT corresponding to the PDU session from the first RAT to the second RAT; The first network element switches the core network corresponding to the PDU session from the first core network to the second core network.

10. The method according to any one of claims 2 to 8, characterized in that, The first indication information includes the movement type indication information; the method further includes: The first network element modifies the SM context information of the PDU session corresponding to the second system or activates the PDU session corresponding to the second system and modifies the SM context information according to the first instruction information.

11. The method according to any one of claims 1 to 10, characterized in that, The first network element obtains the first indication information, including: The first network element receives a first message from the second network element, the first message including the first indication information; The first message is a PDU session update SM context request message.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: The first network element sends a second message to the second network element, the second message being used to indicate the relevant information used in processing the second message; The relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

13. The method according to claim 12, characterized in that, The second message includes system type indication information, which is used to indicate the system type used by the second network element.

14. The method according to claim 10 or 11, characterized in that, The second message is the PDU session update SM context response message.

15. A method for managing inter-system mobility, characterized in that, include: The second network element sends a first instruction message, which is used to indicate inter-system handover or inter-system movement.

16. The method according to claim 15, characterized in that, The first indication information is any one of the following: switching type indication information, movement type indication information; The handover type indication information is used to indicate that the terminal is switching from the first system to the second system; the mobility type indication information is used to indicate that the terminal is migrating from the first system to the second system.

17. The method according to claim 16, characterized in that, Before the second network element sends the first indication information, the method further includes: The second network element obtains the first terminal context, which is the terminal context stored by the second network element. The first terminal context includes: a first mobility management (MM) context. The second network element modifies the first MM context to the second MM context; The first MM context corresponds to the first system, and the second MM context corresponds to the second system.

18. The method according to claim 15 or 16, characterized in that, The first system includes at least one of the following: a first RAT, and a first core network; The second system includes at least one of the following: a second RAT, a second core network.

19. The method according to claim 16 or 18, characterized in that, The handover type indication information includes at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network; Alternatively, the mobility type indication information may include at least one of the following: information of the first RAT, information of the second RAT, information of the first core network, and information of the second core network.

20. The method according to claims 15 to 19, characterized in that, The second network element sends a first indication message, including: The second network element sends the first indication information to the first network element. The first indication information is contained in the first message, which is a PDU session update SM context request message.

21. The method according to claims 15 to 20, characterized in that, The method further includes: The second network element receives a second message sent from the first network element, the second message being used to instruct the second network element to process the relevant information used in the second message; The relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

22. The method according to claim 21, characterized in that, The second message includes system type indication information, which is used to indicate the system type used by the second network element.

23. The method according to claim 21 or 22, characterized in that, The second message is the PDU session update SM context response message.

24. The method according to claims 15 to 23, characterized in that, The method further includes: The second network element sends auxiliary information to the first radio access network (RAN). The auxiliary information is used to assist in selecting the system to which the terminal wants to switch or the RAN corresponding to the system it moves to. The auxiliary information includes the network element information of the second network element and at least one second RAN connected to the second network element.

25. A method for managing inter-system mobility, characterized in that, include: The first RAN acquires auxiliary information, which includes network element information of the second network element and at least one second RAN connected to the second network element; The first RAN determines a third RAN from the at least one second RAN, the third RAN being the RAN corresponding to the system to which the terminal is to switch, or the system to which it is to move; Wherein, the second network element connected to the first RAN and the second RAN is the same.

26. The method according to claim 25, characterized in that, The first RAN acquires auxiliary information, including: The first RAN receives the auxiliary information from the second network element.

27. An inter-system mobility management device, characterized in that, include: Acquisition module and processing module; The acquisition module is used to acquire first indication information, which is used to indicate inter-system switching or inter-system movement; The processing module is used to perform PDU session management operations based on the first indication information.

28. The apparatus according to claim 27, characterized in that, The first indication information includes any one of the following: switching type indication information, movement type indication information; The switching type indication information is used to indicate that the terminal switches from the first system to the second system; the movement type indication information is used to indicate that the terminal moves from the first system to the second system.

29. The apparatus according to claim 27 or 28, characterized in that, The first indication information includes a switching type indication information; the processing module is further configured to perform at least one of the following: Switch the RAT corresponding to the PDU session from the first RAT to the second RAT; Switch the core network corresponding to the PDU session from the first core network to the second core network.

30. The apparatus according to any one of claims 27 or 28, characterized in that, The first indication information includes the mobility type indication information; the processing module is further configured to modify the SM context information of the PDU session corresponding to the second system according to the first indication information, and to activate the PDU session corresponding to the second system and modify the SM context information.

31. The apparatus according to any one of claims 27 to 30, characterized in that, The acquisition module is specifically used to receive a first message from the second network element, wherein the first message includes the first indication information; The first message is a PDU session update SM context request message.

32. The apparatus according to any one of claims 27 to 31, characterized in that, The device further includes: a transmitting module; The sending module is used to send a second message to the second network element, the second message being used to indicate the relevant information used in processing the second message; The relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

33. An inter-system mobility management device, characterized in that, include: Sending module; The sending module is used to send first indication information, which is used to indicate inter-system switching or inter-system movement.

34. The apparatus according to claim 33, characterized in that, The first indication information is any one of the following: switching type indication information, movement type indication information; The handover type indication information is used to indicate that the terminal is switching from the first system to the second system; the mobility type indication information is used to indicate that the terminal is migrating from the first system to the second system.

35. The apparatus according to claim 33, characterized in that, The device further includes: an acquisition module and a processing module; The acquisition module is used to acquire a first terminal context before the sending module sends the first indication information. The first terminal context is the terminal context stored in the second network element. The first terminal context includes: a first mobility management (MM) context. The processing module is used to modify the first MM context to a second MM context; The first MM context corresponds to the first system, and the second MM context corresponds to the second system.

36. The apparatus according to claims 33 to 35, characterized in that, The sending module is specifically used to send the first indication information to the first network element. The first indication information is contained in a first message, which is a PDU session update SM context request message.

37. The apparatus according to claims 33 to 36, characterized in that, The device further includes: a receiving module; The receiving module is used to receive a second message sent from the first network element, the second message being used to instruct the second network element to process the relevant information used in the second message; The relevant information includes at least one of the following: the system type of the second network element, and the capability information of the second network element.

38. The method according to claims 33 to 37, characterized in that, The sending module is further configured to send auxiliary information to the first RAN. The auxiliary information is used to assist in selecting the system to which the terminal wants to switch or the RAN corresponding to the system it moves to. The auxiliary information includes the network element information of the second network element and at least one second RAN connected to the second network element.

39. An inter-system mobility management device, characterized in that, include: Acquisition module and processing module; The acquisition module is used to acquire auxiliary information, which includes network element information of the second network element and at least one second RAN connected to the second network element; The processing module determines a third RAN from the second RAN, wherein the third RAN is the system to which the terminal wants to switch, or the RAN corresponding to the system to which it moves; Wherein, the second network element connected to the first RAN and the second RAN is the same.

40. The apparatus according to claim 39, characterized in that, The acquisition module is specifically used to receive the auxiliary information from the second network element.

Images