Information synchronization method and related device

Abstract

Disclosed in the present application are an information synchronization method and a related device. In one embodiment, an information synchronization method comprises: a first network device acquiring identification information of terminal devices and identification information of a first access network device; the first network device determining a second network device on the basis of the identification information of the first access network device, wherein the second network device is a local network device that provides a service for a terminal device accessing the first access network device when a backhaul link is interrupted; and the first network device sending authentication subscription information of the terminal device that is to be synchronized to the second network device, wherein the authentication subscription information of the terminal device is used for authentication and authorization, at the second network device, of the terminal device accessing the first access network device. Using a method of synchronizing authentication subscription information of some terminal devices to a local network device on demand can not only reduce the storage capacity of the local network device that is used for storing the authentication subscription information of the terminal devices, but can also reduce the risk of disclosure when synchronizing the authentication subscription information of the terminal devices, thus improving the security of the authentication subscription information of the terminal devices.

Description

Information synchronization method and related equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 28, 2023, with application number 202311282656.2 and application name “Information Synchronization Method and Related Equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and in particular to an information synchronization method and related equipment. Background Art

[0003] Isolated E-UTRAN Operation for Public Safety (IOPS) technology: refers to the technology that maintains a certain level of communication capability for terminal devices (e.g., terminal devices of public safety users) through one or a group of IOPS-supported access network devices after backhaul communication is lost. Specifically, this IOPS technology forms an independent service radio access network without backhaul communication by deploying local network devices (e.g., local core network devices and local mission critical (MC) systems) near the access network devices to replace the macro network devices (e.g., macro core network devices and macro MC systems) in the core computer room. This allows the radio access network to use the local network devices to provide communication services such as authentication to public safety users.

[0004] In traditional technology, before backhaul communications are interrupted, the macro network device synchronizes the authentication and subscription information of all terminal devices with a local network device deployed near the access network device. When backhaul communications are interrupted, the access network device activates IOPS mode and forwards relevant information, including authentication requests, from terminal devices residing on the access network device to the local network device. The local network device then provides communication services, including authentication, to the terminal devices residing on the access network device based on the stored authentication and subscription information.

[0005] However, the method of having the local network device store the authentication and contract information of all terminal devices has high requirements on the storage capacity of the local network device, and may also increase the risk of the authentication and contract information of the terminal devices being leaked, thereby reducing security.

[0006] Summary of the Invention

[0007] The present application provides an information synchronization method and related equipment, which adopts the method of synchronizing the authentication and contract information of some terminal devices to the local network device on demand. This not only reduces the storage capacity of the local network device used to store the authentication and contract information of the terminal device, but also reduces the risk of leakage when synchronizing the authentication and contract information of the terminal device, thereby improving the security of the authentication and contract information of the terminal device.

[0008] In a first aspect, the present application provides an information synchronization method, which can be executed by a first network device or by a component of the first network device (e.g., a processor, a chip, or a chip system). Taking the first network device as an example, the first network device obtains identification information of a terminal device and identification information of a first access network device; then, the first network device determines a second network device based on the identification information of the first access network device, where the second network device is a local network device that provides services to the terminal device accessing the first access network device when the backhaul link is interrupted; then, the first network device sends authentication and contract information of the terminal device to be synchronized to the second network device, where the authentication and contract information of the terminal device is used for authentication of the terminal device accessing the first access network device on the second network device.

[0009] It should be understood that the authentication contract information of the terminal device includes the identification information of the terminal device. The first network device can find the authentication contract information corresponding to the terminal device from the authentication contract information of numerous terminal devices based on the received identification information of the terminal device.

[0010] In the present application, the first network device can obtain the identification information of the terminal device and the identification information of the first access network device, and determine the second network device (i.e., the local network device that provides services for the terminal device accessing the first access network device when the backhaul link is interrupted) based on the identification information of the first access network device, and then send the authentication and contract information of the terminal device to the second network device, so that when the terminal device resides on the first access network device, the second network device can use the authentication and contract information of the terminal device for the terminal device to authenticate and authenticate, and then provide communication services for the terminal device. Since the first network device only synchronizes the authentication and contract information of the terminal device that may reside on the first access network device to the second network device, rather than synchronizing the authentication and contract information of all terminal devices, it is beneficial to save the storage space of the local network device (i.e., the second network device) and reduce the storage performance requirements of the local network device. In addition, since only the authentication and contract information of some terminal devices is synchronized to the second network device, and the authentication and contract information of other terminal devices is still stored in the first network device, it is beneficial to reduce the risk of the authentication and contract information of the terminal device being leaked during the synchronization process and improve the security of the authentication and contract information of the stored terminal device.

[0011] In one possible implementation, a first network device stores a first correspondence relationship, where the first correspondence relationship is used to indicate a correspondence relationship between the first access network device and a second network device. The first network device determines the second network device based on identification information of the first access network device, including: the first network device determines the second network device corresponding to the first access network device based on the identification information of the first access network device and the first correspondence relationship.

[0012] In this embodiment, the first network device maintains a correspondence between the access network device and the local network device (for example, the aforementioned first correspondence). The first network device can accurately query the second network device corresponding to the first access network device based on the identification information of the first access network device, which is beneficial to improving the accuracy of the authentication and signing information of the terminal device synchronized by the first network device to the second network device.

[0013] Specifically, the first network device can synchronize the authentication contract information of the terminal device to the second network device directly or indirectly.

[0014] In a possible implementation, the first network device directly sends the authentication subscription information of the terminal device to the second network device.

[0015] If the first network device determines that the connection path between the first network device and the second network device is not interrupted, the first network device sends the authentication contract information of the terminal device to the second network device.

[0016] Exemplarily, the first network device sends a first message, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and contract information of the terminal device.

[0017] In this embodiment, the first network device encapsulates the address information of the second network device in the message header and encapsulates the authentication and contract information of the terminal device in the payload of the message, so that after the first network device sends the message, the message can be transmitted to the second network device. Synchronizing the authentication and contract information of the terminal device through the connection path between the first and second network devices is conducive to ensuring the efficiency of synchronizing the authentication and contract information.

[0018] In another possible implementation, the first network device indirectly sends the authentication and subscription information of the terminal device to the second network device, that is, the first network device forwards the authentication and subscription information of the terminal device to the second network device through other devices or network elements.

[0019] If the first network device determines that the connection path between the first network device and the second network device is interrupted, the first network device determines the second access network device and a third network device corresponding to the second access network device based on the identification information of the first access network device, where the third network device is a local network device that provides services to terminal devices accessing the second access network device when the backhaul link is interrupted, and there is a connection path between the first access network device and the second access network device, and there is a connection path between the first access network device and the second network device; the first network device sends the authentication and contract information of the terminal device to the second network device via the third network device. The third network device is configured to forward the authentication and contract information of the terminal device to the second network device via the connection path between the first access network device and the second access network device.

[0020] In this embodiment, although the connection path between the first network device and the second network device is interrupted, the connection path between the first network device and the third network device is not interrupted, and a connection exists between the first access network device corresponding to the second network device and the second access network device corresponding to the third network device. Therefore, the first network device sends the authentication and contract information of the terminal device to the third network device, and the third network device forwards the authentication and contract information of the terminal device to the second network device via the connection path between the first access network device and the second access network device. This helps to improve the reliability of the synchronization of the authentication and contract information from the first network device to the second network device.

[0021] Exemplarily, the first network device sends a second message, the destination address field of the message header of the second message carries the address information of the third network device, and the payload field of the second message carries the authentication and contract information of the terminal device and the address information of the second network device; the address information of the second network device in the payload field is used by the third network device to generate a third message to be sent to the second network device, the destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and contract information of the terminal device.

[0022] In this embodiment, by carrying the address information of the second network device and the authentication contract information of the terminal device in the payload of the second message, it is indicated that the final recipient of the authentication contract information of the terminal device is the second network device rather than other network devices, which is beneficial for the network device (for example, the third network device) that receives the second message to forward the authentication contract information of the terminal device to the second network device.

[0023] In one possible implementation, the first network device stores a second correspondence, the second correspondence being used to indicate a correspondence between the first access network device and the second access network device; the first network device stores a third correspondence, the third correspondence being used to indicate a correspondence between the second access network device and the third network device. The first network device determines the second access network device and the third network device corresponding to the second access network device based on identification information of the first access network device, including: the first network device determines the second access network device based on the identification information of the first access network device and the second correspondence; and the first access network device determines the third network device corresponding to the second access network device based on the identification information of the second access network device and the third correspondence.

[0024] In this embodiment, it is proposed that the first network device not only maintains the correspondence between the access network device and the local network device (for example, the first correspondence and the third correspondence), but also maintains the correspondence between the access network device and the adjacent access network device (or the connected access network device) (for example, the second correspondence), so that the first network device searches for the second access network device connected to the first access network device based on the identification information of the first access network device and the second correspondence, and then searches for the third network device deployed near the second access network device based on the identification information of the second access network device and the third correspondence. By maintaining the aforementioned correspondence, it is beneficial to improve the path for the first network device to search for the authentication and contract information of the forwarding terminal device, and improve the efficiency of the first network device in synchronizing the authentication and contract information of the terminal device.

[0025] In one possible implementation, a first network device stores identification information of a third access network device and address information of a fourth network device, the third access network device being an access network device previously accessed by a terminal device, the fourth network device being a local network device providing services to a terminal device accessing the third access network device when a backhaul link is interrupted, and the fourth network device storing authentication and subscription information of the terminal device. The method further includes: when the identification information of the first access network device differs from the identification information of the third access network device, the first network device sending first indication information to the fourth network device, the first indication information being used to instruct deletion of the authentication and subscription information of the terminal device.

[0026] In this embodiment, if the local network device corresponding to the access network device to which the terminal device has historically accessed (i.e., the fourth network device corresponding to the third access network device) stores the terminal device's authentication and contract information, the first network device stores the identification information of the third access network device and the address information of the fourth network device. When the first network device receives the terminal device's identification information and the identification information of the first access network device, indicating that the terminal device has left the second access network device, the first network device instructs the fourth network device, via first instruction information, to delete the terminal device's authentication and contract information stored by the fourth network device to ensure the security of the terminal device's authentication and contract information.

[0027] In a possible implementation, after the first network device sends the authentication and contract information of the terminal device to be synchronized to the second network device, the method also includes: the first network device obtains the identification information of the terminal device and the identification information of a fourth access network device, and the fourth access network device is different from the first access network device; the first network device sends a first indication information to the second network device, and the first indication information is used to indicate the deletion of the authentication and contract information of the terminal device.

[0028] In this embodiment, when the first network device receives the identification information of the terminal device and the identification information of the fourth access network device (different from the identification information of the first access network device), it indicates that the terminal device has left the first access network device. In order to ensure the security of the authentication and contract information of the terminal device, the first network device instructs the second network device to delete the authentication and contract information of the terminal device stored by the second network device through the first indication information.

[0029] In one possible implementation, the second network device is a local core network device, and the authentication contract information of the terminal device includes the authentication contract information used by the terminal device in the local core network device; and / or, the second network device is a local MC system, and the authentication contract information of the terminal device includes the authentication contract information used by the terminal device in the local MC system.

[0030] In one possible implementation, the first network device is a business operation support system (BOSS). The authentication and subscription information of the terminal device in the first network device is generated by the first network device or manually configured. In addition, the first network device receives the manually configured identification information of the terminal device and the identification information of the first access network device.

[0031] In one possible implementation, the first network device is a network device that provides services to terminal devices accessing the first access network device when the backhaul link is not interrupted. For example, the first network device is a macro core network device, and / or the first network device is a macro MC system.

[0032] The first network device obtains the authentication and contract information of the terminal device from the telecommunications business and operation support system (BOSS). In addition, the first network device receives the identification information of the terminal device and the identification information of the first access network device from the terminal device through the first access network device.

[0033] In a second aspect, the present application provides an information synchronization method, which can be executed by a terminal device or by a component of the terminal device (for example, a processor, a chip, or a chip system). Taking the terminal device as an example, the terminal device sends the identification information of the terminal device and the identification information of the first access network device to the first network device through the first access network device. The identification information of the terminal device and the identification information of the first access network device are used by the first network device to determine the second network device based on the identification information of the first access network device, and synchronize the authentication and contract information of the terminal device to the second network device. The second network device is a local network device that provides services to the terminal device accessing the first access network device when the backhaul link is interrupted; the terminal device receives the second indication information from the first access network device, and the second indication information is used to indicate that the backhaul link of the first access network device is interrupted; the terminal device performs authentication and obtains communication services on the second network device.

[0034] In this embodiment, the terminal device can report the identification information of the terminal device and the identification information of the first access network device to the first network device, so that the first network device synchronizes the authentication and contract information of the terminal device to the second network device, and then the terminal device can trigger the authentication and certification on the second network device after receiving the second indication information. Since the terminal device reports the identification information of the terminal device and the identification information of the first access network device to the first network device, it only triggers the first network device to synchronize the authentication and contract information of the terminal device to the second network device instead of synchronizing the authentication and contract information of all terminal devices, thereby realizing on-demand synchronization of the authentication and contract information of the terminal device. This is not only beneficial to saving the storage space of the local network device (i.e., the second network device) and reducing the storage performance requirements of the local network device, but also beneficial to reducing the risk of the authentication and contract information of the terminal device being leaked during the synchronization process, and improving the security of the authentication and contract information of the stored terminal device.

[0035] In one possible implementation, the terminal device is a terminal device that has been authenticated on the first network device. For example, when the terminal device accesses the first access network device, the terminal device applies for authentication on the first network device, so that the terminal device can report identification information of the terminal device and identification information of the first access network device to the first network device through the first access network device.

[0036] In a possible implementation, before the terminal device sends the identification information of the terminal device and the identification information of the first access network device to the first network device through the first access network device, the method also includes: the terminal device receives a system broadcast message of the first access network device, and the system broadcast message includes the identification information of the first access network device.

[0037] It should be noted that the specific implementation methods and beneficial effects of this aspect are similar to some implementation methods in the first aspect above. Please refer to the specific implementation methods and beneficial effects of the first aspect for details, and no further details will be given here.

[0038] In a third aspect, the present application provides an information synchronization method, which can be executed by a second network device or by a component of the second network device (e.g., a processor, a chip, or a chip system). Taking the second network device as an example, the second network device receives authentication and contract information of a terminal device, where the terminal device is a terminal device that has been connected to or is about to be connected to a first access network device, and the second network device is a local network device that provides services to the terminal device connected to the first access network device when the backhaul link is interrupted; the second network device performs authentication and certification on the terminal device that applies for authentication and certification based on the authentication and contract information of the terminal device.

[0039] In this embodiment, the second network device only receives authentication and contract information from terminal devices that have connected to or are about to connect to the first access network device, and does not receive authentication and contract information from terminal devices connected to other access network devices. Therefore, this not only helps save storage space on the local network device (i.e., the second network device) and reduces the storage performance requirements of the local network device, but also helps reduce the risk of terminal device authentication and contract information being leaked during the synchronization process, thereby improving the security of the stored terminal device authentication and contract information.

[0040] In one possible implementation, the second network device receives the authentication and contract information of the terminal device, including: the second network device receives the authentication and contract information of the terminal device from the first network device, and the first network device is a network device that provides services to the terminal device accessing the first access network device when the return link is not interrupted.

[0041] In one possible implementation, the second network device receives the authentication and contract information of the terminal device, including: the second network device receives a first message from the first network device, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and contract information of the terminal device.

[0042] In one possible implementation, the second network device receives the authentication and signing information of the terminal device, including: the second network device receives the authentication and signing information of the terminal device sent by the first network device from the third network device through the connection path between the first access network device and the second access network device, the first network device is a network device that provides services for the terminal device accessing the first access network device when the backhaul link is not interrupted, and the third network device is a local network device that provides services for the terminal device accessing the second access network device when the backhaul link is interrupted.

[0043] In one possible implementation, the second network device receives the authentication and signing information of the terminal device, including: the second network device receives a third message from a third network device, the destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and signing information of the terminal device.

[0044] In a possible implementation, the method further includes: the second network device receives first indication information, the first indication information is used to indicate deletion of authentication and contract information of the terminal device; and the second network device deletes the authentication and contract information of the terminal device.

[0045] In a possible implementation manner, the second network device is a local core network device deployed near the first access network device, and / or the second network device is a local MC system deployed near the first access network device.

[0046] It should be noted that the specific implementation methods and beneficial effects of this aspect are similar to some implementation methods in the first aspect above. Please refer to the specific implementation methods and beneficial effects of the first aspect for details, and no further details will be given here.

[0047] In a fourth aspect, embodiments of the present application provide a communications device, which may be a core network device in the aforementioned embodiments, or a chip within the core network device. The core network device may be a macro core network device deployed in a core network computer room, such as a first network device; or a local core network device deployed near an access network device, such as a second network device, a third network device, or a fourth network device. The communications device may include a processing module and a transceiver module. When the communications device is a core network device, the processing module may be a processor, and the transceiver module may be a transceiver. The core network device may also include a storage module, such as a memory; the storage module is configured to store instructions, and the processing module executes the instructions stored in the storage module to cause the macro core network device (e.g., the first network device) to perform the method in the first aspect or any one of the embodiments of the first aspect; or to cause the local core network device (e.g., the second network device) to perform the method in the third aspect or any one of the embodiments of the third aspect. When the communication device is a chip within a core network device, the processing module may be a processor, and the transceiver module may be an input / output interface, a pin, or a circuit, etc.; the processing module executes instructions stored in the storage module to cause the macro core network device (e.g., the first network device) to perform the method of the first aspect or any one of the embodiments of the first aspect; or to cause the local core network device (e.g., the second network device) to perform the method of the third aspect or any one of the embodiments of the third aspect. The storage module may be a storage module within the chip (e.g., a register, a cache, etc.), or a storage module within the core network device located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0048] In a fifth aspect, an embodiment of the present application provides a communication device, which may be a terminal device in the aforementioned embodiment, or a chip within the terminal device. The communication device may include a processing module and a transceiver module. When the communication device is a terminal device, the processing module may be a processor, and the transceiver module may be a transceiver; the terminal device may also include a storage module, which may be a memory; the storage module is used to store instructions, and the processing module executes the instructions stored in the storage module to cause the terminal device to perform the method in the second aspect or any one of the embodiments of the second aspect. When the communication device is a chip within the terminal device, the processing module may be a processor, and the transceiver module may be an input / output interface, pin, or circuit, etc.; the processing module executes the instructions stored in the storage module to cause the terminal device to perform the method in the second aspect or any one of the embodiments of the second aspect. The storage module may be a storage module within the chip (e.g., a register, cache, etc.), or a storage module within the terminal device located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0049] In the sixth aspect, an embodiment of the present application provides a communication device, which may be the MC system (also referred to as MC device) in the aforementioned embodiment, or a chip within the MC system. The MC system may be a macro MC system deployed in a core network room, for example, a first network device; the MC system may also be a local MC system deployed near an access network device, for example, a second network device, a third network device, and a fourth network device. The communication device may include a processing module and a transceiver module. When the communication device is an MC system, the processing module may be a processor, and the transceiver module may be a transceiver; the MC system may also include a storage module, which may be a memory; the storage module is used to store instructions, and the processing module executes the instructions stored in the storage module, so that the macro MC system (for example, the first network device) executes the method in the first aspect or any one of the embodiments of the first aspect; or, so that the local MC system (for example, the second network device) executes the method in the third aspect or any one of the embodiments of the third aspect. When the communication device is a chip within an MC system, the processing module may be a processor, and the transceiver module may be an input / output interface, pin, or circuit. The processing module executes instructions stored in the storage module to cause the macro MC system (e.g., the first network device) to execute the method of the first aspect or any one of the embodiments of the first aspect; or to cause the local MC system (e.g., the second network device) to execute the method of the third aspect or any one of the embodiments of the third aspect. The storage module may be a storage module within the chip (e.g., a register, a cache, etc.) or a storage module within the MC system located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0050] In a seventh aspect, an embodiment of the present application provides a server, which can be the BOSS in the aforementioned embodiment (i.e., an embodiment of the first network device), or a chip within the BOSS. The server may include a processing module and a transceiver module. When the server is a BOSS, the processing module may be a processor, and the transceiver module may be a transceiver; the BOSS may also include a storage module, which may be a memory; the storage module is used to store instructions, and the processing module executes the instructions stored in the storage module to cause the BOSS to perform the method in the third aspect or any of the embodiments of the third aspect. When the server is a chip within the BOSS, the processing module may be a processor, and the transceiver module may be an input / output interface, pin, or circuit, etc.; the processing module executes the instructions stored in the storage module to cause the BOSS to perform the method in the third aspect or any of the embodiments of the third aspect. The storage module may be a storage module within the chip (e.g., a register, cache, etc.), or a storage module within the BOSS located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0051] In an eighth aspect, the present application provides a communication device, which may be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled to a memory, which is configured to store programs or instructions. When the program or instructions are executed by the processor, the communication device performs the method described in any of the embodiments of the aforementioned aspects.

[0052] In a ninth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method as described in any one of the aforementioned aspects.

[0053] In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium comprising instructions, which, when executed on a computer, enable the computer to execute a method as described in any one of the embodiments in the foregoing aspects.

[0054] In the eleventh aspect, an embodiment of the present application provides a communication system, which includes a first network device that executes the aforementioned first aspect and any one of the embodiments of the first aspect, a terminal device that executes the aforementioned second aspect and any one of the embodiments of the second aspect, and a second network device that executes the aforementioned third aspect and any one of the embodiments of the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] FIG1 is a schematic diagram of a network architecture of a communication system in an IOPS scenario;

[0056] FIG2 is a flow chart of the information synchronization method of the present application;

[0057] FIG3 is another flow chart of the information synchronization method of the present application;

[0058] FIG4A is an example diagram of an application scenario of the information synchronization method of the present application;

[0059] FIG4B is another example diagram of an application scenario of the information synchronization method of the present application;

[0060] FIG5 is another flow chart of the information synchronization method of the present application;

[0061] FIG6 is another flow chart of the information synchronization method of the present application;

[0062] FIG7A is another example diagram of an application scenario of the information synchronization method of the present application;

[0063] FIG7B is another example diagram of an application scenario of the information synchronization method of the present application;

[0064] FIG8 is another flow chart of the information synchronization method of the present application;

[0065] FIG9 is a schematic diagram of an embodiment of a communication device provided by the present application;

[0066] FIG10 is a schematic diagram of another embodiment of a communication device provided by the present application;

[0067] FIG11 is a schematic diagram of an embodiment of a server provided by the present application;

[0068] FIG12 is a schematic diagram of an embodiment of the device provided in this application. DETAILED DESCRIPTION

[0069] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

[0070] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0071] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus.

[0072] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0073] The information synchronization method provided in this application can be applied to scenarios where backhaul communications may be interrupted. It is used to synchronize the authentication and contract information of a terminal device to the local network device corresponding to the access network device that the terminal device may access before the backhaul communications are interrupted, so that after the backhaul communications are interrupted, the terminal device can still authenticate and obtain communication services on the local network device. As shown in Figure 1, the communication system in this scenario mainly includes the following network elements:

[0074] Terminal device: refers to a device that provides voice and / or data connectivity to users in a communication system. The terminal device can communicate with the core network (for example, 4G core network (i.e., evolved packet core network (EPC)) or 5G core network (5th generation core, 5GC)) via the radio access network (RAN), and can exchange voice and / or data with the RAN. Some examples of terminal devices are as follows: terminal (Terminal), user equipment (UE), wireless terminal device, mobile terminal (MT) device, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (MS), mobile station (mobile), remote station (remote station), access point (AP), remote terminal device (remote terminal), access terminal device (access terminal), etc. This application does not limit the specific implementation form of the terminal device. In addition to having the functions of a traditional terminal device, the terminal device provided in this application is also installed with an MC client and can apply for authentication in the MC system. In addition, the terminal device can also switch between macro network mode and IOPS mode based on the indication information of the access network device. For example, if the terminal device receives an indication of backhaul communication interruption during the process of accessing the access network device, the terminal device switches from macro network mode to IOPS mode; if the terminal device does not receive an indication of backhaul communication interruption during the process of accessing the access network device, the terminal device defaults to macro network mode.

[0075] Access network equipment: It can be any device with wireless transceiver functions, which can be used to be responsible for air interface related functions, such as wireless link maintenance functions, wireless resource management functions, and some mobility management functions. The access network equipment can also be configured with a baseband unit (BBU) with baseband signal processing functions. There is a communication interface (for example, an Xn interface or an X2 interface) between adjacent access network devices. Exemplarily, the access network equipment (for example, access network equipment 1, access network equipment 2, and access network equipment 3 shown in Figure 1) can be the access network equipment (radio access network, RAN) that currently provides services to the terminal device. At present, some common examples of access network equipment are: Node B (NB), evolved Node B (eNB or eNodeB), next generation node B (gNB) in 5G new radio (NR) system, node in 6G system (e.g., xNodeB), transmission reception point (TRP), radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB or home node (HNB)), etc. In addition, in a network structure such as cloud radio access network (CloudRAN) or open radio access network (ORAN), the access network equipment can be a device including a centralized unit (CU) (also known as a control unit) and / or a distributed unit (DU). This application does not limit the specific implementation form of the access network equipment. In addition to the functions of traditional access network equipment, the access network equipment provided in this application also has the function of detecting the status of the backhaul network and switching between macro network mode and IOPS mode based on whether the backhaul network is faulty. For example, when the backhaul network fails (for example, backhaul communication is interrupted), the access network equipment switches from macro network mode to IOPS mode; when the backhaul network failure is resolved, the access network equipment switches from IOPS mode to macro network mode.

[0076] Core network equipment refers to the equipment in the core network (CN) that provides service support for terminal equipment. For example, the 4G core network (i.e., evolved packet core (EPC)) or the 5G core network (5th generation core, 5GC). Taking EPC as an example, the core network equipment involved in this application mainly includes network elements such as mobility management entity (MME), home subscriber server (HSS), PDN packet data gateway (PDN GateWay, P-GW) and serving gateway (Serving GateWay, S-GW). Taking 5GC as an example, the core network equipment involved in this application mainly includes access and mobility management function (AMF) entity, authentication service function (AUSF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc. Among them, the AMF entity can be responsible for the access management and mobility management of terminal devices; the SMF entity can be responsible for session management, such as user session establishment; the UPF entity can be the functional entity of the user plane, mainly responsible for connecting to the external network.

[0077] It should be noted that the core network devices involved in this application are divided into macro core network devices (for example, the macro core network shown in Figure 1) and local core network devices (for example, local core network 1 and local core network 2 shown in Figure 1). Among them, the macro core network device refers to the core network device used by the macro network deployed in the core computer room. When the backhaul communication is not interrupted, the macro core network device provides authentication and other services to the terminal device. The macro core network device can be an LTE core network device or a 5G core network device. For example, the core network device shown in Figure 1 can be a macro EPC or a macro 5GC. In addition, the local core network device refers to a miniaturized core network device deployed near the access network device and used in IOPS mode. When the backhaul communication is interrupted, the local core network device replaces the macro core network device to provide authentication and other services to the terminal device. The local core network device can be an LTE core network device or a 5G core network device. For example, the local core network 1 and / or local core network 2 shown in Figure 1 can be a Local EPC or a Local 5GC. In addition, the local core network device can be connected to at least one access network device, that is, the local core network device can provide services to at least one access network device at the same time. For example, the local core network 2 shown in Figure 1 is connected to access network device 2 and access network device 3 at the same time.

[0078] Mission-critical (MC) systems are systems that have extremely stringent requirements for real-time, safety, and reliability and are closely related to public safety. Examples include systems in life-critical scenarios such as disaster relief, emergency medical care, rail transit, smart grids, industrial automation, automotive electronics, and medical devices, as well as other systems requiring a range of capabilities, including functional safety, information security, fault isolation and recovery, reliability, and real-time performance. MC systems include at least one functional entity, namely, a configuration management server (CMSS), a group management server (GMSS), and an identity management server (IMSS). The CMSS is used to configure non-group-managed MC service-related information for one or more MC applications, configure data on the CM client, and manage the MC service configurations supported within the MC service provider. The GMSS manages groups supported within the MC service provider and manages media policy information used by terminal devices for media processing. The IMS authenticates MC IDs and can perform identity verification by verifying user-provided credentials.

[0079] It should be noted that the MC system involved in this application is divided into a macro MC system (macro MC system) and a local MC system (Local MC system). Among them, the macro MC system is a server or device deployed in the core room for providing MC services. The macro MC system is connected to the macro core network device and is responsible for providing MC services to users (for example, terminal devices connected to the access network device). In addition, the local MC system is a server or device deployed near the access network device for providing MC services. The local MC system is connected to the local core network device, and the local core network device is connected to the access network device. MC services are provided to users (for example, terminal devices connected to the access network device) in IOPS mode. For example, the local MC system 1 and the local core network 1 in Figure 1 are deployed near the access network device 1 to provide MC services to terminal devices (for example, terminal device 1, terminal device 2, etc.) connected to the access network device 1. In addition, when the local core network device is connected to multiple access network devices, the MC system connected to the core network device can provide MC services to terminal devices connected to the aforementioned multiple access network devices. For example, the local MC system 2 and the local core network 2 in Figure 1 are deployed near the access network device 2 and the access network device 3, that is, the local core network 2 connected to the local MC system 2 is also connected to the access network device 2 and the access network device 3. The local MC system 2 is used to provide MC services for terminal devices (for example, terminal device 3, terminal device 4, terminal device 5, etc.) accessed to the access network device 2 and terminal devices (for example, terminal device 6, terminal device 7, etc.) accessed to the access network device 3.

[0080] It should be understood that the local core network device and the local MC system corresponding to the same access network device can be combined into one device. For example, the local MC system 2 and the local core network 2 shown in Figure 1 can be combined into one device, and the local MC system 1 and the local core network 1 shown in Figure 1 can be combined into one device. In addition, the local network device, the local MC system and the access network device can be combined into one device. For example, the local MC system 1, the local core network 1 and the access network device 1 shown in Figure 1 can be combined into one device. This application is not limited.

[0081] Telecommunications Business & Operation Support System (BOSS): A comprehensive business operations and management platform that integrates the Business Support System (BSS) and the Operation Support System (OSS). In this application, BOSS is used to issue authentication and contract information of terminal devices registered with BOSS to the MC system (macro MC system and / or local MC system) and core network equipment (macro core network equipment and / or local core network equipment), so that the MC system and core network equipment can authenticate the terminal device applying for authentication based on the authentication and contract information of the terminal device.

[0082] In traditional technology, before the backhaul communication is interrupted, the BOSS synchronizes the authentication and contract information of all terminal devices that have opened accounts to the macro network device (i.e., the macro core network device and the macro MC system), and then the macro network device (i.e., the macro core network device and the macro MC system) synchronizes the authentication and contract information of all terminal devices to the local network devices deployed near each access network device (i.e., the local core network device and the local MC system). Taking Figure 1 as an example, if the seven terminal devices in Figure 1 (i.e., terminal device 1 to terminal device 7) all open accounts in the BOSS, the BOSS can generate authentication and contract information for each of the seven terminal devices and synchronize the authentication and contract information of each terminal device to all deployed local network devices (i.e., the local core network device and the local MC system). Among them, the authentication and contract information of each terminal device includes the authentication and contract information used by the terminal device when registering with the core network device (referred to as the core network authentication and contract information) and the authentication and contract information used by the terminal device when registering with the MC system (referred to as the MC system authentication and contract information). BOSS synchronizes the core network authentication and contract information of the 7 terminal devices to the local core network 1 and the local core network 2, and synchronizes the MC system authentication and contract information of the 7 terminal devices to the local MC system 1 and the local MC system 2.

[0083] However, the method of storing the authentication and contract information of all terminal devices by local network devices (local core network devices and / or local MC systems) places high demands on the storage capacity of local network devices. As the number of users increases, the authentication and contract information that needs to be stored may exceed the storage limit of the local network devices. In addition, the network security level of local network devices is limited, and the process may increase the risk of leakage of the authentication and contract information of terminal devices, thereby reducing security.

[0084] In this regard, the present application provides an information synchronization method and related equipment, which adopts the method of synchronizing the authentication and contract information of some terminal devices to the local network device on demand. This not only reduces the storage capacity of the local network device used to store the authentication and contract information of the terminal device, but also reduces the risk of leakage when synchronizing the authentication and contract information of the terminal device, thereby improving the security of the authentication and contract information of the terminal device.

[0085] The main process of the information synchronization method provided by this application is introduced below in conjunction with Figure 2. As shown in Figure 2, each network element involved in the information synchronization method mainly performs the following steps:

[0086] Step 201: A first network device obtains identification information of a terminal device and identification information of a first access network device.

[0087] Among them, the identification information of the terminal device and the identification information of the first access network device are used to indicate that the terminal device has resided in the first access network device, or to indicate that the terminal device may reside in or access the first access network device in the future.

[0088] In addition, the first network device may be a macro network device (for example, a macro core network device and / or a macro MC system as shown in FIG1 ), or may be a telecommunications business operation support system BOSS. It should be understood that when the implementation of the first network device is different, the first network device obtains the identification information of the terminal device and the identification information of the first access network device in different ways. The following are introduced respectively:

[0089] In one possible implementation, the first network device is a macro network device that provides services to a terminal device accessing the first access network device when a backhaul link is not interrupted. The first network device receives identification information of the terminal device and identification information of the first access network device from the terminal device via the first access network device. In this implementation, the identification information of the terminal device and the identification information of the first access network device are used to indicate that the terminal device is resident on the first access network device.

[0090] Exemplarily, when a terminal device resides on a first access network device, the terminal device receives a system broadcast message from the first access network device, the system broadcast message including identification information of the first access network device. The terminal device parses the system broadcast message to obtain the identification information of the first access network device. The terminal device then sends the terminal device's identification information and the identification information of the first access network device to the first access network device, and the first access network device forwards the terminal device's identification information and the identification information of the first access network device to the first network device.

[0091] Optionally, the identification information of the terminal device and the identification information of the first access network device can be carried in one message and sent. For example, the terminal device sends message 1 to the first access network device, and the message 1 includes the identification information of the terminal device and the identification information of the first access network device. The message 1 is used to indicate that the terminal device resides in the cell of the first access network device. After the first access network device receives the message 1, the first access network device forwards the message 1 to the first network device. Optionally, the message 1 can be understood as an information synchronization request, which is used to trigger the first network device to synchronize the authentication and contract information of the terminal device to the local network device deployed near the first access network device.

[0092] Optionally, the terminal device is a terminal device that has already undergone authentication and verification on the first network device. For example, after the terminal device resides on the first access network device, the terminal device sends a request for authentication and verification to the first network device through the first access network device, and then responds to the first network device for authentication and verification. Only after the terminal device has successfully completed authentication and verification on the first network device can the first access network device forward the terminal device identification information and the first access network device identification information sent by the terminal device to the first network device.

[0093] In another possible implementation, the first network device is a telecommunications business operation support system (BOSS), and the first network device receives identification information of a manually configured terminal device and identification information of a first access network device. This can also be understood as a correspondence between the identification information of the manually configured terminal device received by the first network device and the identification information of the first access network device. In this implementation, the identification information of the terminal device and the identification information of the first access network device are used to indicate that the terminal device may reside on or access the first access network device in the future, or to indicate that backhaul communication with the first access network device to which the terminal device is connected has been interrupted.

[0094] In addition, the first network device will also obtain the authentication contract information of the terminal device before executing step 201. The authentication contract information of the terminal device is used for the terminal device to perform authentication and certification on the macro network device or the local network device. For example, when the macro network device stores the authentication contract information of the terminal device, and the backhaul communication of the access network device to which the terminal device accesses is not interrupted, the macro network device provides authentication and certification services to the terminal device based on the authentication contract information of the terminal device; when the local network device stores the authentication contract information of the terminal device, and the backhaul communication of the access network device to which the terminal device accesses is interrupted, the local network device provides authentication and certification services to the terminal device based on the authentication contract information of the terminal device.

[0095] The authentication and contract information of the terminal device includes the authentication and contract information used by the terminal device during authentication and certification of the core network device (referred to as core network authentication and contract information) and the authentication and contract information used by the terminal device during authentication and certification of the MC system (referred to as MC system authentication and contract information). If the first network device is a macro core network device, the first network device obtains at least the core network authentication and contract information; if the first network device is a macro MC system, the first network device obtains at least the MC system authentication and contract information; if the first network device is a BOSS, the first network device can obtain both the core network authentication and contract information and the MC system authentication and contract information.

[0096] Optionally, the authentication contract information of the terminal device includes identification information of the terminal device. Exemplarily, the core network authentication contract information includes identification information of the terminal device to indicate which terminal device the core network authentication contract information is used for to perform authentication and certification in the core network device. Exemplarily, the MC system authentication contract information includes identification information of the terminal device to indicate which terminal device the MC system authentication contract information is used for to perform authentication and certification in the MC system. Optionally, for the same terminal device, the identification information of the terminal device contained in the core network authentication contract information and the identification information of the terminal device contained in the MC system authentication contract information are different types of identification information. For example, the identification information of the terminal device contained in the core network authentication contract information may be an international mobile subscriber identity (IMSI), which can uniquely identify a terminal device; the identification information of the terminal device contained in the MC system authentication contract information is of different types. The identification information may be a mission critical user identity (MC ID), which can uniquely identify an MC client (MC client), and further uniquely identify a terminal device on which the MC client is installed.

[0097] It should be understood that the core network authentication contract information and the MC system authentication contract information are different information. For further introduction to the authentication contract information of the terminal device, please refer to the relevant introduction in step 301 of the embodiment corresponding to Figure 3, which will not be repeated here.

[0098] It should be understood that when the implementation method of the first network device is different, the method in which the first network device obtains the authentication contract information of the terminal device is also different. The following are introduced respectively:

[0099] In one possible implementation, the first network device is a macro network device that provides services to terminal devices accessing the first access network device when the backhaul link is not interrupted, and the first network device obtains the authentication and contract information of the terminal device from the BOSS. For example, after the terminal device opens an account with the BOSS, the BOSS synchronizes the authentication and contract information of at least one terminal device that has opened an account to the first network device (i.e., the macro core network device and the macro MC system). Specifically, if the first network device is a macro core network device, the macro core network device obtains the core network authentication and contract information of the terminal device from the BOSS; and / or, if the first network device is a macro MC system, the macro MC system obtains the MC system authentication and contract information of the terminal device from the BOSS.

[0100] In another possible implementation, the first network device is a BOSS, and the first network device generates authentication and contract information (including core network authentication and contract information and MC system authentication and contract information) for the terminal device. For example, when the terminal device is opening an account with the BOSS, the BOSS can generate the core network authentication and contract information and the MC system authentication and contract information for the terminal device.

[0101] In another possible implementation, the first network device is a macro network device (i.e., a macro core network device and a macro MC system) or a BOSS, and the first network device receives the authentication and contract information of the manually configured terminal device (including core network authentication and contract information and MC system authentication and contract information).

[0102] Step 202: The first network device determines the second network device based on the identification information of the first access network device.

[0103] After the first network device receives the identification information of the terminal device and the identification information of the first access network device, the first network device triggers the determination of the second network device based on the identification information of the first access network device.

[0104] Among them, the second network device is a local network device that provides services to the terminal device accessing the first access network device when the backhaul link is interrupted. That is to say, the second network device is a local network device deployed near the first access network device. When the backhaul communication between the first access network device and the macro network device (i.e., the macro core network device and the macro MC system) is interrupted, the first access network device forwards the authentication request and other related information from the terminal device to the second network device, so that the terminal device performs authentication in the second network device and obtains communication services. Optionally, the second network device is a local core network device configured near the first access network device, and / or the second network device is a local MC system configured near the first access network device. Exemplarily, taking Figure 1 as an example, if the terminal device is terminal device 1, the first access network device is access network device 1, and the second network device is local core network 1 and / or local MC system 1; if the terminal device is terminal device 3, the first access network device is access network device 2, and the second network device is local core network 2 and / or local MC system 2.

[0105] In one possible implementation, the first network device stores a first correspondence relationship, the first correspondence relationship being used to indicate a correspondence relationship between the first access network device and the second network device. The first network device determines the second network device corresponding to the first access network device based on the identification information of the first access network device and the first correspondence relationship.

[0106] Exemplarily, the first correspondence includes a first correspondence 1 and / or a first correspondence 2. The first correspondence 1 is used to indicate the correspondence between the first access network device and the local core network device deployed near the first access network device, and the first correspondence 2 is used to indicate the correspondence between the first access network device and the local MC system deployed near the first access network device.

[0107] Optionally, the first correspondence includes a correspondence between the identification information of the first access network device and the address information of the second network device; or, the first correspondence includes a correspondence between the identification information of the first access network device and the identification information of the second network device. Exemplarily, the address information of the second network device may be the IP address of the second network device, etc. For example, the address information of the second network device may include the IP address of a local core network device deployed near the first access network device, and / or the IP address of a local MC system deployed near the first access network device.

[0108] Optionally, the first network device stores a first mapping table, which is used to maintain the correspondence between the access network device and the local network device. For example, the first mapping table is used to indicate the correspondence between the access network device and the local core network device, and / or to indicate the correspondence between the access network device and the local MC system. The first mapping table includes the aforementioned first correspondence. Optionally, the first mapping table includes a third correspondence, etc. The third correspondence will be described in 203 below and will not be repeated here.

[0109] For example, taking the first mapping table including identification information of the access network device and address information of the local network device as an example, the first mapping table may be as shown in the following Table 1-1:

[0110] Table 1-1

[0111] Taking Table 1-1 as an example, after the first network device receives the identification information of the first access network device, the first network device searches the first mapping table for the address information of the second network device corresponding to the identification information of the first access network device based on the identification information of the first access network device, indicating that the local network device deployed near the first access network device for providing services to the terminal device accessing the first access network device when the return link is interrupted is the second network device. Since the first network device maintains a correspondence between the access network device and the local network device (for example, the aforementioned first correspondence), the first network device can accurately query the second network device corresponding to the first access network device based on the identification information of the first access network device, thereby improving the accuracy of synchronizing the authentication and contract information of the terminal device from the first network device to the second network device.

[0112] In step 203, the first network device sends the authentication and contract information of the terminal device to be synchronized to the second network device; correspondingly, the second network device receives the authentication and contract information of the terminal device.

[0113] Specifically, the first network device will determine whether to synchronize the authentication and contract information of the terminal device to the second network device directly or indirectly based on the connectivity status between the first network device and the second network device.

[0114] In a possible implementation, the first network device directly sends the authentication subscription information of the terminal device to the second network device.

[0115] Specifically, if the first network device determines that the connection path between the first network device and the second network device is not interrupted, the first network device sends the authentication contract information of the terminal device to the second network device.

[0116] Optionally, the first network device encapsulates the address information of the second network device in a message header, and encapsulates the authentication and contract information of the terminal device in the payload of the message, so that after the first network device sends the message, the message can be transmitted to the second network device. For example, the first network device sends a first message, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and contract information of the terminal device. Optionally, the aforementioned message can be an IP message, which is not limited in this application. Synchronizing the authentication and contract information of the terminal device through the connection path between the first network device and the second network device is conducive to ensuring the efficiency of synchronizing the authentication and contract information.

[0117] In one example, if the first network device is a macro core network device, the second network device is a local core network device deployed near the first access network device, and the macro core network device sends the core network authentication and contract information of the terminal device through the interface between the macro core network device and the local core network device; if the first network device is a macro MC system, the second network device is a local MC system deployed near the first access network device, and the macro MC system sends the MC system authentication and contract information of the terminal device through the interface between the macro MC system and the local MC system. For details, please refer to the relevant description in the embodiment corresponding to Figure 3 below, which will not be repeated here.

[0118] In another example, if the first network device is a BOSS, and the second network device is a local core network device deployed near the first access network device and a local MC system deployed near the first access network device, the BOSS sends the core network authentication contract information of the terminal device and the MC system authentication contract information of the terminal device to the local core network device deployed near the first access network device and the local MC system deployed near the first access network device, respectively. For details, please refer to the relevant description in the embodiment corresponding to Figure 5 below, which will not be repeated here.

[0119] In another example, if the first network device is a BOSS, and the second network device is a local core network device deployed near the first access network device and the present MC system deployed near the first access network device, the BOSS sends the core network authentication contract information of the terminal device and the MC system authentication contract information of the terminal device to the local MC system deployed near the first access network device, and the local MC system deployed near the first access network device synchronizes the core network authentication contract information with the core network device deployed near the first access network device; or, the BOSS sends the core network authentication contract information of the terminal device and the MC system authentication contract information of the terminal device to the local core network device deployed near the first access network device, and the local core network device deployed near the first access network device synchronizes the MC system authentication contract information with the MC system deployed near the first access network device. Specifically, please refer to the relevant introduction in the corresponding embodiment of Figure 5 below, which will not be repeated here.

[0120] In another possible implementation, the first network device indirectly sends the authentication and subscription information of the terminal device to the second network device, that is, the first network device forwards the authentication and subscription information of the terminal device to the second network device through other devices or network elements.

[0121] Specifically, if the first network device determines that the connection path between the first network device and the second network device is interrupted, the first network device sends the authentication and contract information of the terminal device to the second network device through the third network device. The third network device is a local network device that provides services for the terminal device accessing the second access network device when the backhaul link is interrupted, and there is a connection path between the first access network device and the second access network device. That is to say, although the connection path between the first network device and the second network device is interrupted, the connection path between the first network device and the third network device is not interrupted, and there is a connection between the first access network device corresponding to the second network device and the second access network device corresponding to the third network device. Therefore, the first network device sends the authentication and contract information of the terminal device to the third network device, and the third network device forwards the authentication and contract information of the terminal device to the second network device through the connection path between the first access network device and the second access network device.

[0122] Specifically, before the first network device forwards the authentication and subscription information of the terminal device to the second network device via the third network device, the first network device determines the second access network device and the third network device corresponding to the second access network device based on the identification information of the first access network device. For example, the first access network device determines the second access network device connected to the first access network device based on the identification information of the first access network device, and then determines that the local network device corresponding to the second access network device is the third network device.

[0123] In one possible implementation, the first network device stores a second correspondence, which indicates a correspondence between the first access network device and a second access network device, where the second access network device is an access network device connected to the first access network device. Furthermore, the first network device stores a third correspondence, which indicates a correspondence between the second access network device and a third network device. The first network device determines the second access network device based on the identification information of the first access network device and the second correspondence; the first access network device determines the third network device corresponding to the second access network device based on the identification information of the second access network device and the third correspondence.

[0124] It should be understood that the connection path between the first network device and the second network device is interrupted, but the connection path between the first network device and the third network device is not interrupted, and a connection exists between the first access network device corresponding to the second network device and the second access network device corresponding to the third network device. Therefore, the first network device sends the authentication and contract information of the terminal device to the third network device, and the third network device forwards the authentication and contract information of the terminal device to the second network device via the connection path between the first access network device and the second access network device. This helps to improve the reliability of the synchronization of the authentication and contract information from the first network device to the second network device.

[0125] Optionally, the second correspondence includes a correspondence between identification information of the first access network device and identification information of the second access network device. Optionally, the first network device stores a second mapping table, which is used to maintain correspondence between the access network device and adjacent access network devices. It can also be understood that the second mapping table is used to maintain correspondence between access network devices that have a connection path. The second mapping table includes the aforementioned second correspondence.

[0126] For example, taking the second mapping table including identification information of the access network device as an example, the second mapping table may be as shown in the following Table 2-1:

[0127] Table 2-1

[0128] It should be understood that there may be more than one access network device adjacent to the first access network device. This application only introduces the access network device adjacent to the first access network device as the second access network device as an example.

[0129] Optionally, the third correspondence includes a third correspondence 1 and / or a third correspondence 2. The third correspondence 1 is used to indicate the correspondence between the second access network device and the local core network device deployed near the second access network device, and the third correspondence 2 is used to indicate the correspondence between the second access network device and the local MC system deployed near the second access network device.

[0130] Optionally, the third correspondence includes a correspondence between the identification information of the second access network device and the address information of the third network device; or, the third correspondence includes a correspondence between the identification information of the second access network device and the identification information of the third network device. Exemplarily, the address information of the third network device may be the IP address of the third network device, etc. For example, the address information of the third network device includes the IP address of a local core network device deployed near the second access network device, and / or the IP address of a local MC system deployed near the second access network device. Since the first network device not only maintains the correspondence between the access network device and the local network device (e.g., the first correspondence and the third correspondence), but also maintains the correspondence between the access network device and the adjacent access network device (or the connected access network device) (e.g., the second correspondence), the first network device searches for the second access network device connected to the first access network device based on the identification information of the first access network device and the second correspondence, and then searches for the third network device deployed near the second access network device based on the identification information of the second access network device and the third correspondence. Maintaining the aforementioned corresponding relationship is beneficial for improving the path for the first network device to search for and forward the authentication and contract information of the terminal device, and improving the efficiency of the first network device in synchronizing the authentication and contract information of the terminal device.

[0131] Optionally, the first mapping table stored in the first network device includes, in addition to the aforementioned first correspondence, the aforementioned third correspondence. For example, taking the example of the first mapping table including the identification information of the access network device and the address information of the local network device, when the first mapping table includes the first correspondence and the third correspondence, the first mapping table may be as shown in Table 1-2 below:

[0132] Table 1-2

[0133] Taking Table 2-1 and Table 1-2 as examples, after the first network device determines the identification information of the second access network device based on the identification information of the first access network device and the second mapping table, the first network device searches the first mapping table for the address information of a third network device corresponding to the identification information of the second access network device based on the identification information of the second access network device. This indicates that the local network device deployed near the second access network device and used to provide services to terminal devices accessing the second access network device when the backhaul link is interrupted is the third network device. The first network device then sends the authentication and subscription information of the terminal device to the second network device via the third network device.

[0134] Optionally, the first network device encapsulates the address information of the third network device in a message header, and encapsulates the authentication contract information of the terminal device and the address information of the second network device in the payload of the message, so that after the first network device sends the message, the message can be transmitted to the third network device. Then, the third network device generates another message, the message header of which includes the address information of the second network device, and the payload of which includes the authentication contract information of the terminal device, so that after the third network device sends the message, the message can be transmitted to the second network device. Optionally, the aforementioned message can be an IP message, which is not limited by this application. Since, by carrying the address information of the second network device and the authentication contract information of the terminal device in the payload of the second message, it is indicated that the final recipient of the authentication contract information of the terminal device is the second network device rather than other network devices, it is beneficial for the network device (for example, the third network device) that receives the second message to forward the authentication contract information of the terminal device to the second network device.

[0135] In step 204, the second network device performs authentication on the terminal device that applies for authentication based on the authentication contract information of the terminal device.

[0136] In this embodiment, step 204 is an optional step.

[0137] After the second network device receives the authentication and contract information of the terminal device, when the backhaul communication of the first access network device is interrupted, the first access network device broadcasts the second indication information in the system message, and the second indication information is used to indicate that the backhaul communication of the first access network device is interrupted. After the terminal device receives the second indication information, the terminal device enters the IOPS mode and uses the access type corresponding to the IOPS mode (for example, the access type is 11-15) to access the first access network device. After the first access network device receives the authentication and certification request from the terminal device, the first access network device forwards the authentication and certification to the second network device, and the second network device performs authentication and certification on the terminal device that applies for authentication and certification based on the authentication and contract information of the terminal device.

[0138] For example, if the second network device is a local core network device, the second network device can authenticate the terminal device based on the core network authentication contract information of the terminal device, and then provide core network-related services; if the second network device is a local MC system, the second network device can authenticate the terminal device based on the MC system authentication contract information of the terminal device, and then provide MC business-related services.

[0139] Step 205: The first network device sends first indication information.

[0140] In this embodiment, step 205 is an optional step.

[0141] In one possible implementation, when the terminal device leaves the first access network device or the terminal device resides in a new access network device (for example, a fourth access network device), the first network device directly or indirectly sends a first indication message to the second network device, where the first indication message is used to indicate the deletion of the authentication and subscription information of the terminal device. For example, the first network device obtains the identification information of the terminal device and the identification information of the fourth access network device, and the fourth access network device is different from the first access network device, that is, the identification information of the fourth access network device is different from the identification information of the first access network device. The first network device determines that the terminal device has left the first access network device and accessed the fourth access network device based on the identification information of the fourth access network device and the identification information of the terminal device, and then the first network device directly or indirectly sends the first indication message to the second network device. In one example, if the connection path between the first network device and the second network device is not interrupted, the first network device directly sends the first indication message to the second network device. In another example, if the connection path between the first network device and the second network device is interrupted, the first network device forwards the authentication and subscription information of the terminal device to the second network device through other devices or network elements. For example, the first network device sends the first indication information to the second network device via the third network device. For an introduction to the third network device, please refer to the relevant introduction in step 203 above, which will not be repeated here.

[0142] In this embodiment, if the local network device corresponding to the access network device to which the terminal device has historically accessed (i.e., the fourth network device corresponding to the third access network device) stores the terminal device's authentication and contract information, the first network device stores the identification information of the third access network device and the address information of the fourth network device. When the first network device receives the terminal device's identification information and the identification information of the first access network device, indicating that the terminal device has left the second access network device, the first network device instructs the fourth network device, via first instruction information, to delete the terminal device's authentication and contract information stored by the fourth network device to ensure the security of the terminal device's authentication and contract information.

[0143] In one possible implementation, if the terminal device has accessed other access network devices (for example, a third access network device) before accessing the first access network device, and the first network device has also synchronized the authentication and contract information of the terminal device to the local network device corresponding to the third access network device (for example, the fourth network device, which is a local network device that provides services to the terminal device accessing the third access network device when the return link is interrupted), then after the first network device synchronizes the authentication and contract information of the terminal device to the second network device, the first network device will also send a first indication information to the fourth network device, so that the fourth network device deletes the authentication and contract information of the terminal device.

[0144] In this embodiment, when the first network device receives the identification information of the terminal device and the identification information of the fourth access network device (different from the identification information of the first access network device), it indicates that the terminal device has left the first access network device. In order to ensure the security of the authentication and contract information of the terminal device, the first network device instructs the second network device to delete the authentication and contract information of the terminal device stored by the second network device through the first indication information.

[0145] Step 206: The second network device deletes the authentication and contract information of the terminal device.

[0146] In this embodiment, step 206 is an optional step. When the first network device executes step 205 and the second network device receives the authentication and signing information of the terminal device, the second network device executes step 206.

[0147] In a possible implementation, the first indication information includes identification information of the terminal device, and the second network device determines which terminal device's authentication and subscription information is to be deleted based on the identification information of the terminal device.

[0148] In another possible implementation, the first indication information and the terminal device's identification information are carried in a single message. For example, if a second network device receives message 2, which includes the terminal device's identification information and the first indication information, the second network device determines which terminal device's authentication and contract information to delete based on the terminal device's identification information in message 2.

[0149] In the present application, the first network device can obtain the identification information of the terminal device and the identification information of the first access network device, and determine the second network device (i.e., the local network device that provides services for the terminal device accessing the first access network device when the backhaul link is interrupted) based on the identification information of the first access network device, and then send the authentication and contract information of the terminal device to the second network device, so that when the terminal device resides on the first access network device, the second network device can use the authentication and contract information of the terminal device for the terminal device to authenticate and authenticate, and then provide communication services for the terminal device. Since the first network device only synchronizes the authentication and contract information of the terminal device that may reside on the first access network device to the second network device, rather than synchronizing the authentication and contract information of all terminal devices, it is beneficial to save the storage space of the local network device (i.e., the second network device) and reduce the storage performance requirements of the local network device. In addition, since only the authentication and contract information of some terminal devices is synchronized to the second network device, and the authentication and contract information of the remaining terminal devices is still stored in the first network device, it is beneficial to reduce the risk of the authentication and contract information of the terminal device being leaked during the synchronization process and improve the security of the authentication and contract information of the stored terminal device.

[0150] 3 and 5 , the following further introduces the situation in which the first network device can directly send the authentication and signing information of the terminal device to the second network device in the information synchronization method provided by the present application.

[0151] As shown in Figures 3 and 4A, each mapping table is maintained in a macro network device. The macro network device is an example of the aforementioned first network device, access network device 1 is an example of the aforementioned first access network device, local network device 1 is an example of the aforementioned second network device, access network device 2 is an example of a third access network device that the terminal device has historically accessed, local network device 2 is an example of a fourth network device corresponding to the third access network device, and terminal device 1 is an example of the aforementioned terminal device. In this embodiment, each network element mainly performs the following steps:

[0152] In step 301 , the BOSS sends the authentication and contract information of the terminal device 1 to the macro network device; correspondingly, the macro network device receives the authentication and contract information of the terminal device 1 from the BOSS.

[0153] After the terminal device 1 opens an account in the BOSS, the BOSS can obtain the authentication and contract information of the terminal device 1. The authentication and contract information of the terminal device 1 in the BOSS can be generated by the BOSS or manually configured, which is not limited in this embodiment.

[0154] Among them, the authentication and contract information of the terminal device 1 includes the core network authentication and contract information of the terminal device 1 and the MC system authentication and contract information of the terminal device 1.

[0155] Exemplarily, when the macro network device is a macro core network device, the BOSS sends the core network authentication and subscription information of the terminal device 1 to the macro core network device. Optionally, the core network authentication and subscription information of the terminal device 1 includes core network authentication information and core network subscription information.

[0156] Among them, the core network authentication information includes: international mobile subscriber identity (IMSI), individual subscriber authentication key (KI), operator variant algorithm configuration field (OP) and other information. The core network subscription information includes: access point name (APN), QoS class identifier (QCI), user equipment-aggregate maximum bit rate (UE-AMBR) and allocation and retention priority (ARP) and other information. Among them, IMSI can uniquely identify a terminal device, that is, IMSI is the identification information of terminal device 1.

[0157] Exemplarily, when the macro network device is a macro MC system, the BOSS sends the MC system authentication and contract information of the terminal device 1 to the macro MC system. Optionally, the MC system authentication and contract information of the terminal device 1 includes MC system authentication information and MC system contract information.

[0158] Among them, the MC system authentication information includes: Mission Critical user identity (MC ID), Mission Critical user password (Mission Critical user password), Internet Protocol multimedia private identity (IMPI) and IP multimedia public identity (IMPU) and other information. The MC system subscription information includes: Group ID, user priority, emergency call number, emergency call type and user-supported service capabilities (for example, whether the user supports point call, group call, video call, short message service, etc.) and other information. Among them, MC ID can uniquely identify an MC client (MC client). Since the terminal device 1 is installed with the MC client, the MC ID can also be used as the identification information of the terminal device 1.

[0159] It should be understood that the BOSS may send only the authentication and contract information of terminal device 1 to the macro network device, or may send the authentication and contract information of multiple terminal devices to the macro network device, where the authentication and contract information of the multiple terminal devices includes the authentication and contract information of terminal device 1. Since the authentication and contract information of terminal device 1 includes the identification information of terminal device 1 (for example, IMSI and MC ID), the macro network device can find the authentication and contract information of terminal device 1 from the received authentication and contract information of multiple terminal devices.

[0160] Step 302: Access network device 1 sends a system broadcast message; correspondingly, terminal device 1 receives the system broadcast message.

[0161] When the terminal device resides on the access network device 1, the terminal device 1 receives a system broadcast message from the access network device 1, which includes identification information of the access network device 1. The terminal device 1 parses the system broadcast message to obtain the identification information of the access network device 1.

[0162] Exemplarily, the system broadcast message may be a system information block (SIB1) message, and the identification information of the access network device 1 may be an E-UTRAN cell global identifier (ECGI), which includes a public land mobile network identity (PLMN Identity), a base station identifier (e.g., eNB ID), and a cell identifier (e.g., Cell ID).

[0163] Step 303: Terminal device 1 performs authentication on the macro network device.

[0164] Exemplarily, when the macro network device is a macro core network device, the terminal device 1 performs authentication on the macro core network device, that is, the macro core network device performs authentication on the terminal device 1 based on the core network authentication contract information of the terminal device 1.

[0165] Exemplarily, when the macro network device is a macro MC system, the terminal device 1 performs authentication in the macro MC system, that is, the macro MC system performs authentication on the terminal device 1 based on the MC system authentication contract information of the terminal device 1.

[0166] Step 304 , terminal device 1 sends identification information of terminal device 1 and identification information of access network device 1 to the macro network device; correspondingly, the macro network device receives the identification information of terminal device 1 and identification information of access network device 1 from terminal device 1 .

[0167] Among them, for specific examples of the identification information of the access network device 1 and the identification information of the terminal device 1, please refer to the relevant introduction in the above steps 301 and 302, which will not be repeated here.

[0168] Specifically, terminal device 1 sends identification information of terminal device 1 and identification information of access network device 1 to the macro network device through access network device 1. For example, terminal device 1 sends message 1 to access network device 1, and access network device 1 sends message 1 to the macro network device, where message 1 includes identification information of terminal device 1 and identification information of access network device 1. The identification information of terminal device 1 and identification information of access network device 1 are used by the macro network device to determine local network device 1 corresponding to access network device 1 based on the identification information of access network device 1.

[0169] Exemplarily, when the macro network device is a macro core network device, the terminal device 1 sends a tracking area update (TAU) message to the macro core network device, and the TAU message includes the identification information of the terminal device 1 and the identification information of the access network device 1; accordingly, the macro core network device obtains the identification information of the terminal device 1 and the identification information of the access network device 1 from the received TAU message.

[0170] Exemplarily, when the macro network device is a macro MC system, the terminal device 1 sends a location information reporting message to the macro MC system, and the location information reporting message includes the identification information of the terminal device 1 and the identification information of the access network device 1; accordingly, the macro MC system obtains the identification information of the terminal device 1 and the identification information of the access network device 1 from the received location information reporting message.

[0171] Step 305 : The macro network device determines the local network device 1 based on the identification information of the access network device 1 and the mapping table 1 .

[0172] The macro network device stores a mapping table 1, which is used to maintain a correspondence between access network devices and local network devices. This mapping table 1 is used to indicate that the local network device is deployed near the access network device, so that when backhaul communication is interrupted, it replaces the macro network device in providing services to terminal devices connected to the access network device. This mapping table 1 includes the correspondence between access network device 1 and local network device 1. Exemplarily, mapping table 1 stores identification information of access network device 1 and address information of local network device 1; alternatively, mapping table 1 stores identification information of access network device 1 and identification information of local network device 1.

[0173] The local network device 1 includes a local core network device 1 and a local MC system 1. The mapping table 1 includes a correspondence between the access network device 1 and the local core network device 1, and / or a correspondence between the access network device 1 and the local MC system 1.

[0174] Exemplarily, if the macro network device is a macro core network device, the mapping table 1 stored in the macro core network device includes identification information of the access network device 1 and address information of the local core network device 1. The mapping table 1 may be as shown in Table 3-1 below:

[0175] Table 3-1

[0176] Taking Table 3-1 as an example, after the macro core network device receives the identification information of the access network device 1, the macro core network device searches for the address information of the local core network device 1 corresponding to the identification information of the access network device 1 in the mapping table 1 based on the identification information of the access network device 1, indicating that the local core network device deployed near the access network device 1 for providing services to the terminal device 1 accessing the access network device 1 when the return link is interrupted is the local core network device 1.

[0177] Exemplarily, if the macro MC system is a macro MC system, the mapping table 1 stored in the macro MC system includes identification information of the access network device 1 and address information of the local MC system 1. The mapping table 1 may be as shown in the following Table 3-2:

[0178] Table 3-2

[0179] Taking Table 3-2 as an example, after the macro MC system receives the identification information of the access network device 1, the macro MC system searches the mapping table 1 based on the identification information of the access network device 1 to find the address information of the local MC system 1 corresponding to the identification information of the access network device 1, indicating that the local MC system deployed near the access network device 1 to provide services to the terminal device 1 accessing the access network device 1 when the return link is interrupted is the local MC system 1.

[0180] Optionally, the mapping table 1 also includes identification information of other access network devices and address information of other local network devices.

[0181] For example, the mapping table 1 stored in the macro core network device also includes the identification information of the access network device 2 and the address information of the local core network device 2. Specifically, as shown in Table 3-3:

[0182] Table 3-3

[0183] For another example, the mapping table 1 stored in the macro MC system also includes the identification information of the access network device 2 and the address information of the local MC system 2. The details are shown in Table 3-4:

[0184] Table 3-4

[0185] Step 306 : The macro network device sends the authentication and signing information of the terminal device 1 to the local network device 1 .

[0186] Exemplarily, when the macro network device is a macro core network device, and local network device 1 is local core network device 1, the macro core network device sends the core network authentication and subscription information of terminal device 1 to local core network device 1. For example, the macro core network device sends message 1-1, the payload of which encapsulates the core network authentication and subscription information of terminal device 1, and the destination address field of the message header of which encapsulates the address information of local core network device 1. Local core network device 1 parses the payload of received message 1-1 to obtain the core network authentication and subscription information of terminal device 1, and stores the core network authentication and subscription information of terminal device 1 for future use by terminal device 1 when applying for authentication and certification from local core network device 1.

[0187] Exemplarily, when the macro network device is a macro MC system, the local network device 1 is a local MC system 1, and the macro MC system sends the MC system authentication and contract information of the terminal device 1 to the local MC system 1. For example, the macro MC system sends message 1-2, the payload of which encapsulates the MC system authentication and contract information of the terminal device 1, and the destination address field of the message header of which encapsulates the address information of the local MC system 1. The local MC system 1 parses the payload of the received message 1-2 to obtain the MC system authentication and contract information of the terminal device 1, and stores the MC system authentication and contract information of the terminal device 1 so that the terminal device 1 can use it in the future when applying for authentication and certification in the local MC system 1.

[0188] Step 307 : Terminal device 1 performs authentication on local network device 1 .

[0189] In this embodiment, step 307 is an optional step.

[0190] When the backhaul communication of the access network device 1 is interrupted, the access network device 1 broadcasts the second indication information (for example, IOPS PLMN) indicating that the backhaul communication of the access network device 1 is interrupted in the system message broadcast (for example, SIB1). After the terminal device 1 receives the second indication information, the terminal device 1 enters the IOPS mode and uses the access type corresponding to the IOPS mode (for example, the access type is 11-15) to access the access network device 1. Then, the terminal device 1 sends a request message for authentication in the core network device 1 and a request message for authentication in the MC system 1. After the access network device 1 receives the request message for authentication in the core network device 1 from the terminal device 1, the access network device 1 forwards the request message for authentication in the core network device 1 to the local core network device 1, and the access network device 1 forwards the request message for authentication in the MC system 1 to the local MC system 1. Then, the local core network device 1 can authenticate the terminal device 1 based on the core network authentication and contract information of the terminal device 1, and then provide core network related services; and the local MC system 1 can authenticate the terminal device 1 based on the MC system authentication and contract information of the terminal device 1, and then provide MC business-related services.

[0191] In step 308 , the macro network device stores the identification information of the terminal device 1 and the identification information of the access network device 1 in a corresponding manner in the mapping table 2 .

[0192] In this embodiment, step 308 is an optional step. There is no time sequence restriction for step 308 and steps 305 to 307, and step 308 can be performed after step 304.

[0193] The macro network device stores a mapping table 2, which is used to maintain the correspondence between the terminal device and the access network device to which the terminal device is connected. This mapping table 2 not only reflects which access network devices the terminal device has accessed, but also indirectly reflects which local network devices corresponding to the access network devices store the terminal device's authentication and contract information. Exemplarily, this mapping table 2 includes the terminal device's identification information and the access network device's identification information.

[0194] Exemplarily, after the macro network device stores the identification information of the terminal device 1 and the identification information of the access network device 1 in a corresponding manner in the mapping table 2, the mapping table 2 includes the identification information of the terminal device 1 and the identification information of the access network device 1. The mapping table 2 may be as shown in the following Table 4-1:

[0195] Table 4-1

[0196] Optionally, if the terminal device 1 has previously accessed access network device 2 before accessing access network device 1 and the macro network device has previously synchronized the authentication and contract information of the terminal device to the local network device corresponding to access network device 2, the terminal device 1 may store the identification information of the terminal device 1 and the identification information of the access network device 2 in a mapping table 2. In this case, the mapping table 2 may be as shown in Table 4-2 below:

[0197] Table 4-2

[0198] Taking Table 4-2 as an example, when the macro network device receives the identification information of the aforementioned terminal device 1 and the identification information of the access network device 1, the macro network device can determine based on the identification information of the aforementioned terminal device 1, the identification information of the access network device 1 and the mapping table 2 that the access network device 1 currently connected to the terminal device 1 and the access network device 2 that the terminal device 1 last accessed are different access network devices, thereby triggering the macro network device to store the identification information of the terminal device 1 and the identification information of the access network device 1 correspondingly in the mapping table 2, and triggering the macro network device to execute steps 309 to 312.

[0199] It should be understood that in this embodiment, steps 309 to 312 are optional steps. When the identification information of access network device 1 received by the macro network device is the same as the identification information of access network device 2, it indicates that the access network device 1 currently accessed by terminal device 1 is the same access network device as the access network device 2 that terminal device 1 last accessed. In this case, the macro network device does not execute step 308 or steps 309 to 312.

[0200] In step 309 , the macro network device determines the local network device 2 storing the authentication and contract information of the terminal device 1 based on the identification information of the terminal device 1 , the mapping table 2 , and the mapping table 1 .

[0201] Specifically, the macro network device determines that the access network device that terminal device 1 has historically accessed is access network device 2 based on the identification information of terminal device 1 and mapping table 2. Then, the macro network device determines the local network device 2 (i.e., local core network device 2 and local MC system 2) corresponding to access network device 2 based on the identification information of access network device 2 and mapping table 1. The local network device 2 stores the authentication and contract information of the terminal device. For example, the local core network device 2 stores the core network authentication and contract information of the terminal device, and the local MC system 2 stores the MC system authentication and contract information of the terminal device.

[0202] Step 310 : The macro network device sends first indication information to the local network device 2 .

[0203] Among them, the first indication information is used to indicate the deletion of the authentication and signing information of the terminal device 1 in the local network device 2.

[0204] Step 311: The local network device 2 deletes the authentication and signing information of the terminal device 1.

[0205] Exemplarily, the macro network device sends first indication information to the local core network device 2 , the local core network device 2 receives the first indication information, and deletes the core network authentication and subscription information of the terminal device 1 in response to the first indication information.

[0206] Exemplarily, the macro network device sends first indication information to the local MC system 2 , the local MC system 2 receives the first indication information, and deletes the MC system authentication and contract information of the terminal device 1 in response to the first indication information.

[0207] Step 312 : The macro network device deletes the correspondence between the terminal device 1 and the access network device 2 in the mapping table 2 .

[0208] Since mapping table 2 not only reflects which access network devices the terminal device has accessed, but also indirectly reflects which local network devices corresponding to the access network devices store the authentication and contract information of the terminal device, when the macro network device instructs local network device 2 to delete the authentication and contract information of terminal device 1, the macro network device deletes the correspondence between terminal device 1 and access network device 2 in mapping table 2.

[0209] In this embodiment, as shown in FIG4A , a mapping table (including mapping relationships between access network devices, local core network devices, and local MC systems) is configured in the macro core network device and the macro MC system, respectively. The macro core network device at least stores the corresponding relationship between the access network device and the local core network device, and the macro MC system at least stores the corresponding relationship between the access network device and the local MC system. Therefore, the macro core network device and the macro MC system can respectively determine the core network authentication contract information and the MC system authentication contract information based on their respective stored mapping tables, and then the macro core network device and the macro MC system respectively synchronize the core network authentication contract information and the MC system authentication contract information to the local core network device 1 and the local MC system 1 corresponding to the access network device 1 accessed by the terminal device 1. This is beneficial for the macro core network device and the macro MC system to simultaneously synchronize the core network authentication contract information and the MC system authentication contract information to the local core network device 1 and the local MC system 1, respectively, thereby improving the efficiency of authentication contract information synchronization.

[0210] As shown in Figures 5 and 4B, each mapping table is maintained in the BOSS. The BOSS is an example of the aforementioned first network device, access network device 1 is an example of the aforementioned first access network device, local network device 1 is an example of the aforementioned second network device, access network device 2 is an example of a third access network device that the terminal device has historically accessed, local network device 2 is an example of a fourth network device corresponding to the third access network device, and terminal device 1 is an example of the aforementioned terminal device. In this embodiment, each network element mainly performs the following steps:

[0211] In step 501 , the BOSS sends the authentication and contract information of the terminal device 1 to the macro network device; correspondingly, the macro network device receives the authentication and contract information of the terminal device 1 from the BOSS.

[0212] Step 502: Access network device 1 sends a system broadcast message; correspondingly, terminal device 1 receives the system broadcast message.

[0213] Step 503: Terminal device 1 performs authentication on the macro network device.

[0214] In this embodiment, steps 501 to 503 are similar to steps 301 to 303 in the embodiment corresponding to FIG. 3 . For details, please refer to the relevant introduction in steps 301 to 303 above.

[0215] Step 504 , the terminal device 1 sends the identification information of the terminal device 1 and the identification information of the access network device 1 to the BOSS through the macro network device; correspondingly, the BOSS receives the identification information of the terminal device 1 and the identification information of the access network device 1 from the terminal device 1 .

[0216] In one possible implementation, the macro network device is a macro MC system, and terminal device 1 sends identification information of terminal device 1 and identification information of access network device 1 to the BOSS via the macro MC system. For example, terminal device 1 sends a location information reporting message to the macro MC system, where the location information reporting message includes identification information of terminal device 1 and identification information of access network device 1. Then, the macro MC system sends the identification information of terminal device 1 and identification information of access network device 1 to the BOSS.

[0217] In one possible implementation, the macro network device is a macro core network device, and the terminal device 1 sends identification information of the terminal device 1 and identification information of the access network device 1 to the BOSS via the macro core network device. For example, the terminal device 1 sends a tracking area update (TAU) message to the macro core network device, where the TAU message includes identification information of the terminal device 1 and identification information of the access network device 1. The macro core network device then sends the identification information of the terminal device 1 and identification information of the access network device 1 to the BOSS.

[0218] Step 505 : The BOSS determines the local network device 1 based on the identification information of the access network device 1 and the mapping table 1 .

[0219] The BOSS stores a mapping table 1, which is used to maintain a correspondence between access network devices and local network devices. This mapping table 1 is used to indicate that the local network device is deployed near the access network device so that, when backhaul communication is interrupted, it replaces the macro network device in providing services to terminal devices connected to the access network device. This mapping table 1 includes the correspondence between access network device 1 and local network device 1. Exemplarily, mapping table 1 stores identification information of access network device 1 and address information of local network device 1; alternatively, mapping table 1 stores identification information of access network device 1 and identification information of local network device 1.

[0220] Among them, the local network device 1 includes a local core network device 1 and a local MC system 1. The mapping table 1 includes the correspondence between the access network device 1 and the local core network device 1, and / or the correspondence between the access network device 1 and the local MC system 1. Exemplarily, the mapping table 1 stores the identification information of the access network device 1, the address information of the local core network device 1 and the address information of the local MC system 1; or, the mapping table 1 stores the identification information of the access network device 1, the identification information of the local core network device 1 and the identification information of the local MC system 1. For a specific example of the mapping table 1, please refer to step 305 above, which will not be repeated here.

[0221] Step 506 , BOSS sends the authentication and signing information of terminal device 1 to local network device 1 .

[0222] When the connection path between the BOSS and the local network device 1 is not interrupted, the BOSS sends the authentication and signing information of the terminal device 1 to the local network device 1 through the interface between the BOSS and the local network device 1.

[0223] In one possible implementation, the BOSS sends the authentication and contract information used by each to the local core network device 1 and the local MC system 1. For example, the BOSS sends the core network authentication and contract information of the terminal device 1 to the local core network device 1; the BOSS sends the MC system authentication and contract information of the terminal device 1 to the local MC system 1.

[0224] In another possible implementation, the BOSS sends the authentication and contract information of the terminal device 1 (including the core network authentication and contract information and the MC system authentication and contract information) to one of the local network devices, and the local network device sends the authentication and contract information used by the local network device to another local network device.

[0225] In one example, the BOSS sends the core network authentication and contract information of the terminal device 1 and the MC system authentication and contract information of the terminal device 1 to the local MC system 1, and then the local MC system 1 sends the core network authentication and contract information of the terminal device 1 to the local core network device 1.

[0226] In another example, the BOSS sends the core network authentication and contract information of the terminal device 1 and the core network authentication and contract information of the terminal device 1 to the local core network device 1, and then the local core network device 1 sends the MC system authentication and contract information of the terminal device 1 to the local MC system 1.

[0227] Step 507 : Terminal device 1 performs authentication on local network device 1 .

[0228] In this embodiment, step 507 is an optional step. Step 507 is similar to step 307 above. For details, please refer to the relevant description of step 307 above, which will not be repeated here.

[0229] In step 508 , the BOSS stores the identification information of the terminal device 1 and the identification information of the access network device 1 in a corresponding manner in the mapping table 2 .

[0230] In this embodiment, step 508 is an optional step. There is no time limit for step 508 and steps 505 to 507. Step 508 can be performed after step 504.

[0231] The BOSS stores a mapping table 2, which is used to maintain the correspondence between terminal devices and the access network devices they access. This mapping table 2 not only reflects which access network devices a terminal device has accessed, but also indirectly reflects which local network devices corresponding to these access network devices store the terminal device's authentication and contract information. Exemplarily, this mapping table 2 includes both the terminal device's identification information and the access network device's identification information.

[0232] Exemplarily, after the BOSS stores the identification information of terminal device 1 and the identification information of access network device 1 in a corresponding manner in mapping table 2, mapping table 2 includes the identification information of terminal device 1 and the identification information of access network device 1. Optionally, if the terminal device 1 has previously accessed access network device 2 before accessing access network device 1, and the BOSS has previously synchronized the authentication and contract information of the terminal device to the local network device corresponding to access network device 2, the terminal device 1 may store the identification information of terminal device 1 and the identification information of access network device 2 in mapping table 2 in a corresponding manner.

[0233] For the introduction of mapping table 2, please refer to the above step 508, which will not be described in detail here.

[0234] In step 509 , the BOSS determines the local network device 2 storing the authentication and contract information of the terminal device 1 based on the identification information of the terminal device 1 , the mapping table 2 , and the mapping table 1 .

[0235] Specifically, based on the identification information of terminal device 1 and mapping table 2, the BOSS determines that the access network device that terminal device 1 has historically accessed is access network device 2. Then, based on the identification information of access network device 2 and mapping table 1, the BOSS determines the local network device 2 (i.e., local core network device 2 and local MC system 2) corresponding to access network device 2. The local network device 2 stores the authentication and contract information of the terminal device. For example, the local core network device 2 stores the core network authentication and contract information of the terminal device, and the local MC system 2 stores the MC system authentication and contract information of the terminal device.

[0236] Step 510 : The BOSS sends first instruction information to the local network device 2 .

[0237] Among them, the first indication information is used to indicate the deletion of the authentication and signing information of the terminal device 1 in the local network device 2.

[0238] Step 511: The local network device 2 deletes the authentication and signing information of the terminal device 1.

[0239] Exemplarily, the BOSS sends a first indication message to the local core network device 2 , the local core network device 2 receives the first indication message, and deletes the core network authentication and contract information of the terminal device 1 in response to the first indication message.

[0240] Exemplarily, the BOSS sends a first indication message to the local MC system 2 , the local MC system 2 receives the first indication message, and deletes the MC system authentication and signing information of the terminal device 1 in response to the first indication message.

[0241] Step 512 : The BOSS deletes the correspondence between the terminal device 1 and the access network device 2 in the mapping table 2 .

[0242] Since mapping table 2 not only reflects which access network devices the terminal device has accessed, but also indirectly reflects which local network devices corresponding to the access network devices store the authentication and contract information of the terminal device, when the BOSS instructs local network device 2 to delete the authentication and contract information of terminal device 1, the BOSS deletes the correspondence between terminal device 1 and access network device 2 in mapping table 2.

[0243] In this embodiment, as shown in FIG4B , the mapping table (including the mapping relationship between the access network device, the local core network device and the local MC system) is centrally configured in the BOSS, that is, the operation and maintenance personnel only need to maintain each mapping relationship in the BOSS, and do not need to configure each mapping relationship separately in the macro MC system and the macro core network device, that is, there is no need to configure and maintain the above mapping relationship through two configuration interfaces at the same time, which reduces the complexity of the operation and maintenance personnel in configuring and maintaining the mapping relationship. In addition, the identification information of the access network device where the terminal device is currently located is reported by the terminal to the macro MC system, and then transferred to the BOSS by the macro MC system. Then, the BOSS adds or deletes the authentication and contract information in the local MC system and the local core network device according to the mapping relationship. Since the terminal device only needs to report the identification information of the terminal device and the identification information of the access network device where it is currently located to the macro MC system, there is no need to report the identification information of the terminal device and the identification information of the access network device where it is currently located to the macro MC system and the macro core network device respectively, which can reduce the signaling overhead caused by the terminal device reporting the above information.

[0244] 6 and 8 , the following further describes the situation in which the first network device sends the authentication and signing information of the terminal device to the second network device through other devices or network elements in the information synchronization method provided by the present application.

[0245] As shown in Figures 6 and 7A, each mapping table is maintained in the BOSS. The BOSS is an example of the aforementioned first network device, access network device 1 is an example of the aforementioned first access network device, local network device 1 is an example of the aforementioned second network device, access network device 2 is an example of a third access network device that the terminal device has historically accessed, local network device 2 is an example of a fourth network device corresponding to the third access network device, access network device 3 is an example of the aforementioned second access network device, local network device 3 is an example of the aforementioned third network device, and terminal device 1 is an example of the aforementioned terminal device. In this embodiment, each network element mainly performs the following steps:

[0246] In step 601 , the BOSS receives the manually configured identification information of the terminal device 1 and the identification information of the access network device 1 , and stores the identification information of the terminal device 1 and the identification information of the access network device 1 in a mapping table 2 in correspondence.

[0247] It can also be understood that the BOSS receives the manually configured correspondence between the terminal device 1 and the access network device 1, indicating that the terminal device 1 may reside in or access the access network device 1 in the future. Specific examples of the identification information of the access network device 1 and the identification information of the terminal device 1 can be found in the description of steps 301 and 302 above, which will not be repeated here.

[0248] The BOSS stores a mapping table 2, which is used to maintain the correspondence between terminal devices and the access network devices they access. This mapping table 2 not only reflects which access network devices a terminal device has accessed, but also indirectly reflects which local network devices corresponding to these access network devices store the terminal device's authentication and contract information. Exemplarily, this mapping table 2 includes both the terminal device's identification information and the access network device's identification information.

[0249] Exemplarily, after the BOSS stores the identification information of terminal device 1 and the identification information of access network device 1 in a corresponding manner in mapping table 2, mapping table 2 includes the identification information of terminal device 1 and the identification information of access network device 1. Optionally, if the terminal device 1 has previously accessed access network device 2 before accessing access network device 1, and the BOSS has previously synchronized the authentication and contract information of the terminal device to the local network device corresponding to access network device 2, the terminal device 1 may store the identification information of terminal device 1 and the identification information of access network device 2 in mapping table 2 in a corresponding manner.

[0250] Step 602 : The BOSS determines the local network device 1 based on the identification information of the access network device 1 and the mapping table 1 .

[0251] The BOSS stores a mapping table 1, which is used to maintain a correspondence between access network devices and local network devices. The mapping table 1 is used to indicate that the local network device is deployed near the access network device so that when backhaul communication is interrupted, the local network device can replace the macro network device to provide services to terminal devices connected to the access network device. The mapping table 1 includes the correspondence between access network device 1 and local network device 1.

[0252] The local network device 1 includes a local core network device 1 and a local MC system 1. The mapping table 1 includes a correspondence between the access network device 1 and the local core network device 1, and / or a correspondence between the access network device 1 and the local MC system 1. For a specific example of the mapping table 1, please refer to step 305 above and will not be repeated here.

[0253] After the BOSS determines the local network device 1 corresponding to access network device 1, it will initiate synchronization of the authentication and contract information of terminal device 1 with local network device 1. At this point, the BOSS will first determine whether the connection between the BOSS and local network device 1 is interrupted. If so, the BOSS will forward the authentication and contract information of terminal device 1 to local network device 1 via other devices or network elements. Specifically, the BOSS will execute steps 603 to 605. If the connection between the BOSS and local network device 1 is not interrupted, the BOSS will send the authentication and contract information of the terminal device to local network device 1. Please refer to the relevant description of step 506 above for details.

[0254] Step 603 : When the BOSS determines that the connection path with the local network device 1 is interrupted, the BOSS determines the local network device 3 corresponding to the access network device 3 adjacent to the access network device 1 based on mapping table 1 and mapping table 3 .

[0255] Since there is a communication interface between the local network device 1 and the access network device 1 , the BOSS can transmit the authentication and signing information of the terminal device 1 to the local network device 1 through the device or network element having the communication interface with the access network device 1 .

[0256] Specifically, the BOSS stores a mapping table 3, which is used to maintain the correspondence between access network devices and adjacent access network devices. Alternatively, mapping table 3 can be understood as maintaining the correspondence between access network devices that have a connection path. Based on mapping table 3, the BOSS can determine which access network devices have a connection path with access network device 1.

[0257] For example, taking mapping table 3 including identification information of access network devices as an example, mapping table 3 may be as shown in the following Table 5-1:

[0258] Table 5-1

[0259] Taking Table 5-1 as an example, the BOSS can determine that the access network device connected to access network device 1 is access network device 3 based on the identification information of access network device 1 and mapping table 3.

[0260] In addition, the BOSS also stores a mapping table 1, which is used to maintain the corresponding relationship between access network devices and local network devices. This mapping table 1 is used to indicate that the local network device is deployed near the access network device so that when backhaul communication is interrupted, it can replace the macro network device to provide services to the terminal device connected to the access network device. This mapping table 1 includes the corresponding relationship between access network device 1 and local network device 1; as well as the corresponding relationship between access network device 3 and local network device 3.

[0261] The local network device 1 includes a local core network device 1 and a local MC system 1. The mapping table 1 includes a correspondence between the access network device 1 and the local core network device 1, and a correspondence between the access network device 1 and the local MC system 1. Exemplarily, the mapping table 1 includes correspondingly stored identification information of the access network device 1, address information of the local core network device 1, and address information of the local MC system 1.

[0262] The local network device 3 includes a local core network device 3 and a local MC system 3. The mapping table 1 includes a correspondence between the access network device 3 and the local core network device 3, and a correspondence between the access network device 3 and the local MC system 3. Exemplarily, the mapping table 1 includes correspondingly stored identification information of the access network device 3, address information of the local core network device 3, and address information of the local MC system 3.

[0263] For example, the mapping table 1 stored in the BOSS may be as shown in Table 3-5 below:

[0264] Table 3-5

[0265] Taking Table 3-5 as an example, the BOSS can determine the local network device 3 (ie, the local core network device 3 and the local MC system 3) corresponding to the access network device 3 based on the identification information of the access network device 3 and the mapping table 1.

[0266] It should be understood that after the BOSS determines that the connection path between the BOSS and local network device 3 is not interrupted, the BOSS sends the authentication and signing information of terminal device 1 to local network device 3. If the BOSS determines that the connection path between the BOSS and local network device 3 is also interrupted, the BOSS then queries other access network devices connected to access network device 1 and the local network device corresponding to the access network device based on mapping table 3 and mapping table 1. This is not detailed here.

[0267] Step 604 , the BOSS sends the authentication and signing information and purpose indication information of the terminal device 1 to the local network device 3 .

[0268] The destination indication information is used to indicate the final recipient of the authentication and contract information of the terminal device 1, that is, the local network device 1. Exemplarily, the destination indication information is the address information of the local network device 1 (that is, the address information of the local core network device 1 and the address information of the local MC system 1).

[0269] Exemplarily, the BOSS sends the core network authentication and contract information of the terminal device 1 and the address information of the local core network device 1 to the local core network device 3. For example, the BOSS sends a message 2-1, the payload of which encapsulates the core network authentication and contract information of the terminal device 1 and the address information of the local core network device 1, and the destination address field of the message header of the message 2-1 encapsulates the address information of the local core network device 3. The local core network device 3 parses the payload of the received message 2-1 to obtain the core network authentication and contract information of the terminal device 1 and the address information of the local core network device 1. The local core network device 3 can determine, based on the address information of the local core network device 1, that the core network authentication and contract information of the terminal device 1 needs to be forwarded to the local core network device 1. For the specific forwarding process, please refer to step 605.

[0270] Exemplarily, the BOSS sends the MC system authentication and contract information of the terminal device 1 and the address information of the local MC system 1 to the local MC system 3. For example, the BOSS sends a message 2-2, the payload of which encapsulates the MC system authentication and contract information of the terminal device 1 and the address information of the local MC system 1, and the destination address field of the message header of the message 2-2 encapsulates the address information of the local MC system 3. The local MC system 3 parses the payload of the received message 2-2 to obtain the MC system authentication and contract information of the terminal device 1 and the address information of the local MC system 1. The local MC system 3 can determine, based on the address information of the local MC system 1, that the MC system authentication and contract information of the terminal device 1 needs to be forwarded to the local MC system 1. For the specific forwarding process, please refer to step 605.

[0271] Step 605: The network device 3 forwards the authentication and signing information of the terminal device 1 based on the destination indication information.

[0272] The local network device 3 uses the address indicated by the destination indication information as the destination address and forwards the authentication and contract information of the terminal device 1.

[0273] Exemplarily, local core network device 3 sends message 3-1. The payload of message 3-1 encapsulates the core network authentication and subscription information of terminal device 1, and the destination address field of the message header of message 3-1 encapsulates the address information of local core network device 1. Message 3-1 arrives at local core network device 1 via the connection path between access network device 3 and access network device 1. Local core network device 1 parses the payload of received message 3-1 to obtain the core network authentication and subscription information of terminal device 1, and stores this core network authentication and subscription information for future use by terminal device 1 when requesting authentication from local core network device 1.

[0274] For example, local core network device 3 sends message 3-2, the payload of which encapsulates the MC system authentication and contract information of terminal device 1. The destination address field of the message header of message 3-2 encapsulates the address information of local MC system 1. Message 3-2 reaches local MC system 1 via the connection path between access network device 3 and access network device 1. Local MC system 1 parses the payload of received message 3-2 to obtain the MC system authentication and contract information of terminal device 1, and stores the MC system authentication and contract information of terminal device 1 for future use by terminal device 1 when applying for authentication and certification in local MC system 1.

[0275] In this embodiment, steps 606 to 610 are optional steps.

[0276] Step 606 : Terminal device 1 performs authentication on local network device 1 .

[0277] When the terminal device 1 is connected to the access network device 1 and the backhaul communication of the access network device 1 is interrupted, the terminal device 1 will perform authentication on the local network device 1 .

[0278] In this embodiment, step 606 is an optional step. Step 606 is similar to step 307 above. For details, please refer to the relevant description of step 307 above, which will not be repeated here.

[0279] Step 607 : The BOSS sends the first indication information and the destination indication information to the local network device 3 .

[0280] Among them, the first indication information is used to indicate the deletion of the authentication and signing information of the terminal device 1 in the local network device 1.

[0281] Step 608: The network device 3 forwards the first indication information based on the destination indication information.

[0282] The way in which BOSS forwards the first indication information is the same as the way in which BOSS forwards the authentication and signing information of terminal device 1. For details, please refer to the relevant introduction in steps 604 to 605 above, which will not be repeated here.

[0283] Step 609: The local network device 1 deletes the authentication and signing information of the terminal device 1.

[0284] Exemplarily, the local core network device 2 receives the first indication information and deletes the core network authentication and subscription information of the terminal device 1 in response to the first indication information.

[0285] Exemplarily, the local MC system 2 receives the first indication information and deletes the MC system authentication and contract information of the terminal device 1 in response to the first indication information.

[0286] In step 610 , the BOSS deletes the correspondence between the terminal device 1 and the access network device 1 in the mapping table 2 .

[0287] Since mapping table 2 not only reflects which access network devices the terminal device has accessed, but also indirectly reflects which local network devices corresponding to the access network devices store the authentication and contract information of the terminal device, when the BOSS instructs local network device 2 to delete the authentication and contract information of terminal device 1, the BOSS deletes the correspondence between terminal device 1 and access network device 2 in mapping table 2.

[0288] In this embodiment, the BOSS not only maintains the correspondence between the access network device and the local network device (e.g., mapping table 1), but also maintains the correspondence between the access network device and the adjacent access network device (or the connected access network device) (e.g., mapping table 3). This allows the BOSS to search for the access network device 3 connected to the access network device 1 based on the identification information of the access network device 1 and mapping table 3, and then search for the local network device 3 deployed near the access network device 3 based on the identification information of the access network device 3 and mapping table 1. The BOSS sends the authentication and contract information of the terminal device to the local network device 1 through the local network device 3. This helps to improve the reliability of the BOSS synchronizing the authentication and contract information to the local network device 1.

[0289] As shown in Figures 8 and 7B, each mapping table is maintained in a macro network device. The macro network device is an example of the aforementioned first network device, access network device 1 is an example of the aforementioned first access network device, local network device 1 is an example of the aforementioned second network device, access network device 2 is an example of a third access network device that the terminal device has historically accessed, local network device 2 is an example of a fourth network device corresponding to the third access network device, access network device 3 is an example of the aforementioned second access network device, local network device 3 is an example of the aforementioned third network device, and terminal device 1 is an example of the aforementioned terminal device. In this embodiment, each network element mainly performs the following steps:

[0290] Step 801: The BOSS sends the authentication and subscription information of the terminal device 1 and the identification information of the access network device 1 to the macro network device.

[0291] The authentication and contract information of the terminal device 1 includes the identification information of the terminal device 1. The authentication and contract information of the terminal device 1 can be generated by the BOSS or manually configured, which is not limited in this application. The identification information of the access network device 1 can be manually configured in the BOSS.

[0292] In step 802 , the macro network device stores the identification information of the terminal device 1 and the identification information of the access network device 1 in a corresponding manner in the mapping table 2 .

[0293] The macro network device stores a mapping table 2 for maintaining the correspondence between the terminal device and the access network device to which the terminal device is connected. For details about the mapping table 2 stored in the macro network device, please refer to the relevant introduction in step 308 above and will not be repeated here.

[0294] Step 803 : The macro network device determines the local network device 1 based on the identification information of the access network device 1 and the mapping table 1 .

[0295] It should be noted that there is no time sequence limit between step 802 and step 803, that is, the macro network device can execute step 802 first and then step 803, or the macro network device can execute step 803 first and then step 802, or the macro network device can execute step 802 and step 803 simultaneously.

[0296] In this embodiment, step 803 is similar to step 305 described above. Please refer to the relevant introduction in step 305 described above for details, which will not be repeated here.

[0297] Step 804 : When the macro network device determines that the connection path between the macro network device and the local network device 1 is interrupted, the macro network device determines the local network device 3 corresponding to the access network device 3 adjacent to the access network device 1 based on mapping table 1 and mapping table 3 .

[0298] Step 805 : The macro network device sends the authentication and contract information and purpose indication information of the terminal device 1 to the local network device 3 .

[0299] Step 806: The network device 3 forwards the authentication and signing information of the terminal device 1 based on the purpose indication information.

[0300] In this embodiment, steps 804 to 806 are similar to steps 603 to 605 performed by the BOSS in the previous text. For details, please refer to the relevant introduction in steps 603 to 605 in the previous text, which will not be repeated here.

[0301] In this embodiment, steps 807 to 811 are optional steps. In this embodiment, steps 807 to 811 are similar to steps 606 to 610 performed by the BOSS above. For details, please refer to the relevant introduction of steps 606 to 610 above, which will not be repeated here.

[0302] Step 807 : Terminal device 1 performs authentication on local network device 1 .

[0303] In this embodiment, step 807 is an optional step. Step 807 is similar to step 307 above. For details, please refer to the relevant description of step 307 above, which will not be repeated here.

[0304] Step 808 : The macro network device sends first indication information and destination indication information to the local network device 3 .

[0305] Step 809: The network device 3 forwards the first indication information based on the destination indication information.

[0306] Step 810: The local network device 1 deletes the authentication and signing information of the terminal device 1.

[0307] In step 811 , the macro network device deletes the correspondence between the terminal device 1 and the access network device 1 in the mapping table 2 .

[0308] In this embodiment, when the connection path between the macro network device (e.g., the macro core network device and / or the macro MC system) and the local network device is interrupted, the macro network device can forward the authentication and contract information of the terminal device through other local network devices (e.g., network device 3). The specific steps are similar to those in the embodiment corresponding to Figure 6 above and are not repeated here.

[0309] In this embodiment, the macro network device not only maintains the correspondence between access network devices and local network devices (e.g., mapping table 1), but also maintains the correspondence between access network devices and adjacent access network devices (or connected access network devices) (e.g., mapping table 3). This allows the macro network device to search for access network device 3 connected to access network device 1 based on the identification information of access network device 1 and mapping table 3, and then search for local network device 3 deployed near access network device 3 based on the identification information of access network device 3 and mapping table 1. The BOSS sends the authentication and contract information of the terminal device to the local network device 1 via the local network device 3. This helps improve the reliability of the macro network device synchronizing the authentication and contract information to the local network device 1.

[0310] Corresponding to the scheme given in the above method embodiment, the embodiment of the present application also provides a corresponding communication device (also referred to as a communication apparatus) and a communication system, which includes a module or unit for executing each part of the above embodiment. The module or unit can be software, hardware, or a combination of software and hardware. The following is only a brief description of the communication device and system. For the details of the implementation of the scheme, please refer to the description of the above method embodiment, which will not be repeated below.

[0311] FIG9 is a schematic diagram of the structure of a communication device 90 provided in this application. It should be understood that the core network device (e.g., a macro core network device or a local core network device) in the method embodiments corresponding to FIG2, FIG3, FIG5, FIG6, or FIG8 can be based on the structure of the communication device 90 shown in FIG9 in this embodiment.

[0312] As shown in Figure 9, the communication device 90 may include a processor 901, a memory 903, and a communication interface 902. The processor 901 is coupled to the memory 903, and the processor 901 is coupled to the communication interface 902.

[0313] The communication interface 902 is connected to other communication devices via a communication link. For example, the communication interface 902 may include a network interface with an access network device (eg, the communication device 90 shown in FIG9 ), such as an S1 interface.

[0314] The processor 901 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or any combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor 901 may be a single processor or may include multiple processors, which is not specifically limited herein.

[0315] In addition, the aforementioned memory 903 is mainly used to store software programs and data. The memory 903 can exist independently and be connected to the processor 901. Optionally, the memory 903 can be integrated with the processor 901, for example, integrated into one or more chips. Among them, the memory 903 can store program codes for executing the technical solutions of the embodiments of the present application, and is controlled and executed by the processor 901. The various types of computer program codes executed can also be regarded as drivers for the processor 901. The memory 903 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory may also include non-volatile memory (non-volatile memory), such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 903 may also include a combination of the above types of memory. The memory 903 may refer to a single memory or may include multiple memories. Exemplarily, the memory 903 is used to store various data. Exemplarily, the memory 903 is used to store the various corresponding relationships (e.g., the first corresponding relationship, the second corresponding relationship, and the third corresponding relationship, etc.) described in the embodiment corresponding to FIG. 2 . Exemplarily, the memory 903 is used to store the various mapping tables (e.g., mapping table 1, mapping table 2, and mapping table 3, etc.) described in the embodiment corresponding to FIG. 3 or FIG. 8 . Exemplarily, the memory 903 is used to store the authentication and contract information of the terminal device, for example, the core network authentication and contract information used by the terminal device when applying for authentication and certification on the core network device (macro core network device or local core network device).

[0316] In one design, a communication device 90 is configured to execute the method of the macro core network device (i.e., the first network device) in the embodiments corresponding to Figures 2, 3, 5, 6, or 8. The communication interface 902 is configured to obtain identification information of a terminal device and identification information of a first access network device; the processor 901 is configured to determine a second network device based on the identification information of the first access network device, where the second network device is a local network device that provides services to terminal devices accessing the first access network device when a backhaul link is interrupted; and the communication interface 902 is further configured to send authentication and contract information of the terminal device to be synchronized to the second network device, where the authentication and contract information of the terminal device is used by the terminal device accessing the first access network device to authenticate on the second network device.

[0317] In one possible implementation, a first correspondence relationship is stored in the memory 903, where the first correspondence relationship is used to indicate a correspondence relationship between the first access network device and the second network device. The processor 901 is specifically configured to determine the second network device corresponding to the first access network device based on the identification information of the first access network device and the first correspondence relationship.

[0318] In a possible implementation, when it is determined that the connection path to the second network device is not interrupted, the communication interface 902 is specifically configured to send the authentication and signing information of the terminal device to the second network device.

[0319] For example, the communication interface 902 is specifically used to send a first message, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and contract information of the terminal device.

[0320] In one possible embodiment, when it is determined that the connection path with the second network device is interrupted, the processor 901 is specifically used to determine the second access network device and a third network device corresponding to the second access network device based on the identification information of the first access network device, the third network device being a local network device that provides services for terminal devices accessing the second access network device when the return link is interrupted, there is a connection path between the first access network device and the second access network device, and there is a connection path between the first access network device and the second network device; the communication interface 902 is specifically used to send authentication and signing information of the terminal device to the second network device through the third network device.

[0321] For example, the communication interface 902 is specifically used to send a second message, the destination address field of the message header of the second message carries the address information of the third network device, and the payload field of the second message carries the authentication and contract information of the terminal device and the address information of the second network device; the address information of the second network device in the payload field is used by the third network device to generate a third message to be sent to the second network device, the destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and contract information of the terminal device.

[0322] In one possible implementation, a second correspondence and a third correspondence are stored in the memory 903, the second correspondence is used to indicate the correspondence between the first access network device and the second access network device, and the third correspondence is used to indicate the correspondence between the second access network device and the third network device; the processor 901 is specifically used to determine the second access network device based on the identification information of the first access network device and the second correspondence; and, determine the third network device corresponding to the second access network device based on the identification information of the second access network device and the third correspondence.

[0323] In a possible implementation, the memory 903 stores identification information of a third access network device and address information of a fourth network device, where the third access network device is an access network device that the terminal device has historically accessed, the fourth network device is a local network device that provides services to the terminal device accessing the third access network device when the backhaul link is interrupted, and the fourth network device stores authentication contract information of the terminal device;

[0324] The processor 901 is also used to send first indication information to the fourth network device through the communication interface 902 when the identification information of the first access network device is different from the identification information of the third access network device. The first indication information is used to indicate the deletion of the authentication and contract information of the terminal device.

[0325] In one possible embodiment, the communication interface 902 is also used to obtain identification information of the terminal device and identification information of a fourth access network device, where the fourth access network device is different from the first access network device; and to send first indication information to the second network device, where the first indication information is used to indicate the deletion of the authentication and contract information of the terminal device.

[0326] It should be noted that the specific implementation methods and beneficial effects of this embodiment can refer to the method of the macro core network device (ie, the first network device) in the above embodiment, which will not be repeated here.

[0327] In another design, a communication device 90 is configured to execute the method of a local core network device (i.e., a second network device) in the embodiments corresponding to Figures 2, 3, 5, 6, or 8. The communication interface 902 is configured to receive authentication contract information of a terminal device, where the terminal device is a terminal device that has accessed or is about to access a first access network device, and the second network device is a local network device that provides services to terminal devices that access the first access network device when a backhaul link is interrupted; and the processor 901 is configured to authenticate the terminal device that applies for authentication based on the authentication contract information of the terminal device.

[0328] In a possible implementation, the communication interface 902 is specifically used to receive authentication and subscription information of a terminal device from a first network device, where the first network device is a network device that provides services to terminal devices accessing the first access network device when the backhaul link is not interrupted.

[0329] For example, the communication interface 902 is specifically used to receive a first message from a first network device, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and contract information of the terminal device.

[0330] In one possible embodiment, the communication interface 902 is specifically used to receive authentication and signing information of a terminal device sent by the first network device from a third network device through a connection path between the first access network device and the second access network device. The first network device is a network device that provides services to terminal devices accessing the first access network device when the return link is not interrupted, and the third network device is a local network device that provides services to terminal devices accessing the second access network device when the return link is interrupted.

[0331] For example, the communication interface 902 is specifically used to receive a third message from a third network device. The destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and contract information of the terminal device.

[0332] In a possible implementation, the communication interface 902 is specifically used to receive first indication information, where the first indication information is used to indicate deletion of authentication and contract information of the terminal device; the processor 901 is also used to delete the authentication and contract information of the terminal device.

[0333] It should be noted that the specific implementation methods and beneficial effects of this embodiment can refer to the method of the local core network device (ie, the second network device) in the above embodiment, which will not be repeated here.

[0334] Figure 10 is a schematic diagram of the structure of another communication device 100 provided in this application. It should be understood that the terminal device in the method embodiments corresponding to Figures 2, 3, 5, 6 or 8 can be based on the structure of the communication device 100 shown in Figure 10 of this embodiment.

[0335] Communication device 100 includes at least one processor 1001, at least one memory 1002, and at least one transceiver 1003. Processor 1001, memory 1002, and transceiver 1003 are connected. Optionally, communication device 100 may further include an input device 1005, an output device 1006, and one or more antennas 1004. Antenna 1004 is connected to transceiver 1003, and input device 1005 and output device 1006 are connected to processor 1001.

[0336] In this embodiment, the memory 1002 is mainly used to store software programs and data. The memory 1002 can be independent and connected to the processor 1001. Optionally, the memory 1002 can be integrated with the processor 1001, for example, integrated into one or more chips. Among them, the memory 1002 can store program codes for executing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 1001. The various types of computer program codes executed can also be regarded as drivers for the processor 1001. It should be understood that Figure 10 in this embodiment only shows one memory and one processor, but in actual applications, the communication device 100 can have multiple processors or multiple memories, which is not limited here. In addition, the memory 1002 can also be referred to as a storage medium or a storage device. The memory 1002 can be a storage element on the same chip as the processor (i.e., an on-chip storage element), or an independent storage element, which is not limited in this embodiment of the present application.

[0337] In this embodiment, the transceiver 1003 can be used to support the reception or transmission of radio frequency signals between the communication device 100 and the access network device. The transceiver 1003 can be connected to the antenna 1004. The transceiver 1003 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1004 can receive radio frequency signals. The receiver Rx of the transceiver 1003 is used to receive the radio frequency signals from the antenna 1004, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 1001 so that the processor 1001 can further process the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transmitter Tx in the transceiver 1003 is also used to receive modulated digital baseband signals or digital intermediate frequency signals from the processor 1001, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 1004. Specifically, the receiver Rx can selectively perform one or more stages of down-mixing and analog-to-digital conversion on the RF signal to obtain a digital baseband signal or a digital intermediate frequency signal. The order of the down-mixing and analog-to-digital conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of up-mixing and digital-to-analog conversion on the modulated digital baseband signal or digital intermediate frequency signal to obtain a RF signal. The order of the up-mixing and digital-to-analog conversion processes is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as digital signals.

[0338] It should be understood that the aforementioned transceiver 1003 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc. Optionally, a device in the transceiver unit that implements a receiving function may be referred to as a receiving unit, and a device in the transceiver unit that implements a transmitting function may be referred to as a transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0339] Processor 1001 can be a baseband processor or a central processing unit (CPU). The baseband processor and CPU can be integrated or separate. Processor 1001 can be used to implement various functions for the terminal device, such as processing communication protocols and communication data, controlling the entire terminal device, executing software programs, and processing software program data; or assisting in completing computing tasks, such as graphics, image processing, or audio processing. Alternatively, processor 1001 can be used to implement one or more of the above functions.

[0340] In addition, the output device 1006 communicates with the processor 1001 and can display information in a variety of ways, which are not specifically limited here.

[0341] In one design, the communication device 100 is configured to execute the method of the terminal device in the embodiment corresponding to Figures 2, 3, 5, 6, or 8. The transceiver 1003 in the communication device 100 is configured to send identification information of the terminal device and identification information of the first access network device to the first network device through the first access network device, the identification information of the terminal device and the identification information of the first access network device being used by the first network device to determine the second network device based on the identification information of the first access network device, and synchronize the authentication and subscription information of the terminal device to the second network device, the second network device being a local network device that provides services to the terminal device accessing the first access network device when the backhaul link is interrupted; and receiving second indication information from the first access network device, the second indication information being used to indicate that the backhaul link of the first access network device is interrupted; the processor 1001 is configured to perform authentication and obtain communication services on the second network device.

[0342] In a possible implementation, the transceiver 1003 is further configured to receive a system broadcast message from the first access network device, where the system broadcast message includes identification information of the first access network device.

[0343] It should be noted that the specific implementation and beneficial effects of this embodiment can be referred to the method of the terminal device in the above embodiment, and will not be repeated here.

[0344] FIG11 is a schematic diagram of the structure of a server 110 provided in this application. It should be understood that the MC system (e.g., macro MC system or local MC system) or BOSS in the method embodiments corresponding to FIG2 , FIG3 , FIG5 , FIG6 , or FIG8 can be based on the structure of the server 110 shown in FIG11 in this embodiment.

[0345] As shown in Figure 11, the server 110 may include a processor 1101, a memory 1103, and a communication interface 1102. The processor 1101 is coupled to the memory 1103, and the processor 1101 is coupled to the communication interface 1102.

[0346] The communication interface 1102 is connected to other communication devices via a communication link. For example, the communication interface 1102 may include a network interface, such as an S1 interface, with an access network device (eg, the server 110 shown in FIG11 ).

[0347] The processor 1101 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or any combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor 1101 may be a single processor or may include multiple processors, which is not specifically limited herein.

[0348] In addition, the aforementioned memory 1103 is mainly used to store software programs and data. The memory 1103 can exist independently and be connected to the processor 1101. Optionally, the memory 1103 can be integrated with the processor 1101, for example, integrated into one or more chips. Among them, the memory 1103 can store program codes for executing the technical solutions of the embodiments of the present application, and is controlled and executed by the processor 1101. The various types of computer program codes executed can also be regarded as drivers for the processor 1101. The memory 1103 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory may also include non-volatile memory (non-volatile memory), such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 1103 may also include a combination of the above types of memory. The memory 1103 may refer to one memory or may include multiple memories. Exemplarily, the memory 1103 is used to store various data. Exemplarily, the memory 1103 is used to store the various corresponding relationships introduced in the embodiment corresponding to FIG2 (for example, the first corresponding relationship, the second corresponding relationship, and the third corresponding relationship, etc.). Exemplarily, the memory 1103 is used to store the various mapping tables introduced in the embodiment corresponding to FIG3 or FIG8 (for example, mapping table 1, mapping table 2, and mapping table 3, etc.). Exemplarily, the memory 1103 is used to store the authentication contract information of the terminal device, for example, the MC system authentication contract information used by the terminal device when applying for authentication and certification in the MC system (macro MC system or local MC system).

[0349] In one design, the server 110 is configured to execute the method of the macro MC system (i.e., the first network device) or the BOSS (i.e., the first network device) in the embodiments corresponding to Figures 2, 3, 5, 6, or 8. The communication interface 1102 is configured to obtain identification information of the terminal device and identification information of the first access network device; the processor 1101 is configured to determine a second network device based on the identification information of the first access network device, where the second network device is a local network device that provides services to the terminal device accessing the first access network device when the backhaul link is interrupted; and the communication interface 1102 is further configured to send authentication and contract information of the terminal device to be synchronized to the second network device, where the authentication and contract information of the terminal device is used by the terminal device accessing the first access network device to authenticate on the second network device.

[0350] In one possible implementation, a first correspondence relationship is stored in the memory 1103, where the first correspondence relationship is used to indicate a correspondence relationship between the first access network device and the second network device. The processor 1101 is specifically configured to determine the second network device corresponding to the first access network device based on the identification information of the first access network device and the first correspondence relationship.

[0351] In a possible implementation, when it is determined that the connection path to the second network device is not interrupted, the communication interface 1102 is specifically configured to send the authentication and signing information of the terminal device to the second network device.

[0352] For example, the communication interface 1102 is specifically used to send a first message, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and contract information of the terminal device.

[0353] In one possible embodiment, when it is determined that the connection path between the first access network device and the second network device is interrupted, the processor 1101 is specifically used to determine the second access network device and the third network device corresponding to the second access network device based on the identification information of the first access network device, the third network device is a local network device that provides services for the terminal device accessing the second access network device when the return link is interrupted, there is a connection path between the first access network device and the second access network device, and there is a connection path between the first access network device and the second network device; the communication interface 1102 is specifically used to send the authentication and signing information of the terminal device to the second network device through the third network device.

[0354] For example, the communication interface 1102 is specifically used to send a second message, the destination address field of the message header of the second message carries the address information of the third network device, and the payload field of the second message carries the authentication and contract information of the terminal device and the address information of the second network device; the address information of the second network device in the payload field is used by the third network device to generate a third message to be sent to the second network device, the destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and contract information of the terminal device.

[0355] In one possible implementation, a second correspondence and a third correspondence are stored in the memory 1103, the second correspondence is used to indicate the correspondence between the first access network device and the second access network device, and the third correspondence is used to indicate the correspondence between the second access network device and the third network device; the processor 1101 is specifically used to determine the second access network device based on the identification information of the first access network device and the second correspondence; and, determine the third network device corresponding to the second access network device based on the identification information of the second access network device and the third correspondence.

[0356] In a possible implementation, the memory 1103 stores identification information of a third access network device and address information of a fourth network device, where the third access network device is an access network device that the terminal device has historically accessed, the fourth network device is a local network device that provides services to the terminal device accessing the third access network device when the backhaul link is interrupted, and the fourth network device stores authentication contract information of the terminal device;

[0357] The processor 1101 is also used to send first indication information to the fourth network device through the communication interface 1102 when the identification information of the first access network device is different from the identification information of the third access network device. The first indication information is used to indicate the deletion of the authentication and contract information of the terminal device.

[0358] In one possible embodiment, the communication interface 1102 is also used to obtain identification information of the terminal device and identification information of a fourth access network device, where the fourth access network device is different from the first access network device; and to send first indication information to the second network device, where the first indication information is used to indicate the deletion of the authentication and contract information of the terminal device.

[0359] It should be noted that the specific implementation and beneficial effects of this embodiment can refer to the method of the macro MC system (ie, the first network device) or BOSS (ie, the first network device) in the above embodiments, which will not be repeated here.

[0360] In another design, the server 110 is configured to execute the method of the local MC system (i.e., the second network device) in the embodiments corresponding to Figures 2, 3, 5, 6, or 8. The communication interface 1102 is configured to receive authentication contract information of a terminal device, where the terminal device is a terminal device that has been connected to or is about to be connected to the first access network device, and the second network device is a local network device that provides services to the terminal device connected to the first access network device when the backhaul link is interrupted; and the processor 1101 is configured to authenticate the terminal device that applies for authentication based on the authentication contract information of the terminal device.

[0361] In a possible implementation, the communication interface 1102 is specifically used to receive authentication and subscription information of a terminal device from a first network device, where the first network device is a network device that provides services to terminal devices accessing the first access network device when the backhaul link is not interrupted.

[0362] For example, the communication interface 1102 is specifically used to receive a first message from a first network device, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and signing information of the terminal device.

[0363] In one possible embodiment, the communication interface 1102 is specifically used to receive authentication and signing information of a terminal device sent by the first network device from a third network device through a connection path between the first access network device and the second access network device. The first network device is a network device that provides services to terminal devices accessing the first access network device when the return link is not interrupted, and the third network device is a local network device that provides services to terminal devices accessing the second access network device when the return link is interrupted.

[0364] For example, the communication interface 1102 is specifically used to receive a third message from a third network device. The destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and signing information of the terminal device.

[0365] In a possible implementation, the communication interface 1102 is specifically used to receive first indication information, where the first indication information is used to indicate deletion of the authentication and contract information of the terminal device; the processor 1101 is also used to delete the authentication and contract information of the terminal device.

[0366] It should be noted that the specific implementation methods and beneficial effects of this embodiment can refer to the method of the local core network device (ie, the second network device) in the above embodiment, which will not be repeated here.

[0367] As shown in Figure 12, the present application also provides a device 120. The device 120 can be a terminal device, a core network device MC system, or a BOSS, or a component (e.g., an integrated circuit, a chip, etc.) of the terminal device, the core network device MC system, or the BOSS. The device 120 can also be other communication modules for implementing the methods in the method embodiments of the present application.

[0368] The device 120 may include a processing module 1201 (or processing unit). Optionally, it may also include an interface module 1202 (or transceiver unit or transceiver module) and a storage module 1203 (or storage unit). The interface module 1202 is used to implement communication with other devices. For example, the interface module 1202 may be a transceiver module or an input / output module.

[0369] In one possible design, one or more modules in FIG12 may be implemented by one or more processors, or by one or more processors and memories, or by one or more processors and transceivers, or by one or more processors, memories, and transceivers, which are not limited in this embodiment of the present application. The processors, memories, and transceivers may be provided separately or integrated.

[0370] The device 120 has the functions of implementing the core network device described in the embodiment of the present application. For example, the device 120 includes a module or unit or means (means) corresponding to the core network device executing the steps involved in the core network device described in the embodiment of the present application. The functions or units or means (means) can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment. For details, please refer to the device 90 in the corresponding embodiment of Figure 9 above.

[0371] Alternatively, the device 120 has the functions of implementing the terminal device described in the embodiments of the present application. For example, the device 120 includes a module or unit or means corresponding to the steps involved in the terminal device described in the embodiments of the present application. The functions or units or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment. For details, please refer to the device 100 in the embodiment corresponding to Figure 10 above.

[0372] Alternatively, the device 120 has the function of implementing the MC system (or BOSS) described in the embodiment of the present application. For example, the device 120 includes a module or unit or means (means) corresponding to the MC system (or BOSS) performing the steps involved in the MC system (or BOSS) described in the embodiment of the present application. The function or unit or means (means) can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment. Please refer to the device 110 in the corresponding embodiment of Figure 11 above.

[0373] In addition, the present application provides a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiments of the present application is generated in whole or in part. For example, the method related to the first network device in Figures 2, 3, 5, 6, or 8 is implemented. For another example, the method related to the terminal device in Figures 2, 3, 5, 6, or 8 is implemented. For another example, the method related to the second network device in Figures 2, 3, 5, 6, or 8 is implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network, 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 computer-readable storage medium. 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 available medium capable of storing data on a computer, or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)).

[0374] In addition, the present application also provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement a method related to the first network device as shown in Figures 2, 3, 5, 6 or 8 above.

[0375] In addition, the present application also provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement a method related to the terminal device as shown in Figures 2, 3, 5, 6 or 8 above.

[0376] In addition, the present application also provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement a method related to the second network device as shown in Figures 2, 3, 5, 6 or 8 above.

[0377] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0378] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

Claims

1. An information synchronization method, characterized in that: include: The first network device obtains identification information of the terminal device and identification information of the first access network device; The first network device determines a second network device based on the identification information of the first access network device, where the second network device is a local network device that provides services for a terminal device accessing the first access network device when a backhaul link is interrupted; The first network device sends the authentication and contract information of the terminal device to be synchronized to the second network device, and the authentication and contract information of the terminal device is used for the terminal device accessing the first access network device to authenticate on the second network device.

2. The method according to claim 1, characterized in that The first network device stores a first corresponding relationship, where the first corresponding relationship is used to indicate a corresponding relationship between the first access network device and the second network device; The first network device determines the second network device based on the identification information of the first access network device, including: The first network device determines the second network device corresponding to the first access network device based on the identification information of the first access network device and the first corresponding relationship.

3. The method according to claim 1 or 2, characterized in that: The first network device sends the authentication contract information of the terminal device to be synchronized to the second network device, including: If the first network device determines that the connection path between the first network device and the second network device is not interrupted, the first network device sends the authentication signing information of the terminal device to the second network device.

4. The method according to claim 3, characterized in that The first network device sends the authentication contract information of the terminal device to the second network device, including: The first network device sends a first message, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and signing information of the terminal device.

5. The method according to claim 1 or 2, characterized in that: The first network device sends the authentication contract information of the terminal device to be synchronized to the second network device to the second network device, including: If the first network device determines that the connection path between the first network device and the second network device is interrupted, the first network device determines the second access network device and the third network device corresponding to the second access network device based on the identification information of the first access network device, the third network device is a local network device that provides services for the terminal device accessing the second access network device when the backhaul link is interrupted, there is a connection path between the first access network device and the second access network device, and there is a connection path between the first access network device and the second network device; The first network device sends the authentication signing information of the terminal device to the second network device through the third network device.

6. The method according to claim 5, characterized in that The first network device sends the authentication signing information of the terminal device to the second network device through the third network device, including: The first network device sends a second message, the destination address field of the message header of the second message carries the address information of the third network device, and the payload field of the second message carries the authentication and contract information of the terminal device and the address information of the second network device; the address information of the second network device in the payload field is used by the third network device to generate a third message to be sent to the second network device, the destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and contract information of the terminal device.

7. The method according to claim 5, characterized in that The first network device stores a second corresponding relationship, where the second corresponding relationship is used to indicate the corresponding relationship between the first access network device and the second access network device; the first network device stores a third corresponding relationship, where the third corresponding relationship is used to indicate the corresponding relationship between the second access network device and the third network device; The first network device determines the second access network device and the third network device corresponding to the second access network device based on the identification information of the first access network device, including: The first network device determines the second access network device based on the identification information of the first access network device and the second corresponding relationship; The first access network device determines the third network device corresponding to the second access network device based on the identification information of the second access network device and the third corresponding relationship.

8. The method according to any one of claims 1 to 7, characterized in that The first network device stores identification information of a third access network device and address information of a fourth network device, the third access network device is an access network device that the terminal device has accessed historically, the fourth network device is a local network device that provides services for the terminal device accessing the third access network device when the backhaul link is interrupted, and the fourth network device stores authentication and contract information of the terminal device; The method further comprises: When the identification information of the first access network device is different from the identification information of the third access network device, the first network device sends first indication information to the fourth network device, where the first indication information is used to indicate deletion of the authentication contract information of the terminal device.

9. The method according to any one of claims 1 to 8, characterized in that After the first network device sends the authentication contract information of the terminal device to be synchronized to the second network device, the method further includes: The first network device acquires identification information of the terminal device and identification information of a fourth access network device, where the fourth access network device is different from the first access network device; The first network device sends first indication information to the second network device, where the first indication information is used to indicate deletion of the authentication contract information of the terminal device.

10. The method according to any one of claims 1 to 9, characterized in that The second network device is a local core network device, and the authentication and contract information of the terminal device includes the authentication and contract information used by the terminal device in the local core network device; and / or, the second network device is a local MC system, and the authentication and contract information of the terminal device includes the authentication and contract information used by the terminal device in the local MC system.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: The first network device generates authentication and signing information for the terminal device, and the first network device is a telecommunication business operation support system BOSS.

12. The method according to claim 11, characterized in that The first network device acquires identification information of the terminal device and identification information of the first access network device, including: The first network device receives manually configured identification information of the terminal device and identification information of the first access network device.

13. The method according to any one of claims 1 to 10, characterized in that The method further comprises: The first network device obtains the authentication and contract information of the terminal device from the telecommunications business operation support system BOSS. The first network device is a network device that provides services for terminal devices accessing the first access network device when the return link is not interrupted. The first network device is a macro core network device, and / or the first network device is a macro MC system.

14. The method according to claim 13, characterized in that The first network device acquires identification information of the terminal device and identification information of the first access network device, including: The first network device receives identification information of the terminal device and identification information of the first access network device from the terminal device through the first access network device.

15. An information synchronization method, characterized in that: include: The terminal device sends identification information of the terminal device and identification information of the first access network device to the first network device through the first access network device, and the identification information of the terminal device and the identification information of the first access network device are used by the first network device to determine the second network device based on the identification information of the first access network device, and synchronize the authentication and contract information of the terminal device to the second network device, where the second network device is a local network device that provides services for the terminal device accessing the first access network device when the backhaul link is interrupted; The terminal device receives second indication information from the first access network device, where the second indication information is used to indicate that a backhaul link of the first access network device is interrupted; The terminal device performs authentication on the second network device and obtains communication services.

16. The method according to claim 15, characterized in that The terminal device is a terminal device that has been authenticated in the first network device.

17. The method according to claim 15 or 16, characterized in that Before the terminal device sends the identification information of the terminal device and the identification information of the first access network device to the first network device through the first access network device, the method further includes: The terminal device receives a system broadcast message of the first access network device, where the system broadcast message includes identification information of the first access network device.

18. An information synchronization method, characterized in that: include: The second network device receives authentication and signing information of a terminal device, where the terminal device is a terminal device that has been connected to or is about to be connected to the first access network device, and the second network device is a local network device that provides services for the terminal device that is connected to the first access network device when the backhaul link is interrupted; The second network device performs authentication on the terminal device that applies for authentication based on the authentication contract information of the terminal device.

19. The method according to claim 18, characterized in that The second network device receives the authentication contract information of the terminal device, including: The second network device receives the authentication subscription information of the terminal device from the first network device, and the first network device is a network device that provides services for the terminal device accessing the first access network device when the return link is not interrupted.

20. The method according to claim 18 or 19, characterized in that The second network device receives the authentication contract information of the terminal device, including: The second network device receives a first message from the first network device, the destination address field of the message header of the first message carries the address information of the second network device, and the payload field of the first message carries the authentication and signing information of the terminal device.

21. The method according to claim 18, characterized in that The second network device receives the authentication contract information of the terminal device, including: The second network device receives the authentication signing information of the terminal device sent by the first network device from the third network device through the connection path between the first access network device and the second access network device. The first network device is a network device that provides services for the terminal devices accessing the first access network device when the return link is not interrupted, and the third network device is a local network device that provides services for the terminal devices accessing the second access network device when the return link is interrupted.

22. The method according to claim 18 or 19, characterized in that The second network device receives the authentication contract information of the terminal device, including: The second network device receives a third message from the third network device, the destination address field of the message header of the third message carries the address information of the second network device, and the payload field of the third message carries the authentication and signing information of the terminal device.

23. The method according to any one of claims 18 to 22, characterized in that The method further comprises: The second network device receives first indication information, where the first indication information is used to instruct deletion of authentication and contract information of the terminal device; The second network device deletes the authentication contract information of the terminal device.

24. A communication device, characterized in that: including a processor and a memory; wherein the memory stores a computer program; The processor calls the computer program to cause the communication device to perform the method according to any one of claims 1 to 14.

25. A communication device, characterized in that: including a processor and a memory; wherein the memory stores a computer program; The processor calls the computer program to cause the communication device to perform the method according to any one of claims 15 to 17.

26. A communication device, characterized in that: including a processor and a memory; wherein the memory stores a computer program; The processor invokes the computer program to cause the communication device to perform the method according to any one of claims 18 to 23.

27. A computer-readable storage medium, characterized in that: Instructions are stored, and when the instructions are executed on a computer, the computer executes the method as claimed in any one of claims 1 to 14; or, executes the method as claimed in any one of claims 15 to 17; or, executes the method as claimed in any one of claims 18 to 23.

28. A computer program product, characterized in that When a computer reads and executes the computer program product, the method according to any one of claims 1 to 14 is executed, or the method according to any one of claims 15 to 17 is executed, or the method according to any one of claims 18 to 23 is executed.

Images