CN108668307B - Called service recovery processing method, mobility management entity and service gateway - Google Patents
Called service recovery processing method, mobility management entity and service gateway Download PDFInfo
- Publication number
- CN108668307B CN108668307B CN201710198812.5A CN201710198812A CN108668307B CN 108668307 B CN108668307 B CN 108668307B CN 201710198812 A CN201710198812 A CN 201710198812A CN 108668307 B CN108668307 B CN 108668307B
- Authority
- CN
- China
- Prior art keywords
- management entity
- mobility management
- service
- backup
- called
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a service recovery processing method, a mobility management entity and a service gateway. Wherein the method comprises the following steps: receiving a downlink data notification message, wherein the DDN message comprises an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to an MME attached to a called user detected to have a fault by a service gateway, and the MME is added to a DDN message by an SGW; searching a synchronous interface address of a backup MME corresponding to the MME attached to the called user in a backup relation table according to the service address; wherein, the backup relation table is preset; and acquiring the called user data from the backup MME according to the IMSI and the synchronous interface address so as to recover the called service. The called service recovery processing method, the mobility management entity and the serving gateway provided by the embodiment of the invention can avoid generating a large amount of extra signaling, save system resources and improve the efficiency of called service recovery.
Description
Technical Field
The invention relates to the technical field of mobile communication, in particular to a called service recovery processing method, a mobility management entity and a service gateway.
Background
A Mobility Management Entity (MME) is a key control node of a 3GPP protocol LTE access network, and is responsible for functions such as Mobility Management, bearer Management, authentication and authentication of a user, selection of a Packet data network (PGW) and a Serving Gateway (SGW).
In a called service of a Voice over LTE (VoLTE), if an SGW detects an MME failure attached to a called user through a failure detection mechanism, after receiving an IP Multimedia Subsystem (IMS) signaling included in a Downlink Data message sent by a PGW, a Downlink Data Notification (DDN) message cannot be sent to the failed MME, which causes a signaling flow to be interrupted and the called service to be affected. As shown in fig. 1, in the prior art, a Mobility Management Entity Pool (MME Pool) technology is used for disaster recovery Management, and a called service recovery scheme is as follows: in disaster recovery, any MME in normal operation receives a DDN message carrying an International Mobile Subscriber identity Number (IMSI) sent by the SGW, polls other MMEs in the MME Pool in normal operation according to the IMSI information, acquires called Subscriber data from the MME backed up with the called Subscriber information, and triggers recovery of the called service. In the above scheme, a large amount of signaling is generated in the polling process, especially considering that an MME generally contains hundreds of thousands of user data and an MME Pool may contain up to hundreds of MMEs, which consumes system resources and has the problem of low called service recovery efficiency.
Therefore, how to provide a method to improve the efficiency of recovering the called service becomes an important issue to be solved urgently in the industry.
Disclosure of Invention
Aiming at the defects in the prior art, the embodiment of the invention provides a called service recovery processing method, a mobility management entity and a serving gateway.
In one aspect, an embodiment of the present invention provides a method for recovering and processing a called service, including:
a mobile management entity receives a downlink data notification message, wherein the downlink data notification message comprises an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message;
the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached by the called user in a backup relation table according to the service address; wherein, the backup relation table is preset;
and the mobility management entity acquires the called user data from the backup mobility management entity according to the international mobile subscriber identification code and the synchronous interface address so as to recover the called service.
On the other hand, an embodiment of the present invention further provides a method for processing a called service recovery, including:
after detecting that a mobile management entity attached to a called user has a fault, a service gateway adds a service address corresponding to the mobile management entity attached to the called user to a downlink data notification message;
the service gateway sends the downlink data notification message to any normally working mobility management entity, so that the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address, and acquires the called user data from the backup mobility management entity according to an international mobile subscriber identification code and the synchronous interface address so as to recover the called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
In another aspect, an embodiment of the present invention provides a mobility management entity, including:
a receiving unit, configured to receive a downlink data notification message, where the downlink data notification message includes an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message;
a first searching unit, configured to search, according to the service address, a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relationship table; wherein, the backup relation table is preset;
and the service recovery unit is used for acquiring the called user data from the backup mobility management entity according to the international mobile subscriber identity and the synchronous interface address so as to recover the called service.
In another aspect, an embodiment of the present invention provides a service gateway, including:
an adding unit, configured to add, after detecting that a mobility management entity attached to a called subscriber has a fault, a service address corresponding to the mobility management entity attached to the called subscriber to a downlink data notification message;
a sending unit, configured to send the downlink data notification message to any normally operating mobility management entity, so that the mobility management entity searches, according to the service address, a synchronization interface address of a backup mobility management entity corresponding to the mobility management entity to which the called user is attached in a backup relationship table, and obtains data of the called user from the backup mobility management entity according to an international mobile subscriber identity and the synchronization interface address, so as to recover a called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
According to the called service recovery processing method, the mobility management entity and the service gateway provided by the embodiment of the invention, the service address of the mobility management entity attached to the called user can be carried by the downlink data notification message, and the synchronous interface address of the backup mobility management entity is searched in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic diagram illustrating a called service recovery flow when an MME fails in the prior art;
fig. 2 is a flowchart illustrating a called service recovery processing method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a chained backup manner of user data in an MME Pool according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a called service recovery processing method according to another embodiment of the present invention;
fig. 5 is a schematic structural diagram of a mobility management entity according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a mobility management entity according to another embodiment of the present invention;
fig. 7 is a schematic structural diagram of a service gateway according to an embodiment of the present invention;
fig. 8 is a signaling interaction diagram of a called service recovery processing method according to an embodiment of the present invention;
fig. 9 is a schematic entity structure diagram of a mobility management entity according to an embodiment of the present invention;
fig. 10 is a schematic entity structure diagram of a service gateway according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 2 is a schematic flowchart of a called service recovery processing method according to an embodiment of the present invention, and as shown in fig. 2, the called service recovery processing method according to the embodiment of the present invention includes:
s201, a mobility management entity receives a downlink data notification message, wherein the downlink data notification message comprises an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message;
specifically, for a called service of a voice service based on LTE, when a serving gateway detects that a mobility management entity attached to a called user fails, an SGW adds a service address of an MME attached to the called user to a downlink data notification message, for example, expands a private cell for a DDN message, and uses the private cell to carry the service address; and then sending the DDN message to an MME, wherein the MME can be any MME which normally works in MME Pool, the MME can receive the DDN message sent by the SGW, and the DDN message also comprises the international mobile subscriber identity of the called user.
S202, the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address; wherein, the backup relation table is preset;
specifically, after receiving the DDN message, the MME searches for a synchronous interface address of a backup mobility management entity in a backup relationship table according to the service address included in the DDN message, where the backup MME corresponds to the MME to which the called user is attached and stores the called user data; the backup relation table is preset and comprises the service address and a synchronous interface address of a backup mobile management entity corresponding to the service address.
S203, the mobility management entity acquires the called user data from the backup mobility management entity according to the international mobile subscriber identity and the synchronous interface address so as to recover the called service.
Specifically, after the MME finds the synchronization interface address, the MME accesses the backup MME through the synchronization interface address, and searches for the called user data in the user data stored in the backup MME according to the IMSI of the called user, where the called user data may include an IMSI, a Tracking Area List (TA List), and context information, and if the IMSI included in the user data stored in the backup MME is the same as the IMSI of the called user, the MME may obtain the TA List and the context information of the called user, and send a paging message to the called user according to the IMSI, the TA List, and the context information of the called user, so as to recover the called service.
For example, table 1 is an MME backup relationship table in MME Pool, and as shown in table 1, the service address of the MME corresponds to the synchronous interface address of the only backup MME. Assuming that the called user is attached to the shme 12BER, it can be known from table 1 that the called user data is backed up on the shme 13 BER. And when the SGW detects that the SHMME12BER fails and the called user has called service, triggering a called service recovery process. After the SGW finds that the BER of the shme 12 has failed through a failure detection mechanism, the SGW adds the service address 221.170.0.12 of the BER of the shme 12 to the DDN message, and sends the DDN message to any MME capable of working normally in the MME Pool, assuming that the DDN message is sent to the MME16BER, where the DDN message carries the service address 221.170.0.12 of the BER of the shme 12 and the IMSI of the called user.
After receiving the DDN message, the shme 16BER finds the synchronous interface address 10.10.0.13 of the shme 13BER in table 1 according to the service address 221.170.0.12. The SHMME16BER initiates a user data recovery request to the SHMME13BER through the synchronous interface address 10.10.0.13 to recover the user data, namely, the SHMME13BER is accessed through the synchronous interface address 10.10.0.13, the TA List and the context information of the called user are obtained according to the IMSI of the called user, and then the paging message is sent to the called user according to the IMSI, the TA List and the context information of the called user, so that the called service is recovered.
Table 1 MME Pool MME backup relation table
According to the called service recovery processing method provided by the embodiment of the invention, the service address of the mobility management entity attached to the called user can be carried by the downlink data notification message, and the synchronous interface address of the backup mobility management entity is searched in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved.
On the basis of the foregoing embodiment, further, the method for processing a called service recovery provided in the embodiment of the present invention further includes:
after receiving the downlink data notification message, the mobility management entity searches the name of the backup mobility management entity in the backup relation table according to the service address; and if the mobile management entity judges that the name is the same as the local name, the mobile management entity locally queries the data of the called user according to the international mobile subscriber identity.
Specifically, after receiving the DDN message, the MME searches the backup MME name in the backup relationship table according to the service address included in the DDN message, and compares the searched backup MME name with the local name, and if the backup MME name is the same as the local name, it indicates that the MME is the backup MME. And the MME locally inquires the called user data according to the IMSI of the called user. The backup relation table includes the service address and the name of the backup MME corresponding to the service address.
For example, assuming that the called user is attached to the shme 12BER, it can be known from table 1 that the data backup of the called user is on the shme 13 BER. And when the SGW detects that the SHMME12BER fails and the called user has called service, triggering a called service recovery process. After the SGW finds that the shme 12BER has failed through a failure detection mechanism, the SGW sends a DDN message to the shme 13BER, and the shme 13BER finds that the backup MME of the shme 12BER is the shme 13BER according to the service address 221.170.0.12 of the shme 12BER, that is, the backup MME is the shme 13BER itself, so that the shme 13BER locally queries the called user data according to the IMSI of the called user.
According to the called service recovery processing method provided by the embodiment of the invention, the service address of the mobility management entity attached to the called user can be carried by the downlink data notification message, and the synchronous interface address of the backup mobility management entity is searched in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved. And the mobility management entity locally inquires the data of the called user through the IMSI, so that the efficiency of recovering the called service can be further improved.
On the basis of the above embodiments, further, when the called user data is attached to the called user or the called user data is changed, the mobility management entity attached to the called user synchronizes to the backup mobility management entity through the synchronous interface address.
Specifically, in order to implement the recovery of the called service, the data of the called user needs to be backed up in advance, a synchronous interface may be established between the MME to which the called user is attached and the backup MME, and a unique synchronous interface address may be allocated. And when the called user is in the attachment stage or the data of the called user is changed, the MME attached to the called user synchronizes the called user data to the backup MME through the synchronous interface address, so that the called user data is backed up. The called subscriber data may include IMSI, TA List, and subscriber context information.
The establishment of the synchronous interface between the MME and the backup MME can be implemented as follows. (1) The method includes that user information backup is achieved between an MME and a backup MME through a private Protocol interface (Sds), and specifically, a backup process of the user information between the MME and the backup MME is completed through a Protocol layer (Sds Application Protocol, SdsAP) of the Sds interface. For example, the MME may back up the information of the new User a to the backup MME through an Add User Data Request message, that is, the User attachment is completed; after the information backup of the User A is completed, if the information of the User A is changed in the subsequent service process, the MME can back up the changed part of the increment to the backup MME through an Update User Data Request message. When the User A is detached, or is moved to another MME or leaves the MME Pool, the MME informs the standby MME to Delete the backup information of the User A through a Delete User Data Request message. (2) And the MME and the backup MME multiplex an S10 interface, expand interface information, and contain the user data backup Request and the Response flow in the Echo Request and Echo Response information of the S10 interface to realize the backup of the user data. The triggering mode and message body content of the user data synchronization signaling in the Echo Request and Response signaling messages are similar to the Sds interface, and are not described here again.
According to the called service recovery processing method provided by the embodiment of the invention, the service address of the mobility management entity attached to the called user can be carried by the downlink data notification message, and the synchronous interface address of the backup mobility management entity is searched in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved. And the data of the called user is backed up through the synchronous interface, so that the data of the called user can be quickly recovered, and the recovery of the called service is facilitated.
Fig. 3 is a schematic diagram of a chain backup manner of user data in an MME Pool according to an embodiment of the present invention, and as shown in fig. 3, on the basis of the foregoing embodiments, further, a mobility management entity attached to the called user synchronizes to the backup mobility management entity through a synchronous interface, including a chain backup manner.
Specifically, the chained backup manner is that the MMEs within the MME Pool are cyclically backed up, as shown in fig. 3, the MME2 backs up the user data on the MME1, the MME3 backs up the user data on the MME2, and the MME1 backs up the user data on the MME 3. The chained backup can distribute the online user data to be backed up to each MME for processing, thereby avoiding the congestion of a synchronous interface and being beneficial to backing up the user data in real time.
According to the called service recovery processing method provided by the embodiment of the invention, the service address of the mobility management entity attached to the called user can be carried by the downlink data notification message, and the synchronous interface address of the backup mobility management entity is searched in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved. And the user data is backed up by adopting a chain backup mode, which is favorable for backing up the user data in real time.
Fig. 4 is a schematic flowchart of a called service recovery processing method according to another embodiment of the present invention, and as shown in fig. 4, the called service recovery processing method according to the embodiment of the present invention includes:
s401, after detecting that a mobile management entity attached to a called user has a fault, a service gateway adds a service address corresponding to the mobile management entity attached to the called user to a downlink data notification message;
specifically, for the called service of VoLTE, after the serving gateway detects that the mobility management entity attached to the called user has a fault, the SGW adds the service address to the downlink data notification message, for example, expands a private cell for the DDN message, and uses the private cell to carry the service address. Wherein the service address is the service address of the MME attached to the called user.
The SGW may perform failure detection on the MME through a failure detection mechanism. The failure detection mechanism comprises: performing fault detection through an Echo Request/Response message of a GTP-C protocol, for example, if the Echo Request message sent by the SGW to the MME has no Response, the SGW starts fault detection on the MME, and when no Response of the MME is received by continuous requests for many times, the SGW judges that the MME has a fault; or the fault detection is carried out through the Recovery cell in the GTP-C signaling message, for example, the SGW and the MME can record the restart counter value of the other party through the Recovery cell carried in the GTP-C signaling message. When MME fails and restarts, the local restart counter is increased and sent to SGW in Recovery cell contained in GTP-C signaling message, after SGW receives message, the value of the restart counter of MME is compared with the value stored before, if the value of the restart counter is larger than the value stored before, SGW judges MME failure.
S402, the service gateway sends the downlink data notification message to any normally working mobility management entity, so that the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address, and acquires the called user data from the backup mobility management entity according to an international mobile subscriber identification code and the synchronous interface address to recover the called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
Specifically, the SGW sends the DDN message carrying the service address and the IMSI of the called user to the MME, which may be any one of MME Pool that normally operates. After receiving the DDN message, the MME searches a synchronous interface address of a backup mobility management entity in a backup relation table according to the service address, wherein the backup MME corresponds to the MME attached to the called user and stores the called user data; after the MME finds the synchronous interface address, the MME is accessed through the synchronous interface address, the called user data is searched in the user data stored in the backup MME according to the IMSI of the called user, the called user data can comprise the IMSI, the TA List and the context information, if the IMSI included in the user data stored in the backup MME is the same as the IMSI of the called user, the MME can obtain the TA List and the context information of the called user, and a paging message is sent according to the IMSI, the TA List and the context information of the called user, so that the called service is recovered. The backup relation table is preset and comprises the service address and a synchronous interface address of a backup mobile management entity corresponding to the service address.
According to the called service recovery processing method provided by the embodiment of the invention, the service address of the mobility management entity attached to the called user can be carried by the downlink data notification message, and the synchronous interface address of the backup mobility management entity is searched in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved.
Fig. 5 is a schematic structural diagram of a mobility management entity provided in an embodiment of the present invention, and as shown in fig. 5, the mobility management entity provided in the embodiment of the present invention includes a receiving unit 501, a first searching unit 502, and a service recovering unit 503, where:
the receiving unit 501 is configured to receive a downlink data notification message, where the downlink data notification message includes an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message; the first searching unit 502 is configured to search, according to the service address, a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relationship table; wherein, the backup relation table is preset; the service recovery unit 503 is configured to obtain the called user data from the backup mobility management entity according to the international mobile subscriber identity and the synchronous interface address, so as to recover the called service.
Specifically, for a called service of a voice service based on LTE, when a serving gateway detects that a mobility management entity attached to a called user fails, an SGW adds a service address of an MME attached to the called user to a downlink data notification message, for example, expands a private cell for a DDN message, and uses the private cell to carry the service address; then, the DDN message is sent to an MME, where the MME may be any MME in MME Pool that normally works, and the receiving unit 501 receives the DDN message sent by the SGW, where the DDN message further includes an international mobile subscriber identity of the called user.
After the receiving unit 501 receives the DDN message, the first searching unit 502 searches a synchronous interface address of a backup mobility management entity in a backup relation table according to the service address contained in the DDN message, where the backup MME corresponds to the MME to which the called user is attached and stores the called user data; the backup relation table is preset and comprises the service address and a synchronous interface address of a backup mobile management entity corresponding to the service address.
After the MME finds the synchronization interface address, the service recovery unit 503 accesses the backup MME through the synchronization interface address, and searches the called user data in the user data stored in the backup MME according to the IMSI of the called user, where the called user data may include an IMSI, a Tracking Area List (TA List), and context information, and if the IMSI included in the user data stored in the backup MME is the same as the IMSI of the called user, the service recovery unit 503 may obtain the TA List and the context information of the called user, and send a paging message to the called user according to the IMSI, the TA List, and the context information of the called user, so as to recover the called service.
The mobility management entity provided by the embodiment of the invention can receive the service address of the mobility management entity attached to the called user carried by the downlink data notification message and search the synchronous interface address of the backup mobility management entity in the backup relation table according to the service address, so that the data of the called user can be obtained through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved.
Fig. 6 is a schematic structural diagram of a mobility management entity according to another embodiment of the present invention, and as shown in fig. 6, the mobility management entity according to the embodiment of the present invention further includes a second searching unit 504 and a querying unit 505, where:
the second searching unit 504 is configured to search, after receiving the downlink data notification message, the name of the backup mobility management entity in the backup relationship table according to the service address; the query unit 505 is configured to query the called user data locally according to the international mobile subscriber identity if it is determined that the name is the same as the local name.
Specifically, after the MME receives the DDN message, the second searching unit 504 searches the name of the backup MME in the backup relationship table according to the service address included in the DDN message, and the querying unit 505 compares the searched name of the backup MME with the local name, and if the name of the backup MME is the same as the local name, it indicates that the MME is the backup MME. The query unit 505 locally queries the data of the called user according to the IMSI of the called user. The backup relation table includes the service address and the name of the backup MME corresponding to the service address.
The mobility management entity provided by the embodiment of the invention can receive the service address of the mobility management entity attached to the called user carried by the downlink data notification message and search the synchronous interface address of the backup mobility management entity in the backup relation table according to the service address, so that the data of the called user can be acquired through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved. And the mobility management entity locally inquires the data of the called user through the IMSI, so that the efficiency of recovering the called service can be further improved.
On the basis of the above embodiments, further, when the called user data is attached to the called user or the called user data is changed, the mobility management entity attached to the called user synchronizes to the backup mobility management entity through the synchronous interface address.
Specifically, in order to implement the recovery of the called service, the data of the called user needs to be backed up in advance, a synchronous interface may be established between the MME to which the called user is attached and the backup MME, and a unique synchronous interface address may be allocated. And when the called user is in the attachment stage or the data of the called user is changed, the MME attached to the called user synchronizes the called user data to the backup MME through the synchronous interface address, so that the called user data is backed up. The called subscriber data may include IMSI, TA List, and subscriber context information.
The mobility management entity provided by the embodiment of the invention can receive the service address of the mobility management entity attached to the called user carried by the downlink data notification message and search the synchronous interface address of the backup mobility management entity in the backup relation table according to the service address, so that the data of the called user can be acquired through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved. And the data of the called user is backed up through the synchronous interface, so that the data of the called user can be quickly recovered, and the recovery of the called service is facilitated.
On the basis of the above embodiments, further, the synchronizing of the mobility management entity attached to the called subscriber to the backup mobility management entity through the synchronous interface address includes a chain backup manner.
Specifically, the chain backup manner is a cyclic backup between MMEs in the MME Pool, for example, MME2 backs up user data on MME1, MME3 backs up user data on MME2, and MME1 backs up user data on MME 3. The chained backup can distribute the online user data to be backed up to each MME for processing, thereby avoiding the congestion of a synchronous interface and being beneficial to backing up the user data in real time.
The mobility management entity provided by the embodiment of the invention can receive the service address of the mobility management entity attached to the called user carried by the downlink data notification message and search the synchronous interface address of the backup mobility management entity in the backup relation table according to the service address, so that the data of the called user can be acquired through the synchronous interface address and the IMSI, a large amount of extra signaling is avoided, the system resource can be saved, and the called service recovery efficiency is improved. And the user data is backed up by adopting a chain backup mode, which is favorable for backing up the user data in real time.
The embodiment of the mobility management entity provided in the present invention may be specifically configured to execute the processing procedure of the corresponding method embodiment, and the functions of the embodiment are not described herein again, and refer to the detailed description of the corresponding method embodiment.
Fig. 7 is a schematic structural diagram of a service gateway provided in an embodiment of the present invention, and as shown in fig. 7, the service gateway provided in the embodiment of the present invention includes an adding unit 701 and a sending unit 702, where:
the adding unit 701 is configured to add, after detecting that a mobility management entity attached to a called subscriber fails, a service address corresponding to the mobility management entity attached to the called subscriber to a downlink data notification message; the sending unit 702 is configured to send the downlink data notification message to any normally operating mobility management entity, so that the mobility management entity searches, according to the service address, a synchronization interface address of a backup mobility management entity corresponding to the mobility management entity to which the called user is attached in a backup relationship table, and obtains data of the called user from the backup mobility management entity according to an international mobile subscriber identity and the synchronization interface address, so as to recover a called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
Specifically, for the called service of VoLTE, after the serving gateway detects that the mobility management entity attached to the called user has a failure, the adding unit 701 may add the service address to the downlink data notification message, for example, expand a private cell for the DDN message, and use the private cell to carry the service address. Wherein the service address is the service address of the MME attached to the called user.
The sending unit 702 sends the DDN message carrying the service address and the IMSI of the called user to an MME, which may be any MME in MME Pool that normally works. After receiving the DDN message, the MME searches a synchronous interface address of a backup mobility management entity in a backup relation table according to the service address, wherein the backup MME corresponds to the MME attached to the called user and stores the called user data; after the MME finds the synchronous interface address, the MME is accessed through the synchronous interface address, the called user data is searched in the user data stored in the backup MME according to the IMSI of the called user, the called user data can comprise the IMSI, the TA List and the context information, if the IMSI included in the user data stored in the backup MME is the same as the IMSI of the called user, the MME can obtain the TA List and the context information of the called user, and a paging message is sent according to the IMSI, the TA List and the context information of the called user, so that the called service is recovered. The backup relation table is preset and comprises the service address and a synchronous interface address of a backup mobile management entity corresponding to the service address.
The service gateway provided by the embodiment of the invention can send the service address of the mobility management entity attached to the called user, which is carried by the downlink data notification message, to the mobility management entity, so that the service gateway can search the synchronous interface address of the backup mobility management entity in the backup relation table according to the service address, and obtain the data of the called user through the synchronous interface address and the IMSI, thereby avoiding generating a large amount of extra signaling, saving system resources and improving the efficiency of called service recovery.
The embodiment of the service gateway provided by the present invention may be specifically configured to execute the processing flow of the corresponding method embodiment, and the functions of the embodiment are not described herein again, and refer to the detailed description of the corresponding method embodiment.
Fig. 8 is a signaling interaction diagram of a called service recovery processing method according to an embodiment of the present invention, and as shown in fig. 8, a called service recovery processing flow according to an embodiment of the present invention is as follows:
the first step is as follows: after detecting that the mobility management entity attached to the called user has a fault through a fault detection mechanism, the service gateway adds the service address corresponding to the mobility management entity attached to the called user into the DDN message;
the second step is that: the service gateway sends the DDN message carrying the service address and the IMSI of the called user to an MME, wherein the MME is any one of MME Pool which normally works;
the third step: the MME searches a synchronous interface address of a backup MME corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address; the backup relation table stores the service address and a synchronous interface address of a backup mobile management entity corresponding to the service address;
the fourth step: the MME sends a data recovery request to a backup MME, wherein the data recovery request comprises the synchronous interface address and the IMSI of the called user so as to acquire the data of the called user;
the fifth step: the MME receives the called user data returned by the backup MME, wherein the called user data comprises a TA List and context information;
and a sixth step: and the MME sends a paging message to the called user according to the obtained TA List, the context information and the IMSI.
Fig. 9 is a schematic entity structure diagram of a mobility management entity according to an embodiment of the present invention, and as shown in fig. 9, the mobility management entity according to the present invention includes:
a processor (processor)901, a memory (memory)902, and a communication bus 903;
wherein the content of the first and second substances,
the processor 901 and the memory 902 complete mutual communication through the communication bus 903;
the processor 901 is configured to call the program instructions in the memory 902 to execute the following called service recovery processing method, including: receiving a downlink data notification message, wherein the downlink data notification message comprises an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message; searching a synchronous interface address of a backup mobile management entity corresponding to the mobile management entity attached to the called user in a backup relation table according to the service address; wherein, the backup relation table is preset; and acquiring the called user data from the backup mobile management entity according to the international mobile subscriber identification code and the synchronous interface address so as to recover the called service.
An embodiment of the present invention provides a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions cause a computer to execute a called service recovery processing method, for example, receive a downlink data notification message, where the downlink data notification message includes an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message; searching a synchronous interface address of a backup mobile management entity corresponding to the mobile management entity attached to the called user in a backup relation table according to the service address; wherein, the backup relation table is preset; and acquiring the called user data from the backup mobile management entity according to the international mobile subscriber identification code and the synchronous interface address so as to recover the called service.
An embodiment of the present invention provides a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, when the program instructions are executed by a computer, the computer being capable of executing a called service recovery processing method, including, for example: receiving a downlink data notification message, wherein the downlink data notification message comprises an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message; searching a synchronous interface address of a backup mobile management entity corresponding to the mobile management entity attached to the called user in a backup relation table according to the service address; wherein, the backup relation table is preset; and acquiring the called user data from the backup mobile management entity according to the international mobile subscriber identification code and the synchronous interface address so as to recover the called service.
Fig. 10 is a schematic entity structure diagram of a service gateway provided in an embodiment of the present invention, and as shown in fig. 10, the service gateway provided in the present invention includes:
a processor (processor)1001, a memory (memory)1002, and a communication bus 1003;
wherein the content of the first and second substances,
the processor 1001 and the memory 1002 complete communication with each other through the communication bus 1003;
the processor 1001 is configured to call the program instructions in the memory 1002 to execute the called service recovery processing method, which includes: after detecting that a mobile management entity attached to a called user has a fault, adding a service address corresponding to the mobile management entity attached to the called user into a downlink data notification message; sending the downlink data notification message to any normally working mobility management entity, so that the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address, and acquires the called user data from the backup mobility management entity according to an international mobile subscriber identity and the synchronous interface address to recover the called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
The embodiment of the present invention provides a non-transitory computer readable storage medium, which stores a computer instruction, where the computer instruction causes the computer to execute a called service recovery processing method, for example, after detecting that a mobility management entity attached to a called user has a fault, adding a service address corresponding to the mobility management entity attached to the called user to a downlink data notification message; sending the downlink data notification message to any normally working mobility management entity, so that the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address, and acquires the called user data from the backup mobility management entity according to an international mobile subscriber identity and the synchronous interface address to recover the called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
An embodiment of the present invention provides a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, when the program instructions are executed by a computer, the computer being capable of executing a called service recovery processing method, including, for example: after detecting that a mobile management entity attached to a called user has a fault, adding a service address corresponding to the mobile management entity attached to the called user into a downlink data notification message; sending the downlink data notification message to any normally working mobility management entity, so that the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address, and acquires the called user data from the backup mobility management entity according to an international mobile subscriber identity and the synchronous interface address to recover the called service; wherein the backup relation table is preset, and the downlink data notification message includes the international mobile subscriber identity.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A called service recovery processing method is characterized by comprising the following steps:
a mobile management entity receives a downlink data notification message, wherein the downlink data notification message comprises an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message;
the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached by the called user in a backup relation table according to the service address; wherein, the backup relation table is preset;
the mobility management entity acquires the called user data from the backup mobility management entity according to the international mobile subscriber identity and the synchronous interface address so as to recover the called service; the called user data includes the international mobile subscriber identity, a tracking area list and context information.
2. The method of claim 1, further comprising:
after receiving the downlink data notification message, the mobility management entity searches the name of the backup mobility management entity in the backup relation table according to the service address;
and if the mobile management entity judges that the name is the same as the local name, the mobile management entity locally queries the data of the called user according to the international mobile subscriber identity.
3. The method according to claim 1 or 2,
and when the called user data is attached to the called user or the called user data is changed, the mobile management entity attached to the called user synchronizes to the backup mobile management entity through the synchronous interface address.
4. The method of claim 3, wherein the synchronizing the mobility management entity to which the called subscriber is attached to the backup mobility management entity through the synchronization interface address comprises a chained backup manner.
5. A called service recovery processing method is characterized by comprising the following steps:
after detecting that a mobile management entity attached to a called user has a fault, a service gateway adds a service address corresponding to the mobile management entity attached to the called user to a downlink data notification message;
the service gateway sends the downlink data notification message to any normally working mobility management entity, so that the mobility management entity searches a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relation table according to the service address, and acquires the called user data from the backup mobility management entity according to an international mobile subscriber identification code and the synchronous interface address so as to recover the called service; the backup relation table is preset, and the downlink data notification message comprises the international mobile subscriber identity; the called user data includes the international mobile subscriber identity, a tracking area list and context information.
6. A mobility management entity, comprising:
a receiving unit, configured to receive a downlink data notification message, where the downlink data notification message includes an international mobile subscriber identity and a service address of a called subscriber; the service address corresponds to a mobility management entity attached to a called user whose service gateway detects that a fault occurs, and the service gateway adds the service address to the downlink data notification message;
a first searching unit, configured to search, according to the service address, a synchronous interface address of a backup mobility management entity corresponding to the mobility management entity attached to the called user in a backup relationship table; wherein, the backup relation table is preset;
a service recovery unit, configured to obtain the called user data from the backup mobility management entity according to the international mobile subscriber identity and the synchronous interface address, so as to recover a called service; the called user data includes the international mobile subscriber identity, a tracking area list and context information.
7. The mobility management entity according to claim 6, further comprising:
a second searching unit, configured to search, after receiving the downlink data notification message, a name of the backup mobility management entity in the backup relationship table according to the service address;
and the query unit is used for locally querying the called user data according to the international mobile subscriber identity if the name is judged to be the same as the local name.
8. Mobility management entity according to claim 6 or 7,
and when the called user data is attached to the called user or the called user data is changed, the mobile management entity attached to the called user synchronizes to the backup mobile management entity through the synchronous interface address.
9. The mobility management entity of claim 8, wherein the mobility management entity to which the called subscriber is attached synchronizes to the backup mobility management entity through the synchronization interface address, and wherein the synchronization comprises a chained backup manner.
10. A serving gateway, comprising:
an adding unit, configured to add, after detecting that a mobility management entity attached to a called subscriber has a fault, a service address corresponding to the mobility management entity attached to the called subscriber to a downlink data notification message;
a sending unit, configured to send the downlink data notification message to any normally operating mobility management entity, so that the mobility management entity searches, according to the service address, a synchronization interface address of a backup mobility management entity corresponding to the mobility management entity to which the called user is attached in a backup relationship table, and obtains data of the called user from the backup mobility management entity according to an international mobile subscriber identity and the synchronization interface address, so as to recover a called service; the backup relation table is preset, and the downlink data notification message comprises the international mobile subscriber identity; the called user data includes the international mobile subscriber identity, a tracking area list and context information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710198812.5A CN108668307B (en) | 2017-03-29 | 2017-03-29 | Called service recovery processing method, mobility management entity and service gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710198812.5A CN108668307B (en) | 2017-03-29 | 2017-03-29 | Called service recovery processing method, mobility management entity and service gateway |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108668307A CN108668307A (en) | 2018-10-16 |
| CN108668307B true CN108668307B (en) | 2021-04-27 |
Family
ID=63786768
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710198812.5A Active CN108668307B (en) | 2017-03-29 | 2017-03-29 | Called service recovery processing method, mobility management entity and service gateway |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108668307B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020193445A1 (en) | 2019-03-28 | 2020-10-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Transferring monitoring event information during a mobility procedure |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101646270A (en) * | 2008-08-06 | 2010-02-10 | 华为技术有限公司 | Method, system, mobility management entity and memory device for maintaining service continuity |
| CN101730124A (en) * | 2008-10-29 | 2010-06-09 | 华为技术有限公司 | Method, device and system for resuming service |
| CN103108416A (en) * | 2013-01-25 | 2013-05-15 | 大唐移动通信设备有限公司 | Ip Multimedia Subsystem (IMS) equipment and data processing method thereof |
| CN103874041A (en) * | 2012-12-17 | 2014-06-18 | 中国移动通信集团设计院有限公司 | Multimode dual-standby terminal-based called voice service processing method, device and system |
| CN105376768A (en) * | 2014-08-19 | 2016-03-02 | 中国电信股份有限公司 | Pool disaster recovery method and system for mobility management entity |
| CN105556900A (en) * | 2015-01-30 | 2016-05-04 | 华为技术有限公司 | Business disaster tolerance method and related device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10225178B2 (en) * | 2010-09-15 | 2019-03-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatus for relocating and restoring connections through a failed serving gateway and traffic offloading |
| KR101541987B1 (en) * | 2011-03-18 | 2015-08-04 | 알까뗄 루슨트 | System and method for failover recovery at geo-redundant gateways |
-
2017
- 2017-03-29 CN CN201710198812.5A patent/CN108668307B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101646270A (en) * | 2008-08-06 | 2010-02-10 | 华为技术有限公司 | Method, system, mobility management entity and memory device for maintaining service continuity |
| CN101730124A (en) * | 2008-10-29 | 2010-06-09 | 华为技术有限公司 | Method, device and system for resuming service |
| CN103874041A (en) * | 2012-12-17 | 2014-06-18 | 中国移动通信集团设计院有限公司 | Multimode dual-standby terminal-based called voice service processing method, device and system |
| CN103108416A (en) * | 2013-01-25 | 2013-05-15 | 大唐移动通信设备有限公司 | Ip Multimedia Subsystem (IMS) equipment and data processing method thereof |
| CN105376768A (en) * | 2014-08-19 | 2016-03-02 | 中国电信股份有限公司 | Pool disaster recovery method and system for mobility management entity |
| CN105556900A (en) * | 2015-01-30 | 2016-05-04 | 华为技术有限公司 | Business disaster tolerance method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108668307A (en) | 2018-10-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9143990B2 (en) | Method and device for handling failure of mobility management device in ISR activated scenario | |
| EP3860189B1 (en) | Ue migration method, apparatus, system, and storage medium | |
| CN110535676B (en) | SMF dynamic disaster tolerance realization method, device, equipment and storage medium | |
| KR101467138B1 (en) | System and method for session resiliancy at geo-redundant gateways | |
| CN109818766B (en) | Communication method, network function entity, network function storage and computer readable storage medium | |
| US20230105343A1 (en) | NF SERVICE CONSUMER RESTART DETECTION USING DIRECT SIGNALING BETWEEN NFs | |
| US10405206B2 (en) | Service redundancy method and related apparatus | |
| US20120094656A1 (en) | Mobile communication method, device, and system for ensuring service continuity | |
| KR101896234B1 (en) | Restoration of mobile terminating cs services in case of failure of a ps core network entity in a mobile communication system | |
| EP2807854B1 (en) | Mme restoration | |
| KR20130061738A (en) | Paging processing method system and serving gateway | |
| US10405213B2 (en) | Called service processing method, mobility management entity, and home subscriber server | |
| CN112218283B (en) | Service suspension and recovery method and system, multi-card terminal and storage medium | |
| US9749988B2 (en) | Called recovery method, apparatus, and system | |
| US20160286597A1 (en) | Re-Establishment of a Failed Communication Session | |
| CN105376768A (en) | Pool disaster recovery method and system for mobility management entity | |
| EP3300418A1 (en) | Method and system for recovering communication state after sgw failure, and mme and sgw | |
| CN108668307B (en) | Called service recovery processing method, mobility management entity and service gateway | |
| CN107318121B (en) | Data backup method for LTE EPC system | |
| CN114007238A (en) | Method and device for service recovery after local point failure | |
| CN115349119A (en) | Method and apparatus for enhanced 5GC recovery when deploying a Network Function (NF) set in a network | |
| JP2017034610A (en) | Call processing device, session recovery method and call processing server program | |
| CN112996143B (en) | Processing method and device for recovering network connection and network side equipment | |
| CN109561019B (en) | Method for establishing session, graceful restart communication device and storage medium | |
| CN108966291B (en) | Method and device for recovering circuit switched fallback, mobile management entity and user terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |