Mobility management method, terminal and network side device

Abstract

The application discloses a mobility management method, a terminal and a network side device, and belongs to the technical field of communication. The method of the application embodiment comprises the following steps: a terminal sends a first message to a first core network device corresponding to a first network; wherein, the first message is used for registration of the first network or mobility registration update (MRU), and the first message comprises first indication information, the first indication information is used for indicating that the terminal is in a registration state at the first network or comes from the first network, or the first indication information is used for indicating that the terminal is in a registration state at a second network or comes from the second network, and the first network is a successor network or a next generation network of the second network.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a mobility management method, terminal, and network equipment. Background Technology

[0002] Taking 5G and 6G networks in the evolution of wireless communication technology as examples, relevant technologies stipulate that the format of the 5G Globally Unique Temporary UE Identity (GUTI) corresponding to the 5G network and the 6G GUTI corresponding to the 6G network are the same. Therefore, for network architectures that support both 5G and 6G networks, it is possible to avoid modifying 5G network elements, which is conducive to the rapid development of 6G services.

[0003] However, when performing mobility management on terminals based on GUTI, the fact that 5G GUTI and 6G GUTI have the same format may make it impossible to determine whether the network previously registered by the terminal is a 6G network or a 5G network, thus affecting mobility management performance. Summary of the Invention

[0004] This application provides a mobility management method, terminal, and network device that can solve the problem of not being able to determine the network previously registered by the terminal when performing mobility management based on GUTI, thereby improving mobility management performance.

[0005] In a first aspect, a mobility management method is provided, comprising: a terminal sending a first message to a first core network device corresponding to a first network; wherein the first message is used for registration or Mobility Registration Update (MRU) on the first network, the first message includes first indication information, the first indication information being used to indicate that the terminal is in a registered state on the first network or is from the first network, or the first indication information being used to indicate that the terminal is in a registered state on a second network or is from the second network, wherein the first network is a successor network or a next-generation network of the second network.

[0006] Secondly, a mobility management method is provided, comprising: a first core network device receiving a first message from a terminal, wherein the first message is used for registration or MRU in a first network, and the first message includes first indication information; the first core network device obtaining the context of the terminal in the first network according to the first indication information; wherein the first indication information is used to indicate that the terminal is in a registered state in the first network or is from the first network, or the first indication information is used to indicate that the terminal is in a registered state in a second network or is from the second network, wherein the first network is a successor network or a next-generation network of the second network.

[0007] Thirdly, a mobility management method is provided, comprising: a second core network device receiving a second message from a first core network device; the second core network device performing any of the following based on the second message: if the second message includes second indication information, sending the context of a terminal in a first network to the first core network device; if the second message does not include the second indication information, sending the context of the terminal in a second network to the first core network device; wherein the first network is a successor network or a next-generation network of the second network, and the second indication information is used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; instructing the terminal to perform registration or MRU in the first network.

[0008] Fourthly, a mobility management method is provided, comprising: a fourth core network device receiving an update message from a first core network device; the fourth core network device performing any of the following based on the update message: if the update message includes third indication information, recording that the terminal is in a first network or is in a registered state in the first network; if the update message does not include the third indication information, recording that the terminal is in a second network or is in a registered state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the third indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform registration or MRU in the first network.

[0009] Fifthly, a mobility management device is provided, comprising: a sending module, configured to send a first message to a first core network device corresponding to a first network; wherein the first message is used for registration or MRU in the first network, the first message includes first indication information, the first indication information being used to indicate that the terminal is in a registration state in the first network or is from the first network, or, the first indication information being used to indicate that the terminal is in a registration state in a second network or is from the second network, wherein the first network is a successor network or next-generation network of the second network.

[0010] A sixth aspect provides a mobility management device, comprising: a receiving module for receiving a first message from a terminal, wherein the first message is for registration or MRU in a first network, and the first message includes first indication information; and a processing module for obtaining the context of the terminal in the first network based on the first indication information; wherein the first indication information is used to indicate that the terminal is in a registration state in the first network or is from the first network, or the first indication information is used to indicate that the terminal is in a registration state in a second network or is from the second network, wherein the first network is a successor network or a next-generation network of the second network.

[0011] A seventh aspect provides a mobility management apparatus, comprising: a receiving module for receiving a second message from a first core network device; and a sending module for performing any of the following based on the second message: if the second message includes second indication information, sending the context of a terminal in a first network to the first core network device; if the second message does not include the second indication information, sending the context of the terminal in a second network to the first core network device; wherein the first network is a successor network or a next-generation network of the second network, and the second indication information is used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; or instructing the terminal to perform registration or MRU in the first network.

[0012] Eighthly, a mobility management apparatus is provided, comprising: a receiving module for receiving an update message from a first core network device; and a processing module for performing any of the following based on the update message: if the update message includes third indication information, recording that the terminal is in a first network or is in a registered state in the first network; if the update message does not include the third indication information, recording that the terminal is in a second network or is in a registered state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the third indication information is used for at least one of the following: indicating that the update message corresponds to the first network; or instructing the terminal to perform registration or MRU in the first network.

[0013] A ninth aspect provides a mobility management apparatus configured to perform the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect, or implement the steps of the method described in the third aspect, or implement the steps of the method described in the fourth aspect.

[0014] In a tenth aspect, a terminal is provided, the terminal 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.

[0015] Eleventhly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send a first message to a first core network device corresponding to a first network; wherein the first message is used for registration or MRU of the first network, the first message includes first indication information, the first indication information is used to indicate that the terminal is in a registration state or from the first network, or, the first indication information is used to indicate that the terminal is in a registration state or from the second network in a second network, wherein the first network is a successor network or next-generation network of the second network.

[0016] In a twelfth aspect, a network-side device is provided, the network-side device 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 second aspect, or implementing the steps of the method as described in the third aspect, or implementing the steps of the method as described in the fourth aspect.

[0017] In a thirteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a first message from a terminal, wherein the first message is used for registration or MRU of a first network, and the first message includes first indication information; the processor is configured to obtain the context of the terminal in the first network according to the first indication information; wherein the first indication information is used to indicate that the terminal is in a registration state or from the first network, or the first indication information is used to indicate that the terminal is in a registration state or from the second network in a second network, wherein the first network is a successor network or a next-generation network of the second network.

[0018] In a fourteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a second message from a first core network device, and to perform any of the following based on the second message: if the second message includes second indication information, sending the context of a terminal in a first network to the first core network device; if the second message does not include the second indication information, sending the context of the terminal in a second network to the first core network device; wherein the first network is a successor network or a next-generation network of the second network, and the second indication information is used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; instructing the terminal to perform registration or MRU in the first network.

[0019] In a fifteenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive an update message from a first core network device; the processor is configured to perform any of the following based on the update message: if the update message includes third indication information, record that the terminal is in a first network or is in a registration state in the first network; if the update message does not include the third indication information, record that the terminal is in a second network or is in a registration state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the third indication information is used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform registration or MRU in the first network.

[0020] In a sixteenth 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 the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect.

[0021] In a seventeenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second, third, or fourth aspect.

[0022] Eighteenthly, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect.

[0023] In a nineteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect.

[0024] In this embodiment of the application, when performing mobility management of a terminal based on GUTI, the first indication information can be used to indicate to the first core network device corresponding to the first network whether the terminal was previously registered in the first network or the second network, or whether the terminal came from the first network or the second network. This allows the first core network device to clearly know which network the terminal was previously registered in or came from, thereby realizing mobility management of the terminal and improving mobility management performance. Attached Figure Description

[0025] Figure 1a This is a schematic diagram of the structure of a wireless communication system provided in an exemplary embodiment of this application.

[0026] Figure 1b This is one of the schematic diagrams of a wireless communication architecture provided in an exemplary embodiment of this application.

[0027] Figure 1c This is a second schematic diagram of a wireless communication architecture provided in an exemplary embodiment of this application.

[0028] Figure 2 This is one of the flowcharts illustrating a mobility management method provided in an exemplary embodiment of this application.

[0029] Figure 3a This is a second flowchart illustrating a mobility management method provided in an exemplary embodiment of this application.

[0030] Figure 3b This is one of the schematic diagrams of a sub-process of the mobility management method provided in an exemplary embodiment of this application.

[0031] Figure 3c This is a second schematic diagram of a sub-process of the mobility management method provided in an exemplary embodiment of this application.

[0032] Figure 4a This is one of the interactive flow diagrams of a mobility management method provided in an exemplary embodiment of this application.

[0033] Figure 4b This is the second schematic diagram of the interaction flow of the mobility management method provided in an exemplary embodiment of this application.

[0034] Figure 4cThis is the third schematic diagram of the interaction flow of the mobility management method provided in an exemplary embodiment of this application.

[0035] Figure 5 This is the third flowchart of a mobility management method provided in an exemplary embodiment of this application.

[0036] Figure 6 This is the fourth flowchart of a mobility management method provided in an exemplary embodiment of this application.

[0037] Figure 7 This is one of the structural schematic diagrams of a mobility management device provided in an exemplary embodiment of this application.

[0038] Figure 8 This is a second schematic diagram of the structure of a mobility management device provided in an exemplary embodiment of this application.

[0039] Figure 9 This is the third schematic diagram of the structure of the mobility management device provided in an exemplary embodiment of this application.

[0040] Figure 10 This is the fourth schematic diagram of the structure of a mobility management device provided in an exemplary embodiment of this application.

[0041] Figure 11 This is a schematic diagram of the structure of a communication device provided in an exemplary embodiment of this application.

[0042] Figure 12 This is a schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application.

[0043] Figure 13 This is a schematic diagram of the structure of a network-side device provided in an exemplary embodiment of this application. Detailed Implementation

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

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

[0046] 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.; 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.

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

[0048] Figure 1aThis 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. Furthermore, terminal 11 can be any of the terminals described above, or it can be a chip within a terminal, such as a modem chip, a system-on-chip (SoC), etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 can include access network equipment or core network equipment, wherein access network equipment can also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment can include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.In this context, a base station may be referred to as a Node B (NB), an Evolved Node B (eNB), a Next Generation Node B (gNB), a New Radio Node B (NRNode B), an Access Point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a Radio Base Station, a Radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The base station is not limited to any specific technical terminology. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.

[0049] 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 for description, 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 also be within the scope of protection of this application.

[0050] 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).

[0051] Based on this, such as Figure 1b and Figure 1c The diagram shows two 6G network architectures provided in this application. Among them, Figure 1b In the 6G network architecture shown, the 6G network and the 5G network share the access control network element, and the terminal can use either the 6G access network device or the 5G access network device to access the shared core network.

[0052] Figure 1c In the 6G network architecture shown, the 6G network and the 5G network each have independent access control network elements. Terminals can only access the 6G core network (6GC) through 6G access network equipment and access the 5G core network (5GC) through 5G access network equipment.

[0053] It is worth noting that (1) in Figure 1b In the network architecture shown, all 6G network elements are shared with 5G, while... Figure 1c In the network architecture shown, only some network elements are shared with 5G. These shared network elements are used for 6G and 5G interworking.

[0054] (2) In Figure 1b and Figure 1c In the network architecture shown, "e" represents an enhancement of 5G network elements. For example, eAMF represents enhanced AMF, which is obtained by enhancing 5G AMF. Figure 1b , Figure 1c The enhanced network elements in the network architecture shown can also be replaced with other names. For example, eAMF can be replaced with 6G mobility management function (MMF) or 6G AMF, etc. There are no restrictions here.

[0055] For the two aforementioned network architectures, related technologies may stipulate that the 5G GUTI and 6G GUTI have the same format to avoid modifications to the 5G AMF. However, when the 5G GUTI and 6G GUTI have the same format, the core network equipment (such as eAMF) cannot determine whether the terminal last registered with a 6G or 5G network when performing mobility management based on the GUTI, thus affecting mobility management performance. To address this, this application provides a mobility management scheme that can effectively determine whether the terminal last registered with a 6G or 5G network when performing mobility management based on the GUTI, thereby improving mobility management performance.

[0056] It should be noted that the 5G and 6G networks mentioned above are merely examples, meaning that the technical solutions provided in this application can be applied to, but are not limited to, 5G and 6G networks.

[0057] The technical solutions provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0058] like Figure 2 The diagram shown is a flowchart of a mobility management method 200 provided in an exemplary embodiment of this application. This method 200 can be executed by a terminal, but is not limited to that executed by a terminal; specifically, it can be executed by hardware and / or software installed in the terminal. In this embodiment, the method 200 may include at least the following steps.

[0059] S210, the terminal sends the first message to the first core network device corresponding to the first network.

[0060] Wherein, when the first network is a 6G network, the first core network device can be Figure 1b or Figure 1c eAMF in.

[0061] The first message is used for registration or MRU in the first network, which can be understood or replaced as: the first message is used for the terminal to register or MRU in the first network; or, the first message is used for the terminal to initiate a registration or MRU request in the first network.

[0062] The first message includes first indication information, which indicates that the terminal is in a registered state or from (move from or mobility from) the first network, or the first indication information indicates that the terminal is in a registered state or from the second network, wherein the first network is a successor network or next-generation network of the second network.

[0063] The phrase "the terminal is in a registered state on the first network" can be understood or replaced as: the terminal resides on the first network; or, the terminal is in a registered state on the first network before sending the first message; or, the terminal resides on the first network before sending the first message.

[0064] Similarly, "the terminal is in a registered state on the second network" can be understood or replaced as: the terminal resides on the second network; or, the terminal is in a registered state on the second network before sending the first message; or, the terminal resides on the second network before sending the first message.

[0065] In other words, when the GUTI corresponding to the first network and the GUTI corresponding to the second network have the same format, in this embodiment, when performing mobility management on the terminal based on the GUTI, the first indication information can be used to indicate to the first core network device corresponding to the first network whether the terminal was previously registered in the first network or the second network, or whether the terminal came from the first network or the second network. This allows the first core network device to clearly know which network the terminal was previously registered in or from, thereby realizing mobility management of the terminal and improving mobility management performance.

[0066] In some embodiments, the first indication information can be implemented in various ways. For example, the first indication information can be a newly introduced indication information specifically used to indicate which network the terminal is registered with or which network it comes from. Alternatively, the first indication information can also reuse existing indication information in related technologies.

[0067] In the case where "the first indication information reuses existing indication information in related technologies", the first indication information may include at least one of the second information and the UE status information element (UEstatus IE).

[0068] Where the first indication information includes the second information, the first message further includes the first GUTI corresponding to the first network. If the second information indicates that the type of the first GUTI is native, the second information also indicates that the terminal is registered with the first network or originates from the first network. Alternatively, if the second information indicates that the type of the first GUTI is mapped, the second information also indicates that the terminal is registered with the second network or originates from the second network.

[0069] In this embodiment, the first indication information being the second information can be understood as: by reusing the type indication information of the first GUTI (i.e., the second information) to indicate which network the terminal is registered in or which network it comes from, it is possible to avoid introducing new indication bits and save signaling overhead.

[0070] The fact that the first GUTI is of type Native can be understood as: the first GUTI is a GUTI allocated to the terminal by the core network device. For example, if the terminal sends the first GUTI through the first network, then the GUTI is allocated to the terminal by the core network device corresponding to the first network.

[0071] The fact that the first GUTI is of type "mapped" can be understood as follows: the first GUTI is obtained by mapping the GUTI corresponding to the previous network to which the terminal registered. For example, assuming that the terminal was previously registered on a 5G network, when the terminal moves from a 5G network to a 6G network, the first GUTI included in the first message is obtained by mapping the GUTI corresponding to the 5G network, that is, the first GUTI is of type "mapped".

[0072] When the first indication information includes a terminal status information element, the terminal status information element includes the terminal's registration status in various networks. For example, a first bit indicates whether the terminal is registered in a 4G network, a second bit indicates whether the terminal is registered in a 5G network, a third bit indicates whether the terminal is registered in a 6G network, and so on. Based on this, this embodiment can reuse the terminal status information element to indicate which network the terminal is registered in or from which network, thereby avoiding the introduction of new indication bits and saving signaling overhead. For example, when the bit corresponding to the first network in the terminal status information element has a first predetermined value, the terminal status information element is also used to indicate whether the terminal is registered in the first network or from the first network; or, when the bit corresponding to the second network in the terminal status information element has a second predetermined value, the terminal status information element is also used to indicate whether the terminal is registered in the second network or from the second network.

[0073] The first predetermined value and the second predetermined value may be the same or different.

[0074] The first predetermined value and the second predetermined value can be agreed upon by the protocol or configured by a higher layer. For example, the first predetermined value and / or the second predetermined value can be agreed upon by the protocol or configured by a higher layer to be 1. That is, when the bit corresponding to the first network in the terminal status information element is 1, it can be determined that the terminal is in a registered state in the first network or is from the first network. Alternatively, when the bit corresponding to the second network in the terminal status information element is 1, it can be determined that the terminal is in a registered state in the second network or is from the second network.

[0075] In some embodiments, the aforementioned first network being a successor or next-generation network of the second network can also be understood as the first network being proposed or developed based on the second network. For example, in this embodiment, the first network may include a 6G network, and the second network may include a 5G network or a 4G network; or, the first network may include a 5G network, and the second network may include a 4G network, ...

[0076] In some embodiments, the first network and the second network share the first core network device, for example, assuming... Figure 1b As shown, the first network is a 6G network, the second network is a 5G network, and the first core network device is an eAMF. Therefore, the 6G network and the 5G network share the eAMF.

[0077] Alternatively, the first network corresponds to the first core network device. For example, suppose... Figure 1c As shown, the first network is a 6G network, the second network is a 5G network, and the first core network device is an eAMF. Therefore, the 6G network corresponds to the eAMF and is not shared with the 5G network.

[0078] In some embodiments, after the first core network device completes the registration or MRU of the terminal in the first network according to the first message, it may send a response message to the terminal to instruct the terminal to accept the registration or MRU of the terminal in the first network.

[0079] Optionally, if the first message is a registration message, the response message can be a registration accept message. The registration accept message may carry a GUTI reassigned to the terminal by the first core network device for subsequent mobility management.

[0080] like Figure 3aThe diagram shown is a flowchart of a mobility management method 300 provided in an exemplary embodiment of this application. This method 300 can be executed by, but is not limited to, a first core network device, specifically by hardware and / or software installed in a terminal. In this embodiment, the method 300 may include at least the following steps.

[0081] S310, the first core network device receives the first message from the terminal.

[0082] Wherein, when the first network is a 6G network, the first core network device can be Figure 1b or Figure 1c eAMF in.

[0083] S320, the first core network device obtains the context of the terminal in the first network according to the first indication information.

[0084] Wherein, the first message is used for registration or MRU in the first network, which can be understood or replaced as: the first message is used for the terminal to register or MRU in the first network; or, the first message is used for the terminal to initiate a registration or MRU request in the first network.

[0085] The first message includes first indication information. Specifically, the first indication information indicates that the terminal is registered in or originates from the first network, or that the first indication information indicates that the terminal is registered in or originates from a second network, wherein the first network is a successor network or a next-generation network of the second network.

[0086] The phrase "the terminal is in a registered state on the first network" can be understood or replaced as: the terminal resides on the first network; or, the terminal is in a registered state on the first network before sending the first message; or, the terminal resides on the first network before sending the first message.

[0087] Similarly, "the terminal is in a registered state on the second network" can be understood or replaced as: the terminal resides on the second network; or, the terminal is in a registered state on the second network before sending the first message; or, the terminal resides on the second network before sending the first message.

[0088] In other words, when the GUTI corresponding to the first network and the GUTI corresponding to the second network have the same format, in this embodiment, when performing mobility management on the terminal based on the GUTI, the terminal can be determined whether it was previously registered in the first network or the second network, or whether it came from the first network or the second network, according to the first indication information sent by the terminal. Thus, through the indication of the first indication information, the first core network device can clearly know which network the terminal was previously registered in or from, thereby realizing mobility management of the terminal and improving mobility management performance.

[0089] In some embodiments, the first indication information can be implemented in various ways. For example, the first indication information can be a newly introduced indication information specifically used to indicate which network the terminal is registered with or which network it comes from. Alternatively, the first indication information can also reuse existing indication information in related technologies.

[0090] In the case where "the first indication information reuses existing indication information in related technologies", the first indication information may include at least one of the second information and the UE status information element (UEstatus IE).

[0091] Where the first indication information includes the second information, the first message further includes the first GUTI corresponding to the first network. If the second information indicates that the type of the first GUTI is native, the second information also indicates that the terminal is registered with the first network or originates from the first network. Alternatively, if the second information indicates that the type of the first GUTI is mapped, the second information also indicates that the terminal is registered with the second network or originates from the second network.

[0092] In this embodiment, the first indication information being the second information can be understood as: by reusing the type indication information of the first GUTI (i.e., the second information) to indicate which network the terminal is registered in or which network it comes from, it is possible to avoid introducing new indication bits and save signaling overhead.

[0093] The fact that the first GUTI is of type Native can be understood as: the first GUTI is a GUTI allocated to the terminal by the core network device. For example, if the terminal sends the first GUTI through the first network, this GUTI is allocated to the terminal by the core network device corresponding to the first network.

[0094] The fact that the first GUTI is of type "mapped" can be understood as follows: the first GUTI is obtained by mapping the GUTI corresponding to the previous network to which the terminal registered. For example, assuming the terminal was previously registered on a 5G network, when the terminal moves from a 5G network to a 6G network, the first GUTI included in the first message during 6G network registration or MRU is obtained by mapping the GUTI corresponding to the 5G network.

[0095] When the first indication information includes a terminal status information element, the terminal status information element includes the terminal's registration status in various networks. For example, a first bit indicates whether the terminal is registered in a 4G network, a second bit indicates whether the terminal is registered in a 5G network, a third bit indicates whether the terminal is registered in a 6G network, and so on. Based on this, this embodiment can reuse the terminal status information element to indicate which network the terminal is registered in or from which network, thereby avoiding the introduction of new indication bits and saving signaling overhead. For example, when the bit corresponding to the first network in the terminal status information element has a first predetermined value, the terminal status information element is also used to indicate whether the terminal is registered in the first network or from the first network; or, when the bit corresponding to the second network in the terminal status information element has a second predetermined value, the terminal status information element is also used to indicate whether the terminal is registered in the second network or from the second network.

[0096] The first predetermined value and the second predetermined value may be the same or different.

[0097] The first predetermined value and the second predetermined value can be agreed upon by the protocol or configured by a higher layer. For example, the first predetermined value and / or the second predetermined value can be agreed upon by the protocol or configured by a higher layer to be 1. That is, when the bit corresponding to the first network in the terminal status information element is 1, it can be determined that the terminal is in a registered state in the first network or is from the first network. Alternatively, when the bit corresponding to the second network in the terminal status information element is 1, it can be determined that the terminal is in a registered state in the second network or is from the second network.

[0098] In some embodiments, the aforementioned first network being a successor or next-generation network of the second network can also be understood as the first network being proposed or developed based on the second network. For example, in this embodiment, the first network may include a 6G network, and the second network may include a 5G network or a 4G network; or, the first network may include a 5G network, and the second network may include a 4G network, ...

[0099] In some embodiments, the first network and the second network share the first core network device, for example, assuming... Figure 1b As shown, the first network is a 6G network, the second network is a 5G network, and the first core network device is an eAMF. Therefore, the 6G network and the 5G network share the eAMF.

[0100] Alternatively, the first network corresponds to the first core network device. For example, suppose... Figure 1c As shown, the first network is a 6G network, the second network is a 5G network, and the first core network device is an eAMF. Therefore, the 6G network corresponds to the eAMF and is not shared with the 5G network.

[0101] In some embodiments, depending on the first indication information, the first core network device in S320 may obtain the context of the terminal in the first network in various ways. As an optional implementation, such as... Figure 3b As shown, the process by which the first core network device in S320 obtains the context of the terminal in the first network according to the first indication information may include the following step S3201.

[0102] S3201, when the first indication information is used to indicate that the terminal is in a registered state or from the first network, the first core network device requests the context of the terminal in the first network from the second core network device.

[0103] The second core network device can be understood as the core network device corresponding to the first network that the terminal previously registered with, that is, the first core network device is a new core network device relative to the second core network device.

[0104] In this embodiment, since the first core network device can determine that the terminal is moving between first networks based on the first indication information, the first core network device can request the terminal in the context of the first network from the second core network device corresponding to the first network that was previously registered, thereby effectively improving the registration or MRU process of the terminal in the first network and improving mobility management performance.

[0105] Optionally, the process by which the first core network device requests the terminal in the context of the first network from the second core network device in S3201 may include: the first core network device sending a second message to the second core network device, wherein the second message includes second indication information, which can be understood as an indication of the first network, such that the second indication information can be used for at least one of the following 11)-13).

[0106] 11) Indicate that the second message corresponds to the first network.

[0107] 12) Request the terminal in the context of the first network.

[0108] 13) Instruct the terminal to perform registration or MRU on the first network.

[0109] In this embodiment, when the first core network device obtains the context from the second core network device corresponding to the first network previously registered by the terminal, it implements at least one of the aforementioned 11)-13) through the second indication information. This enables the second core network device to determine whether the second message is a message from the first network or the second network based on whether the second message includes the second indication information, and then provides context feedback based on the determination result to improve mobility management efficiency.

[0110] For example, if the second core network device determines that the second message is a message from the first network when the second message includes the second indication information, it can send the context of the terminal in the first network to the first core network device.

[0111] Alternatively, if the second core network device determines that the second message is a message from the second network when the second message does not include the second indication information, it may send the context of the terminal in the second network to the first core network device.

[0112] Optionally, the third indication information may be represented by at least one of network access type, Subscription Permanent Identifier (SUPI), and first parameter. The first parameter indicates that the terminal performs registration or MRU on the first network; it may be a parameter newly introduced in this application or a parameter already existing in related technologies, and is not limited thereto.

[0113] Optionally, in this implementation, assuming the first network is a 6G network and the second network is a 5G network, then the first core network device and the second core network device can be, but are not limited to, the aforementioned types. Figure 1b , Figure 1c eAMF in.

[0114] As another alternative implementation, such as Figure 3c As shown, the process by which the first core network device in S320 obtains the context of the terminal in the first network according to the first indication information may include the following steps S3202-S3203.

[0115] S3202, when the first indication information is used to indicate that the terminal is in a registered state or from the second network, the first core network device first requests the context of the terminal in the second network from the second core network device.

[0116] The second core network device can be understood as the core network device corresponding to the second network that the terminal previously registered with, that is, the first core network device is a new core network device relative to the second core network device.

[0117] S3203, the first core network device maps the terminal in the context of the second network to the context of the first network.

[0118] Optionally, the process by which the first core network device requests the context of the terminal in the second network from the second core network device may include: the first core network device requesting the context of the terminal from the second core network device according to the terminal context acquisition process corresponding to the second network.

[0119] Since the first core network device can determine from the first indication information that the terminal moved from the second network to the first network, it can first request the context of the terminal in the second network from the second core network device corresponding to the second network that was previously registered, and then map the context of the terminal in the second network to the context in the first network, thereby effectively improving the registration or MRU process of the terminal in the first network and improving mobility management performance.

[0120] Furthermore, in this embodiment, by requesting the terminal's context in the second network according to the terminal context acquisition process corresponding to the second network, and then mapping it to the context of the first network, it can be ensured that there is no need to upgrade the second core network equipment corresponding to the second network, which is conducive to the rapid development of network services corresponding to the first network.

[0121] For example, assuming the first network is a 6G network and the second network is a 5G network, and the terminal moves or reselects from the 5G network to the 6G network and needs to register or perform an MRU on the 6G network, then the first core network device corresponding to the 6G network can obtain the terminal's context in the 5G network from the second core network device corresponding to the 5G network according to the terminal context acquisition process corresponding to the 5G network, and then map the terminal's context in the 5G network to the context of the 6G network. In other words, when the terminal moves or reselects from the 5G network to the 6G network, subsequent operations can be completed according to the 5G process, thus ensuring that the process can be completed quickly and avoiding the need to upgrade the second core network device corresponding to the 5G network, which is conducive to the rapid deployment of 6G services.

[0122] Optionally, in this implementation, assuming the first network is a 6G network and the second network is a 5G network, the first core network device can be, but is not limited to, the aforementioned... Figure 1b , Figure 1c In the eAMF, the second core network device can be, but is not limited to, the aforementioned Figure 1b , Figure 1c AMF in the middle.

[0123] In some embodiments, after the first core network device obtains the context of the terminal in the first network, it may also send a registration message to a third core network device; and / or send an update message to a fourth core network device.

[0124] The third core network device may be, but is not limited to, UDM, eUDM, etc., and the registration message may include third information, which is used to indicate the Radio Access Technology (RAT) corresponding to the first network. This allows the third core network device to distinguish whether the registration message is from the first network or the second network based on the third information, thereby improving mobility management efficiency.

[0125] The fourth core network device may be, but is not limited to, SMF, eSMF, etc. The first core network device sends the update message to the fourth core network device to instruct the fourth core network device to update the network context registered by the terminal according to the update message.

[0126] In this embodiment, the update message may include third indication information, which is used to indicate that the update message corresponds to the first network; and / or, the third indication information is used to instruct the terminal to perform registration or MRU in the first network, so that the fourth core network device can determine whether the update message is a message of the first network or the second network based on whether the update message includes the third indication information, so as to improve mobility management efficiency while avoiding upgrading the first core network device (such as AMF), which is conducive to the rapid development of network services corresponding to the first network.

[0127] For example, if the fourth core network device includes third indication information in the update message, it determines that the update message comes from the first network and records that the terminal is in the first network or is in a registered state in the first network.

[0128] Alternatively, if the fourth core network device does not include the third indication information in the update message, it determines that the update message comes from the second network and records that the terminal is in the second network or is in a registered state in the second network.

[0129] Optionally, the third indication information may be represented by at least one of network access type, SUPI, and the first parameter. The first parameter indicates that the terminal performs registration or MRU on the first network; it may be a parameter newly introduced in this application or a parameter already existing in related technologies, and is not limited thereto.

[0130] In some embodiments, after the first core network device completes the registration or MRU of the terminal in the first network according to the first message, it may send a response message to the terminal to instruct the terminal to accept the registration or MRU of the terminal in the first network.

[0131] Optionally, if the first message is a registration message, the response message can be a registration accept message. The registration accept message may carry a GUTI reassigned to the terminal by the first core network device for subsequent mobility management.

[0132] Based on the mobility management methods provided in the aforementioned method embodiments 200 and 300, for ease of understanding, the implementation process of the mobility management method provided in this application is described below with reference to examples. It is assumed that the first network is a 6G network and the second network is a 5G network.

[0133] Example 1: The terminal moves between 6G networks. Assuming the terminal was previously registered on a 6G network and has stored the first GUTI corresponding to the 6G network (also denoted as the 6G GUTI), then, as Figure 4a As shown, when the terminal needs to re-register on the 6G network (e.g., after the user turns the device off and on again) or execute an MRU, the implementation process of the mobility management method is as follows.

[0134] S411, the terminal sends a first message, such as a registration message, to the first eAMF. The registration message may include a first GUTI and first indication information, the first indication information indicating that the terminal is registered in the 6G network or is from the 6G network.

[0135] Optionally, the first indication information includes at least one of second information and terminal status information elements. The second information is used to indicate that the type of the first GUTI is native.

[0136] The bit in the terminal status information element that corresponds to the 6G network (such as the 6GMM-REGISTERED bit) is set to a predetermined value, such as 1, that is, the terminal status information element indicates that the terminal is in the registered state in the 6G network.

[0137] S412, the first eAMF requests the context of the terminal in the 6G network from the second eAMF (i.e., the eAMF that was registered last time or previously) according to the first instruction information.

[0138] Optionally, when the first eAMF requests the terminal in the 6G network context from the second eAMF based on the first indication information, it may send a second message, such as Namf_Communication_UEContextTransfer, to the second eAMF.

[0139] The second message includes second indication information, wherein the second indication information is used for at least one of the following a)-c).

[0140] a) Indicates that the second message corresponds to the 6G network.

[0141] b) Request the terminal in the context of the 6G network.

[0142] c) Instruct the terminal to perform registration or MRU on the 6G network.

[0143] S413, the second eAMF sends the context of the terminal in the 6G network to the first eAMF according to the second message.

[0144] Optionally, if the second eAMF includes second indication information in the second message, it determines that the second message is a message of the 6G network and sends the terminal's context in the 6G network to the first eAMF.

[0145] Optionally, the terminal's context in the 6G network can be carried through the Namf_Communication_UEContextTransfer response.

[0146] S414, the first eAMF sends a registration message to the eUDM to register the terminal.

[0147] The registration message includes third information, which is used to indicate the RAT corresponding to the 6G network.

[0148] Optionally, the registration message can be Nudm_UECM_Registration.

[0149] S415, the first eAMF obtains the 6G subscription information of the terminal from the UDM.

[0150] S416, the first eAMF sends an update message to the eSMF.

[0151] The update message includes third indication information, which is used for at least one of the following a)-b.

[0152] a) Indicates that the update message corresponds to the 6G network.

[0153] b) Instruct the terminal to perform registration or MRU on the 6G network.

[0154] S417, eSMF determines that the update message is a message of the 6G network based on the third indication information in the update message, and records that the terminal is in the 6G network or is in the registration state of the 6G network.

[0155] Optionally, the update message can be, but is not limited to, Nsmf_PDUSession_UpdateSMContext.

[0156] S418, the first eAMF sends a response message corresponding to the first message, such as a registrationaccept message, to the terminal.

[0157] The response message may include a 6G GUTI newly allocated to the terminal by the first eAMF.

[0158] In Example 1, the first eAMF determines that the terminal was previously in a registered state on the 6G network based on the first indication information. Therefore, it can obtain the context of the terminal on the 6G network from the second eAMF corresponding to the previously registered 6G network, ensuring that the 6G registration or MRU process is completed quickly.

[0159] Furthermore, for messages between the first eAMF and the second eAMF, eUDM, and eSMF, by carrying 6G indications (such as third information, third indication information, or second indication information), the second eAMF, eUDM, and eSMF can determine that the received message is a message corresponding to the 6G network based on the 6G indications, thereby avoiding the need to upgrade the first eAMF and facilitating the rapid deployment of 6G services.

[0160] It is understood that the relevant descriptions of each step in this Example 1 can be referred to the descriptions of the aforementioned method embodiments 200 or 300, and will not be repeated here. In addition, this Example 1 may include more or fewer steps than the aforementioned S411-S418, and there is no limitation here.

[0161] Example 2: The terminal moves from a 5G network to a 6G network. Assuming the terminal was previously registered on a 5G network and has stored the corresponding 5G network GUTI (which can also be referred to as the 5G GUTI), then, as Figure 4b As shown, when the terminal needs to register on a 6G network to enter the connected state, the implementation process of the mobility management method is as follows.

[0162] S421, the terminal sends a first message, such as a registration message, to the first eAMF. The registration message may include a first GUTI and first indication information, the first indication information indicating that the terminal is registered with the 5G network or is from the 5G network.

[0163] Optionally, the first indication information includes at least one of second information and terminal status information elements. The second information is used to indicate that the type of the first GUTI is mapped.

[0164] The bit in the terminal status information element that corresponds to the 5G network (such as the 5GMM-REGISTERED bit) is set to a predetermined value, such as 1, that is, the terminal status information element indicates that the terminal is in the registered state in the 5G network.

[0165] S422, the first eAMF requests the terminal in the context of the 5G network from the second AMF (i.e., the 5GAMF that was registered last or previously) based on the first indication information.

[0166] Optionally, when the first eAMF requests the terminal in the context of the 5G network from the second AMF according to the first indication information, it may send a second message to the second AMF, wherein the second message includes a 5G GUTI, which is obtained by the first eAMF based on the first GUTI.

[0167] S423, the second AMF sends the terminal's 5G network context, i.e., 5G Context, to the first eAMF based on the 5G GUTI.

[0168] Optionally, the terminal's context in the 5G network can be carried through the Namf_Communication_UEContextTransfer response.

[0169] S424, after receiving the context of the terminal in the 5G network, the first eAMF locally maps the context of the terminal in the 5G network to the context of the 6G network, i.e., 6G Context.

[0170] S425, the first eAMF sends a registration message to the UDM to register the terminal.

[0171] The registration message includes third information, which is used to indicate the RAT corresponding to the 6G network.

[0172] Optionally, the registration message can be Nudm_UECM_Registration.

[0173] S426, the first eAMF sends an update message to the eSMF.

[0174] The update message includes third indication information, which is used for at least one of the following a)-b.

[0175] a) Indicates that the update message corresponds to the 6G network.

[0176] b) Instruct the terminal to perform registration or MRU on the 6G network.

[0177] Optionally, the update message can be, but is not limited to, Nsmf_PDUSession_UpdateSMContext.

[0178] S427, eSMF determines that the update message is a message from the 6G network based on the third indication information in the update message, and records that the terminal is in the 6G network or is in the registration state in the 6G network.

[0179] S428, the first eAMF sends a response message corresponding to the first message, such as a registrationaccept message, to the terminal.

[0180] The response message may include a 6G GUTI newly allocated to the terminal by the first eAMF.

[0181] In this Example 2, when the terminal moves from the 5G network or reselects to the 6G network, it can complete the subsequent operations according to the 5G process to ensure that the registration or MRU process can be completed quickly.

[0182] Furthermore, by carrying 6G indications (such as third indication information) for messages between the first eAMF and the eSMF, the eSMF can determine that the received message is a message corresponding to the 6G network based on the 6G indication, thereby avoiding the need to upgrade the first eAMF and facilitating the rapid deployment of 6G services.

[0183] It is understood that the relevant descriptions of each step in this Example 2 can be referred to the descriptions of the aforementioned method embodiments 200 or 300, and will not be repeated here. In addition, this Example 2 may include more or fewer steps than the aforementioned S421-S428, and there is no limitation here.

[0184] Example 3: The terminal moves from a 6G network to a 5G network. Assuming the terminal was previously registered on a 6G network and has stored the corresponding GUTI for the 6G network (also referred to as the 6G GUTI), then, as Figure 4c As shown, when the terminal moves or reselects to a 5G network and needs to register on the 5G network and enter the connected state, the implementation process of the mobility management method is as follows.

[0185] S431, the terminal sends a first message, such as a registration message, to the first AMF. The registration message may include a first GUTI and first indication information, the first indication information indicating that the terminal is registered in the 6G network or is from the 6G network.

[0186] Optionally, the first indication information includes at least one of second information and terminal status information elements. The second information is used to indicate that the type of the first GUTI is native.

[0187] The bit in the terminal status information element that corresponds to the 6G network (such as the 6GMM-REGISTERED bit) is set to a predetermined value, such as 1, that is, the terminal status information element indicates that the terminal is in the registered state in the 6G network.

[0188] S432, the first AMF obtains the terminal's context in the 5G network from the second eAMF (i.e., the AMF corresponding to the network that was last registered) according to the first instruction information and the 5G process.

[0189] That is, when the first eAMF requests the terminal in the context of the 6G network from the second eAMF based on the first indication information, the second message sent to the second eAMF does not include the second indication information.

[0190] S433, the second eAMF determines that the second message is a 5G network message based on the fact that the second message does not include the second indication information, and maps the terminal's 6G network context to the terminal's 5G network context.

[0191] S434, the second eAMF sends the terminal in the context of the 5G network to the first AMF.

[0192] Optionally, the terminal's context in the 5G network can be carried through the Namf_Communication_UEContextTransfer response.

[0193] S435, the first AMF sends a registration message to the UDM according to the 5G process.

[0194] Optionally, the registration message can be Nudm_UECM_Registration.

[0195] S436, the first AMF sends an update message to the eSMF according to the 5G procedure.

[0196] Optionally, the update message can be, but is not limited to, Nsmf_PDUSession_UpdateSMContext.

[0197] S437, eSMF determines that the update message is a 5G network message based on the fact that the received update message does not include third indication information, and records that the terminal is in a 5G network or is in a 5G network registration state.

[0198] S438, the first AMF sends a response message corresponding to the first message to the terminal, such as a registration accept message.

[0199] The response message may include the 5G GUTI allocated to the terminal by the first AMF.

[0200] In Example 3, when the terminal moves from the 6G network or reselects to the 5G network, if it selects the un-upgraded 5G AMF (i.e., the aforementioned first AMF), it can complete the subsequent operations according to the 5G process without upgrading the 5G AMF, ensuring that the process can be completed quickly.

[0201] Furthermore, for messages between the first AMF and the eSMF, by indicating whether or not a 6G indication (such as a third indication information) is carried, the eSMF can determine whether the received message corresponds to a 6G network or a 5G network, thereby avoiding the need to upgrade the 5G AMF and facilitating the rapid deployment of 6G services.

[0202] It is understood that the relevant descriptions of each step in this Example 3 can be referred to the descriptions of the aforementioned method embodiments 200 or 300, and will not be repeated here. In addition, this Example 3 may include more or fewer steps than the aforementioned S431-S438, and there is no limitation here.

[0203] like Figure 5 The diagram shown illustrates a flow chart of a mobility management method 500 provided in an exemplary embodiment of this application. This method 500 can be executed by, but is not limited to, a second core network device, specifically by hardware and / or software installed in the second core network device. In this embodiment, the method 500 may include at least the following steps.

[0204] S510, the second core network device receives a second message from the first core network device; S520, the second core network device performs a first operation based on the second message, the first operation including any of the following.

[0205] If the second message includes second instruction information, the terminal in the context of the first network is sent to the first core network device. If the second instruction information is not included in the second message, the context of the terminal in the second network is sent to the first core network device.

[0206] Wherein, the first network is a successor network or next-generation network of the second network, and the second indication information is used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; instructing the terminal to perform registration or MRU in the first network.

[0207] In some embodiments, the second indication information is represented by at least one of the following: network access type; Subscription Permanent Identifier (SUPI); and a first parameter indicating that the terminal performs registration or MRU on the first network.

[0208] In some embodiments, the Globally Unique Temporary Terminal Identifier (GUTI) corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0209] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0210] This method embodiment 500 has the same or corresponding technical features as the aforementioned method embodiments 200 or 300. Therefore, each implementation process in this method embodiment 500 can refer to the relevant descriptions in the aforementioned method embodiments 200 or 300 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0211] like Figure 6 The diagram shown illustrates a flow chart of a mobility management method 600 provided in an exemplary embodiment of this application. This method 600 can be executed, but is not limited to, by a fourth core network device, specifically by hardware and / or software installed in the fourth core network device. In this embodiment, the method 600 may include at least the following steps.

[0212] S610, the fourth core network device receives update messages from the first core network device; S620, the fourth core network device performs a second operation based on the update message, the second operation including any of the following.

[0213] If the update message includes third indication information, it records that the terminal is in the first network or is in a registered state in the first network.

[0214] If the third indication information is not included in the update message, the terminal is recorded as being in the second network or in a registered state in the second network.

[0215] Wherein, the first network is the successor network or next-generation network of the second network, and the third indication information is used for at least one of the following: indicating that the update message corresponds to the first network; indicating that the terminal performs a registration or mobility registration update MRU on the first network.

[0216] In some embodiments, the third indication information is represented by at least one of the following: network access type; Subscription Permanent Identifier (SUPI); and a first parameter indicating that the terminal performs registration or MRU on the first network.

[0217] In some embodiments, the Globally Unique Temporary Terminal Identifier (GUTI) corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0218] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0219] This method embodiment 600 has the same or corresponding technical features as the aforementioned method embodiments 200 or 300. Therefore, each implementation process in this method embodiment 600 can refer to the relevant descriptions in the aforementioned method embodiments 200 or 300 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0220] The mobility management method provided in this application can be executed by a mobility management device. This application uses the example of a mobility management device executing the mobility management method to illustrate the mobility management device provided in this application.

[0221] This application provides a mobility management device. As an example, the 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.

[0222] The 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.

[0223] Specifically, see Figure 7 When the mobility management device is a terminal or a component within a terminal, the mobility management device 700 includes a sending module 710 for sending a first message to a first core network device corresponding to a first network; wherein the first message is used for registration or MRU in the first network, and the first message includes first indication information, the first indication information being used to indicate that the terminal is in a registered state in the first network or is from the first network, or the first indication information being used to indicate that the terminal is in a registered state in a second network or is from the second network, wherein the first network is a successor network or next-generation network of the second network.

[0224] Optionally, the device 700 further includes a receiving module 720, configured to receive a response message sent by the first core network device, the response message corresponding to the first message.

[0225] In some embodiments, where the first message further includes a first globally unique temporary terminal identifier (GUTI) corresponding to the first network, the first indication information includes second information; wherein, where the second information is used to indicate that the type of the first GUTI is native, the second information is also used to indicate that the terminal is registered in the first network or is from the first network; or, where the second information is used to indicate that the type of the first GUTI is mapped, the second information is also used to indicate that the terminal is registered in the second network or is from the second network.

[0226] In some embodiments, the first indication information includes a terminal status information element; wherein, when the bit in the terminal status information element corresponding to the first network is a first predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or is from the first network; or, when the bit in the terminal status information element corresponding to the second network is a second predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or is from the second network.

[0227] In some embodiments, the GUTI corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0228] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0229] In some embodiments, the first network and the second network share the first core network device.

[0230] The mobility management device 700 provided in this application embodiment can achieve Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0231] See Figure 8When the mobility management device is a network-side device or a component of a network-side device, the mobility management device 800 includes a receiving module 810 for receiving a first message from a terminal, wherein the first message is for registration or MRU of a first network, and the first message includes first indication information; and a processing module 820 for obtaining the context of the terminal in the first network according to the first indication information; wherein the first indication information is used to indicate that the terminal is in a registered state in the first network or from the first network, or the first indication information is used to indicate that the terminal is in a registered state in a second network or from the second network, wherein the first network is a successor network or a next-generation network of the second network.

[0232] In some embodiments, where the first message further includes a first globally unique temporary terminal identifier (GUTI) corresponding to the first network, the first indication information includes second information; wherein, where the second information is used to indicate that the type of the first GUTI is native, the second information is also used to indicate that the terminal is registered in the first network or is from the first network; or, where the second information is used to indicate that the type of the first GUTI is mapped, the second information is also used to indicate that the terminal is registered in the second network or is from the second network.

[0233] In some embodiments, the first indication information includes a terminal status information element; wherein, when the bit in the terminal status information element corresponding to the first network is a first predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or is from the first network; or, when the bit in the terminal status information element corresponding to the second network is a second predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or is from the second network.

[0234] In some embodiments, obtaining the context of the terminal in the first network according to the first indication information includes: requesting the context of the terminal in the first network from a second core network device when the first indication information indicates that the terminal is in a registered state or from the first network.

[0235] In some embodiments, requesting the terminal to the second core network device in the context of the first network includes: sending a second message to the second core network device; wherein the second message includes second indication information, the second indication information being used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; instructing the terminal to perform registration or MRU in the first network.

[0236] In some embodiments, obtaining the context of the terminal in the first network according to the first indication information includes: requesting the context of the terminal in the second network from a second core network device when the first indication information indicates that the terminal is in a registered state in the second network or is from the second network; and mapping the context of the terminal in the second network to the context in the first network.

[0237] In some embodiments, requesting the context of the terminal in the second network from the second core network device includes: requesting the context of the terminal from the second core network device according to the terminal context acquisition process corresponding to the second network.

[0238] In some embodiments, the apparatus 500 further includes a sending module for at least one of the following: sending a registration message to a third core network device, wherein the registration message includes third information, the third information being used to indicate the Radio Access Technology (RAT) corresponding to the first network; sending an update message to a fourth core network device, the update message including third indication information, the third indication information being used for at least one of the following: indicating that the update message corresponds to the first network; instructing the terminal to perform registration or MRU on the first network.

[0239] In some embodiments, at least one of the second indication information and the third indication information is represented by at least one of the following: network access type; Subscription Permanent Identifier (SUPI); and a first parameter indicating that the terminal performs registration or MRU on the first network.

[0240] In some embodiments, the GUTI corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0241] In some embodiments, the first network includes a 6G network, and the second network includes either a 5G network or a 4G network.

[0242] In some embodiments, the first network and the second network share the first core network device.

[0243] The mobility management device provided in this application embodiment can achieve Figure 3aThe various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0244] See Figure 9 When the mobility management device is a network-side device or a component of a network-side device, the mobility management device 900 includes a receiving module 910 for receiving a second message from a first core network device; and a sending module 920 for performing any of the following based on the second message: if the second message includes second indication information, sending the context of the terminal in the first network to the first core network device; if the second message does not include the second indication information, sending the context of the terminal in the second network to the first core network device; wherein the first network is a successor network or a next-generation network of the second network, and the second indication information is used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; or instructing the terminal to perform registration or MRU in the first network.

[0245] In some embodiments, the second indication information is represented by at least one of the following: network access type; Subscription Permanent Identifier (SUPI); and a first parameter indicating that the terminal performs registration or MRU on the first network.

[0246] In some embodiments, the Globally Unique Temporary Terminal Identifier (GUTI) corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0247] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0248] The mobility management device 900 provided in this application embodiment can achieve Figure 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0249] See Figure 10When the mobility management device is a network-side device or a component of a network-side device, the mobility management device 1000 includes a receiving module 1010 for receiving an update message from a first core network device; and a processing module 1020 for performing any of the following based on the update message: if the update message includes third indication information, recording that the terminal is in a first network or is in a registered state in the first network; if the update message does not include the third indication information, recording that the terminal is in a second network or is in a registered state in the second network; wherein the first network is a successor network or a next-generation network of the second network, and the third indication information is used for at least one of the following: indicating that the update message corresponds to the first network; or instructing the terminal to perform registration or MRU in the first network.

[0250] In some embodiments, the third indication information is represented by at least one of the following: network access type; Subscription Permanent Identifier (SUPI); and a first parameter indicating that the terminal performs registration or MRU on the first network.

[0251] In some embodiments, the Globally Unique Temporary Terminal Identifier (GUTI) corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0252] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0253] The mobility management device 1000 provided in this application embodiment can achieve... Figure 6 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0254] like Figure 11 As shown, this application embodiment also provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores programs or instructions that can run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instructions executed by the processor 1101 implement the various steps of the mobility management method embodiment 200 described above, and can achieve the same technical effect. When the communication device 1100 is a network-side device, the program or instructions executed by the processor 1101 implement the various steps of the mobility management method embodiments 300, 500, or 600 described above, and can achieve the same technical effect. To avoid repetition, further details are omitted here.

[0255] This application embodiment 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, for example... Figure 2The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 7 The mobility management device 700 shown. Specifically, Figure 12 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application. The terminal 1200 includes, but is not limited to, at least some of the following components: radio frequency unit 1201, network module 1202, audio output unit 1203, input unit 1204, sensor 1205, display unit 1206, user input unit 1207, interface unit 1208, memory 1209, and processor 1210.

[0256] Those skilled in the art will understand that the terminal 1200 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 1210 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 12 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.

[0257] It should be understood that, in this embodiment, the input unit 1204 may include a graphics processor 12041 and a microphone 12042. The graphics processor 12041 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 1206 may include a display panel 12061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include a touch detection device and a touch controller. Other input devices 12072 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.

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

[0259] The memory 1209 can be used to store software programs or instructions, as well as various data. The memory 1209 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 1209 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 1209 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0260] Processor 1210 may include one or more processing units; optionally, processor 1210 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 1210.

[0261] The radio frequency unit 1201 is used to send a first message to the first core network device corresponding to the first network; wherein the first message is used for registration or MRU of the first network, and the first message includes first indication information, which is used to indicate that the terminal is in a registration state or from the first network, or the first indication information is used to indicate that the terminal is in a registration state or from the second network in the second network, wherein the first network is the successor network or next-generation network of the second network.

[0262] Optionally, the radio frequency unit 1201 is further configured to receive a response message sent by the first core network device, the response message corresponding to the first message.

[0263] In some embodiments, where the first message further includes a first globally unique temporary terminal identifier (GUTI) corresponding to the first network, the first indication information includes second information; wherein, where the second information is used to indicate that the type of the first GUTI is native, the second information is also used to indicate that the terminal is registered in the first network or is from the first network; or, where the second information is used to indicate that the type of the first GUTI is mapped, the second information is also used to indicate that the terminal is registered in the second network or is from the second network.

[0264] In some embodiments, the first indication information includes a terminal status information element; wherein, when the bit in the terminal status information element corresponding to the first network is a first predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or is from the first network; or, when the bit in the terminal status information element corresponding to the second network is a second predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or is from the second network.

[0265] In some embodiments, the GUTI corresponding to the first network has the same format as the GUTI corresponding to the second network.

[0266] In some embodiments, the first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

[0267] In some embodiments, the first network and the second network share the first core network device.

[0268] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0269] This application embodiment 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, for example... Figure 3a or Figure 5 or Figure 6The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0270] Specifically, embodiments of this application also provide a network-side device. For example... Figure 13 As shown, the network-side device 1300 includes: a processor 1301, a network interface 1302, and a memory 1303. This network-side device can be... Figure 8 or Figure 9 or Figure 10 The mobility management device shown. The network interface 1302 is, for example, a common public radio interface (CPRI).

[0271] Specifically, the network-side device 1300 in this application embodiment further includes: instructions or programs stored in memory 1303 and executable on processor 1301, wherein processor 1301 calls the instructions or programs in memory 1303 to execute. Figure 8 or Figure 9 or Figure 10 The steps in the methods executed by each module are shown.

[0272] For example, the processor 1301 executes instructions or programs stored in the memory 1303. Figure 8 or Figure 9 or Figure 10 In the case of the methods executed by the modules shown, the network interface 1302 in the network-side device 1300 can be used to receive a first message from the terminal, wherein the first message is used for registration or MRU of the first network, and the first message includes first indication information; the processor 1301 can be used to obtain the context of the terminal in the first network according to the first indication information; wherein the first indication information is used to indicate that the terminal is in a registration state in the first network or from the first network, or the first indication information is used to indicate that the terminal is in a registration state in a second network or from the second network, wherein the first network is a successor network or next-generation network of the second network.

[0273] For example, the processor 1301 executes instructions or programs stored in the memory 1303. Figure 9In the case of the methods executed by the modules shown, the network interface 1302 in the network-side device 1300 can be used to receive a second message from the first core network device; and to perform any of the following based on the second message: if the second message includes second indication information, send the context of the terminal in the first network to the first core network device; if the second message does not include the second indication information, send the context of the terminal in the second network to the first core network device; wherein the first network is a successor network or next-generation network of the second network, and the second indication information is used for at least one of the following: indicating that the second message corresponds to the first network; requesting the terminal in the context of the first network; instructing the terminal to perform registration or MRU in the first network.

[0274] For example, the processor 1301 may execute instructions or programs stored in the memory 1303. Figure 10 In the case of the methods executed by the modules shown, the network interface 1302 in the network-side device 1300 can be used to receive update messages from the first core network device; the processor 1301 can be used to perform any of the following according to the update message: if the update message includes third indication information, record that the terminal is in the first network or is in a registration state in the first network; if the update message does not include the third indication information, record that the terminal is in the second network or is in a registration state in the second network; wherein, the first network is the successor network or next-generation network of the second network, and the third indication information is used for at least one of the following: indicating that the update message corresponds to the first network; indicating that the terminal performs registration or MRU in the first network.

[0275] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant descriptions of method embodiment 300, 500 or 600, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0276] 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 mobility management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

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

[0278] 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 mobility management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0280] 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 mobility management method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0281] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to implement the various processes of the above-described mobility management method embodiment 200, and the network-side device can be used to implement the various processes of the above-described mobility management method embodiments 300, 500, or 600, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

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

[0284] 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 mobility management method, characterized in that, include: The terminal sends a first message to the first core network device corresponding to the first network; The first message is used for registration or mobility registration update (MRU) on the first network. The first message includes first indication information, which indicates that the terminal is in a registered state on the first network or is from the first network. Alternatively, the first indication information indicates that the terminal is in a registered state on a second network or is from the second network. The first network is a successor network or a next-generation network of the second network.

2. The method as described in claim 1, characterized in that, If the first message also includes the first globally unique temporary terminal identifier (GUTI) corresponding to the first network, the first indication information includes the second information. Wherein, if the second information is used to indicate that the type of the first GUTI is a native type, the second information is also used to indicate that the terminal is registered in the first network or is from the first network; or... In cases where the second information is used to indicate that the type of the first GUTI is a mapped type, the second information is also used to indicate that the terminal is in a registered state on the second network or is from the second network.

3. The method as described in claim 1 or 2, characterized in that, The first indication information includes terminal status information elements; Wherein, if the bit corresponding to the first network in the terminal status information element takes a first predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or originates from the first network; or... When the bit corresponding to the second network in the terminal status information element takes a second predetermined value, the terminal status information element is also used to indicate that the terminal is in a registered state or is from the second network.

4. The method according to any one of claims 1-3, characterized in that, The GUTI corresponding to the first network has the same format as the GUTI corresponding to the second network.

5. The method according to any one of claims 1-4, characterized in that, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

6. The method according to any one of claims 1-5, characterized in that, The first network and the second network share the first core network equipment.

7. A mobility management method, characterized in that, include: The first core network device receives a first message from a terminal, wherein the first message is used for registration or mobility registration update MRU of the first network, and the first message includes first indication information; The first core network device obtains the context of the terminal in the first network based on the first indication information; Wherein, the first indication information is used to indicate that the terminal is in a registered state in the first network or from the first network, or the first indication information is used to indicate that the terminal is in a registered state in the second network or from the second network, wherein the first network is a successor network or a next-generation network of the second network.

8. The method as described in claim 7, characterized in that, If the first message also includes the first globally unique temporary terminal identifier (GUTI) corresponding to the first network, the first indication information includes the second information. Wherein, in the case where the second information is used to indicate that the type of the first GUTI is a native type; the second information is also used to indicate that the terminal is registered in the first network or is from the first network; or... In cases where the second information is used to indicate that the type of the first GUTI is a mapped type, the second information is also used to indicate that the terminal is in a registered state on the second network or is from the second network.

9. The method as described in claim 7 or 8, characterized in that, The first indication information includes terminal status information elements; Wherein, if the bit corresponding to the first network in the terminal status information element takes a first predetermined value, the terminal status information element is further used to indicate that the terminal is in a registered state or originates from the first network; or... When the bit corresponding to the second network in the terminal status information element takes a first predetermined value, the terminal status information element is also used to indicate that the terminal is in a registered state or is from the second network.

10. The method according to any one of claims 7-9, characterized in that, The first core network device obtains the context of the terminal in the first network based on the first indication information, including: When the first indication information is used to indicate that the terminal is in a registered state or from the first network, the first core network device requests the context of the terminal in the first network from the second core network device.

11. The method as described in claim 10, characterized in that, The first core network device requests the terminal's context in the first network from the second core network device, including: The first core network device sends a second message to the second core network device; The second message includes a second indication message, which is used for at least one of the following: The second message corresponds to the first network; The terminal is requested to be in the context of the first network; The terminal is instructed to perform registration or MRU on the first network.

12. The method according to any one of claims 7-9, characterized in that, The first core network device obtains the context of the terminal in the first network based on the first indication information, including: When the first indication information is used to indicate that the terminal is in a registered state or from the second network, the first core network device requests the context of the terminal in the second network from the second core network device; The first core network device maps the terminal's context in the second network to its context in the first network.

13. The method as described in claim 12, characterized in that, The first core network device requests the context of the terminal in the second network from the second core network device, including: The first core network device requests the terminal's context from the second core network device according to the terminal context acquisition process corresponding to the second network.

14. The method according to any one of claims 7-13, characterized in that, The method further includes at least one of the following: The first core network device sends a registration message to the third core network device, wherein the registration message includes third information, which is used to indicate the Radio Access Technology (RAT) corresponding to the first network; The first core network device sends an update message to the fourth core network device, the update message including third indication information, the third indication information being used for at least one of the following: The update message is indicated to correspond to the first network; The terminal is instructed to perform registration or MRU on the first network.

15. The method as described in claim 11 or 14, characterized in that, At least one of the second indication information and the third indication information is represented by at least one of the following: Network access type; Sign a permanent SUPI logo; The first parameter is used to indicate that the terminal performs registration or MRU in the first network.

16. The method according to any one of claims 7-15, characterized in that, The GUTI corresponding to the first network has the same format as the GUTI corresponding to the second network.

17. The method according to any one of claims 7-15, characterized in that, The first network includes a 6G network, and the second network includes either a 5G network or a 4G network.

18. The method according to any one of claims 7-15, characterized in that, The first network and the second network share the first core network equipment.

19. A mobility management method, characterized in that, include: The second core network device receives a second message from the first core network device; The second core network device performs any of the following actions based on the second message: If the second message includes second indication information, the terminal sends a message to the first core network device in the context of the first network. If the second indication information is not included in the second message, the context of the terminal in the second network is sent to the first core network device; Wherein, the first network is a successor network or next-generation network of the second network, and the second indication information is used for at least one of the following: The second message corresponds to the first network; The terminal is requested to be in the context of the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

20. The method as described in claim 19, characterized in that, The second indication information is represented by at least one of the following: Network access type; Sign a permanent SUPI logo; The first parameter is used to indicate that the terminal performs registration or MRU in the first network.

21. The method as described in claim 19 or 20, characterized in that, The Globally Unique Temporary Terminal Identifier (GUTI) corresponding to the first network has the same format as the GUTI corresponding to the second network.

22. The method as described in claim 19 or 20, characterized in that, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

23. A mobility management method, characterized in that, include: The fourth core network device receives update messages from the first core network device; The fourth core network device performs any of the following actions based on the update message: If the update message includes third indication information, it indicates that the terminal is in the first network or is in a registered state in the first network. If the third indication information is not included in the update message, the terminal is recorded as being in the second network or in a registered state in the second network. Wherein, the first network is the successor network or next-generation network of the second network, and the third indication information is used for at least one of the following: The update message is indicated to correspond to the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

24. The method as described in claim 23, characterized in that, The third indication information is represented by at least one of the following: Network access type; Sign a permanent SUPI logo; The first parameter is used to indicate that the terminal performs registration or MRU in the first network.

25. The method as described in claim 23 or 24, characterized in that, The Globally Unique Temporary Terminal Identifier (GUTI) corresponding to the first network has the same format as the GUTI corresponding to the second network.

26. The method as described in claim 23 or 24, characterized in that, The first network includes a 6G network, and the second network includes one of a 5G network and a 4G network.

27. A mobility management device, characterized in that, include: The sending module is used to send a first message to the first core network device corresponding to the first network; The first message is used for registration or mobility registration update (MRU) of the first network. The first message includes first indication information, which indicates that the terminal is in a registered state or from the first network, or the first indication information indicates that the terminal is in a registered state or from the second network, wherein the first network is a successor network or next-generation network of the second network.

28. The apparatus as claimed in claim 27, characterized in that, If the first message also includes the first globally unique temporary terminal identifier (GUTI) corresponding to the first network, the first indication information includes the second information. Wherein, if the second information is used to indicate that the type of the first GUTI is a native type, the second information is also used to indicate that the terminal is registered in the first network or is from the first network; or... In cases where the second information is used to indicate that the type of the first GUTI is a mapped type, the second information is also used to indicate that the terminal is in a registered state on the second network or is from the second network.

29. A mobility management device, characterized in that, include: A receiving module is configured to receive a first message from a terminal, wherein the first message is for a registration or mobility registration update (MRU) of a first network, and the first message includes first indication information; The processing module is configured to obtain the context of the terminal in the first network based on the first indication information; Wherein, the first indication information is used to indicate that the terminal is in a registered state in the first network or from the first network, or the first indication information is used to indicate that the terminal is in a registered state in the second network or from the second network, wherein the first network is a successor network or a next-generation network of the second network.

30. The apparatus as claimed in claim 29, characterized in that, The step of obtaining the context of the terminal in the first network based on the first indication information includes: When the first indication information is used to instruct the terminal to request the context of the terminal in the first network from the second core network device, if the terminal is in a registered state or is from the first network.

31. A mobility management device, characterized in that, include: The receiving module is used to receive the second message from the first core network device; The sending module is configured to perform any of the following based on the second message: If the second message includes second indication information, the terminal sends a message to the first core network device in the context of the first network. If the second indication information is not included in the second message, the context of the terminal in the second network is sent to the first core network device; Wherein, the first network is a successor network or next-generation network of the second network, and the second indication information is used for at least one of the following: The second message corresponds to the first network; The terminal is requested to be in the context of the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

32. A mobility management device, characterized in that, include: The receiving module is used to receive update messages from the first core network device; The processing module is configured to perform any of the following based on the update message: If the update message includes third indication information, it indicates that the terminal is in the first network or is in a registered state in the first network. If the third indication information is not included in the update message, the terminal is recorded as being in the second network or in a registered state in the second network. Wherein, the first network is the successor network or next-generation network of the second network, and the third indication information is used for at least one of the following: The update message is indicated to correspond to the first network; The terminal is instructed to perform a registration or mobility registration update MRU on the first network.

33. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 6.

34. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 7 to 26.

35. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 6, or the steps of the method as claimed in any one of claims 7 to 26.

Images