WO2020063248A1 - Procédé de déploiement multinuage de service en nuage basé sur un équipement de coordination - Google Patents

Procédé de déploiement multinuage de service en nuage basé sur un équipement de coordination Download PDF

Info

Publication number
WO2020063248A1
WO2020063248A1 PCT/CN2019/103480 CN2019103480W WO2020063248A1 WO 2020063248 A1 WO2020063248 A1 WO 2020063248A1 CN 2019103480 W CN2019103480 W CN 2019103480W WO 2020063248 A1 WO2020063248 A1 WO 2020063248A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
network element
terminal
base station
data
Prior art date
Application number
PCT/CN2019/103480
Other languages
English (en)
Chinese (zh)
Inventor
曹明荣
任嵘
陆晓萍
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020063248A1 publication Critical patent/WO2020063248A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a data backup method, device, and communication system.
  • the core network is an important part of the communication network. It is used to provide terminals with various functions such as mobility management, subscription information storage, authentication, and billing. It connects mobile terminals to external data networks in groups.
  • Various core network elements in the core network will store terminal data.
  • EPC evolved packet core network
  • MME mobility management entity
  • HSS home subscriber server
  • PCRF policy and charging rules function server
  • PCRF policy and charging rule function
  • a 1: 1 hot backup mechanism can be used to back up terminal data by performing symmetrical redundant deployment of each core network element.
  • N primary core network elements and N standby core network elements are deployed, and each primary core network element has a corresponding standby core network element, and each standby core network element and corresponding The storage capacity of the network elements of the main core network is the same.
  • the primary core network element When the primary core network element is in a normal state, the primary core network element will process the terminal's services and synchronize all stored data to the corresponding standby core network element in real time.
  • the standby core network element needs to correspond to the corresponding primary core network.
  • the network elements maintain synchronization in real time, receive all data stored by the network elements of the main core network, and store a backup of all data stored by the network elements of the main core network.
  • each standby core network element needs to maintain real-time synchronization with the corresponding primary core network element, and the storage capacity of each standby core network element needs to be the same as the corresponding primary core network element, resulting in a standby core network Network elements have high operating costs and costs.
  • the embodiments of the present application provide a data backup method, device, and communication system, which can solve the technical problems of excessive running cost and high cost of the backup core network element in related technologies.
  • the technical solution is as follows:
  • a data backup method includes:
  • the coordinating node stores the terminal of the primary core network element according to the correspondence between the base station and the standby core network
  • the data is synchronized to the standby core network element corresponding to the base station.
  • the backup core network element only needs to store the terminal data without real-time synchronization with the main core network element, thereby reducing the operating cost of the standby core network element.
  • each standby core network element only needs to store the terminal data of the corresponding base station, but does not need to store the data of all terminals, which reduces the storage capacity requirements of the standby core network element.
  • data disaster recovery can be achieved by backing up data on storage terminals of each standby core network.
  • the standby core network can take over the services of the main core network, which can improve the reliability and security of the core network.
  • the main core network access is normal, the operating cost of the standby core network is lower and the system performance is better.
  • determining the target standby core network corresponding to the base station from at least one standby core network according to the identifier of the base station includes:
  • the identifier of the base station query the correspondence between the identifier of the base station and the standby core network to obtain the target standby core network corresponding to the identifier of the base station.
  • the data of the terminal stored by the at least one primary core network element is sent to the at least one target standby core.
  • Network element including at least one of the following steps:
  • the address of the target standby core network element is sent to the main core network element, and the address of the target standby core network element is used for For the primary core network element to send data of the terminal to the target standby core network element;
  • each main core network element in the at least one main core network element sending a terminal data request to the main core network element, receiving data of the terminal of the main core network element,
  • the target standby core network element sends data of the terminal, wherein the terminal data request carries an identifier of the terminal.
  • the receiving the identity of the base station includes:
  • the at least one main core network element is located on a first cloud platform
  • the at least one target standby core network element is located on a second cloud platform
  • the second cloud platform is different from the first cloud platform .
  • the data of the terminal stored by the at least one primary core network element is sent to the at least one target standby core.
  • Network elements including:
  • the function type is compared with the function type according to the address of the target standby core network element and the function type of the target standby core network element.
  • Data of the terminal corresponding to the function type stored in the same primary core network element is sent to the target standby core network element.
  • the function storing the function type of the main core network element of the same function type as the function type
  • the data of the terminal corresponding to the type is sent to the target standby core network element, including at least one of the following steps:
  • a data backup device includes: a device for executing the data backup method.
  • the data backup device includes a function module for executing the data backup method according to the first aspect or any one of the first aspects.
  • a communication system includes a main core network, at least one standby core network, and a coordination node.
  • the main core network is configured to store data of a terminal
  • the coordination node is configured to receive an identity of the base station when the terminal is attached through a base station; and determine, from at least one standby core network, a target standby core network corresponding to the base station according to the base station identifier; The address of at least one target standby core network element in the target standby core network sends data of the terminal stored in at least one primary core network element to the at least one target standby core network element
  • a computer device includes a processor and a memory.
  • the memory stores at least one instruction, and the instruction is loaded and executed by the processor to implement the first aspect or the first aspect.
  • a computer-readable storage medium stores at least one instruction, and the instruction is loaded and executed by the processor to implement the first aspect or any one of the first aspects. The operations performed by the data backup method described in the selection method.
  • a computer program product containing instructions, which, when run on a computer device, enables the computer device to implement the data backup according to the first aspect or any one of the first optional aspects. The action performed by the method.
  • a chip is provided, where the chip includes a processor and / or program instructions, and when the chip is running, the data backup according to the first aspect or any one of the first optional aspects is implemented. The action performed by the method.
  • FIG. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic architecture diagram of a communication system according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 7 is a schematic architecture diagram of a communication system according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a computer device according to an embodiment of the present application.
  • FIG. 9 is a flowchart of a data backup method according to an embodiment of the present application.
  • FIG. 10 is a flowchart of a data backup method according to an embodiment of the present application.
  • FIG. 11 is a flowchart of a data backup method according to an embodiment of the present application.
  • FIG. 12 is a flowchart of a data backup method according to an embodiment of the present application.
  • FIG. 13 is a flowchart of a data backup method according to an embodiment of the present application.
  • 16 is a flowchart of a service processing method according to an embodiment of the present application.
  • FIG. 17 is a flowchart of a service processing method according to an embodiment of the present application.
  • FIG. 18 is a flowchart of a service processing method according to an embodiment of the present application.
  • FIG. 19 is a flowchart of a service processing method according to an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of a data backup device according to an embodiment of the present application.
  • FIG. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application.
  • the communication system includes a main core network, at least one standby core network, and a coordination node.
  • the main core network, at least one standby core network, and the coordination node may be interconnected through a network.
  • the communication system may further include at least one base station and at least one terminal.
  • the core network may be a core network in any kind of mobile communication network.
  • the core network may be an EPC network in a 4G network, including the following key network elements: MME network element, HSS network element, serving-gateway (SGW) network element, and packet data network gateway (packet data) network gateway (abbreviation: PGW) network element, PCRF network element, etc.
  • MME network element MME network element
  • HSS network element HSS network element
  • SGW serving-gateway
  • PGW packet data network gateway
  • PCRF network element Packet data network gateway
  • the core network may also be a core network in a 5G network
  • the core network may also be a core network in a 3G network. This embodiment does not limit the type of the core network.
  • the main core network element is used to provide core network related services.
  • the main core network element can be configured as the main service network element of the core network.
  • the network element of the main core network can store data of any terminal in the entire network.
  • the main core network element may be run on a cloud platform in the form of a cloud service, including but not limited to public cloud and private cloud.
  • the main core network element may also be deployed on an offline server.
  • the backup core network element is used to back up and store the data of the terminal stored by the primary core network element.
  • the backup core network element may be configured as a backup service network element of the core network.
  • the standby core network element can be used to provide core network services when the primary core network element is in an access failure state.
  • the data amount of the data of the terminal stored by the network element of the standby core network may be smaller than the data amount of the data of the terminal stored by the network element of the primary core network.
  • the specifications of the backup core network element may be smaller than the specifications of the primary core network element.
  • the storage capability of the backup core network element may be smaller than the storage capability of the primary core network element.
  • the processing capability of the backup core network element may be less than the processing capability of the primary core network element.
  • the backup core network element may be run on a cloud platform in the form of a cloud service, including but not limited to public cloud and private cloud.
  • the standby core network element may also be deployed on an offline server.
  • the coordination node is used to control data synchronization between the primary core network element and the standby core network element.
  • the coordinating node can operate in cooperation with the network element of the main core network.
  • the coordinating node can exchange information with the main base station and synchronize the terminal's data from the main core network element to the target backup device corresponding to the base station. Core network element.
  • the coordination node may also be used to perform fault detection on the main core network, and route and forward the request packets of the terminal according to the fault detection result.
  • the coordination node When the main core network is in the normal access state, if the coordination node receives the request message from the terminal, the coordination node can route the request message from the terminal to the network element of the main core network.
  • the coordination node When the main core network is in an access failure state, if the coordination node receives a request message from the terminal, the coordination node can route the request message from the terminal to the standby core network element.
  • the coordination node may include at least one of a first coordination node and a second coordination node.
  • the first coordination node is configured to route and forward the request message of the terminal, and the second coordination node is configured to control data synchronization between the primary core network element and the standby core network element.
  • the first coordination node may be deployed on any routing or switching device in the transmission network.
  • the first coordinating node may be one or more program modules newly added to the routing or switching device, thereby enhancing the functions of the original routing or switching device, so that the original routing or switching device can be implemented during operation.
  • the first coordination node may be deployed in an access layer or an aggregation layer of the bearer transmission network. Accordingly, the device where the first coordination node is located is a network device with data exchange and routing functions.
  • the device where the first coordination node can be deployed can be deployed at the eNodeB access to the WAN exit, such as PTN (packet transport network, PTN for short) and ATN (agile transport network, ATN) for access And so on.
  • the first coordination node may also be deployed on a virtualized white box router.
  • the first coordination node may be deployed separately from the routing or switching device.
  • the routing or switching device is used to forward the request message of the terminal.
  • the first coordination node may control one or more routing or switching devices.
  • the routing or switching equipment can be connected to the base station, the main core network element and the standby core network element.
  • the first coordination node is configured to control a manner in which the routing or switching device forwards the request message and an object in which the routing or switching device forwards the request message.
  • the first coordination node may maintain a routing table stored in a routing or switching device. When the primary core network element is in a normal access state, the first coordination node may write to a destination address in the routing table.
  • the first coordination node may control the routing or switching device to enable the diversion function, so as to forward the request packet of the terminal to the standby core network element.
  • the communication system may further include a routing node, and the routing node may be connected to the first coordination node and the backup core network element.
  • the routing node When the primary core network element is in an access failure state, the routing node is used to select the target standby core network element from multiple standby core network elements according to the routing priority.
  • the selected target standby core network element can Replaces the services of the network elements of the main core network.
  • the second coordination node may be uniformly deployed with the main core network element.
  • the second coordination node may be located in the same wireless network as the main core network element.
  • the second coordination node and the main core network element may both be deployed, for example, on the same public cloud or the same private cloud.
  • both the second coordination node and the main core network element may be deployed on an offline server.
  • the second coordination node may be one or more microservices newly added to the network element of the main core network.
  • an independent coordination microservice can be deployed in the main core network, and the coordination microservice can be used as the second coordination node.
  • the second coordination node may also be deployed in an existing microservice, for example, it is deployed in an access and mobility management (access and mobility management function (AMF)) network element.
  • AMF access and mobility management function
  • the second coordination node may also be a new program module in an original functional network element in the main core network, for example, it may be a new program module in an original MME network element in the main core network.
  • the main core network and the standby core network can be deployed on different cloud platforms to implement multi-cloud deployment of core network services.
  • the main core network may be located on the first cloud platform, and at least one standby core network may be located on the second cloud platform.
  • the second cloud platform is different from the first cloud platform.
  • the main core network and the standby core network may also be deployed in an offline network, and the networks where the main core network and the standby core network are located are isolated.
  • the deployment methods of the primary core network element and the standby core network element may include the following (1) to (4).
  • the main core network is located in the public cloud, and at least one standby core network is located in the private cloud.
  • different standby core network network elements in the at least one standby core network may be located on different private clouds.
  • all standby core network elements in standby core network 1 may be located on private cloud xx
  • standby core network element 1 on standby core network 2 may be located on private cloud yy
  • this standby core network 2 The standby core network element 2 may be located on the private cloud zz.
  • the main core network can be distributed and deployed on multiple public clouds.
  • different main core network elements in the main core network may be located on different public clouds.
  • the main core network element of the control plane and the main core network node of the data plane may be located on different public clouds.
  • different main core network nodes of the control plane may also be located on different public clouds.
  • different main core network nodes on the data plane can also be located on different public clouds.
  • the main core network is located in a private cloud, and at least one standby core network is located in a public cloud.
  • main core network By deploying the main core network on the private cloud and the standby core network on the public cloud, even if the private cloud has an access failure, core network services can still be provided through the backup core network elements located in the public cloud to reduce access failures. At the same time, the main core network is located in the private cloud, which can reduce the access delay of services under normal conditions.
  • different standby core network elements in the at least one standby core network may be located on different public clouds.
  • all the standby core network elements in the standby core network 1 are located on the public cloud aa
  • the standby core network element 1 in the standby core network 2 may be located on the public cloud bb and the standby core network 2
  • the standby core network element 2 may be located on the public cloud CC.
  • the main core network can be distributed and deployed on multiple private clouds.
  • different main core network elements in the main core network may be located on different private clouds.
  • the main core network element of the control plane and the main core network element of the data plane may be located on different private clouds.
  • different main core network element of the control plane may be located on different private clouds.
  • different main core network elements on the data plane can be located on different private clouds.
  • the main core network is located in the first public cloud, and at least one standby core network is located in the second public cloud.
  • the second public cloud is different from the first public cloud.
  • the main core network and at least one standby core network can be deployed on different public clouds.
  • the main core network may be deployed on multiple first public clouds in a distributed manner.
  • different main core network elements in the main core network may be located on different first public clouds.
  • the main core network element of the control plane and the main core network element of the data plane may be located on different first public clouds.
  • the network elements of different main core networks on the control plane may be located on different first public clouds.
  • different primary core network elements on the data plane can be located on different first public clouds.
  • the standby core network can be deployed on multiple second public clouds.
  • different standby core network elements in the standby core network may be located on different second public clouds.
  • the backup core network element on the control plane and the backup core network element on the data plane may be located on different second public clouds.
  • different standby core network network elements on the control plane may be located on different second public clouds.
  • different backup core network elements on the data plane can be located on different second public clouds.
  • the main core network is located in the first private cloud, and at least one standby core network is located in the second private cloud.
  • the second private cloud is different from the first private cloud.
  • the main core network and at least one standby core network can be deployed on different private clouds.
  • the main core network may be distributed and deployed on multiple first private clouds.
  • different main core network elements in the main core network may be located on different first private clouds.
  • the main core network element of the control plane and the main core network element of the data plane may be located on different first private clouds.
  • the network elements of different main core networks on the control plane may be located on different first private clouds.
  • different primary core network elements on the data plane may be located on different first private clouds.
  • the standby core network can be distributed and deployed on multiple second private clouds.
  • different standby core network elements in the standby core network may be located on different second private clouds.
  • the backup core network element on the control plane and the backup core network element on the data plane may be located on different second private clouds.
  • different standby core network nodes of the control plane may be located on different second private clouds.
  • different standby core network nodes on the data plane may be located on different second private clouds.
  • a layered model of the core network's network capabilities is provided.
  • the core network services are converted to software as a service (SaaS)
  • the reliability of the core network services can be enhanced. It can realize the diversity and dynamics of the core network service provision forms, so that the main body of the core network service can perform various combinations as needed, and is not limited to the reliability guarantee provided by the public cloud.
  • SaaS software as a service
  • the deployment methods of the primary core network element and the standby core network element may include the following (1) to (2):
  • the functions of the standby core network are the same as those of the main core network.
  • the backup core network element included in the standby core network and the main core network element included in the main core network can be functionally symmetrically deployed.
  • the functions of the standby core network can be in one-to-one correspondence with the functions of the primary core network.
  • the main core network may include an MME network element, an HSS network element, an SGW network element, a PGW network element, and a PCRF network element.
  • the standby core network may also include an MME network element, an HSS network element, an SGW network element, a PGW network element, and a PCRF network element.
  • the functions of the standby core network do not include at least one of an authentication function and a charging function.
  • the functional network elements included in the standby core network can be deployed asymmetrically to the functional network elements of the main core network.
  • the functions of the standby core network can be deployed on demand. For example, deploying the standby core network elements only for basic communication functions without deploying authentication
  • the network functions related to the rights function and the charging function are not included in the standby core network.
  • the main core network may include an MME network element, an HSS network element, an SGW network element, a PGW network element, and a PCRF network element.
  • the standby core network may not include HSS network elements and PCRF network elements, but include MME network elements, SGW network elements, and PGW network elements.
  • the standby MME network element can close the Purge (clear) process to avoid the timeout, the MME network element initiates the UE separation process, thereby avoiding carrying a globally unique temporary UE identity The attached user is authenticated again.
  • the standby MME network element may be configured with the same MME identity as the primary MME network element, and hide the updated information of the MME, thereby preventing the terminal from re-authenticating to access the network.
  • core network services may not be available to the terminals of these users.
  • the standby PGW network element may be configured to not use the PCRF function, and the standby PGW network element may establish a bearer by using a local configuration policy for charging.
  • the terminal can be a mobile phone or other device with 3G or 4G communication capabilities.
  • the terminal may be provided as a user equipment (user equipment) in the mobile communication technology.
  • the access network may be an access network in any type of mobile communication network.
  • the access network may be an evolved UMTS terrestrial radio access network (E-UTRAN) network in the 4G network, including the following key network elements: evolved node B (evolved node B) , Referred to as: eNodeB).
  • E-UTRAN evolved UMTS terrestrial radio access network
  • the access network may also be an access network in a 5G network or an access network in a 3G network.
  • the type of the access network is not limited.
  • FIG. 8 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • the computer device may be provided as a coordination node in the embodiment of the present application.
  • the computer device 800 may have a relatively large difference due to different configurations or performances, and may include one or more processors (central processing units) 801 and one or more memories 802.
  • the memory 802 stores therein At least one instruction, the at least one instruction is loaded and executed by the processor 801 to implement the data backup method provided by each method embodiment described below.
  • the computer device may also have components such as a wired or wireless network interface and an input-output interface for input and output, and the computer device may further include other components for implementing device functions, which are not described herein.
  • a computer-readable storage medium such as a memory including instructions, which can be executed by a processor in a computer device to complete the data backup method in the following embodiments.
  • the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc (read-only memory) (abbreviated as: CD-ROM), magnetic tape, floppy disks, and optical data storage devices.
  • FIG. 9 is a flowchart of a data backup method provided by an embodiment of the present application. The method is executed by a coordination node. The method includes the following steps:
  • the coordination node receives the identity of the base station.
  • Attach refers to the process of the terminal registering with the core network. Specifically, when the terminal needs to attach, the terminal may generate an attach request and send the attach request to the base station. The base station can receive the terminal's attach request and send the terminal's attach request to the core network element. The core network element can receive the terminal's attach request and register the terminal with the core network. In an exemplary scenario, in an LTE project, a terminal may be attached to an EPC network through an eNodeB.
  • the identity of the base station received by the coordination node may come from the primary MME network element.
  • the master MME network element may obtain the identity of the base station and send the identity of the base station to the coordination node.
  • the coordinating node can receive the identity of the base station.
  • the coordination node may also receive the identity of the base station sent by other network element equipment other than the primary MME network element.
  • the base station may actively send the identity of the base station to the coordination node, and the coordination node may receive the identity of the base station.
  • the functional network element may be specifically set according to requirements, which is not limited in this embodiment.
  • the manner in which the coordination node receives the base station identifier sent by the network element of the main core network may include any one or more of the following manners 1 to 2:
  • Method 1 The coordination node receives the attachment notification of the network element of the main core network.
  • the attach notification is used to notify the coordinating node that the terminal is attached to the network. Attach notification can be triggered by an event that the terminal successfully attaches.
  • the attach notification can carry the terminal identity and the base station identity that the terminal accesses.
  • the identifier of the base station is used to uniquely determine the corresponding base station.
  • the identification of the base station may be an identification number (Identity, ID for short), a number, and the like.
  • the attachment notification may carry the identity of the eNodeB.
  • the network element of the main core network may obtain the identity of the base station, generate an attachment notification according to the identity of the base station, and send the attachment notification to the coordinating node.
  • the coordinating node receives the attach notification of the network element of the main core network, the coordinating node can parse the attach notification and obtain the identity of the base station.
  • the master MME network element may generate an attachment notification, and the master MME network element may send an attachment notification to the coordinating node.
  • the coordinating node receives the attach notification of the main MME, the coordinating node can parse the attach notification and obtain the eNodeB identity carried in the attach notification.
  • Method 2 The coordination node receives the address request of the network element of the main core network.
  • the address request is used to request the address of the target standby core network element.
  • the address request carries the identity of the base station.
  • the address request may carry the identity of the eNodeB.
  • the network element of the main core network when the terminal is attached through the base station, can obtain the identity of the base station, and can generate an address request based on the identity of the base station, and send an address request to the coordinating node.
  • the coordinating node receives the address request of the network element of the main core network, the coordinating node can parse the address request and obtain the identity of the base station carried in the address request.
  • the master MME network element may generate an address request and send the address request to the coordinating node.
  • the address request may be used to request the address of the standby MME network element.
  • the coordinating node receives the address request of the primary MME, the coordinating node can parse the address request to obtain the identity of the eNodeB and the type of the primary network element carried in the address request.
  • the master HSS network element may generate an address request, and the master HSS network element may send an address request to the coordinating node.
  • the address request may be used to request the address of the standby HSS network element.
  • the coordinating node can receive the address request of the primary HSS network element.
  • the coordinating node can parse the address request to obtain the identity of the eNodeB and the main network element type carried in the address request.
  • the master core network element may also send the identity of the terminal to the coordinating node, and the coordinating node may receive the identity of the terminal.
  • the coordination node may receive an attachment notification or an address request, and the attachment notification or address request carries the identity of the base station and the identity of the terminal.
  • the coordination node may record the identity of the base station accessed by the terminal by maintaining record information. Specifically, the coordination node may store record information. When the coordination node receives the identity of the base station and the identity of the terminal, the coordination node may write the correspondence between the identity of the terminal and the identity of the base station to the record information.
  • the record information is used to record the base station accessed by each terminal.
  • the record information may include an identifier of at least one terminal and an identifier of at least one base station.
  • the manner in which the network element of the primary core network obtains the identity of the base station may include any one or more of the following (1) to (2):
  • the network element of the main core network can parse the terminal data to obtain the base station identifier carried by the terminal data.
  • the terminal may send an attachment request to the network element of the main core network.
  • the terminal parses the attachment request to obtain the identity of the base station carried by the attachment request.
  • the terminal may send an attachment request to the primary MME network element through the eNodeB.
  • the primary MME network element receives the terminal attachment request through the eNodeB
  • the primary MME network element parses the attachment request and obtains the identity of the eNodeB carried by the attachment request.
  • the network element of the main core network can receive the identity of the base station sent by other network elements of the main core network.
  • the master MME network element may send the identity of the eNodeB to the master HSS network element, and the master HSS network element may receive the identity of the eNodeB of the master MME network element.
  • the terminal may send an attach request to the primary MME network element.
  • the primary MME network element may send an authentication request to the primary HSS network element.
  • the primary HSS network element receives the authentication request of the primary MME network element and can generate an authentication response, and the primary HSS network element can send an authentication response to the primary MME network element.
  • the primary MME network element may send registration information to the primary HSS network element, where the registration information includes the identity of the eNodeB and the identity of the terminal.
  • the primary HSS network element can receive the registration information, thereby obtaining the identity of the eNodeB accessed by the terminal from the registration information.
  • the coordination node determines a target standby core network corresponding to the base station from at least one standby core network according to the identifier of the base station.
  • the address of the standby core network element is used to access the standby core network element.
  • the address of the network element of the standby core network may include at least one of an Internet Protocol (IP) address and a port number of the network element of the standby core network.
  • IP Internet Protocol
  • the address of the network element of the standby core network may be stored in the coordination node in advance.
  • the at least one standby core network may correspond to at least one base station.
  • the network element in each standby core network can be used to back up and store data of the terminal accessed through the corresponding base station.
  • the correspondence between the standby core network and the base station may be stored in the coordination node in advance.
  • the correspondence between the standby core network and the base station can be shown in Table 1 below.
  • the standby core network 1 can be used to back up and store data of all terminals accessed through the base station a. When any terminal accesses the core through the base station, After the network connection a is attached, each network element in the main core network stores the data of the terminal, and each network element in the standby core network 1 backs up the data of the terminal.
  • the standby core network 2 can be used to back up and store data of all terminals accessed through the base station b, and details are not described herein.
  • Standby core network Base station Standby core network 1 Base station a Standby core network 2 Base station b Standby core network 3 Base station c
  • the target standby core network element refers to at least one standby core network element corresponding to the base station accessed by the terminal in at least one standby core network.
  • the target standby core network element is used to back up and store the data of the terminal.
  • the target standby core network element of the terminal is the standby
  • the network elements included in the core network 1 are backed up and stored by the backup core network elements.
  • the coordination node may query the correspondence between the identity of the base station and the address of the standby core network element according to the identity of the base station to obtain the address of each target standby core network element corresponding to the identity of the base station.
  • the correspondence between the identity of the base station and the address of the network element of the standby core network may include the identity of at least one base station and the address of the network element of the standby core network.
  • the correspondence between the identifier of the base station and the address of the backup core network element can be stored in the coordination node in advance, so that the coordination node can read the correspondence between the identifier of the base station and the address of the backup core network element in advance.
  • the correspondence between the identifier of the base station and the address of the network element of the standby core network may be shown in Table 2 below:
  • the correspondence between the identity of the base station and the standby core network and network elements of the standby core network may be configured according to requirements.
  • the coordination node may obtain a configuration instruction, and according to the configuration instruction, configure a correspondence between an identifier of the base station and an address of the standby core network and the network element of the standby core network.
  • the configuration instruction may be triggered by an input operation on the coordination node, or may be issued by the same operation and maintenance management platform. For example, referring to FIG. 10, FIG. 11, FIG. 12, and FIG. 13, the correspondence relationship between the eNodeB and the standby core network may be configured on the coordination node in advance.
  • the correspondence between the identifier of the base station and the address of the network element of the standby core network may include a first mapping relationship and a second mapping relationship.
  • the first mapping relationship is a mapping relationship between an identifier of a base station and an identifier of a backup core network element.
  • the first mapping relationship includes an identifier of at least one base station and an identifier of a corresponding at least one backup core network element.
  • the second mapping relationship is a mapping relationship between the identity of the standby core network element and the address of the standby core network element.
  • the second mapping relationship includes the identity of at least one standby core network element and the corresponding at least one standby core network. The address of the network element.
  • the coordination node may query the first mapping relationship according to the identity of the base station, and obtain the identity of the target standby core network element corresponding to the identity of the base station in the first mapping relationship.
  • the second mapping relationship may be queried according to the identity of the target standby core network element, to obtain the address of the target standby core network element corresponding to the identity of the target standby core network element in the second mapping relationship.
  • each standby core network may correspond to a geographical area.
  • Each standby core network element in the standby core network may be used to back up and store data of a terminal accessed through a base station in a corresponding geographic area.
  • the geographical areas corresponding to different standby core networks may be different.
  • a main core network may be deployed for a provincial capital city.
  • the backup core network 2 is used to back up and store the data of terminals accessing the core network through all base stations within the range of county 2. It is used to backup and store the data of terminals that access the core network through all base stations in county 3.
  • the main core network can store data for all terminals in the entire provincial capital city. For each terminal located in county 1, these terminals will be attached through the base station of county 1.
  • the target standby core network of these terminals is the standby core network 1 corresponding to the base station of county 1. Data for backup storage.
  • terminal data located in counties 2 and 3 will be backed up to the network elements in the corresponding standby core network 2 and standby core network 3, respectively.
  • different backup core network elements provide data backup services for terminals that access the core network from different geographical areas.
  • the function of offloading terminal data according to geographical areas can be implemented, and The data of the terminal is shared among network elements of different standby core networks.
  • the network element of the primary core network may request the address of the target backup core network element from the coordination node through the identity of the terminal.
  • the network element of the main core network may send an address request to the coordinating node, and the address request carries the identifier of the terminal and the network element type of the main core network.
  • the coordinating node can parse the address request to obtain the identity of the terminal and the type of the main core network element carried in the address request.
  • the coordination node may query the record information according to the terminal identifier and the type of the network element, determine the address of the target backup core network element corresponding to the base station from the address of at least one backup core network element, and send the target to the primary core network element The address of the standby core network element.
  • the network element of the main core network may generate an address request carrying the identity of the terminal and send the address request to the coordinating node.
  • the coordination node can parse the address request and obtain the identity of the terminal carried in the address request.
  • the coordinating node may query the record information according to the identity of the terminal, and obtain the identity of the eNodeB network element corresponding to the identity of the terminal.
  • the coordinating node may determine the address of the target standby core network element corresponding to the eNodeB network element from the addresses of at least one standby core network element according to the identifier of the eNodeB.
  • the coordination node may send the address of the target standby core network element to the primary core network element.
  • the core network element may be an MME network element or an HSS network element.
  • the coordination node sends the data of the terminal stored in the at least one primary core network element to the at least one target standby core network element according to the address of at least one target standby core network element in the target standby core network.
  • the coordinating node may, according to the address of the target standby core network element and the function type of the target standby core network element, compare the function type with the function type The data of the terminal corresponding to the function type stored in the same primary core network element is sent to the target standby core network element.
  • the function type of the network element may include at least one of mobility management, access control, legality monitoring, packet depth inspection, charging, bearer, IP address allocation, paging, handover, and roaming.
  • network elements may be divided into at least one of an MME network element, an HSS network element, and a PCRF network element according to different types of functions.
  • the data of the terminal may include at least one of context data, subscription data, and policy configuration data, where the context data corresponds to the MME network element, the contract data corresponds to the HSS network element, and the policy configuration data corresponds to the PCRF network element.
  • the network element may have other names, the network element may also have other function types, and the data of the terminal corresponding to the function type of the network element may be other data.
  • the specific function type of the network element, the name of the network element, and the data of the terminal are not limited.
  • the data of the terminal corresponding to the function type stored by the main core network element with the same function type as the function type is sent
  • the step of providing the target standby core network element may include any one or more of the following (1) to (3):
  • the context data of the terminal stored in the primary MME network element is synchronized to the target MME network element.
  • step 903 may include a combination of any one or more of the following manners 1 to 2.
  • Method 1 The coordination node sends the address of the target standby core network element to the primary core network element.
  • the primary core network element may send terminal data to the target standby core network element according to the address of the target standby core network element.
  • the main core network element can actively push the data of the terminal to the target standby core network element through a data push method.
  • the primary core network element can establish a network connection with the target standby core network element, and the primary core network element can send data of the terminal to the target standby core network element through the network connection.
  • the network connection between the primary core network element and the target standby core network element includes, but is not limited to, Internet protocol security (ipsec) tunnels, virtual private networks (VPN), etc. This embodiment does not limit this.
  • the coordination node may send the address of the target standby MME network element to the primary MME network element.
  • the primary MME network element may send the context data of the terminal to the target standby MME network element.
  • the coordination node may send the address of the target standby HSS network element to the primary HSS network element.
  • the primary HSS network element receives the address of the target standby HSS network element, the primary HSS The network element may send the UE's subscription information to the target standby HSS network element.
  • the coordination node sends a terminal data request to the main core network element.
  • the network element of the main core network receives the terminal data request from the coordination node
  • the network element of the main core network sends the data of the terminal to the coordination node.
  • the coordination node receives the data of the terminal of the network element of the primary core network, and sends the data of the terminal to the network element of the target backup core network.
  • the coordination node can actively push the data of the terminal to the target standby core network element through a data push method.
  • the terminal data request may carry the identity of the terminal.
  • the terminal data request is used to request data from the terminal.
  • the data of the terminal may include at least one of related data such as context data of the terminal and subscription information of the terminal, which is not limited in this embodiment.
  • the terminal data request may include at least one of related requests such as a context data request and a subscription information request.
  • the context data request is used to request context data of the terminal.
  • the contract information request is used to request contract information of the terminal.
  • the coordination node can establish a network connection with the target standby core network element, and the coordination node can send terminal data to the target standby core network element through the network connection.
  • the method for coordinating the network connection between the node and the target backup core network element includes, but is not limited to, an ipsec tunnel, a VPN, and the like, which is not limited in this embodiment.
  • the coordination node may send a context data request to the primary MME network element.
  • the master MME network element may send the context data of the terminal to the coordination node.
  • the coordination node may send the context data of the terminal to the target standby MME network element.
  • the coordination node may send a subscription information request to the primary HSS network element.
  • the primary HSS network element may send the subscription information of the terminal to the coordination node.
  • the coordination node may send the subscription information of the terminal to the target standby HSS network element.
  • the coordination node may provide an authentication function, and the coordination node may authenticate the backup core network element, thereby preventing configuration information from being tampered with, and ensuring that the backup core network element is a trusted network element.
  • the coordination node may perform identity verification on the standby HSS network element in advance.
  • the target standby HSS network element is a legitimate HSS network element
  • the coordinating node will send the subscription information of the terminal stored by the primary HSS network element to the target standby HSS network element.
  • the coordinating node may refuse to send the subscription information of the terminal stored by the primary HSS network element to the target standby HSS network element.
  • the network element of the main core network may store the data of the terminal in advance.
  • the primary HSS network element may store subscription information of the terminal in advance.
  • the network element of the main core network may generate data of the terminal.
  • the primary MME network element may allocate terminal communication resources to generate terminal context data.
  • the number of network elements of the target standby core network may be one or more.
  • the primary MME network element may be configured with multiple target standby MME network elements
  • the primary HSS network element may be configured with multiple target standby HSS network elements.
  • the main core network element may select any target backup core network element from the multiple target backup core network elements and synchronize the data of the stored terminal to the target backup.
  • the target standby core network element can receive data from the terminal sent by the primary core network element, and synchronize the terminal data to other target standby core network elements.
  • the data of the stored terminal may also be synchronized to the multiple target standby core network network elements by the primary core network network element at the same time.
  • each standby core network element by deploying a corresponding standby core network element for each base station, each standby core network element backs up and stores data of a terminal accessed by the corresponding base station, thereby storing the primary core network element.
  • the stored data of all terminals are backed up to the backup core network elements corresponding to different base stations in a distributed manner, which can reduce the requirements for the storage capacity and specifications of a single backup core network element.
  • the standby core network element does not need to maintain real-time synchronization with the primary core network element, which reduces the processing overhead and operating cost of the standby core network element.
  • data disaster recovery can be achieved by backing up data on storage terminals of each standby core network.
  • the standby core network can take over the services of the main core network, which can improve the reliability and security of the core network.
  • the main core network access is normal, the operating cost of the standby core network is lower and the system performance is better.
  • the coordination node may include at least one of a first coordination node and a second coordination node, and the second coordination node is configured to execute the foregoing method embodiment to synchronize data of the terminal stored by the primary core network element to the standby core.
  • the first coordination node is configured to route and route the request message of the terminal. The following describes the process of routing the first coordination node through the embodiment of FIG. 14 in detail.
  • FIG. 14 is a flowchart of a service processing method according to an embodiment of the present application. The method may be applied to a scenario where a service is switched when a main service is in an access failure state.
  • the interaction body of the method includes a coordination node, a terminal, a base station, a primary core network element and a standby core network element. The method includes the following steps:
  • the first coordination node obtains the access status of the network elements of the main core network.
  • the access status is used to indicate whether the network elements of the main core network can access normally.
  • the access status may include at least one of an access normal status and an access failure status.
  • the normal access status is used to indicate that the network elements of the main core network can access normally.
  • the access failure status is used to indicate that the network elements of the main core network cannot access normally.
  • the first coordinating node and the second coordinating node may complete a process of detecting an access state of the network element of the main core network.
  • the second coordination node may be located in the same wireless network as the main core network element, and the access state of the second coordination node may reflect the access state of the main core network element. Therefore, the first coordination node can detect the access status of the second coordination node, and use the access status of the second coordination node as the access status of the primary core network element.
  • the detection process of the access status of the network elements of the main core network may include the following steps 1 to 2:
  • Step 1 The first coordination node sends a fault detection message to the second coordination node, and the fault detection message is used to detect the access status of the second coordination node.
  • Step 2 The first coordination node determines the access status of the primary core network element according to the response of the second coordination node.
  • the second coordination node may receive a fault detection message. After the second coordination node receives the fault detection message, it may generate a response message and send a response message to the first coordination node, where the response message is used to indicate that the second coordination node has received the fault detection message.
  • the first coordination node receives the response message from the second coordination node, it can be determined that the second coordination node is in a normal access state, and it is determined that the network element of the main core network is in a normal access state. If the second coordinating node is in an access failure state, the second coordinating node will not receive a failure detection message, and will not send a response message to the first coordinating node. Then, when the first coordination node does not receive a response message from the second coordination node, it may be determined that the second coordination node is in an access failure state, and it is determined that the primary core network element is in an access failure state.
  • fault detection can also be implemented by using open source distributed application coordination services such as zooKeeper.
  • fault detection can also be implemented using any master-slave synchronous network protocol.
  • the fault detection method in this embodiment is not Be limited.
  • the above step 1 and the above step 2 may provide a process for the first coordination node and the second coordination node to perform health checks with each other.
  • the first coordination node may The state of the second coordination node is taken as the health state of the network element of the main core network, so that the health state of the network element of the main core network is detected.
  • the first coordination node receives a request message from the terminal.
  • the request message is used to request any service in the core network.
  • the request message may include an attach request, a network access request, a location update request, and the like.
  • the first coordination node routes the request message to the target backup core network element corresponding to the base station accessed by the terminal.
  • the first coordination node may determine the destination of the request message according to the access status of the primary core network element obtained in step 1401. If the access state of the network element of the main core network is an access failure state, the first coordination node may route the request message to the network element of the target backup core network. If the access state of the network element of the primary core network is the normal access state, the first coordination node may route the request message to the network element of the standby core network.
  • the method steps in the embodiment of FIG. 9 described above may be executed to synchronize the terminal data stored in the network element of the primary core network to the network element of the target standby core network.
  • the first coordination node may send a request message of the terminal to the primary MME network element, thereby performing mobility of the terminal through the primary MME network element. management.
  • the first coordinating node may enable a traffic diversion function and route the request message of the terminal to the target standby MME network element, thereby performing mobility management on the terminal through the target standby MME network element.
  • the first coordinating node may direct the request message of the terminal to the target standby PGW network element, thereby performing session management on the terminal through the target standby PGW network element.
  • the number of target backup core network element corresponding to one main core network element may be one or more. If the number of target standby core network network elements is multiple, optionally, the first coordination node may route the request message to the target standby core with the highest routing priority according to the routing priority of each target standby core network element. Network element. The routing priority of each target standby core network element can be set according to service requirements.
  • the target standby core network element when the primary core network element is in an access failure state, if the target standby core network element stores the terminal's subscription information and the terminal's context data, and the communication link required by the corresponding terminal's request message And the communication bearer may not be established yet, the target standby core network element may send a response message to the terminal according to the processing result, and the terminal may choose to re-access the network.
  • the terminal may re-initiate an attach request according to a response message of a request message sent last time, thereby attaching again.
  • the terminal when the network element of the primary core network is in an access failure state, the terminal may move to another area and access the network through the base station in the other area. Due to the correspondence between the base station and the network element of the standby core network , There will be a situation where the target standby core network element does not store the terminal data.
  • the target standby core network element may query whether the terminal has stored the terminal information. If the local terminal has stored the information of the terminal, the request message of the terminal is processed.
  • the target standby core network element can send a terminal information request to other standby core network elements to obtain terminal information from other standby core network elements to complete subsequent service processing, and Through the interaction between the target standby core network element and other standby core network elements, terminal data on other standby core network elements is deleted to eliminate terminal access conflicts.
  • the standby core network element 1 may query whether the terminal stores data of the terminal. If the backup core network element 1 has stored the terminal data, as shown in FIG. 16, the standby core network element 1 can process the request message of the terminal. If the standby core network element 1 has not stored the terminal data, as shown in FIG. 17, the standby core network element 1 broadcasts the terminal data request to other standby core network elements, thereby obtaining the terminal data from the standby core network 2 network element 1. To complete subsequent business processing.
  • the first coordinating node may enable a diversion function to divert the request message of the terminal to the standby core network element.
  • the main core network element access fails, the reliability and availability of core network services can be improved, the impact caused by the failure of the network where the main core network element is located, and the user experience is improved.
  • FIG. 18 is a flowchart of a service processing method according to an embodiment of the present application. The method may be applied to a scenario where a service switching is performed when a main core network element switches from an access failure state to a normal access state.
  • the interaction body includes a first coordination node, a terminal, a base station, a primary core network element and a standby core network element. The method includes the following steps:
  • Step 1 When the first coordination node receives a request message from the terminal, the first coordination node determines whether the access failure of the network element of the main core network is recovered.
  • the first coordination node may obtain the access status of the main core network element, and determine whether the access failure of the main core network element is recovered according to the access status of the main core network element.
  • the access state of the network element of the main core network is an access failure state
  • the first coordinating node may perform the following step two.
  • the access state of the network element of the main core network is the normal access state
  • the first coordinating node may perform step three below.
  • step 1401 The process of obtaining the access status of the network elements of the main core network is the same as step 1401 in the foregoing embodiment of FIG. 14, and details are not described herein.
  • Step 2 When the access state of the primary core network element is an access failure state, the first coordination node routes the request message to the target standby core network element.
  • the access state of the main core network element is an access failure state, it can be determined that the access fault of the main core network element has not recovered, and the main core network element cannot temporarily process the terminal's services, then the first coordination node can switch the terminal The request message is routed to a healthy standby core network element, so that the terminal's request message is processed by the healthy standby core network element.
  • Step 3 When the access state of the network element of the primary core network is the normal access state, the first coordination node queries the communication resources of the terminal in the network element of the target backup core network according to the identity of the terminal.
  • the communication resources of the terminal may include, but are not limited to, an evolved packet system (evolved packet system, referred to as EPS) bearer and a tunnel endpoint identifier (tunnel endpoint ID, referred to as TEID).
  • EPS evolved packet system
  • TEID tunnel endpoint identifier
  • the first coordination node may determine that the access failure of the network element of the main core network has been recovered.
  • the first coordination node may generate a query request according to the identity of the terminal, and send a query request to the target standby core network element, where the query request carries the identity of the terminal.
  • the target backup core network element receives the query request from the first coordination node, it can query whether the backup core network element stores the communication resources of the terminal and send the query result to the first coordination node.
  • the first coordination node may determine whether the communication resource of the terminal is stored in the target standby core network element according to a query result of the target standby core network element. For example, if the query result of the target standby core network element is empty, it is determined that the communication resource of the terminal is not stored in the target standby core network element or the terminal has been separated from the standby core network or the terminal has moved to a location.
  • the first coordination node performs the following steps 4 and 5; if the target backup core network element does not store the communication resources of the terminal, the first coordination node performs The following steps six and seven.
  • Step 4 The first coordination node sends a request message of the terminal to the target backup core network element.
  • the first coordination node may continue to forward the request message of the terminal to the target standby core network element so that The target standby core network element continues to process the request packets of the terminal, so as to achieve the effect of gradually switching from the standby core network to the main core network to provide services to the terminal without affecting the terminal's current network connectivity.
  • Step 5 The target backup core network element processes the request message of the terminal.
  • Step 6 The first coordination node sends the request message to the network element of the main core network.
  • the first coordination node may directly send the request message of the terminal to the network element of the main core network, so that the request message of the terminal is processed by the network element of the main core network.
  • Step 7 The network element of the main core network processes the request message of the terminal.
  • Step 8 The terminal responds according to the request message and performs subsequent service processing.
  • FIG. 19 is a flowchart of a service processing method according to an embodiment of the present application.
  • the method may be applied to a scenario where a service switching is performed when a main core network element switches from an access failure state to a normal access state.
  • the interaction body includes a first coordination node, a terminal, a base station, a primary core network element and a standby core network element. The method includes the following steps:
  • Step 1 When the first coordination node receives a request message from the terminal, the first coordination node determines whether the access failure of the network element of the main core network is recovered.
  • the first coordinating node may perform the following step two.
  • the access state of the network element of the main core network is the normal access state
  • the first coordinating node may perform step 4 below.
  • Step 2 When the access state of the network element of the primary core network is an access failure state, the first coordination node sends a request message for the terminal to the network element of the target backup core network.
  • Step 3 The target backup core network element receives the request message from the terminal, and processes the request message from the terminal.
  • Step 4 When the access state of the network element of the main core network is the normal access state, the first coordination node sends a request message of the terminal to the network element of the main core network.
  • the first coordinating node can turn off the routing function and directly forward the request message of the terminal to the network element of the main core network, so as to pass the main network element Request message for processing.
  • Step 5 The network element of the main core network processes the request message of the terminal.
  • Step 6 The terminal responds according to the request message and performs subsequent service processing.
  • FIG. 20 is a schematic structural diagram of a data backup device according to an embodiment of the present application. As shown in FIG. 20, the device includes:
  • a receiving module 2001 configured to perform the foregoing step 901;
  • a determining module 2002 configured to execute the foregoing step 902;
  • the sending module 2003 is configured to perform the foregoing step 903.
  • the determining module 2002 is configured to query the correspondence between the identity of the base station network element and the address of the standby core network element according to the identity of the base station network element to obtain the target corresponding to the identity of the base station network element.
  • the address of the standby core network element is configured to query the correspondence between the identity of the base station network element and the address of the standby core network element according to the identity of the base station network element to obtain the target corresponding to the identity of the base station network element.
  • the address of the standby core network element is configured to query the correspondence between the identity of the base station network element and the address of the standby core network element according to the identity of the base station network element to obtain the target corresponding to the identity of the base station network element.
  • the sending module 2003 is configured to execute any one or a combination of multiple manners in the first to the second manners in step 903.
  • the receiving module 2001 is configured to execute any one or a combination of multiple manners in the first to the second manners in step 901.
  • the "device” in the above embodiment may be a software-implemented virtualization device, and each module may specifically be a software module that executes a corresponding function in the software, that is, the "module” may be a group of computer programs
  • the computer program may be a source program or a target program, and the computer program may be implemented by any programming language.
  • the coordination node can implement the data backup function based on the processor and memory hardware, that is, the processor can run the software code stored in the memory to execute the corresponding software to implement the data backup.
  • the second point that needs to be explained is that when the data backup device provided in the foregoing embodiment backs up data, it only uses the division of the above functional modules as an example. In practical applications, the above functions can be allocated by different functional modules as required. Finished, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the data backup device and the data backup method embodiments provided by the foregoing embodiments belong to the same concept. For specific implementation processes, refer to the method embodiments, and details are not described herein again.
  • the present application further provides a computer program product containing instructions, which when run on a computer device, enables the computer device to implement the operations performed by the data backup method in the foregoing embodiment.
  • the present application further provides a chip that includes a processor and / or program instructions.
  • the chip When the chip is running, the operations performed by the data backup method in the foregoing embodiment are implemented.
  • the computer program product includes one or more computer program instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program instructions may be transmitted from a website node, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integrations.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD), or a semiconductor medium (for example, a solid state hard disk), or the like.
  • multiple means two or more than two, for example, multiple data packets refer to two or more data packets.
  • first and second in this application are used to distinguish the same or similar items with basically the same function and function. Those skilled in the art can understand that the words “first” and “second” are not correct in quantity. And execution order.
  • the program may be stored in a computer-readable storage medium.
  • the storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte au domaine technique des communications, et concerne un procédé et un dispositif de sauvegarde de données et un système de communication. Selon la présente invention, un cœur de réseau de secours correspondant est déployé pour chaque station de base ; après qu'un terminal a été rattaché au moyen de la station de base, un nœud de coordination synchronise des données du terminal qui sont stockées dans un élément de cœur de réseau primaire conformément à une correspondance entre la station de base et le cœur de réseau de secours. Après que le terminal a été rattaché, un élément de cœur de réseau de secours a seulement besoin de stocker les données du terminal sans nécessiter une synchronisation en temps réel avec l'élément de cœur de réseau primaire, ce qui permet de réduire les coûts d'exploitation du cœur de réseau de secours. De plus, chaque élément de cœur de réseau de secours a seulement besoin de stocker les données d'un terminal qui sont accessibles auprès d'une station de base correspondante et n'a pas besoin de stocker les données de tous les terminaux, ce qui réduit les exigences de capacité de stockage pour l'élément de cœur de réseau de secours.
PCT/CN2019/103480 2018-09-25 2019-08-30 Procédé de déploiement multinuage de service en nuage basé sur un équipement de coordination WO2020063248A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811119939.4A CN110944029B (zh) 2018-09-25 2018-09-25 数据备份方法、装置及通信系统
CN201811119939.4 2018-09-25

Publications (1)

Publication Number Publication Date
WO2020063248A1 true WO2020063248A1 (fr) 2020-04-02

Family

ID=69905217

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/103480 WO2020063248A1 (fr) 2018-09-25 2019-08-30 Procédé de déploiement multinuage de service en nuage basé sur un équipement de coordination

Country Status (2)

Country Link
CN (1) CN110944029B (fr)
WO (1) WO2020063248A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101052212A (zh) * 2006-04-03 2007-10-10 华为技术有限公司 一种移动终端重新附着网络的方法
CN104081808A (zh) * 2012-01-24 2014-10-01 瑞典爱立信有限公司 Mme恢复
CN104581814A (zh) * 2013-10-11 2015-04-29 思科技术公司 网络环境中订户群组的策略应用
CN105556900A (zh) * 2015-01-30 2016-05-04 华为技术有限公司 一种业务容灾的方法和相关装置
US9608860B1 (en) * 2016-03-28 2017-03-28 Affirmed Networks Communications Technologies, Inc. Synchronized MME pool

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102083178B (zh) * 2010-09-29 2014-04-02 电信科学技术研究院 启动阶段指示发送及网关节点选择方法、系统和设备
US8774824B1 (en) * 2012-08-08 2014-07-08 Sprint Communications Company L.P. Alleviating and overriding throttled conditions in LTE

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101052212A (zh) * 2006-04-03 2007-10-10 华为技术有限公司 一种移动终端重新附着网络的方法
CN104081808A (zh) * 2012-01-24 2014-10-01 瑞典爱立信有限公司 Mme恢复
CN104581814A (zh) * 2013-10-11 2015-04-29 思科技术公司 网络环境中订户群组的策略应用
CN105556900A (zh) * 2015-01-30 2016-05-04 华为技术有限公司 一种业务容灾的方法和相关装置
US9608860B1 (en) * 2016-03-28 2017-03-28 Affirmed Networks Communications Technologies, Inc. Synchronized MME pool

Also Published As

Publication number Publication date
CN110944029B (zh) 2021-12-17
CN110944029A (zh) 2020-03-31

Similar Documents

Publication Publication Date Title
US11968750B2 (en) System and method for session relocation at edge networks
US11166325B2 (en) Control plane based configuration for time sensitive networking
US20220345928A1 (en) Packet Duplication
US11606699B2 (en) Scalable evolved packet core
US9642077B2 (en) Node selection in virtual evolved packet core
WO2019158132A1 (fr) Procédé, appareil et système de transfert de réseau, ainsi que procédé et appareil de détermination de transfert
US8983475B2 (en) System and method for partner network sharing architecture
CN111771394A (zh) 用于ue上下文和pdu会话上下文管理的系统和方法
EP2497287A1 (fr) Sélection d'un n ud dans un réseau de communication
EP3150020B1 (fr) Rétablissement d'une session de communication défaillante
WO2012071695A1 (fr) Procédé, système et dispositif associé de traitement de panne de nœud
US20220322282A1 (en) Communication Method and Apparatus
JP7357682B2 (ja) サーバコンピュータ、アプリケーションを提供するための方法、移動通信ネットワーク、及びサーバコンピュータへのアクセスを提供するための方法
US10623996B2 (en) GTP tunnels for the support of anchorless backhaul
US10693733B2 (en) Horizontal scaling of fabric networks
US20230422052A1 (en) System and method for creating and managing private subnetworks of lte base stations
CN107948002B (zh) Ap接入控制方法和装置
WO2020063248A1 (fr) Procédé de déploiement multinuage de service en nuage basé sur un équipement de coordination
WO2008151554A1 (fr) Procédé, système et appareil pour déterminer la route dans un réseau à accès multiple par répartition en code
WO2018188447A1 (fr) Procédé et dispositif de configuration d'adresse ip
WO2024099244A1 (fr) Procédé et appareil de communication, dispositif associé, et support de stockage
WO2013044801A1 (fr) Procédé et dispositif de gestion de la migration d'un utilisateur

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19864326

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19864326

Country of ref document: EP

Kind code of ref document: A1