CN106686569A - Method, device and system for managing serving gateway (SGW) - Google Patents

Abstract

The present invention provides a service gateway management method, device and system, wherein the method includes: the service gateway SGW-C of the control plane receives the registration message of the service gateway SGW-U of the forwarding plane, wherein the registration message carries The service area information of the SGW-U, and/or, the SGW-C sends an update message for updating the SGW-U to the mobility management unit MME, where the update message carries the identity of the SGW-U and/or The IP address of the SGW-U and the service area information of the SGW-U. The service area information is used to instruct the MME to allocate a tracking area identifier TAI list for the terminal that does not exceed the area served by the SGW-U, which solves how the MME knows the SGW The problem of the service area of -U realizes that the TAI list allocated by the MME to the user will not exceed the service area of the SGW-U.

Description

Service gateway management method, device and system

technical field

The present invention relates to the communication field, in particular to a management method, device and system of a service gateway.

Background technique

Figure 1 is a schematic diagram of the network architecture of 4G EPS in the related art. As shown in Figure 1, the functions of each network element of the evolved packet system (Evolved Packet System, referred to as EPS) are as follows:

UE (UE Equipment): A terminal that accesses the core network through the air interface and 4G base station, and accesses the service network through the Evolved Packet Core (EPC) network. The terminal can be in the idle state and the connected state. When establishing a Radio Resource Connection (RRC) connection with the base station, it enters the connected state, and when the RRC connection is released, it enters the idle state.

eNodeB: 4G base station, providing wireless access for UEs, the main function is to perform radio resource control and scheduling, and provide mobility management within the base station.

Mobility Management Element (MME for short): a network element on the control plane of the core network, which mainly performs authentication and subscription check on the UE. The MME simultaneously selects a Serving Gateway (Serving Gateway, referred to as Serving GW) and a packet domain gateway (Packet Data Network Gateway, referred to as PDN GW) for the user. When the user is in an idle state, the MME can initiate paging of the user to the base station according to the saved user context. The MME also provides mobility management across base stations.

Serving GW: User plane network element, the anchor point when the user moves across base stations, and provides a roaming interface with PDNGW in the case of roaming. When the user is in an idle state, the Serving GW caches user data and triggers the MME to page the user.

PDN GW: user plane network element, which assigns IP (Internet Protocol) addresses to UEs and accesses service networks. When the user moves, the PDN GW is the anchor point of the IP layer and will not change, thereby ensuring service continuity.

In Figure 1, S1-MME, S11, and S5/S8-C are control plane interfaces, based on the GPRS Tunneling Protocol control plane (GPRS Tunneling Protocol-C, referred to as GTP-C), and transmit signaling plane data; S1-U, S5/S8-U is a user plane interface, and transmits user plane data based on the GPRS Tunneling Protocol-U (GTP-U for short).

With the deployment of 4G networks and the popularization of smart terminals, the data traffic carried by the operator's network is increasing rapidly, and the operator is facing pressure to upgrade the network. For the gateway, because the control plane and the forwarding plane are integrated, so It needs to be upgraded together, and the cost is relatively high.

In related technologies, the control plane of the Serving GW is separated from the forwarding plane. Figure 2 is a schematic diagram of the architecture of the separation of the control plane and the forwarding plane of the Serving GW in the related art. As shown in Figure 2, the SGW is divided into the control plane SGW-C and the forwarding plane SGW-U, which interact through a new interface.

The main function of SGW-C is to provide control plane interfaces with MME and PDN GW, and control SGW-U at the same time. One SGW-C is generally deployed in a centralized manner, while the location of SGW-U can be more flexible. One SGW-C can control one or more SGW-Us.

The main function of SGW-U is to provide the user plane interface with the base station and PDN GW, and accept the control of SGW-C. The control of SGW-U by SGW-C mainly includes requesting SGW-U to allocate or release GTP-U tunnel resources of S1-U and S5/S8-U. Each SGW-U has a service area, and base stations in this area can access the SGW-U. Generally, SGW-U reselection occurs when crossing service areas.

After SGW-U and SGW-C are separated, MME needs to ensure that all tracking areas in the TAI list will not exceed the selected SGW-U service when allocating Tracking Area Identity (TAI) list to users. area, so as to ensure that the UE does not need to reselect the SGW-U when moving in all the tracking areas in the TAI list. There is no solution for how the MME knows the service area of the SGW-U. In addition, after the separation of SGW-U and SGW-C, there is still no solution for how SGW-C manages SGW-U.

There is currently no effective solution for how the MME learns the service area of the SGW-U in related technologies.

Contents of the invention

The present invention provides a service gateway management method, device and system to at least solve the problem of how the MME knows the service area of the SGW-U in the related art.

According to one aspect of the present invention, a management method of a service gateway is provided, including:

The serving gateway SGW-C of the control plane receives the registration message of the serving gateway SGW-U of the forwarding plane, wherein the registration message carries the service area information of the SGW-U; and/or,

The SGW-C sends an update message for updating the SGW-U to the mobility management unit MME to which the SGW-U belongs, where the update message carries the identity of the SGW-U and/or the SGW-U The IP address of U and the service area information, where the service area information is used to instruct the MME to allocate a tracking area identifier TAI list for the terminal that does not exceed the area served by the SGW-U.

Further, the registration message also includes at least one of the following:

The identifier of the SGW-U, the capacity weight of the SGW-U, the user type served by the SGW-U, and the service information served by the SGW-U.

Further, the service area information includes:

The tracking area identifier TAI list of the SGW-U.

Further, after the SGW-C sends an update message for updating the SGW-U to the mobility management unit MME to which the SGW-U belongs, it includes:

The SGW-C sends a keep-alive request to the SGW-U;

If the SGW-C receives the keep-alive response from the SGW-U, confirm that the SGW-U is valid;

If the SGW-C does not receive the keep-alive response from the SGW-U, confirm that the SGW-U is invalid, and delete the user data of the SGW-U locally at the SGW-C, and Sending a message for updating the SGW-U to the MME, where the message carries the SGW-U identifier and failure indication.

Further, the method also includes:

The SGW-C receives the de-registration request of the SGW-U;

The SGW-C sends a de-registration response to the SGW-U, and sends a message to update the SGW-U to the MME, where the message carries the SGW-U identifier and failure indication.

Further, after receiving the de-registration request of the SGW-U, the SGW-C includes:

The SGW-C reselects the SGW-U;

If the reselection fails, send the SGW-C failure information to the MME.

Further, the method also includes:

The SGW-C sends a request to the SGW-U to delete the SGW-U, and sends a message to the MME to update the SGW-U, and the message carries the SGW-U identification and invalidation indication .

According to another aspect of the present invention, a management method of a service gateway is also provided, including:

The mobility management unit MME receives an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the identity of the SGW-U IP address and service area information of the SGW-U;

The tracking area identifier TAI list allocated by the MME to the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U.

Further, the method also includes:

The MME receives the message for updating the SGW-U sent by the SGW-C, where the message carries the identity of the SGW-U and the service area information of the SGW-U.

According to another aspect of the present invention, there is also provided a serving gateway management device, which is located in the serving gateway SGW-C on the control plane, including:

The first receiving module is configured to receive a registration message of the serving gateway SGW-U on the forwarding plane, wherein the registration message carries the service area information of the SGW-U; and/or,

A sending module, configured to send an update message for updating the SGW-U to a mobility management unit MME to which the SGW-U belongs, where the update message carries the identity of the SGW-U and/or the SGW-U The IP address of U and the service area information, where the service area information is used to indicate that the TAI list allocated by the MME to the terminal does not exceed the area served by the SGW-U.

Further, the registration message also includes at least one of the following:

The identifier of the SGW-U, the capacity weight of the SGW-U, the user type served by the SGW-U, and the service information served by the SGW-U.

Further, the service area information includes:

The tracking area identifier TAI list of the SGW-U.

Further, the device includes:

A keep-alive module, configured to send a keep-alive request to the SGW-U after sending an update message for updating the SGW-U to the mobility management unit MME to which the SGW-U belongs; and when the SGW-C receives If the keep-alive response from the SGW-U is received, confirm that the SGW-U is valid; if the keep-alive response from the SGW-U is not received, confirm that the SGW-U is invalid, and The SGW-C locally deletes the user data of the SGW-U, and sends a message for updating the SGW-U to the MME, and the message carries the identification of the SGW-U and a failure indication.

Further, the device also includes:

A registration module, configured to receive the de-registration request of the SGW-U; and send a de-registration response to the SGW-U, and send a message for updating the SGW-U to the MME, the message carrying the Identification and failure indication of SGW-U.

Further, the device also includes:

The selecting module is configured to reselect the SGW-U after receiving the de-registration request of the SGW-U; and if the reselection fails, send the SGW-C failure information to the MME.

Further, the device also includes:

A deletion module, configured to send a request to the SGW-U to delete the SGW-U, and send a message to the MME to update the SGW-U, where the message carries the SGW-U identifier and failure indication .

According to another aspect of the present invention, there is also provided a management device for a serving gateway, located in a mobility management unit MME, characterized in that it includes:

The second receiving module is configured to receive an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the SGW-U U's IP address and the service area information;

An allocating module, configured to allocate a TAI list for the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U.

Further, the device also includes:

An updating module, configured to receive a message for updating the SGW-U sent by the SGW-C, wherein the message carries the identifier of the SGW-U and the service area information of the SGW-U.

According to another aspect of the present invention, there is also provided a serving gateway management system, which is characterized in that it includes: the serving gateway SGW-C on the control plane, the serving gateway SGW-U on the forwarding plane, and the mobility management unit MME:

The SGW-C is configured to receive a registration message of the SGW-U, wherein the registration message carries the service area information of the SGW-U; and report to the mobility management unit MME to which the SGW-U belongs sending an update message for updating the SGW-U, where the update message carries the identity of the SGW-U and the service area information;

The MME is configured to allocate a TAI list for the terminal according to the service area information, and the TAI list does not exceed the area served by the SGW-U.

According to the present invention, the serving gateway SGW-C of the control plane is used to receive the registration message of the serving gateway SGW-U of the forwarding plane, wherein the registration message carries the service area information of the SGW-U, and/or, the SGW- C sends an update message for updating the SGW-U to the mobility management unit MME, where the update message carries the identity of the SGW-U and/or the IP address of the SGW-U and the service area information of the SGW-U, The service area information is used to indicate that the tracking area identification TAI list allocated by the MME to the terminal does not exceed the area served by the SGW-U, which solves the problem of how the MME knows the service area of the SGW-U, and realizes that the MME allocates the TAI to the user. The TAI list will not exceed the SGW-U service area.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a schematic diagram of a network architecture of 4G EPS in the related art;

FIG. 2 is a schematic diagram of an architecture in which the control plane and the forwarding plane of the Serving GW are separated in the related art;

Fig. 3 is a flow chart 1 of a management method of a service gateway according to an embodiment of the present invention;

FIG. 4 is a second flowchart of a management method of a service gateway according to an embodiment of the present invention;

FIG. 5 is a structural block diagram 1 of a management device of a service gateway according to an embodiment of the present invention;

Fig. 6 is a structural block diagram 2 of a management device of a service gateway according to an embodiment of the present invention;

FIG. 7 is a third structural block diagram of a management device of a service gateway according to an embodiment of the present invention;

FIG. 8 is a fourth structural block diagram of a management device of a service gateway according to an embodiment of the present invention;

FIG. 9 is a structural block diagram five of a management device of a service gateway according to an embodiment of the present invention;

FIG. 10 is a sixth structural diagram of a management device of a service gateway according to an embodiment of the present invention;

Fig. 11 is a structural block diagram VII of a management device of a service gateway according to an embodiment of the present invention;

Fig. 12 is a flow chart 1 of interaction between the serving gateway and the MME according to a preferred embodiment of the present invention;

Fig. 13 is the second interaction flow chart between the serving gateway and the MME according to the preferred embodiment of the present invention;

Fig. 14 is a third flowchart of the interaction between the serving gateway and the MME according to the preferred embodiment of the present invention.

detailed description

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

It should be noted that the terms "first" and "second" in the description and claims of the present invention and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence.

In this embodiment, a management method of a service gateway is provided. FIG. 3 is a flow chart 1 of a management method of a service gateway according to an embodiment of the present invention. As shown in FIG. 3 , the process includes the following steps:

Step S302, the serving gateway SGW-C of the control plane receives the registration message of the serving gateway SGW-U of the forwarding plane, wherein the registration message carries the service area information of the SGW-U; and/or,

Step S304, according to the service area information of the SGW-U, the SGW-C determines the mobility management unit related to the service area, and then sends an update message for updating the SGW-U information to the mobility management unit MME, wherein , the update message carries the identity of the SGW-U and/or the IP address of the SGW-U and the service area information, and the service area information is used to indicate that the tracking area identifier TAI list allocated by the MME for the terminal does not exceed the SGW-U The area served.

Through the above steps, the serving gateway SGW-C of the control plane receives the registration message of the serving gateway SGW-U of the forwarding plane, wherein the registration message carries the service area information of the SGW-U, and/or, the SGW-C sends The mobility management unit MME sends an update message for updating the SGW-U, where the update message carries the identity of the SGW-U and/or the IP address of the SGW-U and the service area information, and the service area information is used for Instruct the MME that the tracking area identification TAI list allocated for the terminal does not exceed the area served by the SGW-U, which solves the problem of how the MME knows the service area of the SGW-U, and realizes that the TAI list allocated by the MME to the user will not exceed the area served by the SGW-U. SGW-U service area.

In this embodiment, the registration message also includes at least one of the following:

The identifier of the SGW-U, the capacity weight of the SGW-U, the user type served by the SGW-U, and the service information served by the SGW-U.

In this embodiment, the service area information includes:

The tracking area identifier TAI list of the SGW-U.

In this embodiment, after the SGW-C sends an update message for updating the SGW-U to the mobility management unit MME, the SGW-C sends a keep-alive request to the SGW-U;

When the SGW-C receives the keep-alive response from the SGW-U, confirm that the SGW-U is valid;

If the SGW-C does not receive the keep-alive response from the SGW-U, confirm that the SGW-U is invalid, delete the user data of the SGW-U locally at the SGW-C, and send an update to the MME A message of the SGW-U, where the message carries the SGW-U identification and failure indication.

In this embodiment, the SGW-C receives the de-registration request of the SGW-U;

The SGW-C sends a deregistration response to the SGW-U, and sends a message to update the SGW-U to the MME, where the message carries the SGW-U identifier and failure indication.

In this embodiment, after the SGW-C receives the de-registration request from the SGW-U, the SGW-C reselects the SGW-U;

If the reselection fails, send the SGW-C failure information to the MME.

In this embodiment, the SGW-C sends a request to delete the SGW-U to the SGW-U, and sends a message to update the SGW-U to the MME, and the message carries the identification of the SGW-U and an invalidation indication.

In this embodiment, a management method of a service gateway is also provided. FIG. 4 is a flow chart 2 of a management method of a service gateway according to an embodiment of the present invention. As shown in FIG. 4 , the process includes the following steps:

Step S402, the mobility management unit MME receives an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the SGW-U IP address and service area information of the SGW-U;

Step S404, the MME allocates a TAI list to the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U.

Through the above steps, the mobility management unit MME receives an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the SGW-U According to the IP address of U and the service area information of the SGW-U, the MME allocates a tracking area identifier TAI list to the terminal according to the service area information. The TAI does not exceed the area served by the SGW-U, which solves how the MME knows The problem of the service area of the SGW-U is to realize that the TAI list allocated by the MME to the user will not exceed the service area of the SGW-U.

In this embodiment, the MME receives a message for updating the SGW-U sent by the SGW-C, where the message carries the identifier of the SGW-U and the service area information of the SGW-U.

This embodiment also provides a service gateway management device, which is used to implement the above embodiments and preferred implementation modes, and what has been described will not be repeated. As used below, the term "module" may be a combination of software and/or hardware that realizes a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

Fig. 5 is a structural block diagram 1 of a management device of a serving gateway according to an embodiment of the present invention. As shown in Fig. 5, the device is located in the serving gateway SGW-C on the control plane, including

The first receiving module 52 is configured to receive a registration message of the serving gateway SGW-U on the forwarding plane, where the registration message carries the service area information of the SGW-U; and/or,

The sending module 54 is configured to send an update message for updating the SGW-U to the selected mobility management unit MME, where the update message carries the identity of the SGW-U and/or the IP address of the SGW-U and the SGW-U - service area information of the U, the service area information is used to indicate that the MME allocates a tracking area identifier TAI list for the terminal that does not exceed the area served by the SGW-U.

Through the above device, the first receiving module 52 receives the registration message of the serving gateway SGW-U on the forwarding plane, and the sending module 54 sends an update message for updating the SGW-U to the mobility management unit MME, which solves how the MME knows the SGW-U The problem of the service area of U realizes that the TAI list allocated by the MME to the user will not exceed the service area of the SGW-U.

In this embodiment, the registration message also includes at least one of the following:

The identifier of the SGW-U, the capacity weight of the SGW-U, the user type served by the SGW-U, and the service information served by the SGW-U.

In this embodiment, the service area information includes: a tracking area identifier TAI list of the SGW-U.

Fig. 6 is a structural block diagram 2 of a management device of a service gateway according to an embodiment of the present invention. As shown in Fig. 6, in addition to the modules in Fig. 5, the device also includes:

The keep-alive module 62 is configured to send a keep-alive request to the SGW-U after sending an update message for updating the SGW-U to the mobility management unit MME;

The keep-alive module 62 is further configured to confirm that the SGW-U is valid when the SGW-C receives the keep-alive response from the SGW-U;

The keep-alive module 62 is further configured to confirm that the SGW-U is invalid when no keep-alive response from the SGW-U is received, and delete the user data of the SGW-U locally at the SGW-C, and Send a message for updating the SGW-U to the MME, where the message carries the SGW-U identifier and failure indication.

Fig. 7 is a structural block diagram three of a management device of a service gateway according to an embodiment of the present invention. As shown in Fig. 7, in addition to the modules in Fig. 5, the device also includes:

A registration module 72, configured to receive the de-registration request of the SGW-U;

The registration module 72 is also configured to send a de-registration response to the SGW-U, and send a message to update the SGW-U to the MME, where the message carries the SGW-U identification and invalidation indication.

Fig. 8 is a structural block diagram 4 of a management device of a service gateway according to an embodiment of the present invention. As shown in Fig. 8, in addition to the modules in Fig. 5, the device also includes:

The selection module 82 is configured to reselect the SGW-U after receiving the de-registration request of the SGW-U;

The selection module 82 is further configured to send the SGW-C failure information to the MME when the reselection fails.

Fig. 9 is a structural block diagram five of a management device of a service gateway according to an embodiment of the present invention. As shown in Fig. 9, in addition to the modules in Fig. 5, the device also includes:

The deletion module 92 is configured to send a request for deleting the SGW-U to the SGW-U, and send a message for updating the SGW-U to the MME, where the message carries the identification of the SGW-U and a failure indication.

Fig. 10 is a structural block diagram six of a management device of a serving gateway according to an embodiment of the present invention, which is located in a mobility management unit MME. As shown in Fig. 10 , the device further includes:

The second receiving module 1002 is configured to receive an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the SGW-U IP address and service area information of the SGW-U;

The allocation module 1004 is configured to allocate a TAI list to the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U.

Through the above means, the second receiving module 1002 receives an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the SGW-U Based on the IP address of U and the service area information of the SGW-U, the allocation module 1004 allocates a tracking area identifier TAI list to the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U, which solves the problem of MME How to know the service area of the SGW-U realizes that the TAI list allocated by the MME to the user will not exceed the service area of the SGW-U.

Fig. 11 is a structural block diagram VII of a management device of a service gateway according to an embodiment of the present invention. In addition to the modules in Fig. 10, the device also includes:

The update module 1102 is configured to receive a message for updating the SGW-U sent by the SGW-C, wherein the message carries the identifier of the SGW-U and the service area information of the SGW-U.

In another embodiment of the present invention, a serving gateway management system is also provided, including: a serving gateway SGW-C on the control plane, a serving gateway SGW-U on the forwarding plane, and a mobility management unit MME:

The SGW-C receives the registration message of the SGW-U, wherein the registration message carries the service area information of the SGW-U;

The SGW-C selects a mobility management unit MME according to the service area information of the SGW-U, and then sends an update message for updating the SGW-U to the MME, where the update message carries the identity of the SGW-U and Service area information of the SGW-U;

The MME allocates a TAI list for the terminal according to the service area information, and the TAI list does not exceed the area served by the SGW-U.

The present invention will be described in detail below in combination with preferred embodiments and implementation modes.

Figure 12 is a flow chart of the interaction between the serving gateway and the MME according to the preferred embodiment of the present invention. After the SGW-U is started, it performs a registration request process to the SGW-C. Through this process, the association between the SGW-C and the SGW-U is realized. , and MME can know the service area of SGW-U, the process includes:

Step S1201, after the SGW-U is powered on, find the IP address of the SGW-C according to the pre-configuration information, and then initiate a registration process to the SGW-C, the registration request message contains the SGW-U identifier, the SGW-U Service area (such as TAI list), capacity weight of SGW-U. The capacity weight of the SGW-U is used for subsequent SGW-U selection to achieve load balancing of the SGW-U. At some point, the SGW-U is only responsible for one type of user or one type of service, so the registration request message may also contain the user type or service information served by the SGW-U.

In step S1202, after saving the relevant information of the SGW-U, the SGW-C returns a registration response to the SGW-U.

Step S1203, SGW-C finds the corresponding MME according to the TAI list served by the SGW-U, and then updates the SGW-U information to the MME, the update message contains the SGW-U identification and the SGW-U served Regional information, such as TAI list. The MME stores the identity of the SGW-U and the information of the area it serves. This information is used by the MME to allocate a TAI list for the terminal. It is necessary to ensure that the TAI list allocated to the terminal cannot exceed the area served by the SGW-U.

In step S1204 and step S1205, SGW-U and SGW-C can also send keep-alive requests and keep-alive responses to each other, so that they can know whether each other exists.

Step S1206, when the SGW-C finds that the SGW-U is invalid, it will locally delete the user data related to the SGW-U and send the updated SGW-U information to the MME, carrying the SGW-U identification and invalidation indication.

Step S1207, when SGW-U finds that SGW-C is invalid, it will delete user data locally and then may find a new SGW-C for registration. If no suitable SGW-C is found, it will send an alarm and wait for further operations by the administrator.

Fig. 13 is the second flow chart of the interaction between the serving gateway and the MME according to the preferred embodiment of the present invention. As shown in Fig. 13, it is a schematic diagram of the de-registration process initiated by SGW-U. Through this process, SGW-U and SGW-C cancel the association relationship , the process includes:

In step S1301, the SGW-U may initiate a de-registration request to the SGW-C, carrying the SGW-U identifier.

In step S1302, SGW-C sends a de-registration response to SGW-U after receiving it.

In step S1303, the SGW-C reselects a new SGW-U for all current users, and may initiate the SGW-U reselection process. If the SGW-C successfully selects the SGW-U, the subsequent process will use the new SGW-U.

Step S1304, if re-selecting a new SGW-U fails, send an SGW notification request to the MME to notify the MME that the SGW has failed, and then the MME may re-select a new SGW-C, if the selection fails, the MME deactivates the user.

Step S1303 and step S1304 need to be processed separately for each user of the SGW-U. In addition, after step 402, the SGW-C may send separate updated SGW-U information to the MME, carrying the SGW-U identity and failure indication. After receiving it, the MME deletes the stored information of the SGW-U service area.

Fig. 14 is the third interaction flowchart between the serving gateway and the MME according to the preferred embodiment of the present invention. As shown in Fig. 14, the SGW-C initiates the process of deleting the SGW-U, and the process includes:

Step 1401, SGW-C can also initiate a request to delete SGW-U at any time

Step 1402, after the SGW-U receives it, it will delete the user data locally.

In step 1403, the SGW-C needs to initiate a process of updating the SGW-U information to the MME, and the MME deletes the saved service area information of the SGW-U after receiving it.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is Better implementation. Based on such an understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

It should be noted that each of the above-mentioned modules can be implemented by software or hardware. For the latter, it can be implemented in the following manner, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules are respectively located in multiple in the processor.

The embodiment of the invention also provides a storage medium. Optionally, in this embodiment, the foregoing storage medium may be configured to store program codes for executing the method steps of the foregoing embodiments:

Optionally, the storage medium is also configured to store program codes for executing the method steps of the foregoing embodiments:

Optionally, in this embodiment, the above-mentioned storage medium may include but not limited to: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk Various media that can store program codes such as discs or optical discs.

Optionally, in this embodiment, the processor executes the method steps of the foregoing embodiments according to the program code stored in the storage medium.

Optionally, for specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and optional implementation manners, and details are not repeated in this embodiment.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases, in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (19)

1. A management method for a service gateway, comprising: The serving gateway SGW-C of the control plane receives the registration message of the serving gateway SGW-U of the forwarding plane, wherein the registration message carries the service area information of the SGW-U; and/or, The SGW-C sends an update message for updating the SGW-U to the mobility management unit MME, where the update message carries the identity of the SGW-U and/or the IP address of the SGW-U and the Service area information, where the service area information is used to instruct the MME to allocate a tracking area identifier TAI list for the terminal that does not exceed the area served by the SGW-U. 2. The method according to claim 1, wherein the registration message further includes at least one of the following: The identifier of the SGW-U, the capacity weight of the SGW-U, the user type served by the SGW-U, and the service information served by the SGW-U. 3. The method according to claim 1, wherein the service area information includes: The tracking area identifier TAI list of the SGW-U. 4. The method according to claim 1, wherein after the SGW-C sends an update message for updating the SGW-U to the mobility management unit MME to which the SGW-U belongs, the method includes: The SGW-C sends a keep-alive request to the SGW-U; If the SGW-C receives the keep-alive response from the SGW-U, confirm that the SGW-U is valid; If the SGW-C does not receive the keep-alive response from the SGW-U, confirm that the SGW-U is invalid, and delete the user data of the SGW-U locally at the SGW-C, and Sending a message for updating the SGW-U to the MME, where the message carries the SGW-U identifier and failure indication. 5. The method according to claim 1, wherein the method further comprises: The SGW-C receives the de-registration request of the SGW-U; The SGW-C sends a de-registration response to the SGW-U, and sends a message to update the SGW-U to the MME, where the message carries the SGW-U identifier and failure indication. 6. The method according to claim 5, wherein after the SGW-C receives the de-registration request of the SGW-U, it comprises: The SGW-C reselects the SGW-U; If the reselection fails, send the SGW-C failure information to the MME. 7. The method according to claim 1, further comprising: The SGW-C sends a request to the SGW-U to delete the SGW-U, and sends a message to the MME to update the SGW-U, and the message carries the SGW-U identification and invalidation indication . 8. A management method for a service gateway, comprising: The mobility management unit MME receives an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the identity of the SGW-U IP address and the service area information; The MME allocates a TAI list to the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U. 9. The method of claim 8, further comprising: The MME receives the message for updating the SGW-U sent by the SGW-C, where the message carries the identifier of the SGW-U and the service area information of the SGW-U. 10. A management device for a serving gateway, located in the serving gateway SGW-C of the control plane, characterized in that it comprises: The first receiving module is configured to receive a registration message of the serving gateway SGW-U on the forwarding plane, wherein the registration message carries the service area information of the SGW-U; and/or, A sending module, configured to send an update message for updating the SGW-U to a mobility management unit MME to which the SGW-U belongs, where the update message carries the identity of the SGW-U and/or the SGW-U The IP address of U and the service area information, where the service area information is used to indicate that the TAI list allocated by the MME to the terminal does not exceed the area served by the SGW-U. 11. The device according to claim 10, wherein the registration message further includes at least one of the following: The identifier of the SGW-U, the capacity weight of the SGW-U, the user type served by the SGW-U, and the service information served by the SGW-U. 12. The device according to claim 10, wherein the service area information includes: The tracking area identifier TAI list of the SGW-U. 13. The device of claim 10, wherein the device comprises: A keep-alive module, configured to send a keep-alive request to the SGW-U after sending an update message for updating the SGW-U to the mobility management unit MME to which the SGW-U belongs; and when the SGW-C receives If the keep-alive response from the SGW-U is received, confirm that the SGW-U is valid; if the keep-alive response from the SGW-U is not received, confirm that the SGW-U is invalid, and The SGW-C locally deletes the user data of the SGW-U, and sends a message for updating the SGW-U to the MME, and the message carries the identification of the SGW-U and a failure indication. 14. The device according to claim 10, further comprising: A registration module, configured to receive the de-registration request of the SGW-U; and send a de-registration response to the SGW-U, and send a message for updating the SGW-U to the MME, the message carrying the Identification and failure indication of SGW-U. 15. The device according to claim 10, further comprising: The selecting module is configured to reselect the SGW-U after receiving the de-registration request of the SGW-U; and if the reselection fails, send the SGW-C failure information to the MME. 16. The device according to claim 10, further comprising: A deletion module, configured to send a request to the SGW-U to delete the SGW-U, and send a message to the MME to update the SGW-U, where the message carries the SGW-U identifier and failure indication . 17. A management device for a serving gateway, located in a mobility management unit MME, characterized in that it includes: The second receiving module is configured to receive an update message sent by the serving gateway SGW-C of the control plane to update the serving gateway SGW-U of the forwarding plane, wherein the update message carries the identity of the SGW-U and/or the SGW-U U's IP address and the service area information; An allocating module, configured to allocate a TAI list for the terminal according to the service area information, wherein the TAI list does not exceed the area served by the SGW-U. 18. The device according to claim 17, further comprising: An updating module, configured to receive a message for updating the SGW-U sent by the SGW-C, wherein the message carries the identifier of the SGW-U and the service area information of the SGW-U. 19. A management system for a serving gateway, comprising: a serving gateway SGW-C on a control plane, a serving gateway SGW-U on a forwarding plane, and a mobility management unit MME: The SGW-C is configured to receive a registration message of the SGW-U, wherein the registration message carries the service area information of the SGW-U; and report to the mobility management unit MME to which the SGW-U belongs sending an update message for updating the SGW-U; The MME is configured to allocate a TAI list for the terminal according to the service area information, and the TAI list does not exceed the area served by the SGW-U.