WO2009043276A1

WO2009043276A1 - Method for providing load information

Info

Publication number: WO2009043276A1
Application number: PCT/CN2008/072484
Authority: WO
Inventors: Yi Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-27
Filing date: 2008-09-24
Publication date: 2009-04-09
Also published as: CN101400099A

Abstract

A method for providing load information involves creating the load information of S-GW and sending the load information of S-GW to Mobility Management Entity MME. The method is applied to a S-GW, a method for controlling S-GW and a MME.

Description

Load information providing method, S-GW, S-GW control method and MME. The application request is submitted to the Chinese Patent Office on September 27, 2007, the application number is 200710151716.1, and the invention name is "load information providing method, S-GW, The control method of the service gateway and the priority of the Chinese patent application of the MME, the entire contents of which are incorporated herein by reference. Technical field

The present invention relates to wireless communication technologies, and in particular, to a control technology of a Serving Gateway (S-GW).

Background technique

General Packet Radio Service (GPRS) is a mobile packet data service developed on the basis of Global System for Mobile Communications (GSM). GPRS completes data transmission in packet mode by introducing a packet-switched functional entity in the GSM digital mobile communication network. For example, GPRS adds a Serving GPRS Supporting Node (SGSN) and a Gateway GPRS Support Node (GGSN). , Gateway GPRS Supporting Node ), and enhanced the software features of a series of original GSM functional entities. Since GPRS uses packet communication technology, the user does not occupy the wireless channel in the data communication process, so that channel resources can be more reasonably applied.

The Evolved Packet System (EPS) network can be considered as the next generation GPRS network. As shown in FIG. 1, the EPS network includes a Mobility Management Entity (MME) 101, an S-GW 102, a PDN Gateway (PDN Gateway) 103, and an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). , Evolved Universal Terrestril Radio Access Network ) 104 and user equipment (11, User Equipment) 105 and other network entities. The MME 101 and the S-GW 102 can be regarded as two entities separated by the SGSN, and the functions of the P-GW 103 and the GGSN are similar. The MME 101 implements the functions of the control plane, including mobility management, access signaling, bearer management, roaming management, etc. The S-GW 102 implements the functions of the bearer plane, including the routing of packets, and the anchor function of the local access network. The MME 101 and the S-GW 102 have a certain control relationship, and the S11 interface between the two can use the GPRS Tunneling Protocol (GTP). As shown in FIG. 2, MME1 can simultaneously control S-GW1 and S-GW2, and MME2 can simultaneously control S-GW1, S-GW2, and S-GWn, etc., and S-GW1 and S-GW2 can be simultaneously controlled by MME1 and MME2, respectively. . In addition, one user can only correspond to one MME and one S-GW. A user can establish multiple bearers at the same time, but multiple bearers established simultaneously by the same user must be on one S-GW. Since the MME only processes the signaling of the control plane, and the S-GW needs to process the data forwarding of the bearer plane, in general, the capacity of the MME is larger than that of the S-GW.

The inventors of the present invention have found in the process of implementing the present invention that, in general, the MME controls the S-GW based on information such as pre-configured parameters. For example, when the MME needs to select an S-GW to establish a first bearer for the user, the MME selects one S-GW from the S-GWs according to the pre-configured weights of the respective S-GWs, where the weight is selected. Generally related to the capacity of the S-GW. In practical applications, the S-GW may change with the increase of the running time. If the MME still selects the S-GW according to the static selection weight, the selected S-GW may not be the most suitable S-GW. Further, there is a possibility of causing an imbalance in load between the S-GWs. Similarly, in the other processes in which the MME controls the S-GW, most of the operations are performed based on pre-configured static information, and further problems may occur. For example, in the process of establishing a bearer on the S-GW, the MME establishes a bearer on the S-GW according to the pre-configured static information. As mentioned above, the load of the S-GW may change with the running time. In this way, the load on the S-GW based on the pre-configured static information to load the S-GW that may cause the load to be heavy will become heavier and heavier, and in severe cases, the operation of the S-GW will approach collapse. Regardless of the load imbalance between the S-GWs or the increasing load on the S-GW, the MME has not been able to effectively control the performance of the S-GW.

Summary of the invention

A technical problem to be solved by the embodiments of the present invention is to provide a load information providing method, an S-GW, a S-GW control method, and an MME, for effectively controlling the S-GW.

To solve the above technical problem, the present invention provides an embodiment of a load information providing method, including: generating load information of an S-GW; and providing load information of the S-GW to a mobility management entity. The present invention further provides a An embodiment of the S-GW control method includes: obtaining load information of at least one S-GW; and controlling the S-GW according to the obtained load information.

The present invention further provides an embodiment of the S-GW, including: a load information generating unit, configured to generate load information; and a load information providing unit, configured to provide load information generated by the load information generating unit to the MME.

The present invention also provides an embodiment of an MME, including: a load information obtaining unit, configured to obtain The load information of the at least one S-GW; the S-GW control unit is configured to control the S-GW according to the load information obtained by the load information obtaining unit.

The present invention also provides a wireless communication system including at least one S-GW and an MME that controls the at least one S-GW; the S-GW is configured to generate load information, and provide the load information to the MME The MME is configured to control the S-GW according to the load information provided by the at least one S-GW.

In the load information providing embodiment of the present invention, the S-GW can provide the load information to the MME, so that the MME can control the S-GW according to the load information, and avoids controlling each generated by the S-GW according to the static information. A problem that effectively controls the S-GW.

In the service gateway control embodiment of the present invention, the MME may perform load information according to the S-GW.

The S-GW performs control to avoid various problems caused by controlling the S-GW according to static information, and effectively controls the S-GW.

DRAWINGS

1 is a schematic structural diagram of an existing EPS network;

2 is a schematic diagram of a control relationship between an existing MME and an S-GW;

3 is a flow chart of a first application embodiment of the present invention;

4 is a flow chart of a second application embodiment of the present invention;

Figure 5 is a flow chart of a third application embodiment of the present invention;

Figure 6 is a flow chart of a fourth application embodiment of the present invention;

Figure 7 is a flow chart of a fifth application embodiment of the present invention;

Figure 8 is a flow chart of a sixth application embodiment of the present invention;

Figure 9 is a flow chart of a seventh application embodiment of the present invention.

detailed description

First, an embodiment of the load information providing method of the present invention will be described as a whole. An embodiment of the load information providing method includes: generating load information of the S-GW; and providing load information of the S-GW to the MME.

The load information generating the S-GW and the body providing the load information of the S-GW to the MME may be an S-GW. Before the S-GW provides the load information to the MME, it may receive the load information request sent by the MME, and after receiving the request, the S-GW provides the load information to the MME. S-GW The load information may also be actively provided to the MME. For example, the S-GW may periodically provide load information to the MME, or may provide load information to the MME when the load changes. The S-GW may provide load information to the MME using a separate message, or may provide load information to the MME using a message carrying a setup request or a bearer setup response message. The load information may be carried in a field in which the original GTP message is extended, or carried in an independent GTP message. The GTP message with an extended field is, for example, an echo request, an echo response, a Create PDP Context Request, or a Create PDP Context Response. In addition, the load information may be a load level used to indicate the degree of S-GW load, or a load-related resource detailed information indicating a percentage of each resource being occupied, and the load-related resource detailed information may include at least a percentage of the bearer number, and a packet service processing. Information such as percentage of information, percentage of data throughput, or percentage of CPU load.

The embodiment of the S-GW control method will be further described below. An embodiment of the S-GW control method includes: obtaining load information of at least one S-GW; and controlling the S-GW according to the obtained load information.

The body that obtains the load information and controls the S-GW may be the MME. The MME may request load information from at least one S-GW that it controls, and after receiving the request from the MME, the S-GW may return load information to the MME. Of course, the MME may request load information to the at least one S-GW that it controls, for example, periodically. This period may be set by the MME or other network entity, and may be configured in the MME. The MME may also request the S-GW to provide the load information when the bearer setup request is sent to the S-GW. Accordingly, the S-GW may provide the load information when returning the bearer setup response to the MME. For example, the bearer setup request sent by the MME may carry the request information, and the bearer setup response returned by the S-GW may carry the load information.

In addition, the S-GW can also actively provide load information to the MME. For example, when the load of the S-GW changes, the S-GW can actively report the current load information to the MME. Specifically, the load can be set to a threshold. When the load exceeds or equals the threshold, the S-GW can actively report the current load information. Further, the load information may include multiple load parameters at the same time, and may also set a load threshold for each load parameter. When the value of the load parameter exceeds or equals the load threshold, the S-GW sends the load information to the MME. The load threshold may be dynamically set by the MME, or may be dynamically set by the S-GW, and the load threshold of each S-GW may be the same or different. For another example, the S-GW can periodically report the load information, in particular, if the load of the S-GW does not change during the period. If the load value does not exceed the preset load threshold, the S-GW may not report the load information even when the load information is reported. For example, when the S-GW sends a bearer setup request to the MME, the load information may be carried in the bearer setup request and sent to the MME. For example, when the MME sends a bearer setup request to the S-GW, although the bearer setup request does not necessarily have a request for providing load information, the S-GW may carry the bearer information in the bearer setup response returned to the MME.

The load information of the S-GW may be carried in the existing GTP message, but the field of the existing GTP message needs to be extended. For example, the load information of the S-GW may be carried in the extended echo request sent by the S-GW. Or the extended echo response may also be carried in the extended Create PDP Context Request or the extended Create PDP Context Response. The load information of the S-GW may also be carried in the newly added GTP message, or carried in a message independent of the existing GTP message, for example, a newly added request or a response GTP message.

The load information of the S-GW may be a load level, which is used to indicate the current load level of the S-GW. The load information of the S-GW may also be related resource detail information including multiple resource occupation parameters, and each resource occupancy parameter is used to indicate the percentage of the resource occupied. For example, the load-related resource detailed information may include at least a percentage of the number of bearers. Packet service processing information percentage, data throughput percentage or CPU load percentage.

In an embodiment of the foregoing S-GW control method, the MME may select one S-GW from the at least one S-GW according to the obtained load information. For example, after obtaining the load information of the at least one S-GW, the MME may first select one S-GW with the lowest load from the S-GWs, and select the S-GW with the lowest load, and then determine the S with the lowest load. - Whether the GW is overloaded. If not, the subsequent processing can be performed normally, for example, accepting the current bearer setup request, etc., but if the S-GW is overloaded, it is necessary to reject some or all of the bearer setup requests, or even directly reject the current The bearer setup request is to alleviate the congestion level of the S-GW. Of course, if the S-GW is overloaded, it can also determine whether the current bearer can be established according to the load information, and if so, accept the current bearer setup request, otherwise, reject the current bearer setup request.

In the foregoing embodiment of the S-GW control method, the MME may also determine, according to the obtained load information, whether there is an overload of the S-GW or whether the load of any one of the S-GWs is overloaded, if all the loads of the S-GW are If there is no overload or the load of the specified S-GW is not overloaded, normal subsequent processing can be performed, for example, accepting the current bearer setup request, etc.; if there is overload of the S-GW Or the load of the specified S-GW is overloaded, and at least one bearer setup request for the overloaded S-GW may be rejected, and the current bearer setup request may be directly rejected. Of course, if the load of the S-GW is overloaded or the load of the designated S-GW is overloaded, it is also determined whether the current bearer can be established according to the load information, and if yes, accept the current bearer setup request, otherwise, reject the current Bearer setup request.

In addition, after the MME obtains the load information of the at least one S-GW, when the MME performs the first bearer setup of the user, the MME may first select an S-GW according to the saved load information of the S-GW; When the non-first bearer is established, the MME does not need to select the S-GW, but determines whether the S-GW selected during the execution of the first bearer of the user is overloaded according to the stored load information of the S-GW. Then decide whether you need to reject the bearer setup request.

Several practical application embodiments will be described below with reference to the accompanying drawings.

3 is a flow chart of a first application embodiment of the present invention. As shown in FIG. 3, the method includes the following steps: Step S301: The S-GW1 generates load level information according to the resource occupation status, and periodically sends the load level information to all MMEs in a controlled relationship by using the extended Echo Request message. The resource occupancy includes, for example, the number of bearers, packet service processing, data throughput, CPU load, etc., among which the load level information needs to reflect the most critical resource condition. The load level information can be a value in a load level sequence. Take the load level sequence as 0, 80, 100 as an example, where 0 means that the S-GW has no load. At this time, the S-GW can accept all bearer setup requests, 80 means the S-GW is overloaded, and 100 means the S-GW has At full load, the S-GW can no longer accept the bearer setup request. Of course, the load level information may also have other representations, for example, using the values in 0-5, where 0 indicates that the S-GW is not overloaded, and 2 indicates that the MME needs to reduce the bearer setup request to the S-GW by 40%. 5 indicates that the MME needs to reduce the bearer setup request to the S-GW by 100%. In addition, the reporting period can be configured on S-GW1.

Step S302: After receiving the Echo Request message, the MME returns an Echo Response message to the S-GW1.

Step S301: The S-GW2 generates load level information according to the resource occupation status, and periodically sends the load level information to all MMEs in control relationship with the MME through the extended Echo Request message. The reporting period can be configured on the S-GW2.

Step S302': After receiving the Echo Request message, the MME returns an Echo Response to the S-GW2. Message.

It should be noted that, although the S-GW1 and the S-GW2 are two entities that are independent of each other, and the load information needs to be reported to the MME, there is no necessary sequence for reporting the load information, so step S301 and step S301' There is no inevitable sequence of execution.

Step S303: When the user attaches, the location updates, the handover, and the MME needs to create the first bearer of the user, the MME selects a low-load S-GW to establish a bearer based on the load information, and assumes that the S-GW1 load is low, and the MME selects S-GW1.

Step S304: The MME determines whether the S-GW1 is overloaded according to the selected load level information of the S-GW1. If the S-GW1 is not overloaded, the process goes to step S305. If the S-GW1 is overloaded, the MME determines the current information according to the load level information. If the bearer can be established, the process may go to step S305. If the S-GW1 is overloaded, and the MME determines that the bearer cannot be established according to the load level information, the process goes to step S307. For example, suppose the load level information is a value in a load level sequence, and the load level sequence is assumed to be 0, 80, 100, where 0 indicates that the S-GW has no load, and at this time, the S-GW can accept all bearer setup requests, 80 Indicates that the S-GW is overloaded, and 100 indicates that the S-GW is fully loaded. At this time, the S-GW can no longer accept the bearer setup request. When the load level information of the selected S-GW1 is 80, the MME may determine that the S-GW1 is overloaded, but the overload is not equal to the full load, or the load level information is not 100, so the MME may determine the current The bearer can be established.

Step S305: The MME sends a bearer setup request to the S-GW1, and the process goes to step S306.

Step S306: The S-GW1 returns a bearer setup response to the MME.

Step S307: The MME rejects the corresponding user attachment, location update, and handover request.

4 is a flow chart of a second application embodiment of the present invention. As shown in Figure 4, it includes:

Step S401: The S-GW1 generates the load-related resource detailed information according to the resource occupation situation, and transmits the load-related resource detailed information to the MME by using the newly added GTP message. These load related resources include, for example, the number of bearers, packet service processing, data throughput, CPU load, and the like. The load-related resource details may include the following resource occupancy parameters. The resource occupancy parameter may be a percentage integer. The calculation method may be occupied resource/total resource χΙΟΟ, which may indicate the percentage of resources occupied, as follows:

Percentage of bearers: Number of bearers established / Maximum number of bearers that can be established by S-GW; Percentage of packet service processing: Number of current packet service processing / S-GW maximum packet service processing number Percentage of data throughput: Current data throughput / S-GW maximum data throughput; CPU load percentage: Current CPU load / CPU maximum load.

In addition, one or more negatives can be set individually for each load-related resource occupancy parameter.

S-GW1 sends load information to the MME. In addition, the load-specific load threshold for each load can be configured in S-GW1.

Step S402: After receiving the load related resource detailed information, the MME returns a load information report response message to the S-GW1.

Step S401': S-GW2 generates load-related resource detailed information according to the resource occupation situation, and transmits the load-related resource detailed information to the MME by using the newly added GTP message. In addition, one or more load thresholds may be separately set for each load-related resource occupancy parameter, that is, when the value of each resource occupancy parameter exceeds or falls below a preset load threshold, S-GW2 Send load information to the MME. In addition, the load-specific load threshold for each load can be configured in S-GW2.

Step S402': After receiving the load related resource detailed information, the MME returns a load information report response message to the S-GW2.

It should be noted that, although S-GW1 and S-GW2 are two entities that are independent of each other, and both need to report load information to the MME, there is no necessary sequence for reporting load information, so step S401 and step S401' There is no inevitable sequence of execution.

Step S403: When the user attaches, the location updates, the handover, and the MME needs to create the first bearer of the user, the MME selects an S-GW with the most remaining resources according to the load-related resource detailed information. The remaining resource information can be obtained according to the load-related resource detailed information of the S-GW. For example, if the load-related resource detailed information of an S-GW indicates that its load reaches 40%, the remaining resource of the S-GW is 60%. In addition, the remaining resource information may also be obtained according to the load-related resource detailed information of the S-GW and the S-GW capacity configured by the MME. For example, the S-GW capacity configured by the MME may be a value, and the value and the load-related resource detailed information representation. The product of the percentage can also be considered as load-related resource details. It is assumed here that the S-GW1 load is low and the MME selects S-GW1.

Step S404: The MME determines according to the selected load-related resource detailed information of the S-GW1. Whether the S-GW1 is overloaded. If the MME determines that the occupancy of all the resources in the load-related resource detailed information of the S-GW1 does not exceed the load threshold, it indicates that the S-GW1 is not overloaded, and the process goes to step S405. Otherwise, the process goes to step S407. For example, if the load-related resource detailed information of S-GW1 indicates that its load has reached 90%, and the load threshold set by the MME is 80%, the MME can judge that S-GW1 has been overloaded accordingly. In addition, if it is determined that the S-GW1 is overloaded, but the MME determines that the bearer can be established according to the load-related resource detailed information, it may also proceed to step S405.

Step S405: The MME sends a bearer setup request to the S-GW1, and the process goes to step S406.

Step S406: The S-GW1 returns a bearer setup response to the MME.

Step S407: The MME rejects the corresponding user attachment, location update, and handover request.

Figure 5 is a flow chart of a third application embodiment of the present invention. As shown in FIG. 5, the method includes the following steps: Step S501: The S-GW1 generates load level information according to the resource occupation status, and when the S-GW1 initiates the bearer establishment of the user A to the MME, the load level information is carried in the bearer setup request message. To the MME. For the specific generation manner of the load level information, refer to the first application embodiment.

Step S502: After receiving the bearer setup request, the MME returns a bearer setup response to the S-GW1. Step S501': The S-GW2 generates the load level information according to the resource occupation situation, and when the S-GW2 initiates the bearer establishment of the user B to the MME, the load level information is carried in the bearer setup request message and sent to the MME.

Step S502': After receiving the bearer setup request, the MME returns a bearer setup response to the S-GW2. It should be noted that, although S-GW1 and S-GW2 are two entities that are independent of each other, and both need to send a bearer setup request to the MME, there is no necessary sequence for issuing the bearer setup request, so step S501 and steps are performed. S501' does not have a sequential order of execution.

Step S503: When the user C attaches, the location update, the handover, and the MME needs to create the first bearer of the user C, the MME selects a low-load S-GW to establish a bearer based on the load information, and assumes that the S-GW1 load is low. The MME has selected S-GW1.

Step S504: The MME determines whether the S-GW1 is overloaded according to the selected load level information of the S-GW1. If the S-GW1 is not overloaded, or the S-GW1 is overloaded, the MME determines that the bearer can be established according to the load level information. Go to step S505, otherwise, go to step S507.

Step S505: The MME sends the first bearer setup request of the user C to the S-GW1, and the process goes to step S506. Step S506: The S-GW1 returns a bearer setup response to the MME.

Step S507: The MME rejects the corresponding user C attachment, location update, and handover request.

Figure 6 is a flow chart of a fourth application embodiment of the present invention. As shown in Figure 6, it includes:

Step S601: The MME periodically sends an Echo Request message to the S-GW1, where the Echo Request message can carry the load request information. Of course, the MME can also use other messages or add an additional message to request load information. The sending period of the Echo Request message can be configured in the MME.

Step S602: The S-GW1 generates the load level information according to the resource occupation situation, and carries the load level information in the Echo Response message according to the load request information carried in the Echo Request message, and returns an Echo Response message to the MME. Optionally, if the Echo Request message does not carry the load request information, the S-GW1 may also actively carry the load level information in the Echo Response message and return it to the MME.

Step S601': The MME periodically sends an Echo Request message to the S-GW2, where the Echo Request message can carry the load request information. Of course, the MME can also use other messages or add a message to request load information. The sending period of the Echo Request message can be configured in the MME.

Step S602: The S-GW2 generates the load level information according to the resource occupation status, and carries the load level information in the Echo Response message according to the load request information carried in the Echo Request message, and returns an Echo Response message to the MME. Optionally, if the Echo Request message does not carry the load request information, the S-GW2 may also actively carry the load level information in the Echo Response message and return it to the MME.

It should be noted that, although the MME needs to send an Echo Request to the S-GW1 and the S-GW2 respectively, there is no necessary sequence for issuing the Echo Request. Therefore, there is no necessary sequence of execution in steps S601 and S601.

Step S603: When the user attaches, the location updates, the handover, and the MME needs to create the first bearer of the user, the MME selects a low-load S-GW to establish a bearer based on the load information, and assumes that the S-GW1 load is low, and the MME selects S-GW1.

Step S604: The MME determines, according to the selected load level information of the S-GW1, whether the S-GW1 is overloaded, if the S-GW1 is not overloaded, or the S-GW1 is overloaded, but the MME is according to the load level. If the information determines that the bearer can be established, then go to step S605, otherwise, go to step S607. Step S605: The MME sends a bearer setup request to the S-GW1, and the process goes to step S606.

Step S606: The S-GW1 returns a bearer setup response to the MME.

Step S607: The MME rejects the corresponding user attachment, location update, and handover request.

Figure 7 is a flow chart of a fifth application embodiment of the present invention. As shown in FIG. 7, the method includes: Step S701: The MME periodically sends load request information to the S-GW1 by using the newly added GTP message. The transmission period of the load request information can be configured in the MME.

Step S702: The S-GW1 generates load level information according to the resource occupation situation, and carries the load level information in the newly added GTP message according to the load request information, and returns a newly added GTP message carrying the load level information to the MME. Optionally, if the MME does not send the load request information, the S-GW1 may also actively carry the load level information to the MME by adding the newly added GTP message.

Step S701': The MME periodically sends the load request information to the S-GW2 by using the newly added GTP message. The transmission period of the load request information can be configured in the MME.

Step S702 ′: The S-GW 2 generates load level information according to the resource occupation situation, and carries the load level information in the newly added GTP message according to the load request information, and returns a newly added GTP message carrying the load level information to the MME. . Optionally, if the MME does not send the load request information, the S-GW2 may also actively carry the load level information to the newly added GTP message and return it to the MME.

It should be noted that the MME needs to send the load request information to the S-GW1 and the S-GW2 respectively, but there is no necessary sequence for issuing the load request information. Therefore, there is no necessary sequence of execution in step S701 and step S701.

Step S703: When the user attaches, the location updates, the handover, and the MME needs to create the first bearer of the user, the MME selects a low-load S-GW to establish a bearer based on the load information, and assumes that the S-GW1 load is low, and the MME selects S-GW1.

Step S704: The MME determines whether the S-GW1 is overloaded according to the selected load level information of the S-GW1. If the S-GW1 is not overloaded, or the S-GW1 is overloaded, the MME determines that the bearer can be established according to the load level information. Go to step S705, otherwise, go to step S707.

Step S705: The MME sends a bearer setup request to the S-GW1, and the process goes to step S706. Step S706: The S-GW1 returns a bearer setup response to the MME.

Step S707: The MME rejects the corresponding user attachment, location update, and handover request.

Figure 8 is a flow chart of a sixth application embodiment of the present invention. As shown in FIG. 8, the method includes the following steps: Step S801: When the MME initiates the bearer establishment of the user A to the S-GW1, the MME sends a bearer setup request carrying the load request information to the S-GW1. Of course, the load establishment request sent to S-GW1 may not carry the load request information.

Step S802: The S-GW1 generates load level information according to the resource occupation situation, and carries the load level information to the bearer establishment response and returns it to the ΜΜΕ. Specifically, after receiving the user Α bearer setup request, the S-GW1 carries the load level information to the MME according to the load request information carried by the bearer setup request, and carries the load level information to the MME. If the bearer setup request sent by the MME to the S-GW1 does not carry the load request information, the S-GW1 may actively carry the load level information in the bearer setup response, and return the bearer setup response carrying the load level information to the MME. For the manner in which the S-GW1 generates the load level information, reference may be made to the first application embodiment.

Step S801': When the MME initiates the bearer establishment of the user B to the S-GW2, the MME sends a bearer setup request carrying the load request information to the S-GW2. Of course, the load establishment request sent to the S-GW 2 may not carry the load request information.

Step S802: The S-GW2 generates load level information according to the resource occupation status, and carries the load level information to the bearer establishment response and returns it to the ΜΜΕ. Specifically, after receiving the user Β bearer setup request, the S-GW2 carries the load level information to the bearer setup response and returns it to the 根据 according to the load request information carried by the bearer setup request. If the bearer setup request sent to the S-GW2 does not carry the load request information, the S-GW2 may actively carry the load level information in the bearer setup response, and return the bearer setup response carrying the load level information to the MME. For the manner in which the S-GW2 generates the load level information, reference may be made to the first application embodiment.

It should be noted that although S-GW1 and S-GW2 are two entities that are independent of each other, and need to issue bearer setup requests to S-GW1 and S-GW2 respectively, there is no necessary sequence for issuing bearer setup requests. Therefore, in step S801 and step S801, there is no necessary sequential execution order.

Step S803: When the user C attaches, the location update, the handover, and the MME needs to create the first bearer of the user C, the MME selects a low-load S-GW to establish a bearer based on the load information. It is assumed here that the S-GW1 load is low and the MME selects S-GW1.

Step S804: The MME determines whether the S-GW1 is overloaded according to the selected load level information of the S-GW1. If the S-GW1 is not overloaded, or the S-GW1 is overloaded, the MME determines that the bearer can be established according to the load level information. Go to step S805, otherwise, go to step S807.

Step S805: The MME sends the first bearer setup request of the user C to the S-GW1, and the step is changed.

S806.

Step S806: The S-GW1 returns a bearer setup response to the MME.

Step S807: The MME rejects the corresponding user C attachment, location update, and handover request.

Figure 9 is a flow chart of a seventh application embodiment of the present invention. As shown in FIG. 9, the method includes the following steps: Step S901: The S-GW1 generates the load-related resource detailed information according to the resource occupation, and transmits the load-related resource detailed information to the MME by using the newly added GTP message. These load related resources include, for example, the number of bearers, packet service processing, data throughput, CPU load, and the like. The load-related resource detailed information may include the following resource occupation parameters, and the resource occupation parameter may be a percentage integer, and the calculation method may be occupied resource/total resource χ ΙΟΟ , which may indicate the percentage of resources occupied, as follows:

Number of bearers: Number of bearers established / The maximum number of bearers that the S-GW can establish;

Packet service processing: current number of packet service processing / S-GW maximum packet service processing number; data throughput: current data throughput / S-GW maximum data throughput;

CPU load.

Step S902: After receiving the load related resource detailed information, the MME returns a load information report response message to the S-GW1.

Step S901 ': S-GW2 generates load-related resource detailed information according to the resource occupation situation, and transmits the load-related resource detailed information to the MME by using the newly added GTP message. In addition, one or more load thresholds may be separately set for each load-related resource occupancy parameter, that is, when the value of each resource occupancy parameter exceeds or falls below a preset load threshold, S-GW2 To MME Send load information. In addition, the load threshold associated with each load can be configured at S-GW2.

Step S902': After receiving the load related resource detailed information, the MME returns a load information report response message to the S-GW2.

It should be noted that, although S-GW1 and S-GW2 are two entities that are independent of each other, and the load information needs to be reported to the MME, there is no necessary sequence for reporting the load information, so step S901 and step S901' There is no inevitable sequence of execution.

Step S903: The S-GW1 sends a bearer setup request of the user A to the MME.

Step S904: The MME determines whether the S-GW1 is overloaded according to the load-related resource detailed information of the S-GW1. If the MME determines that the occupancy of all resources in the load-related resource detailed information of the S-GW1 does not exceed the load threshold, it indicates that S - GW1 is not overloaded, go to step S905, otherwise, go to step S906. If it is determined that the S-GW1 is overloaded, but the MME determines that the 7-load can be established according to the load-related resource detailed information, the process may also proceed to step S905.

Step S905: The MME returns a bearer setup response to the S-GW1, indicating that the S-GW1 can continue processing.

Step S906: The MME returns a bearer setup response to the S-GW1, but indicates that the corresponding bearer setup request is rejected.

It should be noted that the above several application embodiments are only embodiments in which specific technical means are applied. In practical applications, those skilled in the art may modify or replace these specific technical means according to actual needs. For example, in all the foregoing embodiments, the S-GW provides the load level information to the MME, and in other embodiments, the S-GW provides the load related resource detailed information to the MME. In actual applications, the original If the load level information is provided, the load-related resource detailed information may be provided instead, and the load-related resource detailed information may be provided instead, and the load level information may be provided instead. Of course, the essence of the technical solution has not changed.

The embodiment of the load information providing method may be implemented by various forms of devices, and an embodiment of the load information providing device includes: a load information generating unit configured to generate load information; a load information providing unit, configured to The load information generated by the load information generating unit is supplied to the MME.

Before the load information providing unit provides the load information to the MME, it may receive the load information request sent by the MME, and after receiving the request, provide the load information to the MME. Of course, the request may also be received by other units. The load information providing unit may also actively provide load information to the MME. For example, the load information providing unit may periodically provide load information to the MME, or may provide load information to the MME when the load changes. If the load information providing unit periodically supplies the load information to the MME, the load information providing apparatus may further set a timer, and the timer may set the period in which the load information providing unit provides the load information, such that the time one The load information providing unit may provide the load information to the MME. If the load information providing unit provides the load information to the MME when the load changes, the load information providing device may further set a function for determining whether the load is changed. a load change determination unit, wherein when the load change determination unit determines that the load has changed, the load change determination unit may issue a prompt for a load change to the load information providing unit, and the load information providing unit receives After the prompt, the load information can be provided to the MME. The load information providing unit may provide load information to the MME using a separate message, and may also provide load information to the MME using a bearer setup request or a bearer setup response. The load information may be carried in a field of the GTP message extension or carried in a separate GTP message. The GTP message with the extended field is, for example, an echo request, an echo response, a Create PDP Context Request, or a Create PDP Context Response. In addition, the load information may be a load level for indicating the degree of S-GW load, or load-related resource detailed information indicating a percentage of each resource being occupied, and the load-related resource detailed information may include at least a percentage of the number of bearers, grouping Information such as percentage of business processing information, percentage of data throughput, or percentage of CPU load.

It should be noted that each unit of the above-mentioned load information providing apparatus can be applied to the S-GW. The working principle of these units in the S-GW is the same as that of the above-described load information providing apparatus, and details are not described herein again.

An embodiment of the S-GW control method may be implemented by multiple forms of devices, and an embodiment of the S-GW control device includes: a load information obtaining unit, configured to obtain load information of at least one S-GW; The GW control unit is configured to control the S-GW according to the load information obtained by the load information obtaining unit.

The load information obtaining unit may include: a load information requesting unit, configured to request load information from the at least one S-GW; and a load information receiving unit, configured to receive the load information fed back by the at least one S-GW. Of course, the load information obtaining unit may request load information to the at least one S-GW at intervals, for example, periodically, and the period may be set by a certain unit or other network entity in the device, and may be specifically configured in the load information obtaining unit. . The load information obtaining unit may also issue a bearer to the S-GW. When the request is made, the S-GW is requested to provide load information, and correspondingly, the S-GW can provide load information when returning the bearer setup response. For example, the bearer setup request sent by the load information obtaining unit may carry the request information, and the bearer setup response returned by the S-GW may carry the load information.

In addition, the S-GW can also actively provide load information to the load information obtaining unit. For example, when the load of the S-GW changes, the S-GW can actively obtain the current load information on the unit from the load information. Specifically, the load can be set to a threshold. When the load exceeds or equals the threshold, the S-GW can actively report the current load information. Further, the load information may include multiple load parameters at the same time, and may also set a load threshold for each load parameter. When the value of the load parameter exceeds or equals the load threshold, the S-GW sends the load to the load information obtaining unit. Information, wherein the load threshold can be dynamically set by the load information obtaining unit. For example, the S-GW can periodically report the load threshold of the load signal, and the load information may not be reported even when the load information is reported. For example, when the S-GW sends a bearer setup request to the load information obtaining unit, the load information may be carried in the bearer setup request and sent to the load information obtaining unit. For example, when the load information obtaining unit sends a bearer setup request to the S-GW, although the bearer setup request does not necessarily have a request for providing load information, the S-GW may carry the load in the bearer setup response returned to the load information obtaining unit. information.

The load information of the S-GW may be a load level, which is used to indicate the current load level of the S-GW. The load information of the S-GW may also be related resource details including multiple resource occupation parameters, and each resource occupancy parameter is used to indicate the percentage of the resource occupied.

In an embodiment of the foregoing S-GW control apparatus, the S-GW control unit may include an S-GW selection unit. After the load information obtaining unit obtains the load information of the at least one S-GW, the S-GW selection unit may first Select one of the S-GWs with the lowest load and select the one with the most load. After the low S-GW, the overload determination unit set in the S-GW control unit determines whether the S-GW with the lowest load has been overloaded, and if not, the bearer setup request set in the S-GW control unit. The processing unit can perform subsequent processing normally, for example, accepting the current bearer setup request, etc., but if the S-GW is overloaded, the bearer setup request processing unit needs to reject some or all of the bearer setup requests, and may even directly reject the current bearer. Establish a request to alleviate the congestion of the S-GW. Of course, if the S-GW is overloaded, the bearer establishment determining unit set in the S-GW control unit can determine whether the current bearer can be established according to the load information, and if so, the bearer setup request processing unit can accept the current bearer. The request is established, otherwise the current bearer setup request is rejected.

In an embodiment of the above S-GW control device, the load information obtaining unit obtains at least one

After the load information of the S-GW, the overload judging unit can judge whether there is overload of the S-GW or judge whether the load of any S-GW is overloaded according to the obtained load information, if the load of all S-GWs is not overloaded or If the load of the specified S-GW is not overloaded, normal subsequent processing may be performed, for example, accepting the current bearer setup request, etc.; if the load of the S-GW is overloaded or the load of the designated S-GW is overloaded, the bearer setup request is performed. The processing unit may reject at least one bearer setup request for the overloaded S-GW, and may even directly reject the current bearer setup request. Of course, if the overload determination unit determines that the load of the S-GW is overloaded or the load of the designated S-GW is overloaded, whether the bearer establishment determination unit set in the S-GW control unit can determine whether the current bearer is based on the load information. It may be established that, if so, the bearer setup request processing unit may accept the current bearer setup request, otherwise, reject the current bearer setup request.

In addition, after the load information obtaining unit obtains the load information of the at least one S-GW, when the load information obtaining unit or other unit receives the first bearer establishment of the user, the S-GW selecting unit may according to the saved S-GW load. Information, selecting an S-GW; when the load information obtaining unit or other unit receives the non-first bearer establishment of the user, the S-GW selection unit is not required to select the S-GW, but according to the saved S-GW The load information is judged by the overload unit whether the selected S-GW is overloaded, and then the bearer setup request processing unit processes the bearer setup request.

It should be noted that each unit of the foregoing S-GW control apparatus may be applied to the MME. The working principle of these units in the MME is the same as that of the S-GW control apparatus described above, and details are not described herein again. Furthermore, the present invention also provides an embodiment of a wireless communication system including at least one S-GW and an MME that controls the at least one S-GW; the S-GW is configured to generate load information, and The load information is provided to the MME; the MME is configured to control the S-GW according to the load information provided by the at least one S-GW. The working mode of the S-GW is the same as that of the above-mentioned load information providing apparatus. The working mode of the MME is the same as that of the S-GW control apparatus described above, and details are not described herein again.

In the embodiment of the present invention, the MME may select an appropriate S-GW according to the load information of the S-GW, and ensure load balancing between the S-GWs; the MME may determine whether there is an S- according to the load information of the S-GW. The GW is overloaded, or judges whether the specified S-GW is overloaded, and reduces the load of the overloaded S-GW by the technical means of rejecting the bearer setup request, thereby improving the reliability of the S-GW; the load information provided by the S-GW can be carried In the existing GTP message, there is no need to make too many changes to the existing network entity, and the implementation cost is low.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, the program When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It is considered as the scope of protection of the present invention.

Claims

Rights request

A load information providing method, comprising:

Generating load information of the S-GW;

The generated load information of the S-GW is provided to the mobility management entity MME.

The load information providing method according to claim 1, wherein the generated

Before the load information of the S-GW is provided to the MME, the method further includes: receiving a load information request sent by the MME; and providing the load information to the MME, specifically: according to the load information request sent by the MME, the generated S The load information of the GW is provided to the MME.

The load information providing method according to claim 1, wherein if the load information is provided to the MME by the serving gateway S-GW, the generated load information of the S-GW is provided to the MME. Specifically, the S-GW periodically provides the generated load information of the S-GW to the MME, or when the load of the S-GW changes, the S-GW provides the generated S-GW load information to the MME. .

The load information providing method according to claim 3, wherein the load change of the S-GW is specifically: the load of the S-GW exceeds or equals a preset load threshold.

The load information providing method according to claim 1, wherein if the load information is provided by the S-GW to the MME, the generated load information of the S-GW is provided to the MME, specifically The S-GW sends a bearer setup request or a bearer setup response carrying the load information of the generated S-GW to the MME.

The load information providing method according to claim 1, wherein if the load information is provided by the S-GW to the MME, the generated load information of the S-GW is provided to the MME, specifically The S-GW sends an extended GPRS Tunneling Protocol GTP message or an independent GTP message carrying the S-GW load information to the MME.

The load information providing method according to claim 6, wherein the extended GTP message is an echo request, an echo response, a Create PDP Context Request, or a Create

PDP Context Response.

The load information providing method according to claim 1, wherein the load information is a load level for indicating a degree of S-GW load if the load information is provided to the MME by the S-GW. , or load-related resource details indicating the percentage of each resource that is occupied.

The load information providing method according to claim 8, wherein the load level or load-related resource detailed information is generated by the S-GW according to a resource occupation situation, and the resource occupancy situation includes at least a bearer number and a grouping. Business processing, data throughput or CPU load.

The load information providing method according to claim 9, wherein the load level is a value in a sequence for indicating a level of the S-GW load.

The load information providing method according to claim 9, wherein the load related resource detailed information includes at least a port number percentage, a packet service processing information percentage, a data throughput percentage, or a CPU load percentage.

12. A method for controlling an S-GW, characterized in that it comprises:

Obtaining load information of at least one S-GW;

The S-GW is controlled based on the obtained load information.

The method for controlling the S-GW according to claim 12, wherein the obtaining the load information of the at least one S-GW comprises:

Requesting load information from the S-GW;

Receiving load information of at least one S-GW feedback.

The S-GW control method according to claim 13, wherein the requesting the load information from the S-GW is: periodically issuing a load information request to the S-GW.

The method for controlling the S-GW according to claim 13, wherein if the request for the load information of the S-GW is sent by the MME to the S-GW, the request for the load information to the S-GW is specifically: The MME sends a bearer setup request carrying the load information request to the S-GW.

The S-GW control method according to claim 13 or 15, wherein if the load information is the MME, the load information received by the at least one S-GW is specifically: the MME receives at least one S- The bearer setup response carrying the load information returned by the GW.

The method for controlling the S-GW according to claim 12, wherein the receiving the load information of the feedback by the at least one S-GW is: receiving the load information that is actively reported by the at least one S-GW.

The method for controlling the S-GW according to claim 17, wherein the receiving the load information that is actively reported by the at least one S-GW is: receiving the load information periodically reported by the at least one S-GW, or Receiving load information reported by at least one S-GW when the load changes.

The method of controlling an S-GW according to claim 12, wherein the obtained negative The information is controlled by the S-GW, and the S-GW is selected from the at least one S-GW according to the obtained load information.

The S-GW control method according to claim 19, wherein the S-GW having the lowest load is the S-GW having the lowest load level or the S-GW having the most remaining resources.

The control method of the service gateway according to claim 19, wherein after selecting the S-GW with the lowest load from the at least one S-GW, the method further comprises: determining whether the selected S-GW is overloaded, if Yes, the current bearer setup request for the selected S-GW is rejected.

The method for controlling an S-GW according to claim 19, wherein after selecting the S-GW with the lowest load from the at least one S-GW, the method further comprises: determining whether the selected S-GW is overloaded, If yes, it is determined whether the current bearer can be established according to the load information, and if yes, accepts the current 7-carrier establishment request, otherwise, rejects the current 7-carrier establishment request.

The control method of the S-GW according to claim 12, wherein the controlling the S-GW according to the obtained load information is: determining whether the load of the specified S-GW is based on the obtained load information Overload, if yes, reject the current bearer setup request for the specified S-GW.

The control method of the S-GW according to claim 12, wherein the controlling the S-GW according to the obtained load information is: determining whether the load of the specified S-GW is based on the obtained load information Overload, if yes, determine whether the current bearer can be established according to the load information, and if yes, accept the current bearer setup request, otherwise, reject the current bearer setup request.

The control method of the S-GW according to claim 12, wherein the load information is a load level for indicating a degree of S-GW load, or a load correlation indicating a percentage of each resource being occupied. Resource details.

26. An S-GW, characterized in that it comprises:

a load information generating unit, configured to generate load information;

The load information providing unit is configured to provide the load information generated by the load information generating unit to the MME.

The S-GW of claim 26, further comprising:

a timer, configured to set a period in which the load information providing unit provides load information;

The load change determination unit is configured to determine whether the load has changed, and when the load change is determined, issue a change in the load to the load information providing unit.

The S-GW according to claim 26, wherein the load information is a load level for indicating a degree of S-GW load, or a load-related resource detailed information indicating a percentage of each resource being occupied. .

29. An MME, characterized in that:

a load information obtaining unit, configured to obtain load information of at least one S-GW;

The S-GW control unit is configured to control the S-GW according to the load information obtained by the load information obtaining unit.

The MME according to claim 29, wherein the load information obtaining unit comprises:

a load information requesting unit, configured to request load information from the S-GW;

The load information receiving unit is configured to receive load information fed back by at least one S-GW.

The MME according to claim 29, wherein the S-GW control unit comprises: an S-GW selection unit, configured to load information obtained from the load information obtaining unit from the at least one S - Select one S-GW in the GW.

The MME according to claim 31, wherein the S-GW control unit further comprises:

An overload determining unit, configured to determine whether the S-GW selected by the S-GW selecting unit is overloaded; and a bearer setup request processing unit, configured to determine, by the overload determining unit, that the S-GW selected by the S-GW selecting unit has been Upon overload, the current bearer setup request for the selected S-GW is rejected.

The MME according to claim 32, wherein the S-GW control unit further includes: a bearer establishment determining unit, configured to determine, in the overload determining unit, the S selected by the S-GW selection unit - When the GW is overloaded, it is determined whether the current bearer can be established according to the load information. If yes, the bearer setup request processing unit accepts the current bearer setup request, otherwise, rejects the current bearer setup request.

34. A wireless communication system, comprising: at least one S-GW and an MME controlling the at least one S-GW;

The S-GW is configured to generate load information, and provide the load information to the MME. The MME is configured to control the S-GW according to load information provided by at least one S-GW.