WO2011150564A1

WO2011150564A1 - Method, equipment and system for processing data gateway load

Info

Publication number: WO2011150564A1
Application number: PCT/CN2010/073475
Authority: WO
Inventors: 于游洋; 吴问付; 孙晓姬
Original assignee: 华为技术有限公司
Priority date: 2010-06-02
Filing date: 2010-06-02
Publication date: 2011-12-08
Also published as: CN102450052B; CN102450052A

Abstract

The present invention provides a method, equipment and system for processing data gateway load. The method includes the following steps: when the data gateways are normal, a gateway management network element receives state information reporting messages transmitted by the data gateways, wherein, the state information reporting messages carry state information; when the data gateway requiring load balancing is determined, the gateway management network element chooses a target data gateway for the source data gateway according to the state information, wherein, the source data gateway is the data gateway requiring load balancing; the gateway management network element sends the state information of the target data gateway to the source data gateway, so that the source data gateway transfers, according to the state information of the target data gateway, part of the user services from the source data gateway to the target data gateway. The present invention can implement load balance between data gateways.

Description

Data gateway load processing method, device and system

Technical field

The present invention relates to mobile communication technologies, and in particular, to a data gateway load processing method, device and system. Background technique

In the next generation mobile communication network, the user terminal is connected to the core network through the local wireless access network, and accesses the Packet Data Network (PDN) through the core network. The core network includes devices such as Mobility Management Entity (ΜΜΕ), Serving Gateway (SGW), and Data Gateway (PDW Gateway, PGW). Among them, the PGW is mainly responsible for data forwarding and connection management between the user terminal and the PDN it accesses, and is also a service anchor in the process of moving the user terminal.

After the user terminal accesses the core network, the MME selects an appropriate PGW based on the PDN accessed by the user terminal, and the SGW connects to the designated PGW according to the PGW address sent by the MME.

The PGW assigns the connected terminal an IP address so that the user terminal can use this IP address to communicate with the PDN network it accesses. When the user terminal moves, in order to maintain the continuity of the user's service, the IP address of the user terminal should remain unchanged.

At present, as the number of user terminals continues to increase and the types of services continue to be enriched, the burden on the PGW is becoming heavier. Especially when the MME selects the PGW, even if multiple PGWs are available, the candidate weights of the PGWs remain basically unchanged, resulting in higher PGW loads with higher weights and relatively lower PGW loads. Light result. Therefore, in order to make full use of existing equipment resources, load migration processing needs to be performed between each PGW. In addition, when some data gateways fail or need to be upgraded and maintained, they also face the need for load migration.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: In the prior art, no related scheme can discover and handle the overload of the data gateway. Summary of the invention

Embodiments of the present invention provide a data gateway load processing method, device, and system, which implement overload processing between data gateways.

The embodiment of the invention provides a data gateway load processing method, including:

When the data gateway is normal, the gateway management network element receives the status information report message sent by the data gateway, and the status information report message carries the status information;

When the data gateway that needs load balancing is determined, the gateway management network element selects a target data gateway for the source data gateway according to the status information, where the source data gateway is a data gateway that needs to perform load balancing;

The gateway management network element sends the status information of the target data gateway to the source data network element, so that the source data gateway migrates part of the user service from the source data gateway to the Target data gateway.

An embodiment of the present invention provides a data gateway load processing device, including:

a receiving module, configured to: when the data gateway is normal, receive a status information report message sent by the data gateway, where the status information report message carries status information;

a target gateway selection module, configured to select a target data gateway for the source data gateway according to the status information, where the source data gateway is a data gateway that needs to perform load balancing, when determining a data gateway that needs to perform load balancing;

a target gateway sending module, configured to send status information of the target data gateway to the source data network element, so that the source data gateway migrates part of user services by the source data gateway according to status information of the target data gateway Go to the target data gateway.

The embodiment of the invention provides a data gateway load processing system, including:

The gateway management network element is configured to: when the data gateway is normal, receive a status information report message sent by the data gateway, where the status information report message carries status information, and determines a data gateway that needs to be load balanced, according to the status Information for the source data gateway to select the target data gateway, The source data gateway is a data gateway that needs to be load balanced;

And a source data gateway, configured to migrate part of user services from the source data gateway to the target data gateway according to status information of the target data gateway.

According to the foregoing technical solution, the embodiment of the present invention implements load balancing between data gateways by selecting a target data gateway for the source data gateway, and implements overload processing between data gateways. DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying creative labor.

1 is a schematic diagram of a network architecture according to an embodiment of the present invention;

2 is a schematic flow chart of a method according to a first embodiment of the present invention;

3 is a schematic diagram of data storage in an embodiment of the present invention;

4 is a schematic flow chart of a method according to a second embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method for acquiring user context data by a primary data gateway according to an embodiment of the present invention; FIG.

6 is a schematic flow chart of a method according to a third embodiment of the present invention;

FIG. 3 is a schematic flowchart of a method for performing load migration of a source data gateway to a target data gateway according to an embodiment of the present invention;

8 is a schematic flow chart of a method according to a fourth embodiment of the present invention;

9 is a schematic structural diagram of a device according to a fifth embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a system according to a sixth embodiment of the present invention. detailed description The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In order to better understand the embodiments of the present invention, the network architecture of the embodiment of the present invention is first described.

FIG. 1 is a schematic diagram of a network architecture of an embodiment of the present invention, including an MME 11, an SGW 12, a data gateway (taking a PGW in the figure) 13 and a gateway management network element 14. The data gateway of the embodiment of the present invention takes PGW as an example. It can be understood that the data gateway can also be a Gateway General Packet Radio Service (GPRS) support node (Gateway GPRS Support, GGSN) and a packet data service node ( Packet Data Serving Node (PDSN), Access Service Network Gateway (ASN-GW), Packet Data Gateway (PDG), and the like.

Each gateway management network element 14 (for example, one gateway management network element in FIG. 1) is connected to a plurality of data gateways 13 (for example, PGW-1, PGW-2, ..., PGW-n in FIG. 1). Form a data gateway resource pool (hereinafter referred to as a resource pool). Each data gateway is responsible for multiple address pool spaces, and different data gateways may have the same address pool. For example, PGW-1 and PGW-2 may have the same address pool space IP VI, and PGW-2 and PGW-3 may also have the same address pool space IP V2, and the rest are similar. When the data gateway 13 is normal, the status information of the data gateway 13 is reported to the gateway management network element 14, and the status information may include the data gateway identifier (such as the IP address of the data gateway), the address pool space occupied by the data gateway, and the reachable access point name. (Access Point Name, APN) List and load weight parameters, etc. The load weight parameter may be determined based on the data gateway 13's own capabilities and the current load situation. For example, for a data gateway with a higher load capacity and a lower current load, the load weight parameter is larger, and vice versa, for the data to be reached. Gateway, the load weight parameter is small, in other words, the data gateway with higher load capacity and lower current load, The load weight parameter is greater than the load weight parameter of the data gateway with lower load capacity and higher current load. When the data gateway 13 is overloaded, the load weight parameter is obtained as zero. Specifically, a mapping table may be preset in the data gateway 13, where the mapping table indicates the ratio of the current load to the self-loading capability, and the corresponding relationship between the load weight parameter, and the data gateway 13 calculates the current load condition according to the current load capacity. The ratio, after which the corresponding load weight parameter is found in the mapping table. The ratio in the mapping table is inversely proportional to the load weight parameter. That is, the larger the ratio is, the smaller the load weight parameter is. When the ratio is greater than 1, the load weight parameter is 0.

In the embodiment of the present invention, a real-time backup mechanism is adopted, that is, after receiving the data, the primary data gateway backs up the received data to the backup data gateway; after that, during the load migration, the backup data gateway is selected as the target of the source data gateway. Data gateway. The data gateway that needs to be backed up is the primary data gateway, the data gateway to which the data is backed up is called the backup data gateway; the data gateway that needs to perform load migration is the source data gateway, and the data gateway to which the data is migrated is called the target data gateway. .

FIG. 2 is a schematic flowchart of a method according to a first embodiment of the present invention, where the embodiment corresponds to a backup process. See Figure 2, including:

Step 21: When the data gateway is normal, the gateway management network element receives the status information report message sent by the data gateway, where the status information report message carries the status information;

For example, when the data gateway is normal, the data gateway sends a status information report message to the gateway management network element after receiving the ping signaling sent by the gateway management network element, or after the timer set by the data gateway expires. The information report message carries status information, and the status information may include a data gateway identifier, a load weight parameter, an address pool space, a reachable APN list, and the like.

Step 22: When determining the data gateway that needs to be backed up, the gateway management network element selects a backup data gateway according to the status information, and the primary data gateway is a data gateway that needs to be backed up;

In the prior art, the backup data of the internal user data of the device is used in the backup, that is, the user data on the main board in the data gateway is stored in the standby board in real time. When the motherboard fails, enable the standby board to replace the motherboard to provide services for users. However, since the motherboard and the standby board are in the same device, When the entire device fails, user data loss, service interruption, and so on will still occur.

In this embodiment, another data gateway is selected as the backup data gateway.

In addition, in this embodiment, the dedicated backup data gateway may not be set, but the user context data in the data gateway is divided into main user data and backup user data. The data gateway allocates resources for the primary user data, and is responsible for data forwarding and connection management between the primary user terminal and the PDN accessed by the primary user terminal. The data gateway does not allocate resources for the backup user data, but only serves to store the user data.

Further, in order to reduce the burden on the data gateway, the main user data may be divided into several parts and stored in different backup data gateways. For example, FIG. 3 is a schematic diagram of data storage in an embodiment of the present invention. Referring to FIG. 3, a primary data gateway has two backup data gateways as an example, and data gateway-1 and data gateway-3 are backup gateways of data gateway-2. The user data of the data gateway-2 includes primary user data and backup user data. For example, the primary user can be divided into two parts, a primary user data-1 and a primary user data-2, wherein the primary user data-1 is stored to In the data gateway-1, as the backup data of the data gateway-1; the main user data-2 is stored in the data gateway-3 as the backup data of the data gateway-3. In this embodiment, the data gateway-2 can also serve as a backup data gateway of the data gateway-1 and the data gateway-3, and the primary user data backup mode of the data gateway-1 or the data gateway-3 is the same as that of the data gateway-2.

The selection policy of the backup data gateway may be as follows: The gateway management network element sorts all the data gateway devices having the coincidence address pool space with the primary data gateway according to the load weight parameter, if the load weight parameters of the two data gateways are the same, Comparing the similarity between the APN list and the primary data gateway, the data gateway with high similarity is preferred. If the reachable APN list is still the same, the sequence is determined randomly. Since the backup data can be stored separately, the backup data gateway can be N and N is greater than or equal to 1.

Step 23: The gateway management network element sends the status information of the backup data gateway to the primary data gateway, so that the primary data gateway synchronizes the user context data to the backup data gateway according to the status information of the backup data gateway. .

On the one hand, the primary data gateway can choose different user context data in the following manner. Corresponding backup data gateway: The primary data gateway selects the backup data gateway according to the address pool space and load weight parameter that the primary data gateway is responsible for, and the status information of the backup data gateway sent by the gateway management network element. For example, corresponding to a user terminal, the IP address assigned by the primary data gateway to the user terminal is

IP-1 first selects the data gateway with IP-1 in the address pool space. Then, in the data gateway that meets the IP-1 address in the address pool space, the data gateway with large load weight parameter is preferentially selected as the backup data gateway. After that, the relationship between the user context data and the backup data gateway is saved in the primary data gateway.

On the other hand, the primary data gateway can be synchronized in the following manner: For example, a synchronization timer can be set. After the synchronization timer expires, the primary data gateway sends a user context synchronization request to the backup data gateway, and the backup data gateway receives the user context synchronization request. After receiving the user context data sent by the primary data gateway; or, the primary data gateway carries the user context data in the user context synchronization request and sends the data to the backup data gateway. The user context data may be user context data newly created by the primary data gateway, or may be updated user context data.

The above describes the process of synchronizing user context data from the primary data gateway to the backup data gateway, and the primary data gateway can acquire user context data in the following manner.

In this embodiment, by backing up data to another data gateway, data backup to the same data gateway can be avoided, and the data gateway has a data loss problem when the data gateway fails. This embodiment provides real-time backup for subsequent load migration. .

FIG. 4 is a schematic flowchart of a method according to a second embodiment of the present invention, where the embodiment corresponds to a load migration process. Referring to FIG. 4, this embodiment includes:

Step 41: When the data gateway is normal, the gateway management network element receives the status information report message sent by the data gateway, where the status information report message carries the status information;

For example, when the data gateway is normal, the data gateway sends a status information report message to the gateway management network element after receiving the ping signaling sent by the gateway management network element, or after the timer set by the data gateway expires. The information report message carries status information, and the status information may include a data gateway identifier, a load weight parameter, an address pool space, and a reachable APN list. Step 42: When determining a data gateway that needs to perform load balancing, the gateway management network element selects a target data gateway for the source data gateway according to the status information, where the source data gateway is a data gateway that needs to perform load balancing;

Specifically, the following manners can be used to determine whether there is a data gateway that needs to perform load balancing: corresponding to each data gateway, a weight threshold can be set, and different data gateways can be set with the same weight threshold, or different weight thresholds can be set. . When the load weight parameter in the status information reported by the data gateway is less than or equal to the weight threshold, it indicates that load balancing is required.

On the other hand, the target data gateway can be selected as follows:

In the first method, when the source data gateway has a backup data gateway, the gateway management network element sorts the backup data gateway of the source data gateway according to the load weight parameter from the largest to the smallest, and preferentially selects the backup data gateway with the large load weight parameter as the target data gateway;

Manner 2: if the load weight parameter of the backup data gateway of the source data gateway is small, the data gateway with the address pool space and the load weight parameter with the source data gateway is selected as the target data gateway;

Specifically, when the load weight parameters of the two target data gateways are the same, the reachable APN list may be compared, and the target data gateway having the similarity with the reachable APN list of the source data gateway is preferentially selected;

When the reachable APN list is still the same, it can be randomly selected.

Step 43: The gateway management network element sends the status information of the target data gateway to the source data gateway, so that the source data gateway migrates part of the user service from the source data gateway according to the status information of the target data gateway. The target data gateway.

The source data gateway may receive the state information of the target data gateway sent by the gateway management network element; the source data gateway selects the migrated user according to the state information of the target data gateway, and selects the target data gateway for the migrated user; The gateway notifies the target data gateway corresponding to the migrated user to take over the user service of the migrated user.

Specifically, when the target data gateway is a backup data gateway of the migrated user, the source data gateway Sending an invite message to the backup data gateway, where the migrated user identifier is carried, so that the primary user data is allocated resources; when the target data gateway is not the backup data gateway of the migrated user, the data gateway is to be migrated to the user context of the user. The data is saved as the main user data, and resources are allocated to the main user data.

In this embodiment, the target data gateway is selected for the source data gateway, and the user context data can be migrated from the source data gateway to the target data gateway when the load migration is required to implement load balancing, or the service is not interrupted when the fault occurs or the maintenance is performed.

FIG. 5 is a schematic flowchart of a method for acquiring user context data by a primary data gateway according to an embodiment of the present invention, including:

Step 501: The user terminal sends an attach request message to the mobility management network element.

Wherein, for a radio access network or a universal terrestrial radio access network (GERAN/UTRAN), the mobility management network element is a Serving GPRS Support Node (SGSN); In the UMTS Universal Mobile Telecommunications System (EUTRAN) network, the mobility management network element is an MME (Mobility Management Entity).

Step 502: The user terminal performs an authentication and authentication operation with the mobility management network element and the Home Subscriber Server (HSS).

Step 503: Perform a location update and user subscription data insertion process between the mobility management gateway and the HSS. The mobility management network element address is registered in the HSS, and the HSS sends the user subscription data to the mobility management network element for storage.

Step 504: The mobility management network element sends a default bearer request to the SGW, where the primary data gateway identifier, such as the IP address of the primary data gateway, is carried.

The mobility management network element selects the primary data gateway according to the APN information sent by the user terminal or the default APN information carried in the user subscription data; and selects the SGW according to the user location information. Step 505: The SGW creates a new context for the user in the Evolved Packet System (EPS) bearer table, and sends the primary data gateway identifier in the default bearer request sent by the mobility management network element to the primary data gateway. The default bearer request, the SGW sends a default bearer request, and carries information such as an SGW address, an SGW user plane tunnel end identifier (TEID), and an SGW control plane TEID.

Step 506: If a dynamic policy generation mechanism is adopted, the primary data gateway interacts with a Policy and Charging Rule Function (PCRF) to perform a policy control operation.

For example, the PCRF sends a Policy Control and Charging (PCC) rule to the primary data gateway, including the QoS of the bearer, such as bandwidth, delay, packet loss rate, Type of Service (ToS), Differentiated Services Code Point (DSCP), QoS Class Identifier (QCI), etc.; charging rules include charging information corresponding to the service data stream transmitted by the data connection, for example, by time length The value, the flow rate, the pay-per-view value, and so on.

The primary data gateway then creates a user context for the attached user.

The user context includes user identification, bearer context information, PCC session context, charging information, and assigned user IP information. The user identifier may be an International Mobile Subscriber Identity (IMSI), a Network Access Identifier (NAI), or a Mobile Station International ISDN Number (MSISDN); The context information includes the SGW control plane and the user plane address and the TEID, the EPS bearer ID (bearer ID); the assigned user IP information includes the user terminal IP address, the IP address attribute, and the IP address lease period, when the data gateway acts as a DHCP client or/and In the DHCP server, the IP address information of the user terminal also includes the IP address and configuration information maintained by the DHCP.

Step 507: The primary data gateway returns a default bearer response to the SGW.

The default bearer response carries information such as the user plane and control plane address of the primary data gateway, and the TEID and EPS bearer ID. Step 508: The SGW returns a default bearer response to the mobility management network element, where the default bearer response message sent by the SGW carries the SGW address, the user plane and the control plane TEID, and the primary data gateway information.

Step 509: The mobility management network element acquires the primary data gateway information according to the Create Default Bearer Response sent by the SGW, and sends an attach accept message to the user terminal.

If the subscriber's subscription data allows interworking with the non-3GPP, the process of associating the primary data gateway address with the corresponding APN and registering with the HSS is further completed. That further includes:

Step 510: The mobility management network element sends an update data gateway address to the HSS, where the APN and the primary data gateway address used by the user terminal are carried.

Step 511: The HSS saves the APN and the primary data gateway address used by the user terminal, and returns an update response to the mobility management network element.

The real-time backup process in this embodiment can synchronize the user context data created or updated by the primary data gateway to the backup data gateway, avoiding data loss or service interruption when the primary data gateway fails, and improving user data security and service. stability. This embodiment does not have a dedicated backup data gateway, which can save costs. In this embodiment, the backup data can be separately saved, which can reduce the burden on the data gateway and improve system resource utilization.

The above describes the process of load balancing and real-time backup respectively. In the specific implementation, load balancing and real-time backup can be combined.

FIG. 6 is a schematic flowchart of a method according to a third embodiment of the present invention. The embodiment corresponds to a process of combining load balancing and real-time backup. Referring to Figure 6, this embodiment includes:

Step 601: The gateway management network element sends ping signaling to each data gateway.

Step 602: If the data gateway is normal, the data gateway sends a status message to the gateway management network element.

The status information report message carries the status information of the data gateway, and the status information includes a load weight parameter, a data gateway identifier, an address pool space that the data gateway is responsible for, and a reachable APN list.

The above is that the gateway management network element sends a ping signaling to enable the data gateway to send status information to report The data gateway may also set a timer in the data gateway. After the timer expires, the data gateway actively sends a status information report message to the gateway management network element.

Step 603: The gateway management network element performs an overload risk judgment on the data gateway according to the status information report message.

When there is an overload risk, it indicates that the data gateway needs to be load balanced. When there is no overload risk, if the backup gateway of the data gateway does not exist or the backup data gateway of the data gateway fails, it indicates that the data gateway needs to perform real-time backup.

The load weight threshold may be set in the gateway management network element. When the load weight parameter in the status information sent by the data gateway is less than or equal to the load weight threshold, it indicates that there is an overload risk; when the load weight parameter is greater than the load weight threshold , indicating that there is no risk of overload.

The information of each data gateway is saved in the gateway management network element, so that it is known whether the data gateway has a backup data gateway, or whether the backup data gateway fails when the data gateway has a backup data gateway.

The gateway management network element may determine whether to perform load balancing or real-time backup according to the overload risk judgment result. After determining load balancing, the data gateway that sends the status information report message is the source data gateway; when determining to perform real-time backup After that, the data gateway that sends the status information report message is the primary data gateway.

Step 604: The gateway management network element sends a status information feedback message to the primary/source data gateway.

After the overload risk is judged, when the data gateway needs to perform real-time backup, the data gateway is the primary data gateway. At this time, the gateway management network element selects the backup data gateway for the primary data gateway, and then carries the information of the backup data gateway in the state. The information feedback message is sent to the primary data gateway;

After the overload risk is judged, when the data gateway needs to perform load balancing, the data gateway is the source data gateway. At this time, the gateway management network element selects the target data gateway for the source data gateway, and then carries the information of the target data gateway in the state. The information feedback message is sent to the source data gateway.

Step 605: After receiving the status information feedback message, the primary/source data gateway determines to perform real-time backup or load balancing. When performing real-time backup, step 606 is performed, and when load balancing is performed, Go to step 607.

The data gateway can determine whether to perform real-time backup or load balancing according to its own state. For example, the data gateway itself sets a load weight threshold. When the load weight parameter is less than or equal to the load weight threshold, it indicates that load balancing needs to be performed. When the load weight parameter is used. When it is greater than the load weight threshold, it indicates that real-time backup is required.

When the real-time backup is required, the data gateway information carried in the status information feedback message is used as the information of the backup data gateway. When the load balancing is required, the data gateway information carried in the status information feedback message is used as the target data gateway. Information.

Step 606: The primary data gateway and the backup data gateway perform real-time backup.

For details, see step 23.

Step 607: The source data gateway determines whether the target data gateway is a backup data gateway, and then performs a corresponding load migration operation according to whether the target data gateway is a backup data gateway.

FIG. 3 is a schematic flowchart of a method for performing load migration of a source data gateway to a target data gateway according to an embodiment of the present invention. This embodiment uses a target data gateway as a backup data gateway of a source data gateway as an example. See Figure 7, including:

Step 701: The source data gateway sends an invite message to the target data gateway, where the message includes the migrated user identifier, and the user identifier may be IMSI, NAI, MSISDN, or the like. Select the target data gateway for the migrated user for the correspondence between the text data and the backup data gateway.

The target data gateway changes the status of the corresponding standby user data to the primary user data according to the migrated user identifier carried in the Invite message, so as to take over the part of the user service. The backup user data corresponding to the primary user data is sent by the target data gateway to the backup data gateway in the backup data synchronization process. Step 702: The target data gateway sends an update connection tunnel request to the SGW, requesting to update the connection tunnel.

The target data gateway obtains the SGW address according to the user context data, according to the SGW address. The address sends an update connection tunnel request to the access point.

The SGW updates the connection tunnel with the data gateway according to the update connection tunnel request message, that is, establishes a connection tunnel with the target data gateway. The specific update process varies with the tunneling protocol. For example, for the GPRS Tunneling Protocol (GTP), the target data gateway sends a bearer update request to the SGW, and the SGW updates the target data gateway user plane and the control plane address and the TEID, and establishes a GTP tunnel between the target data gateway and the SGW.

Step 703: The target data gateway updates the control session with the PCRF.

For example, the PCRF updates the policy control information under the migrated user source data gateway to the policy control information under the target data gateway. When obtaining the policy control information under the source data gateway corresponding to the migration service data flow information, the PCRF is based on the connection information provided by the target data gateway, such as the UE ID, the PDN ID, or the UE IP address. Or, based on the policy control information identifier obtained by the target data gateway from the source data gateway, searching for the policy control information under the corresponding source data gateway.

The PCRF generates policy control information under the target data gateway according to the service data flow information and the policy control information under the source data gateway, or directly uses the policy control information under the source data gateway as the policy control information under the target data gateway, and then sends the generation policy. Information to the target data gateway.

Step 704: The SGW sends an update connection tunnel request to the mobility management network element, where the updated content includes information such as a target data gateway user plane, a control plane address, and a TEID.

Step 705: The mobility management network element returns an update success message to the SGW. Indicates that the connection tunnel update was successful.

Step 706: The SGW returns an update success message to the target data gateway, indicating that the connection tunnel between the two is successfully established.

Step 707: The target data gateway advertises a routing network segment to the service gateway. The routing network segment information is determined by the IP address of the migrated user terminal. When the migrated user IP address belongs to the same address segment or the same subnet, the routing information of the network segment or subnet is changed, that is, the next hop data gateway address in the routing information of the network segment is changed from the source data gateway to the target data gateway. , establishing a connection between the target data gateway and the message data network. Step 708: The target data gateway sends a load migration success message to the source data gateway. The target data gateway notifies the source data gateway after taking over the user data successfully. The source data gateway deletes the migrated user data and releases the resources.

Step 709: The source data gateway deletes the user context data and translates the resources.

If the subscription data of the user allows interworking with the non-3GPP, the target data gateway address and the corresponding APN information may be further registered by the mobility management network element into the HSS. The message carries the APN and the target data gateway address used by the user; the HSS saves the APN and the target data gateway address information used by the user and returns an update response message to the mobility management network element.

The foregoing describes the process when the target data gateway is the backup data gateway. When the target data gateway is not the backup data gateway, the process is different from the above process, and the foregoing steps 701-702 further include:

The source data gateway sends a user context data delivery request to the target data gateway, and then the user context data is carried in the user context data delivery request and sent to the target data gateway;

The source data gateway sends a delete (delete) message to the backup data gateway corresponding to the migrated user, and instructs the backup data gateway to delete the corresponding backup user data. The delete message includes the migrated user identifier, which may be IMSI, NAI, MSISDN, and the like. After that, the backup data gateway deletes the corresponding backup user data based on the migrated user ID.

In this embodiment, the security of the user data and the stability of the service can be improved by performing real-time backup. Load migration can balance the load of each data gateway and improve system resource utilization.

The above processing of load balancing and/or real-time backup is performed when the data gateway is normal. When the data gateway fails, fault handling is required.

FIG. 8 is a schematic flowchart of a method according to a fourth embodiment of the present invention, including:

Step 801: The gateway management network element determines the faulty data gateway.

The time threshold is set in the gateway management network element. When the time threshold is reached, the data gateway corresponding to the status information reporting message is not the fault data gateway. The status information reporting message may be sent by the data gateway after receiving the ping signaling sent by the gateway management network element, or may be configured by setting a reporting timer in the data gateway, and actively sending the status information report when the time of reporting the timer is reached. Message.

Step 802: The gateway management network element determines a backup data gateway of the faulty data gateway.

The gateway management network element can determine whether the backup data gateway needs to perform load migration by comparing the load weight parameter of the backup data gateway with the set load weight threshold. In the embodiment of the present invention, when the data gateway is faulty or overloaded, it indicates that the data gateway needs to perform load migration, otherwise the load migration is not required.

When the backup data gateway does not need to perform load migration, perform the following steps:

Step 803: The gateway management network element sends an invite message to the backup data gateway, where the message carries the identifier of the fault data gateway, for example, the IP address of the fault data gateway.

After receiving the invite message, the backup data gateway enables the corresponding backup user context data and takes over the corresponding user service according to the fault data gateway identifier carried in the invite message.

Step 804: The backup data gateway sends an update connection tunnel request to the SGW, requesting to update the connection tunnel.

Specifically, the processing of step 702 can be similar.

Step 805: The backup data gateway updates the control session with the PCRF.

Specifically, the processing of step 703 can be similar.

Step 806: The SGW sends an update connection tunnel request to the mobility management network element, where the updated content includes information such as a target data gateway user plane, a control plane address, and a TEID.

Step 807: The mobility management network element returns an update success message to the SGW. Indicates that the connection tunnel update was successful.

Step 808: The SGW returns an update success message to the backup data gateway, indicating that the connection tunnel between the two is successfully established.

Step 809: The backup data gateway advertises a routing network segment to the service gateway. The routing network segment information is determined by the IP address of the migrated user terminal. When the migrated user IP address belongs to the same address segment or the same subnet When the routing information of the network segment or subnet is changed, the next hop data gateway address in the routing information of the network segment is changed from the source data gateway to the target data gateway, so that the target data gateway and the packet data network are established. connection.

If the subscription data of the user allows interworking with the non-3GPP, the backup data gateway address and the corresponding APN information may be further registered by the mobility management network element into the HSS. The message carries the APN and backup data gateway address used by the user; the HSS saves the APN and target data gateway address information used by the user and returns an update response message to the mobility management network element.

The above describes the process when the backup data gateway does not need to perform load migration. When the backup data gateway needs to perform load migration, B'J:

In step 802, the gateway management network element selects a target data gateway for the backup data network element. After step 803, the method further includes:

The gateway management network element carries the target data gateway identifier in the status information feedback message and sends the identifier to the backup data gateway.

The backup data gateway sends the user context data to the target data gateway, where the backup context data is sent to the target data gateway, or the backup data gateway carries the user context data in the user context delivery request and sends the data to the target data gateway;

Thereafter, steps 804-809 are performed by the target data gateway in place of the backup data gateway.

In this embodiment, when the primary data gateway fails, the backup data gateway takes over the service, and the security of the user data and the stability of the service can be ensured. In this embodiment, the target data gateway is migrated after the backup data gateway is overloaded. , can achieve the balance of system resources.

FIG. 9 is a schematic structural diagram of a device according to a fifth embodiment of the present invention, including a receiving module 91, a target gateway selecting module 92, and a target gateway sending module 93. The receiving module 91 is configured to receive status information sent by the data gateway when the data gateway is normal. The status information reporting message carries the status information; the target gateway selecting module 92 is configured to: when determining the data gateway that needs to be load balanced, select the target data gateway according to the status information, and select the target data gateway, the source data. Gateway is needed a data gateway that performs load balancing; the target gateway sending module 93 is configured to send the status information of the target data gateway to the source data network element, so that the source data gateway performs part of the user service according to the status information of the target data gateway. Migrating from the source data gateway to the target data gateway.

On the other hand, the backup gateway selection module 94 and the backup gateway sending module 95 may be further included; the backup gateway selection module 94 is configured to select a backup data gateway for the primary data gateway according to the status information when determining the data gateway that needs to be backed up. The primary data gateway is a data gateway that needs to be backed up; the backup gateway sending module 95 is configured to send status information of the backup data gateway to the primary data gateway, so that the primary data gateway is based on the status of the backup data gateway. Information, synchronizing user context data into the backup data gateway.

On the other hand, the fault gateway determining module 96 and the fault gateway sending module 97 may be further included; the fault gateway determining module 96 is configured to determine a backup data gateway of the faulty data gateway when the data gateway fails; the fault gateway sending module 97 is used to When the backup data gateway is normal and does not need to perform load migration, the faulty data gateway identifier is sent to the backup data gateway, so that the backup data gateway takes over the user service corresponding to the faulty data gateway.

In this embodiment, the security of the user data and the stability of the service can be improved by performing real-time backup. Load migration can balance the load of each data gateway and improve system resource utilization. In this embodiment, when the primary data gateway fails, the backup data gateway takes over the service, and the security of the user data and the stability of the service can be ensured.

10 is a schematic structural diagram of a system according to a sixth embodiment of the present invention, including a gateway management network element 101 and a source data gateway 102. The gateway management network element 101 is configured to receive a status information report message sent by the data gateway when the data gateway is normal. When the status information report message carries the status information, and determines the data gateway that needs to perform the load migration, select the target data gateway for the source data gateway according to the status information, where the source data gateway is a data gateway that needs to perform load balancing; The source data gateway 102 is configured to migrate part of user services from the source data gateway to the target data gateway according to status information of the target data gateway.

On the other hand, the gateway management network element 101 is further configured to determine data that needs to be backed up. At the gateway, the backup data gateway is selected as the primary data gateway according to the status information, and the primary data gateway is a data gateway that needs to be backed up; the system further includes: a primary data gateway 103, and the primary data gateway 103 is configured to use the Backing up the status information of the data gateway, synchronizing user context data into the backup data gateway.

On the other hand, the gateway management network element 101 is further configured to: when the data gateway fails, determine a backup data gateway of the faulty data gateway, and send the faulty data gateway identifier when the backup data gateway is normal and does not need to perform load migration. The backup data gateway is configured to: the backup data gateway 104 is configured to take over the user service corresponding to the faulty data gateway.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing storage medium includes: ROM, RAM, magnetic disk or optical disk, and the like, which can store various program codes. Finally, the above embodiments are only used to illustrate the technical solution of the present invention. The invention is described in detail with reference to the foregoing embodiments, and those of ordinary skill in the art should understand that the technical solutions described in the foregoing embodiments may be modified or some of the techniques may be The features are equivalent to the equivalents; and the modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

1. A data gateway load processing method, which is characterized by:

2. The method according to claim 1, further comprising:

When the data gateway that needs to be backed up is determined, the gateway management network element selects a backup data gateway according to the status information, and the primary data gateway is a data gateway that needs to be backed up;

The gateway management network element sends the status information of the backup data gateway to the primary data gateway, so that the primary data gateway synchronizes the user context data to the backup data gateway according to the status information of the backup data gateway.

3. The method according to claim 1, further comprising:

When the data gateway fails, the gateway management network element determines the backup data gateway of the faulty data gateway; when the backup data gateway is normal and does not need to perform load migration, the gateway management network element sends the faulty data gateway identifier to the backup data gateway. And causing the backup data gateway to take over the user service corresponding to the faulty data gateway.

The method according to claim 1, wherein the status information includes a load weight parameter, and the determining the data gateway that needs to perform load balancing comprises:

When the load weight parameter in the status information sent by the data gateway is less than or equal to a preset weight threshold, the data gateway is determined to be a data gateway that needs to perform load balancing.

The method according to claim 4, wherein the status information further includes an address pool space and a reachable APN list, and the gateway management network element selects a target data gateway for the source data gateway according to the status information, Includes:

When the source data gateway has a backup data gateway and the backup data gateway does not need to perform load migration, the backup data gateway with a large load weight parameter is preferentially selected as the target data gateway;

When the source data gateway does not have a backup data gateway or the backup data gateway needs to perform load migration, the data gateway with the load weight parameter is preferentially selected as the target data gateway in the data gateway having the coincidence address pool space with the source data gateway;

When the load weight parameters of the two data gateways are the same, the data gateway having the similar APN list with a similar degree to the source data gateway is preferentially selected as the target data gateway;

When the APN list is also the same, the data gateway is randomly selected as the target data gateway.

The method according to claim 1, wherein the source data gateway migrates part of the user service from the source data gateway to the target data gateway according to the status information of the target data gateway, including:

The source data gateway receives the state information of the target data gateway sent by the gateway management network element; the source data gateway selects the migrated user according to the state information of the target data gateway and selects the target data gateway for the migrated user;

The source data gateway notifies the target data gateway corresponding to the migrated user to take over the user service of the migrated user.

The method according to claim 6, wherein the source data gateway selects a target data gateway for the migrated user, including:

The backup data gateway where the user context data of the migrated user is located is preferentially selected as the target data gateway of the migrated user;

When the backup data gateway of the migrated user is unavailable, the data gateway with the load weight parameter is preferentially selected as the target data gateway of the migrated user in the data gateway where the address pool space includes the IP address of the migrated user.

The method according to claim 6, wherein the source data gateway notifies the target data gateway corresponding to the migrated user to take over the user service of the migrated user, including:

When the target data gateway is the backup data gateway of the migrated user, the source data gateway sends an invite message to the backup data gateway, where the migrated user identifier is carried, so that the backup data gateway will be the user context data corresponding to the migrated user identifier. Transfer to primary user data and allocate resources to primary user data;

When the target data gateway is not the backup data gateway of the migrated user, the source data gateway sends the user context data of the migrated user to the target data gateway, so that the target data gateway saves the user context data of the migrated user as the main user data, and Allocate resources for the primary user data.

The method according to claim 8, wherein when the target data gateway is not a backup data gateway, the method further includes:

The source data gateway sends a delete message to the backup data gateway corresponding to the migrated user. The delete message carries the migrated user identifier, so that the backup data gateway deletes the user context data corresponding to the migrated user identifier after receiving the delete message.

The method according to claim 2, wherein the determining the data gateway that needs to be backed up comprises:

When the data gateway does not have a backup data gateway or the backup data gateway fails, it is determined that the data gateway is a data gateway that needs to be backed up.

The method according to claim 2, wherein the status information includes a load weight parameter, an address pool space, and a reachable APN list, and the gateway management network element selects a backup for the primary data gateway according to the status information. Data gateway, including:

The gateway management network element preferentially selects a data gateway with a large load weight parameter in a data gateway having a coincidence address pool space with the primary data gateway;

When the load weight parameters are the same, the data gateway having the similarity to the APN list with a similar degree to the primary data gateway is preferentially selected;

When the reachable APN list is the same, it is randomly selected.

The method according to claim 11, wherein the primary data gateway synchronizes the user context data to the backup data gateway according to the status information of the backup data gateway, including:

The primary data gateway receives the status information of the backup data gateway sent by the gateway management network element; the primary data gateway selects the backup data gateway for the backup user according to the status information of the backup data gateway;

The primary data gateway sends the user context data of the backup user to the corresponding backup data gateway, so that the backup data gateway saves the user context data as the backup user data.

The method according to claim 12, wherein the primary data gateway selects the backup data gateway for the backed up user according to the status information of the backup data gateway, including:

In the data gateway where the address pool space contains the IP address of the user being backed up, the data gateway with a large load weight parameter is preferentially selected.

14. The method according to claim 3, wherein the data gateway is faulty, comprising:

When the status information report message sent by the data gateway is not received within the preset time threshold, the gateway management network element determines that the data gateway is a fault data gateway.

15. A data gateway load processing device, comprising:

The device according to claim 15, further comprising: a backup gateway selection module, configured to: when determining a data gateway that needs to be backed up, select a backup data gateway according to the status information, and the primary data gateway is a data gateway that needs to be backed up;

a backup gateway sending module, configured to send status information of the backup data gateway to the primary data gateway, so that the primary data gateway synchronizes user context data to the backup data gateway according to status information of the backup data gateway .

The device according to claim 15, further comprising:

a fault gateway determining module, configured to determine a backup data gateway of the faulty data gateway when the data gateway fails;

a faulty gateway sending module, configured to: when the backup data gateway is normal and does not need to perform load migration, send the faulty data gateway identifier to the backup data gateway, so that the backup data gateway takes over the user corresponding to the faulty data gateway business.

18. A data gateway load processing system, comprising:

The gateway management network element is configured to: when the data gateway is normal, receive a status information report message sent by the data gateway, where the status information report message carries status information, and determines a data gateway that needs to be load balanced, according to the status The information is a source data gateway for selecting a target data gateway, where the source data gateway is a data gateway that needs to perform load balancing;

19. The system of claim 18, wherein:

When the gateway management network element is further configured to determine a data gateway that needs to be backed up, select a backup data gateway according to the status information, and the primary data gateway is a data gateway that needs to be backed up;

The system also includes:

And a primary data gateway, configured to synchronize user context data to the backup data gateway according to status information of the backup data gateway.

20. The system of claim 18, wherein

The gateway management network element is further configured to: when the data gateway is faulty, determine a backup data gateway of the faulty data gateway, and send the faulty data gateway identifier to the backup data when the backup data gateway is normal and does not need to perform load migration. Gateway

The system also includes:

The backup data gateway is configured to take over the user service corresponding to the faulty data gateway.