WO2014205621A1 - Overload control method and apparatus - Google Patents

Overload control method and apparatus Download PDF

Info

Publication number
WO2014205621A1
WO2014205621A1 PCT/CN2013/077755 CN2013077755W WO2014205621A1 WO 2014205621 A1 WO2014205621 A1 WO 2014205621A1 CN 2013077755 W CN2013077755 W CN 2013077755W WO 2014205621 A1 WO2014205621 A1 WO 2014205621A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
network node
user equipment
request message
access
Prior art date
Application number
PCT/CN2013/077755
Other languages
French (fr)
Chinese (zh)
Inventor
陆伟
舒林
李大伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2013/077755 priority Critical patent/WO2014205621A1/en
Publication of WO2014205621A1 publication Critical patent/WO2014205621A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/06Access restriction performed under specific conditions based on traffic conditions

Abstract

Embodiments of the present invention disclose an overload control method and apparatus, which relate to the field of communications and can effectively alleviate congestion of a network device when the network device is congested. A specific solution comprises: a first core network node in a core network receiving an access request message from a user equipment; determining that at least one node in the core network is overloaded, and sending an access rejection message to the user equipment, the access rejection message comprising a first cause value code and duration of a timer, the access rejection message instructing the user equipment to resend an access request message to the first code network node when the timer passes the duration and times out, and the first cause value code being a cause value code for rejecting the access request of the user equipment. The present invention is used in a process in which a user equipment accesses a network.

Description

 Overload control method and device

Technical field

 The present invention relates to the field of communications, and in particular, to an overload control method and apparatus. Background technique

 In a wireless communication network system, when a large number of terminals access the network at the same time, network equipment may be congested. At this time, if the network device rejects the access request of the terminal, the terminal may continuously try to access the network again, further accumulating congestion of the network device.

 In the prior art, according to the latest version of the protocol, the network device can reject the access request of the terminal, and instruct the terminal to set a timer, so that the terminal re-initiates the access request after the timeout expires, so as to prevent the terminal from continuously retrying. Into the network, thereby alleviating network equipment congestion.

 However, the network device designed based on the protocol of the earlier version does not support the timing function. Even if the network device sends a timer indication to the terminal, the terminal cannot identify the terminal, and thus the terminal cannot continuously try to re-attempt to access the network, thereby effectively mitigating the network device. congestion. Summary of the invention

 Embodiments of the present invention provide an overload control method and apparatus, which can effectively alleviate congestion of a network device when the network device is congested.

 In order to achieve the above object, the embodiment of the present invention uses the following technical solutions:

 A first aspect of the embodiments of the present invention provides an overload control method, including: receiving, by a first core network node in a core network, an access request message from a user equipment;

The first core network node determines that at least one node in the core network is overloaded, The first core network node sends an access reject message to the user equipment, where the access reject message includes a first cause value code and a duration of the timer, where the access reject message indicates that the user equipment is After the timeout expires, the timer resends the access request message to the first core network node, where the first cause value code is a reason value code for rejecting the access request of the user equipment.

 With reference to the first aspect, in a possible implementation, the first core network node determines that at least one node in the core network is overloaded, including:

 The first core network node receives a resource response message from a second core network node in the core network;

 The first core network node determines that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message.

 With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, the first core network node is a serving general wireless packet service support node.

SGSN, the second core network node is a gateway general wireless packet service support node GGSN; the timer is T3302;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, the first core network node is a mobility management network element MME, and the second core network node is a gateway GW; The device is T3402;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, the first core network node sends an access reject message to the user equipment. The method further includes:

 The first core network node receives the version information of the user equipment from the access network node, where the version information is received by the access network node from the user equipment, and the version information is used to indicate to the Determining, by the first core network node, a version of the user equipment that sends the access request;

 The first core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and sets the duration of the timer.

 With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, after the first core network node receives the access request message from the user equipment, the method further includes:

 The first core network node sends an initial setup context request to the access network node, so that the access network node sends a radio resource control protocol RRC connection reconfiguration request to the user equipment, so that the user equipment sends the The RRC connection reconfiguration of the version information of the user equipment is responsive to the access network node, and the access network node is further configured to generate an initialization setup context response including the version information of the user equipment;

 The first core network node receives an initialization setup context response from the access network node that includes the version information of the user equipment;

 The first core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and sets the duration of the timer.

 With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, before the first core network node receives the access request message from the user equipment, the method further includes:

 The first core network node receives a service request message or a packet data protocol PDP activation request message from the user equipment;

The first core network node determines that at least one node in the core network is overloaded, and the first core network node sends a packet temporary mobile user identity P-TMSI Assigning a command to the user equipment, where the P-TMSI redistribution command carries a routing area identifier RAI;

 The receiving, by the first core network node, an access request message from the user equipment, specifically includes:

 Receiving, by the first core network node, the route update request message from the user equipment, where the route update request message is that the user equipment receives the

After the P-TMSI redistribution command is initiated, when the RAI carried in the P-TMSI redistribution command is different from the RAI received by the user equipment from the system broadcast;

 The first cause value code is a reason value code for rejecting the routing update request of the user equipment.

 With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, before the first core network node receives the access request message from the user equipment, the method further includes:

 The first core network node receives a service request message or a packet data network PDN connection request message from the user equipment;

 The first core network node determines that at least one node in the core network is overloaded, and the first core network node sends a globally unique temporary identifier GUTI reassignment command to the user equipment, where the GUTI reassignment command carries The tracking area identifies the TAI list; the first core network node receives the access request message from the user equipment, specifically:

 The first core network node receives a tracking area update request message from the user equipment, where the tracking area update request message is sent by the user equipment after the user equipment receives the GUTI reassignment command. The TAI of the system broadcast is not included in the TAI list;

 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.

With reference to the first aspect and the foregoing possible implementation manner, in another possible implementation manner, before the first core network node receives the access request message from the user equipment, the method further includes: The first core network node receives a service request message from the user equipment; the first core network node determines that at least one node in the core network is overloaded, and the first core network node sends a service rejection message to The user equipment, the service rejection message includes a second cause value code, where the second cause value code is a reason for the first core network node to reject the service request of the user equipment according to the version information. Value code

 The receiving, by the first core network node, an access request message from the user equipment, specifically includes:

 The first core network node receives the attach request message from the user equipment, where the attach request message is sent by the user equipment after receiving the service reject message including the second cause value code. .

 The second aspect of the embodiments of the present invention further provides an overload control method, including: the user equipment sends an access request message to a first core network node in a core network; and the user equipment receives the first core network node. The access reject message includes a first cause value code and a duration of the timer, where the access reject message is after the first core network node receives the access request message, And determining, when the at least one node in the core network is overloaded, the first cause value code is a reason value code for rejecting an access request of the user equipment;

 The user equipment starts the timer according to the first cause value code, and resends the access request message to the first core network node after the timer expires after the timer expires.

 With reference to the second aspect, in a possible implementation, after the first core network node determines that at least one node in the core network is overloaded after receiving the access request message, specifically:

 Determining, by the first core network node, that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message;

The resource response message is received by the first core network node from a second core network node in the core network. With reference to the foregoing possible implementation manner of the second aspect, in another possible implementation manner, the first core network node is an SGSN, and the second core network node is a GGSN; the timer is T3302;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 With reference to the foregoing possible implementation manners of the second aspect, in another possible implementation manner, the first core network node is an MME, and the second core network node is a GW; the timer is T3402;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 With the foregoing possible implementation manner of the second aspect, in another possible implementation, the user equipment starts the timer according to the first cause value code, specifically: when the user equipment receives the When the number of the access reject message exceeds a preset threshold, the user equipment starts the timer according to the first cause value code;

 The user equipment sends at least one of the access request messages to the first core network node.

 With the foregoing possible implementation manner of the second aspect, in another possible implementation, before the user equipment receives the access reject message from the first core network node, the method further includes:

 The user equipment sends the version information of the user equipment to the first core network node by using an access network node, so that the first core network node determines that the first cause value code is rejected according to the version information. a reason value code of the access request of the user equipment, and setting the duration of the timer.

Combining the above possible implementations of the second aspect, in another possible implementation The method further includes: before the user equipment receives an access reject message from the first core network node, the method further includes:

 Receiving, by the user equipment, an RRC connection reconfiguration request from an access network node, where the RRC connection reconfiguration request is sent by the access network node after receiving an initialization setup context request from the first core network node ;

 Transmitting, by the user equipment, an RRC connection reconfiguration response including the version information of the user equipment to the access network node, to enable the access network node to generate an initialization of the version information including the user equipment Establishing a context response, and sending the initialization establishment context response including the version information of the user equipment, so that the first core network node determines, according to the version information, that the first cause value code is to reject the A reason value code of the access request of the user equipment, and setting the duration of the timer.

 With the foregoing possible implementation manner of the second aspect, in another possible implementation, before the user equipment sends the access request message to the first core network node, the method further includes:

 Sending, by the user equipment, a service request message or a PDP activation request message to the first core network node;

 The user equipment receives a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI reassignment command is the first core network node. After receiving the service request message or the PDP activation request message, determining that at least one node in the core network is overloaded; the user equipment compares the RAI carried in the P-TMSI reassignment command Receiving, from the user equipment, an RAI broadcasted by the system;

 And the user equipment sends the access request message to the first core network node, where the method includes: if the RAI carried in the P-TMSI redistribution command is different from the RAI received by the user equipment from the system, the user The device sends the route update request message to the first core network node.

Combining the above possible implementations of the second aspect, in another possible implementation The method further includes: before the user equipment sends the access request message to the first core network node, the method further includes:

 Sending, by the user equipment, a service request message or a PDN connection request message to the first core network node;

 Receiving, by the user equipment, a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is that the first core network node receives the service After the request message or the PDN connection request message is determined, it is determined that the at least one node in the core network is overloaded; the user equipment determines whether the TAI list includes a TAI received by the user equipment from a system broadcast;

 And the user equipment sends the access request message to the first core network node, where the method includes: if the TAI list does not include the TAI that the user equipment receives from the system broadcast, the user equipment sends the tracking area update request Message to the first core network node.

 With the foregoing possible implementation manner of the second aspect, in another possible implementation, before the user equipment sends the access request message to the first core network node, the method further includes:

 The user equipment sends a service request message to the first core network node; the user equipment receives a service rejection message from the first core network node, where the service rejection message includes a second cause value code, The second cause value code is a reason value code that is determined by the first core network node to reject the service request of the user equipment according to the version information, where the service rejection message is that the first core network node receives the After the service request message is sent, determining that at least one node in the core network is overloaded;

 And the user equipment sends the access request message to the first core network node, where the user equipment sends the attach request message to the first core network node according to the second cause value code.

A third aspect of the embodiments of the present invention provides a core network node, including: a receiving unit, configured to receive an access request message from a user equipment; a determining unit, configured to determine that at least one node in the core network is overloaded; and a sending unit, configured to send an access reject message to the user equipment after the determining unit determines that at least one node in the core network is overloaded The access reject message includes a first cause value code and a duration of the timer, where the access reject message indicates that the user equipment resends the access request after the timer expires after the timer expires. Sending a message to the core network node, the first cause value code is a reason value code for rejecting an access request of the user equipment.

 With reference to the third aspect, in a possible implementation, the receiving unit is further configured to receive a resource response message from a second core network node in the core network, where the determining unit is further configured to perform Determining, by the receiving unit, the resource limitation indication included in the resource response message, determining that at least one node in the core network is overloaded.

 With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation manner, the core network node is an SGSN, and the second core network node is a GGSN; the timer is T3302;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation manner, the core network node is an MME, the second core network node is a GW, and the timer is T3402;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation, the receiving unit is further configured to send an access reject message to the sending unit to The user equipment is configured to receive version information of the user equipment from the access network node, where the version information is received by the access network node from the user equipment, and the version information is used to indicate to the Sending, by the first core network node, a version of the user equipment of the access request;

 The determining unit is further configured to determine, according to the version information received by the receiving unit, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

 With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation, the sending unit is further configured to send an initialization setup context request after the receiving unit receives an access request message from the user equipment. To the access network node, so that the access network node sends a RRC connection reconfiguration request to the user equipment, so that the user equipment sends an RRC connection including the version information of the user equipment. Reconfiguring a response to the access network node, and causing the access network node to generate an initialization setup context response including the version information of the user equipment;

 The receiving unit is further configured to receive an initialization establishment context response of the version information that includes the user equipment from the access network node;

 The determining unit is further configured to determine, according to the version information received by the receiving unit, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

 With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation, the receiving unit is further configured to receive, before receiving the access request message from the user equipment, the user from the user a service request message or a PDP activation request message of the device;

 The sending unit is further configured to: if the determining unit determines that at least one node in the core network is overloaded, send a P-TMSI reassignment command to the user equipment, where the P-TMSI reassignment command carries an RAI ;

The receiving unit is further configured to receive the route update request message from the user equipment, where the route update request message is that the user equipment receives the After the P-TMSI reassignment command sent by the sending unit, the RAI carried in the P-TMSI reassignment command is initiated when the RAI is different from the RAI broadcast by the user equipment;

 The first cause value code is a reason value code for rejecting the routing update request of the user equipment.

 With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation, the receiving unit is further configured to receive, before receiving the access request message from the user equipment, the user from the user a service request message or a PDN connection request message of the device;

 The sending unit is further configured to: if the determining unit determines that at least one node in the core network is overloaded, send a GUTI reassignment command to the user equipment, where the GUTI reassignment command carries a TAI list;

 The receiving unit is further configured to receive a tracking area update request message from the user equipment, where the tracking area update request message is after the user equipment receives the GUTI reassignment command sent by the sending unit, Transmitting when the user equipment receives a TAI broadcasted by the system that is not included in the TAI list;

 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.

 With reference to the third aspect and the foregoing possible implementation manner, in another possible implementation, the receiving unit is further configured to receive, before receiving the access request message from the user equipment, the user from the user Service request message of the device;

 The sending unit is further configured to: if the determining unit determines that at least one node in the core network is overloaded, send a service reject message to the user equipment, where the service reject message includes a second cause value code, where The second cause value code is a reason value code that the first core network node determines to reject the service request of the user equipment according to the version information;

The receiving unit is further configured to receive the attach request message from the user equipment, where the attach request message is used by the user equipment to receive the second cause value code sent by the sending unit. Sent after the service rejection message. A fourth aspect of the embodiments of the present invention further provides a user equipment, including: a sending unit, configured to send an access request message to a first core network node in a core network;

 a receiving unit, configured to receive an access reject message from the first core network node, where the access reject message includes a first cause value code and a duration of the timer, where the access reject message is the first After receiving the access request message, the core network node determines that the at least one node in the core network is overloaded, and the first cause value code is a reason value code for rejecting the access request of the user equipment. ;

 An opening unit, configured to enable the timer according to the first cause value code received by the receiving unit;

 The sending unit is further configured to resend the access request message to the first core network node after the timer that is turned on by the open unit expires after the timeout period.

 With reference to the fourth aspect, in a possible implementation, after the first core network node determines that the at least one node in the core network is overloaded, after receiving the access request message, specifically:

 Determining, by the first core network node, that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message;

 The resource response message is received by the first core network node from a second core network node in the core network.

 With reference to the fourth aspect, in a possible implementation manner, the first core network node is an SGSN, the second core network node is a GGSN, the timer is T3302, and the access request message is an attach request. The message, the access reject message is an attach reject message;

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation manner, the first core network node is an MME, and the second core network node is a GW; The timer is T3402;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation manner, the enabling unit is further configured to: when the receiving unit receives the number of the access reject message exceeds a preset threshold H 'J turns on the timer according to the first reason value code;

 The sending unit is further configured to send at least one of the access request messages to the first core network node.

 With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation manner, the sending unit is further configured to: before the receiving unit receives an access reject message from the first core network node, Sending, by the access network node, the version information of the user equipment to the first core network node, so that the first core network node determines, according to the version information, that the first cause value code is to reject the user equipment. The reason code of the access request, and set the duration of the timer.

 With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation manner, the receiving unit is further configured to receive, before receiving, an access denied message from the first core network node, An RRC connection reconfiguration request of the network node, where the RRC connection reconfiguration request is sent by the access network node after receiving an initialization establishment context request from the first core network node;

The sending unit is further configured to send an RRC connection reconfiguration response including the version information of the user equipment to the access network node, so that the access network node generates the identifier that includes the user equipment. The initialization of the version information establishes a context response, and sends the initialization establishment context response including the version information of the user equipment, so that the first core network node determines the first cause value code according to the version information. a reason value code for rejecting the access request of the user equipment, and setting the setting The duration of the timer.

 With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation, the sending unit is further configured to send a service request before sending the access request message to the first core network node. a message or PDP activation request message to the first core network node;

 The receiving unit is further configured to receive a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI reassignment command is the first After receiving the service request message or the PDP activation request message sent by the sending unit, the core network node determines that at least one node in the core network is overloaded;

 The receiving unit is further configured to receive an RAI from a system broadcast;

 The user equipment further includes:

 a comparing unit, configured to compare the RAI carried in the P-TMSI redistribution command received by the receiving unit with an RAI received by the receiving unit from the system;

 The sending unit is further configured to: if the comparing unit compares that the RAI carried in the P-TMSI reassignment command is different from the RAI received by the receiving unit from the system, sending the routing update Requesting a message to the first core network node.

 With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation, the sending unit is further configured to send a service request before sending the access request message to the first core network node. a message or PDN connection request message to the first core network node;

 The receiving unit is further configured to receive a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is received by the first core network node After the service request message or the PDN connection request message sent by the sending unit is determined, when it is determined that at least one node in the core network is overloaded;

 The receiving unit is further configured to receive a TAI from a system broadcast;

The user equipment further includes: a determining unit, configured to determine whether the TAI list received by the receiving unit includes a TAI that is received by the receiving unit from the system broadcast;

 The sending unit is further configured to: if the determining unit determines that the TAI list does not include the TAI that the receiving unit receives from the system broadcast, send the tracking area update request message to the first core Network node.

 With reference to the fourth aspect and the foregoing possible implementation manner, in another possible implementation, the sending unit is further configured to send a service request before sending the access request message to the first core network node. Message to the first core network node;

 The receiving unit is further configured to receive a service reject message from the first core network node, where the service reject message includes a second cause value code, where the second cause value code is the first core network node And determining, by the version information, a reason value code for rejecting the service request of the user equipment, where the service rejection message is determined by the first core network node after receiving the service request message sent by the sending unit Transmitted when at least one node in the core network is overloaded;

 The sending unit is further configured to send the attach request message to the first core network node according to the second cause value code received by the receiving unit.

 A fifth aspect of the embodiments of the present invention provides a core network node, including: a receiver, configured to receive an access request message from a user equipment;

 a processor, configured to determine that at least one node in the core network is overloaded; and a transmitter, configured to send an access reject message to the user equipment after the processor determines that at least one node in the core network is overloaded The access reject message includes a first cause value code and a duration of the timer, where the access reject message indicates that the user equipment resends the access request after the timer expires after the timer expires. Sending a message to the core network node, the first cause value code is a reason value code for rejecting an access request of the user equipment.

 With reference to the fifth aspect, in a possible implementation, the receiver is further configured to receive a resource response message from a second core network node in the core network;

The processor is further configured to: according to the resource response message received by the receiver A resource limited indication included in the determining that at least one node in the core network is overloaded. With reference to the fifth aspect and the first possible implementation manner of the fifth aspect, the core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 With reference to the fifth aspect and the foregoing possible implementation manner, in another possible implementation manner, the core network node is an MME, the second core network node is a GW, and the timer is T3402;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 With reference to the fifth aspect and the foregoing possible implementation manner, in another possible implementation manner, the receiver is further configured to: before the sending, by the sender, an access reject message to the user equipment, receiving the access The version information of the user equipment of the network node, the version information is received by the access network node from the user equipment, and the version information is used to send the access to the first core network node. The requested version of the user equipment;

 The processor is further configured to determine, according to the version information received by the receiver, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

With reference to the fifth aspect and the foregoing possible implementation manner, in another possible implementation, the transmitter is further configured to send an initialization setup context request after the receiver receives an access request message from the user equipment. To the access network node, so that the access network node sends a RRC connection reconfiguration request to the use And the user equipment, so that the user equipment sends an RRC connection reconfiguration response including the version information of the user equipment to the access network node, so that the access network node generates a location that includes the user equipment. The initialization of the version information establishes a context response; the receiver is further configured to receive an initialization establishment context response of the version information that includes the user equipment from the access network node;

 The processor is further configured to determine, according to the version information received by the receiver, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

 With reference to the fifth aspect and the foregoing possible implementation manner, in another possible implementation manner, the receiver is further configured to receive, before receiving the access request message from the user equipment, the user from the user a service request message or a PDP activation request message of the device;

 The transmitter is further configured to: if the processor determines that at least one node in the core network is overloaded, send a P-TMSI reassignment command to the user equipment, where the P-TMSI reassignment command carries an RAI ;

 The receiver is further configured to receive the route update request message from the user equipment, where the route update request message is that the user equipment receives the P-TMSI reassignment command sent by the sender After the RAI carried in the P-TMSI redistribution command is different from the RAI that the user equipment receives from the system broadcast,

 The first cause value code is a reason value code for rejecting the routing update request of the user equipment.

 With reference to the fifth aspect and the foregoing possible implementation manner, in another possible implementation manner, the receiver is further configured to receive, before receiving the access request message from the user equipment, the user from the user a service request message or a PDN connection request message of the device;

The transmitter is further configured to: if the processor determines that at least one node in the core network is overloaded, send a GUTI reassignment command to the user equipment, where the GUTI reassignment command carries a TAI list; The receiver is further configured to receive a tracking area update request message from the user equipment, where the tracking area update request message is after the user equipment receives the GUTI reassignment command sent by the sender, Transmitting when the user equipment receives a TAI broadcasted by the system that is not included in the TAI list;

 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.

 With reference to the fifth aspect and the foregoing possible implementation manner, in another possible implementation manner, the receiver is further configured to receive, before receiving the access request message from the user equipment, the user from the user Service request message of the device;

 The transmitter is further configured to: if the processor determines that at least one node in the core network is overloaded, send a service reject message to the user equipment, where the service reject message includes a second cause value code, where The second cause value code is a reason value code that the first core network node determines to reject the service request of the user equipment according to the version information;

 The receiver is further configured to receive the attach request message from the user equipment, where the attach request message is that the user equipment receives the second cause value code sent by the sender Sent after the service rejection message.

 A sixth aspect of the embodiments of the present invention further provides a user equipment, including: a transmitter, configured to send an access request message to a first core network node in a core network; and a receiver, configured to receive the first An access reject message of the core network node, where the access reject message includes a first cause value code and a duration of the timer, where the access reject message is that the first core network node receives the access request After the message is sent, when the at least one node in the core network is determined to be overloaded, the first cause value code is a reason value code for rejecting the access request of the user equipment;

 a processor, configured to enable a timer according to the first cause value code received by the receiver;

The transmitter is further configured to resend the access request message to the first core network node after the timer that is started by the processor expires after the timeout. With reference to the sixth aspect, in a possible implementation, after the first core network node determines that at least one node in the core network is overloaded, after receiving the access request message, specifically:

 Determining, by the first core network node, that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message;

 The resource response message is received by the first core network node from a second core network node in the core network.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation manner, the first core network node is an SGSN, and the second core network node is a GGSN; the timer is T3302;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation manner, the first core network node is an MME, the second core network node is a GW, and the timer is T3402;

 The access request message is an attach request message, and the access reject message is an attach reject message;

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation manner, the processor is further configured to: when the number of the access reject messages received by the receiver exceeds a preset threshold The first cause value code starts the timer, and the transmitter is further configured to send at least one of the access request message to the first core network node.

With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation manner, the transmitter is further configured to receive, at the receiver, the first core network Sending, by the access network node, the version information of the user equipment to the first core network node, so that the first core network node determines the first reason according to the version information, before the access reject message of the node The value code is a reason value code for rejecting the access request of the user equipment, and setting the duration of the timer.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation manner, the receiver is further configured to receive the access before receiving the access reject message from the first core network node. RRC connection reconfiguration request of the network node,

The RRC connection reconfiguration request is sent by the access network node after receiving an initialization setup context request from the first core network node;

 The transmitter is further configured to send an RRC connection reconfiguration response including the version information of the user equipment to the access network node, to enable the access network node to generate the The initialization of the version information establishes a context response, and sends the initialization establishment context response including the version information of the user equipment, so that the first core network node determines the first cause value code according to the version information. The reason value code for rejecting the access request of the user equipment, and setting the duration of the timer.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation, the transmitter is further configured to send a service request before sending the access request message to the first core network node. a message or PDP activation request message to the first core network node;

 The receiver is further configured to receive a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI redistribution command is the first After receiving the service request message or the PDP activation request message sent by the sender, the core network node determines that at least one node in the core network is overloaded;

 The receiver is further configured to receive an RAI from a system broadcast;

The processor is further configured to compare the RAI carried in the P-TMSI redistribution command received by the receiver with the receiver receiving the broadcast from the system RAI;

 The transmitter is further configured to: if the processor compares that the RAI carried in the P-TMSI reassignment command is different from the RAI received by the receiver from the system, sending the routing update Requesting a message to the first core network node.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation, the transmitter is further configured to send a service request before sending the access request message to the first core network node. a message or PDN connection request message to the first core network node;

 The receiver is further configured to receive a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is received by the first core network node After the service request message or the PDN connection request message sent by the sender is determined, it is determined that at least one node in the core network is overloaded;

 The receiver is further configured to receive a TAI from a system broadcast;

 The processor is further configured to determine whether the TAI received by the receiver includes a TAI that is received by the receiver from the system broadcast;

 The transmitter is further configured to: if the processor determines that the TAI list does not include the TAI that the receiver receives from the system broadcast, send the tracking area update request message to the first core Network node.

 With reference to the sixth aspect and the foregoing possible implementation manner, in another possible implementation, the transmitter is further configured to send a service request before sending the access request message to the first core network node. Message to the first core network node;

 The receiver is further configured to receive a service reject message from the first core network node, where the service reject message includes a second cause value code, where the second cause value code is the first core network node Determining, by the version information, a reason value code of the service request of the user equipment, the service rejection message is determined by the first core network node after receiving the service request message sent by the sender Transmitted when at least one node in the core network is overloaded;

The transmitter is further configured to: according to the second cause value code received by the receiver Sending the attach request message to the first core network node.

 The overload control method and apparatus provided by the embodiment of the present invention, the first core network node in the core network receives an access request message from the user equipment; the first core network node determines that at least one node in the core network is overloaded, and the sending access is rejected. The message to the user equipment, the access reject message includes the first cause value code and the duration of the timer, and the access reject message indicates that the user equipment resends the access request message to the first core network node after the timer expires. The first cause value code is a reason value code for rejecting the access request of the user equipment. Compared with the prior art, when the network device is congested, the user equipment continuously tries to access the network again. The first core network node can control the user equipment to pause the attempt to access the network within the timer duration by using the reason code and the duration of the timer. , can effectively alleviate network equipment congestion.

DRAWINGS

 In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a number of embodiments of the present invention, and those skilled in the art will be able to obtain other drawings based on these drawings without paying for inventive labor.

1 is a flowchart of an overload control method according to Embodiment 1 of the present invention; FIG. 2 is a flowchart of an overload control method according to Embodiment 2 of the present invention; FIG. 3 is an overload control according to Embodiment 3 of the present invention; FIG. 4 is a flowchart of another overload control method according to Embodiment 3 of the present invention; FIG. 5 is a flowchart of an overload control method according to Embodiment 4 of the present invention; FIG. 6 is a flowchart of Embodiment 4 of the present invention; FIG. 7 is a schematic diagram of a composition of a core network node according to Embodiment 5 of the present invention; FIG. 8 is a schematic diagram of a composition of a user equipment according to Embodiment 6 of the present invention; A schematic diagram of the composition of another user equipment in Embodiment 6 of the present invention; FIG. 10 is a schematic diagram of the composition of a core network node in the embodiment of the present invention FIG. 11 is a schematic structural diagram of a user equipment according to Embodiment 8 of the present invention. detailed description

 The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

 The various techniques described herein can be used in a variety of wireless communication systems, such as current

2G, 3G communication systems and next-generation communication systems, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA, Time Division Multiple) Access) system, Wideband Code Division Multiple Access (WCDMA), Frequency Division Multiple Access (FDMA), Frequency Division Multiple Addressing (OFDMA), Orthogonal Frequency-Division Multiple Access (OFDMA) System, single carrier FDMA (SC-FDMA) system, General Packet Radio Service (GPRS) system, Long Term Evolution (LTE) system, and other such communication systems.

Various aspects are described herein in connection with a terminal and/or base station and/or base station controller. The user equipment, which may be a wireless terminal or a wired terminal, may be a device that provides voice and/or data connectivity to the user, a handheld device with wireless connectivity, or other processing device connected to the wireless modem. The wireless terminal can communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and with a mobile terminal The computers, for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network. For example, personal communication services (PCS, Personal Communication Service ) Telephone, cordless phone, session-initiated SIP (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), and other devices. A wireless terminal may also be called a system, a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile, a Remote Station, an Access Point, Remote Terminal, Access Terminal, User Terminal, User Agent, User Device, or User Equipment.

 A base station (e.g., an access point) can be a device in the access network that communicates with the wireless terminal over one or more sectors over the air interface. The base station can be used to convert the received air frame to the IP packet as a router between the wireless terminal and the rest of the access network, wherein the remainder of the access network can include an Internet Protocol (IP) network. The base station can also coordinate attribute management of the air interface. For example, the base station may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolved base station in LTE (NodeB or eNB or e-NodeB, evolutional Node B), the invention is not limited.

 The base station controller may be a base station controller (BSC) in GSM or CDMA, or may be a radio network controller (RNC) in WCDMA, which is not limited by the present invention.

 In addition, the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this context is merely an association that describes the associated object, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists separately, and both A and B exist, exist alone B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship. Example 1

An embodiment of the present invention provides an overload control method, as shown in FIG. 1 , including: 5101. The first core network node in the core network receives an access request message from the user equipment.

 It should be noted that the overload control method provided by the embodiment of the present invention can be applied to a Global System of Mobile communication (GSM) system, a Universal Mobile Telecommunications System (UMTS), and a long-term evolution (Long). Term Evolved, LTE) system.

 Specifically, when the method in this embodiment is applied to a GSM system or a UMTS system, the first core network node is a Serving General Packet Radio Service Support Node (SGSN), and the second core network node is a gateway. The General Packet Radio Service Support Node (GGSN); the timer is T3302.

 The access request message is an attach request message, and the access reject message is an attach reject message; or the access request message is a route update request message, and the access reject message is a route update reject message.

 When the method of the embodiment is applied to the LTE system, the first core network node is a mobility management entity (MME), and the second core network node is a gateway (GateWay, GW), where the GW may include: Gateway (Packet GateWay, PGW) and Signaling Gateway (SGW); The timer is T3402.

 The access request message is an attach request message, and the access reject message is an attach reject message; or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 The first core network node determines that at least one node in the core network is overloaded, and the first core network node sends an access reject message to the user equipment, where the access reject message includes the first cause value code and the duration of the timer. The access reject message indicates that the user equipment resends the access request message to the first core network node after the timer expires, and the first cause value code is a reason value code for rejecting the access request of the user equipment.

Exemplarily, the first core network node may determine the core network by using the following method Whether there is overload of the core network node: the first core network node receives the resource response message from the second core network node; and determines that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message.

 Further optionally, the first core network node may further obtain a resource response message from the second core network node by sending control signaling to the second core network node; if the first core network node does not receive the received message within a predetermined time The resource response message of the second core network node, the first core network node determines that at least one node in the core network is overloaded.

 Further, in an application scenario of the embodiment of the present invention, the overload control method provided in this embodiment may be applied to a GSM system or a UMTS system.

 In this application scenario, before the first core network node receives the access request message from the user equipment, the method of the embodiment of the present invention may further include: the first core network node receiving the service request message or the packet data from the user equipment. protocol

(PDP Packet Data Protocol, PDP) activates the request message; if at least one node in the core network is overloaded, the first core network node sends a packet Temporary Mobile Subscriber Identity (P-TMSI) The P-TMSI redistribution command carries a Routing Area Identity (RAI).

 It should be noted that, in the application scenario, the first core network node receives the access request message from the user equipment, where the first core network node receives the route update request message from the user equipment, and the route update request message. After the P-TMSI reassignment command is received by the user equipment, when the RAI carried in the P-TMSI reassignment command is different from the RAI that the user equipment receives from the system broadcast, the first cause value code is specifically to reject the user. The reason value code for the route update request of the device.

 Further, in another application scenario of the embodiment of the present invention, the overload control method provided in this embodiment may be applied to an LTE system.

In this application scenario, before the first core network node receives the access request message from the user equipment, the method of the embodiment of the present invention may further include: a first core network section Point to receive service request message or packet data network from user equipment

(Packet Data Network, PDN) connection request message; if at least one node in the core network is overloaded, the first core network node sends a Globally Unique Temporary Identity (GUTI) reassignment command to the user equipment, and the GUTI redistributes The command carries the Tracking Area Identity (TAI) 歹' J table.

 It should be noted that, in the application scenario, the first core network node receives the access request message from the user equipment, where the first core network node receives the tracking area update request message from the user equipment, and the tracking area is updated. The request message is sent by the user equipment after receiving the GUTI reassignment command, when the user equipment receives the TAI that is not included in the TAI list, and the first reason value code is the reason for rejecting the tracking area update request of the user equipment. Value code.

 Further, in another application scenario of the embodiment of the present invention, the overload control method provided in this embodiment may be applied to the GSM system or the UMTS system; or the overload control method provided in this embodiment may be applied to the LTE system.

 In this application scenario, before the first core network node receives the access request message from the user equipment, the method of the embodiment of the present invention may further include: the first core network node receiving the service request message from the user equipment; At least one node in the network is overloaded, the first core network node sends a service reject message to the user equipment, and the service reject message includes a second cause value code, and the second cause value code is a rejection determined by the first core network node according to the version information. The reason code for the service request of the user device.

 It should be noted that, in this application scenario, the first core network node receives the access request message from the user equipment, where the first core network node receives the attach request message from the user equipment, and the attach request message is the user. The device sends after receiving the service reject message containing the second cause value code.

The overload control method provided by the embodiment of the present invention, the first core network node in the core network receives an access request message from the user equipment; the first core network node determines that at least one node in the core network is overloaded, and sends an access reject message to User equipment, access denied The message includes the first reason value code and the duration of the timer, and the access reject message indicates that the user equipment resends the access request message to the first core network node after the timer expires, and the first cause value code is the rejecting user. The reason code for the access request of the device. Compared with the prior art, when the network device is congested, the user equipment continuously tries to access the network again. The first core network node can control the user equipment to pause the attempt to access the network within the timer duration by using the reason code and the duration of the timer. , can effectively alleviate network equipment congestion. Example 2

 An embodiment of the present invention provides an overload control method. As shown in FIG. 2, the method includes: S201: A user equipment sends an access request message to a first core network node in a core network.

 The first core network node, the second core network node, the access request message, and the like mentioned in this embodiment may refer to the specific description in the other method embodiments of the present invention, and details are not described herein again.

 Further, when the method of this embodiment is applied to the GSM system or the UMTS system, before the user equipment sends the access request message to the first core network node, the method of the embodiment of the present invention may further include: the user equipment sends the service request message. Or the PDP activation request message to the first core network node; the user equipment receives the P-TMSI reassignment command from the first core network node, the P-TMSI reassignment command carries the RAI, and the P-TMSI reassignment command is the first core network. After receiving the service request message or the PDP activation request message, the node is initiated when at least one node in the core network is overloaded; the user equipment compares the RAI carried in the P-TMSI redistribution command with the RAI of the user equipment received by the system.

The user equipment sends an access request message to the first core network node, which may be: if the RAI carried in the P-TMSI redistribution command is different from the RAI received by the user equipment from the system, the user equipment sends a route update request message. To the first core network Node.

 Further, when the method of the embodiment is applied to the LTE system, before the user equipment sends the access request message to the first core network node, the method of the embodiment of the present invention may further include: the user equipment sends a service request message or a PDN connection. Requesting a message to the first core network node; the user equipment receives the GUTI reassignment command from the first core network node, and the GUTI reassignment command carries the TAI list, and the GUTI reassignment command is that the first core network node receives the service request message or After the PDN connection request message is initiated, when at least one node in the core network is overloaded; the user equipment determines whether the TAI list contains the TAI received by the user equipment from the system broadcast.

 The user equipment sends an access request message to the first core network node, which may be: if the TAI list does not include the TAI that the user equipment receives from the system broadcast, the user equipment sends a tracking area update request message to the first core network node. .

 5202. The user equipment receives an access reject message from the first core network node, where the access reject message includes a first cause value code and a duration of the timer, and the access reject message is that the first core network node receives the access request. After the message is determined, when the at least one node in the core network is overloaded, the first cause value code is a reason value code for rejecting the access request of the user equipment.

 Exemplarily, in the GSM system or the UMTS system, the access request message is an attach request message, and the access reject message is an attach reject message; or, the access request message is a route update request message, and the access reject message is a route update reject Message, the preset timer is T3302.

 In the LTE system, the access request message is an attach request message, and the access reject message is an attach reject message; or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message, preset timing The device is Τ3402.

 The first reason value code is specifically: #95 or #96.

S203: The user equipment starts a timer according to the first reason value code, and resends the access request message to the first core network node after the timer expires and times out. Specifically, the user equipment starts the timer according to the first reason value code and the duration of the timer, and may be: when the number of the access reject message received by the user equipment exceeds a preset threshold, the user equipment is according to the first The cause value code and the duration of the timer start the timer; wherein, the user equipment sends the at least one access request message to the first core network node.

 In the overload control method provided by the embodiment of the present invention, the user equipment sends an access request message to the first core network node in the core network, and receives an access reject message from the first core network node, where the access reject message includes the first reason The duration of the value code and the timer, the access reject message is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the access request message, and the first cause value code is the rejection of the user equipment. The reason value code of the access request; the timer is started according to the first reason value code, and the access request message is resent to the first core network node after the timer expires and expires. Compared with the prior art, when the network device is congested, the user equipment can continuously try to access the network, and the user equipment can pause the attempt to access the network within the timer duration according to the cause value code and the timer duration, which can effectively alleviate the network device. congestion. Example 3

 The embodiment of the present invention provides an overload control method. In order to more clearly describe the working process of the user equipment and the core network node in the overload control method provided by the embodiment of the present invention, the embodiment of the present invention provides a GSM system or a UMTS. In the system, the interaction example between the foregoing devices, the overload control method provided in this embodiment includes:

 S301. The user equipment sends a service request message or a PDP activation request message to the SGSN.

When the user equipment sends a service request message to the SGSN, and the core network node is not defined in the SGSN, the user equipment may send a reason value code that may cause the user equipment to delay the attach or route update process, as shown in FIG. S302-S304 may be continued; or, when the user equipment sends a service request message to the SGSN, as shown in FIG. 4, S305-S306 may continue to be performed; or, when the user equipment sends a PDP activation When the message is requested to the SGSN, as shown in FIG. 3, S302-S304 can be continued.

 Further, before performing S302-S304 or S305-S306, the method of the embodiment of the present invention may further include: the first core network node receiving version information of the user equipment from the access network node, and the version information is the access network And receiving, by the user equipment, the version information is used to indicate a version of the user equipment that sends the access request to the first core network node; and the first core network node determines, according to the version information, that the first cause value code is the rejection of the user equipment. Enter the reason code for the request and set the duration of the timer.

 5302. The SGSN determines that at least one node in the core network is overloaded, and the SGSN sends a P-TMSI redistribution command to the user equipment, and the P-TMSI redistribution command carries a routing area identifier RAI.

 The SGSN may obtain a resource response message from the GGSN by sending a control signaling message to the GGSN, and then determine that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message. Specifically, if the resource-restricted indication indicates that the core network resource is restricted, the SGSN may determine that at least one node in the core network is overloaded; or, the SGSN may determine, at least when the resource response message includes the resource-restricted indication, the core network. A node node is overloaded.

 Further, in an application scenario of the embodiment of the present invention, if the SGSN does not receive the resource response message from the GGSN within a predetermined time, the SGSN may also determine that at least one node in the core network is overloaded.

 Exemplarily, the user equipment can receive a system broadcast message, acquire and save the RAI in the system broadcast message.

 5303. Comparison of User Equipment The RAI carried in the P-TMSI redistribution command and the RAI received by the user equipment from the system are received.

 5304. If the RAI carried in the P-TMSI redistribution command is different from the RAI received by the user equipment from the system, the user equipment sends a route update request message to the SGSN.

The user equipment can compare the RAI carried in the P-TMSI redistribution command with the RAI received by the user equipment from the system, and is carried in the P-TMSI reassignment command. When the RAI is different from the RAI that the user equipment receives from the system broadcast, it indicates that the user equipment needs to update the routing area, and the user equipment may send a route update request message to the SGSN.

 As shown in FIG. 4, the method of the embodiment of the present invention may further include: S305-S306:

S305. The SGSN determines that at least one node in the core network is overloaded, and sends a service reject message to the user equipment, where the service reject message includes a second cause value code, where the second cause value code is determined by the first core network node according to the version information. The reason code for the service request of the user device.

 Exemplarily, in this embodiment, in the method shown in FIG. 4, when at least one node in the core network is overloaded, the SGSN may not send a P-TMSI reassignment command to the user equipment, so that the user equipment sends the SGSN to the SGSN. A routing update request is initiated, but a service rejection message carrying the second cause value code is sent to the user equipment, so that the user equipment initiates an attach request to the SGSN according to the second cause value code.

 The second reason value code may be: #9 or #10.

 S306. The user equipment sends an attach request message to the SGSN according to the second cause value code. The user equipment may send an attach request message to the SGSN according to the second cause value code included in the service reject message.

 It should be noted that the service rejection message only includes the second reason value code, and does not include the timer duration. Therefore, the user equipment does not need to start the corresponding timer according to the second reason value code and the timer duration, and the user equipment is receiving. The attach request message can be sent to the SGSN immediately after the service reject message carrying the second cause value code.

 5307. The SGSN determines that the at least one node in the core network is overloaded, and sends an access reject message to the user equipment, where the access reject message includes a first cause value code and a duration of the timer, where the first cause value code is a reject of the user equipment. The reason code for the access request.

Specifically, when the access request message is a route update request message, the access reject message is a route update reject message, as shown in FIG. 3, S307 may specifically be S307a; when the access request message is an attach request message, access The rejection message is an attachment rejection message. As shown in FIG. 4, S307 may specifically be S307b:

 S307a. The SGSN determines that at least one node in the core network is overloaded, and sends a route update reject message to the user equipment, where the route update reject message includes a first cause value code and a duration of the timer, where the first cause value code is a reject of the user equipment. The reason value code for the route update request.

 S307b: The SGSN determines that at least one node in the core network is overloaded, and sends an attach reject message to the user equipment, where the attach reject message includes a first cause value code and a duration of the timer, where the first cause value code is an attach request for rejecting the user equipment. The reason value code.

 It should be noted that, when the user equipment sends a PDP activation request message to the SGSN, and at least one node in the core network is overloaded, the SGSN sends a P-TMSI reassignment command to the user equipment in S202 to prevent the user equipment from being unable to access the device. The core network enters an idle state. In an application scenario of the embodiment of the present invention, if the user equipment sends a PDP activation request message to the SGSN, the S202-S204 or S205-S206 may not be executed, but the following steps are directly performed: if at least one node in the core network If the overload occurs, the SGSN sends a PDP activation reject message to the user equipment. The PDP activation reject message contains the reason value code: #26 and the duration of the timer, and the reason value code #26 is the reason value code for rejecting the PDP activation request of the user equipment.

 S308. The user equipment starts a timer according to the first reason value code, and resends the access request message to the SGSN after the timer expires, and the access request message is an attach request message or a route update request message.

 It should be noted that, in this embodiment, the timer is T3302.

 Preferably, in order to further prevent the user equipment from frequently sending the access request message to the core network node, the congestion of the core network node is aggravated, and the user equipment may, when the number of request rejection messages received by the user equipment exceeds a preset threshold, according to the reason The value code and the timer duration enable the timer, and resend the access request message to the first core network node after the timer expires.

Specifically, after receiving the request rejection message from the SGSN, the user equipment may The timer may be started according to the first reason value code, and the timer is set according to the duration of the timer, and the access request message is resent to the SGSN after the timer expires.

 In the overload control method provided by the embodiment of the present invention, the SGSN in the core network receives an access request message from the user equipment; the SGSN determines that at least one node in the core network is overloaded, sends an access reject message to the user equipment, and accesses the reject message. The time length of the first reason value code and the timer is included, and the access rejection message indicates that the user equipment resends the access request message to the SGSN after the timer expires, and the first reason value code is to reject the access request of the user equipment. Reason value code. Compared with the prior art, when the network device is congested, the SGSN can control the user equipment to pause the attempt to access the network within the timer duration by using the reason code and the duration of the timer. Congestion of network equipment. Example 4

 The embodiment of the present invention provides an overload control method. In order to more clearly describe the working process of the user equipment and the core network node in the overload control method provided by the embodiment of the present invention, the embodiment of the present invention provides an LTE system. An example of the interaction between the foregoing devices, the overload control method provided in this embodiment includes:

 S401. The user equipment sends a service request message or a PDN connection request message to the MME.

 When the user equipment sends a service request message to the MME, and the core network node is not defined in the MME, the user equipment may send a reason value code that may cause the user equipment to delay the attachment or the tracking area update process, as shown in FIG. 5 If the user equipment sends a service request message to the MME, as shown in FIG. 6, S405-S406 may continue to be performed; or, when the user equipment sends a PDN connection request message to the MME, As shown in FIG. 5, S402-S404 can be continued.

Further, before performing S402-S404 or S405-S406, the method of the embodiment of the present invention may further include: sending, by the first core network node, an initialization establishment context, Obtaining an access network node, so that the access network node sends a Radio Resource Control (RRC) connection reconfiguration request to the user equipment, so that the user equipment sends an RRC connection reconfiguration response including the version information of the user equipment. And an access network node, wherein the access network node generates an initialization setup context response including version information of the user equipment; the first core network node receives an initialization setup context response from the access network node that includes version information of the user equipment; The core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting the access request of the user equipment, and sets a timer duration.

 5402. The MME determines that at least one node in the core network is overloaded, and the MME sends a GUTI reassignment command to the user equipment, where the GUTI redistribution command carries the TAI歹l table.

 The MME may obtain a resource response message from the GW by sending a control signaling message to the GW, and then determine that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message. Specifically, if the resource-restricted indication indicates that the core network resource is restricted, the MME may determine that at least one node in the core network is overloaded; or, the MME may determine that at least one of the core networks is included when the resource response message includes the resource-restricted indication. A node node is overloaded.

 Further optionally, if the MME does not receive the resource response message from the GW within a predetermined time, the MME may also determine that at least one node in the core network is overloaded.

 Exemplarily, the user equipment can receive the system broadcast message, obtain and save the TAI list in the system broadcast message.

 5403. The user equipment determines whether the TAI list includes the TAI that the user equipment receives from the system broadcast.

 5404. If the TAI list does not include the TAI that the user equipment receives from the system broadcast, the user equipment sends a tracking area update request message to the MME.

The user equipment may determine whether the TAI list in the GUTI reassignment command includes the TAI received by the user equipment from the system broadcast, and when the TAI list in the GUTI reassignment command does not include the TAI received by the user equipment from the system broadcast, The The user equipment needs to update the tracking area, and the user equipment can send a tracking update request message to the MME.

 As shown in FIG. 6, the method of the embodiment of the present invention may further include: S405-S406:

5405. The MME determines that at least one node in the core network is overloaded, and the MME sends a service reject message to the user equipment, where the service reject message includes a second cause value code, where the second cause value code is determined by the first core network node according to the version information. The reason code for rejecting the service request of the user device.

 Exemplarily, in this embodiment, in the method shown in FIG. 4, when at least one node in the core network is overloaded, the MME may not send a GUTI reassignment command to the user equipment, so that the user equipment initiates tracking to the MME. The area update request sends a service reject message carrying the second cause value code to the user equipment, so that the user equipment initiates an attach request to the MME according to the second cause value code.

 The second reason value code may be: #9 or #10.

 S406. The user equipment sends an attach request message to the MME according to the second cause value code. The user equipment may send an attach request message to the MME according to the second cause value code included in the service reject message.

 It should be noted that the service rejection message only includes the second reason value code, and does not include the timer duration. Therefore, the user equipment does not need to start the corresponding timer according to the second reason value code and the timer duration, and the user equipment is receiving. The attach request message may be sent to the MME immediately after the service reject message carrying the second cause value code.

 S407. The MME determines that the at least one node in the core network is overloaded, and sends an access reject message to the user equipment, where the access reject message includes a first cause value code and a duration of the timer, where the first cause value code is to reject the user equipment. The reason code for the access request.

Specifically, when the access request message is a tracking area update request message, the access reject message is a tracking area update reject message, as shown in FIG. 3, S407 may specifically be S407a; when the access request message is an attach request message, The access reject message is an attach reject message. As shown in FIG. 4, S407 may specifically be S407b: S407a. The MME determines that at least one node in the core network is overloaded, and sends a tracking area update reject message to the user equipment, where the tracking area update reject message includes a first cause value code and a duration of the timer, where the first cause value code is a rejecting user. The reason code for the tracking area update request of the device.

 S407b: The MME determines that at least one node in the core network is overloaded, and sends an attach reject message to the user equipment, where the attach reject message includes a first cause value code and a duration of the timer, where the first cause value code is an attach request for rejecting the user equipment. The reason value code.

 It should be noted that, when the user equipment sends a PDN connection request message to the MME, and at least one node in the core network is overloaded, the MME sends a GUTI reassignment command to the user equipment in S202 to prevent the user equipment from accessing the core network. And enter the idle state. In an application scenario of the embodiment of the present invention, if the user equipment sends a PDN connection request message to the MME, the S202-S204 or S205-S206 may not be executed, but the following steps are directly performed: if at least one node in the core network If the overload occurs, the MME sends a PDN connection reject message to the user equipment. The PDN connection reject message contains the reason value code: #26 and the duration of the timer, and the reason value code #26 is the reason value code for rejecting the PDN connection request of the user equipment.

 S408: The user equipment starts a timer according to the first reason value code, and resends the access request message to the MME after the timer expires, and the access request message is an attach request message or a tracking area update request message.

 It should be noted that, in this embodiment, the timer is T3402.

 Preferably, in order to further prevent the user equipment from frequently sending the access request message to the core network node, the congestion of the core network node is aggravated, and the user equipment may, when the number of request rejection messages received by the user equipment exceeds a preset threshold, according to the reason The value code and the timer duration enable the timer, and resend the access request message to the first core network node after the timer expires.

Specifically, after receiving the request rejection message from the UI, the user equipment may start the timer according to the first reason value code, and set the timing according to the duration of the timer. The device resends the access request message to the MME after the timer expires.

 In the overload control method provided by the embodiment of the present invention, the MME in the core network receives an access request message from the user equipment; the MME determines that at least one node in the core network is overloaded, sends an access reject message to the user equipment, and accesses the reject message. The time length of the first reason value code and the timer is included, and the access reject message indicates that the user equipment resends the access request message to the MME after the timer expires, and the first cause value code is to reject the access request of the user equipment. Reason value code. Compared with the prior art, when the network device is congested, the MME can continuously try to re-attempt to access the network. The MME can control the user equipment to pause the attempt to access the network within the timer duration by using the reason code and the duration of the timer. Congestion of network equipment. Example 5

 The embodiment of the present invention provides a core network node, as shown in FIG. 7, including: a receiving unit 51, a determining unit 52, and a sending unit 53.

 The receiving unit 51 is configured to receive an access request message from the user equipment.

 a determining unit 52, configured to determine that at least one node in the core network is overloaded. The sending unit 53 is configured to send an access reject message to the location after the determining unit 52 determines that at least one node in the core network is overloaded The user equipment, the access reject message includes a first cause value code and a duration of the timer, where the access reject message indicates that the user equipment resends the timer after the timer expires after the timer expires The access request message is sent to the core network node, and the first cause value code is a reason value code for rejecting the access request of the user equipment.

 Further, the receiving unit 51 is further configured to receive a resource response message from a second core network node in the core network.

The determining unit 52 is further configured to determine that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message received by the receiving unit 51. Further, in an application scenario of the embodiment of the present invention, the core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 Further, in this application scenario, the receiving unit 51 is further configured to receive a service request message or a PDP activation request message from the user equipment before receiving the access request message from the user equipment. .

 The sending unit 53 is further configured to: if the determining unit 52 determines that at least one node in the core network is overloaded, send a P-TMSI reassignment command to the user equipment, where the P-TMSI redistribution command is used. Carry the RAI.

 The receiving unit 5 1 is further configured to receive the route update request message from the user equipment, where the route update request message is that the user equipment receives the P-TMSI sent by the sending unit 53 After the reassignment command, the RAI carried in the P-TMSI reassignment command is initiated when the RAI is different from the RAI broadcast by the user equipment.

 The first cause value code is a reason value code for rejecting the routing update request of the user equipment.

 The receiving unit 51 is further configured to: before the sending unit 53 sends an access reject message to the user equipment, receive version information of the user equipment from the access network node, where the version information is the The network access node is received by the user equipment, and the version information is used to indicate a version of the user equipment that sends the access request to the first core network node.

The determining unit 52 is further configured to determine, according to the version information received by the receiving unit 51, the first cause value code as a reason value code for rejecting an access request of the user equipment, and set the timer The length of time. Further, in another application scenario of the embodiment of the present invention, the core network node is an MME, the second core network node is a GW, and the timer is T3402.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 Further, in this application scenario, the sending unit 53 is further configured to: after the receiving unit 51 receives the access request message from the user equipment, send an initialization setup context request to the access network node, so that The access network node sends a radio resource control protocol RRC connection reconfiguration request to the user equipment, so that the user equipment sends an RRC connection reconfiguration response including the version information of the user equipment to the access And the network node, and the access network node, in turn, generates an initialization setup context response including the version information of the user equipment.

 The receiving unit 5 1 is further configured to receive an initialization establishment context response that includes the version information of the user equipment from the access network node.

 The determining unit 52 is further configured to determine, according to the version information received by the receiving unit 51, the first cause value code as a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

 Further, in this application scenario, the receiving unit 51 is further configured to receive a service request message or a PDN connection request message from the user equipment before receiving the access request message from the user equipment. .

 The sending unit 53 is further configured to: if the determining unit 52 determines that at least one node in the core network is overloaded, send a GUTI reassignment command to the user equipment, where the GUTI reassignment command carries a TAI list.

The receiving unit 51 is further configured to receive a tracking area update request message from the user equipment, where the tracking area update request message is that the user equipment receives the GUTI reassignment command sent by the sending unit 53 After receiving the user equipment Transmitted when the TAI of the system broadcast is not included in the TAI list.

 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.

 Further, in another application scenario of the embodiment of the present invention, the core network node is the SGSN, the second core network node is the GGSN, and the timer is the T3302; The core network node is the MME, the second core network node is the GW, and the timer is the T3402.

 In this application scenario, the receiving unit 51 is further configured to receive a service request message from the user equipment before receiving the access request message from the user equipment.

 The sending unit 53 is further configured to: if the determining unit 52 determines that at least one node in the core network is overloaded, send a service reject message to the user equipment, where the service reject message includes a second cause value code And the second cause value code is a reason value code that is determined by the first core network node to reject the service request of the user equipment according to the version information.

 The receiving unit 5 1 is further configured to receive the attach request message from the user equipment, where the attach request message is sent by the user equipment to receive the second cause value sent by the sending unit 53 The code is sent after the service rejects the message.

 It should be noted that the specific description of some of the functional modules in the core network node provided by the embodiment of the present invention may be referred to the corresponding content in the method embodiment, which is not described in detail herein.

The core network node provided by the embodiment of the present invention receives an access request message from the user equipment, determines that at least one node in the core network is overloaded, and sends an access reject message to the user equipment, where the access reject message includes the first cause value code. And the duration of the timer, the access reject message indicates that the user equipment resends the access request message to the core network node after the timer expires, and the first cause value code is a reason value code for rejecting the access request of the user equipment. In the prior art, when the network device is congested, the user equipment is continuously re-established. Compared with the time network, the core network node can control the user equipment to pause the attempt to access the network within the timer duration by using the reason code and the duration of the timer, which can effectively alleviate the congestion of the network device. Example 6

 An embodiment of the present invention provides a user equipment, as shown in FIG. 8, including: a sending unit 6 1 , a receiving unit 62 , and an opening unit 63 .

 The sending unit 6 1 is configured to send an access request message to the first core network node in the core network.

 The receiving unit 62 is configured to receive an access reject message from the first core network node, where the access reject message includes a first cause value code and a duration of the timer, where the access reject message is the After receiving the access request message, the core network node determines that the at least one node in the core network is overloaded, and the first cause value code is a reason value for rejecting the access request of the user equipment. code.

 The opening unit 63 is configured to enable the timer according to the first cause value received by the receiving unit 62.

 The sending unit 6 1 is further configured to resend the access request message to the first core network node after the timer that is turned on by the opening unit 63 expires after the timeout.

 Further, the first core network node, after receiving the access request message, determining that at least one node in the core network is overloaded, specifically: the first core network node according to the resource response message A resource limited indication included in the determining that at least one node in the core network is overloaded.

 The resource response message is received by the first core network node from a second core network node in the core network.

Further, the opening unit 63 is further configured to: when the number of the access reject messages received by the receiving unit 62 exceeds a preset threshold, H′J is according to the first reason The value code turns on the timer.

 The sending unit 61 is further configured to send at least one of the access request messages to the first core network node.

 Further, in an application scenario of the embodiment of the present invention, the first core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 Further, in this application scenario, the sending unit 61 is further configured to send the user by using an access network node before the receiving unit 62 receives an access reject message from the first core network node. The version information of the device is sent to the first core network node, so that the first core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting an access request of the user equipment, And setting the duration of the timer.

 Further, in this application scenario, the sending unit 61 is further configured to send a service request message or a PDP activation request message to the first before sending the access request message to the first core network node. A core network node.

 The receiving unit 62 is further configured to receive a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI reassignment command is the After receiving the service request message or the PDP activation request message sent by the sending unit 61, the core network node determines that at least one node in the core network is overloaded.

 The receiving unit 62 is further configured to receive an RAI from a system broadcast.

Further, as shown in FIG. 9, the user equipment may further include: a comparing unit 64. The comparing unit 64 is configured to compare the RAI carried in the P-TMSI reassignment command received by the receiving unit 62 with the RAI broadcast by the receiving unit 62 from the system.

 The sending unit 61 is further configured to: if the comparing unit 64 compares that the RAI carried in the P-TMSI reassignment command is different from the RAI received by the receiving unit 62 from the system, Routing update request message to the first core network node.

 Further, in another application scenario of the embodiment of the present invention, the first core network node is an MME, the second core network node is a GW, and the timer is T3402.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 Further, in this application scenario, the receiving unit 62 is further configured to receive an RRC connection reconfiguration request from an access network node before receiving an access reject message from the first core network node, where The RRC connection reconfiguration request is sent by the access network node after receiving an initialization setup context request from the first core network node.

 The sending unit 61 is further configured to send an RRC connection reconfiguration response including the version information of the user equipment to the access network node, so that the access network node generates a location that includes the user equipment. Initializing the version information to establish a context response, and sending the initialization establishment context response including the version information of the user equipment, so that the first core network node determines the first cause value according to the version information The code is a reason value code for rejecting the access request of the user equipment, and sets the duration of the timer.

Further, in this application scenario, the sending unit 61 is further configured to send a service request cancellation before sending the access request message to the first core network node. The PDN or PDN connection request message to the first core network node.

 The receiving unit 62 is further configured to receive a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is the first core network node After receiving the service request message or the PDN connection request message sent by the sending unit 61, determining that at least one node in the core network is overloaded.

 The receiving unit 62 is further configured to receive a TAI from a system broadcast.

 The user equipment further includes: a determining unit 65.

 The determining unit 65 is configured to determine whether the TAI received by the receiving unit 62 includes the TAI that the receiving unit 62 receives from the system broadcast.

 The sending unit 61 is further configured to: if the determining unit determines that the TAI list does not include the TAI that the receiving unit 62 receives from the system broadcast, send the tracking area update request message to the A core network node.

 Further, in another application scenario of the embodiment of the present invention, the first core network node is the SGSN, the second core network node is the GGSN, and the timer is the T3302; or The first core network node is the MME, the second core network node is the GW, and the timer is the T3402.

 In this application scenario, the sending unit 61 is further configured to send a service request message to the first core network node before sending the access request message to the first core network node.

 The receiving unit 62 is further configured to receive a service reject message from the first core network node, where the service reject message includes a second cause value code, where the second cause value code is the first core network a reason value code that is determined by the node to reject the service request of the user equipment according to the version information, where the service rejection message is after the first core network node receives the service request message sent by the sending unit 61. And determining to send when at least one node in the core network is overloaded.

The sending unit 61 is further configured to receive the second according to the receiving unit 62. The cause value code sends the attach request message to the first core network node. It should be noted that the specific description of some of the functional modules in the user equipment provided by the embodiments of the present invention may be referred to the corresponding content in the method embodiments.

 The user equipment provided by the embodiment of the present invention sends an access request message to the first core network node in the core network, and receives an access reject message from the first core network node, where the access reject message includes the first cause value code and The duration of the timer, the access reject message is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the access request message, and the first cause value code is to reject the access request of the user equipment. The reason value code; the timer is started according to the first reason value code, and the access request message is resent to the first core network node after the timer expires and times out. Compared with the prior art, when the network device is congested, the user equipment can continuously try to access the network, and the user equipment can pause the attempt to access the network within the timer duration according to the cause value code and the timer duration, which can effectively alleviate the network device. congestion. Example 7

 The embodiment of the present invention provides a core network node, as shown in FIG. 10, including: a receiver 71, a processor 72, and a transmitter 73.

 The receiver 71 is configured to receive an access request message from the user equipment.

 The processor 72 is configured to determine that at least one node in the core network is overloaded.

 The transmitter 73 is configured to send an access reject message to the user equipment after the processor 72 determines that the at least one node in the core network is overloaded, where the access reject message includes a first cause value code and The duration of the timer, the access denial message instructing the user equipment to resend the access request message to the core network node after the timer expires for the duration, the first cause value code A reason value code for rejecting the access request of the user equipment.

Further, the receiver 71 is further configured to receive from the core network. Resource response message of the second core network node.

 The processor 72 is further configured to determine, according to the resource limitation indication included in the resource response message received by the receiver 71, that at least one node in the core network is overloaded.

 Further, in an application scenario of the embodiment of the present invention, the core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 Further, in the application scenario, the receiver 71 is further configured to receive a version of the user equipment from the access network node before the transmitter 73 sends an access reject message to the user equipment. The version information is received by the access network node from the user equipment, and the version information is used to indicate a version of the user equipment that sends the access request to the first core network node.

 The processor 72 is further configured to determine, according to the version information received by the receiver 71, the first cause value code as a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

 Further, in the application scenario, the receiver 71 is further configured to receive a service request message or a PDP activation request message from the user equipment before receiving the access request message from the user equipment. .

 The transmitter 73 is further configured to: if the processor 72 determines that at least one node in the core network is overloaded, send a P-TMSI reassignment command to the user equipment, where the P-TMSI redistribution command is used. Carry the RAI.

The receiver 71 is further configured to receive the route update request message from the user equipment, where the route update request message is that the user equipment receives the P-TMSI sent by the sender 73. After the command is assigned, when the P-TMSI is redistributed The RAI carried in the command is initiated when the RIA is not received by the user equipment from the system broadcast.

 The first cause value code is a reason value code for rejecting the routing update request of the user equipment.

 Further, in another application scenario of the embodiment of the present invention, the core network node is an MME, the second core network node is a GW, and the timer is T3402.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 Further, in this application scenario, the transmitter 73 is further configured to: after the receiver 71 receives the access request message from the user equipment, send an initialization setup context request to the access network node, so as to enable the The access network node sends a radio resource control protocol RRC connection reconfiguration request to the user equipment, so that the user equipment sends an RRC connection reconfiguration response including the version information of the user equipment to the access network. The node, in turn, causes the access network node to generate an initialization setup context response including the version information of the user equipment.

 The receiver 71 is further configured to receive an initialization establishment context response of the version information from the access network node that includes the user equipment.

 The processor 72 is further configured to determine, according to the version information received by the receiver 71, the first cause value code as a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.

 Further, in the application scenario, the receiver 71 is further configured to receive a service request message or a PDN connection request message from the user equipment before receiving the access request message from the user equipment. .

The transmitter 73 is further configured to: if the processor 72 determines that at least one node in the core network is overloaded, send a GUTI reassignment command to the user equipment, where The TTI list is carried in the GUTI redistribution command.

 The receiver 71 is further configured to receive a tracking area update request message from the user equipment, where the tracking area update request message is that the user equipment receives the GUTI reassignment command sent by the sender 73. After that, the user equipment is sent when the TAI broadcasted by the system is not included in the TAI list.

 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.

 Further, in another application scenario of the embodiment of the present invention, the core network node is the SGSN, the second core network node is the GGSN, and the timer is the T3302; The core network node is the MME, the second core network node is the GW, and the timer is the T3402.

 Further, in the application scenario, the receiver 71 is further configured to receive a service request message from the user equipment before receiving the access request message from the user equipment.

 The transmitter 73 is further configured to: if the processor 72 determines that at least one node in the core network is overloaded, send a service reject message to the user equipment, where the service reject message includes a second cause value code And the second cause value code is a reason value code that is determined by the first core network node to reject the service request of the user equipment according to the version information.

 The receiver 71 is further configured to receive the attach request message from the user equipment, where the attach request message is that the user equipment receives the second cause value code sent by the sender 73. The service is sent after the message is rejected.

 It should be noted that the specific description of some of the functional modules in the core network node provided by the embodiment of the present invention may be referred to the corresponding content in the method embodiment, which is not described in detail herein.

The core network node provided by the embodiment of the present invention may receive an access request message from the user equipment, determine that at least one node in the core network is overloaded, and send an access rejection request. The access denied message includes the first cause value code and the duration of the timer, and the access reject message indicates that the user equipment resends the access request message to the core network node after the timer expires, the first The reason value code is the reason value code for rejecting the access request of the user equipment. Compared with the prior art, when the network device is congested, the user equipment continuously tries to access the network again. The core network node can control the user equipment to pause the attempt to access the network within the timer duration by using the reason code and the duration of the timer. Effectively alleviate network equipment congestion. Example 8

 An embodiment of the present invention provides a user equipment, as shown in FIG. 1 , including: a transmitter 81, a receiver 82, and a processor 83.

 The sender 81 is configured to send an access request message to a first core network node in the core network.

 The receiver 82 is configured to receive an access reject message from the first core network node, where the access reject message includes a first cause value code and a duration of the timer, where the access reject message is the After receiving the access request message, the core network node determines that the at least one node in the core network is overloaded, and the first cause value code is a reason value for rejecting the access request of the user equipment. code.

 The processor 83 is configured to enable the timer according to the first cause value code received by the receiver 82.

 The transmitter 81 is further configured to resend the access request message to the first core network node after the timer opened by the processor 83 times out due to the duration.

Further, the first core network node, after receiving the access request message, determining that at least one node in the core network is overloaded, specifically: the first core network node according to the resource response message A resource limited indication included in the determining that at least one node in the core network is overloaded. The resource response message is received by the first core network node from a second core network node in the core network.

 Further, the processor 83 is further configured to: when the number of the access reject messages received by the receiver 82 exceeds a preset threshold, according to the first cause value code and the timer The duration of the timer is turned on.

 The transmitter 81 is further configured to send at least one of the access request messages to the first core network node.

 Further, in an application scenario of the embodiment of the present invention, the first core network node is an SGSN, the second core network node is a GGSN, and the timer is Τ3302.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a route update request message, and the access reject message is a route update reject message.

 Further, in the application scenario, the transmitter 81 is further configured to send the user by using an access network node before the receiver 82 receives an access reject message from the first core network node. The version information of the device is sent to the first core network node, so that the first core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting an access request of the user equipment, And setting the duration of the timer.

 Further, in the application scenario, the sender 81 is further configured to send a service request message or a PDP activation request message to the first before sending the access request message to the first core network node. A core network node.

The receiver 82 is further configured to receive a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI reassignment command is the After receiving the service request message or the PDP activation request message sent by the sender 81, a core network node determines, in the core network, Sent when at least one node is overloaded.

 The receiver 82 is further configured to receive an RAI from a system broadcast.

 The processor 83 is further configured to compare the RAI carried in the P-TMSI redistribution command received by the receiver 82 with the RAI received by the receiver 82 from the system.

 The transmitter 81 is further configured to: if the processor 83 compares that the RAI carried in the P-TMSI reassignment command is different from the RAI that the receiver 82 receives from the system broadcast, Routing update request message to the first core network node.

 Further, in another application scenario of the embodiment of the present invention, the first core network node is the MME, the second core network node is the GW, and the timer is the T3402.

 In this application scenario, the access request message is an attach request message, and the access reject message is an attach reject message.

 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.

 Further, in the application scenario, the receiver 82 is further configured to receive an RRC connection reconfiguration request from the access network node before receiving the access reject message from the first core network node, where The RRC connection reconfiguration request is sent by the access network node after receiving an initialization setup context request from the first core network node.

The transmitter 81 is further configured to send an RRC connection reconfiguration response including the version information of the user equipment to the access network node, so that the access network node generates a location that includes the user equipment. Initializing the version information to establish a context response, and sending the initialization establishment context response including the version information of the user equipment, so that the first core network node determines the first cause value according to the version information The code is a reason value code for rejecting the access request of the user equipment, and sets the duration of the timer. Further, in the application scenario, the transmitter 81 is further configured to send a service request message or a PDN connection request message to the first before sending the access request message to the first core network node. A core network node.

 The receiver 82 is further configured to receive a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is the first core network node After receiving the service request message or the PDN connection request message sent by the sender 81, determining that at least one node in the core network is overloaded.

 The receiver 82 is further configured to receive a TAI from a system broadcast.

 The processor 83 is further configured to determine whether the TAI received by the receiver 82 includes a TAI that the receiver 82 receives from the system broadcast.

 The transmitter 81 is further configured to: if the processor 83 determines that the TAI list does not include the TAI that the receiver 82 receives from the system broadcast, send the tracking area update request message to the The first core network node.

 Further, the transmitter 81 is further configured to send a service request message to the first core network node before sending the access request message to the first core network node.

 The receiver 82 is further configured to receive a service reject message from the first core network node, where the service reject message includes a second cause value code, where the second cause value code is the first core network a reason value code of the service request rejecting the user equipment determined by the node according to the version information, where the service rejection message is after the first core network node receives the service request message sent by the sender 81 And determining to send when at least one node in the core network is overloaded.

 The transmitter 81 is further configured to send the attach request message to the first core network node according to the second cause value code received by the receiver 82.

It should be noted that the specific description of some functional modules in the user equipment provided by the embodiment of the present invention may refer to the corresponding content in the method embodiment. The user equipment provided by the embodiment of the present invention may send an access request message to the first core network node in the core network, and receive an access reject message from the first core network node, where the access reject message includes the first cause value code. And the duration of the timer, the access reject message is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the access request message, and the first cause value code is to reject the access of the user equipment. The reason code of the request; the timer is started according to the first reason value code, and the access request message is resent to the first core network node after the timer expires and expires. Compared with the prior art, when the network device is congested, the user equipment can continuously try to access the network, and the user equipment can pause the attempt to access the network within the timer duration according to the cause value code and the timer duration, which can effectively alleviate the network device. congestion.

 Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above functional modules is illustrated. In practical applications, the above functions can be allocated according to needs. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific operation of the system, the device, and the unit, the corresponding processes in the foregoing method embodiments may be referred to, and details are not described herein.

 In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be used. Combined or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.

The unit described as a separate component may or may not be physically divided The components displayed as the unit may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

 In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

 The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. The instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods of the various embodiments of the present invention. The foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

 The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

 Claims
 1. An overload control method, characterized in that:
 The first core network node in the core network receives an access request message from the user equipment; the first core network node determines that at least one node in the core network is overloaded, and the first core network node sends an access rejection message. a message to the user equipment, where the access reject message includes a first cause value code and a duration of the timer, where the access reject message indicates that the user equipment restarts after the timer expires after the timer expires Sending the access request message to the first core network node, where the first cause value code is a reason value code for rejecting the access request of the user equipment.
 The overload control method according to claim 1, wherein the first core network node determines that at least one node in the core network is overloaded, and includes:
 The first core network node receives a resource response message from a second core network node in the core network;
 The first core network node determines that at least one node in the core network is overloaded according to the resource limited indication included in the resource response message.
 The overload control method according to claim 1 or 2, wherein the first core network node is a serving general wireless packet service support node SGSN, and the second core network node is a gateway universal wireless packet service support. Node GGSN; the timer is T3302;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a route update request message, and the access reject message is a route update reject message.
 The overload control method according to claim 1 or 2, wherein the first core network node is a mobility management network element MME, and the second core network node is a gateway GW; T3402 ;
 The access request message is an attach request message, and the access reject message is an attach reject message;
Or the access request message is a tracking area update request message, and the access rejection The message is a tracking area update reject message.
 The overload control method according to any one of claims 1 to 3, wherein before the first core network node sends an access reject message to the user equipment, the method further includes:
 The first core network node receives the version information of the user equipment from the access network node, where the version information is received by the access network node from the user equipment, and the version information is used to indicate to the Determining, by the first core network node, a version of the user equipment that sends the access request;
 The first core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and sets the duration of the timer.
 The overload control method according to any one of claims 1, 2 or 4, wherein after the first core network node receives an access request message from the user equipment, the method further includes:
 The first core network node sends an initial setup context request to the access network node, so that the access network node sends a radio resource control protocol RRC connection reconfiguration request to the user equipment, so that the user equipment sends the The RRC connection reconfiguration of the version information of the user equipment is responsive to the access network node, and the access network node is further configured to generate an initialization setup context response including the version information of the user equipment;
 The first core network node receives an initialization setup context response from the access network node that includes the version information of the user equipment;
 The first core network node determines, according to the version information, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and sets the duration of the timer.
 The overload control method according to any one of claims 1 to 3, wherein before the first core network node receives an access request message from the user equipment, the method further includes:
The first core network node receives a service request message from the user equipment or Packet data protocol PDP activation request message;
 The first core network node determines that at least one node in the core network is overloaded, and the first core network node sends a packet temporary mobile user identity P-TMSI reassignment command to the user equipment, where the P- The routing area identifier RAI is carried in the TMSI redistribution command;
 The first core network node receives an access request message from the user equipment, and specifically includes:
 The first core network node receives the routing update request message from the user equipment, where the routing update request message is that the user equipment receives the P-TMSI reallocation command, when the P- The RAI carried in the TMSI redistribution command is initiated when the RAI is not received by the user equipment from the system broadcast;
 The first cause value code is a reason value code for rejecting the routing update request of the user equipment.
 The overload control method according to any one of claims 1, 2 or 4, wherein before the first core network node receives an access request message from the user equipment, the method further includes:
 The first core network node receives a service request message or a packet data network PDN connection request message from the user equipment;
 The first core network node determines that at least one node in the core network is overloaded, and the first core network node sends a globally unique temporary identifier GUTI reassignment command to the user equipment, where the GUTI reassignment command carries Tracking area identification TAI list;
 The first core network node receives an access request message from the user equipment, and specifically includes:
 The first core network node receives a tracking area update request message from the user equipment, where the tracking area update request message is sent by the user equipment after the user equipment receives the GUTI reassignment command. The TAI of the system broadcast is not included when the TAI list is sent;
The first cause value code is a reason value code rejecting the tracking area update request of the user equipment. The overload control method according to any one of claims 1 to 4, wherein before the first core network node receives an access request message from the user equipment, the method further includes:
 The first core network node receives a service request message from the user equipment; the first core network node determines that at least one node in the core network is overloaded, and the first core network node sends a service rejection message to The user equipment, the service rejection message includes a second cause value code, where the second cause value code is a reason for the first core network node to reject the service request of the user equipment according to the version information. Value code
 The first core network node receives an access request message from the user equipment, and specifically includes:
 The first core network node receives the attach request message from the user equipment, where the attach request message is sent by the user equipment after receiving the service reject message including the second cause value code. .
 10. An overload control method, comprising:
 The user equipment sends an access request message to the first core network node in the core network; the user equipment receives an access reject message from the first core network node, where the access reject message includes a first cause value code And the duration of the timer, the access denial message is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the access request message, where the first The reason value code is a reason value code for rejecting the access request of the user equipment;
 The user equipment starts the timer according to the first cause value code, and resends the access request message to the first core network node after the timer expires after the timer expires.
 The overload control method according to claim 10, wherein, after receiving the access request message, the first core network node determines that at least one node in the core network is overloaded , Specifically:
Determining, by the first core network node, that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message; The resource response message is received by the first core network node from a second core network node in the core network.
 The overload control method according to claim 10 or 11, wherein the first core network node is an SGSN, the second core network node is a GGSN, and the timer is Τ3302;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a route update request message, and the access reject message is a route update reject message.
 The overload control method according to claim 10 or 11, wherein the first core network node is ΜΜΕ and the second core network node is GW; the timer is Τ3402;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.
 The overload control method according to any one of claims 10 to 13, wherein the user equipment starts the timer according to the first reason value code, specifically: when the user equipment receives When the number of the access reject messages exceeds a preset threshold, the user equipment starts the timer according to the first cause value code;
 The user equipment sends at least one of the access request messages to the first core network node.
 The overload control method according to any one of claims 10 to 12, wherein before the user equipment receives an access reject message from the first core network node, the method further includes:
The user equipment sends the version information of the user equipment to the first core network node by using an access network node, so that the first core network node determines that the first cause value code is rejected according to the version information. a reason value code of the access request of the user equipment, and setting the duration of the timer. The overload control method according to claim 10, 11 or 13, wherein before the user equipment receives an access reject message from the first core network node, the method further includes:
 Receiving, by the user equipment, an RRC connection reconfiguration request from an access network node, where the RRC connection reconfiguration request is sent by the access network node after receiving an initialization setup context request from the first core network node ;
 Transmitting, by the user equipment, an RRC connection reconfiguration response including the version information of the user equipment to the access network node, to enable the access network node to generate an initialization of the version information including the user equipment Establishing a context response, and sending the initialization establishment context response including the version information of the user equipment, so that the first core network node determines, according to the version information, that the first cause value code is to reject the A reason value code of the access request of the user equipment, and setting the duration of the timer.
 The overload control method according to any one of claims 10 to 12, wherein before the user equipment sends an access request message to the first core network node, the method further includes:
 Sending, by the user equipment, a service request message or a PDP activation request message to the first core network node;
 The user equipment receives a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI reassignment command is the first core network node. After receiving the service request message or the PDP activation request message, determining that at least one node in the core network is overloaded; the user equipment compares the RAI carried in the P-TMSI reassignment command Receiving, from the user equipment, an RAI broadcasted by the system;
 And the user equipment sends the access request message to the first core network node, where the method includes: if the RAI carried in the P-TMSI reassignment command is different from the RAI received by the user equipment from the system, the user The device sends the route update request message to the first core network node.
The overload control method according to claim 10, 11 or 13, wherein before the user equipment sends an access request message to the first core network node, The method also includes:
 Sending, by the user equipment, a service request message or a PDN connection request message to the first core network node;
 Receiving, by the user equipment, a GUTI re-allocation command from the first core network node, where the GUTI re-allocation command carries a TAI list, where the GUTI re-allocation command is that the first core network node receives the service After the request message or the PDN connection request message is determined, when the at least one node in the core network is determined to be overloaded, the user equipment determines whether the TAI list includes the TAI received by the user equipment from the system broadcast;
 And sending, by the user equipment, the access request message to the first core network node, specifically: if the TAI list does not include the TAI that the user equipment receives from the system broadcast, the user equipment sends the tracking area update request Message to the first core network node.
 The overload control method according to any one of claims 10 to 14, wherein before the user equipment sends an access request message to the first core network node, the method further includes:
 The user equipment sends a service request message to the first core network node; the user equipment receives a service rejection message from the first core network node, where the service rejection message includes a second cause value code, The second cause value code is a reason value code that is determined by the first core network node to reject the service request of the user equipment according to the version information, where the service rejection message is that the first core network node receives the After the service request message is determined, it is determined that the at least one node in the core network is overloaded; and the user equipment sends an access request message to the first core network node, specifically: the user equipment according to the second reason The value code sends the attach request cancellation to the first core network node.
 20. A core network node, comprising:
 a receiving unit, configured to receive an access request message from the user equipment;
a determining unit, configured to determine that at least one node in the core network is overloaded; and a sending unit, configured to determine, in the determining unit, at least one section in the core network After the point is overloaded, the access reject message is sent to the user equipment, where the access reject message includes a first cause value code and a duration of the timer, and the access reject message indicates that the user equipment is in the timer After the timeout expires, the access request message is resent to the core network node, and the first cause value code is a reason value code for rejecting the access request of the user equipment.
 The core network node according to claim 20, wherein the receiving unit is further configured to receive a resource response message from a second core network node in the core network;
 The determining unit is further configured to determine that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message received by the receiving unit.
 The core network node according to claim 20 or 21, wherein the core network node is an SGSN, and the second core network node is a GGSN; the timer is T3302;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a route update request message, and the access reject message is a route update reject message.
 The core network node according to claim 20 or 21, wherein the core network node is an MME, the second core network node is a GW, and the timer is T3402;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.
The core network node according to any one of claims 20 to 22, wherein the receiving unit is further configured to receive, before the sending unit sends an access reject message to the user equipment, a version information of the user equipment of the access network node, where the version information is received by the access network node from the user equipment, and the version information is used to send the information to the first core network node. Accessing the requested user equipment version of;
 The determining unit is further configured to determine, according to the version information received by the receiving unit, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.
 The core network node according to any one of claims 20, 21 or 23, wherein the sending unit is further configured to: after the receiving unit receives an access request message from a user equipment, send Initializing a context request to the access network node, so that the access network node sends a RRC connection reconfiguration request to the user equipment, so that the user equipment sends the version including the user equipment The RRC connection reconfiguration of the information is responsive to the access network node, and the access network node is further configured to generate an initialization setup context response including the version information of the user equipment; the receiving unit is further configured to receive the Initializing the context response of the version information of the access network node that includes the version information of the user equipment;
 The determining unit is further configured to determine, according to the version information received by the receiving unit, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.
 The core network node according to any one of claims 20 to 22, wherein the receiving unit is further configured to receive the access request message before receiving the access request message from the user equipment. a service request message or a PDP activation request message of the user equipment;
 The sending unit is further configured to: if the determining unit determines that at least one node in the core network is overloaded, send a P-TMSI reassignment command to the user equipment, where the P-TMSI redistribution command carries an RAI ;
 The receiving unit is further configured to receive the route update request message from the user equipment, where the route update request message is that the user equipment receives the P-TMSI reassignment command sent by the sending unit. After the RAI carried in the P-TMSI redistribution command is different from the RAI that the user equipment receives from the system broadcast,
The first cause value code is a reason for rejecting the routing update request of the user equipment Value code.
 The core network node according to any one of claims 20, 21 or 23, wherein the receiving unit is further configured to receive before receiving the access request message from the user equipment. a service request message or a PDN connection request message from the user equipment;
 The sending unit is further configured to: if the determining unit determines that at least one node in the core network is overloaded, send a GUTI reassignment command to the user equipment, where the GUTI reassignment command carries a TAI list;
 The receiving unit is further configured to receive a tracking area update request message from the user equipment, where the tracking area update request message is after the user equipment receives the GUTI reassignment command sent by the sending unit, Transmitting when the user equipment receives a TAI broadcasted by the system that is not included in the TAI list;
 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.
 The core network node according to any one of claims 22 to 23, wherein the receiving unit is further configured to receive the access request message before receiving the access request message from the user equipment. a service request message of the user equipment;
 The sending unit is further configured to: if the determining unit determines that at least one node in the core network is overloaded, send a service reject message to the user equipment, where the service reject message includes a second cause value code, where The second cause value code is a reason value code that is determined by the first core network node to reject the service request of the user equipment according to the version information; the receiving unit is further configured to receive the location from the user equipment And the attach request message is sent by the user equipment after receiving the service reject message that is sent by the sending unit and includes the second cause value code.
 29. A user equipment, comprising:
 a sending unit, configured to send an access request message to a first core network node in the core network;
a receiving unit, configured to receive an access reject message from the first core network node, where the access reject message includes a first cause value code and a duration of the timer, where the access rejection The sever message is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the access request message, where the first cause value code is to reject the user equipment. The reason code of the access request;
 An opening unit, configured to enable the timer according to the first cause value code received by the receiving unit;
 The sending unit is further configured to resend the access request message to the first core network node after the timer that is turned on by the open unit expires after the timeout period.
 The user equipment according to claim 29, wherein, after receiving the access request message, the first core network node determines that at least one node in the core network is overloaded, specifically For:
 Determining, by the first core network node, that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message;
 The resource response message is received by the first core network node from a second core network node in the core network.
 The user equipment according to claim 29 or 30, wherein the first core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a route update request message, and the access reject message is a route update reject message.
 The user equipment according to claim 29 or 30, wherein the first core network node is an MME, the second core network node is a GW, and the timer is T3402;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.
33. A user equipment according to any one of claims 29-32, characterized in that The opening unit is further configured to: when the number of the access reject messages received by the receiving unit exceeds a preset threshold, start the timer according to the first cause value code;
 The sending unit is further configured to send at least one of the access request messages to the first core network node.
 The user equipment according to any one of claims 29 to 3, wherein the sending unit is further configured to receive, at the receiving unit, an access reject message from the first core network node. And transmitting, by the access network node, version information of the user equipment to the first core network node, so that the first core network node determines, according to the version information, that the first cause value code is to reject the A reason value code of the access request of the user equipment, and setting the duration of the timer.
 The user equipment according to any one of claims 29, 30 or 32, wherein the receiving unit is further configured to receive before receiving an access reject message from the first core network node. An RRC connection reconfiguration request from an access network node, the RRC connection reconfiguration request being sent by the access network node after receiving an initialization setup context request from the first core network node;
 The sending unit is further configured to send an RRC connection reconfiguration response including the version information of the user equipment to the access network node, so that the access network node generates the The initialization of the version information establishes a context response, and sends the initialization establishment context response including the version information of the user equipment, so that the first core network node determines the first cause value code according to the version information. The reason value code for rejecting the access request of the user equipment, and setting the duration of the timer.
 The user equipment according to any one of claims 29 to 3, wherein the sending unit is further configured to send, before sending the access request message to the first core network node, a service request message or a PDP activation request message to the first core network node;
The receiving unit is further configured to receive a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, where the P-TMSI is heavy The allocation command is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the service request message or the PDP activation request message sent by the sending unit;
 The receiving unit is further configured to receive an RAI from a system broadcast;
 The user equipment further includes:
 a comparison unit, configured to compare the RAI carried in the P-TMSI reassignment command received by the receiving unit with an RAI received by the receiving unit from the system; the sending unit is further used to Comparing the comparison unit to obtain that the RAI carried in the P-TMSI reassignment command is different from the RAI received by the receiving unit from the system, and sending the route update request message to the first core network node. .
 The user equipment according to claim 29, 30 or 32, wherein the sending unit is further configured to send a service request message before sending the access request message to the first core network node. Or a PDN connection request message to the first core network node;
 The receiving unit is further configured to receive a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is received by the first core network node After the service request message or the PDN connection request message sent by the sending unit is determined, it is determined that at least one node in the core network is overloaded;
 The receiving unit is further configured to receive a TAI from a system broadcast;
 The user equipment further includes:
 a determining unit, configured to determine whether the TAI list received by the receiving unit includes a TAI that is received by the receiving unit from the system broadcast;
 The sending unit is further configured to: if the determining unit determines that the TAI list does not include the TAI that the receiving unit receives from the system broadcast, send the tracking area update request message to the first core Network node.
The user equipment according to any one of claims 29 to 32, wherein the sending unit is further configured to send a service before sending the access request message to the first core network node. Requesting a message to the first core network node; The receiving unit is further configured to receive a service reject message from the first core network node, where the service reject message includes a second cause value code, where the second cause value code is the first core network node And determining, by the version information, a reason value code for rejecting the service request of the user equipment, where the service rejection message is determined by the first core network node after receiving the service request message sent by the sending unit Transmitted when at least one node in the core network is overloaded;
 The sending unit is further configured to send the attach request message to the first core network node according to the second cause value code received by the receiving unit.
 39. A core network node, comprising:
 a receiver, configured to receive an access request message from the user equipment;
 a processor, configured to determine that at least one node in the core network is overloaded;
 a transmitter, configured to send an access reject message to the user equipment after the processor determines that the at least one node in the core network is overloaded, where the access reject message includes a first cause value code and a timer The access denied message indicates that the user equipment resends the access request message to the core network node after the timer expires for the duration, and the first cause value code is rejected. The reason value code of the access request of the user equipment.
 The core network node according to claim 39, wherein the receiver is further configured to receive a resource response message from a second core network node in the core network;
 The processor is further configured to determine that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message received by the receiver.
 The core network node according to claim 39 or 40, wherein the core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302;
 The access request message is an attach request message, and the access reject message is an attach reject message;
Or the access request message is a route update request message, and the access reject message is a route update reject message. The core network node according to claim 39 or 40, wherein the core network node is an MME, the second core network node is a GW, and the timer is T3402;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.
 The core network node according to any one of claims 39-41, wherein the receiver is further configured to receive, before the sender sends an access reject message to the user equipment, a version information of the user equipment of the access network node, where the version information is received by the access network node from the user equipment, and the version information is used to send the information to the first core network node. Accessing the requested version of the user equipment;
 The processor is further configured to determine, according to the version information received by the receiver, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.
 The core network node according to any one of claims 39, 40 or 42, wherein the transmitter is further configured to send after the receiver receives an access request message from a user equipment. Initializing a context request to the access network node, so that the access network node sends a RRC connection reconfiguration request to the user equipment, so that the user equipment sends the version including the user equipment The RRC connection reconfiguration of the information is responsive to the access network node, and the access network node is further configured to generate an initialization setup context response including the version information of the user equipment;
 The receiver is further configured to receive an initialization establishment context response of the version information that includes the user equipment from the access network node;
 The processor is further configured to determine, according to the version information received by the receiver, that the first cause value code is a reason value code for rejecting an access request of the user equipment, and set the timer The length of time.
45. A core network node according to any of claims 39-41, characterized in that The receiver is further configured to receive a service request message or a PDP activation request message from the user equipment before receiving the access request message from the user equipment;
 The transmitter is further configured to: if the processor determines that at least one node in the core network is overloaded, send a P-TMSI reassignment command to the user equipment, where the P-TMSI redistribution command carries an RAI ;
 The receiver is further configured to receive the route update request message from the user equipment, where the route update request message is that the user equipment receives the P-TMSI reassignment command sent by the sender After the RAI carried in the P-TMSI reassignment command is different from the RAI that the user equipment receives from the system broadcast, the first cause value code is a request for rejecting the routing update of the user equipment. The reason value code.
 The core network node according to any one of claims 39, 40 or 42, wherein the receiver is further configured to receive before receiving the access request message from the user equipment. a service request message or a PDN connection request message from the user equipment;
 The transmitter is further configured to: if the processor determines that at least one node in the core network is overloaded, send a GUTI reassignment command to the user equipment, where the GUTI reassignment command carries a TAI list;
 The receiver is further configured to receive a tracking area update request message from the user equipment, where the tracking area update request message is after the user equipment receives the GUTI reassignment command sent by the sender, Transmitting when the user equipment receives a TAI broadcasted by the system that is not included in the TAI list;
 The first cause value code is a reason value code rejecting the tracking area update request of the user equipment.
 The core network node according to any one of claims 39 to 41, wherein the receiver is further configured to receive the access request message before receiving the access request message from the user equipment. a service request message of the user equipment;
The transmitter is further configured to: if the processor determines at least one of the core networks If the node is overloaded, the service reject message is sent to the user equipment, and the service reject message includes a second cause value code, where the second cause value code is determined by the first core network node according to the version information. a reason value code of the service request of the user equipment;
 The receiver is further configured to receive the attach request message from the user equipment, where the attach request message is that the user equipment receives the second cause value code sent by the sender Sent after the service rejection message.
 48. A user equipment, comprising:
 a transmitter, configured to send an access request message to a first core network node in a core network, and a receiver, configured to receive an access reject message from the first core network node, where the access reject message includes a a reason value code and a duration of the timer, where the access reject message is sent by the first core network node after determining that the at least one node in the core network is overloaded after receiving the access request message, The first cause value code is a reason value code for rejecting an access request of the user equipment;
 a processor, configured to enable the timer according to the first cause value code received by the receiver;
 The transmitter is further configured to resend the access request message to the first core network node after the timer opened by the processor expires after the timeout.
 The user equipment according to claim 48, wherein, after receiving the access request message, the first core network node determines that at least one node in the core network is overloaded, specifically For:
 Determining, by the first core network node, that at least one node in the core network is overloaded according to the resource limitation indication included in the resource response message;
 The resource response message is received by the first core network node from a second core network node in the core network.
 The user equipment according to claim 48 or 49, wherein the first core network node is an SGSN, the second core network node is a GGSN, and the timer is T3302;
The access request message is an attach request message, and the access reject message is an attach reject message; Or the access request message is a route update request message, and the access reject message is a route update reject message.
 The user equipment according to claim 48 or 49, wherein the first core network node is an MME, the second core network node is a GW, and the timer is T3402;
 The access request message is an attach request message, and the access reject message is an attach reject message;
 Or the access request message is a tracking area update request message, and the access reject message is a tracking area update reject message.
 The user equipment according to any one of claims 48 to 5, wherein the processor is further configured to: when the number of the access reject messages received by the receiver exceeds a pre- When the threshold is set, the first cause value code starts the timer;
 The transmitter is further configured to send at least one of the access request messages to the first core network node.
 The user equipment according to any one of claims 48 to 50, wherein the transmitter is further configured to: before the receiver receives an access reject message from the first core network node, Transmitting, by the access network node, version information of the user equipment to the first core network node, so that the first core network node determines, according to the version information, that the first cause value code is to reject the user The reason code of the access request of the device, and setting the duration of the timer.
 The user equipment according to any one of claims 48, 49 or 51, wherein the receiver is further configured to: before receiving an access reject message from the first core network node, Receiving an RRC connection reconfiguration request from an access network node, where the RRC connection reconfiguration request is sent by the access network node after receiving an initialization setup context request from the first core network node;
The transmitter is further configured to send an RRC connection reconfiguration response including the version information of the user equipment to the access network node, to enable the access network node to generate the Initializing the version information to establish a context response, and sending the initialization establishment context response including the version information of the user equipment, and further And causing the first core network node to determine, according to the version information, the first cause value code as a reason value code for rejecting an access request of the user equipment, and setting the duration of the timer.
 The user equipment according to any one of claims 48 to 50, wherein the transmitter is further configured to send a service before sending the access request message to the first core network node. a request message or a PDP activation request message to the first core network node;
 The receiver is further configured to receive a P-TMSI reassignment command from the first core network node, where the P-TMSI reassignment command carries an RAI, and the P-TMSI redistribution command is the first After receiving the service request message or the PDP activation request message sent by the sender, the core network node determines that at least one node in the core network is overloaded;
 The receiver is further configured to receive an RAI from a system broadcast;
 The processor is further configured to compare the RAI carried in the P-TMSI reassignment command received by the receiver with the RAI received by the receiver from the system; the transmitter is further used by And sending, by the processor, the RAI carried in the P-TMSI reassignment command to the RAI that is received by the receiver from the system, sending the routing update request message to the first Core network node.
 The user equipment according to any one of claims 48, 49 or 51, wherein the transmitter is further configured to: before sending the access request message to the first core network node, Sending a service request message or a PDN connection request message to the first core network node;
 The receiver is further configured to receive a GUTI reassignment command from the first core network node, where the GUTI reassignment command carries a TAI list, where the GUTI reassignment command is received by the first core network node After the service request message or the PDN connection request message sent by the sender is determined, when it is determined that at least one node in the core network is overloaded;
 The receiver is further configured to receive a TAI from a system broadcast;
The processor is further configured to determine, in the TAI list received by the receiver Whether or not the TAI received by the receiver from the system broadcast is included;
 The transmitter is further configured to: if the processor determines that the TAI list does not include the TAI that the receiver receives from the system broadcast, send the tracking area update request message to the first core Network node.
 The user equipment according to any one of claims 48-51, wherein the transmitter is further configured to send a service before sending the access request message to the first core network node. Requesting a message to the first core network node;
 The receiver is further configured to receive a service reject message from the first core network node, where the service reject message includes a second cause value code, where the second cause value code is the first core network node Determining, by the version information, a reason value code of the service request of the user equipment, the service rejection message is determined by the first core network node after receiving the service request message sent by the sender Transmitted when at least one node in the core network is overloaded;
 The transmitter is further configured to send the attach request message to the first core network node according to the second cause value code received by the receiver.
PCT/CN2013/077755 2013-06-24 2013-06-24 Overload control method and apparatus WO2014205621A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/077755 WO2014205621A1 (en) 2013-06-24 2013-06-24 Overload control method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201380000536.7A CN104429126B (en) 2013-06-24 2013-06-24 A kind of overload controlling method and device
PCT/CN2013/077755 WO2014205621A1 (en) 2013-06-24 2013-06-24 Overload control method and apparatus

Publications (1)

Publication Number Publication Date
WO2014205621A1 true WO2014205621A1 (en) 2014-12-31

Family

ID=52140748

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/077755 WO2014205621A1 (en) 2013-06-24 2013-06-24 Overload control method and apparatus

Country Status (2)

Country Link
CN (1) CN104429126B (en)
WO (1) WO2014205621A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI638576B (en) * 2015-10-13 2018-10-11 電信科學技術研究院 Method for redirecting terminal equipment to private network, terminal equipment and base station
CN109246719A (en) * 2017-04-27 2019-01-18 展讯通信(上海)有限公司 Wireless communications method and device, base station, computer readable storage medium

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106332308A (en) * 2015-07-10 2017-01-11 中兴通讯股份有限公司 RRC (radio resource control) connection denied message transmitting, RRC connection requesting method and device
CN108886831A (en) * 2016-03-31 2018-11-23 华为技术有限公司 A kind of cut-in method and device
CN110677351A (en) * 2019-09-12 2020-01-10 南京大鱼半导体有限公司 Method and device for congestion control of Internet of things, storage medium and electronic equipment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070191010A1 (en) * 2006-01-26 2007-08-16 Samsung Electronics Co., Ltd. Apparatus and method for connecting call in mobile terminal
CN102098759A (en) * 2011-02-18 2011-06-15 电信科学技术研究院 Method and device for access control
CN102469554A (en) * 2010-11-05 2012-05-23 中兴通讯股份有限公司 Method for terminal to switch in network and terminal

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070191010A1 (en) * 2006-01-26 2007-08-16 Samsung Electronics Co., Ltd. Apparatus and method for connecting call in mobile terminal
CN102469554A (en) * 2010-11-05 2012-05-23 中兴通讯股份有限公司 Method for terminal to switch in network and terminal
CN102098759A (en) * 2011-02-18 2011-06-15 电信科学技术研究院 Method and device for access control

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI638576B (en) * 2015-10-13 2018-10-11 電信科學技術研究院 Method for redirecting terminal equipment to private network, terminal equipment and base station
CN109246719A (en) * 2017-04-27 2019-01-18 展讯通信(上海)有限公司 Wireless communications method and device, base station, computer readable storage medium

Also Published As

Publication number Publication date
CN104429126B (en) 2018-11-30
CN104429126A (en) 2015-03-18

Similar Documents

Publication Publication Date Title
JP6453973B2 (en) Multiple Priority Control Method and Apparatus in Wireless Communication System
US20180376363A1 (en) Congestion/overload control method and apparatus
US10425987B2 (en) Registration method, session establishment method, terminal, and AMF entity
US9838998B2 (en) Method of processing downlink data notification message and server therefore
US20160150498A1 (en) Proximity-based service registration method and related apparatus
AU2018203437B2 (en) Use of an oma management object to support application-specific congestion control in mobile networks
US8787159B2 (en) Mechanism for wireless access networks to throttle traffic during congestion
KR101339044B1 (en) Handling reachability of mobile device when serving core network node changes
US9392634B2 (en) Node and method for connection re-establishment
EP3358887B1 (en) User equipment registration method for network slice selection and network controller and network communication system using the same
US9930611B2 (en) Network selection method and core network device
US10542482B2 (en) Access control to services in a network
EP3322223A1 (en) Wireless communications access method, device, processor and wireless terminal
US20180310227A1 (en) Access control method and apparatus
US8837326B2 (en) Session management method and system based on M2M application, and apparatus
EP2244424A1 (en) A method for selecting a policy and charging rules function server on a non-roaming scene
JP6386176B2 (en) Smooth UE transfer in an evolved packet core
US8811985B2 (en) Network registration method, mobile station and subscriber information management server
US9119219B2 (en) Bandwidth control method, apparatus and system
CN103609150A (en) Traffic offload via local network based on APN-specific or non-APN-specific informaiton
US10506465B2 (en) Overload control in a packet mobile communication system
KR101377234B1 (en) Method of handling emergency bearer service in wireless communication system
KR101534902B1 (en) Providing a deny response that specifies a delay time
US20170164256A9 (en) Service offloading method and base station
US20180332636A1 (en) Method for establishing transmission channel, mme, network element device, system and storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13887767

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13887767

Country of ref document: EP

Kind code of ref document: A1