CN101610494B - Method, system and equipment for realizing overload control or differentiated services - Google Patents

Abstract

Embodiments of the present invention relate to a method, device, system, and user equipment for realizing overload control or differentiated services, wherein the method includes: receiving a request message encapsulated with indication information; the indication information includes message type information or service type information or User category information or service priority information; process the request message according to the indication information in the request message and the obtained overload control policy or differentiated service policy. The embodiment of the present invention receives the request message encapsulated with the indication information, identifies the request message according to the indication information, overcomes a series of problems in the prior art such as the inability to identify the type of the request message, and realizes effective overload control or differentiated service.

Description

Method, system and device for realizing overload control or differentiated service

technical field

The embodiments of the present invention relate to the communication field, and in particular, to a method, device, system and user equipment for realizing overload control or differentiated services.

Background technique

In order to enhance the competitiveness of future networks, the 3rd Generation Partnership Project (3GPP) is researching a brand new evolved network, and FIG. 1 is a schematic diagram of a wireless evolved network architecture in the prior art. As shown in Figure 1, the wireless evolved network includes an evolved UMTS Terrestrial Radio Access Network (Evolved UMTST Terrestrial Radio Access Network, hereinafter referred to as: EUTRAN), which is used to implement all functions related to the wireless of the evolved network; the mobility management network element ( Mobility Management Entity, hereinafter referred to as: MME), is used for mobility management of the control plane, including user context and mobile state management, allocation of user temporary identity, etc.; serving gateway entity (Serving Gateway, hereinafter referred to as: SGW), SGW is 3GPP The user plane anchor point between the access networks is the interface that terminates E-TURAN; the packet data network gateway entity (Packet Data Network Gateway, hereinafter referred to as: PGW) is the user plane between the 3GPP access network and the non-3GPP access network The anchor point is the interface between the termination and the external packet data network (Packet Data Network, hereinafter referred to as: PDN); the policy and charging rule function entity (Policy and Charging Rule Function, hereinafter referred to as: PCRF) is used for policy control decision and flow Charging control function; Home Subscriber Server (hereinafter referred to as: HSS) is used to store user subscription information; serving GPRS support node (Serving GPRSSupport Node, hereinafter referred to as: SGSN) is an entity used for mobility management in 3GPP ; GERAN (GSM Edge Radio Access Network) is the access network part of the previous 3GPP system; the IP service controlled by the operator is the IP service used to serve the UE. It should be noted that the wireless evolution network may not be the final system architecture evolution (System Architecture Evolution, hereinafter referred to as: SAE) system, and this is not limited.

Based on the above network architecture, when the MME is overloaded, the MME sends an overload start message to its associated access network side equipment (such as: eNodeB), requesting the eNodeB to reject certain session requests or service requests, for example, service request messages, response paging service requests, all new Radio Resource Control (Radio Resource Control, hereinafter referred to as: RRC) messages, the RRC messages include TAU request messages and attach request messages, etc., and the eNodeB only allows emergency calls. However, in the prior art, the access network side equipment cannot identify different message types, nor can it obtain the service request information in response to paging, nor can it know whether the current session is an emergency call. Therefore, the prior art cannot achieve effective overload control .

In addition, when it is necessary to perform differentiated services in the access network side equipment, it is also because the access network side cannot recognize the type of the above request message, cannot obtain the service request information in response to paging, and cannot know whether the current session is an emergency call or Other business types, so that effective differentiated services cannot be realized accordingly.

Contents of the invention

Embodiments of the present invention provide a method, device, system and user equipment for realizing overload control or differentiated services, which can realize effective overload control or differentiated services.

An embodiment of the present invention provides a method for implementing overload control or differentiated services, which is applied to a communication system including a mobility management network element MME and an evolved base station eNodeB, wherein the user equipment UE accesses the MME through the evolved base station for communication business, including:

The eNodeB receives a request message encapsulated with indication information sent by the UE; the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used to indicate that the request A message type, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user who initiated the request message belongs to a high-end user or a low-end user;

According to the message type information or service type information or user category information or service priority information carried in the request message by the eNodeB, and the message type information or service information sent by the MME or carried in the request message The overload control policy or differentiated service policy corresponding to the type information or user category information or service priority information processes the request message, and if the overload control policy or differentiated service policy indicates that the request message is rejected, the eNodeB rejects the request message The request message.

An embodiment of the present invention provides a device for realizing overload control or differentiated services, including:

The first receiving module is configured to receive a request message encapsulated with indication information sent by the user equipment UE; the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used for Indicate the type of the request message, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user who initiated the request message belongs to a high-end user or a low-end user;

The access module is configured to, according to the message type information or service type information or user category information or service priority information carried in the request message, and the information related to the information issued by the mobility management network element MME or carried in the request message According to the overload control strategy or differentiated service strategy corresponding to the above message type information or service type information or user category information or service priority information, the request message will be processed. If the overload control strategy or differentiated service strategy indicates that the request message is rejected, then The eNodeB rejects the request message.

An embodiment of the present invention provides a user equipment for implementing overload control or differentiated services, including:

A first encapsulation module, configured to encapsulate indication information in a request message, where the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used to indicate the request message type, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user who initiated the request message belongs to a high-end user or a low-end user;

A sending module, configured to send a request message encapsulated with indication information and carrying an overload control policy or a differentiated service policy to the evolved base station eNodeB, so that the eNodeB can use the message type information or service type information or user category information carried in the request message or service priority information, and an overload control policy or differentiated service issued by the MME or carried in the request message corresponding to the message type information or service type information or user category information or service priority information The policy is to process the request message, and if the overload control policy or the differentiated service policy indicates that the request message is rejected, the eNodeB rejects the request message.

An embodiment of the present invention provides a system for implementing overload control or differentiated services, including a user equipment, an evolved base station, and a mobility management network element MME;

The user equipment includes:

A first encapsulation module, configured to encapsulate indication information in a request message, where the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used to indicate the request message type, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user who initiated the request message belongs to a high-end user or a low-end user;

A sending module, configured to send a request message encapsulated with indication information;

The evolved base station includes:

A first receiving module, configured to receive a request message encapsulated with the indication information;

The access module is configured to: according to the message type information or service type information or user category information or service priority information carried in the request message, and the information related to the message type sent by the MME or carried in the request message information or service type information or user category information or service priority information corresponding to the overload control policy or differentiated service policy, process the request message, if the overload control policy or differentiated service policy indicates that the request message is rejected, the eNodeB rejecting the request message;

The MME is configured to issue an overload control policy or a differentiated service policy to the eNB.

The embodiment of the present invention receives the request message encapsulated with the indication information, identifies the request message according to the indication information, overcomes a series of problems in the prior art such as the inability to identify the type of the request message, and realizes effective overload control or differentiated service.

Description of drawings

FIG. 1 is a schematic diagram of a wireless evolution network architecture in the prior art;

2 is a flow chart of a method for implementing overload control or differentiated services according to Embodiment 1 of the present invention;

3 is a signaling flowchart of a method for implementing overload control or differentiated services in Embodiment 2 of the present invention;

FIG. 4 is a signaling flowchart of a method for implementing overload control or differentiated services in Embodiment 3 of the present invention;

FIG. 5 is a signaling flowchart of a method for implementing overload control or differentiated services according to Embodiment 4 of the present invention;

FIG. 6 is a signaling flowchart of a method for implementing overload control or differentiated services according to Embodiment 5 of the present invention;

FIG. 7 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 6 of the present invention;

FIG. 8 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 7 of the present invention;

FIG. 9 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 8 of the present invention;

FIG. 10 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 9 of the present invention;

FIG. 11 is a schematic diagram of a device for implementing overload control or differentiated services according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of a user equipment according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of a system for implementing overload control or differentiated services according to an embodiment of the present invention.

Detailed ways

The technical solutions of the embodiments of the present invention will be described in further detail below with reference to the drawings and embodiments.

FIG. 2 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 1 of the present invention. This embodiment can be applied to a communication system including an MME and an eNodeB, where a user equipment (UE) accesses the MME through the eNodeB to perform communication services, as shown in FIG. 2 , this embodiment specifically includes the following steps:

Step 101, receiving a request message encapsulated with indication information; the indication information includes message type information or service type information or user category information or service priority information;

Specifically, the instruction information can be encapsulated in the newly added cell of the request message or the existing cell or the extended cell; Temporary Mobile Subscriber Identity, hereinafter referred to as: P-TMSI) or Temporary Mobile Subscriber Identity (Temporary Mobile Subscriber Identity, hereinafter referred to as: TMSI) cell encapsulation instruction information (using the reserved bit of the existing cell or extending the existing cell structure).

Among them, the newly added cell refers to the newly added cell in the message, the existing cell refers to the cell obtained by using the reserved bit of the existing cell in the message, and the extended cell refers to the cell obtained by extending the existing cell. And get the cell.

Step 102: Process the request message according to the indication information in the request message and the obtained overload control strategy or differentiated service strategy; the overload control strategy or differentiated service strategy is issued by the network side device before receiving the request message Or carried in the request message sent by the UE.

The foregoing processing of the request message may include: determining to accept the request message or reject the request message, or routing the request message to other network-side devices.

In this embodiment, by receiving a request message encapsulated with indication information and identifying the request message according to the indication information, a series of problems in the prior art such as inability to identify the type of the request message are overcome, and an effective overload control or differentiated service strategy is realized.

The network side device in the embodiment of the present invention may be MME or SGSN, and the access network side device may be RNC or BSC (GERAN/UTRAN network), or eNodeB (EUTRAN network). The following takes the EUTRAN network as an example to further introduce the technical solutions of the embodiments of the present invention.

FIG. 3 is a signaling flowchart of a method for implementing overload control or differentiated services according to Embodiment 2 of the present invention. This embodiment takes the realization of overload control as an example, as shown in Figure 3, which specifically includes:

Step 201, the UE sends an attach request message to the eNodeB, the attach request message is encapsulated with attach request message type information, which is used to mark the request message as an attach request message; in addition, the attach request message also carries an International Mobile Subscriber Identity (International Mobile Subscriber Identity) Mobile Subscriber Identity, hereinafter referred to as: IMSI), or the original GUTI, the Tracking Area Identity of the last visit (TrackingArea Identity, hereinafter referred to as: TAI), UE capability information, PDN type, protocol configuration options, attachment type and other information;

The type information of the attach request message may be encapsulated in a newly added cell, an existing cell or an extended cell of the attach request message. For example, an information element may be added to indicate the type information of the attach request message, or the message type information may be indicated in a reserved bit in the GUTI, P-TMSI, or TMSI, or the GUTI or other existing information elements may be extended to indicate the message type information.

Step 202, the eNodeB determines whether the MME corresponding to the original GUTI carried in the attach request message is overloaded according to the load status of the associated MME, and if so, determines whether to reject the attach request message according to the overload control policy issued by the MME;

If the overload control policy indicates to reject the attach request message, the eNodeB rejects the attach request of the UE. Otherwise, the attach request may be accepted or the attach request message may be routed to other MMEs that are not overloaded, so as to complete the attach process of the UE.

Before step 201, this embodiment further includes: the eNodeB acquires the message type delivered by the MME and the overload control strategy corresponding to the message type; the eNodeB thus determines the overload control strategy corresponding to the attach request message.

Further, this embodiment may also include the following steps:

Step 203, performing an authentication process among UE, MME and HSS;

Step 204, the process of updating location and inserting subscription data is performed between MME and HSS, registering the address of MME in HSS, and at the same time, HSS inserts subscription data of UE into MME;

Step 205, MME selects PGW according to the default access point name (Access Point Name, hereinafter referred to as: APN) in the subscription data, and sends a creation default bearer request message to SGW, which is used to create a default PDN connection. The provincial bearer request message carries PGW address, EPS bearer ID (Evolved Packet Syetem Bearer Identity) and other information;

Step 206, the SGW creates a new context for the user in the EPS bearer table, and sends a default bearer request message to the PGW at the same time, which carries the SGW address, the SGW user plane tunnel endpoint identifier (Tunnel Endpoint Identifier, hereinafter referred to as: TEID), SGW control plane TEID and other information;

Step 207, if there is a Policy Control and Charging Rules Function (Policy Control and Charging Rules Function, hereinafter referred to as: PCRF) in the network, the PGW interacts with the PCRF to obtain the default policy and charging control (Policy and Charging Control, hereinafter referred to as: PCC) rules;

Step 208, the PGW returns a create default bearer response message to the SGW, the create default bearer response message carries information such as the PGW address, the PGW control plane TEID, the PGW user plane TEID, and the EPS bearer ID;

Step 209, the SGW returns a create default bearer response message to the MME, and the create default bearer response message carries information such as the SGW address and TEID;

Step 210, the MME sends an Attach Accept message to the UE;

Step 211, if the user's subscription data allows interworking with non-3GPP, the MME sends a location update request message to the HSS, and the location update request message carries the APN and PGW address information of the default PDN connection used by the UE;

Step 212, the HSS saves the APN and PGW address information used by the UE, and returns a location update response message to the MME.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the attach request message type information is encapsulated in the attach request message and sent to the eNodeB, so that the eNodeB recognizes the received request message as an attach request message according to the attach request message type information, and further determines whether to Accepting the attach request message overcomes the problem in the prior art that the attach request message cannot be identified, and realizes effective overload control.

This embodiment is also applicable to differentiated services, and effective differentiated services are realized according to identifying that the request message is an attach request message and obtaining a differentiated service policy.

FIG. 4 is a signaling flowchart of a method for implementing overload control or differentiated services according to Embodiment 3 of the present invention. This embodiment takes the realization of overload control as an example, as shown in Figure 4, which specifically includes:

Step 301, UE arrives at a new tracking area (Tracking Area, hereinafter referred to as: TA) or routing area (Routing Area, hereinafter referred to as: RA), and sends a tracking area update (Tracking Area Update, hereinafter referred to as: TAU) to the eNodeB A TAU request message requesting message type information, or sending a RAU request message encapsulated with routing area update (Routing Area Update, hereinafter referred to as: RAU) request message type information to RNC/BSC; the following takes eNodeB and network side processing as an example describe.

Step 302. The eNodeB determines whether to reject the TAU request message or the RAU request message according to the request message type information carried in the TAU request message or the RAU request message, and pre-acquires the overload control policy issued by the MME; if the overload control policy indicates rejection For the TAU request message or RAU request message, the eNodeB may reject the TAU request message, or route the TAU request message or RAU request message to other MMEs that are not overloaded.

In step 301, the TAU request message type information may be encapsulated in a newly added cell or an existing cell or an extended cell of the TAU request message, for example, encapsulated in the GUTI or P-TMSI or TMSI carried by the TAU request message; Reasonably, the RAU request message type information may be encapsulated in a new or existing IE or extended IE of the RAU request message, for example, in the P-TMSI or TMSI carried in the RAU request message.

Further, if it is necessary to distinguish whether TAU/RAU is periodic TAU/RAU or normal TAU/RAU, an information element can be added to the TAU request message or RAU request message, or the existing information element or extended information element in the message can be used Encapsulation update type, which identifies TAU/RAU as periodic TAU/RAU or normal TAU/RAU (normal TAU/RAU refers to TAU or RAU initiated by UE arriving at a new TA or RA area, or due to inter-system movement Initiated TAU or RAU, etc. except periodic TAU/RAU TAU/RAU.); The update type can also be encapsulated in the GUTI or P-TMSI or TMSI carried in the TAU request message or RAU request message;

Or, use different request message type information to distinguish periodic TAU/RAU or normal TAU/RAU, specifically as follows: when the TAU is a periodic TAU, the TAU request message type information in step 301 is specifically the first TAU request message Type information; when the TAU is a normal TAU, the TAU request message type information in step 301 is specifically the second TAU request message type information; similarly, when the RAU is a periodic RAU, the RAU request message type information in step 301 Specifically, it is the first RAU request message type information; when the RAU is a normal RAU, the RAU request message type information in step 301 is specifically the second RAU request message type information.

Before step 301, this embodiment further includes: the eNodeB obtains the message type delivered by the MME and the overload control policy corresponding to the message type; the eNodeB thus determines the overload control policy corresponding to the TAU/RAU request message.

After step 302, this embodiment may also include:

Step 303, the target-side MME learns the source-side MME according to the user's GUTI, sends a user context information request message to the source-side MME, and requests to obtain user context information;

Step 304, the source-side MME sends a context response message carrying a user context to the UE, the user context including bearer context, mobility management (Mobility Management, hereinafter referred to as: MM) context, SGW signaling address and TEID and other information;

Step 305, the target-side MME executes an authentication process;

Step 306, the target-side MME sends a context response message to the source-side MME;

Step 307, the target side MME updates the user context information in the SGW;

Step 308, the target-side MME updates the user's MME information in the HSS, and cancels the source-side MME information;

Step 309, the target side MME sends a TAU acceptance message or an RAU acceptance message to the UE;

Step 310, the UE returns a TAU complete message or an RAU complete message to the target MME.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the TAU or RAU request message type information is encapsulated in the TAU or RAU request message and sent to the eNodeB, so that the eNodeB recognizes the received request message as a TAU or RAU request message according to the TAU or RAU request message type information, and further Whether to accept the TAU or RAU request message is determined according to the obtained overload control strategy, which overcomes the problem in the prior art that the TAU or RAU request message cannot be identified, and realizes effective overload control.

This embodiment is also applicable to differentiated services, and effective differentiated services are realized according to the identified request message as a TAU/RAU request message and the obtained differentiated service policy.

FIG. 5 is a signaling flowchart of a method for implementing overload control or differentiated services according to Embodiment 4 of the present invention. This embodiment takes the realization of overload control as an example, as shown in Figure 5, which specifically includes:

Step 401, the UE sends a service request message encapsulated with service request message type information to the eNodeB;

Step 402: The eNodeB determines whether to reject the service request message according to the service request message type information carried in the service request message and the overload control policy issued by the MME; if the overload control policy indicates that the service request message is rejected, the eNodeB rejects the service request message message or route the service request message to other MMEs that are not overloaded.

In step 401, the type information of the service request message may be encapsulated in a new or existing IE or extended IE of the service request message, such as GUTI or P-TMSI or TMSI carried in the service request message.

Further, the service request message initiated by the UE may be for different purposes, for example, there is a service request message initiated for uplink data flow, and there is also a service request message initiated for responding to paging.

In order to distinguish service request messages of different purposes, this embodiment may encapsulate different service request message type information in service request messages of different purposes. When the service request message is initiated due to the upstream data flow, the service request message type information is specifically The first service request message type information (represented by Service Request); when the service request message was initiated due to response paging, the service request message type information was specifically the second service request message type information (represented by Paging Response) .

In order to distinguish service request messages with different purposes, this embodiment can also add an information element to the service request message, or use the existing information element of the service request message to encapsulate the purpose indication information, such as the GUTI or P- The TMSI or the TMSI encapsulates usage indication information, and the usage indication information identifies whether the service request message is initiated by the upstream data flow or in response to paging. Specifically, when the service request message is initiated due to the upstream data flow, the purpose indication information is specifically the first purpose indication information (expressed with Data); when the service request message is initiated due to a response to paging, the purpose indication information Specifically, it is the second purpose indication information (expressed by Paging Response).

Before step 401, this embodiment further includes: the eNodeB obtains the message type delivered by the MME and the overload control strategy corresponding to the message type; the eNodeB thus determines the overload control strategy corresponding to the service request message.

After step 402, this embodiment may also include:

Step 403, execute the authentication process;

Step 404: The MME sends a context initial establishment request message to the eNodeB, the context initial establishment request message carries information such as S-GW address, uplink S1-TEID, bearer quality of service, context security information, MME signal connection ID, etc., and is used to notify the eNodeB Activate all S1 and Radio bearers carried by the activated EPS;

Step 405, the eNodeB initiates a radio bearer establishment process, in which a notification that the non-voice bearer has been restored is carried, and the uplink path is connected at this time, and the UE can send uplink data;

Step 406, UE sends uplink data to SGW and PGW;

Step 407, the eNodeB sends a context initial establishment complete message to the MME, and the context initial establishment complete message carries eNodeB address, downlink S1-TEID and other information;

Step 408, the MME sends a bearer update request message to the SGW, the bearer update request message carries eNodeB address, downlink S1-TEID, delayed downlink data indication, radio access type (RadioAccess Type, hereinafter referred to as: RAT) type and other information;

Step 409, the SGW compares the current RAT with the last RAT, and notifies the PGW of the current RAT if there is a change;

Step 410, the PGW interacts with the PCRF to modify the IP-Connectivity Access Network (IP-Connectivity Access Network, hereinafter referred to as: IP CAN) session;

Step 411, the PGW sends a bearer update response message to the SGW;

Step 412, the SGW forwards the bearer update response message to the MME.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the service request message type information is encapsulated in the service request message and sent to the eNodeB, so that the eNodeB can identify the received request message according to the service request message type information, and further determine whether to accept the service request according to the obtained overload control policy The message overcomes the problem that the service request message cannot be identified in the prior art, and realizes effective overload control.

This embodiment is also applicable to differentiated services, and realizes effective differentiated services according to identifying that the request message is a service request message and obtaining the differentiated service policy.

FIG. 6 is a signaling flowchart of a method for implementing overload control or differentiated services according to Embodiment 5 of the present invention. As shown in Figure 6, this embodiment specifically includes:

Step 501, the UE initiates an emergency service, and sends a service request message encapsulated with service type information to the eNodeB, and the service type information indicates that the session of the service request message is an emergency session;

Step 502, eNodeB receives the service request message encapsulated with service type information, and judges whether the service corresponding to the service request message is an emergency service according to the service type information, and if so, according to the obtained overload control strategy and/or differentiation delivered by the MME service policy, process the service request message; if the overload control policy and/or differentiated service policy indicate to reject the service request message, eNodeB rejects the service request message, otherwise accepts or routes the service request message to other non-overloaded or available The MME of the service.

Before step 501, this embodiment further includes: the eNodeB obtains the service type delivered by the MME and the overload control policy corresponding to the service type; the eNodeB thus determines the overload control policy corresponding to the emergency service.

This embodiment may further include steps 403 to 412 described in Embodiment 4.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the service type information is encapsulated in a service request message and sent to the eNodeB, so that the eNodeB can identify whether the service corresponding to the received request message is an emergency service according to the service type information, and further according to the obtained overload control strategy and/or difference The service policy is used to determine whether to accept the service request message, which overcomes the problem in the prior art that it is impossible to know whether the current session is an emergency call, and realizes effective overload control and/or differentiated services.

FIG. 7 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 6 of the present invention. As shown in Figure 7, this embodiment specifically includes:

Step 601, the eNodeB receives the start message sent by the MME, the start message carries the user category, and the overload control strategy and/or differentiated service strategy corresponding to the user category;

In this embodiment, each user is divided into different user categories, and the user categories can be high-end users and low-end users, or 1st-level users and 2nd-level users, and different overload control strategies and/or differences are adopted for different types of users. For example: when a high-end user initiates a service request message, the overload control strategy and/or differentiated service strategy is to accept the user's service request message; when a low-end user initiates a service The service policy is to reject the service request message or route the service request message to other MMEs.

Step 602, the UE obtains user category information; this step may also be performed before step 601.

User category and user category information are different concepts in the present embodiment, as can be seen from the description in step 601, user category divides each user, as user category is high-end user and low-end user; In this step, user category information refers to In this embodiment, the user category to which the UE belongs, for example, the user category information may be a high-end user or a low-end user.

Specifically, the MME acquires the subscription data of the UE, which includes user category information; the MME encapsulates the user category information in a new information element of a Non-Access Stratum (Non-Access Stratum) message or an extended existing information In the reserved bit of cell or existing cell, the NAS message encapsulated with user category information can be sent to UE through attach process, tracking area update process, routing area update process, service request process or global temporary identifier reassignment process.

Step 603, the eNodeB receives the request message encapsulated with the user category information sent by the UE;

Step 604, the eNodeB determines the user category to which the UE belongs according to the user category information and the user category obtained in step 601;

Step 605, the eNodeB processes the request message according to the user category to which the UE belongs and the overload control strategy and/or differentiated service strategy corresponding to the user category. Processing the request message includes: determining to accept the request message or reject the request message, or routing the request message to other MMEs.

Further, in this embodiment, taking the attach process as an example, a method for the UE to obtain user category information (step 602) is introduced, specifically including:

Step 6021, the UE sends an attach request message to the eNodeB, the attach request message carries NAS information such as IMSI, original GUTI, last accessed TAI, UE capability information, PDN type, protocol configuration options, and attach type;

Step 6022, the eNodeB selects an available MME for the UE, and completes the attach procedure for the UE;

Step 6023, execute authentication process between UE, MME and HSS;

Step 6024, the MME and the HSS execute the process of updating the location and inserting the subscription data, register the address of the MME in the HSS, and at the same time, the HSS inserts the subscription data of the UE into the MME, and the subscription data includes user category information;

Step 6025, MME, SGW, PGW and PCRF complete the default bearer establishment process;

Step 6026: The MME sends an attach accept message to the UE, which carries information elements such as GUTI, TAI list, and user category information allocated by the network side equipment for the UE; the user category information is recorded by the MME according to the UE subscription data in the HSS Determined by the user category information;

Step 6027, if the subscription data of the UE allows interworking with non-3GPP, the MME sends a location update request message to the HSS, and the location update request message carries the APN and PGW address information of the default PDN connection used by the UE;

Step 6028, the HSS saves the APN and PGW address information used by the UE, and returns a location update response message to the MME.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the user category information is encapsulated in a request message and sent to the eNodeB, so that the eNodeB determines whether to accept the request message according to the user category information, the obtained user category and its overload control policy and/or differentiated service policy, Effective overload control and/or differentiated services are achieved.

FIG. 8 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 7 of the present invention. As shown in Figure 8, this embodiment specifically includes:

Step 701, the eNodeB receives the start message sent by the MME, the start message carries the service priority, and the overload control policy and/or differentiated service policy corresponding to the service priority;

In this embodiment, each service belongs to each service priority, and different overload control strategies and/or differentiated service strategies are adopted for services of different service priorities, for example: when the MME is overloaded, for services above a certain service priority All services are accepted, and services lower than the priority of the service are rejected or routed to other MMEs; or, specific processing principles are given for services with specific service priorities, and services with certain service priorities are accepted. Services with certain service priorities are rejected, and services with other service priorities will be routed to other MMEs.

Step 702, the eNodeB receives the request message encapsulated with the service priority information sent by the UE;

In this embodiment, service priority and service priority information are different concepts. As can be seen from the description in step 701, service priority divides each service; business priorities.

In step 703, the eNodeB determines the service priority of the current service according to the service priority information, and processes the request message according to the service priority obtained in step 701 and its corresponding overload control policy and/or differentiated service policy. Processing the request message includes: determining to accept the request message or reject the request message, or routing the request message to other MMEs.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the service priority information is encapsulated in a request message and sent to the eNodeB, so that the eNodeB determines whether to accept the service priority according to the service priority information, the obtained service priority and its overload control policy and/or differentiated service policy request messages, enabling efficient overload control and/or differentiated services.

FIG. 9 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 8 of the present invention. As shown in Figure 9, this embodiment specifically includes:

Step 801, the eNodeB receives the start message sent by the MME, the start message carries the user equipment status category, and the overload control policy and/or differentiated service policy corresponding to the user equipment status category;

In this embodiment, different overload control strategies and/or differentiated service strategies are adopted for UEs in different states. For example, when the MME is overloaded, all request messages initiated by UEs in the active state are accepted, and UEs in the idle state Initiated request messages are rejected or routed to other MMEs.

Step 802, the UE sends a request message to the eNodeB;

Step 803, the eNodeB receives the above request message, judges and obtains the status information of the UE, and can judge whether the UE is in the active state or the idle state according to whether there is an Iu connection or an S1 connection;

Step 804, the eNodeB determines the user equipment status category to which the current status information belongs according to the UE status information, and processes the request message according to the user equipment status category obtained in step 801 and its corresponding overload control strategy and/or differentiated service strategy . Processing the request message includes: determining to accept the request message or reject the request message, or routing the request message to other MMEs.

When the MME resumes normal use, the MME sends a notification message of recovery to the eNodeB.

In this embodiment, the eNodeB determines whether to accept the request message according to the status information of the UE, the obtained user equipment status category and its overload control strategy and/or differentiated service strategy, and realizes effective overload control and/or differentiated service.

FIG. 10 is a flowchart of a method for implementing overload control or differentiated services according to Embodiment 9 of the present invention. As shown in Figure 10, this embodiment specifically includes:

Step 901. The UE receives a policy notification message sent by the MME or forwarded by the MME through the eNodeB. The policy notification message may be a NAS message, which carries UE user category information, and/or user category or service priority or user equipment Status category or service type or message type, and overload control strategy or differentiated service strategy corresponding to user category or service priority or user equipment status category or service type or message type; the information carried can be added by adding one or several It can also be carried by extending existing cells, such as P-TMSI, network capability information, GUTI and other existing cells, and can also be carried in reserved bits of existing cells;

Step 902, the UE sends a request message to the eNodeB;

When the policy notification message carries the user category and the overload control policy or differentiated service policy corresponding to the user category, the request message encapsulates the user category information, and/or the user category, and the overload control policy corresponding to the user category Control strategy or differentiated service strategy;

When the policy notification message carries the service priority and the overload control policy or differentiated service policy corresponding to the service priority, the request message can also encapsulate the service priority information, the service priority, and the service priority corresponding to the service priority. Overload control strategy or differentiated service strategy;

When the policy notification message carries the service type and the overload control policy or differentiated service policy corresponding to the service type, the request message may also encapsulate the service type and the overload control policy or differentiated service policy corresponding to the service type ;

When the policy notification message carries the message type and the overload control policy or differentiated service policy corresponding to the message type, the request message may also encapsulate the message type and the overload control policy or differentiated service policy corresponding to the message type .

Step 903, the user category to which the eNodeB root user category information belongs, and the overload control strategy or differentiated service strategy corresponding to the user category, process the request message;

Or, the eNodeB processes the request message according to the service priority to which the service priority information belongs, and the overload control policy or differentiated service policy corresponding to the service priority;

Or, the eNodeB processes the request message according to the service type and the overload control policy or differentiated service policy corresponding to the service type;

Alternatively, the eNodeB processes the request message according to the message type and the overload control policy or differentiated service policy corresponding to the message type.

When the policy notification message in step 901 carries the user equipment status category and the overload control policy or differentiated service policy corresponding to the user equipment status category, the indication information encapsulated in the request message in step 902 is the user equipment status category, and An overload control strategy or a differentiated service strategy corresponding to the user equipment status category; before step 903, the eNodeB also includes judging and obtaining the status information of the user equipment, and it can be judged that the UE is in an active state or whether there is an Iu connection or an S1 connection. Idle state; step 903 is specifically: process the request message according to the user equipment status category to which the user equipment status information belongs, and the overload control strategy and/or differentiated service strategy corresponding to the user equipment status category. The processing of the request message includes: determining to accept the request message or reject the request message, or to route the request message to other MMEs.

In this embodiment, the indication information is encapsulated in a request message and sent to the eNodeB, so that the eNodeB determines whether to accept the request message according to the indication information and the obtained overload control policy and/or differentiated service policy, thereby realizing effective overload control and/or or differentiated services.

Fig. 11 is a schematic diagram of an apparatus for implementing overload control or differentiated services according to an embodiment of the present invention. This embodiment may be a separate functional entity, or may be integrated into an access network side device. For example, in an EUTRAN network, this embodiment integrates In the eNodeB. As shown in FIG. 11 , this embodiment specifically includes: a first receiving module 11, configured to receive a request message encapsulated with indication information; the indication information includes message type information or service type information or user category information or service priority information; The access module 12 is configured to process the request message according to the indication information in the request message and the obtained overload control policy or differentiated service policy.

The first receiving module 11 may be specifically a second receiving module, configured to receive a request message for encapsulating indication information in a newly added cell or an existing cell or an extended cell of the request message; the first receiving module 11 may also be specifically The third receiving module is configured to receive the request message for encapsulating indication information in the globally unique temporary identifier or P-TMSI or TMSI included in the request message.

This embodiment may also include: a fourth receiving module 13, configured to receive the start message sent by the network side device, the start message carries user category or service priority or user equipment status category or message type or service type, and Overload control strategy or differentiated service strategy corresponding to user category or service priority or user equipment status category or message type or service type.

In this embodiment, by receiving a request message encapsulated with indication information and identifying the request message according to the indication information, a series of problems in the prior art such as inability to identify the type of the request message are overcome, and effective overload control or differentiated services are realized.

FIG. 12 is a schematic diagram of a user equipment according to an embodiment of the present invention. As shown in FIG. 12 , this embodiment specifically includes: a first encapsulation module 21, configured to encapsulate indication information in a request message, the indication information including message type information or service Type information or user category information or service priority information; sending module 22, configured to send a request message encapsulated with indication information.

The first encapsulation module 21 can be specifically the second encapsulation module, and is used for encapsulating the indication information in the newly added cell or the existing cell or the extended cell of the request message; the first encapsulation module 21 can also be specifically the third encapsulation module A module, configured to encapsulate the indication information in the globally unique temporary identifier or P-TMSI or TMSI included in the request message.

This embodiment may further include: an acquisition module 23, configured to acquire user category information.

The acquisition module 23 may be specifically a first acquisition module, configured to receive a policy notification message sent by the network side device or forwarded by the network side device through the access network side device, the policy notification message carrying the user category information of the user equipment, And/or, user category or service priority or user equipment status category or message type or service type, and an overload control strategy or difference corresponding to the user category or service priority or user equipment status category or message type or service type customized service strategy.

In this embodiment, by encapsulating the indication information in the request message and identifying the request message according to the indication information, a series of problems in the prior art such as inability to identify the type of the request message are overcome, and effective overload control or differentiated services are realized.

FIG. 13 is a schematic diagram of a system for implementing overload control or differentiated services according to an embodiment of the present invention. As shown in FIG. 13 , this embodiment specifically includes a user equipment 31 and an eNodeB 32 .

The user equipment 31 may include: a first encapsulation module 311, configured to encapsulate indication information in a request message, the indication information including message type information or service type information or user category information or service priority information; a sending module 312 for Send a request message encapsulated with indication information.

The eNodeB32 may include: a first receiving module 321, configured to receive a request message encapsulated with indication information; an access module 322, configured to convert the request message according to the indication information in the request message and the obtained overload control strategy or differentiated service strategy to process.

This embodiment may further include MME33, configured to obtain subscription data including user category information, and combine user category information, and/or user category or service priority or user equipment status category or message type or service type, and the The overload control policy or differentiated service policy corresponding to the user category or service priority user equipment status category or message type or service type is encapsulated in the new or existing or extended cells of the NAS message, and the NAS The message is sent to the user device.

The foregoing user equipment may be any user equipment described in the user equipment in the embodiment of the present invention, and the foregoing eNodeB may be any eNodeB described in the apparatus for realizing overload control in the embodiment of the present invention.

In this embodiment, by encapsulating the indication information in the request message and identifying the request message according to the indication information, a series of problems in the prior art such as inability to identify the type of the request message are overcome, and effective overload control or differentiated services are realized.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the The steps of the above-mentioned method embodiments are included, and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, not to limit them; although the embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand : It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical aspects of the embodiments of the present invention. The spirit and scope of the programme.

Claims (30)

1. A method for realizing overload control or differentiated services, which is applied to a communication system including a mobility management network element MME and an evolved base station eNodeB, wherein a user equipment UE accesses the MME through an evolved base station to perform communication services, its characteristics is to include: The eNodeB receives a request message encapsulated with indication information sent by the UE; the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used to indicate that the request A message type, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user equipment that initiated the request message belongs to a high-end user or a low-end user; According to the message type information or service type information or user category information or service priority information carried in the request message by the eNodeB, and the message type information or service information sent by the MME or carried in the request message type information or user category information or service priority information corresponding to the overload control policy or differentiated service policy, process the request message, if the overload control policy or differentiated service policy indicates that the request message is rejected, the The eNodeB rejects the request message. 2. The method for realizing overload control or differentiated service according to claim 1, characterized in that receiving the request message encapsulated with indication information is specifically: receiving a newly added cell or an existing cell or an extended cell in the request message A request message encapsulating indication information in a cell. 3. The method for realizing overload control or differentiated service according to claim 2, characterized in that the receiving the request message for encapsulating indication information in the existing cell or extended cell of the request message is specifically: receiving the request message in The globally unique temporary identifier or packet temporary mobile subscriber identity P-TMSI or temporary mobile subscriber identity TMSI included in the request message encapsulates the request message for indicating information. 4. The method for implementing overload control or differentiated services according to claim 2 or 3, characterized in that before receiving the request message, it further comprises: the eNodeB obtains the message type or service type issued by the MME , and an overload control strategy or a differentiated service strategy corresponding to the message type or service type. 5. The method for realizing overload control or differentiated services according to claim 4, wherein receiving the request message encapsulated with message type information is specifically: receiving the request message encapsulated with message type information sent by the user equipment, the The request message is an attach request message, and the message type information is type information of the attach request message. 6. The method for realizing overload control or differentiated services according to claim 4, wherein receiving the request message encapsulated with message type information is specifically: receiving the request message encapsulated with message type information sent by the user equipment, and the The request message is a tracking area update TAU request message, and the message type information is the type information of the TAU request message; or, receiving a request message encapsulated with message type information sent by the user equipment, the request message is a routing area update RAU request message, the message type information is the type information of the RAU request message. 7. The method for realizing overload control or differentiated service according to claim 6, characterized in that, an update type is also encapsulated in the newly added cell or existing cell or extended cell, and the update type Identify the TAU/RAU as periodic TAU/RAU or normal TAU/RAU. 8. The method for realizing overload control or differentiated services according to claim 6, wherein when the TAU is a periodic TAU, the type information of the TAU request message is the first TAU request message type information; when the TAU When it is a normal TAU, the type information of the TAU request message is the second TAU request message type information; When the RAU is a periodic RAU, the type information of the RAU request message is the first RAU request message type information; when the RAU is a normal RAU, the type information of the RAU request message is the second RAU request message type information. 9. The method for implementing overload control or differentiated services according to claim 4, wherein receiving the request message encapsulated with message type information is specifically: receiving the request message encapsulated with message type information sent by the user equipment, the The request message is a service request message, and the message type information is the type information of the service request message; When the service request message is a service request message initiated due to an uplink data flow, the type information of the service request message is specifically the first service request message type information; when the service request message is a service request message initiated due to a response to paging In the case of a service request message, the type information of the service request message is the second service request message type information. 10. The method for implementing overload control or differentiated services according to claim 4, wherein receiving the request message encapsulated with message type information is specifically: receiving the request message encapsulated with message type information sent by the user equipment, the The request message is a service request message, and the message type information is the type information of the service request message; Use indication information for distinguishing the purpose of the service request message is also encapsulated in the newly added cell or existing cell or extended cell, when the service request message is a service request message initiated due to an upstream data flow , the usage indication information is specifically first usage indication information; when the service request message is a service request message initiated due to paging response, the usage indication information is specifically second usage indication information. 11. The method for implementing overload control or differentiated services according to claim 2, further comprising: receiving, by the eNodeB, a start message sent by the MME before the receiving the request message, in the start message It carries the user category or service priority or user equipment status category, and the overload control strategy or differentiated service strategy corresponding to the user category or service priority or user equipment status category. 12 . The method for implementing overload control or differentiated services according to claim 11 , further comprising: before receiving the request message, the user equipment acquires user category information. 13 . 13. The method for implementing overload control or differentiated services according to claim 12, wherein the acquiring the user category information by the user equipment comprises: The MME encapsulates the user category information in a new information element or an existing information element or an extended information element of a non-access stratum NAS message, and sends the NAS message encapsulated with the user category information to the user equipment. 14. The method for implementing overload control or differentiated services according to claim 13, wherein the receiving the request message encapsulated with indication information is specifically: receiving the request message encapsulated with user category information or service priority sent by the user equipment Information request message. 15. The method for implementing overload control or differentiated services according to claim 2, further comprising: before receiving the request message, the user equipment receives the policy sent by the MME or forwarded by the MME through the eNodeB A notification message, wherein the policy notification message carries user category information of the user equipment, and/or user category or service priority or user equipment status category or service type or message type, and information related to the user category or service priority Or an overload control policy or a differentiated service policy corresponding to a user equipment status category, service type, or message type, where the user category information is the user category to which the user equipment belongs. 16. The method for implementing overload control or differentiated services according to claim 15, wherein the receiving the request message encapsulated with indication information is specifically: receiving the request message encapsulated with user category information, user category, and a request message of an overload control policy or a differentiated service policy corresponding to the user category, or receiving a request message sent by the user equipment that encapsulates service priority information, service priority, and an overload control policy corresponding to the service priority Or a request message for a differentiated service policy, the user category information is the user category to which the user equipment belongs, and the service priority information is the service priority to which the current service belongs; The processing the request message specifically includes: processing the request message according to the user category corresponding to the user category information and the overload control strategy or differentiated service strategy corresponding to the user category; or, according to the service priority The service priority corresponding to the information, and the overload control strategy or differentiated service strategy corresponding to the service priority will process the request message. 17. The method for implementing overload control or differentiated services according to claim 15, wherein the receiving the request message encapsulated with indication information is specifically: receiving the service type information encapsulated with service type information, service type and A request message for an overload control strategy or a differentiated service strategy corresponding to the service type, where the service type information is the service type to which the current service belongs. 18. The method for implementing overload control or differentiated services according to claim 15, wherein the receiving the request message encapsulated with indication information is specifically: receiving the message type information encapsulated with message type information, message type and A request message of an overload control strategy or a differentiated service strategy corresponding to the message type, and the message type information is the message type to which the request message belongs. 19. A device for realizing overload control or differentiated services, characterized by comprising: The first receiving module is configured to receive a request message encapsulated with indication information sent by the user equipment UE; the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used for Indicate the type of the request message, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user equipment that initiated the request message belongs to a high-end user or a low-end user; The access module is configured to, according to the message type information or service type information or user category information or service priority information carried in the request message, and the information related to the information issued by the mobility management network element MME or carried in the request message According to the overload control policy or differentiated service policy corresponding to the message type information or service type information or user category information or service priority information, process the request message, if the overload control policy or differentiated service policy indicates that the request is rejected message, reject the request message. 20. The device for implementing overload control or differentiated services according to claim 19, characterized in that the device is a separate functional entity, or is integrated in an evolved base station eNodeB. 21. The device for implementing overload control or differentiated services according to claim 20, characterized in that, the first receiving module is specifically configured to receive newly added cells or existing cells or extended cells in the request message A request message encapsulating the indicated information in . 22. The device for implementing overload control or differentiated services according to claim 20, wherein the first receiving module is specifically configured to receive the global unique temporary identifier or group temporary mobile user identity included in the request message Identifies the request message for encapsulating indication information in the P-TMSI or Temporary Mobile Subscriber Identity TMSI. 23. The device for implementing overload control or differentiated services according to claim 20, further comprising: a fourth receiving module, configured to receive the start message sent by the MME, the start message carrying the user category or service priority or user equipment status category or message type or service type, and an overload control strategy or differentiated service strategy corresponding to the user category or service priority or user equipment status category or message type or service type. 24. A user equipment for implementing overload control or differentiated services, characterized by comprising: A first encapsulation module, configured to encapsulate indication information in a request message, where the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used to indicate the request message type, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user equipment that initiated the request message belongs to a high-end user or a low-end user; A sending module, configured to send a request message encapsulated with indication information and carrying an overload control policy or a differentiated service policy to the evolved base station eNodeB, so that the eNodeB can use the message type information or service type information or user category information carried in the request message or service priority information, and an overload control strategy or a differentiated service strategy corresponding to the message type information or service type information or user category information or service priority information issued by the MME or carried in the request message, The request message is processed, and if the overload control policy or differentiated service policy indicates that the request message is rejected, the eNodeB rejects the request message. 25. The user equipment according to claim 24, wherein the first encapsulation module is specifically configured to encapsulate the indication information in a new information element, an existing information element, or an extended information element of the request message. 26. The user equipment according to claim 24, wherein the first encapsulation module is specifically configured to encapsulate the indication information into a globally unique temporary identifier or group temporary mobile user identity P included in the request message - TMSI or Temporary Mobile Subscriber Identity TMSI. 27. The user equipment according to claim 24, further comprising: an acquiring module, configured to acquire the user category information. 28. The user equipment according to claim 27, wherein the acquiring module is specifically configured to receive a policy notification message sent by the MME or forwarded by the MME through the eNodeB, the policy notification message carrying User category information of user equipment, and, user category or service priority or user equipment status category or message type or service type, and corresponding to the user category or service priority or user equipment status category or message type or service type An overload control strategy or a differentiated service strategy, the user category information is the user category to which the user equipment belongs. 29. A system for realizing overload control or differentiated service, characterized in that it includes user equipment, evolved base station and mobility management network element MME; The user equipment includes: A first encapsulation module, configured to encapsulate indication information in a request message, where the indication information includes message type information or service type information or user category information or service priority information, and the message type information is used to indicate the request message type, the service type information is used to indicate the type of service involved in the request message, and the user category information is used to indicate that the user equipment that initiated the request message belongs to a high-end user or a low-end user; A sending module, configured to send a request message encapsulated with indication information; The evolved base station includes: A first receiving module, configured to receive a request message encapsulated with the indication information; The access module is configured to: according to the message type information or service type information or user category information or service priority information carried in the request message, and the information related to the message type sent by the MME or carried in the request message information or service type information or user category information or service priority information corresponding to the overload control policy or differentiated service policy, process the request message, if the overload control policy or differentiated service policy indicates that the request message is rejected, then rejecting the request message; The MME is configured to issue an overload control policy or a differentiated service policy to the eNB. 30. The system for implementing overload control or differentiated services according to claim 29, wherein the MME is further configured to acquire subscription data including the user category information, and store the user category information, and/or , user category or service priority or user equipment status category or message type or service type, and an overload control strategy or differentiated service strategy corresponding to the user category or service priority or user equipment status category or message type or service type encapsulating in a new information element or an existing information element or an extended information element of a non-access stratum NAS message, and sending the NAS message to the user equipment, and the user category information is the user to which the user equipment belongs category.

Images