Registration information synchronization method, apparatus, device, and medium

Abstract

This invention provides a registration information synchronization method, apparatus, device, and medium. The method can be applied to a terminal and includes: when the terminal switches from a first communication system to a second communication system, sending a first tracking area update request message to a network device of the second communication system, the first tracking area update request message including a first GUTI of the terminal in the first communication system; receiving a tracking area update acceptance message from the network device, the tracking area update acceptance message including a second GUTI configured for the terminal; when it is determined that the tracking area update completion message transmission failed, triggering a set timer to start counting until the set timer expires, and then sending a second tracking area update request message to the network device, the second tracking area update request message including the second GUTI. This method is used to improve the probability of successful registration information synchronization in a registration information synchronization scenario.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a registration information synchronization method, apparatus, device and medium. Background Technology

[0002] The current 3rd Generation Partner Project (3GPP) protocol supports interoperability between 4G and 5G mobile communication technology systems. This means that in a network environment where both 5G and 4G networks exist, a terminal can switch between them. 5G is the latest generation of mobile communication technology, offering higher data rates, lower latency, full connectivity for the Internet of Things, greater energy efficiency, lower costs, higher system capacity, and massive device access.

[0003] When a terminal switches from a 5G system to a 4G system, it generally needs to initiate a Tracking Area Update (TAU) process to synchronize the registration information between the terminal and the network-side equipment. However, a failure of TAU can cause the terminal to lose network access, resulting in a poor user experience such as being unable to use 4G system services and dropped calls.

[0004] Therefore, there is an urgent need to provide a new method for synchronizing registration information to improve the success rate of the TAU process, thereby increasing the likelihood of successful registration information synchronization in network switching scenarios. Summary of the Invention

[0005] The purpose of this invention is to provide a registration information synchronization method, apparatus, device, and medium, which improves the likelihood of successful registration information synchronization in network switching scenarios.

[0006] In a first aspect, the present invention provides a registration information synchronization method, which can be applied to a terminal device, comprising: when the terminal switches from a first communication system to a second communication system, sending a first tracking area update request message to a network device of the second communication system, the first tracking area update request message including a first GUTI of the terminal in the first communication system; receiving a tracking area update acceptance message from the network device, the tracking area update acceptance message including a second GUTI configured for the terminal; when it is determined that the tracking area update completion message transmission failed, triggering a set timer to start counting until the set timer expires, and then sending a second tracking area update request message to the network device, the second tracking area update request message including the second GUTI.

[0007] The beneficial effects of the registration information synchronization method provided by this invention are as follows: when a terminal undergoes a network switch, the second GUTI allocated by the switched network is used to retry the TAU process, which helps to increase the probability of the TAU process succeeding. This method can improve the probability of successful registration information synchronization in network switching scenarios without affecting the user's normal use, thereby ensuring business continuity and improving user experience.

[0008] In one possible implementation, sending a second request message to the network device of the second communication system includes: determining whether the tracking area of ​​the cell currently in which the terminal is camped has changed compared to the tracking area of ​​the cell in which it camped when switching to the second communication system; and if it has changed, sending a second request message to the network device of the second communication system. In this implementation, because the tracking area of ​​the terminal's cell has changed, using the second GUTI allocated by the network after the switch to retry the TAU procedure helps increase the likelihood of a successful TAU procedure.

[0009] In another possible implementation, the method further includes: if no change has occurred, resending the first tracking area update request message to the network device of the second communication system. In this implementation, since the tracking area of ​​the terminal's cell has not changed, using the first GUTI to retry the TAU procedure helps increase the likelihood of a successful TAU procedure.

[0010] Other possible implementations include: establishing a service link with the network device of the second communication system when a successful tracking area location update is detected. In this implementation, when the TAU process is successful, the terminal can communicate normally with the network device in the switched network.

[0011] In another possible implementation, when the first communication system is a 5G system, the second communication system is a 4G system.

[0012] Secondly, embodiments of this application provide a registration information synchronization device. Each unit in this device can also execute other possible design methods described in the first aspect above, as detailed in the first aspect. These modules / units can be implemented in hardware or by hardware executing corresponding software.

[0013] Thirdly, embodiments of this application provide a terminal, including a memory and a processor. The memory stores a computer program that can run on the processor. When the computer program is executed by the processor, it causes the electronic device to perform any of the possible design methods described in the first aspect above.

[0014] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes an electronic device to perform any of the possible design methods described in the first aspect.

[0015] Fifthly, embodiments of this application also provide a chip or chip module, the chip and / or chip module memory being coupled for executing a computer program stored in the memory, so that the terminal device executes any of the possible design methods of the first aspect described above.

[0016] For the beneficial effects of the second to fifth aspects mentioned above, please refer to the description of the first aspect mentioned above. Attached Figure Description

[0017] Figure 1 A schematic diagram of a network architecture provided in an embodiment of the present invention;

[0018] Figure 2 This is a schematic diagram of a PDN connection provided in an embodiment of this application;

[0019] Figure 3 A schematic diagram of a PDU session provided in an embodiment of this application;

[0020] Figure 4 This is a schematic flowchart of a registration information synchronization method provided in an embodiment of the present invention;

[0021] Figure 5 This is a schematic diagram of another registration information synchronization method provided in an embodiment of the present invention;

[0022] Figure 6 This is a schematic diagram of the registration information synchronization device provided in the embodiments of this application;

[0023] Figure 7 This is a schematic diagram of the terminal structure provided in an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0025] In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can indicate: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0026] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0027] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0028] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5th Generation (5G) systems, or New Radio (NR) systems, or to future communication systems or other similar communication systems.

[0029] The technical solutions provided in this application are applicable to scenarios where a terminal device switches from a first communication system to a second communication system. The first and second communication systems support different communication standards. Thus, the first communication system can also be referred to as a first network or a first-standard system, and the second communication system can also be referred to as a second network or a second-standard system. For example, the first communication system can be a 5G communication system, and the second communication system can be a 4G communication system. The 5G communication system can also be referred to as a 5G network or simply a 5G system, and the 4G communication system can also be referred to as an EPS network or simply a 4G system. It should be understood that the first and second communication systems in this application's embodiments can also be future communication systems or other similar communication systems. This application is not limited in this regard. Furthermore, the bearer in this application's embodiments can also be referred to as a Quality of Service (QoS) flow, or it can be referred to by other names (without changing functionality) in future communication systems. This application is not limited in this regard.

[0030] See Figure 1 This is a schematic diagram of a possible network architecture applicable to the embodiments of this application, in which 5G network and EPS network coexist. The main network elements involved in this network architecture are described below.

[0031] An EPS network may include the following network elements:

[0032] 1. Radio access network (RAN) element: Used to provide network access functionality for authorized terminal devices in a specific area, and can use transmission tunnels of different quality according to the level of the terminal device, service requirements, etc.

[0033] (R)AN network elements manage radio resources, provide access services to terminal devices, and forward control signals and terminal device data between the terminal devices and the core network. (R)AN network elements can also be understood as base stations in traditional networks. In 4G communication systems, (R)AN network elements can also be called evolved universal terrestrial radio access networks (E-UTRAN) or evolved terrestrial base stations (eNBs), such as... Figure 1 As shown in the image.

[0034] It should be noted that the aforementioned "network element" can also be referred to as an entity, device, apparatus, or module, etc., and this application does not specifically limit it. Furthermore, in this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the (R)AN network element is abbreviated as RAN. In this case, the "(R)AN network element" should be understood as a (R)AN network element or a (R)AN entity. The following omits descriptions of the same or similar cases.

[0035] 2. The Mobility Management Entity (MME) provides mobility management functions. In addition, the MME can also provide functions such as lawful surveillance and access authorization / authentication.

[0036] 3. Serving Gateway (SGW): Used to provide functions such as user data forwarding.

[0037] 4. Packet data network gateway user function (PGW-U) is used to provide user plane functions for public data network (PDN) gateways.

[0038] 5. Packet data network gateway control function (PGW-C) is used to provide control plane functions for the PDN gateway.

[0039] 6. Policy and charging rules function (PCRF): This function provides a unified policy framework to guide network behavior and provides policy rule information to control plane function elements.

[0040] 7. Home subscriber server (HSS), which includes user profiles, performs user authentication and authorization, and provides information about the user's physical location.

[0041] 5G networks may include the following network elements:

[0042] 1. (R)AN network element: used to provide network access function for authorized terminal equipment in a specific area, and can use transmission tunnels of different quality according to the level of the terminal equipment, service requirements, etc.

[0043] In 5G communication systems, (R)AN network elements can also be called next-generation radioaccess networks (NG-RAN, e.g.) Figure 1 (as shown) or next-generation base station (gNB).

[0044] 2. Access and Mobility Management Function (AMF): This function manages access and mobility. In addition, AMF can provide functions such as lawful interception and access authorization / authentication.

[0045] In one possible design, the AMF can communicate with the MME via the N26 interface. Figure 1 In this application, the letters and numbers attached to the connection between network elements indicate the name of the communication interface between the network elements. However, the communication interface between network elements may have other names, which are not limited herein.

[0046] 3. User plane function (UPF) is used for packet routing and forwarding, as well as quality of service (QoS) processing or execution for user plane data.

[0047] 4. Session Management Function (SMF): Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, and selection and management of user plane functions. Additionally, the SMF can serve as the endpoint for policy control and billing function interfaces.

[0048] 5. Policy control function (PCF): A unified policy framework used to guide network behavior, providing policy rule information to control plane function elements (such as AMF, SMF, etc.).

[0049] 6. The Unified Data Management (UDM) network element is used to manage contracted data. It is also used for user service registration management, processing terminal device identification, and access authentication.

[0050] In the network architecture described above, network elements with the same or similar functions can be jointly configured or deployed in a single unit. For example, UPF and PGW-U can be co-located in one device or deployed separately in different devices; SMF and PGW-C can be co-located in one device or deployed separately in different devices; PCF and PCRF can be co-located in one device or deployed separately in different devices; and HSS and UDM can be co-located in one device or deployed separately in different devices.

[0051] It should be understood that the network architecture described above in this application is merely an example of a network architecture described from the perspective of a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0052] The aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0053] In an EPS network, user equipment (UE) establishes a PDN connection with the network. Each PDN connection can establish at least one bearer. The internal structure of a PDN connection is as follows: Figure 2 As shown, the main features are as follows:

[0054] (1) A PDN connection corresponds to an Access Point Name (APN) and an Aggregated Maximum Bit Rate (APN-AMBR) of the Access Point Name. Among them, the APN and APN-AMBR are obtained by the MME from the HSS during the location request process during UE attachment.

[0055] (2) In a PDN connection, there is one and only one default EPSbearer, which is created during the establishment of the PDN connection. At least one Service Data Flow (SDF) can be aggregated in a default EPSbearer. In a PDN connection, there may also be one or more non-guaranteed bit rate EPSbearers (Non-GBR EPSbearers), which are created during the establishment of a dedicated EPSbearer initiated by the UE or the network side. A non-GBR EPSbearer has at least one SDF and may also aggregate one or more other SDFs. In a PDN connection, there may also be one or more guaranteed bit rate EPSbearers (GBR EPSbearers), which are created during the establishment of a dedicated EPSbearer initiated by the UE or the network side. A GBR EPSbearer has at least one SDF and may also aggregate one or more other SDFs.

[0056] in, Figure 2 Each bearer in the network has corresponding QoS parameters and is used to transmit the corresponding SDF. The MME network element assigns an EPS bearer identity (EBI) to each bearer and sends the EPS bearer identity to the UE during the bearer establishment process. For the default bearer, the EPS bearer identity (bearerID) is sent to the UE during the PDN connection establishment process; for dedicated bearers, the EPS bearer identity (bearer ID) is sent to the UE during the dedicated bearer establishment process.

[0057] The QoS parameters for the default bearer and the dedicated bearer are different. The QoS parameters for different types of EPS bearers are shown in Table 1.

[0058] Table 1

[0059]

[0060] In a 5G network, the UE and the network establish a Protocol Data Unit (PDU) session. Each PDU session can establish at least one Quality of Service (QoS) flow. The internal structure of a PDU session is as follows: Figure 3 As shown, the main features are as follows:

[0061] (1) A PDU session corresponds to a DNN, a PDU session identifier (PDU Session ID), and a session aggregate maximum bit rate (Session AMBR). Among them: the DNN and Session AMBR are obtained by the AMF from the UDM during the location request process in the UE registration process; the PDU session ID is assigned by the SMF network element during the PDU session establishment process initiated by the UE.

[0062] (2) A PDU session has one and only one default QoS flow, created during the PDU session establishment process. A default QoS flow can aggregate at least one SDF. A PDU session can also contain one or more non-GBR QoS flows, created during the PDU session modification process initiated by the UE or network side. A non-GBR QoS flow has at least one SDF and can also aggregate multiple SDFs. A PDU session can also contain one or more guaranteed bit rate evolved packet system (GBR) QoS flows, created during the PDU session modification process initiated by the UE or network side. A GBR QoS flow has at least one SDF and can also aggregate multiple SDFs.

[0063] in, Figure 3 Each QoS flow in the network has corresponding QoS parameters and is used to transmit the corresponding service data flow. The SMF network element assigns a Quality of Service Flow ID (QFI) to each QoS flow and sends the QFI to the UE. For the default QoS flow, the QFI is sent to the UE during the establishment of the PDU session; for the dedicated QoS flow, the QFI is sent to the UE during the establishment of the dedicated QoS flow.

[0064] The QoS parameters for the default QoS flow and the dedicated QoS flow are different. The QoS parameters for different types of QoS flows are shown in Table 2.

[0065] Table 2

[0066]

[0067] In the embodiments of this application, the QoS parameters in Tables 1 and 2 are merely illustrative examples. QoS parameters may include one or more of the above parameters, and the embodiments of this application do not impose limitations.

[0068] In summary, during the interoperability between Long Term Evolution (LTE) and 5G networks, PDU sessions correspond to PDN connections, and EPS bearers correspond to QoS flows. Specifically, the correspondence is shown in Table 3.

[0069] Table 3

[0070]

[0071] In this embodiment, user equipment (UE) can also be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. The terminal equipment in this application embodiment can be a mobile phone, tablet computer, smart printer, train detector, gas station detector, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The embodiments of this application do not limit the application scenarios.

[0072] from Figure 1 As can be seen from the network architecture shown, in Figure 1 In the scenario shown where 5G and EPS networks coexist, terminal devices can be moved (including switching or redirecting) from the 4G communication system to the 5G communication system, or they can be moved (including switching or redirecting) from the 5G communication system to the 4G communication system.

[0073] In LTE systems, the concept of a Tracking Area (TA) is introduced to facilitate terminal location management. A TA is defined as a free-moving area where the terminal does not need to update services. Therefore, when a terminal moves from one TA to another, it needs to re-register its location on the new TA to notify the network equipment to update the stored terminal registration information. This process is called a Tracking Area Update (TAU). The TAU process involves numerous network elements, such as the evolved NodeB (eNB), MME, Serving Gateway (SGW), Home Subscriber Server (HSS), and Home Location Register (HLR).

[0074] like Figure 4 As shown in the figure, an embodiment of this application provides a registration information synchronization method, which includes:

[0075] S401, the terminal switches from the first communication system to the second communication system.

[0076] S402, the terminal sends a first tracking area update request message to the second communication system.

[0077] The first Tracking Area Update Request (TAURequest) message includes the terminal's first Globally Unique Temporary Identity (GUTI) in the first communication system.

[0078] S403, the second network sends a tracking area update acceptance message to the terminal.

[0079] The Tracking Area Update Accept (TAU Accept) message includes a second GUTI configured for the terminal.

[0080] S404, the terminal determined that the tracking area update completion message failed to be sent, triggering the set timer to start counting.

[0081] S405, when the set timer expires, a second tracking area update request message is sent to the network device, the second tracking area update request message including the second GUTI.

[0082] S406, the network device of the second communication system updates the registration information of the terminal stored in the network device according to the second request message.

[0083] Optionally, before executing S403, the following judgment is also performed: when the terminal determines through cell signal measurement that the tracking area (TA) of the currently camped cell has changed compared to the TA of the cell camped when switching to the second communication system, the terminal sends a second request message to the second network; when the terminal determines through cell signal measurement that the TA of the currently camped cell is the same as the TA of the cell camped when switching to the second communication system, the terminal sends the first request message to the second network again, and then the network device of the second network updates the registration information of the terminal stored in the network device according to the first request message.

[0084] In one possible implementation, when the terminal detects that the tracking area location update is successful, the terminal establishes a service link with the network device of the second communication system, and then the terminal obtains communication services in the second communication system after the switch.

[0085] The following text uses the example of a UE switching from a 5G network to an LTE network as an example to systematically illustrate the above registration information synchronization method. Figure 5 As shown, the method includes the following steps:

[0086] S501, the UE switches from the 5G network to the LTE network.

[0087] S502, when the UE switches from the 5G network to the LTE network, the UE sends a first TAU ​​request message to the network device of the LTE network. The first TAU ​​request message includes a first GUTI.

[0088] In this step, the UE's LTE Non-Access Stratum (NAS) can send a TAU Request message.

[0089] S503, the network device of the LTE network returns a TAU accept message to the UE, which includes a second GUTI configured for the terminal.

[0090] S504, the UE sends a TAU complete message to the network equipment of the LTE network.

[0091] S505, the UE determines that the TAU completion message transmission failed, and the UE starts a T3411 timer with a duration of 10s.

[0092] After the previous TAU fails, the UE will trigger the first timer to start counting. During the first timer period, although the UE is in the state of attempting to register and update the tracking area location, it suspends sending tracking area location update requests (TAURequest). After the first timer expires, the UE resends the TAU Request to perform TAU.

[0093] S506, when T3411 times out, the UE determines whether the TA of the cell where the UE is camped has changed compared with the TA of the cell where the UE is camped after switching to the LTE network. If so, S507 is executed; otherwise, S508 is executed.

[0094] S507, if the TA of the cell where the UE is camped changes compared to the TA of the cell where it camped when switching to the LTE network, the UE sends a second GUTI to try the TAU procedure again.

[0095] S508, if the TA of the cell where the UE is camped has not changed compared with the TA of the cell where it is camped after switching to the LTE network, the UE sends the first GUTI again and tries the TAU procedure again.

[0096] S509, the terminal updates the registration information of the terminal stored in the network device.

[0097] Afterwards, once the TAU is successful and the registration information between the UE and the LTE network is synchronized, the UE can establish a service link with the network equipment of the LTE network. The registration information includes at least the UE's TA information, and may also include the GUTI assigned to the UE by the network equipment and the UE's request to establish user plane resources.

[0098] It should be understood that there are many reasons why UETAU may fail, such as: underlying failure, timer timeout, TAU rejection caused by EPS Mobility Management (Evolved Packet System-Mobility Management, EMM), etc.

[0099] To implement the functions of the communication methods provided in the embodiments of this application, the terminal may include a hardware structure and / or a software module, implementing the functions in the form of a hardware structure, a software module, or a combination of hardware and software modules. Whether a particular function is executed in the form of a hardware structure, a software module, or a combination of hardware and software modules depends on the specific application and design constraints of the technical solution.

[0100] Similar to the concepts in the above embodiments, this application also provides a registration information synchronization device 600, which is used to implement the terminal function in the above method. For example, the registration information synchronization device 600 can be a terminal or a device within a terminal device. This device can be a chip system within the terminal. In this application embodiment, the chip system can be composed of chips or can include chips and other discrete components.

[0101] In one example, such as Figure 6 As shown, the registration information synchronization device 600 includes a sending unit 601 and a receiving unit 602.

[0102] The sending unit 601 is used to send a first tracking area update request message to the network device of the second communication system when the terminal switches from the first communication system to the second communication system. The first tracking area update request message includes the first globally unique temporary identifier (GUTI) of the terminal in the first communication system.

[0103] The receiving unit 602 is configured to receive a tracking area update acceptance message from a network device of the second communication system, the tracking area update acceptance message including a second GUTI configured for the terminal;

[0104] The sending unit 601 is further configured to, when it is determined that the tracking area update completion message transmission has failed, trigger a set timer to start timing until the set timer expires, and then send a second tracking area update request message to the network device of the second communication system. The second tracking area update request message includes the terminal's second GUTI in the second communication system.

[0105] The device further includes a processing unit 603, used to: transmit services with the network equipment of the second communication system when a successful update of the tracking area location is detected.

[0106] For details on the specific execution process and beneficial effects of the above units, please refer to the above. Figure 4 The relevant methods are documented.

[0107] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0108] In another example, such as Figure 7As shown, the terminal includes at least one processor 710 and a memory 720. The memory 720 stores a computer program. The memory 720 and the processor 710 are coupled. In this embodiment, the coupling is an intermittent coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information interaction between devices, units, or modules. Alternatively, the memory 720 may be located outside the communication device 700. The processor 710 can operate collaboratively with the memory 720. The processor 710 can call the computer program stored in the memory 720. At least one of the at least one memory may be included in the processor.

[0109] In some embodiments, the communication device 700 may further include a communication interface 730 for communicating with other devices via a transmission medium, thereby enabling the devices in the communication device 700 to communicate with other devices. Exemplarily, the communication interface 730 may be a transceiver, circuit, bus, module, or other type of communication interface, and the other device may be another terminal. The processor 710 utilizes the communication interface 730 to send and receive information and to implement the methods in the above embodiments. Exemplarily, the communication interface 730 is used to receive resource indication information. Also exemplaryly, the communication interface 730 is used to send data.

[0110] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0111] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions for storing computer programs and / or data.

[0112] The methods provided in this application can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any medium accessible to a computer or a data storage device such as a server or data center that integrates one or more media. The medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., SSD), etc.

[0113] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for synchronizing registration information, characterized in that, Applied to terminals, including: When the terminal switches from the first communication system to the second communication system, it sends a first tracking area update request message to the network device of the second communication system. The first tracking area update request message includes the terminal's first globally unique temporary identifier (GUTI) in the first communication system. Receive a Tracking Area Update Acceptance Message from the network device, the Tracking Area Update Acceptance Message including a second GUTI configured for the terminal; A tracking area update complete message is sent to the network device. If the tracking area update complete message fails to be sent, a set timer is triggered to start counting. After the set timer expires, it is determined whether the tracking area of ​​the cell where the terminal is currently camped has changed compared with the tracking area of ​​the cell where it camped when switching to the second communication system. If the tracking area has changed, a second tracking area update request message is sent to the network device. The second tracking area update request message includes the second GUTI.

2. The method according to claim 1, characterized in that, Also includes: If the tracking area remains unchanged, the first tracking area update request message is sent again to the network device of the second communication system.

3. The method according to any one of claims 1 to 2, characterized in that, Also includes: When a successful update of the tracking area location is detected, a service link is established with the network device of the second communication system.

4. The method according to any one of claims 1 to 2, characterized in that, When the first communication system is a 5G system, the second communication system is a 4G system.

5. A registration information synchronization device, characterized in that, include: The sending unit is configured to send a first tracking area update request message to the network device of the second communication system when the terminal switches from the first communication system to the second communication system. The first tracking area update request message includes the first globally unique temporary identifier (GUTI) of the terminal in the first communication system. A receiving unit is configured to receive a tracking area update acceptance message from a network device of the second communication system, the tracking area update acceptance message including a second GUTI configured for the terminal; The sending unit is further configured to send a tracking area update complete message to the network device. When it is determined that the tracking area update complete message failed to be sent, a set timer is triggered to start counting until the set timer expires. Then, it is determined whether the tracking area of ​​the cell where the terminal is currently camped has changed compared with the tracking area of ​​the cell where it camped when switching to the second communication system. When the tracking area has changed, a second tracking area update request message is sent to the network device of the second communication system. The second tracking area update request message includes the terminal's second GUTI in the second communication system.

6. The apparatus according to claim 5, characterized in that, The transmitting unit is further configured to: If the tracking area remains unchanged, the first tracking area update request message is sent again to the network device of the second communication system.

7. The apparatus according to any one of claims 5 to 6, characterized in that, The device further includes a processing unit for: When a successful update of the tracking area location is detected, service transmission is performed with the network equipment of the second communication system.

8. The apparatus according to any one of claims 5 to 6, characterized in that, When the first communication system is a 5G system, the second communication system is a 4G system.

9. A terminal, characterized in that, It includes a processor and a memory; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory to cause the terminal to perform the method of any one of claims 1 to 4.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 4.

11. A chip module, characterized in that, The chip module is coupled to a memory for executing a computer program stored in the memory to perform the method as described in any one of claims 1 to 4.

Images