CN111465041A - Method and device for determining main MME in disaster recovery backup - Google Patents

Method and device for determining main MME in disaster recovery backup Download PDF

Info

Publication number
CN111465041A
CN111465041A CN201910052278.6A CN201910052278A CN111465041A CN 111465041 A CN111465041 A CN 111465041A CN 201910052278 A CN201910052278 A CN 201910052278A CN 111465041 A CN111465041 A CN 111465041A
Authority
CN
China
Prior art keywords
mme
connection request
main
response message
load weight
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
CN201910052278.6A
Other languages
Chinese (zh)
Inventor
李俊
徐宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Potevio Information Technology Co Ltd
Original Assignee
Potevio Information Technology Co Ltd
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 Potevio Information Technology Co Ltd filed Critical Potevio Information Technology Co Ltd
Priority to CN201910052278.6A priority Critical patent/CN111465041A/en
Publication of CN111465041A publication Critical patent/CN111465041A/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The embodiment of the invention provides a method and a device for determining a main MME in disaster recovery backup, wherein the method comprises the following steps: respectively sending an S1 connection request to each MME in the MME pool; if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight; and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME. The device performs the above method. According to the method and the device for determining the main MME in the disaster recovery backup, provided by the embodiment of the invention, the main MME can be reasonably determined in the disaster recovery backup by sequentially and respectively using the received S1 connection request response message, the configuration information of the main MME which is not stored in advance locally and the comparison load weight as the judgment conditions for determining the main MME.

Description

Method and device for determining main MME in disaster recovery backup
Technical Field
The embodiment of the invention relates to the technical field of disaster recovery backup, in particular to a method and a device for determining a main MME in disaster recovery backup.
Background
A Mobile Management Entity (MME) is a critical network element of a core network, and if the MME fails, the whole network is greatly affected, so performing disaster recovery backup on the MME is very important.
In the prior art, the MME may be disaster-tolerant backed up by using an MME POO L technology, that is, by selecting a main MME and a standby MME, when the main MME normally works, all the standby MMEs are in a standby state, and once the main MME is abnormal, one standby MME is selected to take over the abnormal main MME to work.
Therefore, how to avoid the above-mentioned drawbacks and reasonably determine the primary MME in the disaster recovery backup becomes a problem to be solved urgently.
Disclosure of Invention
To solve the problems in the prior art, embodiments of the present invention provide a method and an apparatus for determining a main MME in a disaster recovery backup.
The embodiment of the invention provides a method for determining a main MME in disaster recovery backup, which comprises the following steps:
respectively sending an S1 connection request to each MME in the MME pool;
if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight;
and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
An embodiment of the present invention provides an apparatus for determining a main MME in a disaster recovery backup, including:
a sending unit, configured to send an S1 connection request to each MME in the MME pool;
a comparing unit, configured to compare a value of each load weight if an S1 connection request response message returned by at least two MMEs for the S1 connection request is received within a preset time period, and the pre-stored configuration information that takes the MME containing the S1 connection request response message returned as a master MME is not locally detected; wherein, each S1 connection request response message carries a load weight;
and the determining unit is used for taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
An embodiment of the present invention provides an electronic device, including: the system comprises a processor, a memory and a bus, wherein the processor and the memory are communicated with each other through the bus;
the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform a method comprising:
respectively sending an S1 connection request to each MME in the MME pool;
if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight;
and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
An embodiment of the present invention provides a non-transitory computer-readable storage medium, including:
the non-transitory computer readable storage medium stores computer instructions that cause the computer to perform a method comprising:
respectively sending an S1 connection request to each MME in the MME pool;
if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight;
and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
According to the method and the device for determining the main MME in the disaster recovery backup, provided by the embodiment of the invention, the main MME can be reasonably determined in the disaster recovery backup by sequentially and respectively using the received S1 connection request response message, the configuration information of the main MME which is not stored in advance locally and the comparison load weight as the judgment conditions for determining the main MME.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a flowchart of an embodiment of a method for determining a main MME in disaster recovery backup according to the present invention;
FIG. 2 is a flowchart illustrating a method for determining a primary MME during disaster recovery backup according to another embodiment of the present invention;
fig. 3 is a schematic structural diagram of an apparatus for determining a main MME in disaster recovery backup according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a flowchart of an embodiment of a method for determining a main MME in disaster recovery backup according to the present invention, and as shown in fig. 1, the method for determining a main MME in disaster recovery backup according to the embodiment of the present invention includes the following steps:
s101: and respectively sending S1 connection requests to each MME in the MME pool.
Specifically, the apparatus sends S1 connection requests to each MME in the MME pool, respectively. The apparatus may be a base station, and the S1 connection request may be: an S1 setup request message for requesting to establish an S1 connection of the interface device.
S102: if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight.
Specifically, if the device receives an S1 connection request response message returned by at least two MMEs for the S1 connection request within a preset time period and does not locally detect the configuration information which is stored in advance and takes the MME containing the returned S1 connection request response message as the master MME, the device compares the values of the load weights; wherein, each S1 connection request response message carries a load weight. The preset time period can be set independently according to actual conditions, and can be selected to be 1 minute. The S1 connection request response message may be an S1 setup response message for responding to the request, and the load weight may be Relative mmecapability for indicating unused capacity in the MME. The configuration information of the main MME can be stored to the local base station in advance by writing in a flash mode. Examples are as follows: there are three MMEs in the MME pool, MME1, MME2 and MME3 respectively, if MME3 returns no S1 connection request response message to the base station within 1 minute, MME1 and MME2 both return S1 connection request response messages to the base station within 1 minute, and configuration information with MME1 or MME2 as the master MME is not stored locally at the base station, the value of the load weight of MME1, M1, and the value of the load weight of MME2, M2, are compared.
It should be noted that: if the base station is newly added, the configuration information of the main MME needs to be configured on the base station side when the main MME is accessed to the network.
S103: and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
Specifically, the apparatus sets the target MME corresponding to the larger target load weight in the comparison result as the master MME. Referring to the example above, if M1 > M2, the target MME is MME1 and MME1 is the master MME; if M2 > M1, the target MME is MME2 and MME2 is the master MME.
According to the method for determining the main MME in the disaster recovery backup, provided by the embodiment of the invention, the main MME can be reasonably determined in the disaster recovery backup by respectively using the received S1 connection request response message, the configuration information of the main MME which is not stored locally in advance and the comparison load weight as the judgment conditions for determining the main MME.
On the basis of the above embodiment, the method further includes:
if the number of the MME which is pre-stored and returns the S1 connection request response message is detected to be one locally, the MME is directly accessed to the network according to the configuration information.
Specifically, if the device locally detects that the number of MMEs which are stored in advance and return the S1 connection request response message is one, the device directly accesses the MME to the network according to the configuration information. Fig. 2 is a flowchart of another embodiment of the method for determining the main MME in the disaster recovery backup according to the present invention, as shown in fig. 2, referring to the above example, if the configuration information of the MME1 as the main MME is stored locally in advance in the base station, which can be implemented by storing the identifier of the MME1 in advance, the MME1 can be directly accessed to the network according to the configuration information. It should be noted that: if the number of MMEs to which the connection request response message of S1 is returned is plural, the values of the load weights of these MMEs may be further compared, and the target MME corresponding to the larger target load weight in the comparison result may be set as the master MME.
The method for determining the main MME in the disaster recovery backup provided by the embodiment of the invention can further reasonably determine the main MME in the disaster recovery backup.
On the basis of the above embodiment, the method further includes:
and if an S1 connection request response message returned by one MME aiming at the S1 connection request is received within a preset time period, directly determining the MME as the main MME.
Specifically, if an S1 connection request response message returned by one MME for the S1 connection request is received within a preset time period, the apparatus directly determines the one MME as the master MME. Referring to fig. 2, and the above example, if neither MME2 nor MME3 returned an S1 connection request response message to the base station within 1 minute, but only MME1 returned an S1 connection request response message to the base station within 1 minute, MME1 is directly determined as the master MME.
The method for determining the main MME in the disaster recovery backup provided by the embodiment of the invention can further reasonably determine the main MME in the disaster recovery backup.
On the basis of the foregoing embodiment, after the step of using the target MME corresponding to the larger target load weight in the comparison result as the master MME, the method further includes:
and generating configuration information of the main MME, and storing the configuration information to the local.
Specifically, the device generates configuration information of the master MME, and stores the configuration information locally. Referring to fig. 2, and the above example, if MME1 is determined to be the master MME, configuration information is generated that includes MME1 as the master MME and stored locally to the base station.
According to the method for determining the main MME in the disaster recovery backup, provided by the embodiment of the invention, the configuration information of the main MME is stored to the local, so that the main MME can be further quickly accessed to the network, and the main MME can be quickly determined by the configuration information of the main MME which is pre-stored locally.
On the basis of the foregoing embodiment, after the step of using the target MME corresponding to the larger target load weight in the comparison result as the master MME, the method further includes:
if the S1 connection interruption of the main MME is detected, the step of respectively sending S1 connection requests to each MME in an MME pool is continuously executed so as to re-determine the main MME.
Specifically, if the apparatus detects that the S1 connection of the master MME is interrupted, the apparatus continues to perform the step of sending the S1 connection request to each MME in the MME pool, respectively, to re-determine the master MME. Referring to the above example, if MME1 has been used as the master MME, at this time, the S1 connection of MME1 is interrupted, the base station sends an S1 connection request to MME1, MME2 and MME3, because the S1 connection of MME1 is interrupted, MME1 cannot return an S1 connection request response message to the base station within 1 minute, if both MME2 and MME3 return an S1 connection request response message to the base station within 1 minute, the step of step S102 is continuously executed, at this time, the step of the newly determined master MME may be no longer described with reference to the above description; if only the MME2 returned the S1 connection request response message to the base station within 1 minute, the above-described step of directly determining this MME (i.e., MME2) as the master MME is continued.
According to the method for determining the main MME in the disaster recovery backup, provided by the embodiment of the invention, when the main MME has a sudden failure, the main MME can be reasonably determined again in the disaster recovery backup in time.
On the basis of the above embodiment, the method further includes:
if the main MME is detected to recover the S1 connection, the re-determined main MME is still used as the current main MME.
Specifically, if the apparatus detects that the master MME has recovered the S1 connection, the apparatus still takes the newly determined master MME as the current master MME. Referring to the above example, if the redetermined primary MME is MME2, if the MME1S1 connection interruption, which was originally the primary MME, has been recovered, MME2 is still the current primary MME and MME1 may be the standby MME.
According to the method for determining the main MME in the disaster recovery backup, provided by the embodiment of the invention, even if the original main MME is restored to S1 connection, the re-determined main MME is still used as the current main MME, so that frequent switching of the main MME can be avoided in the disaster recovery backup.
The following briefly describes the handover procedure of the master MME and the standby MME:
assume that the main MME is MME1 at this time, and the other MME is denoted as MME 2. And the base station writes the main MME information into the flash.
When the MME1 is abnormal, the S1 connection between the base station and the MME1 is disconnected, at this time, if the MME2 is normally connected, the base station considers that the priority of the MME2 is greater than that of the MME1, the base station takes the MME2 as a main MME and writes the main MME into flash, and the base station accesses the UE which is accessed subsequently into the MME 2. At this time, if a new base station is accessed, the network management terminal needs to configure the MME2 as the main MME first, and then access is performed, and the new base station can access by using the MME2 as the main MME.
When the S1 connection of the MME1 returns to normal, the operation of changing the master MME is not performed at this time, and the UE to be subsequently accessed still accesses the MME 2.
In this scenario, when receiving the Overload Start message sent by the master MME, the base station may reject the UE access after that. And when receiving the Overload Stop message sent by the main MME, the base station recovers the UE access.
Fig. 3 is a schematic structural diagram of an embodiment of an apparatus for determining a main MME in disaster recovery backup according to the present invention, and as shown in fig. 3, an embodiment of the present invention provides an apparatus for determining a main MME in disaster recovery backup, including a sending unit 301, a comparing unit 302, and a determining unit 303, where:
the sending unit 301 is configured to send an S1 connection request to each MME in the MME pool; the comparing unit 302 is configured to compare the value of each load weight if an S1 connection request response message returned by at least two MMEs for the S1 connection request is received within a preset time period, and the pre-stored configuration information that takes the MME containing the S1 connection request response message returned as the master MME is not locally detected; wherein, each S1 connection request response message carries a load weight; the determining unit 303 is configured to use the target MME corresponding to the larger target load weight in the comparison result as the master MME.
Specifically, the sending unit 301 is configured to send an S1 connection request to each MME in the MME pool; the comparing unit 302 is configured to compare the value of each load weight if an S1 connection request response message returned by at least two MMEs for the S1 connection request is received within a preset time period, and the pre-stored configuration information that takes the MME containing the S1 connection request response message returned as the master MME is not locally detected; wherein, each S1 connection request response message carries a load weight; the determining unit 303 is configured to use the target MME corresponding to the larger target load weight in the comparison result as the master MME.
The device for determining the main MME in the disaster recovery backup provided by the embodiment of the invention can reasonably determine the main MME in the disaster recovery backup by respectively using the received S1 connection request response message, the configuration information of the main MME which is not stored locally in advance and the comparison load weight as the judgment conditions for determining the main MME.
The apparatus for determining a main MME in a disaster recovery backup according to the embodiment of the present invention may be specifically configured to execute the processing flows of the above method embodiments, and the functions of the apparatus are not described herein again, and refer to the detailed description of the method embodiments.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 4, the electronic device includes: a processor (processor)401, a memory (memory)402, and a bus 403;
the processor 401 and the memory 402 complete communication with each other through a bus 403;
the processor 401 is configured to call the program instructions in the memory 402 to execute the methods provided by the above-mentioned method embodiments, for example, including: respectively sending an S1 connection request to each MME in the MME pool; if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight; and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, comprising: respectively sending an S1 connection request to each MME in the MME pool; if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight; and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
The present embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the methods provided by the above method embodiments, for example, including: respectively sending an S1 connection request to each MME in the MME pool; if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight; and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (9)

1. A method for determining a main MME in disaster recovery backup is characterized by comprising the following steps:
respectively sending an S1 connection request to each MME in the MME pool;
if an S1 connection request response message returned by at least two MME aiming at the S1 connection request is received within a preset time period, and the pre-stored configuration information which takes the MME with the returned S1 connection request response message as a main MME is not detected locally, comparing the numerical value of each load weight; wherein, each S1 connection request response message carries a load weight;
and taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
2. The method of claim 1, further comprising:
if the number of the MME which is pre-stored and returns the S1 connection request response message is detected to be one locally, the MME is directly accessed to the network according to the configuration information.
3. The method of claim 1, further comprising:
and if an S1 connection request response message returned by one MME aiming at the S1 connection request is received within a preset time period, directly determining the MME as the main MME.
4. The method according to claim 1, wherein after the step of using the target MME corresponding to the larger target load weight in the comparison result as the master MME, the method further comprises:
and generating configuration information of the main MME, and storing the configuration information to the local.
5. The method according to any of claims 1 to 4, wherein after the step of using the target MME with the larger target load weight in the comparison result as the master MME, the method further comprises:
if the S1 connection interruption of the main MME is detected, the step of respectively sending S1 connection requests to each MME in an MME pool is continuously executed so as to re-determine the main MME.
6. The method of claim 5, further comprising:
if the main MME is detected to recover the S1 connection, the re-determined main MME is still used as the current main MME.
7. An apparatus for determining a primary MME in disaster recovery backup, comprising:
a sending unit, configured to send an S1 connection request to each MME in the MME pool;
a comparing unit, configured to compare a value of each load weight if an S1 connection request response message returned by at least two MMEs for the S1 connection request is received within a preset time period, and the pre-stored configuration information that takes the MME containing the S1 connection request response message returned as a master MME is not locally detected; wherein, each S1 connection request response message carries a load weight;
and the determining unit is used for taking the target MME corresponding to the larger target load weight in the comparison result as the main MME.
8. An electronic device, comprising: a processor, a memory, and a bus, wherein,
the processor and the memory are communicated with each other through the bus;
the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1 to 6.
9. A non-transitory computer-readable storage medium storing computer instructions that cause a computer to perform the method of any one of claims 1 to 6.
CN201910052278.6A 2019-01-21 2019-01-21 Method and device for determining main MME in disaster recovery backup Withdrawn CN111465041A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910052278.6A CN111465041A (en) 2019-01-21 2019-01-21 Method and device for determining main MME in disaster recovery backup

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910052278.6A CN111465041A (en) 2019-01-21 2019-01-21 Method and device for determining main MME in disaster recovery backup

Publications (1)

Publication Number Publication Date
CN111465041A true CN111465041A (en) 2020-07-28

Family

ID=71682187

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910052278.6A Withdrawn CN111465041A (en) 2019-01-21 2019-01-21 Method and device for determining main MME in disaster recovery backup

Country Status (1)

Country Link
CN (1) CN111465041A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605316A (en) * 2009-07-09 2009-12-16 华为技术有限公司 Select mobile management entity, the method that load information is provided and device
CN102281586A (en) * 2010-06-12 2011-12-14 电信科学技术研究院 Method, device and system for selecting mobile management entity
US20130083650A1 (en) * 2010-05-11 2013-04-04 Nec Europe Ltd. Method for handling failure of a mme in a lte/epc network
CN106465094A (en) * 2015-01-30 2017-02-22 华为技术有限公司 Service disaster recovery method, related device, and communication system
CN109005564A (en) * 2018-08-23 2018-12-14 福建三元达网络技术有限公司 A kind of method and system of MME load distribution

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605316A (en) * 2009-07-09 2009-12-16 华为技术有限公司 Select mobile management entity, the method that load information is provided and device
US20130083650A1 (en) * 2010-05-11 2013-04-04 Nec Europe Ltd. Method for handling failure of a mme in a lte/epc network
CN102281586A (en) * 2010-06-12 2011-12-14 电信科学技术研究院 Method, device and system for selecting mobile management entity
CN106465094A (en) * 2015-01-30 2017-02-22 华为技术有限公司 Service disaster recovery method, related device, and communication system
CN109005564A (en) * 2018-08-23 2018-12-14 福建三元达网络技术有限公司 A kind of method and system of MME load distribution

Similar Documents

Publication Publication Date Title
WO2016202051A1 (en) Method and device for managing active and backup nodes in communication system and high-availability cluster
EP3343836B1 (en) Hot backup method, device and system
EP2887720B1 (en) Resource allocation method and device
US11892922B2 (en) State management methods, methods for switching between master application server and backup application server, and electronic devices
CN107508694B (en) Node management method and node equipment in cluster
CN109921942B (en) Cloud platform switching control method, device and system and electronic equipment
CN102035683B (en) Control method and system for switching of main board and standby board
CN111385107B (en) Main/standby switching processing method and device for server
CN111158962A (en) Remote disaster recovery method, device, system, electronic equipment and storage medium
WO2016082710A1 (en) Call control method, diameter protocol forwarding device, and system
US20080082630A1 (en) System and method of fault tolerant reconciliation for control card redundancy
CN113553179A (en) Distributed key value storage load balancing method and system
CN110109772B (en) CPU restarting method, communication equipment and readable storage medium
CN113535480A (en) Data disaster recovery system and method
JP6007988B2 (en) Standby system apparatus, operational system apparatus, redundant configuration system, and load distribution method
CN117201507A (en) Cloud platform switching method and device, electronic equipment and storage medium
CN110661599B (en) HA implementation method, device and storage medium between main node and standby node
CN111465041A (en) Method and device for determining main MME in disaster recovery backup
CN107087021B (en) Master-slave server determination method and device
EP3355480B1 (en) Communication device, communication processing method, communication processing apparatus and communication system
CN109634787B (en) Distributed file system monitor switching method, device, equipment and storage medium
CN113259975A (en) Network game connection method, electronic device and computer readable medium
CN109753292B (en) Method and device for deploying multiple applications in multiple single instance database service
CN112990867A (en) Method, system and equipment for realizing high availability of document platform service
CN103001810B (en) Network path protection changing method and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WW01 Invention patent application withdrawn after publication
WW01 Invention patent application withdrawn after publication

Application publication date: 20200728