WO2017097030A1

WO2017097030A1 - Service recovery management method, mobility management network element, serving gateway, and system

Info

Publication number: WO2017097030A1
Application number: PCT/CN2016/101820
Authority: WO
Inventors: 汪钱纯; 詹徐周
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-12-07
Filing date: 2016-10-11
Publication date: 2017-06-15
Also published as: CN106851700A

Abstract

A service recovery management method, a mobility management network element, a serving gateway, and a communication system. After a mobility management network element sets a periodical regional update timed duration for a user, the mobility management network element sends, to a serving gateway, the periodical regional update timed duration set for the user; and when a fault occurs on the mobility management network element, the serving gateway can set a retention duration of the user according to the periodical regional update timed duration reported the mobility management network element, and starts timing.

Description

Service recovery management method, mobility management network element, service gateway and system

Technical field

The present disclosure relates to the field of communications, for example, to a service recovery management method, a mobility management network element, a service gateway, and a communication system.

Background technique

The 3GPP (3rd Generation Partnership Project) next-generation mobile wireless network project is called System Architecture Evolution (SAE). The architecture of the SAE is shown in Figure 1. It includes the following network elements:

eNB (Evolved Node B): A base station, which is a network element in an Evolved RAN (E-RAN), and provides radio resources for access of the terminal. The evolved radio access network can provide higher uplink and downlink rates, lower transmission delays, and more reliable wireless transmission.

HSS (Home Subscriber Server): A home subscriber server that permanently stores user subscription data.

MME (Mobility Management Entity) mobile management entity, control plane function entity, server for temporarily storing user data, responsible for managing and storing user equipment (User Equipment, UE) context (such as UE user ID, mobility management status, user security parameters) And so on, assigning a temporary identifier to the user, when the UE is camped on the tracking area or the network is responsible for authenticating the user; processing all non-access stratum messages between the MME and the UE; triggering paging at the SAE.

SGSN (Serving GPRS Support Node): Serving GPRS support node, GPRS (General Packet Radio Service) supporting Gb or Iu access, server for temporarily storing user data, responsible for managing and storing GMM (GPRS mobility management) Mobility Management) Context and PDP (Packet Data Protocol) context; processing all non-access stratum messages between the SGSN and the UE;

SGW (Serving Gateway): A service gateway. The gateway is a user plane entity responsible for user plane data routing processing and terminating downlink data of UEs in idle state. Manage and store the SAE bearer context of the UE, such as IP (Internet Protocol) bearer service parameters and network internal routing information. Is the anchor point of the internal user plane of the 3GPP system, a user can only have one SGW at a time;

PDN GW (Packet Data Network Gateway): A packet data network gateway, responsible for the UE accessing the PDN gateway, assigning a user IP address, and being a mobility anchor for 3GPP and non-3GPP access systems. Users can access multiple PDN GWs at the same time.

Policy and Charging Rule Functionality (PCRF): A functional entity that generates QoS (Quality of Service) rules for controlling user data transmission based on service information, user subscription information, and operator configuration information. And billing rules. The functional entity can also control the establishment and release of bearers in the access network.

IMS (IP Multimedia Subsystem) is an IP Multimedia Subsystem.

The user is attached to the packet domain evolution network. After the SGW detects the MME restart, the SGW does not immediately delete the MME-related user. Instead, the SGW does not immediately delete the MME-related user. Instead, the SGW starts a timer to control the maximum duration of the user reservation. This timer is per. The SGW (per SGW) configuration may be performed by using a periodic TAU timer (Tracking Area Update Timer). Before the timer expires, the downlink service (including data or signaling) is received, and the SGW may select the MME to search for the MME. Call the user to resume the service, the timer expires, and the SGW deletes the user.

After the 3GPP standard introduces the MTC (Machine Type Communications) Internet of Things, in order to reduce the network load caused by frequent periodic TAUs, it is necessary to support a longer periodic TAUTimer, thereby increasing the per user (per user). The periodic TAU timer, the user can actively request the corresponding periodic area update timing duration, the HSS can also sign the periodic area update timing duration, and the MME allocates the periodic area to the user according to the periodic area update timing duration that the user requests and the HSS contract. Update the timing duration. This periodic area update timing is per user, that is, different users may be different.

However, due to the introduction of the cyclical area update timing duration of the user level, the service recovery function triggered by the network side is still inappropriate for the SGW to use the periodic area update timing of the per SGW configuration, because there is no distinction between the per user settings. The timer of the user's maximum duration is reserved, and the fixed per SGW periodic area is used to update the time duration. It is easy to cause the user context to be deleted prematurely, which is not conducive to user service recovery, or too late to waste SGW resources.

Summary of the invention

The present disclosure provides a service recovery management method, a mobility management network element, a service gateway, and a communication system, which solves the problem that the service gateway is likely to delete users too early or too late in the related art.

The disclosure provides a service recovery management method, including:

The mobility management network element sets a periodic area update timing duration for the user;

The mobility management network element sends the periodic area update timing duration to the serving gateway, so that the serving gateway determines the retention duration of the user according to the periodic area update timing duration. Optional The mobility management network element sets the periodic area update timing duration for the user to include:

Obtaining, by the mobility management network element, at least one of a periodic area update timing duration requested by the user and a periodic area update timing duration that the home user server subscribes to the user;

The mobility management network element sets the periodic area update timing duration of the user according to the acquired periodic area update timing duration. Optionally, the mobility management network element sets a periodic area update timing duration for the user, including:

The mobility management network element acquires a periodic area update timing duration that the home user server sent by the old mobility management network element subscribes to the user, and a periodic area update timing duration that is set for the user before the old mobility management network element And at least one of a periodic area update timing duration requested by the user;

The mobility management network element sets the periodic area update timing duration of the user according to the acquired periodic area update timing duration.

Optionally, the sending, by the mobility management network element, the periodic area update timing duration to the serving gateway includes:

The mobility management network element adds the periodic area update timing duration to the create session request or modify the bearer request;

The mobility management network element sends the create session request or the modify bearer request to the serving gateway.

Optionally, the mobility management network element is a mobility management entity, and the periodic area update timing duration is a periodic tracking area update timing duration;

Or, the mobility management network element is a serving GPRS support node, and the periodic area update timing duration is a periodic routing area update timing duration.

The present disclosure also provides a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the above described service recovery management method.

The disclosure also provides a service recovery management method, including:

The serving gateway receives the mobility management network element to set a periodic area update timing duration for the user;

When the mobility management network element fails, the serving gateway sets the retention duration of the user according to the periodic area update timing duration, and starts timing.

Optionally, the method further includes: deleting, by the serving gateway, the user when the time duration reaches the retention duration.

Optionally, the serving gateway sets the user according to the periodic area update timing duration. The retention duration includes: the serving gateway sets the retention duration of the user to be equal to the periodic region update timing duration.

Optionally, the mobility management network element fault includes at least one of a mobility management network element restart and a disconnection.

The disclosure also provides a mobility management network element, including a setting module and a sending module;

The setting module is configured to set a periodic area update timing duration for the user;

The sending module is configured to send the periodic area update timing duration to the serving gateway, so that the serving gateway determines the retention duration of the user according to the periodic area update timing duration.

Optionally, the setting module includes a first acquiring submodule and a first setting submodule;

The first obtaining sub-module is configured to acquire at least one of a periodic area update timing duration requested by the user and a periodic area update timing duration that the home user server subscribes to the user;

The first setting sub-module is configured to set a periodic area update timing duration of the user according to each periodic area update timing duration acquired by the first acquisition sub-module; optionally, the setting module includes a second acquisition sub- Module and second setting submodule;

The second obtaining sub-module is configured to obtain a periodic area update time duration that the home user server sends the old mobility management network element to subscribe to, and a periodic area update that is set for the user before the old mobility management network element At least one of a timing duration and a periodic region update timing duration requested by the user;

The second setting sub-module is configured to set a periodic area update timing duration of the user according to each periodic area update timing duration acquired by the second acquisition sub-module.

The present disclosure also provides a service gateway, including: a receiving module and a processing module;

The receiving module is configured to receive a mobility management network element to set a periodic area update timing duration for the user;

The processing module is configured to set a retention duration of the user according to the periodic region update timing duration when the mobility management network element fails, and start timing.

The present disclosure also provides a communication system including a service gateway and a mobility management network element;

The mobility management network element is configured to set a periodic area update timing duration for the user, and send the periodic area update timing duration to the serving gateway;

The service gateway is configured to receive, by the mobility management network element, a periodic area update timing duration for the user, and when the mobility management network element fails, set the retention duration of the user according to the periodic area update timing duration, And start timing.

The service recovery management method, the mobility management network element, the service gateway, and the communication system provided by the disclosure, after the mobility management network element sets the periodic area update timing duration for the user, the periodic area update time period set for the user is sent. When the mobility management network element is faulty, the service gateway can set the retention duration of the user according to the periodic update time of the user reported by the mobility management network element and start timing. That is, the serving gateway of the present disclosure can obtain the periodic area update timing duration of different users from the mobility management network element, and according to different user periodic area update timing durations when the mobility management network element fails (for example, disconnection or restart) Set the retention time of the user, so you can avoid deleting the user context prematurely and ensure the recovery of user services. At the same time, you can avoid deleting the user context too late and improve the service gateway resource utilization.

BRIEF abstract

1 is a schematic diagram of an evolution structure of a system architecture;

2 is a schematic flowchart of a service recovery management method according to Embodiment 1 of the present disclosure;

3 is a schematic structural diagram of a communication system according to Embodiment 2 of the present disclosure;

4 is a schematic structural diagram of a mobility management network element according to Embodiment 2 of the present disclosure;

Figure 5 is a schematic structural view 1 of the module of Figure 4;

Figure 6 is a schematic structural view 2 of the setting module of Figure 4;

FIG. 7 is a schematic structural diagram of a service gateway according to Embodiment 2 of the present disclosure;

FIG. 8 is a schematic flowchart of a service recovery management method according to Embodiment 3 of the present disclosure;

FIG. 9 is a schematic flowchart of another service recovery management method according to Embodiment 3 of the present disclosure;

10 is a schematic flowchart of a method for managing a user attachment process according to Embodiment 3 of the present disclosure;

FIG. 11 is a schematic flowchart of a user activation process management method according to Embodiment 3 of the present disclosure;

FIG. 12 is a schematic flowchart of a method for managing a service update area update process according to Embodiment 3 of the present disclosure, where the mobility management entity and the serving GPRS support node are unchanged;

13 is a mobility management entity or a serving GPRS support node change according to Embodiment 3 of the present disclosure, The service gateway does not change the flow chart of the regional update process management method;

14 is a schematic flowchart of a method for managing a mobility management entity or a service GPRS support node according to Embodiment 3 of the present disclosure, and a service gateway changing region update process;

15 is a schematic flowchart of a management method of a handover process and the like according to Embodiment 3 of the present disclosure;

16 is a schematic flowchart of a path switching process management method according to Embodiment 3 of the present disclosure;

17 is a structural block diagram of an electronic device according to Embodiment 4 of the present disclosure;

FIG. 18 is a structural block diagram of an electronic device according to Embodiment 5 of the present disclosure.

detailed description

The service gateway of the present disclosure may obtain the periodic area update timing duration of different users from the mobility management network element, and set the retention time of each user according to the periodicity of each user periodic area update timing when the mobility management network element fails. The user context can be deleted prematurely to ensure the recovery of user services. At the same time, the user context can be deleted too late, and the utilization of the service gateway resources can be improved. The present disclosure is described in detail below with reference to the accompanying drawings in the accompanying drawings. The features in the following embodiments and examples may be arbitrarily combined with each other without conflict.

Embodiment 1:

Referring to FIG. 2, the service recovery management method provided in this embodiment includes:

Step 210: The mobility management network element sets a periodic time interval for the periodic update of the user.

Step 220: The mobility management network element sends the periodic area update timing set for the user to the serving gateway.

Step 230: The serving gateway receives a periodic area update timing duration set by the mobility management network element for the user.

Step 240: When the mobility management network element fails, the serving gateway sets the retention duration of the user according to the periodic area update timing, and starts timing. In this embodiment, the mobility management network element failure includes, but is not limited to, at least one of mobility management network element restart and disconnection. When the service gateway detects that the time duration has reached the retention time, the user is deleted, that is, the user context is deleted, and the resource utilization is improved.

In the foregoing step 210, the mobility management network element may set the periodic area update timing duration for the user to include the following conditions.

For the process that is not the inter-office mobility process, that is, when the mobility management network element is not involved, for example, the user attaches to the mobility management network element process, the user attaches to the mobility management network element and activates the process. Tracking area update or routing area update process, and path switching process when changing. At this time, the mobility management network element acquires at least one of the periodic area update timing duration requested by the user and the periodic area update timing duration that the home user server subscribes to the user, and then updates the timing duration according to the acquired periodic request area of the user request. The home subscriber server sets the periodic area update timing duration of the user for at least one of the periodic area update timing durations subscribed by the user. Optionally, when the periodic area update timing duration requested by the user and the periodic area update timing duration that the home user server subscribes to the user are acquired at the same time, one of the periodic area updates may be selected as the user according to the current actual selection policy. The time duration of the periodic region update timer is only obtained when the periodic region update timing of the user request or the periodic region update time period for the home subscriber server is subscribed to, and the obtained periodic region update timing duration is directly used as the period of the user. The duration of the sexual area update.

For the inter-office mobility process, that is, when the mobility management network element changes, for example, the mobility management network element changes the service gateway when the service gateway changes or does not change, the tracking area update process or the routing area update process, the handover process, and the like. At this time, the mobility management network element in step 210 is a new mobility management network element, and the new mobility management network element acquires the periodic area update time duration that the home user server sent by the old mobility management network element subscribes to the user, The old mobility management network element is at least one of a periodic area update timing duration set by the user and a periodic area update timing duration requested by the user; and then setting the user time according to the acquired different periodic area update timing duration Periodic area update timing duration. It may be that one of the plurality of periodic region update timing durations acquired is selected as the user's periodic region update timing duration. The selection strategy here can also be flexibly selected according to the current network requirements, and will not be described here.

In the foregoing step 220, the mobility management network element sends the periodic area update timing duration to the service gateway, including:

The mobility management network element adds the periodic area update timing to the create session request or modify the bearer request, and then sends a create session request or modify the bearer request to the serving gateway. That is to say, it can be sent to the service gateway by creating a session request or modifying a bearer request. It can be understood that the embodiment is not limited to the use of the above two types of request transmission, and may also be completed by using any other interactive message between the mobility management network and the serving gateway, or directly by using a new message.

The mobility management network element in this embodiment may be a mobility management entity or a serving GPRS support node. When it is a mobility management entity, the periodicity of the periodic area update time set by the mobility management entity for the user is the periodic tracking area update timing duration. Corresponding TAU Timer (Tracking Area Update Timer) can be used. When the mobility management network element is serving the GPRS support node, the service The periodic area update timing set by the GPRS support node user is the periodic routing area update timing duration, and the RAU Timer (Routing Area Update Timer) can be used.

In the foregoing step 240, the serving gateway sets the retention duration of the user according to the periodic area update timing duration reported by the mobility management network element, and the serving gateway sets the retention duration of the user to be equal to the periodic area update timing duration. In this way, when the duration of the timer reaches the periodic update period (that is, the retention duration) of the user, the serving gateway can immediately delete the user, and the deletion time is consistent with the periodic update timing of the user, not early. Late, it is beneficial to the recovery of services such as MTC disaster recovery and improve the satisfaction of user experience; it can also avoid the waste of service gateway resources and improve resource utilization.

The embodiment further provides a non-transitory computer readable storage medium storing computer executable instructions, the computer executable instructions being configured to perform the foregoing service recovery management method.

Embodiment 2:

Referring to FIG. 3, this embodiment provides a communication system, including a mobility management network element 1 and a service gateway 2;

The mobility management network element 1 is configured to set a periodic area update timing duration for the user, and send the periodic area update timing duration to the serving gateway;

The service gateway 2 is configured to receive the retention mobility management network element 1 to set a periodic area update timing duration for the user, and when the mobility management network element 1 fails, set the retention duration of the user according to the saved periodic area update timing duration, and Start timing.

The mobility management network element 1 in this embodiment may be a mobility management entity, and the periodic area update timing duration set by the user is the periodic tracking area update timing duration; correspondingly, the TAU Timer may be used;

The mobility management network element 1 in this embodiment may also be a serving GPRS support node. In this case, the periodic area update timing duration set by the user is the periodic routing area update timing duration; correspondingly, the RAU Timer may be used.

Optionally, as shown in FIG. 4, a mobility management network element 1 in this embodiment includes:

Setting module 11 is set to set a periodic area update timing duration for the user;

The sending module 12 is configured to send the periodic area update timing duration to the serving gateway, so that the serving gateway determines the retention duration of the user according to the periodic area update timing duration.

Referring to FIG. 5, the setting module 11 in this embodiment includes a first obtaining submodule 111 and a a setting sub-module 112; the setting module 11 is configured to set the periodic area update timing duration of the user when not in the inter-office mobility process, that is, when the mobility management network element is not involved; for example, the user attaches to the mobility management The network element process, the user attaches to the activation process after the mobility management network element, and the service gateway changes the tracking area update process or the routing area update process, the path switching process, etc.; optional:

The first obtaining sub-module 111 is configured to acquire at least one of a periodic area update timing duration requested by the user and a periodic area update timing duration that the home subscriber server subscribes to the user;

The first setting sub-module 112 is configured to set the periodicity of the periodic area update timing of the user according to the multiple periodic area update timing durations acquired by the first obtaining sub-module 111; optionally, when the periodicity of the user request is simultaneously acquired When the time length of the area update and the time period of the periodic area update for the user to be subscribed by the user are selected, one of the periodic area update timings may be selected as the user according to the current actual selection policy; and only the periodic area requested by the user is obtained. When the update timing duration or the periodic user area of the home subscriber server is updated, the obtained periodic area update timing duration may be directly used as the periodic area update timing duration of the user.

Referring to FIG. 6, the setting module 11 in this embodiment includes a second obtaining submodule 113 and a second setting submodule 114. The setting module 11 is configured to be in an interoffice mobility process, that is, a mobility management network. When the meta changes, the periodic area update timing of the user is set. For example, the tracking area update process or the routing area update process, the handover process, and the like when the mobility management network element change service gateway changes or does not change. Optional:

The second obtaining sub-module 113 is configured to set a periodic area update timing duration that the home user server sends for the old mobility management network element, and a periodic area update timing duration that the old mobility management network element sets for the user. And at least one of a periodic area update timing duration requested by the user;

The second setting sub-module 114 is configured to set the periodic area update timing duration of the user according to the plurality of periodic area update timing durations acquired by the second acquisition sub-module 113. Optionally, one of the plurality of periodic area update timing durations acquired from the second acquisition sub-module 113 is selected as the periodic area update timing duration of the user. The selection strategy here can also be flexibly selected according to the current network requirements, and will not be described here.

The sending module 2 in this embodiment may be sent to the serving gateway by creating a session request or modifying a bearer request. It can be understood that the embodiment is not limited to the use of the above two types of request transmission, and the sending module 2 may further complete the sending by using any other interactive message between the mobility management network and the serving gateway, or directly send the new message.

Referring to FIG. 7, the serving gateway 2 in this embodiment includes:

The receiving module 21 is configured to receive the storage mobility management network element to set a periodic area update timing duration for the user;

The processing module 22 is configured to set the retention time of the user according to the periodic area update timing duration received by the receiving module 21 when the mobility management network element fails, and start timing. The processing module 22 sets the retention time of the user to be equal to the duration of the periodic area update timing. In this way, when the duration of the timer reaches the periodic update period (that is, the retention duration) of the user, the serving gateway can immediately delete the user, and the deletion time is consistent with the periodic update timing of the user, not early. Late, it is beneficial to the recovery of services such as MTC disaster recovery and improve the satisfaction of user experience; it can also avoid the waste of service gateway resources and improve resource utilization.

It will be apparent to those skilled in the art that the various modules or steps of the above disclosure may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored by a computing device in a storage medium (ROM/RAM, diskette, optical disk) and, in some cases, The steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into a plurality of integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Embodiment 3:

For a better understanding of the present disclosure, the present embodiment exemplifies the present disclosure by taking a mobility management network element as a mobility management entity or a serving GPRS support node as an example.

When the mobility management network element is a mobility management entity, the periodicity of the periodic area update time set by the mobility management entity for the user is the periodic tracking area update timing duration. In this embodiment, the periodic TAU Timer (Tracking Area Update Timer) is used. Area update timer) is indicated. The management process at this time is shown in Figure 8, including:

Step 801: The mobility management entity sets a periodic TAU Timer for the user and sends it to the serving gateway.

If it is not the inter-office mobility procedure, the mobility management entity allocates a periodic TAU Timer of the per user to the user, saves the periodic TAU Timer, and notifies the periodic TAU Timer to the serving gateway;

In the case of an interoffice mobility procedure, the old mobility management entity or the serving GPRS support node sends the periodic TAU Timer subscribed by the user and the periodic TAU Timer of the per user assigned by the old mobility management entity or the serving GPRS support node to the new mobility management entity. The new mobility management entity allocates a periodic TAU Timer of the per user to the user, saves the periodic TAU Timer, and notifies the serving gateway of the periodic TAU Timer;

Step 802: The service gateway records the periodic TAU Timer of the user.

Step 803: The serving gateway detects that the mobility management entity restarts or disconnects, and starts the reserved user retention timer according to the saved user's periodic TAU Timer.

When the mobility management network element is a serving GPRS support node, the time period of the periodic area update time set by the mobility management entity for the user is the routing area update timing duration. This embodiment is represented by a periodic RAU Timer. The management process at this time is shown in Figure 9, including:

Step 901: The serving GPRS support node sets a periodic RAU Timer for the user and sends it to the serving gateway.

If it is not the inter-office mobility procedure, the serving GPRS support node allocates a periodic RAU Timer of the per user to the user, saves the periodic RAU Timer, and notifies the serving gateway of the periodic RAU Timer;

In the case of an interoffice mobility procedure, the old mobility management entity or the serving GPRS support node sends the periodic RAU Timer subscribed by the user and the periodic RAU Timer of the per user assigned by the old mobility management entity or the serving GPRS support node to the new service GPRS support. node. The new serving GPRS support node allocates a periodic RAU Timer of the per user to the user, saves the periodic RAU Timer, and notifies the serving gateway of the periodic RAU Timer;

Step 902: The serving gateway records the periodic RAU Timer of the user.

Step 903: The serving gateway detects that the mobility management entity restarts or disconnects, and starts the reserved user duration timer according to the saved user's periodic RAU Timer.

The following description of the disclosure is made by taking several optional application scenarios as an example.

As shown in FIG. 10, it is a management process in which a user attaches to a mobility management entity, including:

Step 1001: The user initiates an attach message to the network.

Step 1002: If the mobility management entity allocates a Per User periodic TAU Timer to the user, save it;

Step 1003: The mobility management entity sends a create session request message to the service gateway, where the message includes a periodic TAU Timer of the Per user;

Step 1004: The service gateway records a periodic TAU Timer of the Per user;

Step 1005: The serving gateway sends a create session request message to the packet data gateway.

Step 1006: The packet data gateway sends a create session response message to the serving gateway.

Step 1007: The serving gateway sends a create session response message to the mobility management entity.

Step 1008: Perform other process processing of attaching;

Step 1009: The serving gateway detects that the mobility management entity restarts or the link is interrupted.

Step 1010: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic TAU Timer of the Per user sent by the mobility management entity.

As shown in FIG. 11, it is a management process in which a user attaches to a serving GPRS support node and subsequently initiates an activation process, including:

Step 1101: The user initiates an attach message to the network.

Step 1102: If the serving GPRS support node allocates a periodic RAU Timer of the Per user to the user, save it;

Step 1103: Perform other process processing of attaching;

Step 1104: The user initiates an activation request message to the network.

Step 1105: The serving GPRS support node sends a create session request message to the serving gateway, where the message includes a periodic RAU Timer of Per user;

Step 1106: The service gateway records the periodic RAU Timer of the Peruser;

Step 1107: The serving gateway sends a create session request message to the packet data gateway.

Step 1108: The packet data gateway sends a create session response message to the serving gateway.

Step 1109: The serving gateway sends a create session response message to the serving GPRS support node.

Step 1110: Perform other process processing of activation;

Step 1111: The serving gateway detects that the serving GPRS support node is restarted or the link is interrupted.

Step 1112: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic RAU Timer of the Per user carried by the SGSN.

As shown in FIG. 12, it is a management process in which the mobility management entity/service GPRS support node does not change, the tracking area update of the service gateway changes, or the routing area update process, including:

Step 1201: The user initiates a tracking area update or routing area update message to the network;

Step 1202: If the mobility management entity/serving GPRS support node allocates a Per User periodic TAU/RAU Timer to the user, save it;

Step 1203: The mobility management entity/serving GPRS support node sends a create session request message to the serving gateway, where the message includes a periodic TAU/RAU Timer of Per user;

Step 1204: The serving gateway records a periodic TAU/RAU Timer of the Per user;

Step 1205: The serving gateway sends a modify bearer request message to the packet data gateway.

Step 1206: The packet data gateway sends a modify bearer response message to the serving gateway.

Step 1207: The serving gateway sends a create session ring to the mobility management entity/serving GPRS support node. Message

Step 1208: Perform other process processing of tracking area update or routing area update;

Step 1209: The serving gateway detects that the mobility management entity/serving GPRS support node is restarted or the link is interrupted.

Step 1210: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic TAU/RAU Timer of the Per user carried by the MME/SGSN.

As shown in FIG. 13, the management process of the tracking area update or the routing area update process in which the mobility management entity/service GPRS support node changes, the service gateway does not change, includes:

Step 1301: The user initiates a tracking area update or routing area update message to the network;

Step 1302: A Context Request procedure, in which the old mobility management entity/serving GPRS support node carries the periodic TAU/RAU Timer of its previously saved user subscription to the new mobility management entity/serving GPRS support node and its assigned per User's periodic TAU Timer;

Step 1303: If the mobility management entity/serving GPRS support node allocates a Per User periodic TAU/RAU Timer to the user, save it;

Step 1304: The mobility management entity/serving GPRS support node sends a modify bearer request message to the serving gateway, where the message includes a periodic TAU/RAU Timer of Per user;

Step 1305: The serving gateway records a periodic TAU/RAU Timer of the Per user;

Step 1306: The serving gateway sends a modify bearer request message to the packet data gateway.

Step 1307: The packet data gateway sends a modify bearer response message to the serving gateway.

Step 1308: The serving gateway sends a modify bearer response message to the mobility management entity/serving GPRS support node.

Step 1309: Perform other process processing of tracking area update or routing area update;

Step 1310: The serving gateway detects that the mobility management entity/serving GPRS support node is restarted or the link is interrupted.

Step 1311: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic TAU/RAU Timer of the Per user carried by the MME/SGSN.

As shown in FIG. 14, it is a management process of a mobility management entity/service GPRS support node change, a tracking area update of a service gateway change, or a routing area update process, including:

Step 1401: The user initiates a tracking area update or routing area update message to the network;

Step 1402: Context Request process, in which the old MME/SGSN carries the periodic TAU/RAU Timer signed by the previously saved user and the periodic TAU Timer of the allocated per user to the new MME/SGSN;

Step 1403: If the mobility management entity/serving GPRS support node allocates a Per User periodic TAU/RAU Timer to the user, save it;

Step 1404: The mobility management entity/service GPRS support node sends a create session request message to the service gateway, where the message includes a periodic TAU/RAU Timer of Per user;

Step 1405: The serving gateway records a periodic TAU/RAU Timer of the Per user;

Step 1406: The serving gateway sends a modify bearer request message to the packet data gateway.

Step 1407: The packet data gateway sends a modify bearer response message to the serving gateway.

Step 1408: The serving gateway sends a create session response message to the mobility management entity/serving GPRS support node.

Step 1409: Perform other process processing of tracking area update or routing area update;

Step 1410: The serving gateway detects that the mobility management entity/serving GPRS support node is restarted or the link is interrupted.

Step 1411: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic TAU/RAU Timer of the Per user carried by the MME/SGSN.

As shown in Figure 15, it is the management process of the handover process, including:

Step 1501: The radio access network element sends a handover request message.

Step 1502: Forward Forwarding Request (Forward Relocation Request) process, in which the old MME/SGSN carries the periodic TAU/RAU Timer signed by the previously saved user and the periodic TAU Timer of the allocated per user to the new MME/SGSN;

Step 1503: If the mobility management entity/serving GPRS support node allocates a periodic TAU/RAU Timer of the Per user to the user, save it;

Step 1504: Perform other process processing of the handover;

Step 1505: The mobility management entity/serving GPRS support node sends a modify bearer request message to the serving gateway, where the message includes a periodic TAU/RAU Timer of Per user;

Step 1506: The serving gateway records a periodic TAU/RAU Timer of the Per user;

Step 1507: The serving gateway sends a modify bearer request message to the packet data gateway.

Step 1508: The packet data gateway sends a modify bearer response message to the serving gateway.

Step 1509: The serving gateway sends a modify bearer response message to the mobility management entity/serving GPRS support node.

Step 1510: Perform other processing of the handover;

Step 1511: The serving gateway detects that the mobility management entity/serving GPRS support node is restarted or the link is interrupted.

Step 1512: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic TAU/RAU Timer of the Per user carried by the MME/SGSN.

As shown in Figure 16, it is the management process in the path switching process, including:

Step 1601: The radio access network element sends a path switch request message.

Step 1602: If the mobility management entity/serving GPRS support node allocates a Per User periodic TAU/RAU Timer to the user;

Step 1603: The mobility management entity/service GPRS support node sends a create request message to the service gateway, where the message includes a periodic TAU/RAU Timer of Peruser;

Step 1604: The serving gateway records a periodic TAU/RAU Timer of the Per user;

Step 1605: The serving gateway sends a modify bearer request message to the packet data gateway.

Step 1606: The packet data gateway sends a modify bearer response message to the serving gateway.

Step 1607: The serving gateway sends a create session response message to the mobility management entity/serving GPRS support node.

Step 1608: Perform other process processing of path switching.

Step 1609: The serving gateway detects that the mobility management entity/serving GPRS support node is restarted or the link is interrupted.

Step 1610: The serving gateway starts a timer for retaining the maximum duration of the user according to the periodic TAU/RAU Timer of the Per user carried by the MME/SGSN.

Embodiment 4:

FIG. 17 is a structural block diagram of an electronic device according to Embodiment 4 of the present disclosure. The electronic device provided by the embodiment of the present disclosure is configured on the mobility management network element side, and the electronic device may include a processor 1701 and a memory 1703, and may further include a communication interface 1702 and a bus 1704. The processor 1701, the communication interface 1702, and the memory 1703 can complete communication with each other through the bus 1704. Communication interface 1702 can be used for information transfer. The processor 1701 can call the logic instructions in the memory 1703 to perform the service recovery of the above embodiment. Management method.

Furthermore, the logic instructions in the memory 1703 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in various embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

Embodiment 5:

FIG. 18 is a structural block diagram of an electronic device according to Embodiment 5 of the present disclosure. The electronic device provided by the embodiment of the present disclosure is configured on the service gateway side, and the electronic device may include a processor 1801 and a memory 1803, and may further include a communication interface 1802 and a bus 1804. The processor 1801, the communication interface 1802, and the memory 1803 can complete communication with each other through the bus 1804. Communication interface 1802 can be used for information transfer. The processor 1801 can call the logic instructions in the memory 1803 to perform the service recovery management method of the above embodiment.

In addition, the logic instructions in the memory 1803 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in various embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

In the above embodiment, "/" means "or". The above is a detailed description of the present disclosure in conjunction with the optional embodiments, and it is not considered that the alternative embodiments of the present disclosure are limited to the description.

Industrial applicability

The service gateway of the present disclosure can acquire the periodic area of different users from the mobility management network element. The new timing duration, when the mobility management network element is faulty (for example, disconnected or restarted), the user's retention duration is set according to the periodic update time of different users. Therefore, the user context can be deleted prematurely to ensure the recovery of the user service. At the same time, it can avoid deleting the user context too late and improve the service gateway resource utilization.

Claims

A business recovery management method includes:

The mobility management network element sets a periodic area update timing duration for the user;

The mobility management network element sends the periodic area update timing duration to the serving gateway, so that the serving gateway determines the retention duration of the user according to the periodic area update timing duration.
The service recovery management method according to claim 1, wherein the mobility management network element sets the periodic area update timing duration for the user to include:

Obtaining, by the mobility management network element, at least one of a periodic area update timing duration requested by the user and a periodic area update timing duration that the home user server subscribes to the user;

The mobility management network element sets a periodicity of the periodic area update timing of the user according to the acquired periodic area update timing duration.
The service recovery management method according to claim 1, wherein the mobility management network element sets the periodic area update timing duration for the user to include:

The mobility management network element acquires a periodic area update timing duration that the home user server sent by the old mobility management network element subscribes to the user, and the periodic area update timing set by the old mobility management network element for the user At least one of a duration, and a periodic region update timing duration requested by the user;

The mobility management network element sets a periodicity of the periodic area update timing of the user according to the acquired periodic area update timing duration.
The service recovery management method according to claim 1, wherein the mobility management network element sends the periodic area update timing duration to the service gateway, including:

The mobility management network element adds the periodic area update timing duration to the create session request or modify the bearer request;

The mobility management network element sends the create session request or the modify bearer request to the serving gateway.
The service recovery management method according to any one of claims 1 to 4, wherein the mobility management network element is a mobility management entity, and the periodic area update timing duration is a periodic tracking area update timing duration;

Or, the mobility management network element is a serving GPRS support node, and the periodic area update timing duration is a periodic routing area update timing duration.
A business recovery management method includes:

The serving gateway receives the mobility management network element to set a periodic area update timing duration for the user;

When the mobility management network element fails, the serving gateway sets the retention duration of the user according to the periodic area update timing duration, and starts timing.
The service recovery management method according to claim 6, further comprising: deleting, by the service gateway, the user when the time duration reaches the retention time.
The service recovery management method according to claim 6 or 7, wherein the setting, by the serving gateway, the retention duration of the user according to the periodic area update timing duration comprises: the service gateway setting the retention duration of the user It is equal to the periodic area update timing duration.
The service recovery management method according to claim 6 or 7, wherein the mobility management network element failure comprises at least one of a mobility management network element restart and a disconnection.
A mobility management network element includes: a setting module and a sending module;

The setting module is configured to set a periodic area update timing duration for the user, and the sending module is configured to send the periodic area update timing duration to the serving gateway, where the serving gateway is configured according to the period The duration of the sexual region update determines the retention duration of the user.
The mobility management network element according to claim 10, wherein the setting module comprises a first obtaining submodule and a first setting submodule;

The first obtaining sub-module is configured to acquire at least one of a periodic area update timing duration requested by the user and a periodic area update timing duration that the home user server subscribes to the user;

The first setting sub-module is configured to set a periodic region update timing duration of the user according to a periodic region update timing duration acquired by the first acquiring sub-module;
The mobility management network element according to claim 10, wherein the setting module comprises a second obtaining submodule and a second setting submodule;

The second obtaining sub-module is configured to acquire a periodic area update timing duration that the home user server sends the old mobility management network element to subscribe to, and the old mobility management network element is a periodic area set by the user. Updating at least one of a timing duration and a periodic region update timing duration requested by the user;

The second setting sub-module is configured to set a periodic area update timing duration of the user according to a periodic area update timing duration acquired by the second acquiring sub-module.
The mobility management network element according to claim 10 or 11, wherein the mobility management network element is a mobility management entity, and the periodic area update timing duration is a periodic tracking area update timing duration;

Or the mobility management network element is a serving GPRS support node, and the periodic area is updated. The duration is the periodic routing area update timing.
A service gateway includes: a receiving module and a processing module;

The receiving module is configured to receive a mobility management network element to set a periodic area update timing duration for the user.

The processing module is configured to set a retention duration of the user according to the periodic region update timing duration when the mobility management network element fails, and start timing.
A communication system including a service gateway and a mobility management network element;

The mobility management network element is configured to set a periodic area update timing duration for the user, and send the periodic area update timing duration to the serving gateway;

The service gateway is configured to receive, by the mobility management network element, a periodic area update timing duration for the user, and when the mobility management network element fails, set the retention duration of the user according to the periodic area update timing duration, And start timing.
A non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of claims 1-4.
A non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of claims 5-8.