WO2016119263A1 - 一种业务容灾的方法和相关装置 - Google Patents

一种业务容灾的方法和相关装置 Download PDF

Info

Publication number
WO2016119263A1
WO2016119263A1 PCT/CN2015/072051 CN2015072051W WO2016119263A1 WO 2016119263 A1 WO2016119263 A1 WO 2016119263A1 CN 2015072051 W CN2015072051 W CN 2015072051W WO 2016119263 A1 WO2016119263 A1 WO 2016119263A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
identifier
backup
request message
attached
Prior art date
Application number
PCT/CN2015/072051
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to JP2017540599A priority Critical patent/JP6487563B2/ja
Priority to CN201910975917.6A priority patent/CN110830288B/zh
Priority to PCT/CN2015/072051 priority patent/WO2016119263A1/zh
Priority to EP15879471.9A priority patent/EP3253090B1/en
Priority to CN201580001104.7A priority patent/CN105556900B/zh
Priority to KR1020177024067A priority patent/KR101974022B1/ko
Publication of WO2016119263A1 publication Critical patent/WO2016119263A1/zh
Priority to US15/664,986 priority patent/US10405206B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and related apparatus for service disaster tolerance.
  • a Mobility Management Entity (MME) pool is a plurality of MMEs serving the same radio area at the same time.
  • MME Mobility Management Entity
  • All the base stations in the pool are interconnected, and the MME in the MME Pool implements resource sharing and service load sharing.
  • the base station serving the UE will pass a preset policy, such as load balancing.
  • a preset policy such as load balancing.
  • the principle is that the service request of the UE is sent to another working MME in the MME Pool, and the working MME rejects the service request of the UE, and the UE needs to be reattached to the working MME.
  • the recovery of the service enables the disaster recovery between the MMEs in the MME Pool.
  • the solution provided by the prior art has a poor disaster tolerance effect.
  • VoIP voice over LTE
  • the base station serving the UE will send the VoLTE calling service request message of the UE to a new MME in the MME Pool, but the new MME will reject the VoLTE calling service request of the UE.
  • the UE whose service request is rejected is re-initiated the attach procedure, attaches to the new MME, and initiates the VoLTE calling service again, and the new MME provides the service for the VoLTE calling service of the UE. This results in the UE's VoLTE calling service not being successful at one time.
  • HSS Home Subscriber Server
  • the embodiments of the present invention provide a method and related device for service disaster tolerance, which solves the problem that the disaster tolerance effect of the existing disaster recovery solution is poor.
  • an embodiment of the present invention provides a method for service disaster tolerance, where the method includes:
  • the mobility management entity MME sends a request message to the domain name service system DNS server, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire all MMEs in the MME pool area.
  • MME code MMEC MME code MMEC
  • the MME sends an interface request message to the DNS server, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used to request to acquire the backup MME. Interface information;
  • the MME sends the user information of the user equipment UE attached to the MME to the backup MME according to the interface information of the backup MME.
  • an embodiment of the present invention provides a method for service disaster tolerance, where the method includes:
  • the domain name service system DNS server receives the request message sent by the mobility management entity MME, where the request message includes the pool area identifier of the MME pool area where the MME is located.
  • the request message is used to request to obtain the MME coded MMEC of all MMEs in the MME pool area;
  • the request response message includes the MMECs of all the MMEs, so that the MME determines the backup MME of the MME according to the MMEC of all the MMEs;
  • the DNS server receives an interface request message sent by the MME, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used to request to acquire the backup MME. Interface information;
  • an embodiment of the present invention provides a method for service disaster tolerance, where the method includes:
  • the serving MME receives the service request message sent by the UE through the evolved base station eNodeB, where the service request message includes the identifier of the UE and the identifier of the MME to which the UE is attached.
  • the service request message is used to request that the MME to which the UE is attached to provide the UE with the service; wherein the serving MME is that the eNodeB selects to provide the service for the UE after the MME attached to the UE is faulty.
  • MME, the MME attached to the UE and the serving MME are located in the same MME pool area;
  • the serving MME acquires user information of the UE according to the identifier of the UE or according to the identifier of the UE and the identifier of the MME to which the UE is attached.
  • the serving MME provides the UE with a service corresponding to the service request message according to the user information of the UE.
  • the embodiment of the present invention provides a method for service disaster tolerance, and the method include:
  • the serving MME receives a paging request message sent by the core network element of the circuit switched CS domain of the second generation mobile communication technology 2G or the third generation mobile communication technology 3G network.
  • the paging request message includes an identifier of the UE, where the paging request message is used to request to initiate a CSFB or a 1xCSFB paging to the UE, where the serving MME is when the MME attached to the UE fails.
  • the MME that provides the service to the UE, where the MME attached to the UE and the serving MME are located in the same MME pool area;
  • the serving MME acquires a tracking area where the UE is located according to the user information, and initiates a paging request in the tracking area.
  • an embodiment of the present invention provides a mobility management entity MME, where the MME includes: a sending unit, a receiving unit, and a determining unit;
  • the sending unit is configured to send a request message to the domain name service system DNS server, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool area.
  • the MME of all MMEs encodes the MMEC;
  • the receiving unit is configured to receive a request response message sent by the DNS server, where the request response message includes an MMEC of all MMEs in the MME pool area;
  • the determining unit is configured to determine, according to a preset policy, a backup MME of the MME according to an MMEC of all MMEs in the MME pool area;
  • the sending unit is further configured to: send an interface request message to the DNS server, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used for requesting Obtaining interface information of the backup MME;
  • the receiving unit is further configured to: receive an interface response message sent by the DNS server, where the interface response message includes interface information of the backup MME;
  • the sending unit is further configured to: send user information of the user equipment UE attached to the MME to the backup MME according to the interface information of the backup MME.
  • the determining unit is specifically configured to:
  • MMEC of all MMEs in the MME pool area are sorted according to the MMEC in order of small to large to obtain a ranking result
  • the MME that is adjacent to the MMEC of the MME and greater than the MME of the MME is used as the backup MME, and if the MMEC of the MME is the largest of the ranking results, the MME The MME with the smallest MMEC in the ranking result is used as the backup MME.
  • the sending unit is specifically configured to:
  • an embodiment of the present invention provides a domain name service system DNS server, where the DNS server includes: a receiving unit, a first acquiring unit, a sending unit, and a second acquiring unit;
  • the receiving unit is configured to receive a request message sent by the mobility management entity MME, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool area.
  • the MME of all MMEs encodes the MMEC;
  • the first obtaining unit is configured to acquire, according to the pool area identifier of the MME pool area, an MMEC of all MMEs in the MME pool area corresponding to the pool area identifier of the MME pool area;
  • the sending unit is configured to send a request response message to the MME, where the request response message includes the MMEC of all the MMEs, so that the MME determines the backup MME of the MME according to the MMEC of all the MMEs;
  • the receiving unit is further configured to: receive an interface request message sent by the MME, where the interface request message includes an MMEC of the backup MME and the MME pool area The pool area identifier, the interface request message is used to request to obtain interface information of the backup MME;
  • the second acquiring unit is configured to obtain interface information of the backup MME according to the MMEC of the backup MME and the pool area identifier of the MME pool area;
  • the sending unit includes: sending an interface response message to the MME, where the interface response message includes interface information of the backup MME, so that the MME attaches to the MME according to the interface information of the backup MME.
  • the user information of the user equipment UE is sent to the backup MME.
  • an embodiment of the present invention provides a serving mobility management entity MME, where the serving MME includes: a receiving unit, an obtaining unit, and a service unit;
  • the receiving unit configured to receive a service request message sent by the UE by using an evolved base station eNodeB after the mobile device management entity MME attached to the user equipment UE fails, where the service request message includes an identifier of the UE and the UE An identifier of the attached MME, where the service request message is used to request the MME to which the UE is attached to provide the UE with a service, where the serving MME is selected by the eNodeB after the MME attached to the UE is faulty.
  • the MME that the UE provides, the MME attached to the UE and the serving MME are located in the same MME pool area;
  • the acquiring unit is configured to acquire user information of the UE according to the identifier of the UE or according to an identifier of the UE and an identifier of an MME to which the UE is attached;
  • the service unit is configured to provide the UE with a service corresponding to the service request message according to the user information of the UE.
  • the receiving unit is further configured to: receive user information of the UE and an identifier of the UE that are sent by an MME attached to the UE, and record the UE Correspondence between user information and the identity of the UE;
  • the acquiring unit is specifically configured to: obtain the user information of the UE saved by the serving MME according to the identifier of the UE.
  • the acquiring unit is specifically configured to:
  • the identifier of the MME to which the UE is attached is the MME coded MMEC of the MME to which the UE is attached, and the acquiring unit is specifically configured to:
  • the request message includes a pool area identifier of the MME pool area where the serving MME is located, and the request message is used to request the MME code MMEC of all MMEs in the MME pool area.
  • the DNS server sends an interface request message, where the interface request message includes the MMEC of the backup MME and the pool area identifier of the MME pool area, so that the DNS server identifies the pool area identifier according to the MME pool area and The MMEC of the backup MME acquires interface information of the backup MME;
  • the service request message is a long-term evolution-based voice VoLTE caller of the UE a service request message, or a round-trip CSFB request message for the UE or a 1xCSFB request message for the UE;
  • the identifier of the MME to which the UE is attached is the MMEC of the MME to which the UE is attached;
  • the service request message is a tracking area update TAU request message of the UE, and the identifier of the MME to which the UE is attached is a globally unique temporary user equipment identifier GUTI allocated by the MME to which the UE is attached to the UE, in the GUTI The MMEC of the MME to which the UE is attached.
  • the identifier of the UE is a short format temporary mobile subscriber identity S-TMSI of the UE .
  • the serving MME further includes: a determining unit and a sending unit;
  • the determining unit is configured to determine, according to the user information of the UE, that the UE is a legal user;
  • the sending unit is configured to send a modification request message to the serving gateway SGW and the home user register HSS that are connected to the MME, where the modification request message includes an identifier of the UE, and the modification request message is used to request the Determining, by the SGW or the HSS, a correspondence between the UE and an MME to which the UE is attached, to a correspondence between the UE and the serving MME; re-allocating a GUTI for the UE and sending the re-allocated GUTI To the UE, to cause the UE to attach to the serving MME.
  • an embodiment of the present invention provides a serving MME, where the serving MME includes: a receiving unit, an obtaining unit, and a paging unit;
  • the receiving unit is configured to receive, after the fault of the mobility management entity MME to which the user equipment UE is attached, the core network element of the circuit switched CS domain of the second generation mobile communication technology 2G or the third generation mobile communication technology 3G network a call request message, where the paging request message includes an identifier of the UE, where the paging request message is used to request to initiate a CSFB or a 1xCSFB paging to the UE, where the serving MME is when the UE attaches
  • the MME that provides the service to the UE when the MME fails, the MME to which the UE is attached and the serving MME are located in the same MME pool area;
  • the acquiring unit is configured to acquire user information of the UE according to the identifier of the UE;
  • the paging unit is configured to acquire a tracking area where the UE is located according to the user information, and initiate a paging request in the tracking area.
  • the serving MME Also included: a recording unit;
  • the receiving unit is further configured to: receive user information of the UE and an identifier of the UE that are sent by the MME attached to the UE;
  • the recording unit is configured to record a correspondence between user information of the UE and an identifier of the UE;
  • the acquiring unit is configured to acquire user information of the UE saved by the serving MME according to the identifier of the UE.
  • the serving MME further includes: a sending unit;
  • the sending unit is configured to send a broadcast request message to all MMEs in the MME pool area, where the broadcast request message includes an identifier of the UE, and the broadcast message is used to request to acquire user information of the UE;
  • the receiving unit is further configured to receive a broadcast response message of the backup MME of the MME to which the UE is attached, where the broadcast response message includes user information of the UE.
  • An embodiment of the present invention provides a method and a related device for service disaster recovery.
  • the MME obtains, by using a MME, all MMEs in the MME pool area where the MME is located, and the MME is all according to the MME pool area.
  • the MME of the MME obtains the backup MME of the MME by using a preset policy, and obtains the interface information of the backup MME by using the MME, and the MME backs up the user information of the UE attached to the MME to the MME.
  • the backup MME when the MME sends a fault, the network side sends a request message of the service corresponding to the UE to a working MME in the MME pool area as a serving MME of the UE, and the serving MME
  • the user information of the UE can be obtained from the backup MME to provide a service for the UE, so that the service of the UE can be successfully performed at one time, and the problem that the service disaster tolerance effect of the prior art service is poor is solved.
  • 1 is a schematic diagram of an LTE network architecture
  • FIG. 2 is a flow chart 1 of a method for service disaster tolerance
  • FIG. 3 is a schematic diagram of a MME chain backup relationship
  • FIG. 4 is a flow chart 2 of a method for service disaster tolerance
  • FIG. 5 is a flowchart 3 of a method for service disaster tolerance
  • FIG. 6 is a flowchart 4 of a method for service disaster tolerance
  • FIG. 8 is a schematic diagram of a DNS server
  • FIG. 9 is a schematic diagram 1 of a serving MME
  • 10 is a schematic diagram 2 of a serving MME
  • 11 is a schematic diagram of another MME or DNS server or service MME.
  • an LTE network architecture is exemplarily described.
  • MME1, MME2, and MME3 form an MME Pool, a Serving Gateway (SGW), and The Packet Data Network Gateway (PGW) constitutes a GW Pool.
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • each mobile communication device is connected to a base station in the LTE access network, and the base station in the access network is connected to each MME in the MME Pool.
  • the HSS actually has a connection relationship with each MME in the MME Pool, and The MMEs in the MME Pool are connected to each other and the like.
  • the MME Pool can implement the disaster recovery of the UE service. For example, when the MME1 attached to the UE1 fails, the service request initiated by the UE1 is sent to the MME pool by the base station 1 serving the UE1. On the MME, the MME is assumed to be the MME2. Since there is no user information of the UE on the MME2, the MME2 rejects the service request of the UE, and the UE1 attaches to the MME2 by re-initiating the attach procedure, so that the service of the UE1 is restored. The disaster recovery of the MME in the MME pool area is implemented.
  • the disaster recovery effect of the prior art is poor.
  • the MME1 fails, and the base station 1 selects the MME2 to provide the service for the UE1.
  • the MME2 since the MME2 does not have the user information of the UE1, the MME2 cannot provide the service for the user. Therefore, the MME2 will reject the VoLTE calling service request of the UE1, and the MME2 can provide the service for the UE1 after the UE1 is attached to the MME2. On the one hand, this will result in the UE's VoLTE service not being successful at one time, which makes the user experience worse.
  • the user information of the UE may include the subscription data information of the UE, the information corresponding to the service of the UE, etc., when there is a VoLTE calling party service of the UE, a CSFB calling party service, and a TAU updating service of the UE, the MME may The information required to process these services is obtained from the user information of the UE.
  • the embodiment of the present invention provides a method for service disaster tolerance.
  • the method includes:
  • the mobile management entity MME sends a request message to the domain name service system DNS server, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to obtain the MME pool area.
  • the MME of all MMEs encodes the MMEC.
  • MME1, MME2, and MME3 form an MME Pool, which is an MME Pool in the LTE network shown in FIG. 1.
  • the LTE network shown in FIG. 1 may also have Other MME Pools not shown.
  • Each MME Pool in the LTE network has a MME Pool ID (MMEGI) corresponding to it, and the MME Code (MMEC) of the MME in the pool area is the MME in the MME Pool.
  • MMEGI MME Pool ID
  • MMEC MME Code
  • a backup MME can be configured for each MME by using a preset policy.
  • DNS Domain Name System
  • the coded MMEC of all MMEs and the available interface information of all MMEs are pre-configured by the pool.
  • the MME in the area obtains the MMEC information of all the MMEs in the pool area and the available interface information of all the MMEs from the DNS server, and parses the backup MME of the MME by using a preset policy.
  • the DNS server stores an identifier MMEGI (MME Group ID) of each MME Pool and an MMEC of each MME in the MME pool area.
  • the DNS server divides all MMEs in the MME pool into at least one group, and assigns each group an identification information LIST_ID that uniquely identifies the group.
  • the MMEGI of an MME pool area is MMEGI-1, and there are 10 MMEs in the MME pool area, which are respectively MME1-MME10, and the MMECs of the 10 MMEs are respectively 1-10, and are pre-stored in the DNS server.
  • the relevant data information of the MME pool area for example, the MMEGI information of the MME pool area, pre-allocates the 10 MMEs into two groups, and the identification information LIST_ID of the corresponding group of the first group is LIST_ID-1, including MME1-MME6. 6 MMEs, the LIST_ID corresponding to the second group is LIST_ID-2, and includes 4 MMEs of MME7-MME10.
  • the MME may send the request message to the DNS server by using a first fully qualified domain name (Fully Qualified Domain Name, FQDN), where the first FQDN may be:
  • the MMEGI is the pool area identification information of the MME pool area where the MME is located. Assume that it is MMEGI-1.
  • the MNC is used to distinguish the carrier information to which the network belongs.
  • the MNC consists of two decimal numbers. The encoding range is 00-99 in decimal. For example, China Mobile's MNC is 00, 02, 04, and 06. Unicom's MNC is 01, 05, 07, and China Telecom's MNC is 03.
  • the MCC is the mobile signal country code, which is used to uniquely identify the country to which the mobile subscriber belongs.
  • the DNS server matches the information of LIST_ID-1 and LIST_ID-2 in the above MME pool area according to MMEGI-1, and the MMEC information of all MMEs in LIST_ID-1 and LIST_ID-2.
  • the MME receives a request response message sent by the DNS server, where the request response message includes an MMEC of all MMEs in the MME pool area.
  • the MME request response message sent by the DNS server may be in the form indicated by the second FQDN:
  • the DNS server sends 10 messages as shown in the second FQND to the MME.
  • the MMEC represents MME1
  • ⁇ LIST_ID> represents the identification information LIST_ID-1 of the group in which the MME1 is located
  • the MMEGI is the identification information MMEGI-1 of the MME pool area in which the MME1 is located.
  • the MME may obtain MMEC information of all MMEs in the MME pool area and LIST_ID information corresponding to each MME according to the information in the second FQDN, that is, the MME pool area includes 10 MMEs, and 10
  • the MMEs are divided into two groups.
  • the identification information of the two groups is LIST_ID-1 and LIST_ID-2, respectively.
  • the group corresponding to LIST_ID-1 includes the MMEs of MME1-MME6, and the MMEC information of the six MMEs.
  • the group corresponding to LIST_ID-2 includes four MMEs of MME7-MME10, and MMEC information of the four MMEs.
  • the MME determines, according to a preset policy, a backup MME of the MME according to an MMEC of all MMEs in the MME pool area.
  • the MME sorts the MMECs of all MMEs in the MME pool area according to the order of the MMEC from small to large to obtain a sorting result
  • the MME is adjacent to the MMEC of the MME, and the MME of the MMEC that is greater than the MME is used as the backup MME, and if the MMEC of the MME is the largest of the ranking results, the MME The MME uses the MME with the smallest MMEC in the ranking result as the backup MME.
  • the MMECs of the MMEs in the same group are sorted in order from small to large, and a chain backup ring as shown in FIG. 3 is generated.
  • an MME chain backup ring is exemplarily described. It is assumed that the MME is MME1, the identifier of the group in which the MME1 is located is LIST_ID-1, and the six MMEs in the group are respectively MME1-MME6. Assuming that the MMECs of MME1-MME6 are sequentially increased from small to large, the six MMEs can form a chained backup relationship as shown in FIG. In the chain backup ring, the MME with the smaller MMEC number selects the MME with the larger MMEC number as the backup MME, and the MME with the largest MMEC number selects the MME with the smallest MMEC number in the chain backup ring as the backup MME. .
  • the backup MME of MME1 is MME2
  • the backup MME of MME2 is MME3
  • the backup MME of MME5 is MME6
  • the backup MME of MME6 is MME1.
  • the MME can also obtain the chain backup ring of the group corresponding to the LIST_ID-2 in the same manner, thereby obtaining the backup relationship of all the MMEs in the MME pool area.
  • the chain backup relationship shown in FIG. 3 is only a feasible implementation manner, and the MME may also generate another type of backup relationship of the MME in the pool area according to a preset policy. This is not limited, and any method for obtaining a backup MME of an MME in the same pool area based on the idea of the present invention is within the protection scope of the present invention.
  • the MME sends an interface request message to the DNS server, where
  • the interface request message includes the MMEC of the backup MME and the pool area identifier of the MME pool area, where the interface request message is used to request to obtain interface information of the backup MME.
  • the ⁇ interface-name> of the second FQDN carries only one interface information of the MME, but the MME in the pool area actually includes multiple interfaces, and one MME in the pool area wants to perform with another MME.
  • the MME in the pool area actually includes multiple interfaces, and one MME in the pool area wants to perform with another MME.
  • communicating only one interface of the MME may not be able to communicate, and other available interface information of the MME needs to be obtained.
  • the MME needs to back up the user information of the UE to the backup MME. Therefore, the MME needs to obtain all the interface information of the backup MME.
  • the MME may send the following third FQDN to the DNS server:
  • the MMEC in the third FQDN is the MMEC of the backup MME, and is used to indicate that the MME requests to back up information of all the interfaces of the MME, and the DNS server performs query and parsing through the information in the third FQDN, and obtains all interfaces of the backup MME. Information, and sending address information of all interfaces of the backup MME to the MME.
  • the MME receives an interface response message sent by the DNS server, where the interface response message includes interface information of the backup MME.
  • the interface response message is a fourth FQDN:
  • the MME in the pool area only needs to go through the steps 201 to the step.
  • the MME re-acquires the MMEC of all MMEs in the pool area and the available interface information of each MME, and parses the information of the backup MME by using a preset policy. For example, when the MME 6 stops using, the backup MME of the MME 1 becomes the MME 5, which is not only guaranteed.
  • Each MME in the MME pool area has its backup MME, and reduces the complexity of the backup relationship of all MMEs in the pool area and the interface information of all MMEs.
  • the MME sends user information of the user equipment UE attached to the MME to the backup MME according to the interface information of the backup MME.
  • the MME sends a backup request message to the backup MME by using the interface of the backup MME, where the backup request message carries the identifier information of the UE, and the user information of the UE, the backup request information. And configured to request the backup MME to back up user information of the UE.
  • the backup MME After receiving the backup request message, the backup MME stores the user information of the UE, and records the correspondence between the identifier information of the UE and the user information of the UE.
  • the embodiment of the present invention provides a method for service disaster tolerance, in which the MMEC information of all MMEs in the pool area and the available interface information of all MMEs are pre-configured in the DNS server, and the MME needs to be attached to the MME.
  • the MME queries the DNS server for the MMEC information of all the MMEs in the pool area where the MME is located, and obtains the information of the backup MME of the MME according to a preset policy.
  • the user information of the UE is backed up to the backup MME by using the available interface of the backup MME, and the MME pool area is restored after the MME fails.
  • the other MMEs in the MME obtain the user information of the UE from the backup MME, so as to provide services for the UE, so that the service of the UE can be successfully succeeded at one time, and the problem that the service disaster tolerance effect of the prior art service is poor is solved.
  • the embodiment of the present invention further provides a service disaster tolerance.
  • Method comprising:
  • the domain name service system DNS server receives a request message sent by the mobility management entity MME, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool area.
  • the MME of all MMEs encodes the MMEC.
  • the DNS server acquires, according to the pool area identifier of the MME pool area, the MMECs of all MMEs in the MME pool area corresponding to the pool area identifier of the MME pool area, and sends a request response message to the MME.
  • the request response message includes the MMECs of all the MMEs, so that the MME determines the backup MME of the MME according to the MMEC of all the MMEs.
  • the DNS server receives an interface request message sent by the MME, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used to request to obtain the Back up the interface information of the MME.
  • the DNS server obtains the interface information of the backup MME according to the MMEC of the backup MME and the pool area identifier of the MME pool area, and sends an interface response message to the MME, where the interface response message includes The interface information of the MME is backed up, so that the MME sends the user information of the user equipment UE attached to the MME to the backup MME according to the interface information of the backup MME.
  • the embodiment of the present invention provides a service disaster tolerance method.
  • the MMEC information of all MMEs in the MME pool area and the available interface information of all MMEs are pre-configured in the DNS server.
  • the MME queries the DNS server for the MMEC information of all MMEs in the MME pool area to which the MME belongs, and according to the MMEC information of all the MMEs, Obtaining information of the backup MME of the MME by using a preset policy.
  • the user of the UE is obtained through the available interface of the backup MME by querying the DNS server for the available interface information of the backup MME.
  • the embodiment of the present invention further provides a service disaster tolerance method, where the method includes:
  • the serving MME receives a service request message sent by the UE by using the evolved base station eNodeB, where the service request message includes an identifier of the UE and an MME attached to the UE. And the service request message is used to request that the MME to which the UE is attached to provide the UE with a service, where the serving MME is that the eNodeB selects the UE after the MME attached to the UE is faulty.
  • the serving MME, the MME attached to the UE and the serving MME are located in the same MME pool area.
  • the service request message needs to be sent to the base station connected to the UE.
  • the service request is according to the UE.
  • the services to be initiated are different, for example, the VoLTE calling service corresponds to a VoLTE calling service request, and the CSFB calling service corresponds to a CSFB calling service request.
  • the service request message carries the identifier information of the UE, where the identifier information of the UE is information that can uniquely identify the user in a network where the UE is located, such as a short-form temporary mobile subscriber identifier of the user (Short Temporary Mobile Subscriber Identity, S-TMSI).
  • S-TMSI Short Temporary Mobile Subscriber Identity
  • the UE is the UE1 in FIG. 1, and the UE is originally attached to the MME1 in FIG. 1.
  • the base station 1 serving the UE1 determines the MME1. A failure has occurred and it is no longer possible to provide service to UE1.
  • the base station 1 reselects an MME for the UE1 in the same MME pool area as the MME1 according to a preset policy, such as the load balancing principle.
  • the MME2 in FIG. 1 provides the UE1 with a service, which may be referred to as the above. Serving the MME of the UE1, and transmitting the service request message of the UE1 to the MME2, and instructing the MME2 to provide a service for the UE1.
  • the serving MME acquires user information of the UE according to the identifier of the UE or according to the identifier of the UE and the identifier of the MME to which the UE is attached.
  • the serving MME of the UE1 After receiving the service request message of the UE1 sent by the base station 1, the serving MME of the UE1 determines whether the user information of the UE1 is stored according to the S-TMSI of the UE1 carried in the service request message.
  • MME2 is the backup MME of MME1
  • MME1 backs up the user information of UE1 to MME2 before the failure
  • MME2 records the correspondence between the identifier of UE1 and the user information of UE1.
  • the MME2 can obtain the user information of the UE1 directly from the storage space in which the user information is stored according to the identifier of the UE1.
  • the MME2 If the MME2 is not the backup MME of the MME1, and the MME3 in FIG. 1 is the backup MME of the MME1, the MME2 does not store the user information of the UE1, and the user information of the UE1 cannot be obtained according to the identification information of the UE1. At this time, the MME2 backs up from the MME1. The MME, that is, the MME 3, acquires the user information of the UE1.
  • the serving MME obtains the user information of the UE by using the following process: the serving MME sends a request message to the domain name service system DNS server, where the request message carries the pool of the MME pool area where the serving MME is located a zone identifier, the request message is used to request an MMEC of all MMEs in the MME pool area;
  • the serving MME acquires a backup MME of the MME to which the UE is attached according to the MME C of the MME to which the UE is attached, and the MMEC of the MME, and sends an interface request message to the DNS server, where the interface request message is sent.
  • a backup MME of the MME to which the UE is attached according to the MME C of the MME to which the UE is attached, and the MMEC of the MME, and sends an interface request message to the DNS server, where the interface request message is sent.
  • the serving MME receives an interface response message sent by the DNS server, where the interface response message includes information about an interface of the backup MME.
  • the serving MME may acquire the MMEC of all MMEs in the MME pool area by using the first FQDN, and parse the MMEC in the MME pool area before receiving the service request message.
  • the backup relationship of all MMEs in the MME pool area, the LIST_ID information corresponding to each MME, and the information of all available interfaces of all MMEs in the MME pool area through the third FQDN, when the serving MME receives After the service request message of the UE, the backup MME of the MME to which the UE is attached, and the available interface information of the backup MME may be obtained by using the MME C information of the MME that is attached to the UE.
  • the user information of the UE is obtained through the available interface of the backup MME, and the message is not queried to the DNS server every time the service request message is received, thereby reducing the overhead of the message.
  • the serving MME sends a user information request message to the backup MME by using the interface of the backup MME, where the user information request message includes identifier information of the UE.
  • the backup MME acquires user information of the UE according to the identifier information of the UE, and sends the user information of the UE to the serving MME.
  • the process of the serving MME acquiring the backup MME of the MME attached to the UE and the interface of the backup MME is similar to the process of the MME attached by the UE acquiring the interface of the backup MME and the backup MME, and detailed technical features thereof are provided.
  • the process of the serving MME acquiring the backup MME of the MME attached to the UE and the interface of the backup MME is similar to the process of the MME attached by the UE acquiring the interface of the backup MME and the backup MME, and detailed technical features thereof are provided.
  • the MME attached by the UE The identifier information is the MMEC information of the MME to which the UE is attached, the identifier information of the UE is the S-TMSI information of the UE, or, if the service request message is the TAU request message of the UE, The identity information of the MME attached to the UE is the MME attached to the UE.
  • the globally unique Temporary UE Identity (GUTI) information of the UE includes MMEC information of the MME to which the UE is attached, and the identifier information of the UE is the S- of the UE TMSI information.
  • GUTI globally unique Temporary UE Identity
  • the identifier of the MME to which the UE is attached which is included in the query request message, identifies that the MME that the UE requests the UE to attach to provide services for the UE.
  • the eNodeB that provides the service to the UE sends the service request message of the UE to another MME in the MME pool area, which may be called the serving MME.
  • the MME may reject the service request of the UE because there is no user information of the UE.
  • the UE is attached to the serving MME by the re-attachment process, and the UE initiates the service request again.
  • the service request message initiated by the UE includes the identifier of the serving MME, indicating that the UE requests the serving MME to be the The UE provides the service.
  • the serving MME provides the UE with a service corresponding to the service request message according to the user information of the UE.
  • the serving MME further needs to determine, according to the user information of the UE, whether the UE is a legal UE, and if not, the serving MME directly rejects the a service request of the UE, if yes, the serving MME needs to send a modification request message to the SGW and the HSS connected to the serving MME, where the modification request message carries the identifier information of the UE, and the modification request message is used for
  • the SGW and the HSS are requested to modify the correspondence between the UE and the MME to which the UE is attached, to the corresponding relationship between the UE and the serving MME.
  • the serving MME further needs to re-allocate the GUTI for the UE, so that the UE is attached to the serving MME, so that all services of the UE are subsequently completed by the serving MME.
  • the serving MME sends the modification request message to the HSS by a preset time delay.
  • the reason for this is that the number of users attached to the MME attached to the UE is tens of thousands. After the MME attached to the UE fails, the MME attached to the original MME needs the MME in the MME pool to work as the UE.
  • Provide services At this time, if each serving MME sends a modification request message to the HSS, the HSS will receive a large number of modification request messages in a short period of time, resulting in a large load of the HSS, which may cause congestion, and because the HSS is an LTE core.
  • the important network elements in the network, the congestion of the HSS will have a great impact on the processing of the network service. Therefore, the serving MME may delay sending the modification request message to the HSS by a preset time to avoid the HSS being short. The load suddenly increased during the time.
  • the HSS may receive 10,000 of the modification request messages, causing the load of the HSS to suddenly Increase, causing congestion, but if the serving MME sends the modification request by delay, 100 pieces of the modification request are sent every second, and the modification request is sent to the HSS in 100 seconds. Reduce the load of HSS in unit time and reduce the impact on HSS.
  • the HSS is also responsible for a large number of other services. For example, when the UE is called as a VoLTE, the HSS also completes a domain selection process to determine information about the domain in which the UE is currently located, if the HSS is congested. Then, the UE's VoLTE called service will fail.
  • the HSS selects any working MME in the pool area to obtain the foregoing domain selection process.
  • the information of the UE does not cause the called service of the UE to fail.
  • the serving MME if the UE is registered in the CS domain core network MSC network element of the 2G/3G network, the serving MME also needs to send a location update request message to the MSC for updating the MME information registered on the MSC. . If the UE is registered in the core network 1xCS IWS network element of the CDMA2000 network, the serving MME also needs to send an MME change notification message to the 1xCS IWS for updating the MME information registered on the 1xCS IWS.
  • the serving MME further needs to send an indication message to the base station serving the UE, instructing the base station to establish a link and a bearer on the radio side, and sending a request message to the SGW to request to establish a tunnel that interfaces with the SGW.
  • the serving MME further needs to instruct the UE to re-establish the correspondence between the IMSI and the TMSI.
  • CSFB Circuit Switched Fallback
  • WCDMA Wideband Code Division Multiple Access
  • 1xCSFB calling service the serving MME instructing the base station to perform the circuit domain fallback of the UE.
  • the embodiment of the present invention provides a service disaster tolerance method, in which, when a MME attached to a UE fails and a base station serving the UE detects the fault, the base station serves the UE.
  • the request message is sent to the other normal MME in the pool area where the MME to which the UE is attached, as the serving MME of the UE, and when the serving MME is the backup MME of the MME to which the UE is attached, the serving MME is configured according to the The information of the UE is obtained from the storage space of the UE. If the serving MME is not the backup MME of the MME to which the UE is attached, the serving MME obtains the information of the backup MME of the MME to which the UE is attached.
  • the registration request achieves the effect of avoiding HSS congestion, and solves the problem that the prior art business disaster tolerance effect is poor.
  • the embodiment of the present invention further provides a method for service disaster tolerance, which includes:
  • the serving MME receives the paging request message sent by the core network element of the circuit switched CS domain of the second generation mobile communication technology 2G or the third generation mobile communication technology 3G network.
  • the paging request message includes an identifier of the UE, where the paging request message is used to request to initiate a CSFB or a 1xCSFB paging to the UE, where the serving MME is when an MME attached to the UE occurs.
  • the MME that provides the service to the UE, the MME to which the UE is attached and the serving MME are located in the same MME pool area.
  • the network element of the CS domain of the 2G/3G network to which the UE falls back sends a paging request message to the MME attached to the UE, so that the UE is attached.
  • the MME pages the UE.
  • the network element of the CS domain of the 2G/3G network sends the paging request message to a normal MME in the pool area where the MME attached to the UE is located after the MME attached to the UE fails.
  • the MME acts as a serving MME that processes the paging request message.
  • both CSFB and 1xCSFB are circuit domain switchback, but the corresponding UEs fall back to different networks, one corresponding to the UE falling back to the Wideband Code Division Multiple Access (WCDMA) network, one Correspondingly, it falls back to the WCDMA2000 network.
  • WCDMA Wideband Code Division Multiple Access
  • the serving MME acquires user information of the UE according to the identifier of the UE.
  • the serving MME may also receive the UE sent by the MME attached to the UE before the MME attached to the UE fails.
  • the user information and the identifier of the UE, and the corresponding relationship between the user information of the UE and the identifier of the UE is recorded; at this time, the serving MME may acquire the saved by the serving MME according to the identifier of the UE.
  • User information of the UE is a backup MME of the MME to which the UE is attached.
  • the serving MME sends a broadcast request message to all MMEs in the MME pool area, where the broadcast request message includes the identifier of the UE.
  • the broadcast message is used to request to acquire user information of the UE.
  • the backup MME of the MME to which the UE is attached may send a broadcast response message to the serving MME after receiving the broadcast message, where the broadcast response message includes user information of the UE.
  • the serving MME acquires a tracking area where the UE is located according to the user information, and initiates a paging request in the tracking area.
  • the 2G/3G core network element that is dropped by the UE passes the preset policy in the MME pool after the MME attached to the UE fails.
  • An MME is selected as the serving MME of the UE to initiate a paging request.
  • the serving MME does not have the user information of the UE, the serving MME cannot obtain the tracking area where the UE is located, and the serving MME can only search in multiple tracking areas. Calling the UE, the paging efficiency is low.
  • the serving MME acquires the information of the tracking area of the UE according to the user information of the UE, and initiates a paging procedure in the tracking area of the UE, which greatly improves the paging efficiency.
  • the embodiment of the present invention provides a service disaster tolerance method, in which the UE falls back to the 2G/3G network after the UE is the called user of the CSFB/1xCSFB and the MME attached to the UE fails.
  • the network element of the CS domain sends a paging request message to other normally working MMEs in the MME pool area, and the working MME processes the paging request message as a serving MME.
  • the serving MME acquires user information of the UE from itself or from a backup MME of the MME to which the UE is attached, and acquires information of the tracking area of the UE from the user information of the UE, and is in the tracking area.
  • the paging process is initiated, so that the CSFB/1xCSFB called service of the UE succeeds once, and the problem that the current service disaster tolerance effect is poor is solved.
  • the MME includes: a sending unit 701, a receiving unit 702, and a determining unit 703, in order to solve the problem that the prior art service disaster tolerance is poor.
  • the sending unit 701 is configured to send a request message to the domain name service system DNS server, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool.
  • the MME of all MMEs in the area encodes the MMEC;
  • the receiving unit 702 is configured to receive a request response message sent by the DNS server, where the request response message includes an MMEC of all MMEs in the MME pool area;
  • the determining unit 703 is configured to: according to all MMEs in the MME pool area
  • the MMEC determines the backup MME of the MME according to a preset policy
  • the sending unit 701 is further configured to: send an interface request message to the DNS server, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used. Requesting to obtain interface information of the backup MME;
  • the receiving unit 702 is further configured to: receive an interface response message sent by the DNS server, where the interface response message includes interface information of the backup MME;
  • the sending unit 701 is further configured to: send user information of the user equipment UE attached to the MME to the backup MME according to the interface information of the backup MME.
  • the determining unit 703 is configured to:
  • MMEC of all MMEs in the MME pool area are sorted according to the MMEC in order of small to large to obtain a ranking result
  • the MME that is adjacent to the MMEC of the MME and greater than the MME of the MME is used as the backup MME, and if the MMEC of the MME is the largest of the ranking results, the MME The MME with the smallest MMEC in the ranking result is used as the backup MME.
  • the sending unit 701 is configured to:
  • the MME provides an MME.
  • the MME needs to back up the user information of the UE attached to the MME, the MME queries the DNS server through the FQDN for all the MMEs in the pool area where the MME is located.
  • the MMEC information is obtained, and the information about the backup MME of the MME is obtained according to the preset policy, and the user information of the UE is backed up by using the available interface of the backup MME by querying the DNS server for the available interface information of the backup MME.
  • the MME obtains the user information of the UE, thereby providing a service for the UE, so that the service of the UE can be successfully successful at one time, and the problem that the current service disaster tolerance effect is poor is solved.
  • the embodiment of the present invention further provides a DNS server, where the DNS server includes: a receiving unit 801, a first obtaining unit 802, a sending unit 803, and a second obtaining unit 804;
  • the receiving unit 801 is configured to receive a request message sent by the mobility management entity MME, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool.
  • the MME of all MMEs in the area encodes the MMEC;
  • the first obtaining unit 802 is configured to obtain, according to the pool area identifier of the MME pool area, an MMEC of all MMEs in the MME pool area corresponding to the pool area identifier of the MME pool area;
  • the sending unit 803 is configured to send a request response message to the MME, where the request response message includes the MMEC of all the MMEs, so that the MME determines the backup MME of the MME according to the MMEC of all the MMEs;
  • the receiving unit 801 is further configured to: receive an interface request message sent by the MME, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used for requesting Obtaining interface information of the backup MME;
  • the second obtaining unit 804 is configured to obtain interface information of the backup MME according to the MMEC of the backup MME and the pool area identifier of the MME pool area;
  • the sending unit 803 is configured to: send an interface response message to the MME, where the interface response message includes interface information of the backup MME, so that the MME attaches to the interface according to the interface information of the backup MME.
  • the user information of the user equipment UE on the MME is sent to the backup MME.
  • the embodiment of the present invention provides a DNS server, where the MMEC information of all the MMEs in the MME pool area and the available interface information of all the MMEs are pre-configured, and the MME in the MME pool area needs to be attached to the MME.
  • the MME queries the DNS server for the MMEC information of all the MMEs in the MME pool area to which the MME belongs, and obtains the backup of the MME according to the MMEC information of all the MMEs according to the preset policy. MME information.
  • the user information of the UE is backed up to the backup MME by using the available interface of the backup MME by querying the DNS server for the available interface information of the backup MME, so that after the MME fails, the MME pool area
  • the other MMEs obtain the user information of the UE from the backup MME, thereby providing a service for the UE, so that the service of the UE can be successfully succeeded at one time, and the problem that the service disaster tolerance effect of the prior art service is poor is solved.
  • the MME includes: a receiving unit 901, an obtaining unit 902, and a service unit 903, in order to solve the problem that the prior art service disaster tolerance is poor.
  • the receiving unit 901 is configured to: after a fault of the mobility management entity MME to which the user equipment UE is connected, receive a service request message sent by the UE by using an evolved base station eNodeB, where the service request message includes the identifier of the UE and the An MME that is attached to the UE, where the service request message is used to request that the MME to which the UE is attached to provide the UE with a service, where the serving MME is selected by the eNodeB after the MME attached to the UE is faulty.
  • An MME that provides the UE with the MME and the serving MME that are attached to the UE are located in the same MME pool area;
  • the obtaining unit 902 is configured to acquire user information of the UE according to the identifier of the UE or according to the identifier of the UE and the identifier of the MME to which the UE is attached;
  • the service unit 903 is configured to provide the UE with a service corresponding to the service request message according to the user information of the UE.
  • the receiving unit 901 is further configured to: receive user information of the UE and an identifier of the UE that are sent by the MME that is attached to the UE, and record user information of the UE and an identifier of the UE. Correspondence relationship
  • the obtaining unit 902 is specifically configured to: obtain the user information of the UE saved by the serving MME according to the identifier of the UE.
  • the acquiring unit 902 is configured to: according to the MME attached by the UE And obtaining the interface information of the backup MME of the MME to which the UE is attached, and acquiring the user information of the UE from the backup MME according to the identifier of the UE and the interface information of the backup MME, where the The backup MME and the serving MME are located in the same MME pool area.
  • the identifier of the MME to which the UE is attached is the MME coded MMEC of the MME to which the UE is attached, and the acquiring unit 902 is specifically configured to:
  • the request message includes a pool area identifier of the MME pool area where the serving MME is located, and the request message is used to request the MME code MMEC of all MMEs in the MME pool area.
  • the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, so that the DNS server identifies the pool area identifier according to the MME pool area.
  • the MMEC of the backup MME acquiring interface information of the backup MME;
  • the service request message is a caller service request message of the long-term evolution-based voice VoLTE of the UE, or a circuit domain exchange fallback CSFB request message of the UE or a 1xCSFB request message of the UE;
  • the identifier of the MME to which the UE is attached is the MMEC of the MME to which the UE is attached; or
  • the service request message is a tracking area update TAU request message of the UE, and the identifier of the MME to which the UE is attached is a globally unique temporary user equipment identifier GUTI allocated by the MME to which the UE is attached to the UE, in the GUTI The MMEC of the MME to which the UE is attached.
  • the specific identifier of the UE is a short format temporary mobile subscriber identity S-TMSI of the UE.
  • the serving MME further includes: a determining unit 904 and a sending unit 905;
  • the determining unit 904 is configured to determine, according to the user information of the UE, that the UE is a legal user;
  • the sending unit 905 is configured to send a modification request message to the serving gateway SGW and the home user register HSS connected to the MME, where the modification request message includes an identifier of the UE, and the modification request message is used to request
  • the SGW or the HSS modifies a correspondence between the UE and an MME to which the UE is attached, to a correspondence between the UE and the serving MME, re-allocates a GUTI for the UE, and re-allocates the GUTI Sent to the UE to attach the UE to the serving MME.
  • An embodiment of the present invention provides an MME, after the MME that is attached to the UE fails and the base station serving the UE detects the fault, the base station sends a service request message of the UE to the MME, when the MME is the backup MME of the MME to which the UE is attached, the MME obtains the user information of the UE from the storage space of the UE according to the identifier information of the UE, if the MME is not the MME attached to the UE.
  • the backup MME, the MME acquires the information of the backup MME of the MME to which the UE is attached, and requests the backup MME for the user information of the UE, and the MME provides the UE with the service according to the user information of the UE.
  • the effect of avoiding HSS congestion is achieved, and the problem that the service disaster tolerance effect of the prior art is poor is solved.
  • the embodiment of the present invention further provides a serving MME, where the serving MME includes: a receiving unit 1001, an obtaining unit 1002, and a paging unit 1003;
  • the receiving unit 1001 is configured to receive, after the failure of the mobility management entity MME to which the user equipment UE is attached, the core network element of the circuit switched CS domain of the second generation mobile communication technology 2G or the third generation mobile communication technology 3G network.
  • a paging request message where the paging request message includes an identifier of the UE, where the paging request message is used to request to initiate a CSFB or a 1xCSFB paging to the UE, where the serving MME is when the UE
  • the attached MME fails, the MME that provides the UE with the service,
  • the MME attached to the UE and the serving MME are located in the same MME pool area;
  • the obtaining unit 1002 is configured to acquire user information of the UE according to the identifier of the UE.
  • the paging unit 1003 is configured to acquire a tracking area where the UE is located according to the user information, and initiate a paging request in the tracking area.
  • the serving MME further includes: a recording unit 1004;
  • the receiving unit 1001 is further configured to: receive user information of the UE and an identifier of the UE that are sent by an MME that is attached to the UE;
  • the recording unit 1004 is configured to record a correspondence between user information of the UE and an identifier of the UE;
  • the obtaining unit 1002 is configured to acquire user information of the UE saved by the serving MME according to the identifier of the UE.
  • the serving MME further includes: a sending unit 1005;
  • the sending unit 1005 is configured to send a broadcast request message to all MMEs in the MME pool area, where the broadcast request message includes an identifier of the UE, where the broadcast message is used to request to acquire user information of the UE. ;
  • the receiving unit 1001 is further configured to receive a broadcast response message of the backup MME of the MME to which the UE is attached, where the broadcast response message includes user information of the UE.
  • An embodiment of the present invention provides an MME, where a network element of a CS domain of a 2G/3G network that the UE falls back to after the UE is a called user of the CSFB/1xCSFB and the MME attached to the UE fails Sending a request message to the MME, the MME acquiring user information of the UE from itself or from a backup MME of the MME to which the UE is attached, and acquiring information of the tracking area of the UE from the user information of the UE, And the paging process is initiated in the tracking area, so that the CSFB/1xCSFB called service of the UE succeeds once, and the problem that the current service disaster tolerance effect is poor is solved.
  • the embodiment of the present invention further provides an MME, where the MME includes: a transmitter 1105, a processor 1102, a bus 1103, a memory 1104, and a receiver 1101. ;
  • the sender 1105 is configured to send a request message to the domain name service system DNS server, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool.
  • the MME of all MMEs in the area encodes the MMEC;
  • the receiver 1101 is configured to receive a request response message sent by the DNS server, where the request response message includes an MMEC of all MMEs in the MME pool area;
  • the processor 1102 obtains the instruction in the memory 1104 by using the bus 1103, for determining, according to a preset policy, a backup MME of the MME according to a MMEC of all MMEs in the MME pool area;
  • the sender 1105 is further configured to: send an interface request message to the DNS server, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used. Requesting to obtain interface information of the backup MME;
  • the receiver 1101 is further configured to: receive an interface response message sent by the DNS server, where the interface response message includes interface information of the backup MME;
  • the processor 1102 is further configured to: send, according to the interface information of the backup MME, user information of the user equipment UE attached to the MME to the backup MME by using the transmitter 1105.
  • the processor 1102 is configured to: sort the MMECs of all MMEs in the MME pool area according to the MMEC in a small to large order to obtain a sorting result;
  • the MME that is adjacent to the MMEC of the MME and greater than the MME of the MME is used as the backup MME, and if the MMEC of the MME is the largest of the ranking results, the MME The MME with the smallest MMEC in the ranking result is used as the backup MME.
  • the processor 1102 is configured to: send, by using the interface corresponding to the interface information of the backup MME, a backup request message to the backup MME by using the sender 1105, where the backup request message includes the UE And the user information of the UE, where the backup request message is used to request the backup MME to use the UE User information is backed up.
  • the MME provides an MME.
  • the MME needs to back up the user information of the UE attached to the MME, the MME queries the DNS server through the FQDN for all the MMEs in the pool area where the MME is located.
  • the MMEC information is obtained, and the information about the backup MME of the MME is obtained according to the preset policy, and the user information of the UE is backed up by using the available interface of the backup MME by querying the DNS server for the available interface information of the backup MME.
  • the other MMEs in the MME pool acquire the user information of the UE from the backup MME, thereby providing services for the UE, thereby making the UE
  • the service can be successfully successful at one time, and solves the problem of poor disaster recovery effect of the existing technology business.
  • the embodiment of the present invention further provides a DNS server, where the DNS server includes: a receiver 1101, a processor 1102, a bus 1103, a memory 1104, and Transmitter 1105;
  • the receiver 1101 is configured to receive a request message sent by the mobility management entity MME, where the request message includes a pool area identifier of the MME pool area where the MME is located, and the request message is used to request to acquire the MME pool.
  • the MME of all MMEs in the area encodes the MMEC;
  • the processor 1102 obtains the instruction in the memory 1104 by using the bus 1103, and the server obtains the MME pool corresponding to the pool area identifier of the MME pool area according to the pool area identifier of the MME pool area.
  • the transmitter 1105 is configured to send a request response message to the MME, where the request response message includes the MMEC of all the MMEs, so that the MME determines the backup MME of the MME according to the MMEC of all the MMEs;
  • the receiver 1101 is further configured to: receive an interface request message sent by the MME, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, where the interface request message is used for requesting Obtaining interface information of the backup MME;
  • the processor 1102 is further configured to: according to the MMEC and the location of the backup MME Obtaining the interface information of the backup MME by using the pool area identifier of the MME pool area;
  • the transmitter 1105 is further configured to: send an interface response message to the MME, where the interface response message includes interface information of the backup MME, so that the MME attaches to the interface according to the interface information of the backup MME.
  • the user information of the user equipment UE on the MME is sent to the backup MME.
  • the embodiment of the present invention provides a DNS server, where the MMEC information of all the MMEs in the MME pool area and the available interface information of all the MMEs are pre-configured, and the MME in the MME pool area needs to be attached to the MME.
  • the MME queries the DNS server for the MMEC information of all the MMEs in the MME pool area to which the MME belongs, and obtains the MMEC information according to the MMEC information of all the MMEs.
  • the information of the backup MME of the MME is backed up.
  • the user information of the UE is backed up to the backup MME by using the available interface of the backup MME by querying the DNS server for the available interface information of the backup MME, so that after the MME fails, the MME pool area
  • the other MMEs obtain the user information of the UE from the backup MME, thereby providing a service for the UE, so that the service of the UE can be successfully succeeded at one time, and the problem that the service disaster tolerance effect of the prior art service is poor is solved.
  • the MME includes: a receiver 1101, a processor 1102, a bus 1103, and a memory 1104, in order to solve the problem that the service disaster tolerance of the prior art is poor.
  • the embodiment of the present invention further provides an MME, where the MME includes: a receiver 1101, a processor 1102, a bus 1103, and a memory 1104.
  • the receiver 1101 is configured to: after the fault of the mobility management entity MME to which the user equipment UE is attached, the serving MME receives a service request message sent by the UE by using the evolved base station eNodeB, where the service request message includes the identifier of the UE and An identifier of the MME to which the UE is attached, where the service request message is used to request the MME to which the UE is attached to provide the service to the UE, where the serving MME is after the MME of the eNodeB attached to the UE fails.
  • the selected MME that provides the service to the UE, where the MME attached to the UE and the serving MME are located in the same MME pool area;
  • the processor 1102 acquires an instruction in the memory 1104 through the bus 1103, for using according to the identifier of the UE or according to the identifier of the UE and the Obtaining an identifier of the MME to which the UE is attached, and acquiring user information of the UE;
  • the receiver 1101 is further configured to: receive user information of the UE and an identifier of the UE that are sent by an MME attached to the UE;
  • the processor 1102 is specifically configured to: record a correspondence between user information of the UE and an identifier of the UE;
  • the processor 1102 is configured to: obtain, according to the identifier of the MME to which the UE is attached, the interface information of the backup MME of the MME to which the UE is attached, and according to the identifier of the UE and the interface information of the backup MME.
  • the user information of the UE is obtained from the backup MME, where the backup MME and the serving MME are located in the same MME pool area.
  • the identifier of the MME to which the UE is attached is the MME coded MMEC of the MME to which the UE is attached, and the service MME further includes: a transmitter 11051305;
  • the sender 1105 is configured to send a request message to the domain name service system DNS server, where the request message includes a pool area identifier of the MME pool area where the serving MME is located, and the request message is used to request the MME pool.
  • the MME of all MMEs in the area encodes the MMEC;
  • the receiver 1101 is configured to receive a request response message sent by the DNS server, where the request response message includes an MMEC of all MMEs in the MME pool area;
  • the processor 1102 is configured to acquire, according to a preset policy, a backup MME of the MME to which the UE is attached, according to the MMEC of the MME to which the UE is attached, and the MMEC of all the MMEs;
  • the transmitter 1105 is further configured to send an interface request message to the DNS server, where the interface request message includes an MMEC of the backup MME and a pool area identifier of the MME pool area, so that the DNS server is configured according to the MME pool area
  • the pool area identifier and the MMEC of the backup MME acquire interface information of the backup MME.
  • the receiver 1101 is further configured to receive an interface response message sent by the DNS server, where the interface response message includes interface information of the backup MME.
  • the service request message is a caller service request message of the long-term evolution-based voice VoLTE of the UE, or a circuit domain exchange fallback CSFB request message of the UE or a 1xCSFB request message of the UE;
  • the identifier of the MME to which the UE is attached is the MMEC of the MME to which the UE is attached; or
  • the service request message is a tracking area update TAU request message of the UE, and the identifier of the MME to which the UE is attached is a globally unique temporary user equipment identifier GUTI allocated by the MME to which the UE is attached to the UE, in the GUTI The MMEC of the MME to which the UE is attached.
  • the identifier of the UE is a short format temporary mobile subscriber identity S-TMSI of the UE.
  • processor 1102 is further configured to:
  • the transmitter 1105 is further configured to: send a modification request message to the serving gateway SGW and the home user register HSS that are connected to the MME, where the modification request message includes an identifier of the UE, where the modification request message is used. And requesting, by the SGW or the HSS, the correspondence between the UE and the MME to which the UE is attached to be modified as a correspondence between the UE and the serving MME;
  • the processor 1102 is further configured to: re-allocate a GUTI for the UE and send the re-allocated GUTI to the UE by using the transmitter 1105, so that the UE is attached to the serving MME.
  • An embodiment of the present invention provides an MME, after the MME that is attached to the UE fails and the base station serving the UE detects the fault, the base station sends a service request message of the UE to the MME, when When the MME is the backup MME of the MME to which the UE is attached, the MME obtains the user information of the UE from the storage space of the UE according to the identifier information of the UE, if the MME is not the UE.
  • the MME acquiring the information of the backup MME of the MME to which the UE is attached, and requesting the user information of the UE from the backup MME, where the MME is the UE according to the user information of the UE.
  • the service is provided to enable the service of the UE to be successful at one time, and the request for sending the registration request to the HSS is delayed to avoid the congestion of the HSS, and the problem that the service disaster tolerance of the prior art is poor is solved.
  • an embodiment of the present invention further provides an MME, where the MME includes: a receiver 1101, a processor 1102, a bus 1103, a memory 1104, and a transmitter. 1105;
  • the receiver 1101 is configured to receive, after the failure of the mobility management entity MME to which the user equipment UE is attached, the core network element of the circuit switched CS domain of the second generation mobile communication technology 2G or the third generation mobile communication technology 3G network.
  • a paging request message where the paging request message includes an identifier of the UE, where the paging request message is used to request to initiate a CSFB or a 1xCSFB paging to the UE, where the serving MME is when the UE
  • the attached MME fails, the MME that provides the service to the UE, the MME attached to the UE and the serving MME are located in the same MME pool area;
  • the processor 1102 acquires an instruction in the memory 1104 by using the bus 1103, and is configured to acquire user information of the UE according to the identifier of the UE;
  • the receiver 1101 is further configured to: receive user information of the UE and an identifier of the UE that are sent by an MME attached to the UE;
  • the processor 1102 is specifically configured to: record a correspondence between user information of the UE and an identifier of the UE;
  • the transmitter 1105 is further configured to:
  • the receiver 1101 is further configured to: receive a broadcast response message of the backup MME of the MME to which the UE is attached, where the broadcast response message includes user information of the UE.
  • An embodiment of the present invention provides an MME, where a network element of a CS domain of a 2G/3G network that the UE falls back to after the UE is a called user of the CSFB/1xCSFB and the MME attached to the UE fails Sending a request message to the MME, the MME acquiring user information of the UE from itself or from a backup MME of the MME to which the UE is attached, and acquiring information of the tracking area of the UE from the user information of the UE, And the paging process is initiated in the tracking area, so that the CSFB/1xCSFB called service of the UE succeeds once, and the problem that the current service disaster tolerance effect is poor is solved.

Landscapes

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

Abstract

本发明实施例提供了一种业务容灾的方法和相关装置，解决了现有技术业务容灾效果较差的问题。该方法包括：MME向DNS服务器发送请求消息，包含MME所位于的MME池区的池区标识；MME接收DNS服务器发送的请求响应消息，包含MME池区中所有MME的MMEC；MME根据MME池区中所有MME的MMEC，确定MME的备份MME；MME向DNS服务器发送接口请求消息，包含备份MME的MMEC和MME池区的池区标识；MME接收DNS服务器发送的接口响应消息，包含备份MME的接口信息；MME根据备份MME的接口信息，将附着在MME上的UE的用户信息发送至备份MME。该方法适用于通信技术领域。

Description

一种业务容灾的方法和相关装置 技术领域
本发明涉及通信技术领域，尤其涉及一种业务容灾的方法和相关装置。
背景技术
在长期演进(Long Term Evolution，LTE)网络架构下，移动管理实体(Mobility Management Entity，MME)池区(Pool)是多个MME同时为相同的无线区域服务，MME Pool内的每个MME与MME Pool内的所有基站互联，MME Pool内的MME实现资源共享，业务负荷分担。
当MME Pool中的某个MME发生故障，如果附着在该故障MME上的用户设备(User Equipment，UE)主动发起的业务请求，则为该UE服务的基站会通过预设的策略，如负载均衡的原则，将该UE的业务请求发送到MME Pool内的另一个正常工作的MME上，该正常工作的MME会拒绝该UE的业务请求，该UE需要通过重新附着到该正常工作的MME上实现业务的恢复，从而实现MME Pool内MME间的容灾。
但是，现有技术所提供的这种方案容灾效果较差，例如，当UE需要发起基于长期演进的语音(Voice over LTE，VoLTE)主叫业务，且该UE所附着的MME发生故障时，为该UE提供服务的基站会将该UE的VoLTE主叫业务请求消息发送至MME Pool内的一个新的MME上，但是新的MME会拒绝UE的VoLTE主叫业务请求。业务请求被拒的UE通过重新发起附着流程，附着到新的MME上，并再次发起VoLTE主叫业务，由新的MME为该UE的VoLTE主叫业务提供服务。这导致UE的VoLTE主叫业务不能一次成功。并且MME故障后，故障MME上附着的所有UE发起的业务请求都会被网络侧拒绝而触发这些UE的重新附着流程，这种较短时间内大量用户产 生的附着流程也会为LTE网络中其他网元，如家乡用户寄存器(Home Subscriber Server，HSS)带来大量的信今冲击，造成HSS拥塞。HSS是整个网络的关键节点，HSS拥塞会造成用户无法接入网络，或者VoLTE通话成功率大幅下降。
发明内容
本发明的实施例提供一种业务容灾的方法和相关装置，解决了现有容灾方案容灾效果较差的问题。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，本发明实施例提供了一种业务容灾的方法，该方法包括：
移动管理实体MME向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述MME接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
所述MME根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME；
所述MME向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述MME接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息；
所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
第二方面，本发明实施例提供了一种业务容灾的方法，该方法包括：
域名服务***DNS服务器接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标 识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述DNS服务器根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC，并向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME；
所述DNS服务器接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述DNS服务器根据所述备份MME的MMEC和所述MME池区的池区标识获取所述备份MME的接口信息，并向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
第三方面，本发明实施例提供了一种业务容灾的方法，该方法包括：
在用户设备UE附着的移动管理实体MME发生故障后，服务MME接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务；其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述服务MME根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息，
所述服务MME根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
第四方面，本发明实施例提供了一种业务容灾的方法，该方法 包括：
在用户设备UE附着的移动管理实体MME故障后，服务MME接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述服务MME根据所述UE的标识获取所述UE的用户信息；
所述服务MME根据所述用户信息获取所述UE所在的跟踪区，并在所述跟踪区内发起寻呼请求。
第五方面，本发明实施例提供了一种移动管理实体MME，该MME包括：发送单元，接收单元和确定单元；
所述发送单元，用于向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述接收单元，用于接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
所述确定单元，用于根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME；
所述发送单元还用于：向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述接收单元还用于：接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息；
所述发送单元还用于：根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
在第一种可能的实施方式中，结合第五方面，所述确定单元具体用于：
将所述MME池区中所有MME的MMEC按照MMEC由小到大的顺序进行排序获得排序结果；
将所述排序结果中与所述MME的MMEC相邻，且大于所述MME的MMEC的MME作为所述备份MME，若所述MME的MMEC是所述排序结果中最大的，则所述MME将所述排序结果中MMEC最小的MME作为所述备份MME。
在第二种可能的实施方式中，结合第五方面或第五方面第一种可能的实施方式，所述发送单元具体用于：
通过所述备份MME的接口信息所对应的接口，向所述备份MME发送备份请求消息，所述备份请求消息中包含所述UE的标识和所述UE的用户信息，所述备份请求消息用于请求所述备份MME对所述UE的用户信息进行备份。
第六方面，本发明实施例提供了一种域名服务***DNS服务器，所述DNS服务器包括：接收单元，第一获取单元，发送单元和第二获取单元；
所述接受单元，用于接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述第一获取单元，用于根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC；
所述发送单元，用于向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME；
所述接收单元还用于：接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区 的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述第二获取单元，用于根据所述备份MME的MMEC和所述MME池区的池区标识获取所述备份MME的接口信息；
所述发送单元包括：向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
第七方面，本发明实施例提供了一种服务移动管理实体MME，所述服务MME包括：接收单元，获取单元和服务单元；
所述接收单元，用于在用户设备UE附着的移动管理实体MME发生故障后，接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务，其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述获取单元，用于根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息；
所述服务单元，用于根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
在第一种可能的实施方式中，结合第七方面，所述接收单元还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识，并记录所述UE的用户信息和所述UE的标识的对应关系；
所述获取单元具体用于：根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
在第二种可能的实施方式中，结合第七方面，所述获取单元具体用于：
根据所述UE附着的MME的标识，获取所述UE附着的MME的备份MME的接口信息，并根据所述UE的标识和所述备份MME的接口信息，从所述备份MME获取所述UE的用户信息，其中，所述备份MME和所述服务MME位于同一个MME池区中。
在第三种可能的实施方式中，结合第二种可能的实施方式，所述UE附着的MME的标识为所述UE附着的MME的MME编码MMEC，所述获取单元具体用于：
向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述服务MME所位于的MME池区的池区标识，所述请求消息用于请求所述MME池区中所有MME的MME编码MMEC；
接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
根据所述UE附着的MME的MMEC，以及所述所有MME的MMEC，按照预设的策略，获取所述UE附着的MME的备份MME；
所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC以及所述MME池区的池区标识，以便于所述DNS服务器根据所述MME池区的池区标识以及所述备份MME的MMEC，获取所述备份MME的接口信息；
接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息。
在第四种可能的实施方式中，结合第七方面至第七方面第三种可能的实施方式中的任一种，所述服务请求消息为所述UE的基于长期演进的语音VoLTE的主叫业务请求消息，或为所述UE的电路域交换回落CSFB请求消息或为所述UE的1xCSFB请求消息；所述UE附着的MME的标识为所述UE附着的MME的MMEC；或者，
所述服务请求消息为所述UE的跟踪区更新TAU请求消息，所述UE附着的MME的标识为所述UE附着的MME分配给所述UE的全球唯一临时用户设备标识GUTI，所述GUTI中包含所述UE附着的MME的MMEC。
在第五种可能的实施方式中，结合第七方面至第七方面第四种可能的实施方式中的任一种，所述UE的标识为所述UE的短格式临时移动用户标识S-TMSI。
在第六种可能的实施方式中，结合第七方面至第七方面第五种可能的实施方式中的任一种，所述服务MME还包括：确定单元和发送单元；
所述确定单元，用于根据所述UE的用户信息，确定所述UE为合法用户；
所述发送单元，用于分别向与所述MME相连的服务网关SGW和家乡用户寄存器HSS发送修改请求消息，所述修改请求消息中包含所述UE的标识，所述修改请求消息用于请求所述SGW或所述HSS将所述UE与所述UE附着的MME的对应关系修改为所述UE和所述服务MME的对应关系；为所述UE重新分配GUTI并将所述重新分配的GUTI发送至所述UE，以使所述UE附着在所述服务MME上。
第八方面，本发明实施例提供了一种服务MME，所述服务MME包括：接收单元，获取单元和寻呼单元；
所述接收单元，用于在用户设备UE附着的移动管理实体MME故障后，接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述获取单元，用于根据所述UE的标识获取所述UE的用户信息；
所述寻呼单元，用于根据所述用户信息获取所述UE所在的跟踪区，并在所述跟踪区内发起寻呼请求。
在第一种可能的实施方式中，结合第八方面，所述服务MME 还包括：记录单元；
所述接收单元还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识；
所述记录单元，用于记录所述UE的用户信息和所述UE的标识的对应关系；
所述获取单元，用于根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
在第二种可能的实施方式中，结合第八方面，所述服务MME还包括：发送单元；
所述发送单元，用于向所述MME池区内的所有MME发送广播请求消息，所述广播请求消息中包含所述UE的标识，所述广播消息用于请求获取所述UE的用户信息；
所述接收单元，还用于接收所述UE附着的MME的备份MME的广播响应消息，所述广播响应消息中包含所述UE的用户信息。
本发明实施例提供了一种业务容灾的方法和相关装置，MME通过从DNS服务器获取所述MME所位于的MME池区中的所有MME的MMEC，所述MME根据所述MME池区中所有MME的MMEC，通过预设的策略获取所述MME的备份MME，并通过向所述DNS服务器获取到所述备份MME的接口信息，所述MME将所述MME上附着的UE的用户信息备份至所述备份MME，当所述MME发送故障时，网络侧将所述UE对应的业务的请求消息发送至所述MME池区中一个正常工作的MME作为所述UE的服务MME，所述服务MME从所述备份MME可以获取所述UE的用户信息从而为UE提供服务，使得UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于 本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为一种LTE网络架构示意图；
图2为一种业务容灾的方法流程图一；
图3为一种MME链式备份关系示意图；
图4为一种业务容灾的方法流程图二；
图5为一种业务容灾的方法流程图三；
图6为一种业务容灾的方法流程图四；
图7为一种MME示意图；
图8为一种DNS服务器示意图；
图9为一种服务MME示意图一；
图10为一种服务MME示意图二；
图11为另一种MME或DNS服务器或服务MME示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
结合图1，示例性的描述了一种LTE网络架构，在该架构的分组交换(packet switching，PS)域核心网中，MME1、MME2以及MME3组成MME Pool，服务网关(Serving Gateway，SGW)以及报文数据网络网关(Packet Data Network Gateway，PGW)组成GW Pool，另外，LTE网络的PS域核心网中还包含家乡用户寄存器(Home Subscriber Server，HSS)。
在该架构的接入网中，各个移动通信设备与LTE接入网中的基站相连，接入网中的基站与MME Pool中的每个MME相连，需要说明的是，在图1中只是示例性的描述了部分网元的连接关系，例如HSS实际上是与MME Pool中的每个MME都存在连接关系，以及 MME Pool中的MME两两相互连接等。
通过MME Pool可以实现UE业务的容灾，举例来说，当UE1所附着的MME1发生故障时，UE1主动发起的业务请求会通过为UE1提供服务的基站1发送到MME池区内的一个正常工作的MME上，假设该正常工作的MME为MME2，由于MME2上没有UE的用户信息，则MME2拒绝UE的业务请求，UE1通过重新发起附着流程附着在该MME2上，使得UE1的业务得到恢复，从而实现MME池区中MME的容灾。
但是，现有技术容灾效果较差，如当UE1发起VoLTE主叫业务时MME1发生故障，基站1选择MME2为UE1提供服务。此时由于MME2没有UE1的用户信息，MME2无法为用户提供服务，因此MME2将拒绝UE1的VoLTE主叫业务请求，当UE1附着在MME2之后，MME2才能为UE1提供服务。一方面，这将导致UE的VoLTE业务不能一次成功，使得用户体验较差；另一方面，MME1故障后，MME1上附着的所有UE发起的业务请求都会被网络侧拒绝，从而触发这些UE的重新附着流程，短时间内大量用户的附着流程将给网络中其他相关网元，如HSS产生大量的信今冲击，造成HSS拥塞，产生用户无法接入网络，或者VoLTE通话成功率大幅下降的负面影响。
具体的，UE的用户信息中可以包含UE的签约数据信息，UE的业务所对应的信息等，当存在UE的VoLTE主被叫业务，CSFB主被叫业务以及UE的TAU更新业务时，MME可以从UE的用户信息中获取到处理这些业务所需的信息。
为解决现有技术容灾效果较差的问题，本发明实施例提供了一种业务容灾的方法，结合图2，该方法包括：
201、移动管理实体MME向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC。
结合图1，MME1、MME2和MME3组成一个MME Pool，该MME Pool是图1所示的LTE网络中的一个MME池区(MME Pool)，具体的，图1所示的LTE网络中还可能有其他未示出的MME Pool。
LTE网络中的每个MME Pool都有一个与其唯一对应的MME池区标识(MME Group ID，MMEGI)，池区内每个MME的编号(MME Code，MMEC)是该MME在该MME Pool内的唯一标识。
基于此，可以通过预设的策略，为每个MME配置一个备份MME，如在域名服务***(Domain Name System，DNS)服务器中预配置所有MME的编码MMEC以及所有MME的可用接口信息，由池区中的MME从所述DNS服务器获取池区中所有MME的MMEC信息和所有MME的可用接口信息，并通过预设的策略解析所述MME的备份MME。
具体的，DNS服务器中存储有每个MME Pool的标识MMEGI(MME Group ID)以及该MME池区内每个MME的MMEC。DNS服务器将该MME池区内的所有MME分为至少一组，并为每组分配唯一标识该组的标识信息LIST_ID。
举例来说，一个MME池区的MMEGI为MMEGI-1，该MME池区内有10个MME，分别为MME1-MME10，假设这10个MME的MMEC分别为1-10，在DNS服务器中预存储这个MME池区的相关数据信息，例如，该MME池区的MMEGI信息，将这10个MME预分配为两组，第一组对应的组的标识信息LIST_ID为LIST_ID-1，包含MME1-MME6这6个MME，第二组对应的LIST_ID为LIST_ID-2，包含MME7-MME10这4个MME。
具体的，所述MME可以通过第一完全合格域名/全称域名(Fully Qualified Domain Name，FQDN)向所述DNS服务器发送所述请求消息，该第一FQDN可以为：
ring.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnet work.org
其中，MMEGI为所述MME所在的MME池区的池区标识信息， 假设为MMEGI-1，MNC用于区分该网络所属的运营商信息，MNC由二个十进制数组成，编码范围为十进制的00-99，例如***的MNC为00、02、04和06，***的MNC为01、05、07，中国电信的MNC为03，MCC为移动信号国家码，用于唯一识别移动用户所属的国家。
DNS服务器根据MMEGI-1匹配到上述MME池区中的LIST_ID-1和LIST_ID-2的信息，以及LIST_ID-1和LIST_ID-2中的所有MME的MMEC信息。
202、所述MME接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC。
具体的，DNS服务器发送的MME请求响应消息可以是如下第二FQDN所示的形式：
<interface-name>.ring.mmec<MMEC>.list<LIST_ID>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
举例来说，若MME所在的池区中有10个MME，DNS服务器会向所述MME发送10条如上第二FQND所示的消息，例如所述MMEC代表的是MME1，则前缀<interface-name>携带MME1的一个可用接口信息，<LIST_ID>代表MME1所在的组的标识信息LIST_ID-1，MMEGI为MME1所在的MME池区的标识信息MMEGI-1。
所述MME根据所述第二FQDN中的信息就可以获取所述MME池区内所有MME的MMEC信息以及每个MME所对应的LIST_ID信息，即所述MME池区中包含10个MME，这10个MME被分为两组，这两组的标识信息分别为LIST_ID-1和LIST_ID-2，LIST_ID-1所对应的组中包含MME1-MME6这六个MME，以及这六个MME的MMEC信息，LIST_ID-2所对应的组中包含MME7-MME10这四个MME，以及这四个MME的MMEC信息。
203、所述MME根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME。
具体的，所述MME将所述MME池区中所有MME的MMEC按照MMEC由小到大的顺序进行排序获得排序结果；
所述MME将所述排序结果中与所述MME的MMEC相邻，且大于所述MME的MMEC的MME作为所述备份MME，若所述MME的MMEC是所述排序结果中最大的，则所述MME将所述排序结果中MMEC最小的MME作为所述备份MME。
例如，所述MME获取到所述所有MME的MMEC后，对同一组中的MME的MMEC按照由小到大的顺序进行排序，生成如图3所示的链式备份环。
具体的，结合图3，示例性的描述了一种MME链式备份环，假设所述MME为MME1，MME1所在组的标识为LIST_ID-1，该组中的6个MME分别为MME1-MME6，假设MME1-MME6的MMEC由小到大依次升高，则这6个MME可以组成如图4所示的链式备份关系。在该链式备份环中，MMEC数字较小的MME选择数值排序上相邻的MMEC数字较大的MME作为备份MME，MMEC数字最大的MME选择链式备份环中MMEC数字最小的MME作为备份MME。
举例来说，MME1的备份MME为MME2，MME2的备份MME为MME3...MME5的备份MME为MME6，MME6的备份MME为MME1。
当然，所述MME也可以按照同样的方法获取LIST_ID-2所对应的组的链式备份环，从而获得该MME池区中所有MME的备份关系。
需要说明的是，图3所示的链式备份关系只是一种可行的实施方式，所述MME还可以按照预设的策略生成一个池区内的MME的其他形式的备份关系，本发明实施例对此不做限定，并且，任何基于本发明思想的获取一个MME在同池区内的备份MME的方法，都在本发明的保护范围之内。
204、所述MME向所述DNS服务器发送接口请求消息，所述 接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息。
进一步的，所述第二FQDN的<interface-name>中只携带MME的一个接口信息，但实际上池区中的MME包含多个接口，当池区中的一个MME想要跟另外一个MME进行通信时，只根据该MME的一个接口可能无法进行通信，需要获取该MME的其他可用接口信息。
在本发明实施例所示的场景下，所述MME需要将UE的用户信息备份至备份MME，因此，所述MME需要获取所述备份MME的所有接口信息。
此时，所述MME可以向所述DNS服务器发送如下第三FQDN：
mmec<MMEC>.list<LIST_ID>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
第三FQDN中的MMEC为备份MME的MMEC，用于标志所述MME请求备份MME的所有接口的信息，DNS服务器通过第三FQDN中的信息进行查询解析，获取到所述备份MME的所有接口的信息，并将所述备份MME所有接口的地址信息发送至所述MME。
205、所述MME接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息。
所述接口响应消息为第四FQDN：
<interface-name>.ring.mmec<MMEC>.list<LIST_ID>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org，其中，所述第四FQDN中的MMEC为所述备份MME的MMEC，所述interface-name中包含所述备份MMEC的所有接口信息，或者，若所述备份MME有F个接口，则所述接口响应消息中包含F个所述第四FQDN，每个所述第四FQDN中的interface-name中包含所述备份MME的一个接口信息，所述F个第四FQDN中包含的所述备份MME的接口信息两两不同。
需要说明的是，当池区中增加或减少MME时，例如，结合图3，当MME6停止使用时，通过本发明是实施例提供的技术方案，池区中的MME只需要通过步骤201到步骤205重新获取池区中所有MME的MMEC以及每个MME的可用接口信息，并通过预设的策略解析其备份MME的信息，例如，当MME6停止使用时，MME1的备份MME变为MME5，不但保证MME池区中的每个MME都有其备份MME，而且降低了每个MME获取池区中所有MME的备份关系以及所有MME的接口信息的复杂程度。
206、所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
具体的，所述MME通过所述备份MME的接口向所述备份MME发送备份请求消息，所述备份请求消息中携带所述UE的标识信息，以及所述UE的用户信息，所述备份请求信息用于请求所述备份MME对所述UE的用户信息进行备份。
所述备份MME接收到所述备份请求消息后，将所述UE的用户信息进行存储，并记录所述UE的标识信息与所述UE的用户信息的对应关系。
本发明实施例提供了一种业务容灾的方法，在该方法中，DNS服务器中预配置有池区内所有MME的MMEC信息以及所有MME的可用接口信息，当所述MME需要将附着在所述MME上的UE的用户信息进行备份时，所述MME通过FQDN向DNS服务器查询所示MME所在池区内所有MME的MMEC信息，并根据预设的策略获取所述MME的备份MME的信息，并通过向DNS服务器查询备份MME的可用接口信息，通过所述备份MME的可用接口将所述UE的用户信息备份至所述备份MME，以使得当所述MME发生故障后，所述MME池区内的其他MME从所述备份MME获取所述UE的用户信息，从而为所述UE提供服务，从而使所述UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题。
进一步的，结合图4，本发明实施例还提供了一种业务容灾的 方法，该方法包括：
401、域名服务***DNS服务器接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC。
402、所述DNS服务器根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC，并向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME。
403、所述DNS服务器接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息。
404、所述DNS服务器根据所述备份MME的MMEC和所述MME池区的池区标识获取所述备份MME的接口信息，并向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
具体的，本发明实施例的详细技术特征可参见上述图2所对应的实施例，本发明实施对此不再赘述。
本发明实施例提供了一种业务容灾的方法，在该方法中，DNS服务器中预配置有MME池区内所有MME的MMEC信息以及所有MME的可用接口信息，当所述MME池区中的MME需要将附着在所述MME上的UE的用户信息进行备份时，所述MME通过FQDN向DNS服务器查询所属MME所在MME池区内所有MME的MMEC信息，并根据所述所有MME的MMEC信息，通过预设的策略获取所述MME的备份MME的信息。通过向DNS服务器查询备份MME的可用接口信息，通过所述备份MME的可用接口将所述UE的用户 信息备份至所述备份MME，以使得当所述MME发生故障后，所述MME池区内的其他MME从所述备份MME获取所述UE的用户信息，从而为所述UE提供服务，从而使所述UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图5，本发明实施例还提供了一种业务容灾的方法，该方法包括：
501、在用户设备UE附着的移动管理实体MME发生故障后，服务MME接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务，其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中。
具体的，当UE需要进行VoLTE主叫业务、或者数据业务，或者回落到宽带码分多址(Wideband Code Division Multiple Access，WCDMA)网络的电路域交换回落(Circuit Switched Fallback，CSFB)主叫业务，或者回落到WCDMA2000网络的1xCSFB主叫业务，或者跟踪区更新(Tracking Area Update，TAU)业务时，需要先向与该UE连接的基站发送服务请求消息，具体的，所述服务请求根据所述UE所要发起的业务不同而不同，例如，所述VoLTE主叫业务对应的是VoLTE主叫业务请求，CSFB主叫业务对应的是CSFB主叫业务请求等。
所述服务请求消息中携带所述UE的标识信息，所述UE的标识信息是能够在所述UE所处的网络中唯一标识所述用户的信息，如用户的短格式临时移动用户标识(Short Temporary Mobile Subscriber Identity，S-TMSI)。
结合图1，假设所述UE为所述图1中的UE1，所述UE原来附着在图1中的MME1上，当所述MME1发生故障后，为所述UE1服务的基站1判断所述MME1发生故障，无法继续为UE1提供服务， 基站1根据预设的策略，如负载均衡的原则，在与MME1相同的MME池区内为UE1重选一个MME，如图1中的MME2为所述UE1提供服务，我们可以称之为所述UE1的服务MME，并将所述UE1的服务请求消息发送至所述MME2，并指示所述MME2为所述UE1提供服务。
502、所述服务MME根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息。
UE1的服务MME，即MME2接收到基站1发送的UE1的服务请求消息后，根据所述服务请求消息中携带的UE1的S-TMSI判断是否存储有UE1的用户信息。
具体的，结合图2和图4所对应的实施例，若MME2为MME1的备份MME，则MME1在故障之前将UE1的用户信息备份至MME2，MME2记录有UE1的标识与UE1的用户信息的对应关系，MME2可以根据UE1的标识直接从存储有所述用户信息的存储空间中获取所述UE1的用户信息。
若MME2不是MME1的备份MME，假设图1中的MME3是MME1的备份MME，则MME2没有存储UE1的用户信息，根据UE1的标识信息无法获取到UE1的用户信息，此时，MME2从MME1的备份MME，即MME3获取所述UE1的用户信息。
具体的，所述服务MME通过如下过程获取所述UE的用户信息：所述服务MME向域名服务***DNS服务器发送请求消息，所述请求消息中携带所述服务MME所位于的MME池区的池区标识，所述请求消息用于请求所述MME池区内所有MME的MMEC；
所述服务MME接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区内所有MME的MMEC；
所述服务MME根据所述UE附着的MME的MMEC，以及所述所有MME的MMEC，获取所述UE附着的MME的备份MME，并向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的标识以及所述MME池区的池区标识，以使得所述 DNS服务器根据所述池区标识以及所述备份MME的标识，获取所述备份MME的接口信息；
所述服务MME接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口的信息。
需要说明的是，所述服务MME可以通过图3所对应的实施例的方法，在接收所述业务请求消息之前通过第一FQDN获取所述MME池区内所有MME的MMEC，并解析到如图4所示的MME池区中的所有MME的备份关系，每个MME所对应的LIST_ID信息以及通过第三FQDN查询所述MME池区所有MME的所有可用接口的信息，当所述服务MME接收到所述UE的业务请求消息之后，可以通过所述UE附着的MME的MMEC信息直接从所述所有MME的备份关系中获取所述UE附着的MME的备份MME，以及所述备份MME的可用接口信息，通过所述备份MME的可用接口获取所述UE的用户信息，而不用每次收到业务请求消息后再向DNS服务器查询上述消息，从而减少了信今的开销。
所述服务MME通过所述备份MME的接口向所述备份MME发送用户信息请求消息，所述用户信息请求消息包含所述UE的标识信息。所述备份MME根据所述UE的标识信息获取所述UE的用户信息，并将所述UE的用户信息发送至所述服务MME。
需要说明的是，服务MME获取所述UE附着的MME的备份MME以及该备份MME的接口的过程与UE附着的MME获取所述备份MME以及该备份MME的接口的过程相似，其的详细技术特征可参见上述图3所对应的实施例，本发明实施例对此不再赘述。
需要说明的是，若所述服务请求消息为所述UE的VoLTE的主叫业务请求消息，或所述服务请求消息为所述UE的CSFB请求消息或1xCSFB请求消息，则所述UE附着的MME的标识信息为所述UE附着的MME的MMEC信息，所述UE的标识信息为所述UE的S-TMSI信息，或者，若所述服务请求消息为所述UE的TAU请求消息，则所述UE附着的MME的标识信息为所述UE附着的MME分 配给所述UE的全球唯一临时用户设备标识(Globally Unique Temporary UE Identity，GUTI)信息，所述GUTI信息包含所述UE附着的MME的MMEC信息，所述UE的标识信息为所述UE的S-TMSI信息。
需要说明的是，所述查询请求消息中包含的所述UE附着的MME的标识，标识所述UE请求所述UE附着的MME为所述UE提供服务，在现有技术中，当UE附着的MME发生故障后，为UE提供服务的eNodeB会将UE的服务请求消息发送至MME池区中的另一个MME，可称服务MME，该MME由于没有UE的用户信息会拒绝UE的服务请求，此时UE通过重新附着流程附着到该服务MME上，UE再次发起服务请求，此时UE发起的服务请求消息中包含的是所述服务MME的标识，表示所述UE请求所述服务MME为所述UE提供服务。
503、所述服务MME根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
具体的，当所述服务MME获取所述UE的用户信息之后，所述服务MME还需要根据所述UE的用户信息判断所述UE是否是合法UE，若不是，所述服务MME直接拒绝所述UE的服务请求，若是，所述服务MME还需要向与所述服务MME相连的SGW和HSS发送修改请求消息，所述修改请求消息中携带所述UE的标识信息，所述修改请求消息用于请求所述SGW和所述HSS将所述UE与所述UE附着的MME的对应关系修改为所述UE和所述服务MME的对应关系。并且，所述服务MME还需要为所述UE重分配GUTI，以使得所述UE附着在所述服务MME上，以使得之后所述UE的所有业务都由所述服务MME来完成。
需要说明的是，所述服务MME延迟预设时间向所述HSS发送所述修改请求消息。这样做的原因是，UE附着的MME上附着的用户是数以万计的，当UE附着的MME发生故障后，附着在原MME上的UE都需要MME池区中正常工作的MME为所述UE提供服务， 此时，若每个服务MME都向HSS发送修改请求消息，会导致HSS在短时间内接收大量的修改请求消息，导致HSS的负载较大，可能造成拥塞现象的产生，又由于HSS是LTE核心网中的重要网元，HSS的拥塞会为网络业务的处理带来极大的影响，因此，服务MME会延迟预设时间向所述HSS发送所述修改请求消息，以避免所述HSS在短时间内的负荷突然增大。
举例来说，当UE附着的MME上附着有一万个用户且所述UE附着的MME发生故障时，所述HSS可能要接收到一万条所述修改请求消息，导致所述HSS的负荷突然增大，造成拥塞，但是，若所述服务MME通过延时发送所述修改请求，每秒钟发送100条所述修改请求，分为100秒将所述修改请求发送至所述HSS，就可以减少HSS在单位时间内的负荷，减少对HSS的冲击。
进一步的，HSS还承担有大量其他业务，例如，当所述UE作为VoLTE的被叫时，所述HSS还要完成域选流程，确定所述UE当前所在的域的信息，若所述HSS拥塞，则所述UE的VoLTE被叫业务就会失败。
并且，若所述HSS在接收所述服务MME的修改请求之前要执行所述UE的VoLTE被叫业务，所述HSS会在池区内选择任一正常工作的MME来获得上述域选流程所需要的UE的信息，并不会使得UE的被叫业务失败。
进一步的，在本发明实施例中，若UE在2G/3G网络的CS域核心网MSC网元注册过，服务MME还需要向MSC发送位置更新请求消息，用于更新在MSC上注册的MME信息。若UE在CDMA2000网络的核心网1xCS IWS网元注册过，服务MME还需要向1xCS IWS发送MME变更通知消息，用于更新在1xCS IWS上注册的MME信息。
在本发明实施例中，服务MME还需要向为UE提供服务的基站发送指示消息，指示所述基站建立无线侧的链路与承载，并向SGW发送请求消息，请求建立与SGW接口的隧道。
进一步的，若2G/3G网络的CS域核心网网元MSC所述UE重分配了TMSI，所述服务MME还需要指示所述UE重新建立IMSI与TMSI的对应关系。
在本发明实施例中，当UE需要进行回落到宽带码分多址(Wideband Code Division Multiple Access，WCDMA)网络的电路域交换回落(Circuit Switched Fallback，CSFB)主叫业务，或者回落到WCDMA2000网络的1xCSFB主叫业务，所述服务MME指示所述基站将所述UE进行电路域的回落。
本发明实施例提供了一种业务容灾的方法，在该方法中，当UE附着的MME发生故障且为该UE提供服务的基站检测到这一故障后，所述基站将所述UE的服务请求消息发送至所述UE附着的MME所在池区内的其他正常MME作为所述UE的服务MME，当所述服务MME为所述UE附着的MME的备份MME时，所述服务MME根据所述UE的标识信息从自身的存储空间中获取所述UE的用户信息，若所述服务MME不是所述UE附着的MME的备份MME，所述服务MME获取所述UE附着的MME的备份MME的信息并向所述备份MME请求所述UE的用户信息，所述服务MME根据所述UE的用户信息为所述UE提供服务，以使得所述UE的业务能够一次成功，并且通过延时向HSS发送注册请求达到了避免HSS拥塞的效果，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图6，本发明实施例还提供了一种业务容灾的方法，该方法包括：
601、在用户设备UE附着的移动管理实体MME故障后，服务MME接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中。
当所述UE作为CSFB/1xCSFB的被叫用户时，所述UE回落到的2G/3G网络的CS域的网元向所述UE附着的MME发送寻呼请求消息，以使得所述UE附着的MME寻呼所述UE。
所述2G/3G网络的CS域的网元在所述UE附着的MME发生故障后将所述寻呼请求消息发送至所述UE附着的MME所在池区内的一个正常的MME，由该正常MME作为处理所述寻呼请求消息的服务MME。
需要说明的是，CSFB和1xCSFB都是电路域交换回落，但是分别对应的UE回落到的网络不同，一个对应的是UE回落到宽带码分多址(Wideband Code Division Multiple Access，WCDMA)网络，一个对应的是回落到WCDMA2000网络。
602、所述服务MME根据所述UE的标识获取所述UE的用户信息。
具体的，若所述服务MME即为所述UE附着的MME的备份MME，则所述服务MME在所述UE附着的MME发生故障之前，还会接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识，并记录所述UE的用户信息和所述UE的标识的对应关系；此时，所述服务MME根据所述UE的标识就可以获取所述服务MME保存的所述UE的用户信息。
若所述服务MME不是所述UE附着的MME的备份MME，则所述服务MME向所述MME池区内的所有MME发送广播请求消息，所述广播请求消息中包含所述UE的标识，所述广播消息用于请求获取所述UE的用户信息。只有所述UE附着的MME的备份MME接收到所述广播消息后会向所述服务MME发送广播响应消息，所述广播响应消息中包含所述UE的用户信息。
603、所述服务MME根据所述用户信息获取所述UE所在的跟踪区，并在所述跟踪区内发起寻呼请求。
需要说明的是，在现有技术中，虽然UE回落的2G/3G核心网网元在所述UE附着的MME故障后也会通过预设的策略在MME池 区中另选一个MME作为UE的服务MME发起寻呼请求，但是由于服务MME中没有UE的用户信息，因此服务MME无法获取到UE所在的跟踪区，服务MME只能在多个跟踪区内寻呼该UE，寻呼效率较低。
但是，在本发明中，服务MME根据所述UE的用户信息获取所述UE的跟踪区的信息，在所述UE的跟踪区内发起寻呼流程，大大提高了寻呼的效率。
具体的，本发明详细技术特征可参见上述图5所对应的实施例的技术特征，本发明实施例对此不再赘述。
本发明实施例提供了一种业务容灾的方法，在该方法中，当UE作为CSFB/1xCSFB的被叫用户且所述UE附着的MME发生故障后，所述UE回落到的2G/3G网络的CS域的网元将寻呼请求消息发送至所述MME池区内的其他正常工作的MME，该正常工作的MME作为服务MME对所述寻呼请求消息进行处理。所述服务MME从自身或从所述UE附着的MME的备份MME获取所述UE的用户信息，从所述UE的用户信息中获取所述UE的跟踪区的信息，并在所述跟踪区内发起寻呼流程，从而使得所述UE的CSFB/1xCSFB被叫业务一次成功，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图7，本发明实施例还提供了一种MME，该MME包括：发送单元701，接收单元702和确定单元703；
所述发送单元701，用于向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述接收单元702，用于接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
所述确定单元703，用于根据所述MME池区中所有MME的 MMEC，按照预设的策略，确定所述MME的备份MME；
所述发送单元701还用于：向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述接收单元702还用于：接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息；
所述发送单元701还用于：根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
具体的，所述确定单元703用于：
将所述MME池区中所有MME的MMEC按照MMEC由小到大的顺序进行排序获得排序结果；
将所述排序结果中与所述MME的MMEC相邻，且大于所述MME的MMEC的MME作为所述备份MME，若所述MME的MMEC是所述排序结果中最大的，则所述MME将所述排序结果中MMEC最小的MME作为所述备份MME。
具体的，所述发送单元701用于：
通过所述备份MME的接口信息所对应的接口，向所述备份MME发送备份请求消息，所述备份请求消息中包含所述UE的标识和所述UE的用户信息，所述备份请求消息用于请求所述备份MME对所述UE的用户信息进行备份。
本发明实施例提供了一种MME，当所述MME需要将附着在所述MME上的UE的用户信息进行备份时，所述MME通过FQDN向DNS服务器查询所示MME所在池区内所有MME的MMEC信息，并根据预设的策略获取所述MME的备份MME的信息，并通过向DNS服务器查询备份MME的可用接口信息，通过所述备份MME的可用接口将所述UE的用户信息备份至所述备份MME，以使得当所述MME发生故障后，所述MME池区内的其他MME从所述备份 MME获取所述UE的用户信息，从而为所述UE提供服务，从而使所述UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题.
为解决现有技术业务容灾效果较差的问题，结合图8，本发明实施例还提供了一种DNS服务器，所述DNS服务器包括：接收单元801，第一获取单元802，发送单元803和第二获取单元804；
所述接受单元801，用于接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述第一获取单元802，用于根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC；
所述发送单元803，用于向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME；
所述接收单元801还用于：接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述第二获取单元804，用于根据所述备份MME的MMEC和所述MME池区的池区标识获取所述备份MME的接口信息；
所述发送单元803用于：向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
本发明实施例提供了一种DNS服务器，DNS服务器中预配置有MME池区内所有MME的MMEC信息以及所有MME的可用接口信息，当所述MME池区中的MME需要将附着在所述MME上的UE 的用户信息进行备份时，所述MME通过FQDN向DNS服务器查询所属MME所在MME池区内所有MME的MMEC信息，并根据所述所有MME的MMEC信息，通过预设的策略获取所述MME的备份MME的信息。通过向DNS服务器查询备份MME的可用接口信息，通过所述备份MME的可用接口将所述UE的用户信息备份至所述备份MME，以使得当所述MME发生故障后，所述MME池区内的其他MME从所述备份MME获取所述UE的用户信息，从而为所述UE提供服务，从而使所述UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图9，本发明实施例还提供了一种服务MME，所述MME包括：接收单元901，获取单元902和服务单元903；
所述接收单元901，用于在用户设备UE附着的移动管理实体MME发生故障后，接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务，其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述获取单元902，用于根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息；
所述服务单元903，用于根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
可选的，所述接收单元901还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识，并记录所述UE的用户信息和所述UE的标识的对应关系；
所述获取单元902具体用于：根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
具体的，所述获取单元902用于：根据所述UE附着的MME 的标识，获取所述UE附着的MME的备份MME的接口信息，并根据所述UE的标识和所述备份MME的接口信息，从所述备份MME获取所述UE的用户信息，其中，所述备份MME和所述服务MME位于同一个MME池区中。
具体的，所述UE附着的MME的标识为所述UE附着的MME的MME编码MMEC，所述获取单元902具体用于：
向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述服务MME所位于的MME池区的池区标识，所述请求消息用于请求所述MME池区中所有MME的MME编码MMEC；
接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
根据所述UE附着的MME的MMEC，以及所述所有MME的MMEC，按照预设的策略，获取所述UE附着的MME的备份MME；
向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC以及所述MME池区的池区标识，以便于所述DNS服务器根据所述MME池区的池区标识以及所述备份MME的MMEC，获取所述备份MME的接口信息；
收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息。
具体的，所述服务请求消息为所述UE的基于长期演进的语音VoLTE的主叫业务请求消息，或为所述UE的电路域交换回落CSFB请求消息或为所述UE的1xCSFB请求消息；所述UE附着的MME的标识为所述UE附着的MME的MMEC；或者，
所述服务请求消息为所述UE的跟踪区更新TAU请求消息，所述UE附着的MME的标识为所述UE附着的MME分配给所述UE的全球唯一临时用户设备标识GUTI，所述GUTI中包含所述UE附着的MME的MMEC。
具体的所述UE的标识为所述UE的短格式临时移动用户标识S-TMSI。
具体的，所述服务MME还包括：确定单元904和发送单元905；
所述确定单元904，用于根据所述UE的用户信息，确定所述UE为合法用户；
所述发送单元905，用于分别向与所述MME相连的服务网关SGW和家乡用户寄存器HSS发送修改请求消息，所述修改请求消息中包含所述UE的标识，所述修改请求消息用于请求所述SGW或所述HSS将所述UE与所述UE附着的MME的对应关系修改为所述UE和所述服务MME的对应关系；为所述UE重新分配GUTI并将所述重新分配的GUTI发送至所述UE，以使所述UE附着在所述服务MME上。
本发明实施例提供了一种MME，当UE附着的MME发生故障且为该UE提供服务的基站检测到这一故障后，所述基站将所述UE的服务请求消息发送至所述MME，当所述MME为所述UE附着的MME的备份MME时，所述MME根据所述UE的标识信息从自身的存储空间中获取所述UE的用户信息，若所述MME不是所述UE附着的MME的备份MME，所述MME获取所述UE附着的MME的备份MME的信息并向所述备份MME请求所述UE的用户信息，所述MME根据所述UE的用户信息为所述UE提供服务，以使得所述UE的业务能够一次成功，并且通过延时向HSS发送注册请求达到了避免HSS拥塞的效果，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图10，本发明实施例还提供了一种服务MME，所述服务MME包括：接收单元1001，获取单元1002和寻呼单元1003；
所述接收单元1001，用于在用户设备UE附着的移动管理实体MME故障后，接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME， 所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述获取单元1002，用于根据所述UE的标识获取所述UE的用户信息；
所述寻呼单元1003，用于根据所述用户信息获取所述UE所在的跟踪区，并在所述跟踪区内发起寻呼请求。
可选的，所述服务MME还包括：记录单元1004；
所述接收单元1001还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识；
所述记录单元1004，用于记录所述UE的用户信息和所述UE的标识的对应关系；
所述获取单元1002，用于根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
具体的，所述服务MME还包括：发送单元1005；
所述发送单元1005，用于向所述MME池区内的所有MME发送广播请求消息，所述广播请求消息中包含所述UE的标识，所述广播消息用于请求获取所述UE的用户信息；
所述接收单元1001，还用于接收所述UE附着的MME的备份MME的广播响应消息，所述广播响应消息中包含所述UE的用户信息。
本发明实施例提供了一种MME，当UE作为CSFB/1xCSFB的被叫用户且所述UE附着的MME发生故障后，所述UE回落到的2G/3G网络的CS域的网元将寻呼请求消息发送至所述MME，所述MME从自身或从所述UE附着的MME的备份MME获取所述UE的用户信息，从所述UE的用户信息中获取所述UE的跟踪区的信息，并在所述跟踪区内发起寻呼流程，从而使得所述UE的CSFB/1xCSFB被叫业务一次成功，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图11，本发明实施例还提供了一种MME，该MME包括：发送器1105，处理器1102、总线1103，存储器1104和接收器1101；
所述发送器1105，用于向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述接收器1101，用于接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
所述处理器1102通过所述总线1103获得所述存储器1104中的指令，以用于根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME；
所述发送器1105还用于：向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述接收器1101还用于：接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息；
所述处理器1102还用于：根据所述备份MME的接口信息，通过所述发送器1105将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
具体的，所述处理器1102用于：将所述MME池区中所有MME的MMEC按照MMEC由小到大的顺序进行排序获得排序结果；
将所述排序结果中与所述MME的MMEC相邻，且大于所述MME的MMEC的MME作为所述备份MME，若所述MME的MMEC是所述排序结果中最大的，则所述MME将所述排序结果中MMEC最小的MME作为所述备份MME。
具体的，所述处理器1102用于：通过所述备份MME的接口信息所对应的接口，通过所述发送器1105向所述备份MME发送备份请求消息，所述备份请求消息中包含所述UE的标识和所述UE的用户信息，所述备份请求消息用于请求所述备份MME对所述UE的用 户信息进行备份。
本发明实施例提供了一种MME，当所述MME需要将附着在所述MME上的UE的用户信息进行备份时，所述MME通过FQDN向DNS服务器查询所示MME所在池区内所有MME的MMEC信息，并根据预设的策略获取所述MME的备份MME的信息，并通过向DNS服务器查询备份MME的可用接口信息，通过所述备份MME的可用接口将所述UE的用户信息备份至所述备份MME，以使得当所述MME发生故障后，所述MME池区内的其他MME从所述备份MME获取所述UE的用户信息，从而为所述UE提供服务，从而使所述UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题.
为解决现有技术业务容灾效果较差的问题，结合图11，本发明实施例还提供了一种DNS服务器，所述DNS服务器包括：接收器1101，处理器1102，总线1103，存储器1104和发送器1105；
所述接收器1101，用于接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
所述处理器1102通过所述总线1103获取所述存储器1104中的指令，以用于务器根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC；
所述发送器1105，用于向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME；
所述接收器1101还用于：接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
所述处理器1102还用于：根据所述备份MME的MMEC和所 述MME池区的池区标识获取所述备份MME的接口信息；
所述发送器1105还用于：向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
本发明实施例提供了一种DNS服务器，DNS服务器中预配置有MME池区内所有MME的MMEC信息以及所有MME的可用接口信息，当所述MME池区中的MME需要将附着在所述MME上的UE的用户信息进行备份时，所述MME通过FQDN向DNS服务器查询所属MME所在MME池区内所有MME的MMEC信息，并根据所述所有MME的MMEC信息，通过预设的策略获取所述MME的备份MME的信息。通过向DNS服务器查询备份MME的可用接口信息，通过所述备份MME的可用接口将所述UE的用户信息备份至所述备份MME，以使得当所述MME发生故障后，所述MME池区内的其他MME从所述备份MME获取所述UE的用户信息，从而为所述UE提供服务，从而使所述UE的业务能够一次成功，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图11，本发明实施例还提供了一种MME，所述MME包括：接收器1101，处理器1102，总线1103和存储器1104；
所述接收器1101，用于在用户设备UE附着的移动管理实体MME发生故障后，服务MME接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务，其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述处理器1102通过所述总线1103获取所述存储器1104中的指令，以用于根据所述UE的标识或者根据所述UE的标识和所述 UE附着的MME的标识，获取所述UE的用户信息；
根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
具体的，所述接收器1101还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识；
所述处理器1102具体用于：并记录所述UE的用户信息和所述UE的标识的对应关系；
根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
具体的，所述处理器1102用于：根据所述UE附着的MME的标识，获取所述UE附着的MME的备份MME的接口信息，并根据所述UE的标识和所述备份MME的接口信息，从所述备份MME获取所述UE的用户信息，其中，所述备份MME和所述服务MME位于同一个MME池区中。
具体的，所述UE附着的MME的标识为所述UE附着的MME的MME编码MMEC，所述服务MME还包括：发送器11051305；
所述发送器1105，用于向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述服务MME所位于的MME池区的池区标识，所述请求消息用于请求所述MME池区中所有MME的MME编码MMEC；
所述接收器1101，用于接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
所述处理器1102，用于根据所述UE附着的MME的MMEC，以及所述所有MME的MMEC，按照预设的策略，获取所述UE附着的MME的备份MME；
所述发送器1105，还用于向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC以及所述MME池区的池区标识，以便于所述DNS服务器根据所述MME池区 的池区标识以及所述备份MME的MMEC，获取所述备份MME的接口信息；
所述接收器1101，还用于接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息。
具体的，所述服务请求消息为所述UE的基于长期演进的语音VoLTE的主叫业务请求消息，或为所述UE的电路域交换回落CSFB请求消息或为所述UE的1xCSFB请求消息；所述UE附着的MME的标识为所述UE附着的MME的MMEC；或者，
所述服务请求消息为所述UE的跟踪区更新TAU请求消息，所述UE附着的MME的标识为所述UE附着的MME分配给所述UE的全球唯一临时用户设备标识GUTI，所述GUTI中包含所述UE附着的MME的MMEC。
具体的，所述UE的标识为所述UE的短格式临时移动用户标识S-TMSI。
具体的，所述处理器1102还用于：
根据所述UE的用户信息，确定所述UE为合法用户；
所述发送器1105还用于：分别向与所述MME相连的服务网关SGW和家乡用户寄存器HSS发送修改请求消息，所述修改请求消息中包含所述UE的标识，所述修改请求消息用于请求所述SGW或所述HSS将所述UE与所述UE附着的MME的对应关系修改为所述UE和所述服务MME的对应关系；
所述处理器1102还用于：为所述UE重新分配GUTI并将所述重新分配的GUTI通过所述发送器1105发送至所述UE，以使所述UE附着在所述服务MME上。
本发明实施例提供了一种MME，当UE附着的MME发生故障且为该UE提供服务的基站检测到这一故障后，所述基站将所述UE的服务请求消息发送至所述MME，当所述MME为所述UE附着的MME的备份MME时，所述MME根据所述UE的标识信息从自身的存储空间中获取所述UE的用户信息，若所述MME不是所述UE 附着的MME的备份MME，所述MME获取所述UE附着的MME的备份MME的信息并向所述备份MME请求所述UE的用户信息，所述MME根据所述UE的用户信息为所述UE提供服务，以使得所述UE的业务能够一次成功，并且通过延时向HSS发送注册请求达到了避免HSS拥塞的效果，解决了现有技术业务容灾效果较差的问题。
为解决现有技术业务容灾效果较差的问题，结合图11，本发明实施例还提供了一种MME，所述MME包括：接收器1101，处理器1102，总线1103、存储器1104和发送器1105；
所述接收器1101，用于在用户设备UE附着的移动管理实体MME故障后，接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
所述处理器1102通过所述总线1103获取所述存储器1104中的指令，以用于根据所述UE的标识获取所述UE的用户信息；
根据所述用户信息获取所述UE所在的跟踪区，并通过所述发送器1105在所述跟踪区内发起寻呼请求。
具体的，所述接收器1101还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识；
所述处理器1102具体用于：记录所述UE的用户信息和所述UE的标识的对应关系；
根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
具体的，所述发送器1105还用于：
向所述MME池区内的所有MME发送广播请求消息，所述广播请求消息中包含所述UE的标识，所述广播消息用于请求获取所述UE的用户信息；
所述接收器1101还用于：接收所述UE附着的MME的备份MME的广播响应消息，所述广播响应消息中包含所述UE的用户信息。
本发明实施例提供了一种MME，当UE作为CSFB/1xCSFB的被叫用户且所述UE附着的MME发生故障后，所述UE回落到的2G/3G网络的CS域的网元将寻呼请求消息发送至所述MME，所述MME从自身或从所述UE附着的MME的备份MME获取所述UE的用户信息，从所述UE的用户信息中获取所述UE的跟踪区的信息，并在所述跟踪区内发起寻呼流程，从而使得所述UE的CSFB/1xCSFB被叫业务一次成功，解决了现有技术业务容灾效果较差的问题。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (28)

  1. 一种业务容灾的方法，其特征在于，该方法包括：
    移动管理实体MME向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
    所述MME接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
    所述MME根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME；
    所述MME向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
    所述MME接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息；
    所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
  2. 根据权利要求1所述的方法，其特征在于，所述MME根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME具体包括：
    所述MME将所述MME池区中所有MME的MMEC按照MMEC由小到大的顺序进行排序获得排序结果；
    所述MME将所述排序结果中与所述MME的MMEC相邻，且大于所述MME的MMEC的MME作为所述备份MME，若所述MME的MMEC是所述排序结果中最大的，则所述MME将所述排序结果中MMEC最小的MME作为所述备份MME。
  3. 根据权利要求1或2所述的方法，其特征在于，所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME具体包括：
    所述MME通过所述备份MME的接口信息所对应的接口，向所述备份MME发送备份请求消息，所述备份请求消息中包含所述UE的标识和所述UE的用户信息，所述备份请求消息用于请求所述备份MME对所述UE的用户信息进行备份。
  4. 一种业务容灾的方法，其特征在于，该方法包括：
    域名服务***DNS服务器接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
    所述DNS服务器根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC，并向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME；
    所述DNS服务器接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
    所述DNS服务器根据所述备份MME的MMEC和所述MME池区的池区标识获取所述备份MME的接口信息，并向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
  5. 一种业务容灾的方法，其特征在于，该方法包括：
    在用户设备UE附着的移动管理实体MME发生故障后，服务MME接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务，其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和 所述服务MME位于同一个MME池区中；
    所述服务MME根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息；
    所述服务MME根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
  6. 根据权利要求5所述的方法，其特征在于，在所述用户设备UE附着的移动管理实体MME故障之前，所述方法还包括：
    所述服务MME接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识，并记录所述UE的用户信息和所述UE的标识的对应关系；
    则所述服务MME根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息具体包括：
    所述服务MME根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
  7. 根据权利要求5所述的方法，其特征在于，所述服务MME根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息包括：
    所述服务MME根据所述UE附着的MME的标识，获取所述UE附着的MME的备份MME的接口信息，并根据所述UE的标识和所述备份MME的接口信息，从所述备份MME获取所述UE的用户信息，其中，所述备份MME和所述服务MME位于同一个MME池区中。
  8. 根据权利要求7所述的方法，其特征在于，所述UE附着的MME的标识为所述UE附着的MME的MME编码MMEC；
    则所述服务MME根据所述UE附着的MME的标识，获取所述UE附着的MME的备份MME的接口信息具体包括：
    所述MME向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述服务MME所位于的MME池区的池区标识，所述请求消息用于请求所述MME池区中所有MME的MME编码MMEC；
    所述服务MME接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
    所述服务MME根据所述UE附着的MME的MMEC，以及所述所有MME的MMEC，按照预设的策略，获取所述UE附着的MME的备份MME，并向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC以及所述MME池区的池区标识，以便于所述DNS服务器根据所述MME池区的池区标识以及所述备份MME的MMEC，获取所述备份MME的接口信息；
    所述服务MME接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息。
  9. 根据权利要求5-8任一项所述的方法，其特征在于，所述服务请求消息为所述UE的基于长期演进的语音VoLTE的主叫业务请求消息，或为所述UE的电路域交换回落CSFB请求消息或为所述UE的1xCSFB请求消息；所述UE附着的MME的标识为所述UE附着的MME的MMEC；或者，
    所述服务请求消息为所述UE的跟踪区更新TAU请求消息，所述UE附着的MME的标识为所述UE附着的MME分配给所述UE的全球唯一临时用户设备标识GUTI，所述GUTI中包含所述UE附着的MME的MMEC。
  10. 根据权利要求5-9任一项所述的方法，其特征在于，所述UE的标识为所述UE的短格式临时移动用户标识S-TMSI。
  11. 根据权利要求5-10任一项所述的方法，其特征在于，所述服务MME根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息之后，所述方法还包括：
    所述服务MME根据所述UE的用户信息，确定所述UE为合法用户；
    所述服务MME分别向与所述MME相连的服务网关SGW和家乡用户寄存器HSS发送修改请求消息，所述修改请求消息中包含所述UE的标识，所述修改请求消息用于请求所述SGW或所述HSS将 所述UE与所述UE附着的MME的对应关系修改为所述UE和所述服务MME的对应关系；
    所述服务MME为所述UE重新分配GUTI并将所述重新分配的GUTI发送至所述UE，以使所述UE附着在所述服务MME上。
  12. 一种业务容灾的方法，其特征在于，该方法包括：
    在用户设备UE附着的移动管理实体MME故障后，服务MME接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
    所述服务MME根据所述UE的标识获取所述UE的用户信息；
    所述服务MME根据所述用户信息获取所述UE所在的跟踪区，并在所述跟踪区内发起寻呼请求。
  13. 根据权利要求12所述的方法，其特征在于，在所述用户设备UE附着的移动管理实体MME故障之前，所述方法还包括：
    所述服务MME接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识，并记录所述UE的用户信息和所述UE的标识的对应关系；
    则所述服务MME根据所述UE的标识获取所述UE的用户信息具体包括：
    所述服务MME根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
  14. 根据权利要求12所述的方法，其特征在于，所述服务MME根据所述UE的标识获取所述UE的用户信息具体包括：
    所述服务MME向所述MME池区内的所有MME发送广播请求消息，所述广播请求消息中包含所述UE的标识，所述广播消息用于请求获取所述UE的用户信息；
    所述MME接收所述UE附着的MME的备份MME的广播响应消息，所述广播响应消息中包含所述UE的用户信息。
  15. 一种移动管理实体MME，其特征在于，所述MME包括：发送单元，接收单元和确定单元；
    所述发送单元，用于向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
    所述接收单元，用于接收所述DNS服务器发送的请求响应消息，所述请求响应消息中包含所述MME池区中所有MME的MMEC；
    所述确定单元，用于根据所述MME池区中所有MME的MMEC，按照预设的策略，确定所述MME的备份MME；
    所述发送单元还用于：向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
    所述接收单元还用于：接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息；
    所述发送单元还用于：根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
  16. 根据权利要求15所述的MME，其特征在于，所述确定单元具体用于：
    将所述MME池区中所有MME的MMEC按照MMEC由小到大的顺序进行排序获得排序结果；
    将所述排序结果中与所述MME的MMEC相邻，且大于所述MME的MMEC的MME作为所述备份MME，若所述MME的MMEC是所述排序结果中最大的，则所述MME将所述排序结果中MMEC最小的MME作为所述备份MME。
  17. 根据权利要求15或16所述的MME，其特征在于，所述发 送单元具体用于：
    通过所述备份MME的接口信息所对应的接口，向所述备份MME发送备份请求消息，所述备份请求消息中包含所述UE的标识和所述UE的用户信息，所述备份请求消息用于请求所述备份MME对所述UE的用户信息进行备份。
  18. 一种域名服务***DNS服务器，其特征在于，所述DNS服务器包括：接收单元，第一获取单元，发送单元和第二获取单元；
    所述接受单元，用于接收移动管理实体MME发送的请求消息，所述请求消息中包含所述MME所位于的MME池区的池区标识，所述请求消息用于请求获取所述MME池区中所有MME的MME编码MMEC；
    所述第一获取单元，用于根据所述MME池区的池区标识，获取所述MME池区的池区标识所对应的MME池区中的所有MME的MMEC；
    所述发送单元，用于向所述MME发送请求响应消息，所述请求响应消息中包含所述所有MME的MMEC，以便所述MME根据所述所有MME的MMEC确定所述MME的备份MME；
    所述接收单元还用于：接收所述MME发送的接口请求消息，所述接口请求消息包含所述备份MME的MMEC和所述MME池区的池区标识，所述接口请求消息用于请求获取所述备份MME的接口信息；
    所述第二获取单元，用于根据所述备份MME的MMEC和所述MME池区的池区标识获取所述备份MME的接口信息；
    所述发送单元用于：向所述MME发送接口响应消息，所述接口响应消息中包含所述备份MME的接口信息，以便所述MME根据所述备份MME的接口信息，将附着在所述MME上的用户设备UE的用户信息发送至所述备份MME。
  19. 一种服务移动管理实体MME，其特征在于，所述服务MME包括：接收单元，获取单元和服务单元；
    所述接收单元，用于在用户设备UE附着的移动管理实体MME 发生故障后，接收所述UE通过演进基站eNodeB发送的服务请求消息，所述服务请求消息包含所述UE的标识和所述UE附着的MME的标识，所述服务请求消息用于请求所述UE附着的MME为所述UE提供服务，其中，所述服务MME是所述eNodeB在所述UE附着的MME故障后，选择的为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
    所述获取单元，用于根据所述UE的标识或者根据所述UE的标识和所述UE附着的MME的标识，获取所述UE的用户信息；
    所述服务单元，用于根据所述UE的用户信息为所述UE提供所述服务请求消息所对应的服务。
  20. 根据权利要求19所述的服务MME，其特征在于，所述接收单元还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识，并记录所述UE的用户信息和所述UE的标识的对应关系；
    所述获取单元具体用于：根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
  21. 根据权利要求19所述的服务MME，其特征在于，所述获取单元具体用于：
    根据所述UE附着的MME的标识，获取所述UE附着的MME的备份MME的接口信息，并根据所述UE的标识和所述备份MME的接口信息，从所述备份MME获取所述UE的用户信息，其中，所述备份MME和所述服务MME位于同一个MME池区中。
  22. 根据权利要求21所述的服务MME，其特征在于，所述UE附着的MME的标识为所述UE附着的MME的MME编码MMEC，所述获取单元具体用于：
    向域名服务***DNS服务器发送请求消息，所述请求消息中包含所述服务MME所位于的MME池区的池区标识，所述请求消息用于请求所述MME池区中所有MME的MME编码MMEC；
    接收所述DNS服务器发送的请求响应消息，所述请求响应消息 中包含所述MME池区中所有MME的MMEC；
    根据所述UE附着的MME的MMEC，以及所述所有MME的MMEC，按照预设的策略，获取所述UE附着的MME的备份MME；
    向所述DNS服务器发送接口请求消息，所述接口请求消息中包含所述备份MME的MMEC以及所述MME池区的池区标识，以便于所述DNS服务器根据所述MME池区的池区标识以及所述备份MME的MMEC，获取所述备份MME的接口信息；
    接收所述DNS服务器发送的接口响应消息，所述接口响应消息中包含所述备份MME的接口信息。
  23. 根据权利要求19至权利要求22中的任一项所述的服务MME，其特征在于，所述服务请求消息为所述UE的基于长期演进的语音VoLTE的主叫业务请求消息，或为所述UE的电路域交换回落CSFB请求消息或为所述UE的1xCSFB请求消息；所述UE附着的MME的标识为所述UE附着的MME的MMEC；或者，
    所述服务请求消息为所述UE的跟踪区更新TAU请求消息，所述UE附着的MME的标识为所述UE附着的MME分配给所述UE的全球唯一临时用户设备标识GUTI，所述GUTI中包含所述UE附着的MME的MMEC。
  24. 根据权利要求19至权利要求23中的任一项所述的服务MME，其特征在于，所述UE的标识为所述UE的短格式临时移动用户标识S-TMSI。
  25. 根据权利要求19至权利要求24中的任一项所述的服务MME，其特征在于，所述服务MME还包括：确定单元和发送单元；
    所述确定单元，用于根据所述UE的用户信息，确定所述UE为合法用户；
    所述发送单元，用于分别向与所述MME相连的服务网关SGW和家乡用户寄存器HSS发送修改请求消息，所述修改请求消息中包含所述UE的标识，所述修改请求消息用于请求所述SGW或所述HSS将所述UE与所述UE附着的MME的对应关系修改为所述UE和所述 服务MME的对应关系；为所述UE重新分配GUTI并将所述重新分配的GUTI发送至所述UE，以使所述UE附着在所述服务MME上。
  26. 一种服务移动管理实体MME，其特征在于，所述服务MME包括：接收单元，获取单元和寻呼单元；
    所述接收单元，用于在用户设备UE附着的移动管理实体MME故障后，接收第二代移动通信技术2G或第三代移动通信技术3G网络的电路交换CS域的核心网网元发送的寻呼请求消息，所述寻呼请求消息中包含所述UE的标识，所述寻呼请求消息用于请求对所述UE发起CSFB或1xCSFB寻呼，其中，所述服务MME是当所述UE附着的MME发生故障时，为所述UE提供服务的MME，所述UE附着的MME和所述服务MME位于同一个MME池区中；
    所述获取单元，用于根据所述UE的标识获取所述UE的用户信息；
    所述寻呼单元，用于根据所述用户信息获取所述UE所在的跟踪区，并在所述跟踪区内发起寻呼请求。
  27. 根据权利要求26所述的服务MME，其特征在于，所述服务MME还包括：记录单元；
    所述接收单元还用于：接收所述UE附着的MME发送的所述UE的用户信息和所述UE的标识；
    所述记录单元，用于记录所述UE的用户信息和所述UE的标识的对应关系；
    所述获取单元，用于根据所述UE的标识，获取所述服务MME保存的所述UE的用户信息。
  28. 根据权利要求26所述的服务MME，其特征在于，所述服务MME还包括：发送单元；
    所述发送单元，用于向所述MME池区内的所有MME发送广播请求消息，所述广播请求消息中包含所述UE的标识，所述广播消息用于请求获取所述UE的用户信息；
    所述接收单元，还用于接收所述UE附着的MME的备份MME 的广播响应消息，所述广播响应消息中包含所述UE的用户信息。
PCT/CN2015/072051 2015-01-30 2015-01-30 一种业务容灾的方法和相关装置 WO2016119263A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2017540599A JP6487563B2 (ja) 2015-01-30 2015-01-30 サービス冗長方法および関係付けられた装置
CN201910975917.6A CN110830288B (zh) 2015-01-30 2015-01-30 一种业务容灾的方法和相关装置
PCT/CN2015/072051 WO2016119263A1 (zh) 2015-01-30 2015-01-30 一种业务容灾的方法和相关装置
EP15879471.9A EP3253090B1 (en) 2015-01-30 2015-01-30 Mme recovery
CN201580001104.7A CN105556900B (zh) 2015-01-30 2015-01-30 一种业务容灾的方法和相关装置
KR1020177024067A KR101974022B1 (ko) 2015-01-30 2015-01-30 서비스 리던던시 방법 및 관련 장치
US15/664,986 US10405206B2 (en) 2015-01-30 2017-07-31 Service redundancy method and related apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/072051 WO2016119263A1 (zh) 2015-01-30 2015-01-30 一种业务容灾的方法和相关装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/664,986 Continuation US10405206B2 (en) 2015-01-30 2017-07-31 Service redundancy method and related apparatus

Publications (1)

Publication Number Publication Date
WO2016119263A1 true WO2016119263A1 (zh) 2016-08-04

Family

ID=55833996

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072051 WO2016119263A1 (zh) 2015-01-30 2015-01-30 一种业务容灾的方法和相关装置

Country Status (6)

Country Link
US (1) US10405206B2 (zh)
EP (1) EP3253090B1 (zh)
JP (1) JP6487563B2 (zh)
KR (1) KR101974022B1 (zh)
CN (2) CN105556900B (zh)
WO (1) WO2016119263A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108966291A (zh) * 2017-05-17 2018-12-07 中兴通讯股份有限公司 电路域回落的恢复方法、装置、移动管理实体及用户终端

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10805217B2 (en) * 2015-11-10 2020-10-13 At&T Intellectual Property I, L.P. Control plane device selection for broadcast session exchange
CN108616913A (zh) * 2016-12-15 2018-10-02 ***通信集团河南有限公司 一种呼叫处理方法、装置及***
CN108616949A (zh) * 2016-12-15 2018-10-02 ***通信集团河南有限公司 一种呼叫处理方法、装置、mme及***
CN108668307B (zh) * 2017-03-29 2021-04-27 ***通信集团上海有限公司 被叫业务恢复处理方法、移动性管理实体及服务网关
CN109996268B (zh) * 2017-12-29 2022-05-31 ***通信集团四川有限公司 通信链路连接方法、装置、设备及介质
CN108924814A (zh) * 2018-06-06 2018-11-30 武汉虹信通信技术有限责任公司 一种基于移动管理实体池的容灾方法
CN110944029B (zh) * 2018-09-25 2021-12-17 华为技术有限公司 数据备份方法、装置及通信***
CN111263355B (zh) * 2018-12-03 2021-07-06 大唐移动通信设备有限公司 Guti分配方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012071695A1 (zh) * 2010-11-29 2012-06-07 华为技术有限公司 节点故障处理方法、***及相关设备
CN103238345A (zh) * 2012-10-31 2013-08-07 华为技术有限公司 一种基于移动管理实体池MME Pool的通信方法、设备及***

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355793B (zh) * 2007-07-27 2011-08-31 华为技术有限公司 识别用户设备的方法和装置及临时标识传递和分配方法
WO2009129465A2 (en) * 2008-04-17 2009-10-22 Alnylam Pharmaceuticals, Inc. Compositions and methods for inhibiting expression of xbp-1 gene
JP5121624B2 (ja) * 2008-08-08 2013-01-16 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法及び回線交換局
US8264956B2 (en) * 2009-02-27 2012-09-11 Cisco Technology, Inc. Service redundancy in wireless networks
US8331224B2 (en) * 2009-11-23 2012-12-11 Telefonaktiebolaget L M Ericsson (Publ) Self-management of mobility management entity (MME) pools
KR20110064407A (ko) * 2009-12-08 2011-06-15 삼성전자주식회사 이동통신시스템에서 서비스 제공 방법 및 이를 위한 시스템
US20110235505A1 (en) * 2010-03-29 2011-09-29 Hitachi, Ltd. Efficient deployment of mobility management entity (MME) with stateful geo-redundancy
JP5524410B2 (ja) * 2010-05-11 2014-06-18 エヌイーシー ヨーロッパ リミテッド Ｌｔｅ／ｅｐｃネットワークにおけるｍｍｅの障害を処理する方法
US8375245B2 (en) * 2010-07-15 2013-02-12 Verizon Patent And Licensing Inc. Mobility management entity failover
US8634832B2 (en) * 2010-08-09 2014-01-21 Telefonaktiebolaget L M Ericsson (Publ) Mobile location recovery for MSC pooling
EP2615874A1 (en) * 2010-09-08 2013-07-17 Huawei Technologies Co., Ltd. Paging processing method and system, serving gateway
US20130235805A1 (en) * 2010-11-14 2013-09-12 Telefonaktiebolaget L M Ericsson (Publ) Circuit switched fallback paging for mobility management entity pool
CN102804910A (zh) * 2011-03-21 2012-11-28 华为技术有限公司 连接建立方法、故障处理方法、通信***及相关设备
US8700002B2 (en) * 2012-01-20 2014-04-15 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (MME) resiliency
US8908603B2 (en) * 2012-01-24 2014-12-09 Telefonaktiebolaget L M Ericsson (Publ) MME restoration
CN103841545B (zh) * 2012-11-27 2017-12-29 华为技术有限公司 一种mme池场景能力信息上报的方法及装置
WO2016111565A1 (en) * 2015-01-07 2016-07-14 Lg Electronics Inc. Method and apparatus for optimizing load re-balancing for dedicated core network in wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012071695A1 (zh) * 2010-11-29 2012-06-07 华为技术有限公司 节点故障处理方法、***及相关设备
CN103238345A (zh) * 2012-10-31 2013-08-07 华为技术有限公司 一种基于移动管理实体池MME Pool的通信方法、设备及***

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108966291A (zh) * 2017-05-17 2018-12-07 中兴通讯股份有限公司 电路域回落的恢复方法、装置、移动管理实体及用户终端
CN108966291B (zh) * 2017-05-17 2021-06-11 中兴通讯股份有限公司 电路域回落的恢复方法、装置、移动管理实体及用户终端

Also Published As

Publication number Publication date
KR20170108128A (ko) 2017-09-26
CN105556900A (zh) 2016-05-04
CN105556900B (zh) 2019-11-05
EP3253090A1 (en) 2017-12-06
CN110830288B (zh) 2022-07-19
EP3253090A4 (en) 2018-03-14
EP3253090B1 (en) 2021-07-28
CN110830288A (zh) 2020-02-21
JP2018507634A (ja) 2018-03-15
US20170332257A1 (en) 2017-11-16
KR101974022B1 (ko) 2019-08-23
US10405206B2 (en) 2019-09-03
JP6487563B2 (ja) 2019-03-20

Similar Documents

Publication Publication Date Title
WO2016119263A1 (zh) 一种业务容灾的方法和相关装置
US9264948B2 (en) Method and device for accessing and obtaining user equipment context and user equipment identity
DK2702793T3 (en) Improvements to completed mobile calls
US9210226B2 (en) Method and device for location management of group-based machine type communication MTC device
JP5432314B2 (ja) ユーザ装置を識別するための方法および装置ならびに一時的識別情報を伝送し、割り当てるための方法
US9014708B2 (en) Network entity for mobile communications towards a mobile station
EP2583508B1 (en) P-gw/ggsn issued paging requests
EP2003913B1 (en) A call recovery method during the network failure and the system thereof
US9667481B2 (en) Correlation identifier for user plane congestion and other use cases
CN102714615B (zh) 节点故障处理方法、***及相关设备
JP2016541174A (ja) ネットワーク選択方法およびコアネットワーク装置
WO2009140919A1 (zh) 一种基于无线分组网关的容灾方法、设备及***
JP2013537375A (ja) ページング処理方法およびシステム、サービングゲートウェイ
WO2013139235A1 (zh) 一种寻呼方法及装置
CN101534500A (zh) 一种寻址方法、网元设备及网络***
WO2010048881A1 (zh) 网络故障时用户业务接续的方法、装置及***
CN109996268B (zh) 通信链路连接方法、装置、设备及介质
WO2015010516A1 (zh) 电路域回落业务中的漫游处理方法及网元

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201580001104.7

Country of ref document: CN

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

Ref document number: 15879471

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017540599

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015879471

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20177024067

Country of ref document: KR

Kind code of ref document: A