TECHNICAL FIELD
[0001] The present invention relates to the field of communications technologies, and in
particular, to a service redundancy method and a related apparatus.
BACKGROUND
[0002] In a Long Term Evolution (Long Term Evolution, LTE) network architecture, multiple
MMEs in a mobility management entity (Mobility Management Entity, MME) pool (Pool)
simultaneously serve a same wireless area, where each MME in the MME Pool is interconnected
with all base stations in the MME Pool, and the MMEs in the MME Pool share resources,
and share service load.
[0003] When an MME in the MME Pool becomes faulty, if user equipment (User Equipment, UE)
attached to the faulty MME actively initiates a service request, a base station serving
the UE sends, by using a preset policy, for example, a load balancing principle, the
service request of the UE to another MME that works normally in the MME Pool; the
MME that works normally rejects the service request of the UE, and the UE needs to
re-attach to the MME that works normally so as to implement service recovery, thereby
implementing redundancy among MMEs in the MME Pool.
[0004] However, a redundancy effect of the solution provided in the prior art is relatively
poor, for example, when a UE needs to initiate a Voice over Long Term Evolution (Voice
over LTE, VoLTE) mobile originated service, and an MME to which the UE is attached
becomes faulty, a base station that provides a service for the UE sends a VoLTE mobile
originated service request message of the UE to a new MME in the MME Pool, but the
new MME rejects the VoLTE mobile originated service request of the UE. The UE of which
the service request is rejected attaches to the new MME by re-initiating an attach
procedure, and re-initiates a VoLTE mobile originated service, and then the new MME
provides a service for the VoLTE mobile originated service of the UE. This causes
that the VoLTE mobile originated service of the UE cannot succeed at a time. In addition,
after an MME becomes faulty, service requests initiated by all UEs that are attached
to the faulty MME are rejected by a network side, which triggers new attach procedures
of these UEs, and attach procedures generated by a large quantity of users in a relatively
short time bring great signaling impact on other network elements, such as a home
subscriber server (Home Subscriber Server, HSS), in an LTE network, causing HSS congestion.
The HSS is a critical node in the entire network, and HSS congestion causes a failure
in accessing the network by a user, or a sharp decrease in a VoLTE call success rate.
SUMMARY
[0005] Embodiments of the present invention provide a service redundancy method and a related
apparatus, which resolve a problem that a redundancy effect of an existing redundancy
solution is relatively poor.
[0006] To achieve the foregoing objective, the following technical solutions are adopted
in the embodiments of the present invention:
[0007] According to a first aspect, an embodiment of the present invention provides a service
redundancy method, where the method includes:
sending, by a mobility management entity MME, a request message to a domain name system
DNS server, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
receiving, by the MME, a request response message sent by the DNS server, where the
request response message includes the MMECs of all the MMEs in the MME pool;
determining, by the MME, a backup MME of the MME according to the MMECs of all the
MMEs in the MME pool and according to a preset policy;
sending, by the MME, an interface request message to the DNS server, where the interface
request message includes an MMEC of the backup MME and the pool identity of the MME
pool, and the interface request message is used to request to acquire interface information
of the backup MME;
receiving, by the MME, an interface response message sent by the DNS server, where
the interface response message includes the interface information of the backup MME;
and
sending, by the MME according to the interface information of the backup MME, user
information of user equipment UE attached to the MME to the backup MME.
[0008] According to a second aspect, an embodiment of the present invention provides a service
redundancy method, where the method includes:
receiving, by a domain name system DNS server, a request message sent by a mobility
management entity MME, where the request message includes a pool identity of an MME
pool in which the MME is located, and the request message is used to request to acquire
MME codes MMECs of all MMEs in the MME pool;
acquiring, by the DNS server according to the pool identity of the MME pool, the MMECs
of all the MMEs in the MME pool corresponding to the pool identity of the MME pool,
and sending a request response message to the MME, where the request response message
includes the MMECs of all the MMEs, so that the MME determines a backup MME of the
MME according to the MMECs of all the MMEs;
receiving, by the DNS server, an interface request message sent by the MME, where
the interface request message includes an MMEC of the backup MME and the pool identity
of the MME pool, and the interface request message is used to request to acquire interface
information of the backup MME; and
acquiring, by the DNS server, the interface information of the backup MME according
to the MMEC of the backup MME and the pool identity of the MME pool, and sending an
interface response message to the MME, where the interface response message includes
the interface information of the backup MME, so that the MME sends, according to the
interface information of the backup MME, user information of user equipment UE attached
to the MME to the backup MME.
[0009] According to a third aspect, an embodiment of the present invention provides a service
redundancy method, where the method includes:
after a mobility management entity MME to which user equipment UE is attached becomes
faulty, receiving, by a serving MME, a service request message sent by the UE by using
an evolved NodeB eNodeB, where the service request message includes an identity of
the UE and an identity of the MME to which the UE is attached, the service request
message is used to request the MME to which the UE is attached to provide a service
for the UE, the serving MME is an MME selected, after the MME to which the UE is attached
becomes faulty, by the eNodeB to provide a service for the UE, and the MME to which
the UE is attached and the serving MME are located in a same MME pool;
acquiring, by the serving MME, user information of the UE according to the identity
of the UE or according to the identity of the UE and the identity of the MME to which
the UE is attached; and
providing, by the serving MME according to the user information of the UE, the service
corresponding to the service request message for the UE.
[0010] According to a fourth aspect, an embodiment of the present invention provides a service
redundancy method, where the method includes:
after a mobility management entity MME to which user equipment UE is attached becomes
faulty, receiving, by a serving MME, a paging request message sent by a network element
of a core network in a circuit switched CS domain that is in a second-generation mobile
communications technology 2G network or a third-generation mobile communications technology
3G network, where the paging request message includes an identity of the UE, the paging
request message is used to request to initiate CSFB paging or 1xCSF paging on the
UE, the serving MME is an MME that provides a service for the UE when the MME to which
the UE is attached becomes faulty, and the MME to which the UE is attached and the
serving MME are located in a same MME pool;
acquiring, by the serving MME, user information of the UE according to the identity
of the UE; and
acquiring, by the serving MME according to the user information, a tracking area in
which the UE is located, and initiating a paging request in the tracking area.
[0011] According to a fifth aspect, 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, where:
the sending unit is configured to send a request message to a domain name system DNS
server, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
the receiving unit is configured to receive a request response message sent by the
DNS server, where the request response message includes the MMECs of all the MMEs
in the MME pool;
the determining unit is configured to determine a backup MME of the MME according
to the MMECs of all the MMEs in the MME pool and according to a preset policy;
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 the pool identity of the MME pool, and the interface request message is used to
request to acquire 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 the interface
information of the backup MME; and
the sending unit is further configured to send, according to the interface information
of the backup MME, user information of user equipment UE attached to the MME to the
backup MME.
[0012] In a first possible implementation manner, with reference to the fifth aspect, the
determining unit is specifically configured to:
sort the MMECs of all the MMEs in the MME pool according to an ascending order of
the MMECs, to obtain a sorting result; and
use an MME corresponding to an MMEC that is adjacent to an MMEC of the MME and greater
than the MMEC of the MME as the backup MME, and if the MMEC of the MME is the largest
in the sorting result, use an MME of which an MMEC is the smallest in the sorting
result as the backup MME.
[0013] In a second possible implementation manner, with reference to the fifth aspect or
the first possible implementation manner of the fifth aspect, the sending unit is
specifically configured to:
send a backup request message to the backup MME by using an interface corresponding
to the interface information of the backup MME, where the backup request message includes
an identity of the UE and the user information of the UE, and the backup request message
is used to request the backup MME to back up the user information of the UE.
[0014] According to a sixth aspect, an embodiment of the present invention provides a domain
name system DNS server, where the DNS server includes a receiving unit, a first acquiring
unit, a sending unit, and a second acquiring unit, where:
the receiving unit is configured to receive a request message sent by a mobility management
entity MME, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
the first acquiring unit is configured to acquire, according to the pool identity
of the MME pool, the MMECs of all the MMEs in the MME pool corresponding to the pool
identity of the MME pool;
the sending unit is configured to send a request response message to the MME, where
the request response message includes the MMECs of all the MMEs, so that the MME determines
a backup MME of the MME according to the MMECs 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 pool identity of the MME pool, and the interface request message is used to
request to acquire interface information of the backup MME;
the second acquiring unit is configured to acquire the interface information of the
backup MME according to the MMEC of the backup MME and the pool identity of the MME
pool; and
the sending unit is configured to send an interface response message to the MME, where
the interface response message includes the interface information of the backup MME,
so that the MME sends, according to the interface information of the backup MME, user
information of user equipment UE attached to the MME to the backup MME.
[0015] According to a seventh aspect, an embodiment of the present invention provides a
serving mobility management entity MME, where the serving MME includes a receiving
unit, an acquiring unit, and a serving unit, where:
the receiving unit is configured to: after a mobility management entity MME to which
user equipment UE is attached becomes faulty, receive a service request message sent
by the UE by using an evolved NodeB eNodeB, where the service request message includes
an identity of the UE and an identity of the MME to which the UE is attached, the
service request message is used to request the MME to which the UE is attached to
provide a service for the UE, the serving MME is an MME selected, after the MME to
which the UE is attached becomes faulty, by the eNodeB to provide a service for the
UE, and the MME to which the UE is attached and the serving MME are located in a same
MME pool;
the acquiring unit is configured to acquire user information of the UE according to
the identity of the UE or according to the identity of the UE and the identity of
the MME to which the UE is attached; and
the serving unit is configured to provide, according to the user information of the
UE, the service corresponding to the service request message for the UE.
[0016] In a first possible implementation manner, with reference to the seventh aspect,
the receiving unit is further configured to: receive the user information of the UE
and the identity of the UE that are sent by the MME to which the UE is attached, and
record a correspondence between the user information of the UE and the identity of
the UE; and
the acquiring unit is specifically configured to acquire, according to the identity
of the UE, the user information that is of the UE and saved by the serving MME.
[0017] In a second possible implementation manner, with reference to the seventh aspect,
the acquiring unit is specifically configured to:
acquire, according to the identity of the MME to which the UE is attached, interface
information of a backup MME of the MME to which the UE is attached, and acquire, from
the backup MME, the user information of the UE according to the identity of the UE
and the interface information of the backup MME, where the backup MME and the serving
MME are located in a same MME pool.
[0018] In a third possible implementation manner, with reference to the second possible
implementation manner, the identity of the MME to which the UE is attached is an MME
code MMEC of the MME to which the UE is attached, and the acquiring unit is specifically
configured to:
send a request message to a domain name system DNS server, where the request message
includes a pool identity of an MME pool in which the serving MME is located, and the
request message is used to request to acquire MME codes MMECs of all MMEs in the MME
pool;
receive a request response message sent by the DNS server, where the request response
message includes the MMECs of all the MMEs in the MME pool;
acquire, according to the MMEC of the MME to which the UE is attached and the MMECs
of all the MMEs and according to a preset policy, the backup MME of the MME to which
the UE is attached;
send an interface request message to the DNS server, where the interface request message
includes an MMEC of the backup MME and the pool identity of the MME pool, so that
the DNS server acquires the interface information of the backup MME according to the
pool identity of the MME pool and the MMEC of the backup MME; and
receive an interface response message sent by the DNS server, where the interface
response message includes the interface information of the backup MME.
[0019] In a fourth possible implementation manner, with reference to any one of the seventh
aspect to the third possible implementation manner of the seventh aspect, the service
request message is a Voice over Long Term Evolution VoLTE mobile originated service
request message of the UE, or a circuit switched fallback CSFB request message of
the UE, or a 1xCSF request message of the UE, and the identity 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 identity of the MME to which the UE is attached is a globally unique temporary
identity (GUTI) allocated to the UE by the MME to which the UE is attached, where
the GUTI includes the MMEC of the MME to which the UE is attached.
[0020] In a fifth possible implementation manner, with reference to any one of the seventh
aspect to the fourth possible implementation manner of the seventh aspect, the identity
of the UE is a short temporary mobile subscriber identity S-TMSI of the UE.
[0021] In a sixth possible implementation manner, with reference to any one of the seventh
aspect to the fifth possible implementation manner of the seventh aspect, the serving
MME further includes a determining unit and a sending unit, where:
the determining unit is configured to determine, according to the user information
of the UE, that the UE is an authorized user; and
the sending unit is configured to separately send a modification request message to
a serving gateway SGW and a home subscriber server HSS that are connected to the MME,
where the modification request message includes the identity of the UE, and the modification
request message is used to request the SGW or the HSS to modify a correspondence between
the UE and the MME to which the UE is attached to a correspondence between the UE
and the serving MME; and reallocate a GUTI to the UE, and send the reallocated GUTI
to the UE, so that the UE is attached to the serving MME.
[0022] According to an eighth aspect, an embodiment of the present invention provides a
serving MME, where the serving MME includes a receiving unit, an acquiring unit, and
a paging unit, where:
the receiving unit is configured to: after a mobility management entity MME to which
user equipment UE is attached becomes faulty, receive a paging request message sent
by a network element of a core network in a circuit switched CS domain that is in
a second-generation mobile communications technology 2G network or a third-generation
mobile communications technology 3G network, where the paging request message includes
an identity of the UE, the paging request message is used to request to initiate CSFB
paging or 1xCSF paging on the UE, the serving MME is an MME that provides a service
for the UE when the MME to which the UE is attached becomes faulty, and the MME to
which the UE is attached and the serving MME are located in a same MME pool;
the acquiring unit is configured to acquire user information of the UE according to
the identity of the UE; and
the paging unit is configured to acquire, according to the user information, a tracking
area in which the UE is located, and initiate a paging request in the tracking area.
[0023] In a first possible implementation manner, with reference to the eighth aspect, the
serving MME further includes a recording unit, where:
the receiving unit is further configured to receive the user information of the UE
and the identity of the UE that are sent by the MME to which the UE is attached;
the recording unit is configured to record a correspondence between the user information
of the UE and the identity of the UE; and
the acquiring unit is configured to acquire, according to the identity of the UE,
the user information that is of the UE and saved by the serving MME.
[0024] In a second possible implementation manner, with reference to the eighth aspect,
the serving MME further includes a sending unit, where:
the sending unit is configured to send a broadcast request message to all MMEs in
the MME pool, where the broadcast request message includes the identity of the UE,
and the broadcast request message is used to request to acquire the user information
of the UE; and
the receiving unit is further configured to receive a broadcast response message of
a backup MME of the MME to which the UE is attached, where the broadcast response
message includes the user information of the UE.
[0025] The embodiments of the present invention provide a service redundancy method and
a related apparatus, where an MME acquires, from a DNS server, MMECs of all MMEs in
an MME pool in which the MME is located; the MME acquires, by using a preset policy,
a backup MME of the MME according to the MMECs of all the MMEs in the MME pool, and
acquires interface information of the backup MME from the DNS server; the MME backs
up user information of a UE attached to the MME to the backup MME; when the MME becomes
faulty, a network side sends a service request message corresponding to the UE to
an MME that works normally in the MME pool, and the MME that works normally is used
as a serving MME of the UE, where the serving MME can acquire the user information
of the UE from the backup MME, so as to provide a service for the UE, so that a service
of the UE can succeed at a time, which resolves a problem in the prior art that a
service redundancy effect is relatively poor.
BRIEF DESCRIPTION OF DRAWINGS
[0026] To describe the technical solutions in the embodiments of the present invention more
clearly, the following briefly introduces the accompanying drawings required for describing
the embodiments or the prior art. Apparently, the accompanying drawings in the following
description show merely some embodiments of the present invention, and a person of
ordinary skill in the art may still derive other drawings from these accompanying
drawings without creative efforts.
FIG. 1 is a schematic diagram of an LTE network architecture;
FIG. 2 is a flowchart 1 of a service redundancy method;
FIG. 3 is a schematic diagram of an MME chain backup relationship;
FIG. 4 is a flowchart 2 of a service redundancy method;
FIG. 5 is a flowchart 3 of a service redundancy method;
FIG. 6 is a flowchart 4 of a service redundancy method;
FIG. 7 is a schematic diagram of an MME;
FIG. 8 is a schematic diagram of a DNS server;
FIG. 9 is a schematic diagram 1 of a serving MME;
FIG. 10 is a schematic diagram 2 of a serving MME; and
FIG. 11 is a schematic diagram of another MME, or DNS server, or serving MME.
DESCRIPTION OF EMBODIMENTS
[0027] The following clearly describes the technical solutions in the embodiments of the
present invention with reference to the accompanying drawings in the embodiments of
the present invention. Apparently, the described embodiments are merely some but not
all of the embodiments of the present invention. All other embodiments obtained by
a person of ordinary skill in the art based on the embodiments of the present invention
without creative efforts shall fall within the protection scope of the present invention.
[0028] With reference to FIG. 1, an LTE network architecture is exemplarily described. In
a core network in a packet switched (packet switching, PS) domain of the architecture,
an MME 1, an MME 2, and an MME 3 form an MME Pool, and a serving gateway (Serving
Gateway, SGW) and a packet data network gateway (Packet Data Network Gateway, PGW)
form a GW Pool; in addition, the core network in the PS domain of the LTE network
further includes a home subscriber server (Home Subscriber Server, HSS).
[0029] In an access network of this architecture, mobile communications devices are connected
to base stations in an LTE access network, and the base stations in the access network
are connected to MMEs in the MME Pool. It should be noted that a connection relationship
of only some network elements is exemplarily described in FIG. 1, for example, the
HSS actually has a connection relationship with each MME in the MME Pool, and any
two of the MMEs in the MME Pool are connected.
[0030] Service redundancy of a UE can be implemented by using the MME Pool, for example,
when the MME 1 to which a UE 1 is attached becomes faulty, a service request actively
initiated by the UE 1 is sent, by using a base station 1 that provides a service for
the UE 1, to an MME that works normally in the MME pool. It is assumed that the MME
that works normally is the MME 2, the MME 2 rejects a service request of the UE 1
because the MME 2 does not have user information of the UE 1, and the UE 1 re-initiates
an attach procedure and attaches to the MME 2, so that a service of the UE 1 is recovered,
thereby implementing MME redundancy in the MME pool.
[0031] However, a redundancy effect in the prior art is relatively poor, for example, when
the UE 1 initiates a VoLTE mobile originated service, the MME 1 becomes faulty, and
then the base station 1 selects the MME 2 to provide a service for the UE 1. In this
case, the MME 2 does not have user information of the UE 1, and the MME 2 cannot provide
a service for a user; therefore, the MME 2 rejects a VoLTE mobile originated service
request of the UE 1, and only after the UE 1 attaches to the MME 2, the MME 2 can
provide a service for the UE 1. On the one hand, this causes that a VoLTE service
of a UE cannot succeed at a time, causing relatively poor user experience; on the
other hand, after the MME 1 becomes faulty, service requests initiated by all UEs
attached to the MME 1 are rejected by a network side, thereby triggering new attach
procedures of these UEs, and attach procedures of a large quantity of users in a relatively
short time bring great signaling impact on other related network elements in the network,
such as the HSS, causing congestion of the HSS, which causes adverse impact that a
user cannot access the network, or a VoLTE call success rate sharply decreases.
[0032] Specifically, user information of a UE may include subscription data information
of the UE, information corresponding to a service of the UE, and the like. When a
VoLTE mobile originated and terminated service of the UE, a CSFB mobile originated
and terminated service of the UE, and a TAU update service of the UE exist, an MME
may acquire, from the user information of the UE, information required for processing
these services.
[0033] To resolve a problem in the prior art that a redundancy effect is relatively poor,
an embodiment of the present invention provides a service redundancy method; with
reference to FIG. 2, the method includes the following steps:
201. A mobility management entity MME sends a request message to a domain name system
DNS server, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool.
[0034] With reference to FIG. 1, the MME 1, the MME 2, and the MME 3 form an MME Pool, where
the MME Pool is an MME pool (MME Pool) in an LTE network shown in FIG. 1. Specifically,
the LTE network shown in FIG. 1 may also have another MME Pool that is not shown.
[0035] Each MME Pool in the LTE network has a uniquely corresponding MME pool identity (MME
Group ID, MMEGI), and a code of each MME (MME Code, MMEC) in the pool is a unique
identity of the MME in the MME Pool.
[0036] Based on this, one backup MME may be configured for each MME by using a preset policy,
for example, MMECs of all MMEs and information about available interfaces of all the
MMEs are pre-configured in the Domain Name System (DNS) server, MMEC information of
all the MMEs and the information about available interfaces of all the MMEs in the
pool are acquired from the DNS server by an MME in the pool, and a backup MME of the
MME is parsed by using the preset policy.
[0037] Specifically, an identity MMEGI (MME Group ID) of each MME Pool and MMECs of MMEs
in the MME pool are stored in the DNS server. The DNS server divides all MMEs in the
MME pool into at least one group, and allocates, to each group, identity information
LIST_ID that uniquely identifies the group.
[0038] For example, an MMEGI of an MME pool is MMEGI-1, and the MME pool has 10 MMEs, which
are respectively MME 1-MME 10; it is assumed that MMECs of the 10 MMEs are respectively
1-10, and data information related to the MME pool is pre-stored in the DNS server,
for example, MMEGI information of the MME pool. The 10 MMEs are divided into two groups
in advance; identity information LIST_ID corresponding to the first group is LIST_ID-1,
and the first group includes six MMEs of MME 1-MME 6; LIST_ID corresponding to the
second group is LIST_ID-2, and the second group includes four MMEs of MME 7-MME 10.
[0039] Specifically, 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:
ring.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.
org.
[0040] MMEGI is pool identity information of the MME pool in which the MME is located, and
it is assumed that the MMEGI is MMEGI-1. MNC is used to distinguish information about
an operator to which a network belongs, where the MNC includes two decimal numbers,
and a code range is decimal 00-99. For example, an MNC of China Mobile is 00, 02,
04, and 06, an MNC of China Unicom is 01, 05, and 07, and an MNC of China Telecom
is 03. MCC is a mobile country code, and is used to uniquely identify a country to
which a mobile subscriber belongs.
[0041] The DNS server queries, according to MMEGI-1, information about LIST_ID-1 and LIST_ID-2
that are in the foregoing MME pool, and MMEC information of all MMEs in LIST_ID-1
and LIST_ID-2.
[0042] 202. The MME receives a request response message sent by the DNS server, where the
request response message includes the MMECs of all the MMEs in the MME pool.
[0043] Specifically, the request response message sent by the DNS server may be in a form
shown in the following second FQDN:
<interface-name>.ring.mmec<MMEC>.list<LIST_ID>.mmegi<MMEGI
>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org.
[0044] For example, if the pool in which the MME is located has 10 MMEs, the DNS server
sends 10 messages shown in the foregoing second FQND to the MME. For example, if MMEC
represents an MME 1, prefix <interface-name> carries information about an available
interface of the MME 1, <LIST_ID> represents identity information LIST_ID-1 of a group
in which the MME 1 is located, and MMEGI is identity information MMEGI-1 of an MME
pool in which the MME 1 is located.
[0045] The MME may acquire, according to information in the second FQDN, MMEC information
of all the MMEs in the MME pool and LIST_ID information corresponding to each MME,
that is, the MME pool includes 10 MMEs, the 10 MMEs are divided into two groups, and
identity information of the two groups is respectively LIST_ID-1 and LIST_ID-2. A
group corresponding to LIST_ID-1 includes six MMEs of MME 1-MME 6, and MMEC information
of the six MMEs; a group corresponding to LIST_ID-2 includes four MMEs of MME 7-MME
10, and MMEC information of the four MMEs.
[0046] 203. The MME determines a backup MME of the MME according to the MMECs of all the
MMEs in the MME pool and according to a preset policy.
[0047] Specifically, the MME sorts the MMECs of all the MMEs in the MME pool according to
an ascending order of the MMECs, to obtain a sorting result.
[0048] The MME uses an MME corresponding to an MMEC that is adjacent to an MMEC of the MME
and greater than the MMEC of the MME as the backup MME, and if the MMEC of the MME
is the largest in the sorting result, the MME uses an MME of which an MMEC is the
smallest in the sorting result as the backup MME.
[0049] For example, after acquiring the MMECs of all the MMEs, the MME sorts MMECs of MMEs
in a same group according to an ascending order, so as to generate a chain backup
loop shown in FIG. 3.
[0050] Specifically, with reference to FIG. 3, an MME chain backup loop is exemplarily described.
It is assumed that the MME is an MME 1, an identity of a group in which the MME 1
is located is LIST_ID-1, and six MMEs in the group are respectively MME 1-MME 6; it
is assumed that MMECs of MME 1-MME 6 successively increase in ascending order, and
the six MMEs can form a chain backup relationship shown in FIG. 3. In the chain backup
loop, an MME of which an MMEC number is relatively small selects an MME of which an
MMEC number is relatively large and adjacent to the MME in value sorting as a backup
MME, and an MME of which an MMEC number is the largest selects an MME of which an
MMEC number is the smallest in the chain backup loop as a backup MME.
[0051] For example, a backup MME of the MME 1 is an MME 2, a backup MME of the MME 2 is
an MME 3, ..., a backup MME of an MME 5 is the MME 6, and a backup MME of the MME
6 is the MME 1.
[0052] Certainly, the MME may also acquire, according to a same method, a chain backup loop
of a group corresponding to LIST_ID-2, so as to obtain backup relationships of all
the MMEs in the MME pool.
[0053] It should be noted that the chain backup relationship shown in FIG. 3 is only a feasible
implementation manner. The MME may further generate a backup relationship of MMEs
in a pool in another form according to a preset policy, which is not limited in this
embodiment of the present invention. In addition, any method, based on the idea of
the present invention, for acquiring a backup MME of an MME in a same pool is within
the protection scope of the present invention.
[0054] 204. The MME sends an interface request message to the DNS server, where the interface
request message includes an MMEC of the backup MME and the pool identity of the MME
pool, and the interface request message is used to request to acquire interface information
of the backup MME.
[0055] Further, <interface-name> in the second FQDN carries information about only one interface
of an MME. However, actually, an MME in the pool includes multiple interfaces. When
an MME in the pool wants to communicate with another MME, communication may not be
performed according to only one interface of the MME, and information about another
available interface of the MME needs to be acquired.
[0056] In a scenario shown in this embodiment of the present invention, the MME needs to
back up user information of a UE to the backup MME. Therefore, the MME needs to acquire
information about all interfaces of the backup MME.
[0057] In this case, the MME may send the following third FQDN to the DNS server:
mmec<MMEC>.list<LIST_ID>.mmegi<MMEGI>.mme.epc.mnc<MNC
>.mcc<MCC>.3gppnetwork.org.
[0058] MMEC in the third FQDN is the MMEC of the backup MME, and is used to identify the
information that is about all the interfaces of the backup MME and the MME requests
to acquire. The DNS server performs querying and parsing, by using information in
the third FQDN, to acquire the information about all the interfaces of the backup
MME, and sends address information of all the interfaces of the backup MME to the
MME.
[0059] 205. The MME receives an interface response message sent by the DNS server, where
the interface response message includes the interface information of the backup MME.
[0060] The interface response message is a fourth FQDN:
<interface-name>.ring.mmec<MMEC>.list<LIST_ID>.mmegi<MMEGI >.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org,
where MMEC in the fourth FQDN is the MMEC of the backup MME, and interface-name includes
the information about all the interfaces of the backup MME; or, if the backup MME
has F interfaces, the interface response message includes F fourth FQDNs, and interface-name
of each fourth FQDN includes information about one interface of the backup MME, where
any two pieces of information that is about an interface of the backup MME and included
in the F fourth FQDNs are different.
[0061] It should be noted that when MMEs increase or decrease in the pool, for example,
with reference to FIG. 3, when the MME 6 stops being used, by using technical solutions
in this embodiment of the present invention, an MME in the pool only needs to re-acquire
MMECs of all MMEs in the pool and information about an available interface of each
MME by performing step 201 to step 205, and parse information about a backup MME of
the MME by using a preset policy. For example, when the MME 6 stops being used, a
backup MME of the MME 1 changes to the MME 5, which not only ensures that each MME
in the MME pool has a backup MME, but also reduces complexity of acquiring, by each
MME, backup relationships of all the MMEs in the pool and information about interfaces
of all the MMEs.
[0062] 206. The MME sends, according to the interface information of the backup MME, user
information of user equipment UE attached to the MME to the backup MME.
[0063] Specifically, the MME sends a backup request message to the backup MME by using an
interface of the backup MME, where the backup request message carries identity information
of the UE and the user information of the UE, and the backup request message is used
to request the backup MME to back up the user information of the UE.
[0064] After receiving the backup request message, the backup MME stores the user information
of the UE, and records a correspondence between the identity information of the UE
and the user information of the UE.
[0065] This embodiment of the present invention provides a service redundancy method. In
this method, MMEC information of all MMEs in a pool and information about available
interfaces of all the MMEs are pre-configured in a DNS server. When the MME needs
to back up user information of a UE attached to the MME, the MME queries, from the
DNS server by using an FQDN, MMEC information of all MMEs in a pool in which the MME
is located, acquires information about a backup MME of the MME according to a preset
policy, queries information about an available interface of the backup MME from the
DNS server, and backs up the user information of the UE to the backup MME by using
the available interface of the backup MME, so that when the MME becomes faulty, another
MME in the MME pool acquires the user information of the UE from the backup MME, so
as to provide a service for the UE. Therefore, a service of the UE can succeed at
a time, which resolves a problem in the prior art that a service redundancy effect
is relatively poor.
[0066] Further, with reference to FIG. 4, an embodiment of the present invention further
provides a service redundancy method, where the method includes the following steps:
401. A domain name system DNS server receives a request message sent by a mobility
management entity MME, where the request message includes a pool identity of an MME
pool in which the MME is located, and the request message is used to request to acquire
MME codes MMECs of all MMEs in the MME pool.
402. The DNS server acquires, according to the pool identity of the MME pool, the
MMECs of all the MMEs in the MME pool corresponding to the pool identity of the MME
pool, and sends a request response message to the MME, where the request response
message includes the MMECs of all the MMEs, so that the MME determines a backup MME
of the MME according to the MMECs of all the MMEs.
403. 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 the pool identity
of the MME pool, and the interface request message is used to request to acquire interface
information of the backup MME.
404. The DNS server acquires the interface information of the backup MME according
to the MMEC of the backup MME and the pool identity of the MME pool, and sends an
interface response message to the MME, where the interface response message includes
the interface information of the backup MME, so that the MME sends, according to the
interface information of the backup MME, user information of user equipment UE attached
to the MME to the backup MME.
[0067] Specifically, for detailed technical features in this embodiment of the present invention,
reference may be made to the foregoing embodiment corresponding to FIG. 2, and details
are not described again in this embodiment of the present invention.
[0068] This embodiment of the present invention provides a service redundancy method. In
this method, MMEC information of all MMEs in an MME pool and information about available
interfaces of all the MMEs are pre-configured in a DNS server. When an MME in the
MME pool needs to back up user information of a UE attached to the MME, the MME queries,
from the DNS server by using an FQDN, the MMEC information of all the MMEs in the
MME pool in which the MME is located, and acquires information about a backup MME
of the MME according to the MMEC information of all the MMEs by using a preset policy;
and queries information about an available interface of the backup MME from the DNS
server, and backs up the user information of the UE to the backup MME by using the
available interface of the backup MME, so that when the MME becomes faulty, another
MME in the MME pool acquires the user information of the UE from the backup MME, so
as to provide a service for the UE. Therefore, a service of the UE can succeed at
a time, which resolves a problem in the prior art that a service redundancy effect
is relatively poor.
[0069] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 5, an embodiment of the present invention further provides
a service redundancy method, where the method includes the following steps:
[0070] 501. After a mobility management entity MME to which user equipment UE is attached
becomes faulty, a serving MME receives a service request message sent by the UE by
using an evolved NodeB eNodeB, where the service request message includes an identity
of the UE and an identity of the MME to which the UE is attached, the service request
message is used to request the MME to which the UE is attached to provide a service
for the UE, the serving MME is an MME selected, after the MME to which the UE is attached
becomes faulty, by the eNodeB to provide a service for the UE, and the MME to which
the UE is attached and the serving MME are located in a same MME pool.
[0071] Specifically, when the UE needs to perform a VoLTE mobile originated service, or
a data service, or a circuit switched fallback (Circuit Switched Fallback, CSFB) mobile
originated service that falls back to a Wideband Code Division Multiple Access (Wideband
Code Division Multiple Access, WCDMA) network, or a 1xCSF mobile originated service
that falls back to a WCDMA2000 network, or a tracking area update (Tracking Area Update,
TAU) service, the UE needs to first send a service request message to a base station
connected to the UE. Specifically, the service request varies with a service that
the UE needs to initiate. For example, the VoLTE mobile originated service is corresponding
to a VoLTE mobile originated service request, and the CSFB mobile originated service
is corresponding to a CSFB mobile originated service request.
[0072] The service request message carries identity information of the UE, where the identity
information of the UE is information that can uniquely identify the user in a network
in which the UE is located, for example, a short temporary mobile subscriber identity
(Short Temporary Mobile Subscriber Identity, S-TMSI) of the user.
[0073] With reference to FIG. 1, it is assumed that the UE is the UE 1 in FIG. 1, and the
UE is originally attached to the MME 1 in FIG. 1. After the MME 1 becomes faulty,
a base station 1 that serves the UE 1 determines that the MME 1 becomes faulty and
cannot continue to provide a service for the UE 1. The base station 1 reselects an
MME, for example, the MME 2 in FIG. 1 to provide a service for the UE 1, in an MME
pool same as that of the MME 1 for the UE 1 according to a preset policy, for example,
a load balancing principle. The MME 2 may be referred to as a serving MME of the UE
1, and a service request message of the UE 1 is sent to the MME 2, so as to instruct
the MME 2 to provide a service for the UE 1.
[0074] 502. The serving MME acquires user information of the UE according to the identity
of the UE or according to the identity of the UE and the identity of the MME to which
the UE is attached.
[0075] After receiving the service request message of the UE 1 that is sent by the base
station 1, the serving MME of the UE 1, that is, the MME 2, determines, according
to an S-TMSI that is of the UE 1 and carried in the service request message, whether
user information of the UE 1 is stored.
[0076] Specifically, with reference to embodiments corresponding to FIG. 2 and FIG. 4, if
the MME 2 is a backup MME of the MME 1, the MME 1 backs up the user information of
the UE 1 to the MME 2 before the MME 1 becomes faulty, where the MME 2 records a correspondence
between an identity of the UE 1 and the user information of the UE 1, and the MME
2 can directly acquire, according to the identity of the UE 1, the user information
of the UE 1 from storage space that stores the user information.
[0077] If the MME 2 is not the backup MME of the MME 1, and it is assumed that the MME 3
in FIG. 1 is the backup MME of the MME 1, the MME 2 does not store the user information
of the UE 1, and cannot acquire the user information of the UE 1 according to identity
information of the UE 1. In this case, the MME 2 acquires the user information of
the UE 1 from the backup MME of the MME 1, that is, from the MME 3.
[0078] Specifically, the serving MME acquires the user information of the UE through the
following process: The serving MME sends a request message to a domain name system
DNS server, where the request message carries a pool identity of an MME pool in which
the serving MME is located, and the request message is used to request to acquire
MMECs of all MMEs in the MME pool;
the serving MME receives a request response message sent by the DNS server, where
the request response message includes the MMECs of all the MMEs in the MME pool;
the serving MME acquires, according to an MMEC of the MME to which the UE is attached
and the MMECs of all the MMEs, a backup MME of the MME to which the UE is attached,
and sends an interface request message to the DNS server, where the interface request
message includes an identity of the backup MME and the pool identity of the MME pool,
so that the DNS server acquires interface information of the backup MME according
to the pool identity and the identity of the backup MME; and
the serving MME receives an interface response message sent by the DNS server, where
the interface response message includes the interface information of the backup MME.
[0079] It should be noted that by using the method in the embodiment corresponding to FIG.
3, before receiving the service request message, the serving MME may acquire, by using
the first FQDN, the MMECs of all the MMEs in the MME pool and information about LIST_ID
corresponding to each MME; obtain by means of parsing backup relationships of all
the MMEs in the MME pool shown in FIG. 4; and query, by using the third FQDN, information
about all available interfaces of all the MMEs in the MME pool. After receiving the
service request message of the UE, the serving MME may directly acquire, from the
backup relationships of all the MMEs by using MMEC information of the MME to which
the UE is attached, the backup MME of the MME to which the UE is attached and information
about an available interface of the backup MME; and acquire the user information of
the UE by using the available interface of the backup MME, without a need to query,
each time after receiving a service request message, the foregoing message from the
DNS server, thereby reducing a signaling overhead.
[0080] The serving MME sends a user information request message to the backup MME by using
an interface of the backup MME, where the user information request message includes
the identity information of the UE. The backup MME acquires the user information of
the UE according to the identity information of the UE, and sends the user information
of the UE to the serving MME.
[0081] It should be noted that a process in which the serving MME acquires the backup MME
of the MME to which the UE is attached and the interface of the backup MME is similar
to a process in which the MME to which the UE is attached acquires the backup MME
and the interface of the backup MME. For detailed technical features, reference may
be made to the foregoing embodiment corresponding to FIG. 3, and details are not described
again in this embodiment of the present invention.
[0082] It should be noted that if the service request message is a VoLTE mobile originated
service request message of the UE, or the service request message is a CSFB request
message or 1xCSF request message of the UE, the identity information of the MME to
which the UE is attached is the MMEC information of the MME to which the UE is attached,
and the identity information of the UE is S-TMSI information of the UE; or, if the
service request message is a TAU request message of the UE, the identity information
of the MME to which the UE is attached is GUTI information allocated to the UE by
the MME to which the UE is attached, where the GUTI information includes the MMEC
information of the MME to which the UE is attached, and the identity information of
the UE is S-TMSI information of the UE.
[0083] It should be noted that the identity, of the MME to which the UE is attached, that
is included in a query request message identifies that the UE requests the MME to
which the UE is attached to provide a service for the UE. In the prior art, after
the MME to which the UE is attached becomes faulty, an eNodeB that provides a service
for the UE sends the service request message of the UE to another MME in the MME pool,
where the another MME may be referred to as a serving MME. The serving MME rejects
the service request of the UE because of lack of the user information of the UE. In
this case, the UE attaches to the serving MME through a new attach procedure, and
the UE re-initiates a service request; in this case, a service request message initiated
by the UE includes an identity of the serving MME, which indicates that the UE requests
the serving MME to provide a service for the UE.
[0084] 503. The serving MME provides, according to the user information of the UE, the service
corresponding to the service request message for the UE.
[0085] Specifically, after the serving MME acquires 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 an authorized UE. If the UE is not an authorized UE, the serving
MME directly rejects the service request of the UE; if the UE is an authorized UE,
the serving MME further needs to send a modification request message to an SGW and
an HSS that are connected to the serving MME, where the modification request message
carries the identity information of the UE, and the modification request message is
used to request the SGW and the HSS to modify a correspondence between the UE and
the MME to which the UE is attached to a correspondence between the UE and the serving
MME. In addition, the serving MME further needs to reallocate a GUTI to the UE, so
that the UE attaches to the serving MME, and all services of the UE are completed
by the serving MME afterward.
[0086] It should be noted that the serving MME delays preset time and sends the modification
request message to the HSS. A reason for doing this is that there are tens of thousands
of users attached to the MME to which the UE is attached, and after the MME to which
the UE is attached becomes faulty, UEs attached to the original MME need an MME that
works normally in the MME pool to provide a service for the UEs. In this case, if
each serving MME sends a modification request message to the HSS, the HSS receives
a large quantity of modification request messages in a short time, causing relatively
heavy load of the HSS, which may cause a congestion phenomenon. In addition, because
the HSS is an important network element in an LTE core network, congestion of the
HSS greatly affects processing of a network service. Therefore, the serving MME delays
the preset time and sends the modification request message to the HSS, so as to avoid
that load of the HSS suddenly increases in a short time.
[0087] For example, when there are ten thousand users attached to the MME to which the UE
is attached, and the MME to which the UE is attached becomes faulty, the HSS may need
to receive ten thousand modification request messages, which causes that load of the
HSS suddenly increases, causing congestion. However, if the serving MME delays sending
the modification requests, sends 100 modification requests per second, and sends the
modification requests to the HSS in 100 seconds, load of the HSS in unit time can
be reduced, and impact on the HSS is reduced.
[0088] Further, the HSS further bears a large quantity of other services, for example, when
the UE is used as a VoLTE called party, the HSS further needs to complete a domain
selection procedure, so as to determine information about a domain in which the UE
is currently located; if the HSS is congested, a VoLTE terminated call service of
the UE fails.
[0089] In addition, if the HSS needs to perform a VoLTE terminated call service of the UE
before receiving the modification request of the serving MME, the HSS selects, from
the pool, any MME that works normally to obtain information that is about the UE and
required in the foregoing domain selection procedure, which does not fail the mobile
terminated call service of the UE.
[0090] Further, in this embodiment of the present invention, if the UE has registered with
an MSC network element of a core network in a CS domain in a 2G/3G network, the serving
MME further needs to send a location update request message to the MSC, and the location
update request message is used to update information about an MME that has registered
with the MSC. If the UE has registered with a 1xCS IWS network element of a core network
in a CDMA2000 network, the serving MME further needs to send an MME change notification
message to the 1xCS IWS, and the MME change notification message is used to update
information about an MME that has registered with the 1xCS IWS.
[0091] In this embodiment of the present invention, the serving MME further needs to send
an indication massage to a base station that provides a service for the UE, so as
to instruct the base station to establish a link and a bearer on a wireless side;
and send a request message to the SGW, so as to request to establish a tunnel between
the serving MME and an SGW interface.
[0092] Further, if the MSC network element in the core network in the CS domain in the 2G/3G
network reallocates a TMSI to the UE, the serving MME further needs to instruct the
UE to re-establish a correspondence between an IMSI and a TMSI.
[0093] In this embodiment of the present invention, when the UE needs to perform a circuit
switched fallback (Circuit Switched Fallback, CSFB) mobile originated service that
falls back to a Wideband Code Division Multiple Access (Wideband Code Division Multiple
Access, WCDMA) network, or a 1xCSF mobile originated service that falls back to a
WCDMA2000 network, the serving MME instructs the base station to enable the UE to
fall back to the circuit switched domain.
[0094] This embodiment of the present invention provides a service redundancy method. In
this method, after an MME to which a UE is attached becomes faulty, and a base station
that provides a service for the UE detects the fault, the base station sends a service
request message of the UE to another normal MME in a pool in which the MME to which
the UE is attached is located, where the another normal MME is used as a serving MME
of the UE. When the serving MME is a backup MME of the MME to which the UE is attached,
the serving MME acquires, according to identity information of the UE, user information
of the UE from storage space of the serving MME. If the serving MME is not the backup
MME of the MME to which the UE is attached, the serving MME acquires information about
the backup MME of the MME to which the UE is attached, and requests the user information
of the UE from the backup MME, where the serving MME provides a service for the UE
according to the user information of the UE, so that a service of the UE can succeed
at a time, and an effect of avoiding HSS congestion is reached by delaying sending
a registration request to an HSS, which resolves a problem in the prior art that a
service redundancy effect is relatively poor.
[0095] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 6, an embodiment of the present invention further provides
a service redundancy method, where the method includes the following steps:
[0096] 601. After a mobility management entity MME to which user equipment UE is attached
becomes faulty, a serving MME receives a paging request message sent by a network
element of a core network in a circuit switched CS domain that is in a second-generation
mobile communications technology 2G network or a third-generation mobile communications
technology 3G network, where the paging request message includes an identity of the
UE, and the paging request message is used to request to initiate CSFB paging or 1xCSF
paging on the UE, and the serving MME is an MME that provides a service for the UE
when the MME to which the UE is attached becomes faulty, and the MME to which the
UE is attached and the serving MME are located in a same MME pool.
[0097] When the UE is used as a called user of CSFB/1xCSFB, a network element in a CS domain
in a 2G/3G network to which the UE falls back sends a paging request message to the
MME to which the UE is attached, so that the MME to which the UE is attached pages
the UE.
[0098] After the MME to which the UE is attached becomes faulty, the network element in
the CS domain in the 2G/3G network sends the paging request message to a normal MME
in a pool in which the MME to which the UE is attached is located, and the normal
MME is used as a serving MME that processes the paging request message.
[0099] It should be noted that both CSFB and 1xCSF are circuit switched fallback, but respectively
corresponding networks to which a UE falls back are different; for CSFB, a UE falls
back to a Wideband Code Division Multiple Access (Wideband Code Division Multiple
Access, WCDMA) network, and for 1xCSFB, a UE falls back to a WCDMA2000 network.
[0100] 602. The serving MME acquires user information of the UE according to the identity
of the UE.
[0101] Specifically, if the serving MME is a backup MME of the MME to which the UE is attached,
before the MME to which the UE is attached becomes faulty, the serving MME further
receives the user information of the UE and the identity of the UE that are sent by
the MME to which the UE is attached, and records a correspondence between the user
information of the UE and the identity of the UE; in this case, the serving MME can
acquire, according to the identity of the UE, the user information that is of the
UE and saved by the serving MME.
[0102] If the serving MME is not the 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, where
the broadcast request message includes the identity of the UE, and the broadcast request
message is used to request to acquire the user information of the UE. After receiving
the broadcast request message, the backup MME of the MME to which the UE is attached
sends a broadcast response message to the serving MME, where the broadcast response
message includes the user information of the UE.
[0103] 603. The serving MME acquires, according to the user information, a tracking area
in which the UE is located, and initiates a paging request in the tracking area.
[0104] It should be noted that in the prior art, after the MME to which the UE is attached
becomes faulty, a network element in a 2G/3G core network to which the UE falls back
also selects, by using a preset policy, another MME in the MME pool as a serving MME
of the UE to initiate a paging request, but the serving MME does not have the user
information of the UE. Therefore, the serving MME cannot acquire the tracking area
in which the UE is located, the serving MME can only page the UE in multiple tracking
areas, and a paging efficiency is relatively low.
[0105] However, in the present invention, the serving MME acquires information about 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.
[0106] Specifically, for detailed technical features in the present invention, reference
may be made to the technical features in the foregoing embodiment corresponding to
FIG. 5, and details are not described again in this embodiment of the present invention.
[0107] This embodiment of the present invention provides a service redundancy method. In
this method, after a UE is used as a called user of CSFB/1xCSFB, and an MME to which
the UE is attached becomes faulty, a network element in a CS domain in a 2G/3G network
to which the UE falls back sends a paging request message to another MME that works
normally in a MME pool, where the MME that works normally is used as a serving MME
to process the paging request message. The serving MME acquires user information of
the UE from the serving MME itself or from a backup MME of the MME to which the UE
is attached, acquires information about a tracking area of the UE from the user information
of the UE, and initiates a paging procedure in the tracking area, so that a CSFB/1xCSFB
mobile terminated call service of the UE succeeds at a time, which resolves a problem
in the prior art that a service redundancy effect is relatively poor.
[0108] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 7, an embodiment of the present invention further provides
an MME, where the MME includes a sending unit 701, a receiving unit 702, and a determining
unit 703, where:
the sending unit 701 is configured to send a request message to a domain name system
DNS server, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
the receiving unit 702 is configured to receive a request response message sent by
the DNS server, where the request response message includes the MMECs of all the MMEs
in the MME pool; and
the determining unit 703 is configured to determine a backup MME of the MME according
to the MMECs of all the MMEs in the MME pool and according to a preset policy.
[0109] 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 the pool identity of the MME pool, and the interface request message is used
to request to acquire 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 the interface
information of the backup MME; and
the sending unit 701 is further configured to send, according to the interface information
of the backup MME, user information of user equipment UE attached to the MME to the
backup MME.
[0110] Specifically, the determining unit 703 is configured to:
sort the MMECs of all the MMEs in the MME pool according to an ascending order of
the MMECs, to obtain a sorting result; and
use an MME corresponding to an MMEC that is adjacent to an MMEC of the MME and greater
than the MMEC of the MME as the backup MME, and if the MMEC of the MME is the largest
in the sorting result, use an MME of which an MMEC is the smallest in the sorting
result as the backup MME.
[0111] Specifically, the sending unit 701 is configured to:
send a backup request message to the backup MME by using an interface corresponding
to the interface information of the backup MME, where the backup request message includes
an identity of the UE and the user information of the UE, and the backup request message
is used to request the backup MME to back up the user information of the UE.
[0112] This embodiment of the present invention provides an MME. When the MME needs to back
up user information of a UE attached to the MME, the MME queries, from a DNS server
by using an FQDN, MMEC information of all MMEs in a pool in which the MME is located,
acquires information about a backup MME of the MME according to a preset policy, queries
information about an available interface of the backup MME from the DNS server, and
backs up the user information of the UE to the backup MME by using the available interface
of the backup MME, so that when the MME becomes faulty, another MME in the MME pool
acquires the user information of the UE from the backup MME, so as to provide a service
for the UE. Therefore, a service of the UE can succeed at a time, which resolves a
problem in the prior art that a service redundancy effect is relatively poor.
[0113] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 8, an embodiment of the present invention further provides
a DNS server, where the DNS server includes a receiving unit 801, a first acquiring
unit 802, a sending unit 803, and a second acquiring unit 804, where:
the receiving unit 801 is configured to receive a request message sent by a mobility
management entity MME, where the request message includes a pool identity of an MME
pool in which the MME is located, and the request message is used to request to acquire
MME codes MMECs of all MMEs in the MME pool;
the first acquiring unit 802 is configured to acquire, according to the pool identity
of the MME pool, the MMECs of all the MMEs in the MME pool corresponding to the pool
identity of the MME pool; and
the sending unit 803 is configured to send a request response message to the MME,
where the request response message includes the MMECs of all the MMEs, so that the
MME determines a backup MME of the MME according to the MMECs of all the MMEs.
[0114] 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 the pool identity of the MME pool, and the interface request message is used
to request to acquire interface information of the backup MME;
the second acquiring unit 804 is configured to acquire the interface information of
the backup MME according to the MMEC of the backup MME and the pool identity of the
MME pool; and
the sending unit 803 is configured to send an interface response message to the MME,
where the interface response message includes the interface information of the backup
MME, so that the MME sends, according to the interface information of the backup MME,
user information of user equipment UE attached to the MME to the backup MME.
[0115] This embodiment of the present invention provides a DNS server. MMEC information
of all MMEs in an MME pool and information about available interfaces of all the MMEs
are pre-configured in the DNS server. When an MME in the MME pool needs to back up
user information of a UE attached to the MME, the MME queries, from the DNS server
by using an FQDN, the MMEC information of all the MMEs in the MME pool in which the
MME is located, and acquires, by using a preset policy, information about a backup
MME of the MME according to the MMEC information of all the MMEs; and queries information
about an available interface of the backup MME from the DNS server, and backs up the
user information of the UE to the backup MME by using the available interface of the
backup MME, so that when the MME becomes faulty, another MME in the MME pool acquires
the user information of the UE from the backup MME, so as to provide a service for
the UE. Therefore, a service of the UE can succeed at a time, which resolves a problem
in the prior art that a service redundancy effect is relatively poor.
[0116] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 9, an embodiment of the present invention further provides
a serving MME, where the MME includes a receiving unit 901, an acquiring unit 902,
and a serving unit 903, where:
the receiving unit 901 is configured to: after a mobility management entity MME to
which user equipment UE is attached becomes faulty, receive a service request message
sent by the UE by using an evolved NodeB eNodeB, where the service request message
includes an identity of the UE and an identity of the MME to which the UE is attached,
the service request message is used to request the MME to which the UE is attached
to provide a service for the UE, the serving MME is an MME selected, after the MME
to which the UE is attached becomes faulty, by the eNodeB to provide a service for
the UE, and the MME to which the UE is attached and the serving MME are located in
a same MME pool;
the acquiring unit 902 is configured to acquire user information of the UE according
to the identity of the UE or according to the identity of the UE and the identity
of the MME to which the UE is attached; and
the serving unit 903 is configured to provide, according to the user information of
the UE, the service corresponding to the service request message for the UE.
[0117] Optionally, the receiving unit 901 is further configured to: receive the user information
of the UE and the identity of the UE that are sent by the MME to which the UE is attached,
and record a correspondence between the user information of the UE and the identity
of the UE; and
the acquiring unit 902 is specifically configured to acquire, according to the identity
of the UE, the user information that is of the UE and saved by the serving MME.
[0118] Specifically, the acquiring unit 902 is configured to: acquire, according to the
identity of the MME to which the UE is attached, interface information of a backup
MME of the MME to which the UE is attached, and acquire, from the backup MME, the
user information of the UE according to the identity of the UE and the interface information
of the backup MME, where the backup MME and the serving MME are located in a same
MME pool.
[0119] Specifically, the identity of the MME to which the UE is attached is an MME code
MMEC of the MME to which the UE is attached, and the acquiring unit 902 is specifically
configured to:
send a request message to a domain name system DNS server, where the request message
includes a pool identity of an MME pool in which the serving MME is located, and the
request message is used to request to acquire MME codes MMECs of all MMEs in the MME
pool;
receive a request response message sent by the DNS server, where the request response
message includes the MMECs of all the MMEs in the MME pool;
acquire, according to the MMEC of the MME to which the UE is attached and the MMECs
of all the MMEs and according to a preset policy, the backup MME of the MME to which
the UE is attached;
send an interface request message to the DNS server, where the interface request message
includes an MMEC of the backup MME and the pool identity of the MME pool, so that
the DNS server acquires the interface information of the backup MME according to the
pool identity of the MME pool and the MMEC of the backup MME; and
receive an interface response message sent by the DNS server, where the interface
response message includes the interface information of the backup MME.
[0120] Specifically, the service request message is a Voice over Long Term Evolution VoLTE
mobile originated service request message of the UE, or a circuit switched fallback
CSFB request message of the UE, or a 1xCSF request message of the UE, and the identity
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 identity of the MME to which the UE is attached is a GUTI allocated to the
UE by the MME to which the UE is attached, where the GUTI includes the MMEC of the
MME to which the UE is attached.
[0121] Specifically, the identity of the UE is a short temporary mobile subscriber identity
S-TMSI of the UE.
[0122] Specifically, the serving MME further includes a determining unit 904 and a sending
unit 905, where:
the determining unit 904 is configured to determine, according to the user information
of the UE, that the UE is an authorized user; and
the sending unit 905 is configured to separately send a modification request message
to a serving gateway SGW and a home subscriber server HSS that are connected to the
MME, where the modification request message includes the identity of the UE, and the
modification request message is used to request the SGW or the HSS to modify a correspondence
between the UE and the MME to which the UE is attached to a correspondence between
the UE and the serving MME; and reallocate a GUTI to the UE, and send the reallocated
GUTI to the UE, so that the UE is attached to the serving MME.
[0123] This embodiment of the present invention provides an serving MME. After an MME to
which a UE is attached becomes faulty, and a base station that provides a service
for the UE detects the fault, the base station sends a service request message of
the UE to the MME. When the MME is a backup MME of the MME to which the UE is attached,
the MME acquires user information of the UE from storage space of the MME itself according
to identity information of the UE. If the MME is not the backup MME of the MME to
which the UE is attached, the MME acquires information about the backup MME of the
MME to which the UE is attached, and requests the user information of the UE from
the backup MME, where the MME provides a service for the UE according to the user
information of the UE, so that a service of the UE can succeed at a time, and an effect
of avoiding HSS congestion is reached by delaying sending a registration request to
an HSS, which resolves a problem in the prior art that a service redundancy effect
is relatively poor.
[0124] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 10, an embodiment of the present invention further provides
a serving MME, where the serving MME includes a receiving unit 1001, an acquiring
unit 1002, and a paging unit 1003, where:
the receiving unit 1001 is configured to: after a mobility management entity MME to
which user equipment UE is attached becomes faulty, receive a paging request message
sent by a network element of a core network in a circuit switched CS domain that is
in a second-generation mobile communications technology 2G network or a third-generation
mobile communications technology 3G network, where the paging request message includes
an identity of the UE, the paging request message is used to request to initiate CSFB
paging or 1xCSF paging on the UE, the serving MME is an MME that provides a service
for the UE when the MME to which the UE is attached becomes faulty, and the MME to
which the UE is attached and the serving MME are located in a same MME pool;
the acquiring unit 1002 is configured to acquire user information of the UE according
to the identity of the UE; and
the paging unit 1003 is configured to acquire, according to the user information,
a tracking area in which the UE is located, and initiate a paging request in the tracking
area.
[0125] Optionally, the serving MME further includes a recording unit 1004, where:
the receiving unit 1001 is further configured to receive the user information of the
UE and the identity of the UE that are sent by the MME to which the UE is attached;
the recording unit 1004 is configured to record a correspondence between the user
information of the UE and the identity of the UE; and
the acquiring unit 1002 is configured to acquire, according to the identity of the
UE, the user information that is of the UE and saved by the serving MME.
[0126] Specifically, the serving MME further includes a sending unit 1005, where:
the sending unit 1005 is configured to send a broadcast request message to all MMEs
in the MME pool, where the broadcast request message includes the identity of the
UE, and the broadcast request message is used to request to acquire the user information
of the UE; and
the receiving unit 1001 is further configured to receive a broadcast response message
of a backup MME of the MME to which the UE is attached, where the broadcast response
message includes the user information of the UE.
[0127] This embodiment of the present invention provides an MME. After a UE is used as a
called user of CSFB/1xCSFB, and an MME to which the UE is attached becomes faulty,
a network element in a CS domain in a 2G/3G network to which the UE falls back sends
a paging request message to the MME. The MME acquires user information of the UE from
the MME itself or from a backup MME of the MME to which the UE is attached, acquires
information about a tracking area of the UE from the user information of the UE, and
initiates a paging procedure in the tracking area, so that a CSFB/1xCSFB mobile terminated
call service of the UE succeeds at a time, which resolves a problem in the prior art
that a service redundancy effect is relatively poor.
[0128] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 11, an 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, where:
the transmitter 1105 is configured to send a request message to a domain name system
DNS server, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
the receiver 1101 is configured to receive a request response message sent by the
DNS server, where the request response message includes the MMECs of all the MMEs
in the MME pool; and
the processor 1102 obtains an instruction in the memory 1104 by using the bus 1103,
so as to determine a backup MME of the MME according to the MMECs of all the MMEs
in the MME pool and according to a preset policy.
[0129] 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 the pool identity of the MME pool, and the interface request message is used
to request to 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 the interface information
of the backup MME; and
the processor 1102 is further configured to send, according to the interface information
of the backup MME by using the transmitter 1105, user information of user equipment
UE attached to the MME to the backup MME.
[0130] Specifically, the processor 1102 is configured to sort the MMECs of all the MMEs
in the MME pool according to an ascending order of the MMECs, to obtain a sorting
result; and
use an MME corresponding to an MMEC that is adjacent to an MMEC of the MME and greater
than the MMEC of the MME as the backup MME, and if the MMEC of the MME is the largest
in the sorting result, use an MME of which an MMEC is the smallest in the sorting
result as the backup MME.
[0131] Specifically, the processor 1102 is configured to send, by using the transmitter
1105, a backup request message to the backup MME by using an interface corresponding
to the interface information of the backup MME, where the backup request message includes
an identity of the UE and the user information of the UE, and the backup request message
is used to request the backup MME to back up the user information of the UE.
[0132] This embodiment of the present invention provides an MME. When the MME needs to back
up user information of a UE attached to the MME, the MME queries, from a DNS server
by using an FQDN, MMEC information of all MMEs in a pool in which the MME is located,
acquires information about a backup MME of the MME according to a preset policy, queries
information about an available interface of the backup MME from the DNS server, and
backs up the user information of the UE to the backup MME by using the available interface
of the backup MME, so that when the MME becomes faulty, another MME in the MME pool
acquires the user information of the UE from the backup MME, so as to provide a service
for the UE. Therefore, a service of the UE can succeed at a time, which resolves a
problem in the prior art that a service redundancy effect is relatively poor.
[0133] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 11, an 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 a transmitter 1105, where:
the receiver 1101 is configured to receive a request message sent by a mobility management
entity MME, where the request message includes a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
the processor 1102 acquires an instruction in the memory 1104 by using the bus 1103,
so as to acquire, according to the pool identity of the MME pool, the MMECs of all
the MMEs in the MME pool corresponding to the pool identity of the MME pool; and
the transmitter 1105 is configured to send a request response message to the MME,
where the request response message includes the MMECs of all the MMEs, so that the
MME determines a backup MME of the MME according to the MMECs of all the MMEs.
[0134] 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 the pool identity of the MME pool, and the interface request message is used to
request to acquire interface information of the backup MME;
the processor 1102 is further configured to acquire the interface information of the
backup MME according to the MMEC of the backup MME and the pool identity of the MME
pool; and
the transmitter 1105 is further configured to send an interface response message to
the MME, where the interface response message includes the interface information of
the backup MME, so that the MME sends, according to the interface information of the
backup MME, user information of user equipment UE attached to the MME to the backup
MME.
[0135] This embodiment of the present invention provides a DNS server. MMEC information
of all MMEs in an MME pool and information about available interfaces of all the MMEs
are pre-configured in the DNS server. When an MME in the MME pool needs to back up
user information of a UE attached to the MME, the MME queries, from the DNS server
by using an FQDN, the MMEC information of all the MMEs in the MME pool in which the
MME is located, and acquires, by using a preset policy, information about a backup
MME of the MME according to the MMEC information of all the MMEs; and queries information
about an available interface of the backup MME from the DNS server, and backs up the
user information of the UE to the backup MME by using the available interface of the
backup MME, so that when the MME becomes faulty, another MME in the MME pool acquires
the user information of the UE from the backup MME, so as to provide a service for
the UE. Therefore, a service of the UE can succeed at a time, which resolves a problem
in the prior art that a service redundancy effect is relatively poor.
[0136] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 11, an 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, where:
the receiver 1101 is configured to: after a mobility management entity MME to which
user equipment UE is attached becomes faulty, receive a service request message sent
by the UE by using an evolved NodeB eNodeB, where the service request message includes
an identity of the UE and an identity of the MME to which the UE is attached, the
service request message is used to request the MME to which the UE is attached to
provide a service for the UE, the serving MME is an MME selected, after the MME to
which the UE is attached becomes faulty, by the eNodeB to provide a service for the
UE, and the MME to which the UE is attached and the serving MME are located in a same
MME pool; and
the processor 1102 acquires an instruction in the memory 1104 by using the bus 1103,
so as to acquire user information of the UE according to the identity of the UE or
according to the identity of the UE and the identity of the MME to which the UE is
attached; and
provide, according to the user information of the UE, the service corresponding to
the service request message for the UE.
[0137] Specifically, the receiver 1101 is further configured to receive the user information
of the UE and the identity of the UE that are sent by the MME to which the UE is attached;
and
the processor 1102 is specifically configured to record a correspondence between the
user information of the UE and the identity of the UE; and
acquire, according to the identity of the UE, the user information that is of the
UE and saved by the serving MME.
[0138] Specifically, the processor 1102 is configured to: acquire, according to the identity
of the MME to which the UE is attached, interface information of a backup MME of the
MME to which the UE is attached, and acquire, from the backup MME, the user information
of the UE according to the identity of the UE and the interface information of the
backup MME, where the backup MME and the serving MME are located in a same MME pool.
[0139] Specifically, the identity of the MME to which the UE is attached is an MME code
MMEC of the MME to which the UE is attached, and the serving MME further includes
a transmitter 1105, where:
the transmitter 1105 is configured to send a request message to a domain name system
DNS server, where the request message includes a pool identity of an MME pool in which
the serving MME is located, and the request message is used to request to acquire
MME codes MMECs of all MMEs in the MME pool;
the receiver 1101 is configured to receive a request response message sent by the
DNS server, where the request response message includes the MMECs of all the MMEs
in the MME pool;
the processor 1102 is configured to acquire, according to the MMEC of the MME to which
the UE is attached and the MMECs of all the MMEs and according to a preset policy,
the backup MME of the MME to which the UE is attached;
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 the pool identity of the MME pool, so that the DNS server acquires interface
information of the backup MME according to the pool identity of the MME pool and the
MMEC of the backup MME; and
the receiver 1101 is further configured to receive an interface response message sent
by the DNS server, where the interface response message includes the interface information
of the backup MME.
[0140] Specifically, the service request message is a Voice over Long Term Evolution VoLTE
mobile originated service request message of the UE, or a circuit switched fallback
CSFB request message of the UE, or a 1xCSF request message of the UE, and the identity
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 identity of the MME to which the UE is attached is a GUTI allocated to the
UE by the MME to which the UE is attached, where the GUTI includes the MMEC of the
MME to which the UE is attached.
[0141] Specifically, the identity of the UE is a short temporary mobile subscriber identity
S-TMSI of the UE.
[0142] Specifically, the processor 1102 is further configured to:
determine, according to the user information of the UE, that the UE is an authorized
user.
[0143] The transmitter 1105 is further configured to separately send a modification request
message to a serving gateway SGW and a home subscriber server HSS that are connected
to the MME, where the modification request message includes the identity of the UE,
and the modification request message is used to request the SGW or the HSS to modify
a correspondence between the UE and the MME to which the UE is attached to a correspondence
between the UE and the serving MME; and
the processor 1102 is further configured to reallocate a GUTI to the UE, and send
the reallocated GUTI to the UE by using the transmitter 1105, so that the UE is attached
to the serving MME.
[0144] This embodiment of the present invention provides an MME. After an MME to which a
UE is attached becomes faulty, and a base station that provides a service for the
UE detects the fault, the base station sends a service request message of the UE to
the MME. When the MME is a backup MME of the MME to which the UE is attached, the
MME acquires user information of the UE from storage space of the MME itself according
to identity information of the UE. If the MME is not the backup MME of the MME to
which the UE is attached, the MME acquires information about the backup MME of the
MME to which the UE is attached, and requests the user information of the UE from
the backup MME, where the MME provides a service for the UE according to the user
information of the UE, so that a service of the UE can succeed at a time, and an effect
of avoiding HSS congestion is reached by delaying sending a registration request to
an HSS, which resolves a problem in the prior art that a service redundancy effect
is relatively poor.
[0145] To resolve a problem in the prior art that a service redundancy effect is relatively
poor, with reference to FIG. 11, 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, where:
the receiver 1101 is configured to: after a mobility management entity MME to which
user equipment UE is attached becomes faulty, receive a paging request message sent
by a network element of a core network in a circuit switched CS domain that is in
a second-generation mobile communications technology 2G network or a third-generation
mobile communications technology 3G network, where the paging request message includes
an identity of the UE, the paging request message is used to request to initiate CSFB
paging or 1xCSF paging on the UE, the serving MME is an MME that provides a service
for the UE when the MME to which the UE is attached becomes faulty, and the MME to
which the UE is attached and the serving MME are located in a same MME pool; and
the processor 1102 acquires an instruction in the memory 1104 by using the bus 1103,
so as to acquire user information of the UE according to the identity of the UE; and
acquire, according to the user information, a tracking area in which the UE is located,
and initiate a paging request in the tracking area by using the transmitter 1105.
[0146] Specifically, the receiver 1101 is further configured to receive the user information
of the UE and the identity of the UE that are sent by the MME to which the UE is attached;
and
the processor 1102 is specifically configured to record a correspondence between the
user information of the UE and the identity of the UE; and
acquire, according to the identity of the UE, the user information that is of the
UE and saved by the serving MME.
[0147] Specifically, the transmitter 1105 is further configured to:
send a broadcast request message to all MMEs in the MME pool, where the broadcast
request message includes the identity of the UE, and the broadcast request message
is used to request to acquire the user information of the UE.
[0148] The receiver 1101 is further configured to receive a broadcast response message of
a backup MME of the MME to which the UE is attached, where the broadcast response
message includes the user information of the UE.
[0149] This embodiment of the present invention provides an MME. After a UE is used as a
called user of CSFB/1xCSFB, and an MME to which the UE is attached becomes faulty,
a network element in a CS domain in a 2G/3G network to which the UE falls back sends
a paging request message to the MME. The MME acquires user information of the UE from
the MME itself or from a backup MME of the MME to which the UE is attached, acquires
information about a tracking area of the UE from the user information of the UE, and
initiates a paging procedure in the tracking area, so that a CSFB/1xCSFB mobile terminated
call service of the UE succeeds at a time, which resolves a problem in the prior art
that a service redundancy effect is relatively poor.
[0150] The foregoing descriptions are merely specific implementation manners of the present
invention, but are not intended to limit the protection scope of the present invention.
Any variation or replacement readily figured out by a person skilled in the art within
the technical scope disclosed in the present invention shall fall within the protection
scope of the present invention. Therefore, the protection scope of the present invention
shall be subject to the protection scope of the claims.
1. A service redundancy method, wherein the method comprises:
sending, by a mobility management entity MME, a request message to a domain name system
DNS server, wherein the request message comprises a pool identity of an MME pool in
which the MME is located, and the request message is used to request to acquire MME
codes MMECs of all MMEs in the MME pool;
receiving, by the MME, a request response message sent by the DNS server, wherein
the request response message comprises the MMECs of all the MMEs in the MME pool;
determining, by the MME, a backup MME of the MME according to the MMECs of all the
MMEs in the MME pool and according to a preset policy;
sending, by the MME, an interface request message to the DNS server, wherein the interface
request message comprises an MMEC of the backup MME and the pool identity of the MME
pool, and the interface request message is used to request to acquire interface information
of the backup MME;
receiving, by the MME, an interface response message sent by the DNS server, wherein
the interface response message comprises the interface information of the backup MME;
and
sending, by the MME according to the interface information of the backup MME, user
information of user equipment UE attached to the MME to the backup MME.
2. The method according to claim 1, wherein the determining, by the MME, a backup MME
of the MME according to the MMECs of all the MMEs in the MME pool and according to
a preset policy specifically comprises:
sorting, by the MME, the MMECs of all the MMEs in the MME pool according to an ascending
order of the MMECs, to obtain a sorting result; and
using, by the MME, an MME corresponding to an MMEC that is adjacent to an MMEC of
the MME and greater than the MMEC of the MME as the backup MME, and if the MMEC of
the MME is the largest in the sorting result, using, by the MME, an MME of which an
MMEC is the smallest in the sorting result as the backup MME.
3. The method according to claim 1 or 2, wherein the sending, by the MME according to
the interface information of the backup MME, user information of user equipment UE
attached to the MME to the backup MME specifically comprises:
sending, by the MME, a backup request message to the backup MME by using an interface
corresponding to the interface information of the backup MME, wherein the backup request
message comprises an identity of the UE and the user information of the UE, and the
backup request message is used to request the backup MME to back up the user information
of the UE.
4. A service redundancy method, wherein the method comprises:
receiving, by a domain name system DNS server, a request message sent by a mobility
management entity MME, wherein the request message comprises a pool identity of an
MME pool in which the MME is located, and the request message is used to request to
acquire MME codes MMECs of all MMEs in the MME pool;
acquiring, by the DNS server according to the pool identity of the MME pool, the MMECs
of all the MMEs in the MME pool, and sending a request response message to the MME,
wherein the request response message comprises the MMECs of all the MMEs, so that
the MME determines a backup MME of the MME according to the MMECs of all the MMEs;
receiving, by the DNS server, an interface request message sent by the MME, wherein
the interface request message comprises an MMEC of the backup MME and the pool identity
of the MME pool, and the interface request message is used to request to acquire interface
information of the backup MME; and
acquiring, by the DNS server, the interface information of the backup MME according
to the MMEC of the backup MME and the pool identity of the MME pool, and sending an
interface response message to the MME, wherein the interface response message comprises
the interface information of the backup MME, so that the MME sends, according to the
interface information of the backup MME, user information of user equipment UE attached
to the MME to the backup MME.
5. A service redundancy method, wherein the method comprises:
after a mobility management entity MME to which user equipment UE is attached becomes
faulty, receiving, by a serving MME, a service request message sent by the UE by using
an evolved NodeB eNodeB, wherein the service request message comprises an identity
of the UE and an identity of the MME to which the UE is attached, the service request
message is used to request the MME to which the UE is attached to provide a service
for the UE, the serving MME is an MME selected, after the MME to which the UE is attached
becomes faulty, by the eNodeB to provide a service for the UE, and the MME to which
the UE is attached and the serving MME are located in a same MME pool;
acquiring, by the serving MME, user information of the UE according to the identity
of the UE or according to the identity of the UE and the identity of the MME to which
the UE is attached; and
providing, by the serving MME according to the user information of the UE, the service
corresponding to the service request message for the UE.
6. The method according to claim 5, wherein before the mobility management entity MME
to which the user equipment UE is attached becomes faulty, the method further comprises:
receiving, by the serving MME, the user information of the UE and the identity of
the UE that are sent by the MME to which the UE is attached, and recording a correspondence
between the user information of the UE and the identity of the UE;
then, the acquiring, by the serving MME, user information of the UE according to the
identity of the UE or according to the identity of the UE and the identity of the
MME to which the UE is attached specifically comprises:
acquiring, by the serving MME according to the identity of the UE, the user information
that is of the UE and saved by the serving MME.
7. The method according to claim 5, wherein the acquiring, by the serving MME, user information
of the UE according to the identity of the UE or according to the identity of the
UE and the identity of the MME to which the UE is attached comprises:
acquiring, by the serving MME according to the identity of the MME to which the UE
is attached, interface information of a backup MME of the MME to which the UE is attached,
and acquiring, from the backup MME, the user information of the UE according to the
identity of the UE and the interface information of the backup MME, wherein the backup
MME and the serving MME are located in a same MME pool.
8. The method according to claim 7, wherein the identity of the MME to which the UE is
attached is an MME code MMEC of the MME to which the UE is attached;
the acquiring, by the serving MME according to the identity of the MME to which the
UE is attached, interface information of a backup MME of the MME to which the UE is
attached specifically comprises:
sending, by the serving MME, a request message to a domain name system DNS server,
wherein the request message comprises a pool identity of an MME pool in which the
serving MME is located, and the request message is used to request to acquire MME
codes MMECs of all MMEs in the MME pool;
receiving, by the serving MME, a request response message sent by the DNS server,
wherein the request response message comprises the MMECs of all the MMEs in the MME
pool;
acquiring, by the serving MME according to the MMEC of the MME to which the UE is
attached and the MMECs of all the MMEs and according to a preset policy, the backup
MME of the MME to which the UE is attached, and sending an interface request message
to the DNS server, wherein the interface request message comprises an MMEC of the
backup MME and the pool identity of the MME pool, so that the DNS server acquires
the interface information of the backup MME according to the pool identity of the
MME pool and the MMEC of the backup MME; and
receiving, by the serving MME, an interface response message sent by the DNS server,
wherein the interface response message comprises the interface information of the
backup MME.
9. The method according to any one of claims 5 to 8, wherein the service request message
is a Voice over Long Term Evolution VoLTE mobile originated service request message
of the UE, or a circuit switched fallback CSFB request message of the UE, or a 1xCSF
request message of the UE, and the identity 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 identity of the MME to which the UE is attached is a globally unique temporary
identity GUTI allocated to the UE by the MME to which the UE is attached, wherein
the GUTI comprises the MMEC of the MME to which the UE is attached.
10. The method according to any one of claims 5 to 9, wherein the identity of the UE is
a short temporary mobile subscriber identity S-TMSI of the UE.
11. The method according to any one of claims 5 to 10, wherein after the acquiring, by
the serving MME, user information of the UE according to the identity of the UE or
according to the identity of the UE and the identity of the MME to which the UE is
attached, the method further comprises:
determining, by the serving MME according to the user information of the UE, that
the UE is an authorized user;
separately sending, by the serving MME, a modification request message to a serving
gateway SGW and a home subscriber server HSS that are connected to the serving MME,
wherein the modification request message comprises the identity of the UE, and the
modification request message is used to request the SGW or the HSS to modify a correspondence
between the UE and the MME to which the UE is attached to a correspondence between
the UE and the serving MME; and
reallocating, by the serving MME, a GUTI to the UE, and sending the reallocated GUTI
to the UE, so that the UE is attached to the serving MME.
12. A service redundancy method, wherein the method comprises:
after a mobility management entity MME to which user equipment UE is attached becomes
faulty, receiving, by a serving MME, a paging request message sent by a network element
of a core network in a circuit switched CS domain that is in a second-generation mobile
communications technology 2G network or a third-generation mobile communications technology
3G network, wherein the paging request message comprises an identity of the UE, the
paging request message is used to request to initiate CSFB paging or 1xCSF paging
on the UE, the serving MME is an MME that provides a service for the UE when the MME
to which the UE is attached becomes faulty, and the MME to which the UE is attached
and the serving MME are located in a same MME pool;
acquiring, by the serving MME, user information of the UE according to the identity
of the UE; and
acquiring, by the serving MME according to the user information, a tracking area in
which the UE is located, and initiating a paging request in the tracking area.
13. The method according to claim 12, wherein before the mobility management entity MME
to which the user equipment UE is attached becomes faulty, the method further comprises:
receiving, by the serving MME, the user information of the UE and the identity of
the UE that are sent by the MME to which the UE is attached, and recording a correspondence
between the user information of the UE and the identity of the UE;
then, the acquiring, by the serving MME, user information of the UE according to the
identity of the UE specifically comprises:
acquiring, by the serving MME according to the identity of the UE, the user information
that is of the UE and saved by the serving MME.
14. The method according to claim 12, wherein the acquiring, by the serving MME, user
information of the UE according to the identity of the UE specifically comprises:
sending, by the serving MME, a broadcast request message to all MMEs in an MME pool,
wherein the broadcast request message comprises the identity of the UE, and the broadcast
request message is used to request to acquire the user information of the UE; and
receiving, by the serving MME, a broadcast response message of a backup MME of the
MME to which the UE is attached, wherein the broadcast response message comprises
the user information of the UE.
15. A mobility management entity MME, wherein the MME comprises a sending unit, a receiving
unit, and a determining unit, wherein:
the sending unit is configured to send a request message to a domain name system DNS
server, wherein the request message comprises a pool identity of an MME pool in which
the MME is located, and the request message is used to request to acquire MME codes
MMECs of all MMEs in the MME pool;
the receiving unit is configured to receive a request response message sent by the
DNS server, wherein the request response message comprises the MMECs of all the MMEs
in the MME pool;
the determining unit is configured to determine a backup MME of the MME according
to the MMECs of all the MMEs in the MME pool and according to a preset policy;
the sending unit is further configured to send an interface request message to the
DNS server, wherein the interface request message comprises an MMEC of the backup
MME and the pool identity of the MME pool, and the interface request message is used
to request to acquire interface information of the backup MME;
the receiving unit is further configured to receive an interface response message
sent by the DNS server, wherein the interface response message comprises the interface
information of the backup MME; and
the sending unit is further configured to send, according to the interface information
of the backup MME, user information of user equipment UE attached to the MME to the
backup MME.
16. The MME according to claim 15, wherein the determining unit is specifically configured
to:
sort the MMECs of all the MMEs in the MME pool according to an ascending order of
the MMECs, to obtain a sorting result; and
use an MME corresponding to an MMEC that is adjacent to an MMEC of the MME and greater
than the MMEC of the MME as the backup MME, and if the MMEC of the MME is the largest
in the sorting result, use an MME of which an MMEC is the smallest in the sorting
result as the backup MME.
17. The MME according to claim 15 or 16, wherein the sending unit is specifically configured
to:
send a backup request message to the backup MME by using an interface corresponding
to the interface information of the backup MME, wherein the backup request message
comprises an identity of the UE and the user information of the UE, and the backup
request message is used to request the backup MME to back up the user information
of the UE.
18. A domain name system DNS server, wherein the DNS server comprises a receiving unit,
a first acquiring unit, a sending unit, and a second acquiring unit, wherein:
the receiving unit is configured to receive a request message sent by a mobility management
entity MME, wherein the request message comprises a pool identity of an MME pool in
which the MME is located, and the request message is used to request to acquire MME
codes MMECs of all MMEs in the MME pool;
the first acquiring unit is configured to acquire, according to the pool identity
of the MME pool, the MMECs of all the MMEs in the MME pool corresponding to the pool
identity of the MME pool;
the sending unit is configured to send a request response message to the MME, wherein
the request response message comprises the MMECs of all the MMEs, so that the MME
determines a backup MME of the MME according to the MMECs of all the MMEs;
the receiving unit is further configured to receive an interface request message sent
by the MME, wherein the interface request message comprises an MMEC of the backup
MME and the pool identity of the MME pool, and the interface request message is used
to request to acquire interface information of the backup MME;
the second acquiring unit is configured to acquire the interface information of the
backup MME according to the MMEC of the backup MME and the pool identity of the MME
pool; and
the sending unit is configured to send an interface response message to the MME, wherein
the interface response message comprises the interface information of the backup MME,
so that the MME sends, according to the interface information of the backup MME, user
information of user equipment UE attached to the MME to the backup MME.
19. A serving mobility management entity MME, wherein the serving MME comprises a receiving
unit, an acquiring unit, and a serving unit, wherein:
the receiving unit is configured to: after a mobility management entity MME to which
user equipment UE is attached becomes faulty, receive a service request message sent
by the UE by using an evolved NodeB eNodeB, wherein the service request message comprises
an identity of the UE and an identity of the MME to which the UE is attached, the
service request message is used to request the MME to which the UE is attached to
provide a service for the UE, the serving MME is an MME selected, after the MME to
which the UE is attached becomes faulty, by the eNodeB to provide a service for the
UE, and the MME to which the UE is attached and the serving MME are located in a same
MME pool;
the acquiring unit is configured to acquire user information of the UE according to
the identity of the UE or according to the identity of the UE and the identity of
the MME to which the UE is attached; and
the serving unit is configured to provide, according to the user information of the
UE, the service corresponding to the service request message for the UE.
20. The serving MME according to claim 19, wherein the receiving unit is further configured
to: receive the user information of the UE and the identity of the UE that are sent
by the MME to which the UE is attached, and record a correspondence between the user
information of the UE and the identity of the UE; and
the acquiring unit is specifically configured to acquire, according to the identity
of the UE, the user information that is of the UE and saved by the serving MME.
21. The serving MME according to claim 19, wherein the acquiring unit is specifically
configured to:
acquire, according to the identity of the MME to which the UE is attached, interface
information of a backup MME of the MME to which the UE is attached, and acquire, from
the backup MME, the user information of the UE according to the identity of the UE
and the interface information of the backup MME, wherein the backup MME and the serving
MME are located in a same MME pool.
22. The serving MME according to claim 21, wherein the identity of the MME to which the
UE is attached is an MME code MMEC of the MME to which the UE is attached, and the
acquiring unit is specifically configured to:
send a request message to a domain name system DNS server, wherein the request message
comprises a pool identity of an MME pool in which the serving MME is located, and
the request message is used to request to acquire MME codes MMECs of all MME in the
MME pool;
receive a request response message sent by the DNS server, wherein the request response
message comprises the MMECs of all the MMEs in the MME pool;
acquire, according to the MMEC of the MME to which the UE is attached and the MMECs
of all the MMEs and according to a preset policy, the backup MME of the MME to which
the UE is attached;
send an interface request message to the DNS server, wherein the interface request
message comprises an MMEC of the backup MME and the pool identity of the MME pool,
so that the DNS server acquires the interface information of the backup MME according
to the pool identity of the MME pool and the MMEC of the backup MME; and
receive an interface response message sent by the DNS server, wherein the interface
response message comprises the interface information of the backup MME.
23. The serving MME according to any one of claims 19 to 22, wherein the service request
message is a Voice over Long Term Evolution VoLTE mobile originated service request
message of the UE, or a circuit switched fallback CSFB request message of the UE,
or a 1xCSF request message of the UE, and the identity 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 identity of the MME to which the UE is attached is a globally unique temporary
identity GUTI allocated to the UE by the MME to which the UE is attached, wherein
the GUTI comprises the MMEC of the MME to which the UE is attached.
24. The serving MME according to any one of claims 19 to 23, wherein the identity of the
UE is a short temporary mobile subscriber identity S-TMSI of the UE.
25. The serving MME according to any one of claims 19 to 24, wherein the serving MME further
comprises a determining unit and a sending unit, wherein:
the determining unit is configured to determine, according to the user information
of the UE, that the UE is an authorized user; and
the sending unit is configured to separately send a modification request message to
a serving gateway SGW and a home subscriber server HSS that are connected to the serving
MME, wherein the modification request message comprises the identity of the UE, and
the modification request message is used to request the SGW or the HSS to modify a
correspondence between the UE and the MME to which the UE is attached to a correspondence
between the UE and the serving MME; and reallocate a GUTI to the UE, and send the
reallocated GUTI to the UE, so that the UE is attached to the serving MME.
26. A serving mobility management entity MME, wherein the serving MME comprises a receiving
unit, an acquiring unit, and a paging unit, wherein:
the receiving unit is configured to: after a mobility management entity MME to which
user equipment UE is attached becomes faulty, receive a paging request message sent
by a network element of a core network in a circuit switched CS domain that is in
a second-generation mobile communications technology 2G network or a third-generation
mobile communications technology 3G network, wherein the paging request message comprises
an identity of the UE, the paging request message is used to request to initiate CSFB
paging or 1xCSF paging on the UE, the serving MME is an MME that provides a service
for the UE when the MME to which the UE is attached becomes faulty, and the MME to
which the UE is attached and the serving MME are located in a same MME pool;
the acquiring unit is configured to acquire user information of the UE according to
the identity of the UE; and
the paging unit is configured to acquire, according to the user information, a tracking
area in which the UE is located, and initiate a paging request in the tracking area.
27. The serving MME according to claim 26, wherein the serving MME further comprises a
recording unit, wherein:
the receiving unit is further configured to receive the user information of the UE
and the identity of the UE that are sent by the MME to which the UE is attached;
the recording unit is configured to record a correspondence between the user information
of the UE and the identity of the UE; and
the acquiring unit is configured to acquire, according to the identity of the UE,
the user information that is of the UE and saved by the serving MME.
28. The serving MME according to claim 26, wherein the serving MME further comprises a
sending unit, wherein:
the sending unit is configured to send a broadcast request message to all MMEs in
the MME pool, wherein the broadcast request message comprises the identity of the
UE, and the broadcast request message is used to request to acquire the user information
of the UE; and
the receiving unit is further configured to receive a broadcast response message of
a backup MME of the MME to which the UE is attached, wherein the broadcast response
message comprises the user information of the UE.