WO2011150564A1 - 数据网关负载处理方法、设备及系统 - Google Patents
数据网关负载处理方法、设备及系统 Download PDFInfo
- Publication number
- WO2011150564A1 WO2011150564A1 PCT/CN2010/073475 CN2010073475W WO2011150564A1 WO 2011150564 A1 WO2011150564 A1 WO 2011150564A1 CN 2010073475 W CN2010073475 W CN 2010073475W WO 2011150564 A1 WO2011150564 A1 WO 2011150564A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data gateway
- gateway
- backup
- user
- data
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/088—Load balancing or load distribution among core entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- the present invention relates to mobile communication technologies, and in particular, to a data gateway load processing method, device and system. Background technique
- 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).
- ⁇ Mobility Management Entity
- SGW Serving Gateway
- PGW Data Gateway
- 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.
- 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.
- the IP address of the user terminal should remain unchanged.
- 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:
- the gateway management network element 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;
- 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;
- 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.
- 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.
- FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.
- FIG. 2 is a schematic flow chart of a method according to a first embodiment of the present invention.
- FIG. 3 is a schematic diagram of data storage in an embodiment of the present invention.
- FIG. 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
- FIG. 8 is a schematic flow chart of a method according to a fourth embodiment of the present invention.
- FIG. 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.
- 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.
- 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.
- GPRS General Packet Radio Service
- GGSN Gateway General Packet Radio Service
- PDSN Packet Data Serving Node
- ASN-GW Access Service Network Gateway
- PGW Packet Data Gateway
- 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.
- PGW-1 and PGW-2 may have the same address pool space IP VI
- PGW-2 and PGW-3 may also have the same address pool space IP V2, and the rest are similar.
- 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.
- 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.
- the load weight parameter is obtained as zero.
- 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.
- the load weight parameter is 0.
- 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.
- 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;
- the data gateway 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;
- 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.
- the motherboard fails, enable the standby board to replace the motherboard to provide services for users.
- 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.
- another data gateway is selected as the backup data gateway.
- 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.
- FIG. 3 is a schematic diagram of data storage in an embodiment of the present invention.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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;
- the data gateway 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;
- 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. .
- 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.
- the target data gateway can be selected as follows:
- 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;
- 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;
- 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 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 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.
- 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
- 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.
- 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.
- 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).
- SGSN Serving GPRS Support Node
- EUTRAN UMTS Universal Mobile Telecommunications System
- 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).
- HSS Home Subscriber Server
- 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.
- TEID SGW user plane tunnel end identifier
- 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.
- PCRF Policy and Charging Rule Function
- 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.
- PCC Policy Control and Charging
- 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 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.
- 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.
- the backup data can be separately saved, which can reduce the burden on the data gateway and improve system resource utilization.
- 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 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.
- 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.
- 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.
- the data gateway is the primary data gateway.
- 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;
- the data gateway is the source data gateway.
- 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.
- the data gateway information carried in the status information feedback message is used as the information of the backup data gateway.
- 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.
- step 23 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.
- 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.
- GTP GPRS Tunneling Protocol
- Step 703 The target data gateway updates the control session with the PCRF.
- the PCRF updates the policy control information under the migrated user source data gateway to the policy control information under the target data gateway.
- 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.
- 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.
- 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.
- 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 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.
- 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.
- 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.
- 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.
- the backup 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.
- step 702 can be similar.
- Step 805 The backup data gateway updates the control session with the PCRF.
- 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.
- the migrated user IP address belongs to the same address segment or the same subnet
- 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.
- 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.
- step 802 the gateway management network element selects a target data gateway for the backup data network element.
- 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;
- steps 804-809 are performed by the target data gateway in place of the backup data gateway.
- the backup data gateway takes over the service, and the security of the user data and the stability of the service can be ensured.
- 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.
- 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.
- 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.
- 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.
- 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 backup data gateway takes over the service, and the security of the user data and the stability of the service can be ensured.
- 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.
- 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.
- the gateway management network element 101 is further configured to determine data that needs to be backed up.
- 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.
- 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.
- the backup data gateway takes over the service, and the security of the user data and the stability of the service can be ensured.
- the target data gateway is migrated after the backup data gateway is overloaded. , can achieve the balance of system resources.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
数据网关负载处理方法、 设备及系统
技术领域
本发明涉及移动通信技术, 尤其涉及一种数据网关负载处理方法、 设备 及系统。 背景技术
在下一代移动通信网络中, 用户终端通过本地无线接入网络连接到核心 网络中, 并通过核心网络访问才艮文数据网络( Packet Data Network , PDN )。 核心网络包括移动管理网元( Mobility Management Entity , ΜΜΕ )、 服务网关 ( Serving Gateway, SGW )和数据网关(PDN Gateway, PGW )等设备。 其 中, PGW主要负责用户终端与其访问的 PDN之间的数据转发与连接管理工 作, 同时也是用户终端移动过程中的服务锚点。
用户终端接入核心网络后 , 由 MME基于用户终端所访问的 PDN为其选 择合适的 PGW,并由 SGW根据 MME发送的 PGW地址连接到指定的 PGW。
PGW为用户终端分配连接的 IP地址, 使得用户终端可以使用此 IP地址和其 访问的 PDN网络进行通信。当用户终端移动时,为了保持用户业务的连续性, 用户终端的 IP地址应保持不变。
目前, 随着用户终端数目的不断增加, 业务类型的不断丰富, PGW的负 担越来越重。 尤其在 MME选择 PGW时, 即便有多个 PGW可选, 也会由于 各 PGW的备选权重基本保持不变, 造成某些权重较大的 PGW负载较高, 而 权重较小的 PGW负载相对较轻的结果。 因此, 为了充分利用现有设备资源, 需要在各 PGW之间进行负载迁移处理。 此外, 当某些数据网关出现故障或 需升级维护时同样面临负载迁移的需求。
在实现本发明过程中, 发明人发现现有技术至少存在如下问题: 现有技 术中, 没有相关方案可以发现并处理数据网关的过载。
发明内容
本发明实施例是提供一种数据网关负载处理方法、 设备及系统, 实现数 据网关间的过载处理。
本发明实施例提供了一种数据网关负载处理方法, 包括:
当数据网关正常时, 网关管理网元接收数据网关发送的状态信息上报消 息 , 所述状态信息上报消息中携带状态信息;
当确定出需要进行负载均衡的数据网关时, 网关管理网元根据所述状态 信息为源数据网关选择目标数据网关, 所述源数据网关为需要进行负载均衡 的数据网关;
网关管理网元将目标数据网关的状态信息发送给所述源数据网元, 使得 所述源数据网关根据所述目标数据网关的状态信息, 将部分用户业务由所述 源数据网关迁移到所述目标数据网关。
本发明实施例提供一种数据网关负载处理设备, 包括:
接收模块, 用于当数据网关正常时, 接收数据网关发送的状态信息上报 消息 , 所述状态信息上报消息中携带状态信息;
目标网关选择模块, 用于当确定出需要进行负载均衡的数据网关时, 根 据所述状态信息为源数据网关选择目标数据网关, 所述源数据网关为需要进 行负载均衡的数据网关;
目标网关发送模块, 用于将目标数据网关的状态信息发送给所述源数据 网元, 使得所述源数据网关根据所述目标数据网关的状态信息, 将部分用户 业务由所述源数据网关迁移到所述目标数据网关。
本发明实施例提供一种数据网关负载处理系统, 包括:
网关管理网元, 用于当数据网关正常时, 接收数据网关发送的状态信息 上报消息, 所述状态信息上报消息中携带状态信息, 并确定出需要进行负载 均衡的数据网关时, 根据所述状态信息为源数据网关选择目标数据网关, 所
述源数据网关为需要进行负载均衡的数据网关;
源数据网关, 用于根据所述目标数据网关的状态信息, 将部分用户业务 由所述源数据网关迁移到所述目标数据网关。
由上述技术方案可知, 本发明实施例通过为源数据网关选择目标数据网 关, 实现了数据网关间的负载均衡, 实现了数据网关间的过载处理。 附图说明
为了更清楚地说明本发明实施例中的技术方案, 下面将对实施例描述中 所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图是本发明 的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前 提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例的网络架构示意图;
图 2为本发明第一实施例的方法流程示意图;
图 3为本发明实施例中数据存储示意图;
图 4为本发明第二实施例的方法流程示意图;
图 5为本发明实施例中主数据网关获取用户上下文数据的方法流程示意 图;
图 6为本发明第三实施例的方法流程示意图;
图 Ί为本发明实施例中源数据网关向目标数据网关进行负载迁移的方法 流程示意图;
图 8为本发明第四实施例的方法流程示意图;
图 9为本发明第五实施例的设备结构示意图;
图 10为本发明第六实施例的系统结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发 明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于 本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获 得的所有其他实施例, 都属于本发明保护的范围。
为了更好地理解本发明实施例, 首先对本发明实施例的网络架构进行描 述。
图 1为本发明实施例的网络架构示意图, 包括 MME 11、 SGW 12、 数据 网关 (图中以 PGW为例 ) 13和网关管理网元 14。 本发明实施例的数据网关 以 PGW 为例, 可以理解的是, 数据网关还可以是网关通用分组无线业务 ( General Packet Radio Service, GPRS ) 支持节点 ( Gateway GPRS Support, GGSN ) 、 分组数据服务节点 (Packet Data Serving Node, PDSN ) 、 接入服 务网网关( Access Service Network Gateway, ASN-GW )、分组数据网关( Packet Data Gateway, PDG )等。
每个网关管理网元 14 (图 1中以 1个网关管理网元为例 )与多个数据网 关 13 (图 1中以 PGW-1 、 PGW-2...PGW-n 为例)相连, 组成数据网关资源 池(以下简称资源池) 。 每个数据网关负责多个地址池空间, 不同的数据网 关可能存在相同的地址池。 例如, PGW-1与 PGW-2可能存在相同的一段地 址池空间 IP VI , 同时 PGW-2与 PGW-3也可能存在一段相同的地址池空间 IP V2, 其余类似。 当数据网关 13正常时, 会上报自身的状态信息给网关管 理网元 14, 状态信息可以包括数据网关标识(例如数据网关的 IP地址)、 数 据网关负责的地址池空间、 可达接入点名称 (Access Point Name, APN ) 列 表及负载权重参数等。 其中, 负载权重参数可以基于数据网关 13 自身能力与 当前负载情况确定, 例如, 对于自身负载能力较高而目前负载较低的数据网 关, 负载权重参数较大, 反之, 对于将要达到负载极限的数据网关, 负载权 重参数较小, 换而言之, 自身负载能力较高而目前负载较低的数据网关, 其
负载权重参数大于负载能力较低而目前负载较高的数据网关的负载权重参 数。 当数据网关 13过载时, 得到负载权重参数为 0。 具体地, 可以在数据网 关 13 中预先设置一个映射表, 该映射表表明目前负载与自身负载能力的比 值, 与负载权重参数的对应关系, 数据网关 13根据当前的负载情况与自身负 载能力计算得到该比值, 之后, 在该映射表中找到对应的负载权重参数。 其 中, 该映射表中的该比值与负载权重参数成反比, 即该比值越大, 该负载权 重参数越小, 当该比值大于 1时, 该负载权重参数为 0。
本发明实施例中, 采用实时备份机制, 即主数据网关在接收到数据后, 会将接收的数据备份到备份数据网关中; 之后, 在负载迁移时, 选择备份数 据网关作为源数据网关的目标数据网关。 其中, 需要进行备份的数据网关为 主数据网关, 数据被备份到的数据网关称为备份数据网关; 需要进行负载迁 移的数据网关为源数据网关, 数据被迁移到的数据网关称为目标数据网关。
图 2为本发明第一实施例的方法流程示意图,本实施例对应于备份流程。 参见图 2, 包括:
步骤 21 : 当数据网关正常时, 网关管理网元接收数据网关发送的状态信 息上报消息 , 所述状态信息上报消息中携带状态信息;
例如,当数据网关正常时,数据网关会在接收到网关管理网元发送的 ping 信令后, 或者, 在数据网关设置的定时器超时后, 发送状态信息上报消息给 网关管理网元, 该状态信息上报消息中携带状态信息, 该状态信息可以包括 数据网关标识、 负载权重参数、 地址池空间、 可达 APN列表等。
步骤 22: 当确定出需要进行备份的数据网关时, 网关管理网元根据所述 状态信息为主数据网关选择备份数据网关, 所述主数据网关为需要进行备份 的数据网关;
现有技术中在进行备份时是采用设备内部用户数据实时备份方案, 即数 据网关中主板上的用户数据全部实时存储到备板中。 当主板故障时, 启用备 板代替主板为用户提供服务。 但是, 由于主板和备板处于同一个设备中, 当
整个设备故障时, 仍会出现用户数据丟失、 业务中断等状况。
而本实施例是选择另外的数据网关作为备份数据网关。
另外, 本实施例可以不设置专门的备份数据网关, 而是将数据网关中的 用户上下文数据分为主用户数据和备用户数据。 数据网关为主用户数据分配 资源, 负责主用户终端与其访问的 PDN之间的数据转发与连接管理工作。 数 据网关不为备用户数据分配资源, 只起到存储备用户数据的作用。
进一步地, 为了减轻数据网关的负担, 可以将主用户数据分为若干份, 分别存储到不同的备份数据网关。 例如, 图 3为本发明实施例中数据存储示 意图, 参见图 3 , 以一个主数据网关拥有两个备份数据网关为例, 数据网关 -1 与数据网关 -3为数据网关 -2的备份数据网关, 数据网关 -2的用户数据包括主 用户数据和备份用户数据, 举例来说, 主用户可以分为 2份, 主用户数据 -1 和主用户数据 -2, 其中, 主用户数据 -1存储到数据网关 -1 中, 作为数据网关 -1的备份数据; 主用户数据 -2存储到数据网关 -3中, 作为数据网关 -3的备份 数据。 在本实施例中, 数据网关 -2也可以作为数据网关 -1和数据网关 -3的一 个备份数据网关, 数据网关 -1或数据网关 -3的主用户数据备份方式与数据网 关 -2相同。
备份数据网关的选择策略可以如下: 网关管理网元将所有与主数据网关 具有重合地址池空间的数据网关设备按照负载权重参数由大到小排序, 如果 两个数据网关的负载权重参数相同,则比较可达 APN列表与主数据网关的相 似度, 相似度高的数据网关优先选择, 如果可达 APN列表仍然相同, 则随机 确定先后顺序。 由于备份数据可以分别存储, 因此, 备份数据网关可以为 N 个, N大于等于 1。
步骤 23: 网关管理网元将备份数据网关的状态信息发送给所述主数据网 关, 使得所述主数据网关根据所述备份数据网关的状态信息, 将用户上下文 数据同步到所述备份数据网关中。
一方面, 主数据网关可以采用如下的方式为不同的用户上下文数据选择
对应的备份数据网关: 主数据网关根据主数据网关负责的地址池空间及负载 权重参数, 及网关管理网元发送的备份数据网关的状态信息, 选择备份数据 网关。 例如, 对应于一用户终端, 主数据网关为该用户终端分配的 IP地址为
IP-1 , 则首先选择地址池空间包含 IP-1 的数据网关, 之后, 在满足地址池空 间包含 IP-1的数据网关中, 优先选择负载权重参数大的数据网关作为备份数 据网关。 之后, 在主数据网关中保存用户上下文数据与备份数据网关的关联 关系。
另一方面, 主数据网关可以采用如下方式进行同步: 例如, 可以设置同 步定时器, 当同步定时器超时后, 主数据网关发送用户上下文同步请求到备 份数据网关, 备份数据网关接收用户上下文同步请求后, 接收主数据网关发 送的用户上下文数据; 或者, 主数据网关将用户上下文数据携带在用户上下 文同步请求中发送给备份数据网关。 其中, 用户上下文数据可以是主数据网 关新建的用户上下文数据, 也可以是更新后的用户上下文数据。
上述描述了用户上下文数据从主数据网关同步到备份数据网关的流程, 而主数据网关可以采用如下的方式获取用户上下文数据。
本实施例通过将数据备份到另外的数据网关中, 可以避免数据备份到同 一数据网关中, 而该数据网关出现故障时的数据丟失问题; 本实施例通过实 时备份, 可以为后续负载迁移提供基础。
图 4为本发明第二实施例的方法流程示意图, 本实施例对应负载迁移流 程。 参见图 4, 本实施例包括:
步骤 41 : 当数据网关正常时, 网关管理网元接收数据网关发送的状态信 息上报消息 , 所述状态信息上报消息中携带状态信息;
例如,当数据网关正常时,数据网关会在接收到网关管理网元发送的 ping 信令后, 或者, 在数据网关设置的定时器超时后, 发送状态信息上报消息给 网关管理网元, 该状态信息上报消息中携带状态信息, 该状态信息可以包括 数据网关标识、 负载权重参数、 地址池空间、 可达 APN列表。
步骤 42: 当确定出需要进行负载均衡的数据网关时, 网关管理网元根据 所述状态信息为源数据网关选择目标数据网关, 所述源数据网关为需要进行 负载均衡的数据网关;
具体地, 可以采用如下的方式判断是否存在需要进行负载均衡的数据网 关: 对应于各数据网关, 可以设置权重阈值, 不同的数据网关之间可以设置 相同的权重阈值, 也可以设置不同的权重阈值。 当数据网关上报的状态信息 中的负载权重参数小于等于该权重阈值时, 表明需要进行负载均衡。
另一方面, 可以采用如下方式选择目标数据网关:
方式一, 当源数据网关存在备份数据网关时, 网关管理网元将源数据网 关的备份数据网关按照负载权重参数由大到小排序, 优先选择负载权重参数 大的备份数据网关作为目标数据网关;
方式二, 如果源数据网关的备份数据网关的负载权重参数都很小, 则选 择与源数据网关具有重合地址池空间且负载权重参数较高的数据网关作为目 标数据网关;
特别地,当两个目标数据网关的负载权重参数相同,则可以比较可达 APN 列表, 优先选择具有与源数据网关的可达 APN 列表相似度高的目标数据网 关;
当可达 APN列表仍然相同, 则可以随机选择。
步骤 43: 网关管理网元将目标数据网关的状态信息发送给所述源数据网 关, 使得所述源数据网关根据所述目标数据网关的状态信息, 将部分用户业 务由所述源数据网关迁移到所述目标数据网关。
其中, 可以是, 源数据网关接收网关管理网元发送的目标数据网关的状 态信息; 源数据网关根据所述目标数据网关的状态信息选择被迁移用户及为 被迁移用户选择目标数据网关; 源数据网关通知与被迁移用户对应的目标数 据网关接管被迁移用户的用户业务。
具体地, 当目标数据网关为被迁移用户的备份数据网关时, 源数据网关
向所述备份数据网关发送 invite 消息, 其中携带被迁移用户标识, 以便所述 为主用户数据分配资源; 当目标数据网关不是被迁移用户的备份数据网关时, 数据网关将被迁移用户的用户上下文数据保存为主用户数据, 并为主用户数 据分配资源。
本实施例通过为源数据网关选择目标数据网关,可以在需要负载迁移时 , 将用户上下文数据从源数据网关迁移到目标数据网关, 实现负载均衡, 或者 出现故障或升级维护时保证业务不中断。
图 5为本发明实施例中主数据网关获取用户上下文数据的方法流程示意 图, 包括:
步骤 501 : 用户终端发送附着请求消息到移动性管理网元。
其中, 针对无线接入网或通用陆地无线接入网( GERAN/UTRAN )而言, 所述移动性管理网元为服务 GPRS支持节点 (Serving GPRS Support Node, SGSN ); 针对演进的用移动通信系统( UMTS )无线接入网 ( UMTS Universal Mobile Telecommunications System , EUTRAN )网络而言, 移动性管理网元为 MME ( Mobility Management Entity, 移动管理实体)。
步骤 502 : 用户终端与移动性管理网元和归属网络服务器 (Home Subscriber Server, HSS )执行鉴权认证操作。
步骤 503: 移动性管理网关与 HSS之间执行位置更新与用户签约数据插 入流程。其中包括移动性管理网元地址注册到 HSS中, 同时 HSS将用户签约 数据下发给移动性管理网元存储。
步骤 504: 移动性管理网元向 SGW发送创建缺省承载请求, 其中携带主 数据网关标识, 例如主数据网关的 IP地址。
其中,移动性管理网元根据用户终端发送的 APN信息或用户签约数据中 携带的缺省 APN信息选择主数据网关; 并根据用户位置信息选择 SGW。
步骤 505: SGW在演进分组系统 ( Evolved Packet System, EPS )承载表 中为所述用户新建上下文, 并根据移动管理网元发送的创建缺省承载请求中 的主数据网关标识向主数据网关发送创建缺省承载请求, 所述 SGW发送的 创建缺省承载请求中携带 SGW地址、 SGW用户面隧道端点标识 (Tunnel Endpoint Identifier, TEID )和 SGW控制面 TEID等信息。
步骤 506: 如果采用动态策略生成机制, 主数据网关与策略和计费规则 功能实体(Policy and Charging Rule Function, PCRF )交互, 执行策略控制操 作。
例如, PCRF下发策略控制和计费 (Policy Control and Charging, PCC ) 规则给主数据网关, 其中包括承载的 QoS, 例如带宽、 延时、 丟包率、 服务 类型 (Type of Service, ToS )、 区分服务编码点 ( Differentiated Services Code Point, DSCP )、 服务质量类标识( QoS Class Identifier, QCI )等; 计费规则 包括与数据连接所传输的业务数据流对应的计费信息, 例如, 按时长计费值、 按流量计费值、 按次计费值等。
之后, 主数据网关为附着用户创建用户上下文。
用户上下文包括用户标识、 承载上下文信息、 PCC会话上下文、 计费信 息、 已分配用户 IP 信息。 其中用户标识, 可以是国际移动用户标识 ( International Mobile Subscriber Identity, IMSI )、 网络接入标口、 ( Network Access Identifier, NAI )或移动站国际 ISDN号码 ( Mobile Station International ISDN Number, MSISDN )等; 承载上下文信息包括 SGW控制面与用户面地 址及 TEID、 EPS承载标识( bearer ID ); 已分配用户 IP信息包括用户终端 IP 地址、 IP地址属性和 IP地址租期 , 当数据网关作为 DHCP client或 /和 DHCP server时,用户终端的 IP地址信息也包括 DHCP维护的 IP地址及配置信息等。
步骤 507: 主数据网关向 SGW返回创建缺省承载响应。
该缺省承载响应中携带主数据网关用户面与控制面地址与 TEID、 EPS bearer ID等信息。
步骤 508: SGW返回创建缺省承载响应给移动性管理网元, 所述 SGW 发送的创建缺省承载响应消息中携带 SGW地址、用户面与控制面 TEID及主 数据网关信息。
步骤 509:移动性管理网元根据 SGW发送的创建缺省承载响应获取主数 据网关信息, 并发送附着接受消息给用户终端。
如果用户的签约数据允许跟非 3GPP互通, 则进一步完成主数据网关地 址与对应 APN关联并注册到 HSS的流程。 即进一步包括:
步骤 510: 移动性管理网元向 HSS发送更新数据网关地址, 其中携带用 户终端使用的 APN及主数据网关地址。
步骤 511 : HSS对应保存用户终端使用的 APN和主数据网关地址, 并 返回更新响应到移动性管理网元。
本实施例的实时备份流程,可以将主数据网关创建或更新的用户上下文 数据同步到备份数据网关, 避免主数据网关故障时数据丟失或业务中断的问 题, 提高了用户数据的安全性与业务的稳定性。 本实施例并没有设置专门的 备份数据网关, 可以节省成本。 本实施例可以将备份数据分别保存, 可以降 低数据网关的负担, 提升系统资源利用率。
上述分别描述了负载均衡和实时备份的流程, 在具体实施时, 可以将负 载均衡和实时备份结合。
图 6为本发明第三实施例的方法流程示意图, 本实施例对应负载均衡和 实时备份结合的流程。 参见图 6, 本实施例包括:
步骤 601 : 网关管理网元向各数据网关发送 ping信令。
步骤 602: 如果数据网关正常, 数据网关向网关管理网元发送状态信息 上才艮消息。
该状态信息上报消息中携带数据网关的状态信息, 状态信息包括负载权 重参数, 数据网关标识、 数据网关负责的地址池空间、 可达 APN列表。
上述是通过网关管理网元发送 ping信令使数据网关发送状态信息上报消
息, 也可以是在数据网关中设置定时器, 在该定时器超时后, 数据网关主动 向网关管理网元发送状态信息上报消息。
步骤 603: 网关管理网元根据状态信息上报消息对数据网关进行过载风 险判断。
当存在过载风险时, 表明数据网关需要进行负载均衡。 当不存在过载风 险时, 若数据网关不存在备份数据网关或者数据网关的备份数据网关出现故 障, 则表明数据网关需要进行实时备份。
其中, 可以通过在网关管理网元中设置负载权重阈值, 当数据网关发送 的状态信息中的负载权重参数小于等于该负载权重阈值时, 表明存在过载风 险; 当负载权重参数大于该负载权重阈值时, 表明不存在过载风险。
其中, 网关管理网元中会保存各数据网关的信息, 所以可以获知数据网 关是否存在备份数据网关, 或者, 当数据网关存在备份数据网关时, 该备份 数据网关是否出现故障。
其中, 网关管理网元可以根据过载风险判断结果, 确定是进行负载均衡, 还是进行实时备份, 当确定进行负载均衡后, 该发送状态信息上报消息的数 据网关为源数据网关; 当确定进行实时备份后, 该发送状态信息上报消息的 数据网关为主数据网关。
步骤 604: 网关管理网元向主 /源数据网关发送状态信息反馈消息。
在过载风险判断后, 当数据网关需要进行实时备份时, 该数据网关为主 数据网关, 此时, 网关管理网元为主数据网关选择备份数据网关, 之后, 将 备份数据网关的信息携带在状态信息反馈消息中发送给主数据网关;
在过载风险判断后, 当数据网关需要进行负载均衡时, 该数据网关为源 数据网关, 此时, 网关管理网元为源数据网关选择目标数据网关, 之后, 将 目标数据网关的信息携带在状态信息反馈消息中发送给源数据网关。
步骤 605: 主 /源数据网关接收到状态信息反馈消息后, 判断进行实时备 份或者负载均衡, 当进行实时备份时, 执行步骤 606, 当进行负载均衡时,
执行步骤 607。
其中,数据网关可以结合自身的状态判断是进行实时备份还是负载均衡, 例如, 数据网关自身设置负载权重阈值, 当负载权重参数小于等于该负载权 重阈值时, 表明需要进行负载均衡, 当负载权重参数大于该负载权重阈值时, 表明需要进行实时备份。
当自身需要进行实时备份时, 将该状态信息反馈消息中携带的数据网关 信息作为备份数据网关的信息; 当自身需要进行负载均衡时, 将状态信息反 馈消息中携带的数据网关信息作为目标数据网关的信息。
步骤 606: 主数据网关与备份数据网关进行实时备份。
具体流程可以参见步骤 23。
步骤 607: 源数据网关判断目标数据网关是否为备份数据网关, 之后, 根据目标数据网关是否为备份数据网关执行对应的负载迁移操作。
图 Ί为本发明实施例中源数据网关向目标数据网关进行负载迁移的方法 流程示意图, 本实施例以目标数据网关为源数据网关的备份数据网关为例。 参见图 7 , 包括:
步骤 701 : 源数据网关向目标数据网关发送邀请 ( invite ) 消息, 该消息 中包含被迁移的用户标识, 该用户标识可以为 IMSI、 NAI、 MSISDN等。 为 文数据与备份数据网关的对应关系为迁移用户选择目标数据网关。
目标数据网关根据 Invite消息中携带的被迁移用户标识将对应的备用户 数据状态变为主用户数据, 以便接管这部分用户业务。 其中, 主用户数据对 应的备用户数据将由目标数据网关在备份数据同步流程中发送给其备份数据 网关。 步骤 702: 目标数据网关发送更新连接隧道请求给 SGW, 请求更新连接 隧道。
其中, 目标数据网关根据用户上下文数据获得 SGW地址, 根据 SGW地
址向接入点发送更新连接隧道请求。
SGW根据更新连接隧道请求消息, 更新与数据网关之间的连接隧道, 即 建立与目标数据网关之间的连接隧道。 具体的更新过程随隧道协议的不同而 不同。 例如, 对于 GPRS隧道协议(GPRS Tunneling Protocol, GTP ) , 目标 数据网关发送承载更新请求给 SGW, SGW更新目标数据网关用户面与控制 面地址和 TEID, 建立目标数据网关与 SGW之间的 GTP隧道。
步骤 703: 目标数据网关与 PCRF更新控制会话。
例如, PCRF将迁移用户源数据网关下的策略控制信息更新为目标数据网 关下的策略控制信息。 在获取迁移业务数据流信息对应的源数据网关下的策 略控制信息时, PCRF基于目标数据网关提供的连接信息,如 UE ID、 PDN ID 或 UE IP地址等。 或者, 基于目标数据网关从源数据网关获得的策略控制信 息标识, 查找对应的源数据网关下的策略控制信息。
PCRF根据业务数据流信息与源数据网关下的策略控制信息生成目标数 据网关下的策略控制信息, 或者直接将源数据网关下的策略控制信息作为目 标数据网关下的策略控制信息, 然后发送生成策略信息给目标数据网关。
步骤 704: SGW向移动性管理网元发送更新连接隧道请求, 更新的内容 包括目标数据网关用户面与控制面地址和 TEID等信息。
步骤 705: 移动性管理网元向 SGW返回更新成功消息。 表示连接隧道更 新成功。
步骤 706: SGW向目标数据网关返回更新成功消息, 表示两者之间的连 接隧道建立成功。
步骤 707: 目标数据网关向业务网关发布路由网段。 此路由网段信息由 被迁移用户终端 IP地址决定。 当迁移用户 IP地址属同一地址段或相同子网 时, 则更改该网段或子网的路由信息, 即将该网段路由信息中的下一跳数据 网关地址由源数据网关改为目标数据网关, 使得目标数据网关与报文数据网 络之间建立连接。
步骤 708: 目标数据网关向源数据网关发送负载迁移成功消息。 目标数 据网关接管用户数据成功后通知源数据网关。 源数据网关删除被迁移用户数 据并释放资源。
步骤 709: 源数据网关删除用户上下文数据, 译放资源。
如果用户的签约数据允许跟非 3GPP互通, 则进一步可以由移动性管理 网元将目标数据网关地址与对应 APN信息注册到 HSS中。 消息中携带用户 使用的 APN和目标数据网关地址; HSS保存用户使用的 APN和目标数据网 关地址信息并返回更新响应消息到移动性管理网元。
上述描述了目标数据网关为备份数据网关时的流程, 当目标数据网关不 是备份数据网关时, 与上述流程不同的是, 在上述的步骤 701-702之间还包 括:
源数据网关向目标数据网关发送用户上下文数据传递请求, 之后, 将被 户上下文数据携带在用户上下文数据传递请求中发送给目标数据网关;
源数据网关发送删除(delete ) 消息给被迁移用户对应的备份数据网关, 指示备份数据网关删除相应的备用户数据。 上述的 delete消息中包含被迁移 用户标识, 可以是 IMSI、 NAI、 MSISDN等。 之后, 备份数据网关基于被迁 移用户标识删除相应的备用户数据。
本实施例通过进行实时备份可以提高用户数据的安全性和业务的稳定 性。 通过负载迁移可以均衡各数据网关的负载, 提高系统资源利用率。
上述对负载均衡和 /或实时备份的处理 于数据网关正常时, 当数据网 关出现故障时, 需要进行故障处理。
图 8为本发明第四实施例的方法流程示意图, 包括:
步骤 801 : 网关管理网元确定故障数据网关。
其中, 可以是在网关管理网元中设置时间阈值, 当该时间阈值达到时, 没有收到状态信息上报消息所对应的数据网关为故障数据网关。
状态信息上报消息可以是数据网关在收到网关管理网元发送的 ping信令 后发送的, 也可以是在数据网关中设置上报定时器, 在上报定时器的时间达 到时, 主动发送状态信息上报消息。
步骤 802: 网关管理网元确定该故障数据网关的备份数据网关。
网关管理网元可以通过比较备份数据网关的负载权重参数与设置的负载 权重阈值, 确定备份数据网关是否需要进行负载迁移。 其中, 本发明实施例 中, 数据网关故障或者过载时, 表明该数据网关需要进行负载迁移, 否则不 需要进行负载迁移。
当备份数据网关不需要进行负载迁移时, 执行如下步骤:
步骤 803: 网关管理网元向备份数据网关发送 invite消息, 该消息中携带 故障数据网关的标识, 例如, 故障数据网关的 IP地址。
备份数据网关在接收到 invite消息后,根据该 invite消息中携带的故障数 据网关标识, 启用对应的备份用户上下文数据并接管相应的用户业务。
步骤 804: 备份数据网关发送更新连接隧道请求给 SGW, 请求更新连接 隧道。
具体可以类似步骤 702的处理。
步骤 805: 备份数据网关与 PCRF更新控制会话。
具体可以类似步骤 703的处理。
步骤 806: SGW向移动性管理网元发送更新连接隧道请求, 更新的内容 包括目标数据网关用户面与控制面地址和 TEID等信息。
步骤 807: 移动性管理网元向 SGW返回更新成功消息。 表示连接隧道更 新成功。
步骤 808: SGW向备份数据网关返回更新成功消息, 表示两者之间的连 接隧道建立成功。
步骤 809: 备份数据网关向业务网关发布路由网段。 此路由网段信息由 被迁移用户终端 IP地址决定。 当迁移用户 IP地址属同一地址段或相同子网
时, 则更改该网段或子网的路由信息, 即将该网段路由信息中的下一跳数据 网关地址由源数据网关改为目标数据网关, 使得目标数据网关与报文数据网 络之间建立连接。
如果用户的签约数据允许跟非 3GPP互通, 则进一步可以由移动性管理 网元将备份数据网关地址与对应 APN信息注册到 HSS中。 消息中携带用户 使用的 APN和备份数据网关地址; HSS保存用户使用的 APN和目标数据网 关地址信息并返回更新响应消息到移动性管理网元。
上述描述了备份数据网关不需要进行负载迁移时的流程, 当备份数据网 关需要进行负载迁移时, 贝' J :
在步骤 802中, 网关管理网元为备份数据网元选择目标数据网关; 在步骤 803之后还包括:
网关管理网元将目标数据网关标识携带在状态信息反馈消息中发送给备 份数据网关;
备份数据网关将用户上下文数据发送到目标数据网关, 其中, 可以是备 上下文数据发送给目标数据网关, 或者, 备份数据网关将用户上下文数据携 带在用户上下文传递请求中发送给目标数据网关;
之后, 由目标数据网关替代备份数据网关执行步骤 804-809。
本实施例通过在主数据网关发生故障时, 由备份数据网关接管业务, 可 以保证用户数据的安全性及业务的稳定性; 本实施例通过在备份数据网关过 载时将用户数据迁移后目标数据网关, 可以实现系统资源的均衡。
图 9为本发明第五实施例的设备结构示意图, 包括接收模块 91、 目标网 关选择模块 92和目标网关发送模块 93;接收模块 91用于当数据网关正常时, 接收数据网关发送的状态信息上报消息, 所述状态信息上报消息中携带状态 信息; 目标网关选择模块 92用于当确定出需要进行负载均衡的数据网关时, 根据所述状态信息为源数据网关选择目标数据网关, 所述源数据网关为需要
进行负载均衡的数据网关; 目标网关发送模块 93用于将目标数据网关的状态 信息发送给所述源数据网元, 使得所述源数据网关根据所述目标数据网关的 状态信息, 将部分用户业务由所述源数据网关迁移到所述目标数据网关。
另一方面, 还可以包括备份网关选择模块 94和备份网关发送模块 95; 备份网关选择模块 94用于当确定出需要进行备份的数据网关时,根据所述状 态信息为主数据网关选择备份数据网关, 所述主数据网关为需要进行备份的 数据网关;备份网关发送模块 95用于将备份数据网关的状态信息发送给所述 主数据网关, 使得所述主数据网关根据所述备份数据网关的状态信息, 将用 户上下文数据同步到所述备份数据网关中.
另一方面, 还可以包括故障网关确定模块 96和故障网关发送模块 97; 故障网关确定模块 96用于当数据网关故障时,确定故障数据网关的备份数据 网关;故障网关发送模块 97用于当所述备份数据网关正常且不需要进行负载 迁移时, 将故障数据网关标识发送给所述备份数据网关, 使得所述备份数据 网关接管所述故障数据网关对应的用户业务。
本实施例通过进行实时备份可以提高用户数据的安全性和业务的稳定 性。 通过负载迁移可以均衡各数据网关的负载, 提高系统资源利用率。 本实 施例通过在主数据网关发生故障时, 由备份数据网关接管业务, 可以保证用 户数据的安全性及业务的稳定性。
图 10为本发明第六实施例的系统结构示意图, 包括网关管理网元 101和 源数据网关 102; 网关管理网元 101用于当数据网关正常时, 接收数据网关 发送的状态信息上报消息, 所述状态信息上报消息中携带状态信息, 并确定 出需要进行负载迁移的数据网关时, 根据所述状态信息为源数据网关选择目 标数据网关, 所述源数据网关为需要进行负载均衡的数据网关; 源数据网关 102 用于根据所述目标数据网关的状态信息, 将部分用户业务由所述源数据 网关迁移到所述目标数据网关。
另一方面, 所述网关管理网元 101还用于当确定出需要进行备份的数据
网关时, 根据所述状态信息为主数据网关选择备份数据网关, 所述主数据网 关为需要进行备份的数据网关; 所述系统还包括: 主数据网关 103 , 主数据 网关 103用于根据所述备份数据网关的状态信息, 将用户上下文数据同步到 所述备份数据网关中。
另一方面, 所述网关管理网元 101还用于当数据网关故障时, 确定故障 数据网关的备份数据网关, 当所述备份数据网关正常且不需要进行负载迁移 时, 将故障数据网关标识发送给所述备份数据网关; 所述系统还包括: 备份 数据网关 104, 备份数据网关 104用于接管所述故障数据网关对应的用户业 务。
本实施例通过在主数据网关发生故障时, 由备份数据网关接管业务, 可 以保证用户数据的安全性及业务的稳定性; 本实施例通过在备份数据网关过 载时将用户数据迁移后目标数据网关, 可以实现系统资源的均衡。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其 限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术 人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或 者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。
Claims
1、 数据网关负载处理方法, 其特征在于, 包括:
当数据网关正常时, 网关管理网元接收数据网关发送的状态信息上报消 息 , 所述状态信息上报消息中携带状态信息;
当确定出需要进行负载均衡的数据网关时, 网关管理网元根据所述状态 信息为源数据网关选择目标数据网关, 所述源数据网关为需要进行负载均衡 的数据网关;
网关管理网元将目标数据网关的状态信息发送给所述源数据网元, 使得 所述源数据网关根据所述目标数据网关的状态信息, 将部分用户业务由所述 源数据网关迁移到所述目标数据网关。
2、 根据权利要求 1所述的方法, 其特征在于, 还包括:
当确定出需要进行备份的数据网关时, 网关管理网元根据所述状态信息 为主数据网关选择备份数据网关, 所述主数据网关为需要进行备份的数据网 关;
网关管理网元将备份数据网关的状态信息发送给所述主数据网关, 使得 所述主数据网关根据所述备份数据网关的状态信息, 将用户上下文数据同步 到所述备份数据网关中。
3、 根据权利要求 1所述的方法, 其特征在于, 还包括:
当数据网关故障时, 网关管理网元确定故障数据网关的备份数据网关; 当所述备份数据网关正常且不需要进行负载迁移时, 网关管理网元将故 障数据网关标识发送给所述备份数据网关, 使得所述备份数据网关接管所述 故障数据网关对应的用户业务。
4、 根据权利要求 1所述的方法, 其特征在于, 所述状态信息包括负载权 重参数, 所述确定出需要进行负载均衡的数据网关, 包括:
当数据网关发送的状态信息中的负载权重参数小于等于预先设定的权重 阈值时, 确定出所述数据网关为需要进行负载均衡的数据网关。
5、 根据权利要求 4所述的方法, 其特征在于, 所述状态信息还包括地址 池空间、 可达 APN列表, 所述网关管理网元根据所述状态信息为源数据网关 选择目标数据网关, 包括:
当所述源数据网关存在备份数据网关且备份数据网关不需要进行负载迁 移时, 优先选择负载权重参数大的备份数据网关作为目标数据网关;
当所述源数据网关不存在备份数据网关或备份数据网关需要进行负载迁 移时, 在与源数据网关具有重合地址池空间的数据网关中优先选择负载权重 参数大的数据网关作为目标数据网关;
当两个数据网关的负载权重参数相同时, 优先选择与源数据网关具有相 似程度高的可达 APN列表的数据网关作为目标数据网关;
当 APN列表也相同时, 随机选择数据网关作为目标数据网关。
6、 根据权利要求 1所述的方法, 其特征在于, 所述源数据网关根据所述 目标数据网关的状态信息, 将部分用户业务由所述源数据网关迁移到所述目 标数据网关, 包括:
源数据网关接收网关管理网元发送的目标数据网关的状态信息; 源数据网关根据所述目标数据网关的状态信息选择被迁移用户及为被迁 移用户选择目标数据网关;
源数据网关通知与被迁移用户对应的目标数据网关接管被迁移用户的用 户业务。
7、 根据权利要求 6所述的方法, 其特征在于, 所述源数据网关为被迁移 用户选择目标数据网关包括:
优先选择被迁移用户的用户上下文数据所在的备份数据网关作为被迁移 用户的目标数据网关;
当被迁移用户的备份数据网关不可用时, 在地址池空间包含被迁移用户 的 IP地址的数据网关中优先选择负载权重参数大的数据网关作为被迁移用户 的目标数据网关。
8、 根据权利要求 6所述的方法, 其特征在于, 所述源数据网关通知与被 迁移用户对应的目标数据网关接管被迁移用户的用户业务, 包括:
当目标数据网关为被迁移用户的备份数据网关时, 源数据网关向所述备 份数据网关发送邀请消息, 其中携带被迁移用户标识, 以便所述备份数据网 关将被迁移用户标识对应的用户上下文数据转为主用户数据, 并为主用户数 据分配资源;
当目标数据网关不是被迁移用户的备份数据网关时, 源数据网关将被迁 移用户的用户上下文数据发送给目标数据网关, 使得目标数据网关将被迁移 用户的用户上下文数据保存为主用户数据, 并为主用户数据分配资源。
9、 根据权利要求 8所述的方法, 其特征在于, 当目标数据网关不是备份 数据网关时, 所述方法还包括:
源数据网关向被迁移用户对应的备份数据网关发送 delete消息,该 delete 消息中携带被迁移用户标识, 以便备份数据网关接收到 delete消息后, 删除 被迁移用户标识对应的用户上下文数据。
10、 根据权利要求 2所述的方法, 其特征在于, 所述确定出需要进行备 份的数据网关, 包括:
数据网关没有备份数据网关或者备份数据网关出现故障时, 确定出所述 数据网关为需要进行备份的数据网关。
11、 根据权利要求 2所述的方法, 其特征在于, 所述状态信息包括负载 权重参数、 地址池空间、 可达 APN列表, 所述网关管理网元根据所述状态信 息为主数据网关选择备份数据网关, 包括:
网关管理网元在与主数据网关具有重合地址池空间的数据网关中, 优先 选择负载权重参数大的数据网关;
当负载权重参数相同时, 优先选择与主数据网关具有相似程度高的可达 APN列表的数据网关;
当可达 APN列表相同时, 随机选择。
12、 根据权利要求 11所述的方法, 其特征在于, 所述主数据网关根据所 述备份数据网关的状态信息,将用户上下文数据同步到所述备份数据网关中, 包括:
主数据网关接收网关管理网元发送的备份数据网关的状态信息; 主数据网关根据所述备份数据网关的状态信息, 为被备份用户选择备份 数据网关;
主数据网关将被备份用户的用户上下文数据发送给对应的备份数据网关 中, 使得备份数据网关将用户上下文数据作为备用户数据保存。
13、 根据权利要求 12所述的方法, 其特征在于, 主数据网关根据所述备 份数据网关的状态信息, 为被备份用户选择备份数据网关, 包括:
在地址池空间包含被备份用户的 IP地址的数据网关中,优先选择负载权 重参数大的数据网关。
14、 根据权利要求 3所述的方法, 其特征在于, 所述数据网关故障, 包 括:
当在预先设定的时间阈值内, 没有收到数据网关发送的状态信息上报消 息, 网关管理网元确定所述数据网关为故障数据网关。
15、 一种数据网关负载处理设备, 其特征在于, 包括:
接收模块, 用于当数据网关正常时, 接收数据网关发送的状态信息上报 消息 , 所述状态信息上报消息中携带状态信息;
目标网关选择模块, 用于当确定出需要进行负载均衡的数据网关时, 根 据所述状态信息为源数据网关选择目标数据网关, 所述源数据网关为需要进 行负载均衡的数据网关;
目标网关发送模块, 用于将目标数据网关的状态信息发送给所述源数据 网元, 使得所述源数据网关根据所述目标数据网关的状态信息, 将部分用户 业务由所述源数据网关迁移到所述目标数据网关。
16、 根据权利要求 15所述的设备, 其特征在于, 还包括: 备份网关选择模块, 用于当确定出需要进行备份的数据网关时, 根据所 述状态信息为主数据网关选择备份数据网关, 所述主数据网关为需要进行备 份的数据网关;
备份网关发送模块, 用于将备份数据网关的状态信息发送给所述主数据 网关, 使得所述主数据网关根据所述备份数据网关的状态信息, 将用户上下 文数据同步到所述备份数据网关中。
17、 根据权利要求 15所述的设备, 其特征在于, 还包括:
故障网关确定模块, 用于当数据网关故障时, 确定故障数据网关的备份 数据网关;
故障网关发送模块, 用于当所述备份数据网关正常且不需要进行负载迁 移时, 将故障数据网关标识发送给所述备份数据网关, 使得所述备份数据网 关接管所述故障数据网关对应的用户业务。
18、 一种数据网关负载处理系统, 其特征在于, 包括:
网关管理网元, 用于当数据网关正常时, 接收数据网关发送的状态信息 上报消息, 所述状态信息上报消息中携带状态信息, 并确定出需要进行负载 均衡的数据网关时, 根据所述状态信息为源数据网关选择目标数据网关, 所 述源数据网关为需要进行负载均衡的数据网关;
源数据网关, 用于根据所述目标数据网关的状态信息, 将部分用户业务 由所述源数据网关迁移到所述目标数据网关。
19、 根据权利要求 18所述的系统, 其特征在于,
所述网关管理网元还用于确定出需要进行备份的数据网关时, 根据所述 状态信息为主数据网关选择备份数据网关, 所述主数据网关为需要进行备份 的数据网关;
所述系统还包括:
主数据网关, 用于根据所述备份数据网关的状态信息, 将用户上下文数 据同步到所述备份数据网关中。
20、 根据权利要求 18所述的系统, 其特征在于,
所述网关管理网元还用于当数据网关故障时, 确定故障数据网关的备份 数据网关, 当所述备份数据网关正常且不需要进行负载迁移时, 将故障数据 网关标识发送给所述备份数据网关;
所述系统还包括:
备份数据网关, 用于接管所述故障数据网关对应的用户业务。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201080001579.3A CN102450052B (zh) | 2010-06-02 | 2010-06-02 | 数据网关负载处理方法、设备及系统 |
PCT/CN2010/073475 WO2011150564A1 (zh) | 2010-06-02 | 2010-06-02 | 数据网关负载处理方法、设备及系统 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2010/073475 WO2011150564A1 (zh) | 2010-06-02 | 2010-06-02 | 数据网关负载处理方法、设备及系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011150564A1 true WO2011150564A1 (zh) | 2011-12-08 |
Family
ID=45066123
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/073475 WO2011150564A1 (zh) | 2010-06-02 | 2010-06-02 | 数据网关负载处理方法、设备及系统 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102450052B (zh) |
WO (1) | WO2011150564A1 (zh) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014183696A1 (zh) * | 2013-11-29 | 2014-11-20 | 中兴通讯股份有限公司 | 一种路径建立的方法、控制器及移动性管理实体 |
WO2017000142A1 (zh) * | 2015-06-29 | 2017-01-05 | 华为技术有限公司 | 一种p-cscf负载管理方法及pgw |
CN106452966A (zh) * | 2016-11-02 | 2017-02-22 | 河南智业科技发展有限公司 | 一种OpenStack云桌面的多网关管理的实现方法 |
WO2018120822A1 (zh) * | 2016-12-30 | 2018-07-05 | 华为技术有限公司 | 一种用户数据锚点迁移的方法、设备和系统 |
WO2018133454A1 (zh) * | 2017-01-19 | 2018-07-26 | 广州华多网络科技有限公司 | 远程服务访问路径控制方法和相关设备 |
WO2019134648A1 (zh) * | 2018-01-03 | 2019-07-11 | 中兴通讯股份有限公司 | 一种控制面资源迁移的实现方法、装置及网络功能实体 |
CN112218334A (zh) * | 2019-07-09 | 2021-01-12 | 中国移动通信集团安徽有限公司 | 核心网负荷的动态优化方法、装置及计算设备 |
CN113676415A (zh) * | 2020-05-15 | 2021-11-19 | 中国移动通信集团湖南有限公司 | 一种网络负载均衡的方法、装置及电子设备 |
CN115277569A (zh) * | 2022-07-21 | 2022-11-01 | Oppo广东移动通信有限公司 | 多媒体通信方法、系统、相关设备及存储介质 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016000180A1 (zh) * | 2014-06-30 | 2016-01-07 | 华为技术有限公司 | 终端管理方法和网络设备 |
CN108345516B (zh) * | 2018-01-09 | 2023-02-21 | 创新先进技术有限公司 | 一种账户回迁方法、装置及设备 |
CN110753002B (zh) * | 2019-09-29 | 2023-04-07 | 北京浪潮数据技术有限公司 | 流量调度方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1859285A (zh) * | 2005-11-05 | 2006-11-08 | 华为技术有限公司 | WiMAX接入服务网络中网关间负载均衡的方法 |
CN101217420A (zh) * | 2007-12-27 | 2008-07-09 | 华为技术有限公司 | 一种联动处理方法及设备 |
US20080317053A1 (en) * | 2007-06-22 | 2008-12-25 | Cisco Technology, Inc. | LOAD-BALANCED NSAPI ALLOCATION FOR iWLAN |
-
2010
- 2010-06-02 WO PCT/CN2010/073475 patent/WO2011150564A1/zh active Application Filing
- 2010-06-02 CN CN201080001579.3A patent/CN102450052B/zh active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1859285A (zh) * | 2005-11-05 | 2006-11-08 | 华为技术有限公司 | WiMAX接入服务网络中网关间负载均衡的方法 |
US20080317053A1 (en) * | 2007-06-22 | 2008-12-25 | Cisco Technology, Inc. | LOAD-BALANCED NSAPI ALLOCATION FOR iWLAN |
CN101217420A (zh) * | 2007-12-27 | 2008-07-09 | 华为技术有限公司 | 一种联动处理方法及设备 |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014183696A1 (zh) * | 2013-11-29 | 2014-11-20 | 中兴通讯股份有限公司 | 一种路径建立的方法、控制器及移动性管理实体 |
WO2017000142A1 (zh) * | 2015-06-29 | 2017-01-05 | 华为技术有限公司 | 一种p-cscf负载管理方法及pgw |
CN106452966A (zh) * | 2016-11-02 | 2017-02-22 | 河南智业科技发展有限公司 | 一种OpenStack云桌面的多网关管理的实现方法 |
WO2018120822A1 (zh) * | 2016-12-30 | 2018-07-05 | 华为技术有限公司 | 一种用户数据锚点迁移的方法、设备和系统 |
CN108271149A (zh) * | 2016-12-30 | 2018-07-10 | 华为技术有限公司 | 一种用户数据锚点迁移的方法、设备和系统 |
CN108271149B (zh) * | 2016-12-30 | 2021-09-14 | 华为技术有限公司 | 一种用户数据锚点迁移的方法、设备和系统 |
WO2018133454A1 (zh) * | 2017-01-19 | 2018-07-26 | 广州华多网络科技有限公司 | 远程服务访问路径控制方法和相关设备 |
WO2019134648A1 (zh) * | 2018-01-03 | 2019-07-11 | 中兴通讯股份有限公司 | 一种控制面资源迁移的实现方法、装置及网络功能实体 |
CN112218334A (zh) * | 2019-07-09 | 2021-01-12 | 中国移动通信集团安徽有限公司 | 核心网负荷的动态优化方法、装置及计算设备 |
CN113676415A (zh) * | 2020-05-15 | 2021-11-19 | 中国移动通信集团湖南有限公司 | 一种网络负载均衡的方法、装置及电子设备 |
CN113676415B (zh) * | 2020-05-15 | 2023-10-27 | 中国移动通信集团湖南有限公司 | 一种网络负载均衡的方法、装置及电子设备 |
CN115277569A (zh) * | 2022-07-21 | 2022-11-01 | Oppo广东移动通信有限公司 | 多媒体通信方法、系统、相关设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN102450052B (zh) | 2014-04-02 |
CN102450052A (zh) | 2012-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011150564A1 (zh) | 数据网关负载处理方法、设备及系统 | |
US10375628B2 (en) | Method in a network node of a wireless communications network | |
CN111247832B (zh) | Pdn和pdu会话类型映射和能力发现 | |
CN101588325B (zh) | 一种基于无线分组网关的容灾方法、设备及系统 | |
CN105828315B (zh) | 服务网关选择方法及系统 | |
US10009934B2 (en) | Method for data communication, system for communication and related devices | |
JP5793812B2 (ja) | データオフロードをトリガするための方法、ネットワーク側デバイス、ユーザ機器、およびネットワークシステム | |
US8693456B2 (en) | Method, system, and device for radio network aggregation | |
EP3827577B1 (en) | System and method for intelligently managing sessions in a mobile network | |
US8369288B2 (en) | Method and apparatus for bearer processing | |
US20110007748A1 (en) | Method, system and apparatus for optimizing routes | |
US8867471B2 (en) | Method, device, and system for reporting radio access network element information | |
US20140169332A1 (en) | Method for supporting selection of pdn connections for a mobile terminal and mobile terminal | |
WO2013010415A1 (zh) | 一种实现ip地址属性通知的方法、系统和sgw | |
WO2017162121A1 (zh) | 用户面服务网关选择方法及系统 | |
EP2332319B1 (en) | Systems and methods for bulk release of resources associated with node failure | |
US9668176B2 (en) | Method for selecting shunt gateway and controller | |
JP2022549018A (ja) | セッション管理のための方法および装置 | |
WO2014059647A1 (zh) | 一种数据域业务处理方法、装置及系统 | |
WO2011026391A1 (zh) | 服务网关的负载重分配方法、系统及服务网关 | |
WO2019137242A1 (zh) | 建立承载方法、装置、处理器及存储介质 | |
US10225191B2 (en) | Service packet distribution method and apparatus | |
WO2020030166A1 (zh) | 指示信息的发送方法、装置及系统、存储介质 | |
WO2013159605A1 (zh) | 一种通信系统、装置和方法 | |
WO2017215487A1 (zh) | SGwU地址的传输方法及装置、MME、SGSN |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080001579.3 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10852363 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10852363 Country of ref document: EP Kind code of ref document: A1 |