Mobility management method and apparatus, device, and medium

Abstract

The present disclosure provides a mobility management method and apparatus, a device, and a medium. The method of the present disclosure comprises: acquiring at least two pieces of tracking area identifier list information, different tracking area identifier list information corresponding to different types of access networks; and performing mobility management processing on the basis of the at least two pieces of tracking area identifier list information.

Description

Mobility management methods, devices, equipment and media

[0001] This disclosure claims priority to Chinese Patent Application No. 202411992119.1, filed with the Chinese Patent Office on December 31, 2024, entitled "Method, Apparatus, Device and Medium for Mobility Management", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a mobility management method, apparatus, device and medium. Background Technology

[0003] Non-terrestrial networks (NTNs) in related technologies support satellite access for multiple orbit types, including low Earth orbit (LEO) satellite access and geostationary orbit (GEO) satellite access. The same operator typically connects LEO and GEO satellites to the same core network.

[0004] In related technologies, when a terminal switches to a different access type (e.g., from LEO satellite access to GEO satellite access), the current Tracking Area (TA) may not be in the registered Tracking Area Identity List (TAI List), leading to a mobility registration update. However, if the terminal's absolute location has not actually changed, this mobility registration update is unnecessary and instead increases signaling overhead between networks. Summary of the Invention

[0005] The purpose of this disclosure is to provide a mobility management method, apparatus, device, and medium to solve the problem of increased inter-network signaling overhead caused by performing unnecessary mobility registration update procedures when the absolute position of the terminal does not actually change during network handover in related technologies.

[0006] To achieve the above objectives, in a first aspect, embodiments of this disclosure provide a mobility management method applied to a terminal, comprising:

[0007] Obtain at least two tracking area identifier lists, with different tracking area identifier lists corresponding to different access network types;

[0008] Mobility management processing is performed based on the at least two tracking area identifier lists.

[0009] In some embodiments, mobility management processing is performed based on the at least two tracking area identifier list information, including:

[0010] When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information.

[0011] Once the tracking area identifier broadcast by the target base station is determined to be within the range of the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

[0012] In some embodiments, the method further includes:

[0013] When a terminal registers for the first time, it sends a registration request message to the first core network device. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0014] In some embodiments, obtaining at least two tracking area identifier list information includes:

[0015] Receive first information, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0016] The first information includes a registration confirmation message or a terminal configuration update command.

[0017] In some embodiments, the network handover is a first handover from a first base station to a second base station. The first handover is based on the direct communication interface between base stations. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types.

[0018] After updating the tracking area identifier list information that takes effect after network handover to the first tracking area identifier list information, the method further includes:

[0019] The second access network type and the corresponding tracking area identifier list information are saved as alternatives.

[0020] In some embodiments, the network handover is a second handover from a first base station to a second base station, the second handover being based on a communication interface switch between the base station and the core network, wherein the first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station, the second access network type is one of at least two access network types, and the first core network device is the target core network device; the method further includes:

[0021] The device receives a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0022] The updated tracking area identifier list information that takes effect after the network switch is the first tracking area identifier list information, including:

[0023] When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

[0024] Secondly, this disclosure also provides a mobility management method applied to a first core network device, comprising:

[0025] At least two tracking area identifier list information are sent to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

[0026] In some embodiments, sending at least two tracking area identifier list information to the terminal includes:

[0027] Send first information to the terminal, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0028] The first information includes a registration confirmation message or a terminal configuration update command.

[0029] In some embodiments, sending at least two tracking area identifier list information to the terminal includes:

[0030] Based on the first condition, send at least two tracking area identifier list information to the terminal;

[0031] The first condition includes one or more of the following conditions:

[0032] The terminal provides the ability to manage multiple sets of tracking area identifier lists;

[0033] The types of access networks supported by the terminal's contracted data;

[0034] The second information includes terminal location information and satellite coverage information of ephemeris.

[0035] In some embodiments, the method further includes:

[0036] When the terminal registers for the first time, a registration request message sent by the terminal is received. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0037] Obtain the access network types supported by the terminal subscription data from the unified data management network element.

[0038] In some embodiments, the network handover occurring at the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the target core network device. The method further includes:

[0039] The terminal context request message sent by the source core network device is received. The terminal context request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types and tracking area identifier list information corresponding to each access network type allocated by the source core network device to the terminal. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0040] A terminal context creation response message is sent to the source core network device. The terminal context creation response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0041] In some embodiments, the network handover occurring at the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the source core network device. The method further includes:

[0042] The first base station sends a handover command message to the terminal. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0043] Thirdly, embodiments of this disclosure also provide a terminal, including: a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; the processor is configured to read the program from the memory and execute the following processes:

[0044] Obtain at least two tracking area identifier lists, with different tracking area identifier lists corresponding to different access network types;

[0045] Mobility management processing is performed based on the at least two tracking area identifier lists.

[0046] In some embodiments, the processor is further configured to:

[0047] When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information.

[0048] Once the tracking area identifier broadcast by the target base station is determined to be within the range of the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

[0049] In some embodiments, the transceiver is further configured to:

[0050] When a terminal registers for the first time, it sends a registration request message to the first core network device. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0051] In some embodiments, the processor is further configured to:

[0052] The transceiver receives first information, which includes at least two access network types and a tracking area identifier list for each access network type.

[0053] The first information includes a registration confirmation message or a terminal configuration update command.

[0054] In some embodiments, the network handover is a first handover from a first base station to a second base station. The first handover is based on the direct communication interface between base stations. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types.

[0055] The processor is also used for:

[0056] After updating the tracking area identifier list information that takes effect after the network switch to the first tracking area identifier list information, the second access network type and the tracking area identifier list information corresponding to the second access network type are saved as alternatives.

[0057] In some embodiments, the network handover is a second handover from a first base station to a second base station, the second handover being based on a communication interface switch between the base station and the core network, wherein the first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station, the second access network type is one of at least two access network types, and the first core network device is the target core network device; the transceiver is further configured to:

[0058] The device receives a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0059] The processor is also used for:

[0060] When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

[0061] Fourthly, embodiments of this disclosure also provide a mobility management device, comprising:

[0062] The first acquisition unit is used to acquire at least two tracking area identifier list information, and different tracking area identifier list information corresponds to different access network types;

[0063] The first processing unit is used to perform mobility management processing based on the at least two tracking area identifier list information.

[0064] Fifthly, this disclosure also provides a core network device, which is a first core network device, including: a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor;

[0065] The transceiver is used to send at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

[0066] In some embodiments, the transceiver is further configured to:

[0067] Send first information to the terminal, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0068] The first information includes a registration confirmation message or a terminal configuration update command.

[0069] In some embodiments, the transceiver is further configured to:

[0070] Based on the first condition, send at least two tracking area identifier list information to the terminal;

[0071] The first condition includes one or more of the following conditions:

[0072] The terminal provides the ability to manage multiple sets of tracking area identifier lists;

[0073] The types of access networks supported by the terminal's contracted data;

[0074] The second information includes terminal location information and satellite coverage information of ephemeris.

[0075] In some embodiments, the transceiver is further configured to:

[0076] When the terminal registers for the first time, a registration request message sent by the terminal is received. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0077] Obtain the access network types supported by the terminal subscription data from the unified data management network element.

[0078] In some embodiments, the network handover performed by the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the target core network device. The transceiver is further configured to:

[0079] The terminal context request message sent by the source core network device is received. The terminal context request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types and tracking area identifier list information corresponding to each access network type allocated by the source core network device to the terminal. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0080] A terminal context creation response message is sent to the source core network device. The terminal context creation response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0081] In some embodiments, the network handover performed by the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the source core network device. The transceiver is further configured to:

[0082] The first base station sends a handover command message to the terminal. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0083] Sixthly, embodiments of this disclosure also provide a mobility management device, including:

[0084] The first sending unit is used to send at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

[0085] In a seventh aspect, embodiments of this disclosure also provide a non-transitory readable storage medium storing a program for performing the steps of the mobility management method as described in the first aspect, or performing the steps of the mobility management method as described in the second aspect.

[0086] The above-disclosed technical solution has at least the following beneficial effects:

[0087] In the above technical solution of this disclosure embodiment, by obtaining at least two tracking area identifier list information, with different tracking area identifier list information corresponding to different access network types, and performing mobility management processing based on at least two tracking area identifier list information, the handover process between networks can be optimized by allocating multiple sets of tracking area identifier list information to the terminal. When the absolute location of the terminal has not actually changed, by changing the tracking area identifier list information, unnecessary mobility registration update processes can be reduced, network signaling burden can be reduced, and user experience can be improved. Attached Figure Description

[0088] Figure 1 is one of the schematic diagrams illustrating movement between satellite access networks of different orbit types in related technologies;

[0089] Figure 2 is a second schematic diagram of movement between satellite access networks of different orbit types in related technologies;

[0090] Figure 3 is a schematic flowchart of one of the mobility management methods provided in this embodiment of the present disclosure;

[0091] Figure 4 is a schematic diagram of the relevant process for the first registration of a user according to an embodiment of this disclosure;

[0092] Figure 5 is a schematic diagram of the relevant process for terminal configuration update according to an embodiment of this disclosure;

[0093] Figure 6 is a schematic diagram of the handover process based on the direct communication interface between base stations according to an embodiment of this disclosure;

[0094] Figure 7 is one of the schematic diagrams of the communication interface switching process between the base station and the core network according to an embodiment of this disclosure;

[0095] Figure 8 is a second schematic diagram of the communication interface switching process between the base station and the core network according to an embodiment of this disclosure.

[0096] Figure 9 is a second schematic flowchart of the mobility management method provided in this embodiment of the present disclosure;

[0097] Figure 10 is a structural block diagram of a terminal according to an embodiment of this disclosure;

[0098] Figure 11 is a schematic diagram of one of the modules of a mobility management device according to an embodiment of the present disclosure;

[0099] Figure 12 is a structural block diagram of the core network device according to an embodiment of this disclosure;

[0100] Figure 13 is a second schematic diagram of the mobility management device according to an embodiment of the present disclosure. Detailed Implementation

[0101] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0102] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0103] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0104] To facilitate understanding of the solutions disclosed herein, the relevant content involved in this disclosure will be introduced first.

[0105] A Tracking Area Code (TAC) is an coded identifier for a tracking area, used to distinguish different geographical areas.

[0106] The base station broadcasts the Tracking Area Code (TAC) and Public Land Mobile Network (PLMN) information covering the terminals within its coverage area. These two pieces of information are complementary (the TAC may differ depending on the PLMN), ensuring that the terminal can distinguish the TAC of different operators based on the PLMN, thereby correctly identifying its Tracking Area (TAI). The terminal uses the TAC information broadcast by the base station to determine the corresponding area of ​​the PLMN network it is connected to.

[0107] The Tracking Area Identity (TAI) is an identifier that includes the TAC and PLMN (Carrier Identifier) ​​and is used to indicate the tracking area where the terminal is located.

[0108] The base station reports the Terminal Identification Area (TAI) to the core network. The terminal determines its TAI by obtaining the Terminal Accreditation Code (TAC) broadcast by the current base station and the PLMN it is connected to.

[0109] A TAI List is a list of TAIs that represents multiple tracking areas where a terminal may be located. The TAI List is assigned by the Access and Mobility Management Function (AMF) of the core network during user registration (or location update) and is typically returned to the terminal in the user's registration response message.

[0110] The main processes involved in the TAI List are as follows:

[0111] Terminal initiates registration request: When the terminal starts up or a location update occurs, the terminal will initiate a registration request to the core network, reporting its current TAI and location information.

[0112] The core network (AMF) processes the registration request: When processing this request, the core network determines the terminal's TAI List, which is a list containing multiple TAIs. This list reflects the tracking area that the terminal can cover within its current network (PLMN).

[0113] Registration Response: The core network sends the TAI List as part of the response to the terminal, informing the terminal of other tracking area identifiers that it can use in the future.

[0114] Terminal mobility management: The terminal manages its subsequent mobility and registration updates based on the TAI List. If the terminal moves to a new tracking area, it checks the TAI List for a matching TAI (TAC+PLMN) broadcast by the base station. If a match is found, re-registration is not required; otherwise, a new registration process is triggered.

[0115] Next, we will introduce the relevant content regarding user access and switching between multiple satellites in different orbits.

[0116] In related technologies, the registration process (including mobility registration) and the switching process are two separate processes.

[0117] When GEO and LEO satellite access networks overlap, and the LEO satellite access network does not yet provide continuous LEO satellite access coverage in the early stages of deployment, both networks need to work together to support service continuity for users. For example, when LEO satellite access network coverage is lost, users may need to connect to the GEO satellite access network. Alternatively, based on operator policies, some users may be switched to the GEO satellite access network for communication depending on network conditions.

[0118] Referring to Figures 1 and 2, according to relevant technologies, the terminal accesses the LEO satellite access network at time 1 and obtains the TAI List of the LEO satellite access network; at time 2, the terminal loses satellite coverage corresponding to the LEO satellite access network and switches to the GEO satellite access network to obtain the TAI List of the GEO satellite access network. Thus, even if the terminal's actual location does not change, because the TAI Lists of the GEO and LEO satellite access networks are different, the terminal still needs to trigger a mobility location update process, resulting in increased signaling overhead in the inter-satellite network.

[0119] To address the aforementioned technical problems, embodiments of this disclosure provide mobility management methods, apparatus, devices, and media. The methods and apparatus are based on the same application concept. Since the methods and apparatus solve problems in similar principles, their implementations can be mutually referenced, and repeated details will not be elaborated further.

[0120] Figure 3 shows a flowchart of the mobility management method provided in this embodiment. This method is applied to a terminal, meaning it is executed by the terminal. The method may include:

[0121] Step 301: Obtain at least two tracking area identifier list information, with different tracking area identifier list information corresponding to different access network types;

[0122] In some embodiments, the tracking area identifier list information is a TAI List.

[0123] In some embodiments, obtaining at least two tracking area identifier list information may include receiving at least two tracking area identifier list information sent by a first core network device. That is, the at least two tracking area identifier list information is sent (or provided, or allocated) by the first core network device. Of course, the at least two tracking area identifier list information may also be sent (or provided, or allocated) by other network-side devices, which is not specifically limited here.

[0124] Step 302: Perform mobility management processing based on the at least two tracking area identifier list information.

[0125] Here, by assigning at least two tracking area identifier lists to the terminal, the handover process between networks can be optimized. Specifically, during the network handover phase, when the terminal's absolute location has not actually changed, the tracking area identifier list information is updated to ensure that the current tracking area is in the registered tracking area identifier list information. This reduces unnecessary mobility registration update processes, lowers network signaling burden, and improves user experience.

[0126] In some embodiments, step 302, performing mobility management processing based on the at least two tracking area identifier list information, includes:

[0127] When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information.

[0128] Once the tracking area identifier broadcast by the target base station is determined to be within the range of the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

[0129] In other words, if the terminal determines that the target access network for network handover is the first access network type, and at least two tracking area identifier (TAI) lists exist that correspond to the first access network type (i.e., the first TAI) list information), the terminal updates the TAI list information effective after the network handover to the first TAI list information. Furthermore, if the terminal determines that the TAI list information effective after the network handover matches the TAI broadcast by the target base station (i.e., the TAI broadcast by the target base station is within the range of the TAI list information effective after the network handover), the terminal does not need to re-register, and therefore does not initiate a mobility registration update process; otherwise, a new registration process will be triggered.

[0130] In this way, during the network handover phase, when the absolute position of the terminal has not actually changed, the tracking area identifier list information is updated to ensure that the current tracking area is in the registered tracking area identifier list information, thereby reducing unnecessary mobility registration update processes, reducing network signaling burden, and improving user experience.

[0131] In some embodiments, step 301, obtaining at least two tracking area identifier list information, includes:

[0132] Receive first information, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type; wherein, the first information includes a registration confirmation message or a terminal configuration update command.

[0133] In some embodiments, receiving the first information may include receiving the first information sent by the first core network device.

[0134] The first information includes Registration Accept information, indicating that at least two tracking area identifier list information can be obtained during the initial registration phase of the terminal. The first information also includes UE Configuration Update Command, indicating that at least two tracking area identifier list information can be obtained during the terminal configuration update phase. The terminal configuration update can be initiated by the first core network device (such as AMF).

[0135] In some embodiments, the first information further includes a second capability identifier, which indicates whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0136] Here, the terminal performs mobility management processing based on at least two tracking area identifier list information obtained, indicating that the terminal needs to support the management capability of multiple sets of tracking area identifier list information. Whether the terminal supports the management capability of multiple sets of tracking area identifier list information can be implemented during the initial registration stage of the terminal. Specifically, in some embodiments, the method of this disclosure further includes:

[0137] When a terminal registers for the first time, it sends a registration request message to the first core network device. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0138] To optimize mobile management, the terminal needs to obtain at least two tracking zone identifier lists. As mentioned in the above embodiments, this information can be obtained during the initial registration phase or during the terminal configuration update phase. The following two embodiments illustrate the relevant processes for initial terminal registration and terminal configuration updates.

[0139] Example 1, see Figure 4, illustrates the process for a user's first registration.

[0140] The scenario corresponding to this embodiment can be seen in Figure 1. The UE (terminal) accesses the network from the LEO satellite access network. At the current location of the UE, the coverage area of ​​the GEO satellite access network includes the coverage area of ​​the LEO satellite access network. Specifically, this involves steps 401, 403, 414b, and 421 in the following steps:

[0141] Step 401: The UE initiates a registration request message.

[0142] The registration request message includes a first capability identifier, which identifies whether the terminal supports the Multi-TAI List Support capability.

[0143] Specifically, a first capability identifier is added to the UE's mobility management capabilities (such as 5G Mobility Management Capability, 5GMM capability) information in the registration request message. 5G is an abbreviation for Fifth Generation Mobile Communication Technology.

[0144] Step 402: The Radio Access Network (RAN) equipment performs AMF selection.

[0145] Step 403: The RAN device sends a registration request message to New AMF, which carries user location information.

[0146] New AMF receives a registration request message and saves the first capability identifier and terminal location information.

[0147] Step 404: The New AMF sends a Terminal Context Request message to the Old AMF.

[0148] Step 405: Old AMF returns a terminal context response message to New AMF.

[0149] Step 406: New AMF sends an identity request message to the UE.

[0150] Step 407: The UE returns an identity response message to New AMF.

[0151] Step 408: New AMF selects the Authentication Server Function (AUSF).

[0152] Step 409, Verification / Security.

[0153] Step 410: New AMF sends a registration status update to Old AMF.

[0154] Step 411: New AMF and UE exchange identity request / response information.

[0155] Step 412: New AMF performs a device identity check with the Equipment Identify Register (EIR).

[0156] Step 413: New AMF selects Unified Data Management (UDM).

[0157] Step 414a: New AMF initiates registration with UDM.

[0158] Step 414b: New AMF sends a subscription data request Nudm_SDM_Get to UDM. It retrieves the UE's access and mobility subscription data from the UDM, including the type of access network (RAT) allowed for the UE's access.

[0159] Step 414c: New AMF sends subscription data to UDM to modify Nudm_SDM_Subscribe.

[0160] In step 414d, UDM sends a deregistration message to Old AMF.

[0161] In step 414e, Old AMF sends unsubscribe data to UDM.

[0162] Step 415: New AMF selects the Policy and Charging Rules Function (PCF).

[0163] Step 416: Establish / modify the AM policy association between New AMF and PCF.

[0164] Step 417: New AMF sends the SM context change / release for the Packet Data Unit (PDU) session to SMF.

[0165] Step 418: New AMF sends a terminal context modification request to N3IWF / TNGF / W-AGF.

[0166] N3IWF is short for Non-3GPP InterWorking Function. It is a network function used to provide protocol conversion and data routing between different network and access technologies.

[0167] TNGF is short for Trusted Non-3GPP Gateway Function. The main function of this network function is to enable terminals to access the 5G core network from a trusted non-3GPP network.

[0168] The Wireless Access Gateway Function (W-AGF) is a network function that enables 5G home gateways to access the 5G core network from a wired network.

[0169] Step 419: N3IWF / TNGF / W-AGF returns a terminal context modification response to New AMF.

[0170] Step 419a: New AMF initiates registration with UDM.

[0171] In step 419b, UDM sends a deregistration message to Old AMF.

[0172] In step 419c, Old AMF sends unsubscribe data to UDM.

[0173] Step 421: New AMF sends a Registration Accept message to the UE. The Registration Accept message includes two sets of TAI Lists allocated by New AMF to the UE. One set is the TAI List corresponding to the current access network type, LEO satellite access network, and the other set is the TAI List corresponding to the access network type, GEO satellite access network.

[0174] Here, the AMF adds a second capability identifier, which is used to indicate whether the AMF supports the ability to assign corresponding TAI Lists for different access network types supported by the UE.

[0175] Based on the UE's current access network type, namely LEO satellite access network, the validity of the first capability identifier carried in the UE registration request, and the support for NR, NTN_GEO, and NTN_LEO access types in the access and mobility subscription data, AMF can determine whether to issue multiple TAI Lists for different access network types to the UE.

[0176] Subsequently, the AMF further determines, based on the terminal location information and satellite coverage information from the ephemeris, that the UE's current location is simultaneously covered by both LEO and GEO satellite access networks, and that the LEO satellite access network coverage is discontinuous. The UE will attempt to access the GEO satellite access network after losing LEO satellite access network coverage. In this case, the AMF allocates the aforementioned two TAI Lists to the UE.

[0177] It should be noted that the Registration Accept message also includes a secondary capability identifier. Specifically, the Network Feature Support field in the Registration Accept message carries the secondary capability identifier.

[0178] When the UE receives the Registration Accept message, it saves two sets of TAI Lists and the access network type corresponding to each TAI List, and can also save the second capability identifier.

[0179] Step 421b: Establish AM strategy association between New AMF and PCF.

[0180] Step 422: The UE sends a registration completion message to New AMF.

[0181] Step 423: New AMF provides the UDM with terminal confirmation Nudm_SDM_Info.

[0182] Step 423a: New AMF sends an N2 message to RAN.

[0183] Step 424: New AMF sends the instruction Nudm_UECM_Update to UDM to "Unify support for IMS voice via PS session".

[0184] Step 425: New AMF performs authentication and authorization for specific network segments with the UE.

[0185] Example 2, see Figure 5, illustrates the relevant process for terminal configuration updates.

[0186] When the AMF wants to update access and mobility management parameters in the terminal configuration, this process is initiated by the AMF. If a registration process is required, the AMF provides the UE with an instruction to start the registration process. Obtaining at least two TAI Lists mainly involves step 501 in the following steps, specifically:

[0187] In step 500, the AMF determines whether the terminal configuration needs to be updated or re-registration is required.

[0188] Step 501: The AMF sends a UE Configuration Update Command to the UE. This UE Configuration Update Command includes two TAI Lists assigned to the UE by the AMF.

[0189] Specifically, the AMF sends a configuration update command that includes one or more UE parameters, wherein the configuration update command includes two sets of TAI Lists assigned by the AMF to the UE.

[0190] AMF assigns at least two TAI Lists to a terminal through terminal configuration updates for the following two scenarios:

[0191] Scenario 1: When the AMF is upgraded or its configuration is updated, from not supporting to supporting, the corresponding TAI List capability is assigned to different access network types supported by the UE. In this case, the AMF determines that it can issue multiple TAI Lists for different access network types to the UE based on the UE's current access network type, the first capability identifier (Multi-TAI List Support) saved in the previous registration process is valid, and the subscription data supports NR, NTN_GEO and NTN_LEO access types.

[0192] Subsequently, the AMF further determines, based on the terminal location information and satellite coverage information from the ephemeris, that both LEO and GEO satellite access networks exist at the UE's current location, and that the LEO satellite access network coverage is discontinuous. The UE will attempt to access the GEO satellite access network after losing LEO satellite access network coverage. In this case, the AMF allocates the aforementioned two TAI Lists to the UE through a terminal configuration update command.

[0193] Scenario 2: Based on terminal location information and satellite coverage information such as ephemeris, the AMF determines that the UE's TAI List needs to be updated. Similar to the method in Implementation Example 1, the AMF can allocate the above two sets of TAI Lists to the UE through the terminal configuration update command.

[0194] Step 502a: The UE sends a terminal configuration update completion message to the AMF.

[0195] Step 502b: AMF provides the UDM with the terminal confirmation service Nudm_SDM_Info service.

[0196] Step 502c: Update RAN between AMF and RAN.

[0197] Step 502d: The UE notifies the lower layer.

[0198] Step 503a, as described in Section 4.2.2.2, the terminal initiates the registration process in the Connection Management Connected (CM-CONNECTED) state, skipping steps 503b, 503c and 504.

[0199] Step 503b: The UE configuration change does not affect the existing connection with the AMF.

[0200] Step 503c: UE configuration changes will affect existing connections with the AMF.

[0201] In step 504, unless there is a PDU session related to emergency services, the AMF will trigger the AN release procedure, and the terminal will start the registration procedure after the terminal enters the CM-IDLE (Connection Management Idle) state.

[0202] In some embodiments, the method disclosed herein further includes:

[0203] Receive the second tracking area identifier list information to be updated, the second tracking area identifier list information being determined by the first core network device according to the second condition;

[0204] Based on the second tracking area identifier list information, at least one of the at least two tracking area identifier list information is updated; wherein, the second condition includes one or more of the following conditions:

[0205] Terminal location information;

[0206] Preset strategy.

[0207] In this embodiment, a terminal configuration update command can be received. The terminal configuration update command includes the second tracking area identifier list information to be updated, corresponding to scenario 2 above. For example, a terminal configuration update command sent by a first core network device can be received, and the terminal configuration update command includes the second TAI List to be updated.

[0208] Specifically, based on the second tracking area identifier list information, at least one of the at least two tracking area identifier list information is updated, or the second tracking area identifier list information may be one or more, and some or all of the at least two tracking area identifier list information may be updated.

[0209] Furthermore, the tracking area identifier list information is also updated during user mobility registration or periodic registration processes. For example, referring to Figure 4, in step 421, the AMF updates the UE's TAI List based on terminal location information or operator policies (preset policies). For instance, it can update the TAI List corresponding to the UE's current access network type, the TAI List corresponding to alternative access network types, or update all of them. Here, there are two sets of TAI Lists, one set corresponding to the current access network type and the other set corresponding to the alternative access network types.

[0210] In some embodiments, the network handover is a first handover from a first base station to a second base station. The first handover is based on the direct communication interface between base stations. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types.

[0211] The first switching includes Xn switching, X2 switching, etc.

[0212] In this embodiment, it should be understood that the first base station is the source base station, the second base station is the target base station, and the second base station corresponds to the first access network type.

[0213] Accordingly, after updating the tracking area identifier list information that takes effect after the network handover to the first tracking area identifier list information, the method of this disclosure further includes:

[0214] The second access network type and the corresponding tracking area identifier list information are saved as alternatives.

[0215] Here, the second access network type and the tracking area identifier list information corresponding to the second access network type are saved as alternatives. The purpose is to enable the activation to be triggered again when accessing the access network corresponding to the second access network type again.

[0216] Based on this, in some embodiments, the method of this disclosure further includes:

[0217] After the first handover is completed, if another network handover occurs, and the network handover is a third handover from the second base station to the first base station, and the third handover is based on the direct communication interface handover between base stations, the tracking area identifier list information that takes effect after the network handover is updated to the tracking area identifier list information corresponding to the second access network type.

[0218] Here, during the first handover from the first base station to the second base station, if the terminal returns to the area previously covered by the first base station after a period of time, and the signal strength is better than that of the second base station, or if it switches back to the first base station based on a conditional handover strategy, thus triggering the third handover from the second base station to the first base station, the TAI List corresponding to the previously selected second access network type (the access network type corresponding to the first base station) will be updated with the Tracking Area Identifier List information that takes effect after the network handover. This quickly triggers the Tracking Area Identifier List information to take effect, improving the user experience.

[0219] It should be noted that the first handover and the third handover are handovers with the same interface type. The reason for the different names is to indicate that they are not the same handover, but different handovers, and the target base stations they are switched to are different.

[0220] The following two examples illustrate the handover process based on the direct communication interface between base stations.

[0221] Example 3, referring to Figure 6, illustrates the Xn handover from the LEO satellite base station to the GEO satellite base station.

[0222] The scenario described in this embodiment is: the movement of the LEO satellite-borne base station is about to cause the UE to lose coverage. The LEO satellite-borne base station and the GEO satellite-borne base station switch over via Xn, allowing the user to switch to access via the GEO satellite-borne base station. This mainly involves the following stages and steps:

[0223] Switch to the preparation phase.

[0224] Switch execution phase.

[0225] During the handover execution phase, the UE updates its own access network type to GEO satellite access network based on the target base station information, and determines that the alternative access network type saved during the registration phase is consistent with the current access network type GEO. If so, the TAI List corresponding to the alternative access network type GEO is used as the TAI List that takes effect after the network handover.

[0226] It should be noted that since the LEO access network coverage has been lost, the TAI List corresponding to the LEO access network before the handover can be marked as the alternative access network type (LEO) and the corresponding TAI List on the UE side so that it can be triggered again when accessing a non-continuous LEO access network.

[0227] During the switchover execution phase, the source NG-RAN forwards data to the target NG-RAN. The following execution follows:

[0228] Step 601a: The source NG-RAN sends a RAN usage data report to the AMF.

[0229] In step 601b, the AMF receives the N2 Path Switch Request message sent by the target base station and obtains that the access network type corresponding to the target base station is a GEO satellite access network.

[0230] Step 602: The AMF sends a user session update request (Nsmf_PDUSession_UpdateSMContext Request) message to the Session Management Function (SMF), in which the access network type corresponding to the session is updated to GEO satellite access network.

[0231] It should be noted that the access network type for other network functions also needs to be updated at the same time, which will not be elaborated here.

[0232] Step 603, SMF(s) sends an N4 session modification request to UPF(s).

[0233] Step 604, UPF(s) sends an N4 session modification response to SMF(s).

[0234] Step 605: UPF(s) sends an N3 end marker to the source NG-RAN, and the source NG-RAN sends an N3 end marker to the target NG-RAN.

[0235] Step 606, SMF(s) sends a user session update response to AMF.

[0236] Step 607: AMF sends an N2 path switching request confirmation to the target NG-RAN.

[0237] Step 608: The target NG-RAN sends a resource release instruction to the source NG-RAN.

[0238] Step 609: When the UE determines that the TAI broadcast by the target base station is within the range of the TAI List that takes effect after network handover, it no longer needs to initiate the mobility registration update process.

[0239] Example 4, also referencing Figure 6, illustrates the Xn handover from the GEO satellite base station to the LEO satellite base station.

[0240] The scenario corresponding to this embodiment is that the TAC is planned as a fixed ground location, and the UE's relative movement does not move it out of the TAI List range corresponding to the previous LEO or GEO. Based on embodiment three, after the user switches to a GEO satellite-borne base station for a period of time, an LEO satellite-borne base station covers the UE again. The UE will switch from the GEO satellite-borne base station to the LEO satellite-borne base station based on signal strength (the LEO satellite-borne base station signal is better than the GEO satellite-borne base station) or according to the conditional handover strategy, etc.

[0241] Compared to Example 3:

[0242] During the handover execution phase, the UE updates its access network type to LEO satellite access network based on the target base station information. Based on its Multi-TAI List Support capability (i.e., support for managing multiple TAI Lists), and if the alternative access network type (LEO satellite access network) saved during the registration phase is consistent with the current access network type LEO, then the TAI List corresponding to the alternative access network type LEO will be used as the TAI List that takes effect after the network handover.

[0243] It should be noted that in Embodiment 3, after the UE switches to the GEO access network, the access network type (LEO) is marked as a candidate access network type and the corresponding TAI List is saved.

[0244] In step 601b, the AMF receives the N2 Path Switch Request message sent by the target base station and obtains that the access network type corresponding to the target base station is an LEO satellite access network.

[0245] Step 602: The AMF sends a user session update request (Nsmf_PDUSession_UpdateSMContext Request) message to the Session Management Function (SMF), in which the access network type corresponding to the session is updated to LEO satellite access network.

[0246] It should be noted that the access network type for other network functions also needs to be updated at the same time, which will not be elaborated here.

[0247] Step 609: When the UE determines that the TAI broadcast by the target base station is within the range of the TAI List that takes effect after network handover, it no longer needs to initiate the mobility registration update process.

[0248] In some embodiments, the network handover is a second handover from a first base station to a second base station. The second handover is based on the communication interface switch between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The first core network device is the target core network device.

[0249] The second handover includes N2 handover, S1 handover, etc.

[0250] In this embodiment, it should be understood that the first base station is the source base station, the second base station is the target base station, and the second base station corresponds to the first access network type.

[0251] This embodiment corresponds to a scenario where the first base station and the second base station do not support direct communication interfaces between base stations, or where the first base station and the second base station are connected to different core network devices (AMF), in which case a second handover is performed.

[0252] It should be noted that the first switch and the second switch (or the third switch) are switches between different interface types.

[0253] Accordingly, the methods disclosed herein also include:

[0254] The device receives a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0255] Here, the first base station receives a handover command message from the source core network device and then sends the handover command message to the terminal. In other words, the terminal receives the handover command message forwarded by the first base station from the source core network device.

[0256] Accordingly, the updated tracking area identifier list information that takes effect after the network switch is the first tracking area identifier list information, including:

[0257] When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

[0258] Here, the terminal determines whether the first core network device (target core network device) obtained from the handover command message has the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal. If it has the capability, the terminal can independently update the tracking area identifier list information that takes effect after the network handover; otherwise, it will not independently update the TAI List.

[0259] The following example illustrates the communication interface switching process between the base station and the core network.

[0260] Example 5, referring to Figures 7 and 8, illustrates the N2 handover from the LEO satellite base station to the GEO satellite base station.

[0261] In this embodiment, if the LEO satellite base station and the GEO satellite base station do not support the Xn interface, or if the LEO satellite base station and the GEO satellite base station correspond to different AMF access points, then an N2 handover will be performed, and the LEO satellite base station coverage will be lost, and access will be made to the GEO satellite base station.

[0262] Referring to Figure 7, the switching preparation phase mainly involves steps 703 and 712 in the following steps:

[0263] The source NG-RAN decides to trigger the transfer via N2.

[0264] Step 701: The source NG-RAN sends a handover request to the source AMF.

[0265] Step 702: The source AMF selects the target AMF.

[0266] Step 703 involves AMF reselection. The source AMF sends a Namf_Communication_CreateUEContext Request message to the target AMF. The Namf_Communication_CreateUEContext Request message includes the first capability identifier carried by the terminal when registering with the source AMF, the TAI List assigned by the source AMF for different access network types supported by the UE, and the second capability identifier of the source AMF.

[0267] Step 704: The target AMF sends a user session update request to the SMF.

[0268] Step 705, SMF performs UPF selection.

[0269] Step 706a: SMF sends an N4 session modification request to UPF (PSA).

[0270] In step 706b, the UPF(PSA) returns an N4 session modification response to the SMF.

[0271] Step 706c: SMF sends an N4 session establishment request to the target UPF.

[0272] In step 706d, the target UPF sends an N4 session establishment response to the SMF.

[0273] Step 707: SMF sends a user session update response to the target UPF.

[0274] Step 708: The target AMF performs PDU switching response monitoring.

[0275] Step 709: The target AMF sends a handover request to the target NG-RAN.

[0276] Step 710: The target NG-RAN sends a handover request confirmation to the target AMF.

[0277] Step 711a: The target AMF sends a user session update request to the SMF.

[0278] Step 711b: The SMF sends an N4 session modification request to the target UPF.

[0279] Step 711c: The target UPF sends an N4 session modification response to the SMF.

[0280] Step 711d: SMF sends an N4 session modification request to the source UPF.

[0281] Step 711e: The source UPF sends an N4 session modification response to the SMF.

[0282] Step 711f: SMF sends a user session update response to the target UPF.

[0283] Step 712: The target AMF sends a Create UEContext Response (Namf_Communication_CreateUEContext Response) message to the source AMF. The Create UEContext Response message includes the target AMF's second capability identifier, i.e., whether the target AMF has the capability to allocate corresponding TAI Lists for different access network types supported by the terminal.

[0284] It should be noted that during the handover preparation phase, the target AMF can determine whether to reuse multiple TAI Lists provided by the source AMF based on its policy. If reuse is possible, the multiple TAI Lists provided by the source AMF will be reused directly. If reuse is not possible, multiple new TAI Lists can be allocated by triggering the UE configuration process. The newly allocated TAI Lists triggered by the target AMF will overwrite the multiple TAI Lists provided by the source AMF (which can be understood as the deletion of the multiple TAI Lists provided by the source AMF). The UE saves the newly allocated TAI Lists from the target AMF, and when the target AMF has the capability to allocate corresponding TAI Lists for different access network types supported by the terminal, the UE can automatically update the TAI Lists.

[0285] Referring to Figure 8, the execution phase is switched, which mainly involves the following steps 801, 802, 804, 805 and 807.

[0286] Specifically:

[0287] Step 801: The source AMF sends a handover command message to the source base station (source NG-RAN). The handover command message includes the second capability identifier of the target AMF, that is, whether the target AMF has the capability to allocate corresponding TAI Lists for different access network types supported by the terminal.

[0288] Step 802: The source base station sends a handover command message to the UE, which includes the second capability identifier of the target AMF.

[0289] Step 802a: The source base station transmits the uplink RAN ​​status to the source AMF.

[0290] Step 802b: The source AMF transmits N1N2 messages to the target AMF.

[0291] Step 803a: The source base station directly forwards data to the target base station.

[0292] Step 803b: The source base station performs indirect data forwarding to the source UPF.

[0293] Afterwards, the terminal synchronizes with the new cell.

[0294] Step 804: The UE sends a handover confirmation message to the target base station.

[0295] Here, the UE obtains whether the target AMF has the capability to allocate corresponding TAI Lists for different access network types supported by the terminal based on the handover command message.

[0296] If the target AMF has the capability to assign corresponding TAI Lists to different access network types supported by the terminal, the process is similar to that in Embodiment 3 above, where the terminal performs an autonomous TAI List update. If the AMF does not have the capability to assign corresponding TAI Lists to different access network types supported by the terminal, the terminal does not perform an autonomous TAI List update.

[0297] Step 805: The target AMF receives a handover notification message from the target base station. The handover notification message includes the fact that the access network type corresponding to the target base station is a GEO access network.

[0298] Step 806a: The target AMF sends an N2 message notification to the source AMF.

[0299] Step 806b: The source AMF sends an N2 message to the target AMF to confirm.

[0300] Step 806c: The source AMF sends a user session release request to the SMF.

[0301] Step 807 is similar to step 2 in Embodiment 3. The target AMF sends a User Session Update Request (Nsmf_PDUSession_UpdateSMContext Request) message to the SMF, in which the access network type corresponding to the session is updated to GEO satellite access network.

[0302] Step 808a: SMF sends an N4 session modification request to the target UPF.

[0303] Step 808b: The target UPF sends an N4 session modification response to the SMF.

[0304] Step 809a: SMF sends an N4 session modification request to the source UPF.

[0305] Step 809b: The source UPF sends an N4 session modification response to the SMF.

[0306] Step 810a: SMF sends an N4 session modification request to UPF (PSA).

[0307] Step 810b: UPF(PSA) sends an N4 session modification response to SMF.

[0308] Step 811: The SMF sends a user session update response to the target AMF.

[0309] Step 812, similar to Embodiment 3, if the target AMF has the capability to allocate corresponding TAI Lists for different access network types supported by the terminal, then, similar to Embodiment 3, the mobility registration update process will not be initiated. If the target AMF does not have the capability to allocate corresponding TAI Lists for different access network types supported by the terminal, then the mobility registration update will be performed according to the original standard process.

[0310] Step 813a: SMF sends an N4 session release request to the source UPF.

[0311] Step 813b: The source UPF sends an N4 session release response to the SMF.

[0312] Step 814a: The source AMF sends a terminal context release command to the source base station.

[0313] Step 814b: The source base station sends a terminal context release command to the source AMF to complete the process.

[0314] Figure 9 shows a flowchart of the mobility management method provided in an embodiment of this disclosure. This method is applied to a first core network device, meaning it is executed by the first core network device. The method may include:

[0315] Step 901: Send at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

[0316] It should be noted that this embodiment is a method embodiment corresponding to the opposite side of the aforementioned terminal, namely the first core network equipment side. For a detailed understanding and explanation of related terms or steps, please refer to the description in the terminal-side method section, which will not be repeated here.

[0317] The mobility management method of this disclosure can optimize the handover process between networks by allocating at least two tracking area identifier list information to the terminal. Specifically, it can reduce unnecessary mobility registration update processes, reduce network signaling burden, and improve user experience when the terminal's absolute location has not actually changed, by changing the tracking area identifier list information.

[0318] In some embodiments, step 901, sending at least two tracking area identifier list information to the terminal, may include:

[0319] Send first information to the terminal, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0320] The first information includes a registration confirmation message or a terminal configuration update command.

[0321] In some embodiments, the first information further includes a second capability identifier, which indicates whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0322] In some embodiments, step 901, sending at least two tracking area identifier list information to the terminal, may include:

[0323] Based on the first condition, send at least two tracking area identifier list information to the terminal;

[0324] The first condition includes one or more of the following conditions:

[0325] The terminal provides the ability to manage multiple sets of tracking area identifier lists;

[0326] The types of access networks supported by the terminal's contracted data;

[0327] The second information includes terminal location information and satellite coverage information of ephemeris.

[0328] For example, the primary core network device (such as the AMF) determines, based on the UE's current access network type (LEO satellite access network), the terminal's ability to manage multiple TAI Lists (i.e., the primary capability identifier is valid), and the terminal's subscription data supporting NR, NTN_GEO, and NTN_LEO access types, that it can issue multiple TAI Lists to the UE for different access network types. Subsequently, the primary core network device further determines, based on the terminal's location information and satellite coverage information from ephemeris, that the UE's current location is simultaneously covered by both LEO and GEO satellite access networks, and that the LEO satellite access network coverage is discontinuous. The UE will attempt to access the GEO satellite access network after losing LEO satellite access network coverage. In this case, the AMF allocates two TAI Lists to the UE.

[0329] In some embodiments, the method disclosed herein further includes:

[0330] When the terminal registers for the first time, a registration request message sent by the terminal is received. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0331] Obtain the access network types supported by the terminal subscription data from the Unified Data Management (UDM) network element.

[0332] This involves the process of initial registration of the terminal. For ease of understanding, please refer to Figure 4, which is a detailed description of part of the embodiment. It will not be repeated here.

[0333] In some embodiments, the method disclosed herein may further include:

[0334] Based on the second condition, determine the second tracking area identifier list information to be updated for the terminal;

[0335] The terminal is sent the second tracking area identifier list information to be updated, which is used to update at least one of the at least two tracking area identifier list information.

[0336] The second condition includes one or more of the following conditions:

[0337] Terminal location information;

[0338] Preset strategy.

[0339] In this embodiment, the tracking area identifier list information may be updated during the user mobility registration or periodic registration process.

[0340] For example, referring to Figure 4, in step 21, the AMF updates the TAI List for the UE based on terminal location information or operator policies (preset policies). For example, it can update the TAI List corresponding to the UE's current access network type, update the TAI List corresponding to alternative access network types, or update all of them.

[0341] The first core network device can send a terminal configuration update command to the terminal. The terminal configuration update command includes a second TAI List to be updated. Specifically, based on the second TAI List, at least one of at least two TAI Lists is updated, or there may be one or more second TAI Lists, and some or all of the at least two TAI Lists are updated.

[0342] In some embodiments, the network handover is a second handover from a first base station to a second base station. The second handover is based on a communication interface switch between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The first core network device is the target core network device. Accordingly, the method of this disclosure may further include:

[0343] The terminal context request message sent by the source core network device is received. The terminal context request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types and tracking area identifier list information corresponding to each access network type allocated by the source core network device to the terminal. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0344] A terminal context creation response message is sent to the source core network device. The terminal context creation response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0345] This corresponds to the handover preparation phase based on the communication interface handover between the base station and the core network. For a clearer understanding, please refer to the explanation in Figure 7; it will not be repeated here.

[0346] It should be noted that during the handover preparation phase, the target core network device (target AMF) can determine whether to reuse multiple TAI Lists provided by the source core network device (source AMF) based on its policy. If reuse is possible, the multiple TAI Lists provided by the source core network device will be reused directly. If reuse is not possible, multiple new TAI Lists can be allocated by triggering the UE configuration process. The newly allocated TAI Lists triggered by the target core network device will overwrite the multiple TAI Lists provided by the source core network device (which can be understood as the deletion of the multiple TAI Lists provided by the source AMF). The UE saves the newly allocated TAI Lists from the target core network device, and when the target core network device has the capability to allocate corresponding TAI Lists for different access network types supported by the terminal, the UE can automatically update the TAI Lists.

[0347] In some embodiments, the network handover is a second handover from a first base station to a second base station. The second handover is based on a communication interface switch between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The first core network device is the source core network device. Accordingly, the method of this disclosure may further include:

[0348] The first base station sends a handover command message to the terminal. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0349] This corresponds to the handover execution phase based on the communication interface switching between the base station and the core network. For a clearer understanding, please refer to the explanation in Figure 8; it will not be repeated here.

[0350] The mobility management method of this disclosure sends at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing. In this way, by allocating multiple sets of tracking area identifier list information to the terminal, the handover process between networks can be optimized. Specifically, when the terminal's absolute location has not actually changed, it can reduce unnecessary mobility registration update processes, reduce network signaling burden, and improve user experience by changing the tracking area identifier list information.

[0351] As shown in Figure 10, this embodiment of the present disclosure also provides a terminal, including: a transceiver 1000, a memory 1020, a processor 1010, and a computer program stored in the memory 1020 and executable on the processor 1010; the transceiver 1000 is used to receive and send data under the control of the processor 1010; the processor 1010 is used to read the program in the memory 1020 and execute the following processes:

[0352] Obtain at least two tracking area identifier lists, with different tracking area identifier lists corresponding to different access network types;

[0353] Mobility management processing is performed based on the at least two tracking area identifier lists.

[0354] In Figure 10, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1010 and memory represented by memory 1020. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1000 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1030 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0355] The processor 1010 is responsible for managing the bus architecture and general processing, while the memory 1020 can store the data used by the processor 1010 when performing operations.

[0356] In some embodiments, the processor 1010 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0357] The processor 1010 executes any of the methods provided in the embodiments of this disclosure by calling program instructions stored in the memory, according to the obtained executable instructions. The processor 1010 and the memory 1020 may also be physically separated.

[0358] In some embodiments, the processor 1010 is further configured to:

[0359] When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information.

[0360] Once the tracking area identifier broadcast by the target base station is determined to be within the range of the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

[0361] In some embodiments, the transceiver 1000 is further configured to:

[0362] When a terminal registers for the first time, it sends a registration request message to the first core network device. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0363] In some embodiments, the processor 1010 is further configured to:

[0364] The transceiver receives first information, which includes at least two access network types and a tracking area identifier list for each access network type.

[0365] The first information includes a registration confirmation message or a terminal configuration update command.

[0366] In some embodiments, the network handover is a first handover from a first base station to a second base station. The first handover is based on the direct communication interface between base stations. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types.

[0367] Accordingly, the processor 1010 is also used for:

[0368] After updating the tracking area identifier list information that takes effect after the network switch to the first tracking area identifier list information, the second access network type and the tracking area identifier list information corresponding to the second access network type are saved as alternatives.

[0369] In some embodiments, the network handover is a second handover from a first base station to a second base station, the second handover being based on a communication interface switch between the base station and the core network, wherein the first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station, the second access network type is one of at least two access network types, and the first core network device is the target core network device; the transceiver 1000 is further configured to:

[0370] The device receives a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0371] Accordingly, the processor 1010 is also used for:

[0372] When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

[0373] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0374] As shown in Figure 11, this embodiment of the present disclosure also provides a mobility management device, including:

[0375] The first acquisition unit 1101 is used to acquire at least two tracking area identifier list information, and different tracking area identifier list information corresponds to different access network types;

[0376] The first processing unit 1102 is used to perform mobility management processing based on the at least two tracking area identifier list information.

[0377] In some embodiments, the first processing unit 1102 is specifically used for:

[0378] When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information.

[0379] Once the tracking area identifier broadcast by the target base station is determined to be within the range of the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

[0380] In some embodiments of the present disclosure, the apparatus further includes:

[0381] The second sending unit is used to send a registration request message to the first core network device when the terminal registers for the first time. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0382] In some embodiments, the first acquisition unit 1101 is specifically used for:

[0383] Receive first information, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0384] The first information includes a registration confirmation message or a terminal configuration update command.

[0385] In some embodiments, the network handover is a first handover from a first base station to a second base station, the first handover being based on a direct communication interface handover between base stations, the first access network type corresponding to the second base station being different from the second access network type corresponding to the first base station, and the second access network type being one of at least two access network types; the apparatus of this disclosure embodiment further includes:

[0386] The second processing unit is used to update the tracking area identifier list information that takes effect after network switching to the first tracking area identifier list information, and then save the second access network type and the tracking area identifier list information corresponding to the second access network type as alternatives.

[0387] In some embodiments, the network handover is a second handover from a first base station to a second base station. The second handover is based on a communication interface switch between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The first core network device is the target core network device. The apparatus of this disclosure embodiment further includes:

[0388] The first receiving unit is configured to receive a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0389] Accordingly, the first processing unit 1102 is specifically used for:

[0390] When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

[0391] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0392] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0393] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0394] As shown in Figure 12, this embodiment of the present disclosure also provides a core network device, which is a first core network device, including: a transceiver 1200, a memory 1220, a processor 1210, and a computer program stored in the memory 1220 and executable on the processor 1210; the transceiver 1200 is used to send and receive data under the control of the processor 1210, and to perform the following operations:

[0395] At least two tracking area identifier list information are sent to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

[0396] In Figure 12, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1210 and memory represented by memory 1220. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1200 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0397] The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 can store the data used by the processor 1210 when performing operations.

[0398] The processor 1210 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0399] The processor 1210 executes any of the methods described in the embodiments of this disclosure according to the obtained executable instructions by calling program instructions stored in the memory. The processor 1210 and the memory 1220 may also be physically separated.

[0400] In some embodiments, the transceiver 1200 is further configured to:

[0401] Send first information to the terminal, the first information including the at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0402] The first information includes a registration confirmation message or a terminal configuration update command.

[0403] In some embodiments, the transceiver 1200 is further configured to:

[0404] Based on the first condition, send at least two tracking area identifier list information to the terminal;

[0405] The first condition includes one or more of the following conditions:

[0406] The terminal provides the ability to manage multiple sets of tracking area identifier lists;

[0407] The types of access networks supported by the terminal's contracted data;

[0408] The second information includes terminal location information and satellite coverage information of ephemeris.

[0409] In some embodiments, the transceiver 1200 is further configured to:

[0410] When the terminal registers for the first time, a registration request message sent by the terminal is received. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0411] Obtain the access network types supported by the terminal subscription data from the unified data management network element.

[0412] In some embodiments, the network handover occurring at the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the target core network device. The transceiver 1200 is further configured to:

[0413] The terminal context request message sent by the source core network device is received. The terminal context request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types and tracking area identifier list information corresponding to each access network type allocated by the source core network device to the terminal. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0414] A terminal context creation response message is sent to the source core network device. The terminal context creation response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0415] In some embodiments, the network handover occurring at the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the source core network device. The transceiver 1200 is further configured to:

[0416] The first base station sends a handover command message to the terminal. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0417] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0418] As shown in Figure 13, this disclosure also provides a mobility management device, including:

[0419] The first sending unit 1301 is used to send at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

[0420] In some embodiments, the first transmitting unit 1301 is specifically used for:

[0421] Send first information to the terminal, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type;

[0422] The first information includes a registration confirmation message or a terminal configuration update command.

[0423] In some embodiments, the first transmitting unit 1301 is specifically used for:

[0424] Based on the first condition, send at least two tracking area identifier list information to the terminal;

[0425] The first condition includes one or more of the following conditions:

[0426] The terminal provides the ability to manage multiple sets of tracking area identifier lists;

[0427] The types of access networks supported by the terminal's contracted data;

[0428] The second information includes terminal location information and satellite coverage information of ephemeris.

[0429] In some embodiments of the present disclosure, the apparatus further includes:

[0430] The second receiving unit is used to receive a registration request message sent by the terminal when the terminal registers for the first time. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0431] The second acquisition unit is used to obtain the access network type supported by the terminal subscription data from the unified data management network element.

[0432] In some embodiments, the network handover occurring at the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the target core network device. The apparatus in this embodiment further includes:

[0433] The third receiving unit is used to receive a terminal context creation request message sent by the source core network device. The terminal context creation request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types allocated by the source core network device to the terminal and tracking area identifier list information corresponding to each access network type. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

[0434] The third sending unit is used to send a Create Terminal Context Response message to the source core network device. The Create Terminal Context Response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0435] In some embodiments, the network handover occurring at the terminal is a second handover from a first base station to a second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the source core network device. The apparatus in this embodiment further includes:

[0436] The fourth sending unit is used to send a handover command message to the terminal through the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

[0437] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0438] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0439] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0440] In some embodiments of this disclosure, a non-transitory readable storage medium is also provided, the non-transitory readable storage medium storing a program for executing the mobility management method described above.

[0441] The non-transiently readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., compact disc (CD), digital video disc (DVD), Blu-ray disc (BD), high-definition versatile disc (HVD)), and semiconductor memory (e.g., ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND (Non-volatile Memory Device) FLASH), solid state hard drives (SSD), etc.).

[0442] When the program is executed by the processor, it can implement all the above-described methods applied to the terminal side as shown in Figure 3 or the first core network device side embodiment as shown in Figure 9. To avoid repetition, these will not be described again here.

[0443] This disclosure also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes of the method embodiments shown in FIG3 or FIG9 above and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0444] The technical solutions provided in this disclosure can be applied to a variety of systems. For example, applicable systems may include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) and its evolutionary communication systems, and 6G (sixth generation mobile communication technology) systems. All of these systems include terminal equipment and network equipment. The system may also include a core network component, such as the Evolved Packet System (EPS) or the 5G system (5GS).

[0445] The terminal devices involved in the embodiments of this disclosure can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in 5G or 6G systems, the terminal device may be called User Equipment (UE). Wireless terminal devices can be USB storage devices, other personal computer memory devices, and dongles. They can also communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices. For example, they can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples of such devices include Personal Communication Service (PCS) telephones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, and Machine-type Communication (MTC) terminal devices. Wireless terminal devices can also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile devices, remote stations, access points, remote terminals, access terminals, user terminals, user agents, user devices, and wireless access devices and routers / modems that meet the limitations of this definition, but are not limited to these in the embodiments of this disclosure.

[0446] The network device involved in this disclosure can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in this disclosure can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA) system, a NodeB in a wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, network testing equipment, etc., and is not limited in this disclosure. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0447] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0448] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0449] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0450] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0451] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0452] Furthermore, it should be noted that in the apparatus and method of this disclosure, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of this disclosure. Moreover, the steps performing the above series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of this disclosure can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof, which can be achieved by those skilled in the art using their basic programming skills after reading the description of this disclosure.

[0453] It should be noted that the above division of modules is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, a module can be a separate processing element, or it can be integrated into a chip in the aforementioned device. Alternatively, it can be stored as program code in the memory of the aforementioned device, and its function can be called and executed by a processing element of the device. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element mentioned here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0454] For example, each module, unit, subunit, or submodule can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs). As another example, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together to implement a system-on-a-chip (SOC).

[0455] The terms “first,” “second,” etc., used in this disclosure and in the claims are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this disclosure described herein may be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. Additionally, the use of “and / or” in the specification and claims indicates at least one of the connected objects, such as A and / or B and / or C, indicating seven possibilities: A alone, B alone, C alone, and both A and B, both B and C, both A and C, and A, B, and C. Similarly, the use of “at least one of A and B” in this specification and claims should be understood as “A alone, B alone, or both A and B.”

[0456] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A mobility management method applied to a terminal, the method comprising: Obtain at least two tracking area identifier lists, with different tracking area identifier lists corresponding to different access network types; Mobility management processing is performed based on the at least two tracking area identifier lists.

2. The method according to claim 1, wherein, Based on the at least two tracking area identifier list information, mobility management processing is performed, including: When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information. Once the tracking area identifier broadcast by the target base station is determined to be within the range of the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

3. The method according to claim 1, further comprising: When a terminal registers for the first time, it sends a registration request message to the first core network device. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

4. The method according to claim 1, wherein, The acquisition of at least two tracking area identification information includes: Receive first information, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type; The first information includes a registration confirmation message or a terminal configuration update command.

5. The method according to claim 2, wherein, The network handover is a first handover from the first base station to the second base station. The first handover is based on the direct communication interface between base stations. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. After updating the tracking area identifier list information that takes effect after network handover to the first tracking area identifier list information, the method further includes: The second access network type and the corresponding tracking area identifier list information are saved as alternatives.

6. The method according to claim 2, wherein, The network handover is a second handover from the first base station to the second base station. The second handover is based on the communication interface switch between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The first core network device is the target core network device. The method further includes: The device receives a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal. The updated tracking area identifier list information that takes effect after the network switch is the first tracking area identifier list information, including: When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

7. A mobility management method applied to a first core network device, the method comprising: At least two tracking area identifier list information are sent to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

8. The method according to claim 7, wherein, The step of sending at least two tracking area identifier list information to the terminal includes: Send first information to the terminal, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type; The first information includes a registration confirmation message or a terminal configuration update command.

9. The method according to claim 7, wherein, The step of sending at least two tracking area identifier list information to the terminal includes: Based on the first condition, send at least two tracking area identifier list information to the terminal; The first condition includes one or more of the following conditions: The terminal provides the ability to manage multiple sets of tracking area identifier lists; The types of access networks supported by the terminal's contracted data; The second information includes terminal location information and satellite coverage information of ephemeris.

10. The method according to claim 7, further comprising: When the terminal registers for the first time, a registration request message sent by the terminal is received. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information. Obtain the access network types supported by the terminal subscription data from the unified data management network element.

11. The method according to claim 7, wherein, The network handover that occurs at the terminal is a second handover from the first base station to the second base station. The second handover is based on the communication interface switch between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The first access network type and the second access network type are both one of at least two access network types, and the first core network device is the target core network device. The method further includes: The terminal context request message sent by the source core network device is received. The terminal context request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types and tracking area identifier list information corresponding to each access network type allocated by the source core network device to the terminal. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information. A terminal context creation response message is sent to the source core network device. The terminal context creation response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

12. The method according to claim 7, wherein, The network handover occurring at the terminal is a second handover from the first base station to the second base station. This second handover is based on a switch of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the source core network device. The method further includes: The first base station sends a handover command message to the terminal. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

13. A terminal, comprising: A transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; the processor is configured to read the program from the memory and perform the following processes: Obtain at least two tracking area identifier lists, with different tracking area identifier lists corresponding to different access network types; Mobility management processing is performed based on the at least two tracking area identifier lists.

14. The terminal according to claim 13, wherein, The processor is also used for: When the target access network for network switching is the first access network type, the tracking area identifier list information that takes effect after network switching is updated to the first tracking area identifier list information, and the first tracking area identifier list information is the tracking area identifier list information corresponding to the first access network type among the at least two tracking area identifier list information. Once it is determined that the TAI broadcast by the target base station is within the tracking area identifier list information that takes effect after the network handover, the mobility registration update process will not be initiated.

15. The terminal according to claim 13, wherein, The transceiver is also used for: When a terminal registers for the first time, it sends a registration request message to the first core network device. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information.

16. The terminal according to claim 13, wherein, The processor is also used for: The transceiver receives first information, which includes at least two access network types and a tracking area identifier list for each access network type. The first information includes a registration confirmation message or a terminal configuration update command.

17. The terminal according to claim 14, wherein, The network handover is a first handover from the first base station to the second base station. The first handover is based on the direct communication interface between base stations. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The processor is also used for: After updating the tracking area identifier list information that takes effect after the network switch to the first tracking area identifier list information, the second access network type and the tracking area identifier list information corresponding to the second access network type are saved as alternatives.

18. The terminal according to claim 14, wherein, The network handover is a second handover from the first base station to the second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. The second access network type is one of at least two access network types. The first core network device is the target core network device. The transceiver is also used for: The device receives a handover command message sent by the first base station. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal. The processor is also used for: When the second capability identifier indicates that the first core network device supports the capability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal, the tracking area identifier list information that takes effect after network handover is updated to the first tracking area identifier list information.

19. A mobility management device, comprising: The first acquisition unit is used to acquire at least two tracking area identifier list information, and different tracking area identifier list information corresponds to different access network types; The first processing unit is used to perform mobility management processing based on the at least two tracking area identifier list information.

20. A core network device, wherein the core network device is a first core network device, comprising: A transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor; The transceiver is used to send at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

21. The core network device according to claim 20, wherein, The transceiver is also used for: Send first information to the terminal, the first information including at least two access network types and a tracking area identifier list information corresponding to each access network type; The first information includes a registration confirmation message or a terminal configuration update command.

22. The core network device according to claim 20, wherein, The transceiver is also used for: Based on the first condition, send at least two tracking area identifier list information to the terminal; The first condition includes one or more of the following conditions: The terminal provides the ability to manage multiple sets of tracking area identifier lists; The types of access networks supported by the terminal's contracted data; The second information includes terminal location information and satellite coverage information of ephemeris.

23. The core network equipment according to claim 20, wherein, The transceiver is also used for: When the terminal registers for the first time, a registration request message sent by the terminal is received. The registration request message includes a first capability identifier and terminal location information. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information. Obtain the access network types supported by the terminal subscription data from the unified data management network element.

24. The core network equipment according to claim 20, wherein, The network handover occurring at the terminal is a second handover from the first base station to the second base station. This second handover is based on a switching of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the target core network device. The transceiver is also used for: The terminal context request message sent by the source core network device is received. The terminal context request message includes a first capability identifier carried by the terminal when registering with the source core network device, and at least two access network types and tracking area identifier list information corresponding to each access network type allocated by the source core network device to the terminal. The first capability identifier is used to identify whether the terminal supports the ability to manage multiple sets of tracking area identifier list information. A terminal context creation response message is sent to the source core network device. The terminal context creation response message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

25. The core network equipment according to claim 20, wherein, The network handover occurring at the terminal is a second handover from the first base station to the second base station. This second handover is based on a switch of the communication interface between the base station and the core network. The first access network type corresponding to the second base station is different from the second access network type corresponding to the first base station. Both the first and second access network types are at least one of two access network types, and the first core network device is the source core network device. The transceiver is also used for: The first base station sends a handover command message to the terminal. The handover command message includes a second capability identifier, which is used to identify whether the first core network device supports the ability to allocate corresponding tracking area identifier list information for different access network types supported by the terminal.

26. A mobility management device, comprising: The first sending unit is used to send at least two tracking area identifier list information to the terminal. Different tracking area identifier list information corresponds to different access network types. The at least two tracking area identifier list information is used for mobility management processing.

27. A non-transiently readable storage medium storing a program for performing the steps of the mobility management method according to any one of claims 1 to 6, or performing the steps of the mobility management method according to any one of claims 7 to 12.

Images