WO2012058965A1

WO2012058965A1 - Method and terminal for terminal to access network

Info

Publication number: WO2012058965A1
Application number: PCT/CN2011/078438
Authority: WO
Inventors: 邓云; 戴谦; 艾建勋; 毛磊
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-05
Filing date: 2011-08-15
Publication date: 2012-05-10
Also published as: CN102469554B; CN102469554A

Abstract

Disclosed are a method and a terminal for a terminal to access a network. According to the method: after a terminal receives an RRC connection release signal transmitted by a network, the terminal determines the wait time needed for the terminal to re-access the network; and when the terminal confirms the time the terminal has waited is equal to or greater than the wait time, the terminal is allowed to transmit an RRC connection request to the network. Use of the present invention can avoid large volume impacts on a network, or even network overload problems, that are due to follow-up RRC connection requests and simultaneous RRC requests from numerous terminals.

Description

The present invention relates to the field of communications, and in particular to a method and terminal for a terminal to access a network. BACKGROUND OF THE INVENTION H2H (Human to Human) communication refers to communication between people. Humans communicate through the operation of devices, and existing wireless communication technologies are developed based on H2H communication. The narrow definition of M2M (Machine to Machine) is machine-to-machine communication. Broadly defined, it is a networked application and service centered on intelligent interaction of machine terminals. M2M is an intelligent machine terminal based on a variety of communication methods to provide customers with information solutions to meet customer information needs for monitoring, command and dispatch, data acquisition and measurement. The development of wireless technology is an important factor in the development of the M2M market. It breaks through the space-time constraints and geographical barriers of traditional communication methods, freeing enterprises and the public from cable shackles, allowing customers to more effectively control costs, reduce installation costs, and is simple to use. . In addition, the growing demand drives M2M to keep moving forward. However, contrary to the continuous growth of information processing capabilities and network bandwidth, the means of information acquisition lag far behind, and M2M satisfies people's needs very well. Through it, people can monitor the external environment in real time, enabling large-scale, automated information collection. Therefore, M2M can be applied to industrial applications, home applications, personal applications, and the like. Among them, industry applications such as: traffic monitoring, warning systems, maritime rescue, vending machines, paying for cars, etc.; household applications such as: automatic meter reading, temperature control, etc.; personal applications such as: life detection, remote diagnosis, etc.

The communication object of M2M is machine-to-machine or person-to-machine. Data communication between one or more machines is defined as MTC (Machine Type Communication), in which case human interaction is less required. A machine participating in MTC is defined as an MTC device (hereinafter also referred to as an MTC terminal). The MTC terminal can communicate with other MTC terminals or MTC servers through a PLMN (Public Land Mobile-communication Network) network. After the M2M application is introduced, the existing system can be optimized according to its characteristics to meet the requirements of the M2M application and has no impact on the common user equipment in the existing system. Some notable features of M2M applications are: MTC devices are numerous, the amount of data transmitted per time is small, the transmission interval is large, and the position is relatively fixed. However, in view of the large number of MTC devices and the number of H2H devices (User Equipments), which are not more than an order of magnitude, the widespread use of MTC devices is likely to overload the network, such as when a cell suddenly experiences a power outage. When the power is restored, many MTC devices may try to access the network at the same time, which will Causes the network to be overloaded. In order to cope with the overload caused by the introduction of the MTC device, the network side needs to improve the overload control capability. The existing protocol requires a new processing overload capability for the core network element, such as the MME of the Long Term Evolution (LTE) system. Mobility Management Entity (Mobility Management Entity), which implements APN-based overload control according to the traffic volume of the APN (Access Point name) reported by the MTC device (the maximum number of active bearers, the maximum bearer rate, etc.). The registration rejection (Attach Reject) and the location area update rejection may be sent to the UE. The base station on the network side also needs to have the capability of implementing different access control according to the identity of the access terminal (whether it is an MTC device), such as the RRC Connection Reject or RRC connection through the RRC (Radio Resource Control) connection. Release signaling limits access to certain MTC devices. 1 is a schematic diagram of a RRC (Radio Resource Control) connection rejection process in the prior art. As shown in FIG. 1, the process is specifically described as follows: Step 102: The MTC device initiates random access and sends an RRC connection request. (RRC Connection Request) message to the network side; Step 104: If the network side resource is tight or other reasons at this time, the network side may send an RRC Connection Reject signaling to reject the connection request of the MTC device, and in the signaling The value of the Wait Time is used to limit the MTC device from re-acquiring random access during this period of time.

After receiving the RRC Connection Reject signaling, the MTC device notifies the upper layer that the RRC connection establishment fails, and sets the terminal local timer T302 to the value indicated by the Wait Time and starts. Before the T302 times out, the wireless connection establishment request cannot be initiated again. . The current value of the Wait Time in the protocol is 1-16 seconds. The RRC connection refusal can only be applied to the MTC device to initiate the connection. When the MTC device establishes the RRC connection, the RRC Connection Release is used to reject the access of the MTC device. In the existing protocol, the RRC connection releases the cell that does not carry the Wait Time, and the idea of the Wait Time can be introduced into the RRC connection release. However, due to the large number of MTC devices, if the MTC device obtains the Wait Time through the RRC connection release, the timer expires. After many MTC devices initiate RRC connection requests at the same time, they still have a lot of impact on the network, and even cause overload of the network. Aiming at the simultaneous initiation of the RRC connection request by many MTC devices in the related art, the network will still have a large impact on the network, and even cause network overload problems. Currently, no effective solution has been proposed. SUMMARY OF THE INVENTION A main object of the present invention is to provide a method and a terminal for a terminal to access a network, so as to at least solve the problem that the foregoing multiple MTC devices release the RRC connection request again, which still causes a large number of impacts on the network, and even causes network overload. . According to an aspect of the present invention, a method for a terminal to access a network is provided, including: determining, by the terminal, a waiting time required for re-accessing the network side when receiving the RRC connection release signaling sent by the network side; When the terminal determines that the time it has waited for is equal to or exceeds the waiting time, the terminal allows an RRC connection request to be initiated to the network side. Preferably, the determining, by the terminal, the waiting time for re-accessing the network side, the method includes: the terminal acquiring a preset access delay time, and determining a waiting time according to the access delay time. Preferably, the terminal acquires a preset access delay time, including one of the following:

The RRC connection release signaling acquires the access delay time; the terminal acquires the access delay time according to the system message of the network side; the terminal acquires the access delay time according to a manner predefined by the protocol. Preferably, the terminal determines the waiting time according to the access delay time, and includes one of the following: the terminal determines that the waiting time value is equal to the access delay time value; and the terminal determines the waiting time value a value equal to 0 to a random value between the access delay time values; the terminal determining that the waiting time value is equal to a product of the access delay time value and an adjustment factor, wherein the adjustment factor is based on the RRC connection release letter Or determining, by the network side, a system message or a protocol pre-defined manner; the terminal determining that the waiting time value is equal to a sum of the access delay time value and a random value. Preferably, the obtaining the access delay time according to the pre-defined manner of the protocol includes: obtaining, by the terminal, the access delay time according to a combination of any one or more of the following: a type and a location of the terminal The priority of the terminal, the priority of the application service initiated by the terminal, whether the terminal is roaming, the access level of the terminal on the network side, and the group to which the terminal belongs. Preferably, the determining, by the terminal, the waiting time for re-accessing the network side, the terminal includes: releasing, by the terminal, the release reason by using the RRC connection release signaling, and determining a waiting time according to the release reason. Preferably, the release cause comprises overloading on the network side. Preferably, after the terminal determines the waiting time required for the terminal to re-access the network side, the method further includes: transmitting, by the RRC layer of the terminal, the waiting time to an upper layer of the terminal; Terminal has When the waiting time is less than the waiting time, the upper layer of the terminal refuses to send the RRC connection request to the network side. According to another aspect of the present invention, a terminal is provided, including: a determining unit, configured to determine, when receiving an RRC connection release signaling sent by a network side, a waiting time required for the terminal to re-access the network side; And setting to initiate an RRC connection request to the network side when it is determined that the time that the terminal has waited for equal to or exceeds the waiting time. Preferably, the determining unit is further configured to acquire a preset access delay time, and determine a waiting time according to the access delay time. Preferably, the determining unit is further configured to acquire the access delay time according to the RRC connection release signaling; or obtain the access delay time according to the system message of the network side; or, according to the protocol The defined access time is obtained in a defined manner. Preferably, the determining unit is further configured to determine that the waiting time value is equal to the access delay time value; or determine that the waiting time value is equal to a random value between 0 and the access delay time value; Or determining, that the waiting time value is equal to a product of the access delay time value and an adjustment factor, where the adjustment factor is determined according to the RRC connection release signaling or a system message or a protocol predefined manner of the network side; Alternatively, it is determined that the waiting time value is equal to a sum of the access delay time value and a random value. Preferably, the determining unit is further configured to acquire the access delay time according to a combination of any one or more of the following: a type of the terminal, a priority of the terminal, and an application service initiated by the terminal. a priority, whether the terminal is roaming, an access level of the terminal on the network side, and a group to which the terminal belongs. Preferably, the determining unit is further configured to acquire a release reason by using the RRC connection release signaling, and determine a waiting time according to the release reason. In the embodiment of the present invention, when receiving the RRC connection release signaling sent by the network side, the terminal determines the waiting time required for re-accessing the network side, that is, determining, by each terminal, the RRC connection release signaling. A waiting time, instead of using the same waiting time as other terminals, avoids the subsequent RRC connection request with a large number of terminals simultaneously causing a large impact on the network, and even causing network overload. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawing: 1 is a schematic diagram of a connection denial process according to the related art; FIG. 2 is a process flow diagram of a method for a terminal to access a network according to an embodiment of the present invention; FIG. 3 is a base station selecting a low priority MTC device according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. In the related art, in the case of a large number of MTC devices, if the MTC device obtains the Wait Time through the RRC connection release, after the timer corresponding to the Wait time expires, the plurality of MTC devices will simultaneously initiate an RRC connection request, and the network will still be sent to the network. A lot of shocks are generated, and even the network is overloaded. To solve the above technical problem, the embodiment of the present invention provides a method for a terminal to access a network. The processing flow is as shown in FIG. 2, and the process includes: Step 202: When the terminal receives the RRC connection release signaling sent by the network side, the terminal determines itself. Re-accessing the waiting time required by the network side; Step 204: When the terminal determines that the time it has waited for is equal to or exceeds the determined waiting time, the terminal allows the RRC connection request to be initiated to the network side. In step 204, the premise that the terminal re-initiates the RRC connection request to the network side is that the non-access stratum of the terminal needs to initiate signaling services or data services. When the terminal has a service requirement, the terminal needs to maintain the waiting state before the timer corresponding to the waiting time expires, and the RRC connection request may not be initiated. In the embodiment of the present invention, when receiving the RRC connection release signaling sent by the network side, the terminal determines the waiting time required for re-accessing the network side, that is, determining, by each terminal, the RRC connection release signaling. A waiting time, instead of using the same waiting time as other terminals, avoids the subsequent RRC connection request with a large number of terminals simultaneously causing a large impact on the network, and even causing network overload. During the implementation, the terminal determines that the waiting time for re-accessing the network side can be determined by multiple methods. For example, a preferred method is: the terminal acquires a preset access delay time, and determines according to the access delay time. waiting time. The access delay time may be obtained in multiple manners. For example, the terminal acquires an access delay time according to the RRC connection release signaling. For example, the terminal acquires an access delay time according to the system message of the network side; For example, the terminal obtains the access delay time according to its own predefined manner in the network side (ie, the protocol pre-defined way). Of course, there are other acquisition methods, and the access delay time can be obtained. The specific implementation manner is determined according to actual conditions. In the implementation, after the terminal obtains the access delay time, the waiting time is determined according to the access delay time, and the terminal determines that the waiting time value is equal to the access delay time value; or the terminal determines that the waiting time value is equal to 0 to the access delay time. A random value between values, for example, the access delay time value is 10, then the wait time value is a random value in [0, 10], such as 5, or 7; for example, the access delay time value is 20, The waiting time value is a random value in [0, 20]; or the terminal determines that the waiting time value is equal to the product of the access delay time value and the adjustment factor, wherein the adjustment factor is based on the RRC connection release signaling or the network side The system message or the terminal is determined by the network side pre-defined (ie, protocol pre-defined), for example, the adjustment factor is a random value in [0, 1], and if the adjustment factor takes a value of 0.1, the current terminal determines its waiting time. The value is one tenth of the value of the access delay time. Further, the terminal may determine that the waiting time value is equal to the sum of the access delay time value and the random value. For example, the random value N is a natural number, N can take the values 0, 1, 2, 3, etc., the access latency value equal to the delay time sum of the N values. During the implementation, the terminal obtains the access delay time according to the manner defined by the terminal and the network side, including: The terminal acquires the access delay time according to the combination of any one or more of the following: the type of the terminal, the priority of the terminal, and the terminal initiated. The priority of the application service, whether the terminal is roaming, the access level of the terminal on the network side, and the group to which the terminal belongs. In the implementation, the terminal obtains the release reason by releasing the signaling through the RRC connection, and determines the waiting time according to the release reason, where the release cause includes the network side overload. The method for the terminal to access the network provided by the embodiment of the present invention may be applied to the H2H device (ie, the UE), and may also be applied to the M2M device, that is, the MTC device, which is described in several specific embodiments. Embodiment 1 In an LTE system, different types of terminals include an H2H device and an MTC device access network, and some are in a connected state, and some are in an idle state. At a certain moment, the core network sends an indication of overload control to the base station due to the increased load of the core network. After the base station obtains the indication of the overload control, the base station selects some terminals according to the type of the terminal, the priority of the service initiated by the terminal, or the priority of the terminal. The release is implemented, for example, the MTC device may be selected for release, or the low priority terminal is released, or the terminal with low service priority is selected to release the load on the network side. In this embodiment, the base station selects the low-priority MTC device to release its RRC connection, and the release process is as shown in FIG. 3: Step 302: The base station sends an RRC connection release signaling to the MTC device, where the signaling includes the access. Delay time and release reason; Step 304: After receiving the RRC connection release signaling, the MTC device obtains an access delay time; the MTC device sets a timer equal to the access delay time, and starts the timer; before the timer expires, The MTC device cannot initiate an RRC connection request again. When the timer expires, the MTC device generates a random time again. During the random time period, the MTC device cannot still initiate the RRC connection request again. The MTC device can initiate an RRC connection request again only after the random time expires. The random time length generated by the MTC device may be referenced by the access delay time. For example, the MTC device generates a uniformly distributed random number between 0 and 1, and multiplies the random number by the access delay time to obtain a random time. Or the MTC device randomly generates a random time within a predetermined time (eg, within 10 seconds or within 10 minutes). In this embodiment, after receiving the release signaling, the MTC device needs to generate a random time again after the timer expires. Only after the random time expires can the RRC connection request be initiated again, so that a large number of MTC devices can be avoided. After being released by the network, accessing the network again at the same time can discretize the time when different MTC devices access the network again. Thus in step 304, the latency of the MTC device is equal to the access delay time value plus a random value. It should be noted that different time names may be used in the actual application, and the foregoing time name is not limited in the embodiment of the present invention. There are other implementation manners in this embodiment. For example, because the RRC connection release signaling includes an access delay time, after receiving the MTC device, the MTC device may directly generate a random number that is less than the access delay time, and the waiting time is equal to the generated random number. Or if the RRC connection release signaling further includes an adjustment factor, after the MTC device receives, the waiting time of the MTC device is the product of the access delay time and the adjustment factor; or the waiting time is equal to the product of the access delay time and the adjustment factor. Add a random time. The MTC device can initiate an RRC connection request again only after the waiting time has expired. Adding an adjustment factor to the RRC connection release signaling can represent a very wide time period using a limited number of bits. In step 302, the eNB may carry the information of the multiple terminals that need to be released in the RRC connection release signaling. For example, if the terminal belongs to a certain group, the base station may carry the identifier of the group in the RRC connection release, so that a letter may be passed. The connection of all the groups is released; or the base station directly carries the identifiers of the multiple terminals in the RRC connection release signaling, so that the group release can also be achieved. The base station can transmit the group release signaling on the common channel, so that the terminal can detect the signal released by the community. In the scenario of group release, in order to make different terminals again When accessing the network, the terminal can be staggered, and the terminal introduces a random time according to the access delay time in the release signaling, and can be staggered again. This embodiment describes the scenario of LTE, but for the Wide-band Code Division Multiple Access (WCDMA) system and the Global System for Mobile communication Edge Radio Access Network (GERAN). The system is equally applicable, and other embodiments are similar. The only difference is that in the WCDMA system, the RRC connection release signaling is the Radio Network Controller (RNC). Embodiment 2 In an LTE system, different types of terminals include an H2H device and an MTC device access network, and some are in a connected state, and some are in an idle state. At some point, the base station detects that its own load is high, or through background operation and maintenance.

(Operation & Maintenance, OAM) The server detects that the core network is heavily loaded, and the base station makes a decision to release some of the terminals. In this embodiment, the base station selects the release of the lower priority terminal according to the priority of the service. The base station sends an RRC connection release signaling to the terminal, where the signaling includes a release reason. After receiving the release signaling, the terminal sets the waiting time according to the access delay time in the system message. It should be noted that the terminal may read the access delay time in the system message when receiving the release signaling, or obtain the access delay time in the system message before receiving the release signaling, if the terminal acquires in advance After the access delay time, the terminal applies the parameter only after receiving the signaling of the RRC connection release. In the existing system message, the access delay time is not included. In order to implement the present invention, it is required to increase the cell to indicate the access delay time. In particular, the system message can set the corresponding access delay time for different types of terminals: You can set the corresponding access delay time for terminals of different priorities. For example, the meter-type terminal can be tolerated for a long time. The priority can be set to a lower priority. For the terminal of the monitoring or alarm type, it needs to be reported immediately. The priority of the data needs to be set to normal priority or high priority. Here, the priority of the terminal can be divided into two or more priority levels according to different application types. The access delay time (the priority of the service can be set according to the service quality parameter of the service); the corresponding access delay time can be set for the terminal that is roaming; the corresponding connection can be set for different groups to which the terminal belongs Incoming delay time; corresponding access delay can be set for the access level of the terminal Time (the access level is saved in the user's card of the terminal). The terminal may set the waiting time according to the following manner: the waiting time is equal to the access delay time; or, the waiting time is a random value less than the access delay time; or The wait time is equal to the access delay time plus a random time. The timer that starts the waiting time of the terminal, and the terminal cannot initiate again before the timer expires.

RRC connection request (or random access). At the same time, the RRC layer of the terminal notifies the upper layer (ie, the non-access stratum of the terminal) the waiting time, so that the upper layer of the terminal can no longer initiate the service establishment request within the time. Embodiment 3 In the LTE system, different types of terminals include an H2H device and an MTC device access network, and some are in a connected state, and some are in an idle state. At some point, the base station detects that its own load is high, or the background operation and maintenance server detects that the load of the core network is high, and the base station makes a decision to release part of the terminal. In this embodiment, the base station selects the release of the lower priority terminal according to the priority of the service. The base station sends an RRC connection release signaling to the terminal, where the signaling includes a release reason. After receiving the release signaling, the terminal obtains the access delay time according to the pre-defined manner of the protocol. The predefined manner of the protocol may include one of the following scenarios or a combination thereof: The access delay time is pre-defined according to the type of the terminal, such as The access delay time of the MTC device is 600 seconds. The access delay time is pre-agreed according to the priority of the terminal. For example, the access delay time of the low-priority MTC device is 1000 seconds, and the high-priority MTC device is connected. The access delay time is 200 seconds, and the access delay time of the H2H device is 0 seconds. The access delay time is pre-agreed according to the priority of the application service initiated by the terminal, such as pre-arranging the connection of the terminal that has established or initiated the establishment of the high priority service. The access delay time is 200 milliseconds, and the access delay time of the terminal that has established or initiated the establishment of the low priority service is 500 milliseconds; the access delay time is pre-agreed according to the access level of the terminal, such as pre-arranging an access level (Access) Class) The access delay time of the terminal. Each terminal has an associated AC level. Each connection is pre-agreed. The access delay time corresponding to the level; the access delay time is pre-agreed according to the group to which the terminal belongs. For example, the access delay time of the terminal of the partial group is 200 seconds, and the access delay time of the terminals of other groups is 0 seconds; The access delay time is pre-agreed according to whether the terminal is roaming. For example, the access delay time of the terminal that is roaming in advance is 300 seconds, and the access delay time of the terminal without roaming is 0 seconds. USIM card at the terminal (Universal Subscriber Identity Module, HPLMN (Home Public Land Mobile Network, Local Public Land Mobile Network), may also include EHPLMN (Equivalent Home PLMN) If the current network is not HPLMN, it indicates that the terminal is a roaming terminal; or if the current network is neither HPLMN nor EHPLMN, the terminal is a roaming terminal. The terminal can obtain the PLMN identity of the network to which the accessed cell belongs by using the system message, and can determine whether it is roaming according to the HPLMN and the EHPLMN in the USIM card. After the terminal obtains the access delay time, set the waiting time according to one of the following ways: the waiting time is equal to the access delay time; the waiting time is a random value less than the access delay time; the waiting time is equal to the access delay time and the adjustment factor The product, the adjustment factor is also pre-agreed; the waiting time is equal to the access delay time plus a random time. The timer that starts the waiting time of the terminal, and the terminal cannot initiate again before the timer expires.

RRC connection request (or random access). At the same time, the RRC layer of the terminal notifies the upper layer (ie, the non-access stratum of the terminal) the waiting time, so that the upper layer of the terminal can no longer initiate the service establishment request within the time. Embodiment 4 In the LTE system, different types of terminals include an H2H device and an MTC device access network, and some are in a connected state, and some are in an idle state. At a certain moment, the core network sends an indication of overload control to the base station due to the increased load of the core network. After the base station obtains the indication of the overload control, the base station selects some terminals according to the type of the terminal, the priority of the service initiated by the terminal, or the priority of the terminal. The release is implemented, for example, the MTC device may be selected for release, or the low priority terminal is released, or the terminal with low service priority is selected to release the load on the network side. In this embodiment, the base station selects the released terminal according to whether the terminal is roaming. In this case, the core network needs to indicate to the base station whether the terminal is roaming, or the terminal reports to the base station whether it roams, and then the base station sends an RRC connection release letter to the roaming terminal. Or the base station selects the roaming MTC device to release, and sends the RRC connection release signaling to the roaming MTC device; or the base station selects the roaming low priority terminal to release, and sends the RRC connection release signaling to the roaming low priority terminal. The reason for the release in the signaling is the network side overload. After receiving the reason for the release, the terminal obtains the access delay time according to the pre-defined method of the protocol, and the protocol may pre-agreed the access delay time corresponding to different release reasons. If the network side overload is agreed, the access delay time is 500 seconds. In order to reduce the impact on the existing protocol, for the reason of the existing release, the access delay time can be agreed to be 0 seconds. After the terminal obtains the access delay time, set the waiting time according to one of the following ways: the waiting time is equal to the access delay time; the waiting time is a random value less than the access delay time; the waiting time is equal to the access delay time plus a random time. The terminal starts a timer corresponding to the waiting time, and the terminal cannot initiate an RRC connection request (or random access) again before the timer expires. At the same time, the RRC layer of the terminal notifies the upper layer (ie, the non-access stratum of the terminal) to release the reason, so that the upper layer of the terminal can learn the release reason and take corresponding operations. Based on the same inventive concept, the embodiment of the present invention further provides a terminal. The structure of the terminal is as shown in FIG. 4, and includes: a determining unit 401, configured to: when receiving a radio resource control RRC connection release command sent by the network side, determine the The waiting time required for the terminal to re-access the network side; the connecting unit 402 is configured to initiate an RRC connection request to the network side when it is determined that the time that the terminal has waited for is equal to or exceeds the determined waiting time. In an embodiment, the determining unit 401 may be configured to acquire a preset access delay time and determine a waiting time according to the access delay time. In an embodiment, the determining unit 401 may be configured to obtain an access delay time according to the RRC connection release signaling; or obtain an access delay time according to a system message of the network side; or acquire according to a manner defined by itself and the network side. Access delay time. In an embodiment, the determining unit 401 may be configured to determine that the waiting time value is equal to the access delay time value; or determine that the waiting time value is equal to a random value between 0 and the access delay time value; or, determine that the waiting time value is equal to The product of the access delay time value and the adjustment factor, wherein the adjustment factor is determined according to the RRC connection release signaling or the system message of the network side or the terminal and the network side predefined; or, determining that the waiting time value is equal to the access delay time value and the randomization The sum of the values. In an embodiment, the determining unit 401 may be configured to obtain an access delay time according to a combination of any one or more of the following: a type of the terminal, a priority of the terminal, a priority of the application service initiated by the terminal, whether the terminal is roaming, The access level of the terminal on the network side and the group to which the terminal belongs. In an embodiment, the determining unit 401 may be configured to acquire a release cause by the RRC connection release signaling, and determine the waiting time according to the release reason. From the above description, it can be seen that the present invention achieves the following technical effects: In the embodiment of the present invention, when the terminal receives the RRC connection release signaling sent by the network side, the terminal determines that it needs to re-access the network side. Time, that is, when each terminal receives the RRC connection release signaling, it determines a waiting time for itself, instead of adopting the same waiting time as other terminals, so as to avoid subsequent large-scale attacks on the network by simultaneously initiating an RRC connection request with a large number of terminals, even Causes network overload. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A method for a terminal to access a network, comprising:

When receiving the radio resource control RRC connection release signaling sent by the network side, the terminal determines the waiting time required for re-accessing the network side;

The terminal allows an RRC connection request to be initiated to the network side when the terminal determines that the time it has waited for is equal to or exceeds the waiting time.

The method according to claim 1, wherein the terminal determines a waiting time required for the terminal to re-access the network side, the method includes: the terminal acquiring a preset access delay time, and according to the access delay Time determines the waiting time.

The method according to claim 2, wherein the terminal acquires a preset access delay time, including one of the following:

The terminal acquires the access delay time according to the RRC connection release signaling; the terminal acquires the access delay time according to the system message of the network side; the terminal acquires the manner according to a predefined manner in a protocol. Access delay time.

The method according to claim 2 or 3, wherein the terminal determines a waiting time according to the access delay time, including one of the following:

The terminal determines that the waiting time value is equal to the access delay time value;

Determining, by the terminal, that the waiting time value is equal to 0 to a random value between the access delay time values;

Determining, by the terminal, that the waiting time value is equal to a product of the access delay time value and an adjustment factor, where the adjustment factor is determined according to the RRC connection release signaling or the network side system message or a protocol predefined manner;

The terminal determines that the waiting time value is equal to a sum of the access delay time value and a random value.

The method according to claim 3, wherein the acquiring the access delay time according to a predefined manner of the protocol includes: The terminal acquires the access delay time according to any one or more of the following combinations: the type of the terminal, the priority of the terminal, the priority of the application service initiated by the terminal, and whether the terminal roams. And an access level of the terminal on the network side and a group to which the terminal belongs.

The method of claim 1, wherein the terminal determines the waiting time required for the terminal to re-access the network side, the method includes: the terminal acquiring the release reason by using the RRC connection release signaling, and according to the method, The reason for the release determines the waiting time.

7. The method according to claim 6, wherein the release cause comprises the network side overload.

The method according to claim 1, after the terminal determines the waiting time required for the terminal to re-access the network side, the method further includes:

The RRC layer of the terminal transmits the waiting time to an upper layer of the terminal;

When the upper layer of the terminal determines that the time that the terminal has waited for is less than the waiting time, the upper layer of the terminal refuses to send the RRC connection request to the network side.

9. A terminal comprising:

a determining unit, configured to: when receiving the radio resource control RRC connection release signaling sent by the network side, determine a waiting time required for the terminal to re-access the network side;

The connection unit is configured to allow an RRC connection request to be initiated to the network side when it is determined that the time that the terminal has waited for equal to or exceeds the waiting time.

The terminal according to claim 9, wherein the determining unit is further configured to acquire a preset access delay time, and determine a waiting time according to the access delay time.

The terminal according to claim 10, wherein the determining unit is further configured to acquire the access delay time according to the RRC connection release signaling; or obtain the connection according to the system message of the network side. The delay time is entered; or, the access delay time is obtained according to a manner predefined by the protocol.

The terminal according to claim 10 or 11, wherein the determining unit is further configured to determine that the waiting time value is equal to the access delay time value; or determine that the waiting time value is equal to 0 to the a random value between the access delay time values; or determining that the waiting time value is equal to a product of the access delay time value and an adjustment factor, wherein the adjustment factor is according to the RRC connection release signaling or the network side The system message or protocol is determined in a predefined manner; or, determining that the latency value is equal to the sum of the access delay time value and the random value.

The terminal according to claim 11, wherein the determining unit is further configured to acquire the access delay time according to a combination of any one or more of the following: a type of the terminal, a priority of the terminal The priority of the application service initiated by the terminal, whether the terminal is roaming, the access level of the terminal on the network side, and the group to which the terminal belongs.

The terminal according to claim 9, wherein the determining unit is further configured to acquire a release cause by the RRC connection release signaling, and determine a waiting time according to the release cause.