Mobility management method, apparatus, system, electronic device, and readable medium

Abstract

The present disclosure provides a mobility management method, device, system, electronic equipment and readable medium, which belongs to the technical field of communication. In the scheme, in the scenario that a UE is double-registered to a first core network and a second core network, the first core network can send the first TAI list allocated by itself to the second core network when allocating the TAI list for the UE, and then receive the second TAI list allocated to the UE after negotiation with the second core network. At this time, in the process of allocating the TAI list for the UE once, the second TAI list allocated by the first core network and the second core network together is obtained through negotiation, thereby simplifying the complex process of allocating the TAI list for the UE respectively. In addition, the second TAI list is allocated by the first core network and the second core network through negotiation, which also avoids the frequent initiation of signaling by the UE when moving between the first core network and the second core network, effectively reduces the network load and terminal energy consumption, and further improves the communication efficiency.

Description

Technical Field

[0001] This disclosure belongs to the field of communication technology, and specifically relates to mobility management methods, mobility management devices, mobility management systems, electronic devices, and computer-readable media. Background Technology

[0002] In mobile networks, to adapt to the complex scenarios of converged deployments, UEs (User Equipment) can selectively support dual registration in addition to single registration to meet service requirements. In dual registration mode, UEs can access different Radio Access Technologies (RATs) and their corresponding core networks sequentially or simultaneously.

[0003] In dual-registration mode, the movement of UEs between different core network combinations will cause a large amount of signaling transmission, resulting in low communication efficiency, high network load and high power consumption. Summary of the Invention

[0004] The purpose of this disclosure is to provide a mobility management method, mobility management device, mobility management system, electronic device, and computer-readable medium that can simplify the process of assigning TAIlists to UEs when UEs are dual-registered to a core network combination, and reduce signaling transmission when UEs move between core network combinations, thereby reducing network load and terminal power consumption, and thus improving communication efficiency.

[0005] To solve the above-mentioned technical problems, this disclosure is implemented as follows:

[0006] In a first aspect, this disclosure provides a mobility management method that can be applied to a first core network. The method may include: sending a first Tracking Area Identifier List (TAI list) assigned to a User Equipment (UE) to a second core network; dual-registering the UE to both the first and second core networks; and receiving a second TAI list assigned to the UE after negotiation with the second core network.

[0007] Optionally, the method further includes sending a response message to the UE, the response message including a second TAI list.

[0008] Optionally, the method further includes sending a response message to the UE, the response message including a second TAI list and an indication that the second TAI list is available under the second core network.

[0009] Optionally, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0010] Optionally, the method further includes: receiving a third TAI list allocated to the UE by the second core network; and sending a response message to the UE, the response message including the third TAI list.

[0011] Optionally, the third TAI list is used by the UE to perform mobility management under the second core network.

[0012] Optionally, the coverage area of ​​the third TAI list overlaps with that of the second TAI list.

[0013] Optionally, receiving the second TAI list allocated to the UE after negotiation with the second core network includes: receiving the second TAI list confirmed by negotiation with the second core network based on the first TAI list.

[0014] Optionally, the second TAI list is at least partially identical to the encoded content of the first TAI list.

[0015] Optionally, the method is applied to the functional network element responsible for mobility management under the first core network.

[0016] Optionally, the first TAI list is used for UE mobility management under the first core network.

[0017] Optionally, the first core network corresponds to the first RAT; the UE accesses the first core network through the first RAT, or the UE accesses the first core network through the second RAT; the second RAT is different from the first RAT.

[0018] Optionally, the response message may include either a re-registration acceptance message or a location update acceptance message.

[0019] Secondly, this disclosure provides a mobility management method that can be applied to a second core network. The method may include: receiving a first TAI list sent by a first core network; the first TAI list being allocated to the UE by the first core network, and the UE dual-registering with both the first core network and the second core network; and sending a negotiated second TAI list allocated to the UE to the first core network.

[0020] Optionally, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0021] Optionally, sending a negotiated second TAI list assigned to the UE to the first core network includes: sending a second TAI list negotiated and confirmed based on the first TAI list to the first core network.

[0022] Optionally, sending a negotiated second TAI list assigned to the UE to the first core network includes: sending a negotiated second TAI list confirmed based on the first TAI list to the first core network, and an indication that the second TAI list is available under the second core network.

[0023] Optionally, the method further includes: paging the UE within the second TAI list.

[0024] Optionally, the method further includes sending a third TAI list assigned to the UE to the first core network.

[0025] Optionally, the third TAI list is used by the UE to perform mobility management under the second core network.

[0026] Optionally, the coverage area of ​​the third TAI list overlaps with that of the second TAI list.

[0027] Optionally, the method further includes: paging the UE within the third TAI list.

[0028] Optionally, the method is applied to the functional network element responsible for mobility management under the second core network.

[0029] Thirdly, this disclosure provides a mobility management method that can be applied to a UE that is dual-registered with a first core network and a second core network. The method may include: receiving a response message sent by the first core network; the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network; and / or, the response message includes a third TAI list allocated by the second core network to the UE; and performing corresponding mobility management based on the response message.

[0030] Optionally, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and performing corresponding mobility management based on the response message includes: performing mobility management under the first core network based on the second TAI list.

[0031] Optionally, the response message includes a third TAI list allocated to the UE by the second core network, and performing corresponding mobility management based on the response message includes performing mobility management under the second core network based on the third TAI list.

[0032] Optionally, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and the response message also includes an indication that the second TAI list is available under the second core network. Performing corresponding mobility management based on the response message includes: performing mobility management under the first core network based on the second TAI list, and performing mobility management under the second core network based on the second TAI list.

[0033] Optionally, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0034] Optionally, the coverage area of ​​the third TAI list overlaps with that of the second TAI list.

[0035] Fourthly, this disclosure provides a mobility management device applied to a first core network. The device may include: a first transmitting module for transmitting a first TAI list allocated to a UE to a second core network; the UE dual-registering with both the first and second core networks; and a first receiving module for receiving a second TAI list allocated to the UE after negotiation with the second core network; the second TAI list corresponding to the same coverage area in both the first and second core networks.

[0036] Fifthly, this disclosure provides a mobility management device applied to a second core network. The device may include: a second receiving module for receiving a first TAI list sent by a first core network; the first TAI list is allocated to the UE by the first core network, and the UE is dual-registered to both the first core network and the second core network; and a second sending module for sending a negotiated second TAI list allocated to the UE to the first core network; the second TAI list corresponds to the same coverage area under both the first and second core networks.

[0037] In a sixth aspect, this disclosure provides a mobility management device applied to a UE, which is dual-registered to a first core network and a second core network. The device may include: a third receiving module for receiving a response message sent by the first core network; the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network; and / or, the response message includes a third TAI list allocated by the second core network to the UE; and a mobility management module for performing corresponding mobility management based on the response message; wherein the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0038] In a seventh aspect, this disclosure provides a mobility management system, which includes a first core network, a second core network, and a UE, wherein the UE is dual-registered with both the first core network and the second core network; wherein the first core network is used to execute the mobility management method of the first aspect; the second core network is used to execute the mobility management method of the second aspect; and the UE is used to execute the mobility management method of the third aspect.

[0039] Eighthly, this disclosure provides an electronic device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the mobility management method as described in the first, second, or third aspects.

[0040] Ninthly, this disclosure provides a computer-readable medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the mobility management method as described in the first, second, or third aspects.

[0041] In a tenth aspect, this disclosure provides a chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the mobility management methods of the first, second, or third aspects.

[0042] In one aspect, this disclosure provides a computer program product containing instructions that, when run on a computer, cause the computer to perform steps such as implementing the mobility management method of the first, second, or third aspect.

[0043] The mobility management method, mobility management device, mobility management system, electronic device, and computer-readable medium disclosed herein, in a scenario where a UE is dual-registered to a first core network and a second core network, allow the first core network to send its allocated first TAI list to the second core network when allocating a TAI list for the UE, and then receive a second TAI list allocated to the UE after negotiation with the second core network. In this case, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists for the UE. Furthermore, since the second TAI list is allocated through negotiation between the first and second core networks, it avoids frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency. Attached Figure Description

[0044] Figure 1 This is one of the flowcharts of the mobility management method provided in the embodiments of this disclosure;

[0045] Figure 2 The second flowchart of the mobility management method provided in this embodiment of the present disclosure;

[0046] Figure 3 The third step of the mobility management method provided in this embodiment of the disclosure;

[0047] Figure 4 The fourth step of the mobility management method provided in this embodiment of the disclosure;

[0048] Figure 5 The fifth step of the mobility management method provided in this embodiment of the disclosure;

[0049] Figure 6 This is one of the structural block diagrams of a mobility management device provided in an embodiment of the present disclosure;

[0050] Figure 7 This is a second structural block diagram of a mobility management device provided in an embodiment of the present disclosure;

[0051] Figure 8 This is the third structural block diagram of a mobility management device provided in this embodiment of the present disclosure;

[0052] Figure 9 A schematic diagram of the architecture of a mobility management system provided in an embodiment of this disclosure;

[0053] Figure 10 This is one of the schematic diagrams of an interaction process under a mobility management system provided in this disclosure embodiment;

[0054] Figure 11 This is a second schematic diagram of an interaction process under a mobility management system provided in this embodiment of the present disclosure;

[0055] Figure 12 This is the third schematic diagram of an interaction process in a mobility management system provided in this embodiment of the present disclosure;

[0056] Figure 13 This is the fourth schematic diagram of an interaction process under a mobility management system provided in this embodiment of the present disclosure;

[0057] Figure 14 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure;

[0058] Figure 15 This is a hardware schematic diagram of an electronic device provided in an embodiment of the present disclosure. Detailed Implementation

[0059] 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, not all, of the embodiments of this disclosure. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0060] The terms "first," "second," etc., used in this disclosure and in the claims are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this disclosure can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0061] Figure 1 This is one of the flowcharts illustrating the steps of a mobility management method provided in an embodiment of this disclosure. This method can be applied to a first core network, such as... Figure 1 As shown, the method may include the following steps 101 to 102.

[0062] Step 101: Send the first TAI list assigned to the UE to the second core network; the UE is dual-registered with both the first and second core networks.

[0063] In this embodiment, the first core network and the second core network can be core networks of different standards forming a core network combination, such as a combination of two 4G core networks, 5G core networks, and 6G core networks. The UE can adopt a dual registration mode, registering to the first core network and the second core network sequentially or simultaneously, so that the first core network and the second core network respectively support the UE's communication services.

[0064] A Tracking Area (TA) is obtained by dividing the global coverage area of ​​the core network and can be uniquely identified using a Tracking Area Identity (TAI). When allocating TAs to a UE, the first core network can use a first TAI list to correspond to a group of TAs. The first TAI list can include one or more TAIs, indicating that the first core network can support communication services when the UE is within the range of the corresponding TA. Based on this, the first core network can send the first TAI list to the second core network.

[0065] Step 102: Receive the second TAI list allocated to the UE after negotiation with the second core network.

[0066] In this embodiment of the disclosure, after the first core network sends the first TAI list to the second core network, the first core network can negotiate with the second core network, and on the basis of the negotiation, the first core network receives the second TAI list jointly allocated to the UE, indicating that the first core network and the second core network can support communication services when the UE is within the corresponding TA range.

[0067] Figure 2 This is a second flowchart illustrating the steps of the mobility management method provided in this embodiment. This method can be applied to a first core network. Specifically, this method can be applied to the functional network elements responsible for mobility management within the first core network.

[0068] In this embodiment, the method can be executed by a functional network element responsible for mobility management under the first core network. This functional network element is responsible for managing the UE's location information, security, and service continuity, maintaining connection status, and ensuring the quality of communication services. When the first core network adopts different standards, its corresponding functional network element may also be different. For example, when the first core network is a 5G core network, the functional network element can be an AMF (Access and Mobility Management Function); when the first core network is a 4G core network, the functional network element can be an MME (Mobility Management Entity); and when the first core network is a 6G core network, the functional network element can be a functional network element responsible for mobility management under the 6G core network.

[0069] In one optional embodiment of this disclosure, the first core network corresponds to the first RAT. The UE accesses the first core network through the first RAT, or the UE accesses the first core network through a second RAT; the second RAT is different from the first RAT.

[0070] In this embodiment of the disclosure, the first core network has a corresponding first RAT. For example, when the first core network is a 5G core network, the first RAT is a 5G RAT; when the first core network is a 4G core network, the first RAT is a 4G RAT; and when the first core network is a 6G core network, the first RAT is a 6G RAT. Based on this, the UE can access the first core network through the first RAT or through a second RAT different from the first RAT. This embodiment of the disclosure does not impose specific limitations on this.

[0071] like Figure 2 As shown, the method may include the following steps 201 to 206.

[0072] Step 201: Send the first TAI list assigned to the UE to the second core network; the UE dual-registers with both the first and second core networks.

[0073] In this embodiment of the disclosure, step 201 can be referred to the relevant description of step 101 above. To avoid repetition, it will not be repeated here.

[0074] In an optional embodiment of the method disclosed herein, the first TAI list is used for UE mobility management under the first core network.

[0075] In this embodiment of the disclosure, the first TAI list allocated by the first core network to the UE can be used for the UE's mobility management under the first core network. At this time, the UE can access the first core network through either the first RAT or the second RAT. However, the first core network does not directly send the first TAI list to the UE; instead, it sends the first TAI list to the second core network for negotiation.

[0076] Step 202: Receive the second TAI list allocated to the UE after negotiation with the second core network.

[0077] In this embodiment of the disclosure, step 202 can be referred to the aforementioned step 102. To avoid repetition, it will not be described again here.

[0078] In an optional embodiment of the method disclosed herein, step 202 may specifically include receiving a second TAI list that has been negotiated and confirmed with the second core network based on the first TAI list.

[0079] In this embodiment of the disclosure, the second TAI list may be based on the first TAI list, and the first core network and the second core network negotiate to retain or modify it for confirmation, so that the first core network and the second core network can support communication services when the UE is within the TA range corresponding to the second TAI list.

[0080] In an optional embodiment of the method disclosed herein, the encoded content of the second TAI list is at least partially the same as that of the first TAI list.

[0081] In this embodiment, the TAIs in the second TAI list have at least partially identical encoded content to the TAIs in the first TAI list. This means they can have completely identical encoded content, or partially identical and partially different encoded content. For example, if the first TAI list contains 1, 2, and 3, then the second TAI list can contain 1, 2, and 3, or 1, 2, or 2, 3, and 4. Here, 1, 2, 3, and 4 are the TAIs corresponding to the TAs. Under the same core network encoding rules, a TAI uniquely identifies a TA; however, under different core network encoding rules, different TAIs may correspond to the same TA.

[0082] In an optional embodiment of the method disclosed herein, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0083] In this embodiment of the disclosure, the second TAI list can correspond to the same coverage area under both the first core network and the second core network. Furthermore, one or more TAs corresponding to TAIs in the second TAI list under the first core network also correspond to the same one or more TAs under the second core network. Therefore, assuming the UE performs mobility management based on the second TAI list, when moving back and forth between the combination of the first and second core networks, the overhead of sending signaling to request TAI list allocation when moving from a TA under the first core network to a different TA under the second core network is reduced.

[0084] In an optional embodiment of the method disclosed herein, when the first core network and the second core network negotiate and determine the second TAI list, the second TAI list can be sent to the UE. In one scenario, the first core network can respond to the UE's request by sending the second TAI list to the UE via a response message, and instructing the UE to perform mobility management based on the second TAI list according to specific service requirements and implementation conditions. The second TAI list can be selectively applied to mobility management under the second core network through additional instructions to avoid unavailability due to different TA planning of the radio networks connected to the second core network and the first core network, or to avoid situations where the second TAI list is not used due to service requirements. The method may further include the following steps 203 or 204:

[0085] Step 203: Send a response message to the UE. The response message includes the second TAI list.

[0086] Step 204: Send a response message to the UE. The response message includes a second TAI list and an indication that the second TAI list is available in the second core network.

[0087] In this embodiment of the disclosure, the first core network can send response messages with different content to the UE based on the actual availability of the second TAI list under the second core network, to further indicate whether it can be used for mobility management under the second core network. Specifically, taking the scheme of step 203 or step 204 as an example, the response message can include the second TAI list but not the indication that the second TAI list is available under the second core network, to indicate that the second TAI list is actually unavailable under the second core network, or that the second TAI list is actually available under the second core network but is not used for mobility management under the second core network; alternatively, the response message can include both the second TAI list and the indication that the second TAI list is available under the second core network, indicating that the second TAI list is actually available under the second core network and can be used for mobility management under the second core network.

[0088] In an optional embodiment of the method disclosed herein, steps 205 to 206 are included:

[0089] Step 205: Receive the third TAI list assigned to the UE by the second core network.

[0090] Step 206: Send a response message to the UE. The response message includes a third TAI list.

[0091] In this embodiment of the disclosure, the first core network can also receive a third TAI list sent by the second core network. The third TAI list can be allocated to the UE by the second core network based on its own encoding rules and TA planning, so that the second core network can support communication services when the UE is within the TA range corresponding to the third TAI list. On this basis, the first core network can send a response message including the third TAI list to the UE.

[0092] In an optional embodiment of this disclosure, the third TAI list is used by the UE to perform mobility management under the second core network.

[0093] In this embodiment of the disclosure, the third TAI list sent by the first core network to the UE is allocated by the second core network to the UE and can be used by the UE for mobility management under the second core network.

[0094] It should be noted that steps 203, 204, or 205 to 206 provided in this embodiment can be implemented independently or in combination in practical applications to flexibly adapt to mobility management needs in different scenarios. For example, the first core network sends a response message to the UE. The response message may include a second TAI list, or it may include a third TAI list, or it may include both a second and a third TAI list, or it may include an indication that the second TAI list is available in the second core network, etc. This embodiment does not impose specific limitations on these aspects.

[0095] In an optional embodiment of the method disclosed herein, the coverage areas of the third TAI list overlap with those of the second TAI list.

[0096] In this embodiment, the third TAI list is allocated based on the encoding rules and TA planning of the second core network, while the second TAI list is allocated through negotiation between the first and second core networks. Based on this, the coverage area actually corresponding to the third TAI list can overlap with the coverage area actually corresponding to the second TAI list. Therefore, when a user moves within the coverage area of ​​the second TAI list, they are actually moving within the coverage area of ​​the third TAI list, thus avoiding the loss caused by multiple signaling initiations during movement.

[0097] In an optional embodiment of the method disclosed herein, the response message includes either a re-registration acceptance message or a location update acceptance message.

[0098] In this embodiment of the disclosure, the first core network can allocate a first TAI list to the UE based on the UE's request, and further negotiate with the second core network to allocate a second TAI list to the UE. For different request types, the first core network can send corresponding response messages to the UE, and provide the second TAI list and / or a third TAI list to the UE in the response messages. For example, the response message can be a re-registration acceptance message, indicating acceptance of the UE's request to re-register, or the response message can be a location update message, indicating that the UE's TA has been updated.

[0099] The mobility management method disclosed herein, in a scenario where a UE is dual-registered to both a first core network and a second core network, allows the first core network to send its allocated first TAI list to the second core network when assigning a TAI list to the UE, and then receive the second TAI list, negotiated with the second core network, assigned to the UE. In this way, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by both the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists to the UE. Furthermore, since the second TAI list is negotiated and allocated by the first and second core networks, it avoids the frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0100] Figure 3 This is the third flowchart illustrating the steps of a mobility management method provided in this embodiment. This method can be applied to a second core network. The method may include steps 301 to 302.

[0101] Step 301: Receive the first TAI list sent by the first core network; the first TAI list is assigned to the UE by the first core network, and the UE is dual-registered with the first core network and the second core network.

[0102] In this embodiment, the first core network, the second core network, and the first TAI list can be referred to the relevant description in step 101 above, and will not be repeated here to avoid repetition. The second core network can receive the first TAI list allocated to the UE by the first core network for subsequent negotiation.

[0103] Step 302: Send the negotiated second TAI list assigned to the UE to the first core network.

[0104] In this embodiment of the disclosure, when the second core network receives the first TAI list sent by the first core network, the second core network can negotiate with the first core network and send a second TIA list jointly allocated to the UE to the first core network based on the negotiation, indicating that the first core network and the second core network can support communication services when the UE is within the corresponding TA range.

[0105] Figure 4 This is the fourth flowchart illustrating the steps of the mobility management method provided in this embodiment. This method can be applied to a second core network. Specifically, this method can be applied to the functional network elements responsible for mobility management within the second core network.

[0106] In this embodiment, the method can be executed by a functional network element responsible for mobility management under the second core network. This functional network element is responsible for managing the UE's location information, security, and service continuity, maintaining connection status, and ensuring the quality of communication services. When the second core network adopts different standards, its corresponding functional network element may also be different. For example, when the second core network is a 5G core network, the functional network element can be an AMF (Access and Mobility Management Function); when the second core network is a 4G core network, the functional network element can be an MME (Mobility Management Entity); and when the second core network is a 6G core network, the functional network element can be a functional network element responsible for mobility management under the 6G core network.

[0107] It should be noted that the second core network can be referred to in the aforementioned manner. Figure 2 The description of the first core network is provided, but the second core network has a different standard than the first core network.

[0108] The method may include steps 401 to 406 as follows.

[0109] Step 401: Receive the first TAI list sent by the first core network; the first TAI list is assigned to the UE by the first core network, and the UE is dual-registered with the first core network and the second core network.

[0110] In this embodiment of the disclosure, step 401 can be referred to the relevant description of step 301 above. To avoid repetition, it will not be repeated here.

[0111] Step 402: Send the second TAI list, which has been negotiated and confirmed based on the first TAI list, to the first core network.

[0112] In this embodiment of the disclosure, step 402 can be referred to the relevant description of step 302 above. To avoid repetition, it will not be repeated here.

[0113] In this embodiment of the disclosure, the second TAI list may be based on the first TAI list, and the first core network and the second core network negotiate to retain or modify it for confirmation, so that the first core network and the second core network can support communication services when the UE is within the TA range corresponding to the second TAI list.

[0114] Step 403: Send the second TAI list, which has been negotiated and confirmed based on the first TAI list, to the first core network, along with an indication of the availability of the second TAI list under the second core network.

[0115] In this embodiment of the disclosure, the second core network can instruct the first core network according to specific service requirements and implementation conditions. The second TAI list can be used for mobility management under the second core network. With additional instructions, the second TAI list can be selectively applied to mobility management under the second core network to avoid situations where the second core network and the first core network are connected to different radio network TA plans, resulting in unavailability, or where the second TAI list is not used due to service requirements.

[0116] At this point, the second core network sends a second TAI list negotiated and confirmed based on the first TAI list, along with an indication that the second TAI list is available under the second core network. Thus, the second TAI list is actually used in the second core network in addition to being actually used in the first core network.

[0117] Based on this, if the second core network sends the second TAI list but does not send an indication that the second TAI list is usable under the second core network, then regardless of whether the TA corresponding to the second TAI list conforms to the coding rules and TA planning of the second core network, the second TAI list is not actually used in the second core network, even though it is actually used in the first core network. For details, please refer to the relevant descriptions of steps 203 or 204 above; to avoid repetition, they will not be repeated here.

[0118] In an optional embodiment of the method disclosed herein, step 403 may be followed by step 404.

[0119] Step 404: Paging the UE within the second TAI list.

[0120] In this embodiment of the disclosure, after the second core network sends a second TAI list and an indication that the second TAI list is available under the second core network, it indicates that the second TAI list can be used for mobility management under the second core network. Based on this, the second core network can page the UE within the range of the second TAI list to activate the UE from the idle state.

[0121] In an optional embodiment of the method disclosed herein, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0122] In this embodiment of the disclosure, the second TAI list can correspond to the same coverage area under both the first core network and the second core network. Furthermore, one or more TAs corresponding to TAIs in the second TAI list under the first core network also correspond to the same one or more TAs under the second core network. Therefore, assuming the UE performs mobility management based on the second TAI list, when moving back and forth between the combination of the first and second core networks, the overhead of sending signaling to request TAI list allocation when moving from a TA under the first core network to a different TA under the second core network is reduced.

[0123] In an optional embodiment of the method disclosed herein, the method may further include the following step 405.

[0124] Step 405: Send the third TAI list assigned to the UE to the first core network.

[0125] In this embodiment of the disclosure, the second core network may also allocate a third TAI list to the UE and send the third TAI list to the first core network. The third TAI list includes a set of TAIs under the coding rules of the second core network, each uniquely identifying a TA under the radio access network plan to which the second core network is connected, thereby enabling the second core network to support communication services when the UE is within the range of the TA corresponding to the third TAI list.

[0126] In an optional embodiment of this disclosure, the third TAI list is used by the UE to perform mobility management under the second core network.

[0127] In this embodiment of the disclosure, the third TAI list sent by the second core network to the first core network can be sent by the first core network to the UE for the UE to perform mobility management under the second core network.

[0128] In an optional embodiment of the method disclosed herein, the coverage areas of the third TAI list overlap with those of the second TAI list.

[0129] In this embodiment, the third TAI list is allocated based on the encoding rules and TA planning of the second core network, while the second TAI list is allocated through negotiation between the first and second core networks. Based on this, the coverage area actually corresponding to the third TAI list can overlap with the coverage area actually corresponding to the second TAI list. Therefore, when a user moves within the coverage area of ​​the second TAI list, they are actually moving within the coverage area of ​​the third TAI list, thus avoiding the loss caused by multiple signaling initiations during movement.

[0130] In an optional embodiment of the method disclosed herein, step 405 may be followed by step 406.

[0131] Step 406: Paging the UE within the third TAI list.

[0132] In this embodiment of the disclosure, after the second core network sends the third TAI list to the first core network, it indicates that the third TAI list can be used for mobility management under the second core network. Based on this, the second core network can page the UE within the range of the third TAI list to activate the UE from the idle state.

[0133] The mobility management method disclosed herein, in a scenario where a UE is dual-registered to both a first core network and a second core network, allows the second core network to receive a first TAI list sent by the first core network. This first TAI list is allocated to the UE by the first core network. Furthermore, the second core network, after negotiation with the first core network, sends a second TAI list allocated to the UE back to the first core network. In this case, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by both the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists to the UE. Moreover, the second TAI list being allocated through negotiation between the first and second core networks avoids frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0134] Figure 5 This is the fifth flowchart illustrating the steps of a mobility management method provided in this embodiment. The method can be applied to a UE (User Equipment). The UE is dual-registered to both a first core network and a second core network. The method may include steps 501 to 502.

[0135] Step 501: Receive a response message sent by the first core network; the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network; and / or, the response message includes a third TAI list allocated by the second core network for the UE.

[0136] In this embodiment, the UE is dual-registered with both a first core network and a second core network, and receives response messages through the first core network without needing to make additional independent requests through the second core network. The response message sent by the first core network may include a second TAI list negotiated and confirmed by the first and second core networks, a third TAI list allocated to the UE by the second core network, or both a second and third TAI list, to flexibly adapt to different implementation conditions and service requirements.

[0137] Step 502: Perform the corresponding mobility management based on the response message.

[0138] In this embodiment of the disclosure, the UE can perform corresponding mobility management based on the TAI list in the response message, and perform mobility management based on the TAI list provided by the first core network in the response message. Depending on the type of the TAI list, the UE can execute different mobility management schemes.

[0139] In an optional embodiment of this disclosure, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and step 502 may include the following step A.

[0140] Step A: Perform mobility management under the first core network based on the second TAI list.

[0141] In this embodiment of the disclosure, when the response message sent by the first core network includes a second TAI list, the second TAI list is obtained by negotiation after the first core network sends the first TAI list allocated to the UE to the second core network, indicating that the UE can perform mobility management under the first core network based on the second TAI list.

[0142] In an optional embodiment of this disclosure, the response message includes a third TAIlist allocated to the UE by the second core network, and step 502 may include step B as follows.

[0143] Step B: Perform mobility management under the second core network based on the third TAI list.

[0144] In this embodiment of the disclosure, when the response message sent by the first core network includes a third TAI list, the third TAI list is allocated and obtained by the second core network for the UE, indicating that the UE can perform mobility management under the second core network based on the third TAI list.

[0145] In an optional embodiment of this disclosure, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and the response message also includes an indication that the second TAI list is available under the second core network. Step 502 may include the following step C.

[0146] Step C: Perform mobility management under the first core network based on the second TAI list, and perform mobility management under the second core network based on the second TAI list.

[0147] In this embodiment of the disclosure, when the response message sent by the first core network includes a second TAI list negotiated and confirmed by the first core network and the second core network, and also includes an indication that the second TAI list is available under the second core network, it indicates that the UE can perform mobility management under the first core network based on the second TAI list, or it can perform mobility management under the second core network based on the second TAI list. At this time, the UE can perform the corresponding mobility management according to the actual scenario.

[0148] In an optional embodiment of the method disclosed herein, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0149] In this embodiment of the disclosure, the second TAI list can correspond to the same coverage area under both the first core network and the second core network. Furthermore, one or more TAs corresponding to TAIs in the second TAI list under the first core network also correspond to the same one or more TAs under the second core network. Therefore, assuming the UE performs mobility management based on the second TAI list, when moving back and forth between the combination of the first and second core networks, the overhead of sending signaling to request TAI list allocation when moving from a TA under the first core network to a different TA under the second core network is reduced.

[0150] In an optional embodiment of the method disclosed herein, the coverage areas of the third TAI list overlap with those of the second TAI list.

[0151] In this embodiment, the third TAI list is allocated based on the encoding rules and TA planning of the second core network, while the second TAI list is allocated through negotiation between the first and second core networks. Based on this, the coverage area actually corresponding to the third TAI list can overlap with the coverage area actually corresponding to the second TAI list. Therefore, when a user moves within the coverage area of ​​the second TAI list, they are actually moving within the coverage area of ​​the third TAI list, thus avoiding the loss caused by multiple signaling initiations during movement.

[0152] The mobility management method disclosed herein, in a scenario where a UE is dual-registered to both a first core network and a second core network, allows the UE to receive a response message sent by the first core network. This response message may include a second TAI list negotiated and confirmed by the first and second core networks, or a third TAI list allocated to the UE by the second core network, or both a second and a third TAI list. Based on this, the UE can perform mobility management based on the response message. In this case, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists for the UE. Furthermore, the second TAI list being negotiated and allocated by the first and second core networks avoids frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0153] Figure 6 This is one of the structural block diagrams of a mobility management device 600 provided in an embodiment of the present disclosure. The device can be applied to a first core network and may include: a first sending module 601, used to send a first TAI list allocated to a UE to a second core network; the UE dual-registers with both the first and second core networks; a first receiving module 602, used to receive a second TAI list allocated to the UE after negotiation with the second core network; the second TAI list corresponds to the same coverage area under both the first and second core networks.

[0154] In an optional embodiment of the present disclosure, the first sending module 601 is further configured to send a response message to the UE, the response message including a second TAI list.

[0155] In an optional embodiment of the apparatus disclosed herein, the first sending module 601 is further configured to send a response message to the UE, the response message including a second TAI list and an indication that the second TAI list is available under the second core network.

[0156] In an optional device embodiment of this disclosure, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0157] In an optional device embodiment of this disclosure, the first receiving module 602 is further configured to receive a third TAI list allocated to the UE by the second core network; and the first sending module 601 is further configured to send a response message to the UE, the response message including the third TAI list.

[0158] In an optional device embodiment of this disclosure, the third TAI list is used by the UE to perform mobility management under the second core network.

[0159] In an optional device embodiment of this disclosure, the coverage areas of the third TAI list overlap with those of the second TAI list.

[0160] In an optional device embodiment of this disclosure, the first transmitting module 601 is specifically used to receive a second TAI list negotiated and confirmed with the second core network based on the first TAI list.

[0161] In an optional embodiment of the apparatus disclosed herein, the encoded content of the second TAI list is at least partially the same as that of the first TAI list.

[0162] In an optional embodiment of this disclosure, the device is applied to a functional network element responsible for mobility management under a first core network.

[0163] In an optional device embodiment of this disclosure, the first TAI list is used for UE mobility management under the first core network.

[0164] In an optional device embodiment of this disclosure, the first core network corresponds to a first radio access technology (RAT); the UE accesses the first core network through the first RAT, or the UE accesses the first core network through a second RAT; the second RAT is different from the first RAT.

[0165] In an optional embodiment of the apparatus disclosed herein, the response message includes either a re-registration acceptance message or a location update acceptance message.

[0166] The mobility management device provided in this embodiment is applied to a first core network. In a scenario where a UE is dual-registered to both the first and second core networks, when the first core network allocates a TAI list for the UE, it can send its allocated first TAI list to the second core network and then receive the second TAI list allocated to the UE after negotiation with the second core network. In this way, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists for the UE. Furthermore, since the second TAI list is allocated through negotiation between the first and second core networks, it avoids the frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0167] Figure 7This is a second structural block diagram of a mobility management device 700 provided in an embodiment of the present disclosure. The device can be applied to a second core network and may include: a second receiving module 701, used to receive a first TAI list sent by a first core network; the first TAI list is allocated by the first core network to the UE, and the UE is dual-registered to both the first core network and the second core network; a second sending module 702, used to send a second TAI list, which is negotiated and allocated to the UE, to the first core network; the second TAI list corresponds to the same coverage area under both the first core network and the second core network.

[0168] In one optional device embodiment of this disclosure, the second TAI list corresponds to the same coverage area under both the first core network and the second core network.

[0169] In an optional device embodiment of this disclosure, the second sending module 702 is specifically used to send a second TAI list negotiated and confirmed based on the first TAI list to the first core network.

[0170] In an optional device embodiment of this disclosure, the second sending module 702 is specifically used to send to the first core network a second TAI list negotiated and confirmed based on the first TAI list, and an indication that the second TAI list is available under the second core network.

[0171] In an optional embodiment of the apparatus disclosed herein, the apparatus further includes a paging module for paging the UE within a second TAI list.

[0172] In an optional embodiment of the apparatus disclosed herein, the second transmitting module 702 is further configured to transmit a third TAI list allocated to the UE to the first core network.

[0173] In an optional device embodiment of this disclosure, the third TAI list is used by the UE to perform mobility management under the second core network.

[0174] In an optional device embodiment of this disclosure, the coverage areas of the third TAI list overlap with those of the second TAI list.

[0175] In an optional embodiment of the apparatus disclosed herein, the apparatus further includes a paging module for paging the UE within a third TAI list.

[0176] In one optional embodiment of this disclosure, the device is applied to a functional network element responsible for mobility management under a second core network.

[0177] The mobility management device provided in this embodiment is applied to a second core network. In a scenario where a UE is dual-registered to both a first core network and a second core network, the second core network can receive a first TAI list sent by the first core network, which is allocated to the UE by the first core network. The second core network can also send a second TAI list allocated to the UE back to the first core network after negotiation with the first core network. In this case, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists to the UE. Furthermore, the second TAI list being allocated through negotiation between the first and second core networks avoids frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0178] Figure 8 This is a third structural block diagram of a mobility management device 800 provided in an embodiment of the present disclosure. The device can be applied to a UE that is dual-registered with a first core network and a second core network. The device may include: a third receiving module 801, used to receive a response message sent by the first core network; the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network; and / or, the response message includes a third TAI list allocated by the second core network to the UE; and a mobility management module 802, used to perform corresponding mobility management based on the response message; wherein the second TAI list corresponds to the same coverage area under both the first and second core networks.

[0179] In an optional device embodiment of this disclosure, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network. The mobility management module 802 is specifically used to perform mobility management under the first core network based on the second TAI list.

[0180] In an optional device embodiment of this disclosure, the response message includes a third TAI list allocated to the UE by the second core network, and the mobility management module 802 is specifically used to perform mobility management under the second core network based on the third TAI list.

[0181] In an optional device embodiment of this disclosure, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and the response message also includes an indication that the second TAI list is available under the second core network. The mobility management module 802 is specifically used to perform mobility management under the first core network based on the second TAI list, and to perform mobility management under the second core network based on the second TAI list.

[0182] In an optional device embodiment of this disclosure, the second TAI list corresponds to the same coverage area under the first core network and the second core network.

[0183] In an optional device embodiment of this disclosure, the coverage areas of the third TAI list overlap with those of the second TAI list.

[0184] The mobility management apparatus provided in this disclosure, in a scenario where a UE is dual-registered to both a first core network and a second core network, allows the UE to receive a response message sent by the first core network. This response message may include a second TAI list negotiated and confirmed by the first and second core networks, or a third TAI list allocated to the UE by the second core network, or both a second and a third TAI list. Based on this, the UE can perform mobility management based on the response message. In this case, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists for the UE. Furthermore, the second TAI list being negotiated and allocated by the first and second core networks avoids the UE frequently initiating signaling when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0185] Figure 9 This is a schematic diagram of the architecture of a mobility management system 900 provided in an embodiment of this disclosure. The system may include a first core network 902, a second core network 903, and a UE 901, which is dual-registered to both the first core network 902 and the second core network 903. The first core network 902 can be used to perform the aforementioned... Figures 1 to 2 Any mobility management method; the second core network 903 can be used to execute the aforementioned Figures 3 to 4 Any mobility management method; UE 901 can be used to perform the aforementioned Figure 5 The mobility management method described above is used. The first core network 902, the second core network 903, and the UE 901 interact based on the above mobility management method, thereby simplifying the process and reducing the signaling initiation, which in turn reduces network load and terminal power consumption, and improves communication efficiency.

[0186] For example, UE 901 can access the first core network 902 via RAT 904, and access the second core network 903 via RAT 905. RAT 904 and RAT 905 are different.

[0187] In this embodiment, a scenario where the UE's location changes while moving is used as an example. In this case, the UE can initiate a re-registration or location update request to the first core network. The mobility management system includes a first core network, a second core network, and the UE. The first core network corresponds to RAT 1, and the second core network corresponds to RAT 2. The UE registers with both the first core network and the second core network sequentially or simultaneously through RAT 1 and RAT 2. Figure 10 This is one of the schematic diagrams of an interaction process under a mobility management system provided in this disclosure embodiment, such as... Figure 10 As shown, the interaction process may include steps 1001 to 1006.

[0188] Step 1001: The UE sends a re-registration or location update request to the first core network via RAT 1.

[0189] Step 1002: The first core network assigns the first TAI list to the UE.

[0190] Step 1003: The first core network sends the first TAI list to the second core network for negotiation.

[0191] Step 1004: The second core network sends a confirmation to the first core network of the second TAI list jointly assigned to the UE.

[0192] Step 1005: The first core network sends the second TAI list to the UE via a response message.

[0193] Step 1006: The UE performs mobility management under the first core network based on the second TAI list.

[0194] Figure 11 This is a second schematic diagram of an interaction process under a mobility management system provided in this disclosure embodiment, as shown below. Figure 11 As shown, the interaction process may include steps 1101 to 1108.

[0195] Step 1101: The UE sends a re-registration or location update request to the first core network via RAT 1.

[0196] Step 1102: The first core network assigns the first TAI list to the UE.

[0197] Step 1103: The first core network sends the first TAI list to the second core network for negotiation.

[0198] Step 1104: The second core network sends a confirmation to the first core network of the second TAI list jointly assigned to the UE, and an indication that the second TAI list can be used by the second core network.

[0199] Step 1105: The first core network sends the second TAI list to the UE via a response message, along with an indication that the second TAI list can be used by the second core network.

[0200] Step 1106: The UE performs mobility management under the first core network based on the second TAI list.

[0201] Step 1107: The UE performs mobility management in the second core network based on the second TAI list.

[0202] Based on this, the method may also include the following step 1108.

[0203] Step 1108: When the second core network receives the downlink data corresponding to the UE, it pages the UE within the second TAIlist range via RAT 2.

[0204] Figure 12 This is the third schematic diagram of an interaction process under a mobility management system provided in this disclosure embodiment, as shown below. Figure 12 As shown, the interaction process may include steps 1201 to 1207.

[0205] Step 1201: The UE sends a re-registration or location update request to the first core network via RAT 1.

[0206] Step 1202: The first core network assigns the first TAI list to the UE.

[0207] Step 1203: The first core network sends the first TAI list to the second core network for negotiation.

[0208] Step 1204: The second core network sends a confirmation to the first core network of the second TAI list jointly assigned to the UE, and the third TAI list assigned to the UE by the second core network.

[0209] Step 1205: The first core network sends the third TAI list to the UE via a response message.

[0210] Step 1206: The UE performs mobility management in the second core network based on the third TAI list.

[0211] Based on this, the method may also include the following step 1207.

[0212] Step 1207: When the second core network receives the downlink data corresponding to the UE, it pages the UE within the third TAIlist range via RAT 2.

[0213] Figure 13This is the fourth schematic diagram of an interaction process in a mobility management system provided in this disclosure, as shown in the following embodiment. Figure 13 As shown, the interaction process may include steps 1301 to 1308.

[0214] Step 1301: The UE sends a re-registration or location update request to the first core network via RAT 1.

[0215] Step 1302: The first core network assigns the first TAI list to the UE.

[0216] Step 1303: The first core network sends the first TAI list to the second core network for negotiation.

[0217] Step 1304: The second core network sends a confirmation to the first core network of the second TAI list jointly assigned to the UE, and the third TAI list assigned to the UE by the second core network.

[0218] Step 1305: The first core network sends the second TAI list and the third TAI list to the UE via a response message.

[0219] Step 1306: The UE performs mobility management under the first core network based on the second TAI list.

[0220] Step 1307: The UE performs mobility management in the second core network based on the third TAI list.

[0221] Based on this, the method may also include the following step 1308.

[0222] Step 1308: When the second core network receives the downlink data corresponding to the UE, it pages the UE within the third TAIlist range via RAT 2.

[0223] The mobility management system provided in this disclosure, in a scenario where a UE is dual-registered to both a first core network and a second core network, allows the first core network to send its allocated first TAI list to the second core network when assigning a TAI list to the UE, and then receive the second TAI list assigned to the UE after negotiation with the second core network. In this case, during a single TAI list allocation process for the UE, a second TAI list jointly allocated by both the first and second core networks is negotiated, simplifying the complex process of separately allocating TAI lists to the UE. Furthermore, the fact that the second TAI list is allocated through negotiation between the first and second core networks avoids the frequent signaling initiation by the UE when moving between the first and second core networks, effectively reducing network load and terminal power consumption, thereby improving communication efficiency.

[0224] Figure 14 This is a schematic diagram of the structure of an electronic device 1400 provided in an embodiment of this disclosure, as shown below. Figure 14 As shown, the electronic device 1400 may include a processor 1401, a memory 1402, and a program or instructions stored in the memory 1402 and executable on the processor 1401. When the program or instructions are executed by the processor 1401, they implement the various processes of the above signaling interoperability embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0225] It should be noted that, Figure 14 The illustrated electronic device 1400 is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0226] Figure 15 This is a hardware schematic diagram of an electronic device 1500 provided in an embodiment of the present disclosure, as shown below. Figure 15 As shown, the electronic device 1500 includes a Central Processing Unit (CPU) 1501, which can perform various appropriate actions and processes based on programs stored in ROM (Read Only Memory) 1502 or programs loaded from storage section 1508 into RAM (Random Access Memory) 1503. The RAM 1503 also stores various programs and data required for system operation. The CPU 1501, ROM 1502, and RAM 1503 are interconnected via bus 1504. An I / O (Input / Output) interface 1505 is also connected to bus 1504.

[0227] The following components are connected to I / O interface 1505: an input section 1506 including a keyboard, mouse, etc.; an output section 1507 including CRT (Cathode Ray Tube), LCD (Liquid Crystal Display), etc., and speakers, etc.; a storage section 1508 including a hard disk, etc.; and a communication section 1509 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1509 performs communication processing via a network such as the Internet. A drive 1510 is also connected to I / O interface 1505 as needed. Removable media 1511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1510 as needed so that computer programs read from them can be installed into storage section 1508 as needed.

[0228] In particular, according to embodiments of this disclosure, the processes described below with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1509, and / or installed from removable medium 1511. When the computer program is executed by the central processing unit (CPU 1501), it performs various functions defined in the system of this application.

[0229] This disclosure also transmits a computer-readable medium storing a program or instructions that, when executed by a processor, implement the various processes of the above signaling interoperability embodiments and achieve the same technical effects. To avoid repetition, these will not be described again here.

[0230] The processor is the processor in the electronic device described in the above embodiments. The computer-readable medium includes computer-readable media such as ROM, RAM, magnetic disk, or optical disk.

[0231] This disclosure also discloses a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above signaling interoperability embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0232] It should be understood that the chip mentioned in the embodiments of this disclosure may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0233] This disclosure provides a computer program product containing instructions that, when run on a computer, causes the computer to perform the signaling interoperability steps described above and achieves the same technical effect. To avoid repetition, further details are omitted here.

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

[0235] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solutions of this disclosure, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, electronic device, air conditioner, or network device, etc.) to execute the methods of the various embodiments of this disclosure.

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

Claims

1. A mobility management method, characterized in that, The method is applied to the first core network, and the method includes: The first Tracking Area Identifier (TAI) list assigned to the User Equipment (UE) is sent to the second core network; the UE is dual-registered with both the first core network and the second core network. The system receives a second TAI list, which is allocated to the UE after negotiation with the second core network. The second TAI list has at least partially the same encoded content as the first TAI list. Send a response message to the UE, the response message including the second TAI list; or, send a response message to the UE, the response message including the second TAI list, and an indication that the second TAI list is available under the second core network.

2. The method according to claim 1, characterized in that, The second TAI list corresponds to the same coverage area under the first core network and the second core network.

3. The method according to claim 1, characterized in that, The method further includes: Receive the third TAI list allocated to the UE by the second core network; A response message is sent to the UE, the response message including the third TAI list.

4. The method according to claim 3, characterized in that, The third TAI list is used by the UE to perform mobility management under the second core network.

5. The method according to claim 3, characterized in that, The coverage area of ​​the third TAI list overlaps with that of the second TAI list.

6. The method according to claim 1, characterized in that, The second TAI list, which is negotiated with the second core network and allocated to the UE, includes: Receive the second TAI list, which is negotiated and confirmed with the second core network based on the first TAI list.

7. The method according to any one of claims 1 to 6, characterized in that, The method is applied to the functional network element responsible for mobility management under the first core network.

8. The method according to any one of claims 1 to 6, characterized in that, The first TAI list is used for the mobility management of the UE under the first core network.

9. The method according to any one of claims 1 to 6, characterized in that, The first core network corresponds to the first radio access technology (RAT). The UE accesses the first core network through the first RAT, or the UE accesses the first core network through the second RAT; the second RAT is different from the first RAT.

10. The method according to any one of claims 1 to 5, characterized in that, The response message includes either a re-registration acceptance message or a location update acceptance message.

11. A mobility management method, characterized in that, The method is applied to the second core network, and the method includes: Receive the first TAI list sent by the first core network; the first TAI list is allocated to the UE by the first core network, and the UE is dual-registered to the first core network and the second core network; Send a negotiated second TAI list to the first core network, wherein the encoded content of the second TAI list is at least partially the same as that of the first TAI list; Sending the negotiated second TAI list assigned to the UE to the first core network includes: Send the second TAI list, negotiated and confirmed based on the first TAI list, to the first core network; or send the second TAI list, negotiated and confirmed based on the first TAI list, and an indication that the second TAI list is available under the second core network, to the first core network.

12. The method according to claim 11, characterized in that, The second TAI list corresponds to the same coverage area under the first core network and the second core network.

13. The method according to claim 11, characterized in that, The method further includes: Paging is performed on the UE within the second TAI list.

14. The method according to claim 11, characterized in that, The method further includes: Send the third TAI list allocated to the UE to the first core network.

15. The method according to claim 14, characterized in that, The third TAI list is used by the UE to perform mobility management under the second core network.

16. The method according to claim 14, characterized in that, The coverage area of ​​the third TAI list overlaps with that of the second TAI list.

17. The method according to claim 14, characterized in that, The method further includes: Paging is performed on the UE within the third TAI list.

18. The method according to claim 11, characterized in that, The method is applied to the functional network element responsible for mobility management under the second core network.

19. A mobility management method, characterized in that, The method is applied to a UE, wherein the UE is dual-registered to a first core network and a second core network, and the method includes: The system receives a response message sent by the first core network; the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, wherein the encoded content of the second TAI list is at least partially the same as that of the first TAI list; and / or, the response message includes a third TAI list allocated by the second core network for the UE. Based on the response message, perform the corresponding mobility management; The response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and the execution of corresponding mobility management based on the response message includes: Mobility management is performed on the first core network based on the second TAI list; Alternatively, the response message may include a second TAI list negotiated and confirmed by the first core network and the second core network, and the response message may also include an indication that the second TAI list is available under the second core network. The execution of corresponding mobility management based on the response message includes: Mobility management is performed on the first core network based on the second TAI list, and mobility management is performed on the second core network based on the second TAI list.

20. The method according to claim 19, characterized in that, The response message includes a third TAI list allocated to the UE by the second core network, and the execution of corresponding mobility management based on the response message includes: Mobility management is performed under the second core network based on the third TAI list.

21. The method according to any one of claims 19 and 20, characterized in that, The second TAI list corresponds to the same coverage area under the first core network and the second core network.

22. The method according to claim 19, characterized in that, The coverage area of ​​the third TAI list overlaps with that of the second TAI list.

23. A mobility management device, characterized in that, The device is applied to the first core network, and the device includes: The first sending module is used to send the first TAI list allocated to the UE to the second core network; the UE is dual-registered to both the first core network and the second core network. The first receiving module is used to receive a second TAI list allocated to the UE after negotiation with the second core network; the second TAI list corresponds to the same coverage area under the first core network and the second core network, and the encoded content of the second TAI list is at least partially the same as that of the first TAI list; The first sending module is further configured to send a response message to the UE, the response message including the second TAIlist; or, the first sending module is further configured to send a response message to the UE, the response message including the second TAIlist and an indication that the second TAIlist is available in the second core network.

24. A mobility management device, characterized in that, The device is applied to the second core network, and the device includes: The second receiving module is used to receive the first TAI list sent by the first core network; the first TAI list is allocated by the first core network to the UE, and the UE is dual-registered to the first core network and the second core network. The second sending module is used to send a negotiated second TAI list allocated to the UE to the first core network; the second TAI list corresponds to the same coverage area under the first core network and the second core network, and the encoded content of the second TAI list is at least partially the same as that of the first TAI list; The second sending module is specifically used to send the second TAI list, which is negotiated and confirmed based on the first TAI list, to the first core network; or, the second sending module is specifically used to send the second TAI list, which is negotiated and confirmed based on the first TAI list, and an indication that the second TAI list is available in the second core network to the first core network.

25. A mobility management device, characterized in that, The device is applied to a UE, which dual-registers to a first core network and a second core network. The device includes: The third receiving module is used to receive a response message sent by the first core network; the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, wherein the encoded content of the second TAI list is at least partially the same as that of the first TAI list; and / or, the response message includes a third TAI list allocated by the second core network for the UE. A mobility management module is used to perform corresponding mobility management based on the response message; wherein the second TAIlist corresponds to the same coverage area in both the first core network and the second core network; The response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and the mobility management module is specifically used to perform mobility management under the first core network based on the second TAI list; or, the response message includes a second TAI list negotiated and confirmed by the first core network and the second core network, and the response message also includes an indication that the second TAI list is available under the second core network, and the mobility management module is specifically used to perform mobility management under the first core network based on the second TAI list, and to perform mobility management under the second core network based on the second TAI list.

26. A mobility management system, characterized in that, The system includes a first core network, a second core network, and a UE, wherein the UE is dual-registered to both the first core network and the second core network; wherein the first core network is used to execute the mobility management method according to any one of claims 1 to 10. The second core network is used to execute the mobility management method according to any one of claims 11 to 18; The UE is used to execute the mobility management method according to any one of claims 19 to 22.

27. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the mobility management method as described in any one of claims 1 to 22.

28. A computer-readable medium, characterized in that, The computer-readable medium stores a program or instructions that, when executed by a processor, implement the mobility management method as described in any one of claims 1 to 22.

29. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the mobility management method according to any one of claims 1 to 22.

Images