WO2012094982A1 - 一种接入控制的方法及装置 - Google Patents

一种接入控制的方法及装置 Download PDF

Info

Publication number
WO2012094982A1
WO2012094982A1 PCT/CN2012/070176 CN2012070176W WO2012094982A1 WO 2012094982 A1 WO2012094982 A1 WO 2012094982A1 CN 2012070176 W CN2012070176 W CN 2012070176W WO 2012094982 A1 WO2012094982 A1 WO 2012094982A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran
overload
backoff time
access
network
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2012/070176
Other languages
English (en)
French (fr)
Inventor
冯媛
全海洋
房家奕
赵毅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
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 Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Priority to US13/978,402 priority Critical patent/US9220031B2/en
Priority to EP12733875.4A priority patent/EP2665310B1/en
Publication of WO2012094982A1 publication Critical patent/WO2012094982A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and an apparatus for access control. Background technique
  • M2M is the machine name of Machine to Machine, which refers to the type of business that communicates between machines and machines.
  • the Internet of Things (IOT) refers to the application of ⁇ 2 ⁇ in the WAN, especially the mobile operator network, that is, using the mobile network operator's wireless network as a platform, using multiple transmission methods (CDMA (Code Division Multiple) Access, CDMA (Global System for Mobile communication) / SMS (Short Message Service), etc., through industry-specific terminals, serving industry users machine-to-machine wireless Data transmission business.
  • CDMA Code Division Multiple
  • CDMA Global System for Mobile communication
  • SMS Short Message Service
  • the M2M/IOT business has a potential market and is geographically distributed. It can be deployed in any network-accessible location, replacing high-cost manned, real-world unattended, for electricity, water, oil, antimony, Information collection in industries such as environmental protection, meteorology, tobacco, and finance is of great significance and has great market value.
  • wireless communication is one of the preferred solutions.
  • Some existing industry applications such as remote meter reading, 7j-bit monitoring, etc., all use GPRS (General Packet Radio Service). Business) Network transmission sensor data set.
  • GPRS General Packet Radio Service
  • Business Network transmission sensor data set.
  • the RRC (Radio Resource Control) connection reject message carries only one backoff time, and is not related to the CN (Core Network) overload or the RAN (Radio Access Network). ) overloaded.
  • the backoff time is too short.
  • the LTE (Long Term Evolution) system is 16 seconds, which causes the UE to access the network excessively frequently, which is not conducive to alleviating network congestion.
  • congestion on the CN There is no difference between the RAN book congestion and the access control granularity.
  • Embodiments of the present invention provide a method and an apparatus for access control, which are used to implement better access control.
  • a method for access control, applied to the RAN side includes the following steps:
  • the radio access network RAN determines whether to allow the UE to access the RAN and the CN according to the current RAN and CN load conditions and the terminal or service information reported by the UE;
  • the RAN When access to at least one of the RAN and the CN is not allowed, the RAN transmits an indication message with a backoff time corresponding to the network that is not allowed to access to the UE.
  • a method for processing a message in an access process, which is applied to a UE side includes the following steps:
  • the UE After receiving the access request, the UE receives an indication message with a backoff time corresponding to the network that is not allowed to access; the UE parses the indication message to obtain a backoff time corresponding to the network that is not allowed to access;
  • the UE does not allow access to the network again according to the backoff time corresponding to the network that is not allowed to access.
  • An access network device including:
  • control module configured to determine, according to a load condition of the current RAN and the CN, and a terminal or service information reported by the UE, whether the UE is allowed to access the RAN and the CN in the random access process;
  • an interface module configured to send, to the UE, an indication message with a backoff time corresponding to the network that is not allowed to access, when the at least one of the RAN and the CN is not allowed to access.
  • a user equipment including:
  • An interface module configured to: after sending an access request, receive an indication message with a backoff time corresponding to a network that is not allowed to access;
  • the parsing module is configured to parse the indication message to obtain a backoff time corresponding to the network that is not allowed to access; and the control module is configured to not access the network again according to the backoff time corresponding to the network that is not allowed to access.
  • a core network device including:
  • the control module is configured to determine whether an overload occurs, and if yes, determine a backoff time for the overload; and the interface module is configured to send, to the RAN, an overload control message carrying a backoff time for the overload.
  • the radio access network performs the judgment on the access control of the RAN and the CN (core network) in the access process, and if there is a network that is not allowed to access, that is, the network is overloaded,
  • the indication message of the UE carries a backoff time corresponding to the network that is not allowed to access. That is to say, the RAN can set the backoff time in a targeted manner for the overload condition of the RAN and the CN, and better perform access control, thereby avoiding network congestion and excessive terminal access delay as much as possible.
  • FIG. 1 is a flowchart of a main method for access control on a network side according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a main method for access control on a UE side according to an embodiment of the present invention
  • 3 is a flowchart of a method for access control on both sides of a RAN and a UE according to an embodiment of the present invention
  • 4 is a flowchart of a method for performing access control that does not need to distinguish between a single CN node overload and only performs backoff time according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for performing access control by using a backoff time and a RAN overload indication without distinguishing a single CN node from being overloaded according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for performing access control when a single CN node is overloaded and an S-TMSI is reported when the S-TMSI is overloaded;
  • FIG. 7 is a flowchart of a method for performing access control when a single CN node is overloaded and reported to GUMMEI according to an embodiment of the present invention
  • FIG. 8 is a structural diagram of an access network device according to an embodiment of the present invention.
  • FIG. 9 is a main structural diagram of a UE according to an embodiment of the present invention.
  • FIG. 10 is a detailed structural diagram of a UE according to an embodiment of the present invention.
  • FIG. 11 is a structural diagram of a core network device according to an embodiment of the present invention. detailed description
  • the radio access network performs the judgment on the access control of the RAN and the CN (core network) in the access process, and if there is a network that is not allowed to access, that is, the network is overloaded,
  • the indication message of the UE carries a backoff time corresponding to the network that is not allowed to access. That is to say, the RAN can set the backoff time in a targeted manner for the overload condition of the RAN and the CN, and better perform access control, thereby avoiding network congestion and excessive terminal access delay as much as possible.
  • the wait time in the RRC Connection Reject message in the prior art does not distinguish whether it is a backoff time for CN overload or a backoff time for RAN overload.
  • the backoff time in the RRC connection reject message in the prior art is taken as the backoff time for the RAN overload, and the backoff time for the CN overload is indicated by adding a new information element (IE).
  • IE new information element
  • the backoff time can be understood by using the non-backoff time literal value, for example, according to the understanding that the size of each integer value represents a power of 2. Referring to FIG. 1, the main method of access control on the network side in this embodiment is as follows:
  • Step 101 In the random access procedure, the radio access network RAN determines whether to allow access to the RAN and the CN according to the current RAN and CN load conditions and the terminal or service information reported by the UE.
  • the judging process may occur after receiving the RRC Connection Request message or after receiving the RRC connection setup complete message.
  • the UE may report the terminal or service information through an RRC connection request message, or establish an RRC connection.
  • the completion message is reported to the terminal or service information.
  • Step 102 When at least one of the RAN and the CN is not allowed, the RAN sends an indication message with a backoff time corresponding to the network that is not allowed to access to the UE. If the CN is overloaded, that is, the CN is not allowed to be accessed, the backoff time carried includes the backoff time for the CN overload; if the RAN is overloaded, that is, the RAN is not allowed to be accessed, the carried back time includes the backoff time for the RAN overload; Both the CN and the CN are overloaded, and the backoff time carried includes the backoff time for the RAN overload and the backoff time for the CN overload.
  • the RAN sends an RRC Connection Setup message to the UE; After the establishment of the RRC connection is completed, the access control is judged, and the RAN and the CN are not overloaded, and the RAN maintains the status quo, and does not need to send an RRC Connection Release (RRCConnectionRelease) message to the UE.
  • RRC Connection Release RRCConnectionRelease
  • the implementation method of the UE side in the access process needs to be introduced.
  • the main method of access control on the UE side in this embodiment is as follows:
  • Step 201 After sending the access request, the UE receives an indication message with a backoff time corresponding to the network that is not allowed to access.
  • the backoff time includes a backoff time for RAN overload, a backoff time for CN overload, or a backoff time for RAN overload and a backoff time for CN overload.
  • Step 202 The UE parses the indication message to obtain a backoff time corresponding to the network that is not allowed to access.
  • Step 203 The UE does not allow to access the network again according to the backoff time corresponding to the network that is not allowed to access.
  • the UE discovery indication message has a backoff time for the RAN overload
  • the UE performs the access control according to the backoff time for the RAN overload.
  • the UE finds that the indication message has a backoff time for the CN overload it performs access control according to the backoff time for the CN overload.
  • the UE finds that the indication message has a backoff time for RAN and CN overload it performs access control according to the backoff time for RAN and CN overload.
  • the access process involves the interaction between the RAN and the UE.
  • the implementation of the access control is described below in conjunction with the RAN and the UE.
  • the method for access control on both sides of the RAN and the UE in this embodiment is as follows:
  • Step 301 The UE sends an RRC connection request message to the RAN, where the RRC connection request message may carry the terminal or service information of the UE and the establishment cause.
  • the terminal or service information includes one of the following information: indicates whether it is a low priority access terminal or service; indicates whether it is a roaming terminal and specific roaming subclass information; indicates whether it is a time tolerant terminal or service; indicates whether it is time Controllable terminal or service; indicates whether it is a small data terminal or service.
  • the terminal or service information may also include other information related to the terminal or service, which is not listed here.
  • the establishment reasons include one of the following reasons: UE-initiated emergency call, UE called access (mt-access), high priority access (high priority access), UE-initiated signaling (mo-Signalling) , data transmission (mo-Data) and low priority Priority access (lowPriority Access). Different establishment reasons may correspond to different access priorities.
  • Step 302 The RAN determines whether to allow the UE to access the RAN and the CN according to the terminal or service information of the UE and the establishment cause, and according to the obtained load information of the current network, when accessing at least one of the RAN and the CN is not allowed. Proceed to step 303, otherwise proceed to step 304.
  • the load information of the current network obtained in the RAN includes the RAN load information and the CN load information, that is, the load conditions of the RAN and the CN, and the CN load information may be controlled by the Mobility Management Entity (MME) through the overload control (OVERLOAD START).
  • MME Mobility Management Entity
  • OVERLOAD START overload control
  • the message is sent to the RAN or configured by the OAM (Operation, Administration and Maintenance) to the RAN.
  • the CN load information such as: rejects all low-priority access devices or services for non-emergency calls; rejects all caller data services and low-priority access devices or services; rejects all caller signaling services for non-emergency calls and Low priority access devices or services; only emergency services and called access are allowed.
  • the CN load information further includes a backoff time for the CN overload, and the backoff time may correspond to the rejection reason.
  • Step 303 The RAN returns an RRC Connection Reject (RRCConnectionReject) message carrying the backoff time corresponding to the network that is not allowed to access to the UE.
  • RRCConnectionReject RRC Connection Reject
  • the RAN Before step 303, when the RAN determines that there is a network overload, the RAN needs to determine the backoff time for the network corresponding to the network that is not allowed to access.
  • the MME sends a reference value of the backoff time to the RAN through the overload initial message, or the reference value of the OAM configuration backoff time is given to the RAN.
  • the RAN determines the final backoff time based on the reference value.
  • the RAN directly uses the reference value as the backoff time; or, the RAN generates a random number, and uses the power of the random number with the reference value as the backoff time; or, the reference value is a range.
  • the RAN generates a random number in the middle reference range, and uses the random number as the backoff time; or, the RAN generates a random number not less than the reference value, and uses the random number as the backoff time.
  • the backoff time There may be other ways to determine the backoff time, and the purpose of alleviating the network side load pressure may be applied to the present embodiment. It is determined that both the RAN and the backoff time for CN overload can be used in the above manner. Preferably, the backoff time in this embodiment is in seconds.
  • Step 304 The RAN returns an RRC Connection Setup message to the UE. Continue with step 306.
  • Step 305 The UE performs access network control according to a backoff time corresponding to the network that is not allowed to access, for example, does not allow access to the network again.
  • Step 306 The UE returns an RRC Connection Setup Complete message to the RAN.
  • step 305 if the RRC connection reject message received by the UE carries the effective backoff time of the CN, the UE needs to leave the backoff time for the CN overload to the internal NAS (Non-Access Stratum) layer. deal with.
  • the T302 timer is started and set according to the backoff time for the RAN overload.
  • the UE controls the temporary through the NAS layer and the T302 timer. Stop access.
  • the T302 timer is the timer specified in the standard. In the existing standard, there is only one Wait Time in the connection reject message. When the UE receives the RRC Connection Reject message, it needs to start the timer T302 according to the Wait Time. try. In the present invention, a new backoff time is added to this message.
  • the original Wait Time still corresponds to the timer T 302.
  • the RAN performs the judgment on the access control of the RAN according to the terminal or service information of the UE and the establishment cause, and according to the obtained load information of the current network, if the access is not allowed. Sending an RRC connection reject message carrying the backoff time for the RAN overload to the UE, and then performing the backoff processing by the UE; if the access is allowed, sending an RRC connection setup message to the UE, completing the RRC connection establishment with the UE, after completing the establishment If the access control of the CN is not performed, if the CN is not allowed to be accessed, the RRC connection release message is sent to the UE, and the RRC connection is disconnected from the UE; otherwise, the registration process to the CN is completed.
  • CN overload does not need to be differentiated whether the MME in the entire MME Pool is overloaded or only some MMEs are overloaded, that is, when the RAN receives load information of n MMEs, the entire CN is determined to be overloaded.
  • the number of pre-configured parameters n is lower than the total number of MMEs in the MME pool connected to the RAN. If the RAN receives the load information of the MME, it determines that the MME is overloaded, and does not receive the load information of other MMEs in the MME pool, and determines that the other MMEs are not overloaded.
  • Step 401 The UE sends an RRC connection request message to the RAN, where the RRC connection request message may carry the terminal or service information of the UE and the establishment cause.
  • Step 402 The RAN determines whether to allow access to the RAN and the CN according to the terminal or service information of the UE and the establishment cause, and according to the obtained load information of the current network, and when accessing at least one of the RAN and the CN is not allowed, continuing Step 403, otherwise proceed to step 404. If the load information of the current network in the RAN includes the overload control information of any MME, the entire CN is determined to be overloaded. If the reason for establishing the UE meets the access reason for denying access in the overload control information of the MME, The access request of the UE is rejected.
  • the load information of the MME in this embodiment includes overload control information of the MME.
  • Step 403 The RAN returns an RRC Connection Reject message carrying the backoff time for the RAN overload or carrying the backoff time for the RAN overload and the CN overload respectively. Continue with step 405.
  • Step 404 The RAN returns an RRC Connection Setup message to the UE. Proceed to step 406.
  • Step 405 The UE parses the RRC Connection Reject message, and does not allow to access the network again according to the backoff time for the RAN and for the CN overload.
  • Step 406 The UE returns an RRC Connection Setup Complete message to the RAN.
  • step 403 if the CN is not overloaded (that is, the CN is allowed to access), and the RAN is overloaded (that is, the RAN is not allowed to access), the RRC connection reject message does not carry the backoff time for the CN overload, and only carries the overload for the RAN. Backoff time.
  • step 405 when the UE finds that there is only the backoff time for the RAN overload, it is determined that the CN is not overloaded, and the RAN is overloaded, and only the backoff time for the RAN overload is processed, such as starting and setting the T302 timer.
  • the RRC Connection Reject message carries the backoff time for the CN overload.
  • the backoff time for the CN overload is handed over to the internal NAS layer for processing.
  • the backoff time for the RAN overload may be set to a specified value, and when the UE finds that the backoff time for the RAN overload is a specified value, the backoff time for the RAN overload is ignored, or the overload for the RAN is ignored.
  • the backoff time is retracted.
  • the specified value can be set to the minimum backoff time value specified by the system. The minimum backoff time value that may be specified by different systems is different.
  • the RAN is also overloaded, and the backoff time for the RAN overload is not a specified value, and the UE processes the backoff time for the RAN overload.
  • the UE obtains the backoff time for the RAN and the CN overload.
  • the RRC layer in the UE maintains the T302 timer, and the NAS layer maintains a timer corresponding to the backoff time of the CN overload.
  • the RRC layer notifies the NAS layer that the T302 timer is turned on or times out. When the T302 timer is valid, the NAS layer disables all access requests that need to be initiated.
  • the NAS layer determines whether to prohibit the initiation of access according to the timer corresponding to the backoff time of the CN overload and the establishment cause. Specifically, the UE is allowed to access at the NAS layer, and whether the UE can finally allow access also needs to be determined according to AS layer rules.
  • the UE In order to alleviate the network side access load, it is also possible to determine whether to allow the access to be initiated on the UE side. For example, when the UE receives the indication message and knows that the CN is overloaded by the indication message, it records the establishment cause corresponding to the RRC connection corresponding to the indication message. If the access priority of the access request is not higher than the access priority of the established establishment cause, the access is prohibited. If the access is performed this time. The access priority of the request establishment cause is higher than the recorded establishment cause priority, and the timer corresponding to all backoff times is invalid, and the access request is sent.
  • the method for distinguishing a single CN node from being overloaded and performing access control through the backoff time and the RAN overload indication is as follows:
  • Step 501 The UE sends an RRC connection request message to the RAN, where the RRC connection request message may carry the terminal or service information of the UE and the establishment cause.
  • Step 502 The RAN determines whether to allow access to the RAN and the CN according to the terminal or service information of the UE and the establishment cause, and according to the obtained load information of the current network, and when the access to the RAN and the CN is not allowed to continue, Step 503, otherwise proceed to step 504.
  • the load information of the current network obtained in the RAN includes the overload control information of any MME, it is determined that the entire CN is overloaded, and the establishment cause of the UE satisfies the access reason rejected by the overload control information of the MME, and the UE is rejected. Access request.
  • Step 503 The RAN returns an RRC Connection Reject message carrying the backoff time for the RAN overload, the RAN overload indication, and the backoff time for the CN overload when the CN is overloaded to the UE.
  • the RAN overload indication may indicate whether the RAN is overloaded, and may also indicate whether the backoff time for the RAN overload is valid.
  • the RAN overload indication is a RAN overload indication indicating that the RAN is overloaded, it indicates that the carried back time for the RAN overload is valid;
  • the RAN overload indication is a RAN overload indication indicating that the RAN is not overloaded, it also indicates that the carried back time for the RAN overload is invalid.
  • Step 504 The RAN returns an RRC Connection Setup message to the UE. Continue with step 506.
  • Step 505 The UE parses the RRC connection reject message, and does not allow to access the network again according to the RAN overload indication, the RAN overload, and the backoff time for the CN overload.
  • Step 506 The UE returns an RRC Connection Setup Complete message to the RAN.
  • the carried backoff time includes a backoff time for the CN overload, and the RAN overload indication is a RAN overload indication indicating that the RAN is not overloaded.
  • the RRC connection reject message may also carry the backoff time for the RAN overload, but the backoff time for the RAN overload is invalid.
  • step 505 when the UE finds that the backoff time for the CN overload is carried, the backoff time for the CN overload is handed over to the internal NAS layer, and when the RAN overload indication is found to indicate that the RAN is not overloaded, the RAN overload indication is ignored. The backoff time of the RAN overload.
  • the backoff time includes a backoff time for the RAN overload, and the RAN overload indication is a RAN overload indication indicating the RAN overload.
  • the RRC connection reject message does not carry the backoff time for the CN overload.
  • step 505 when the UE finds that the RAN overload indication is a RAN overload indication indicating that the RAN is overloaded, according to the backoff time for the RAN overload, if the backoff time for the CN overload is not found, the UE does not need to perform the CN Handling of the backoff time of the overload.
  • the carried backoff time includes a backoff time for the RAN overload and for the CN overload, and the RAN overload indication is a RAN overload indication indicating the RAN overload.
  • the RAN overload indication is a RAN overload indication indicating the RAN overload.
  • the UE performs processing according to the backoff time for the RAN overload, and when there is a backoff time for the CN overload, the backoff time for the CN overload is handed over. Internal NAS layer processing. At this time, the UE obtains the backoff time for the RAN overload and the CN overload.
  • the RRC layer in the UE maintains the T302 timer corresponding to the backoff time of the RAN overload, and the NAS layer maintains the timer corresponding to the backoff time of the CN overload.
  • RRC The layer notifies the NAS layer that the T302 timer is turned on or times out. When the T302 timer is valid, the NAS layer disables all access requests that need to be initiated. When the T302 timer is invalid (not enabled or timed out), the NAS layer determines whether to prohibit the initiation of access according to the timer and the establishment cause corresponding to the backoff time of the CN overload.
  • the RAN needs to determine whether the MME corresponding to the UE is overloaded, and therefore the access control process is slightly different.
  • the RAN may determine the corresponding MME by using the S-TMSI (Sec-Temporary Mobile Subscriber Identify, SAE (System Architecture Evolution) - Temporary Mobile Subscriber Identity) in the RRC Connection Request message, or complete the RRC connection establishment.
  • S-TMSI Sec-Temporary Mobile Subscriber Identify, SAE (System Architecture Evolution) - Temporary Mobile Subscriber Identity
  • SAE System Architecture Evolution
  • GUMMEI Globally Unique MME Identity
  • the method for performing access control when a single CN node is overloaded and reporting S-TMSI is required in this embodiment is as follows:
  • Step 601 The UE sends an RRC connection request message to the RAN, where the RRC connection request message may carry the S-TMSI, the terminal or service information of the UE, and the establishment cause.
  • Step 602 The RAN performs, according to the terminal or service information of the UE, the establishment cause, and the determination of the access control of the RAN according to the obtained load information of the current network (including the RAN and the CN), and the MME that performs the S-TMSI indication.
  • the access control determines that if the MME is overloaded and the access of the RRC establishment cause of the UE is prohibited, the CN overload is determined. Otherwise, it is determined that the CN is not overloaded. When at least one of the RAN and the CN is not allowed to access, proceed to step 603. Otherwise, proceed to step 604.
  • Step 603 The RAN returns an RRC connection reject message carrying the backoff time corresponding to the network that is not allowed to access to the UE. Continue to step 605.
  • RRC connection reject message For the content and parsing process of the RRC connection reject message, refer to the embodiment shown in FIG. 5.
  • Step 604 The RAN returns an RRC Connection Setup message to the UE. Continue to step 606.
  • Step 605 The UE parses the RRC connection reject message, and does not allow to access the network again according to the backoff time corresponding to the network that is not allowed to access.
  • Step 606 The UE returns an RRC Connection Setup Complete message to the RAN.
  • the method for performing access control when a single CN node is overloaded and reported to GUMMEI in this embodiment is as follows:
  • Step 701 The UE sends an RRC connection request message to the RAN, where the RRC connection request message may carry the terminal or service information of the UE and the establishment cause.
  • Step 702 The RAN performs the judgment of the access control of the RAN according to the terminal or service information of the UE and the establishment cause, and according to the obtained load information of the RAN. When the RAN is overloaded, proceed to step 703, otherwise continue. Step 705.
  • Step 703 The RAN returns an RRC Connection Reject message carrying the backoff time for the RAN overload to the UE.
  • Step 705 The RAN returns an RRC Connection Setup message to the UE.
  • Step 706 The UE returns an RRC connection setup complete message carrying the GUMMEI to the RAN.
  • Step 707 The RAN performs the access control judgment of the CN according to the terminal or service information of the UE and the establishment cause, and according to the obtained load information of the CN.
  • the process proceeds to step 708, otherwise the process continues.
  • Step 708 The RAN returns an RRC connection release message carrying the backoff time for the CN overload to the UE. Continue with step 710.
  • Step 709 The RAN registers with the CN.
  • the RAN determines whether there is an S1 interface between the MME corresponding to the GUMMEI and the RAN, and whether the MME allows the UE to access.
  • the RAN first determines whether there is an S1 interface between the MME corresponding to the GUMMEI and the self. If there is an S1 interface, it is determined whether there is overload control information of the MME. If there is overload control information, it is determined whether the establishment request requested by the UE belongs to the overload control information. The reason for the establishment of the access denial is rejected, and if so, then step 708 is continued. If there is an S1 interface and there is no overload control information, that is, the MME is not overloaded, then step 709 is continued for the MME.
  • step 709 If there is no S1 interface, look for an un-overloaded MME from the MME Pool to continue to step 709, or find an MME that is overloaded but does not reject the establishment cause of the UE, if the MME in the MME Pool is overloaded and the establishment of the UE is rejected. If so, proceed to step 708.
  • Step 710 The UE parses the RRC connection release message, and does not allow to access the network again according to the backoff time for the CN overload.
  • the implementation process of the access control is understood by the above description.
  • the process is mainly implemented by the RAN and the UE.
  • the internal structure and functions of the RAN and the UE are introduced below.
  • the access network device in this embodiment includes: a control module 801 and an interface module 802.
  • the access network device may be specifically an access device such as a base station (e.g., evolved base station (e B)) or RNC (wireless network control).
  • a base station e.g., evolved base station (e B)
  • RNC wireless network control
  • the control module 801 is configured to generate various messages, and determine whether to allow access to the RAN and the CN according to the current RAN and CN load conditions and the terminal or service information reported by the UE in the random access procedure.
  • the control module 801 is further configured to determine, according to the current network load situation and the information reported by the terminal, the backoff time for the CN overload according to the current network load condition and the information reported by the terminal, or refer to the backoff time indicated by the MME or the OAM, and
  • the randomization process is used to determine the backoff time for the CN overload for the UE.
  • the self-behavior UE determines the backoff time for the RAN overload.
  • the access request carries the terminal or service information of the UE and the establishment cause.
  • the control module 801 determines whether the RAN is overloaded, and if yes, determines that the RAN is overloaded, otherwise determines that the RAN is not overloaded; and determines whether the UE is allowed to access the CN according to the terminal or service information of the UE and the establishment cause and the overload indication of the CN, and if yes, determines CN is not overloaded, otherwise it is determined that CN is overloaded.
  • the terminal or service information includes one of the following information: indicates whether it is a low priority access terminal or service; indicates whether it is a roaming terminal and specific roaming subclass information; indicates whether it is a time tolerant terminal or service; indicates whether it is time Controllable terminal or service; indicates whether it is a small data terminal or service.
  • the terminal or service information may also include other information related to the terminal or service.
  • the interface module 802 is connected to the UE and the CN, and is configured to send, to the UE, an indication message with a backoff time corresponding to the network that is not allowed to access when the access to the RAN and the CN is not allowed.
  • the RAN transmits an indication message with a backoff time corresponding to the network that is not allowed to access through the RRC Connection Reject message.
  • the method further includes the steps of: receiving the RRC connection complete message sent by the UE, if the RRC connection setup complete message carries the UE registration The MME corresponding to the MME, and the MME corresponding to the user identifier is overloaded and has an SI interface with the RAN, or all MMEs in the MME pool are overloaded, and the RAN sends a backoff time corresponding to the network that is not allowed to access through the RRC connection release message. If the access request carries the user identifier corresponding to the MME registered by the UE, the RAN sends an indication message with a backoff time corresponding to the network that is not allowed
  • the indication message has various forms, and different information elements (IEs) can be used to indicate which network the UE is overloaded, and to indicate the corresponding backoff time.
  • the RRC connection reject message further includes an RAN overload indication indicating whether the RAN is overloaded; when the CN is overloaded and the RAN is not overloaded, the backoff time corresponding to the network that is not allowed to access includes the backoff time for the CN overload, and the RAN overload indication is The RAN is not overloaded with the RAN overload indication; when the RAN is overloaded and the CN is not overloaded, the backoff time includes a backoff time for the RAN overload, the RAN overload indication is a RAN overload indication indicating the RAN overload; and when both the RAN and the CN are overloaded, the backoff time includes The RAN and the backoff time for CN overload, the RAN overload indication is a RAN overload indication indicating RAN overload.
  • IEs information elements
  • the RRC connection reject message further includes a backoff time for the RAN overload when the RAN is not overloaded, and the backoff time for the RAN overload is a specified value. That is, if the CN is not overloaded (that is, it is allowed to access the CN), and the RAN is overloaded (that is, the RAN is not allowed to access), the RRC connection reject message does not carry the backoff time for the CN overload, and only carries the backoff for the RAN overload. time. If the CN is overloaded and the RAN is not overloaded, the RRC connection reject message carries the backoff time for the CN overload and the backoff time for the RAN overload, but the backoff time for the RAN overload is Specify a value. If both the CN and the RAN are overloaded, the RRC connection reject message carries the backoff time for the CN overload and the backoff time for the RAN overload, and the backoff time for the RAN overload is not the specified value.
  • the user equipment in this embodiment includes: an interface module 901, a parsing module 902, and a control module 903.
  • the interface module 901 receives an indication message with a backoff time corresponding to the network that is not allowed to access.
  • the backoff time corresponding to the network that is not allowed to access includes the backoff time for RAN overload, the backoff time for CN overload, or the backoff time for RAN overload and the backoff time for CN overload.
  • the interface module 901 receives an indication message with a backoff time corresponding to the network that is not allowed to access through the RRC connection reject message; the interface module 901 is further configured to send an RRC connection complete message; and the RRC connection setup complete message may be carried with the UE.
  • the user identifier of the MME the interface module 901 may receive an indication message with a backoff time corresponding to the network that is not allowed to access through the RRC connection release message; if the access request carries the user identifier corresponding to the MME registered by the UE, The interface module 901 receives an indication message with a backoff time corresponding to the network that is not allowed to access through the RRC Connection Reject message.
  • the parsing module 902 is configured to parse the indication message to obtain a backoff time corresponding to the network that is not allowed to access.
  • the control module 903 is configured to not allow access to the network again according to the backoff time corresponding to the network that is not allowed to access. Specifically, the control module 903 can start and set the T302 timer according to the backoff time for the RAN overload, and the NAS layer portion of the control module 903 can perform the corresponding backoff processing according to the backoff time for the CN overload.
  • the control module 903 finds that the RRC connection reject message only has a backoff time for the RAN overload, and determines that the CN is not overloaded, and the RAN is overloaded, and only needs to process the backoff time for the RAN overload, such as starting and setting the T302 timer.
  • the UE is not allowed to make an access network attempt during the start of the T302 timer.
  • the control module 903 finds that the RRC connection reject message carries the backoff time for the CN overload, the backoff time for the CN overload is handled by the internal NAS layer, and the UE is not allowed during the timer start corresponding to the backoff time for the CN overload. Try to access the network.
  • the control module 903 finds that the RRC connection reject message carries the backoff time for the RAN overload and the backoff time is the specified value, the backoff time for the RAN overload is ignored, or the backoff time for the RAN overload is processed.
  • the control module 903 finds that the RRC connection reject message carries the backoff time for the CN overload and the backoff time for the RAN overload, and when the backoff time for the RAN overload is not the specified value, the RRC layer in the control module 903 maintains the T302 timer, the NAS layer. Maintain a timer corresponding to the backoff time of the CN overload.
  • the RRC layer notifies the NAS layer that the T302 timer is turned on or times out.
  • the NAS layer disables all access requests that need to be initiated.
  • the NAS layer #> determines whether to prohibit the initiation of access according to the timer corresponding to the backoff time of the CN overload and the establishment cause.
  • the interface module 901 can receive the finger that can receive the backoff time for the CN overload by using the RRC connection release message. Show message.
  • the control module 903 finds that the RRC connection release message carries the backoff time for the CN overload, it will target
  • the backoff time of the CN overload is handled by the internal NAS layer, and the UE is not allowed to make an access network attempt during the start of the timer corresponding to the CN overload backoff time.
  • the RRC Connection Reject message also includes a RAN Overload indication indicating whether the RAN is overloaded.
  • a RAN Overload indication indicating whether the RAN is overloaded.
  • the control module 903 finds that the RAN overload indication is a RAN overload indication indicating that the RAN is overloaded, according to the backoff time for the RAN overload, and does not find the backoff time for the CN overload, it does not need to perform the backoff time for the CN overload. Processing.
  • the control module 903 finds that the RAN overload indication is a RAN overload indication indicating that the RAN is overloaded, it performs processing according to the backoff time for the RAN overload, and does not allow the UE to perform an access network attempt during the start of the T302 timer, and finds that there is a backoff for the CN overload.
  • the backoff time for the CN overload is handled by the internal NAS layer.
  • the control module 903 obtains the backoff time for the RAN and the CN overload, the RRC layer in the control module 903 maintains the T302 timer, and the NAS layer maintains the timer corresponding to the backoff time of the CN overload.
  • the RRC layer notifies the NAS layer that the T302 timer is turned on or times out.
  • the NAS layer disables all access requests that need to be initiated.
  • the NAS layer #> determines whether to prohibit the initiation of access according to the timer and the establishment cause corresponding to the CN overload backoff time.
  • the user equipment when the CN is overloaded, the user equipment further includes: a recording module 904, see FIG.
  • the recording module 904 is configured to: when the discovery indication message carries the backoff time for the CN overload, record the establishment reason corresponding to the RRC connection corresponding to the indication message.
  • the control module 903 needs to perform access again during the start of the timer corresponding to the backoff time of the CN overload, if the access priority of the current access request is not higher than the access priority of the recorded establishment cause If the access priority of the current access request is higher than the priority of the established establishment cause, the timer corresponding to the backoff time of the CN overload is invalid, and the access request is allowed to be sent.
  • the core network device in this embodiment includes: a control module 1101 and an interface module 1102.
  • the core network device can be specifically MME or OAM.
  • the control module 1101 is for determining whether an overload has occurred, and if so, determining a backoff time for the overload.
  • the control module 1101 can reject certain establishment cause accesses according to its own overload condition, and determine an appropriate backoff time based on these establishment reasons for rejection.
  • the interface module 1102 is configured to send an overload control message carrying the backoff time for the overload to the RAN.
  • the MME may determine the backoff time according to the overload condition of itself and other core network nodes, and send the backoff time to the RAN.
  • the OAM can obtain the load condition of each MME, and accordingly determines the backoff time for the overload, and then transmits it to the RAN.
  • the RAN may obtain multiple backoff times for multiple MMEs for overload.
  • the RAN may determine a backoff time for the CN according to the obtained multiple backoff times for the overload, such as selecting a maximum value, or an average value.
  • the RAN determines a backoff time for the CN according to the backoff time for the overload of the MME registered by the UE.
  • the radio access network performs the judgment on the access control of the RAN and the CN (core network) in the access process, and if there is a network that is not allowed to access, that is, the network is overloaded,
  • the indication message of the UE carries a backoff time corresponding to the network that is not allowed to access. That is to say, the RAN can set the backoff time in a targeted manner for the overload condition of the RAN and the CN, and better perform access control, thereby avoiding network congestion and excessive terminal access delay as much as possible.
  • the embodiments of the present invention provide various structures of the indication message, and the multiple structures can be used to notify the UE which network is overloaded and the corresponding backoff time, which is beneficial to flexible configuration. Moreover, for various access control judgment methods, corresponding implementation schemes are provided, which are applicable to various network requirements.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention is in the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) in which computer usable program code is embodied.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种接入控制的方法及装置 本申请要求在 2011年 01月 10日提交中国专利局、 申请号为 201110003807.7、 发明名称为
"一种接入控制的方法及装置 "的中国专利申请的优先权， 其全部内容通过引用结合在本申请 中。 技术领域 本发明涉及通信领域， 特别是涉及一种接入控制的方法及装置。 背景技术
M2M是 Machine to Machine 的筒称， 专指机器与机器间通信的业务类型。 物联网 ( Internet of Things, IOT )则是指 Μ2Μ在广域网、 特别是移动运营商网络中的应用， 即 以移动网络运营商的无线网络为平台， 釆用多种传输方式（CDMA ( Code Division Multiple Access, 码分多址接入 ) /GSM ( Global System for Mobile communication全球移动通信系 统） /SMS ( Short Message Service, 短信息服务）等）， 通过特种行业终端， 服务于行业用 户机器到机器的无线数据传输业务。
M2M/IOT业务具有潜在的市场， 地理分布广泛， 可以部署在任何网络可达的位置， 取 代高成本的有人值守， 实现真正意义上的无人值守， 对于电力、 水利、 釆油、 釆矿、 环保、 气象、 烟草、 金融等行业的信息釆集意义巨大， 有巨大的市场价值。
对于广泛分布的 M2M终端， 釆用无线网络进行通信是优选方案之一， 现有的一些行 业应用， 如远程抄表、 7j位监控等， 都是釆用 GPRS ( General Packet Radio Service, 通用 分组无线业务） 网络传输传感器釆集的数据信息。 随着 M2M应用的发展， 对无线网络存 在着迫切的需求。
当大量 M2M终端比较集中地接入网络时， 对无线、 核心网都将构成比较大的负荷， 拥塞难免会发生， 也会增加人与人之间通信的故障率。 然而， 现有技术中 RRC ( Radio Resource Control,无线资源控制）连接拒绝消息中只携带一个退避时间， 不区分是针对 CN ( Core Network, 核心网络）过载还是 RAN ( Radio Access Network, 无线接入网络）过载 的。 一方面， 该退避时间过短， 以 LTE ( Long Term Evolution, 长期演进） 系统为例， 为 16秒， 会造成 UE过度频繁的接入网络， 不利于緩解网络拥塞； 另外一方面， 对 CN拥塞 和 RAN册拥塞没有区别对待， 接入控制粒度过粗。
发明内容 本发明实施例提供一种接入控制的方法及装置， 用于实现较好的接入控制。
一种接入控制的方法， 应用于 RAN侧， 包括以下步骤：
在随机接入过程中， 无线接入网络 RAN根据当前 RAN和 CN的负荷情况以及 UE上 报的终端或业务信息， 判断是否允许所述 UE接入 RAN和 CN;
当不允许接入 RAN和 CN中至少有一个网络时， RAN向 UE发送带有与不允许接入 的网络对应的退避时间的指示消息。
一种接入过程中的消息处理的方法， 应用于 UE侧， 包括以下步骤：
UE发送接入请求后， 接收带有与不允许接入的网络对应的退避时间的指示消息； UE对指示消息进行解析 , 获得与不允许接入的网络对应的退避时间；
UE根据与不允许接入的网络对应的退避时间不允许再次接入网络。
一种接入网设备， 包括：
控制模块， 用于在随机接入过程中，根据当前 RAN和 CN的负荷情况以及 UE上报的 终端或业务信息， 判断是否允许所述 UE接入 RAN和 CN;
接口模块， 用于当不允许接入 RAN和 CN中至少有一个网络时， 向 UE发送带有与不 允许接入的网络对应的退避时间的指示消息。
一种用户设备， 包括：
接口模块， 用于发送接入请求后， 接收带有与不允许接入的网络对应的退避时间的指 示消息；
解析模块， 用于对指示消息进行解析， 获得与不允许接入的网络对应的退避时间； 控制模块， 用于根据与不允许接入的网络对应的退避时间不允许再次接入网络。
一种核心网设备， 包括：
控制模块， 用于确定自身是否发生过载， 若是， 则确定针对过载的退避时间； 接口模块， 用于向 RAN发送携带有针对过载的退避时间的过载控制消息。
本发明实施例中无线接入网 （ RAN )在接入过程中进行关于 RAN和 CN (核心网）的 接入控制的判断， 若有不允许接入的网络， 即该网络过载， 则在给 UE的指示消息中携带 与不允许接入的网络对应的退避时间。也就是说， RAN可以针对 RAN和 CN的过载情况， 分别有针对性的设置退避时间， 更好的进行接入控制， 从而尽可能避免网络拥塞以及终端 接入时延过大。 附图说明
图 1为本发明实施例中接入控制在网络侧的主要方法流程图；
图 2为本发明实施例中接入控制在 UE侧的主要方法流程图；
图 3为本发明实施例中接入控制在 RAN和 UE两侧的方法流程图； 图 4为本发明实施例中不需要区分单 CN 节点过载且仅通过退避时间进行接入控制的 方法流程图；
图 5为本发明实施例中不需要区分单 CN 节点过载且通过退避时间和 RAN过载指示 进行接入控制的方法流程图；
图 6为本发明实施例中需要区分单 CN 节点过载且上报 S-TMSI时进行接入控制的方 法流程图；
图 7为本发明实施例中需要区分单 CN 节点过载且上报 GUMMEI时进行接入控制的 方法流程图；
图 8为本发明实施例中接入网设备的结构图；
图 9为本发明实施例中 UE的主要结构图；
图 10为本发明实施例中 UE的详细结构图；
图 11为本发明实施例中核心网设备的结构图。 具体实施方式
本发明实施例中无线接入网 （ RAN )在接入过程中进行关于 RAN和 CN (核心网）的 接入控制的判断， 若有不允许接入的网络， 即该网络过载， 则在给 UE的指示消息中携带 与不允许接入的网络对应的退避时间。也就是说， RAN可以针对 RAN和 CN的过载情况， 分别有针对性的设置退避时间， 更好的进行接入控制， 从而尽可能避免网络拥塞以及终端 接入时延过大。
现有技术中的 RRC连接拒绝消息中的退避时间 （ wait time )未区分是针对 CN过载的 退避时间还是针对 RAN过载的退避时间。 本实施例中将现有技术中 RRC连接拒绝消息中 的退避时间作为针对 RAN过载的退避时间， 并通过增加新的信息元（ IE )来表示针对 CN 过载的退避时间。 以便对不同网络分别进行接入控制， 细化了接入控制的粒度。 同时， 为 了增大退避时间的范围， 退避时间可以釆用非退避时间字面值理解， 比如按照其中每个整 数值代表 2的幂的大小的理解来设定等。 参见图 1 , 本实施例中接入控制在网络侧的主要方法流程如下：
步骤 101： 在随机接入过程中， 无线接入网络 RAN根据当前 RAN和 CN的负荷情况 以及 UE上报的终端或业务信息， 判断是否允许接入 RAN和 CN。 该判断过程可以发生在 收到 RRC连接请求（ RRC Connection Request )消息后， 或者发生在收到 RRC连接建立完 成消息后。 UE可以通过 RRC连接请求消息上报终端或业务信息， 或者通过 RRC连接建 立完成消息上报终端或业务信息。
步骤 102: 当不允许 RAN和 CN中至少有一个网络时， RAN向 UE发送带有与不允许 接入的网络对应的退避时间的指示消息。 如果 CN过载， 即不允许接入 CN, 则携带的退 避时间包括针对 CN过载的退避时间； 如果 RAN过载， 即不允许接入 RAN, 则携带的退 避时间包括针对 RAN过载的退避时间； 如果 RAN和 CN均过载， 则携带的退避时间包括 针对 RAN过载的退避时间和针对 CN过载的退避时间。 如果是在接入请求时进行接入控 制的判断，且 RAN和 CN均未过载（即 RAN和 CN均允许接入 ),则 RAN向 UE发送 RRC 连接建立 （ RRC Connection Setup ) 消息； 如果是在 RRC连接建立完成后进行接入控制的 判断， 且 RAN和 CN均未过载， 则 RAN维持现状， 不需要向 UE发送 RRC连接释放 ( RRCConnectionRelease ) 消息。
与网络侧相对的， 需要介绍接入过程中 UE侧的实现方法。
参见图 2, 本实施例中接入控制在 UE侧的主要方法流程如下：
步骤 201 : UE发送接入请求后，接收带有与不允许接入的网络对应的退避时间的指示 消息。该退避时间包括针对 RAN过载的退避时间、针对 CN过载的退避时间、或针对 RAN 过载的退避时间和针对 CN过载的退避时间。
步骤 202: UE对指示消息进行解析， 获得与不允许接入的网络对应的退避时间。 步骤 203: UE根据与不允许接入的网络对应的退避时间不允许再次接入网络。 UE发 现指示消息有针对 RAN过载的退避时间时，根据针对 RAN过载的退避时间进行接入控制。 UE发现指示消息有针对 CN过载的退避时间时，根据针对 CN过载的退避时间进行接入控 制。 UE发现指示消息有针对 RAN和 CN过载的退避时间时， 根据针对 RAN和 CN过载 的退避时间进行接入控制。
接入过程涉及到 RAN与 UE的交互， 下面结合 RAN和 UE两侧来介绍接入控制的实 现过程。
参见图 3 , 本实施例中接入控制在 RAN和 UE两侧的方法流程如下：
步骤 301： UE向 RAN发送 RRC连接请求消息， RRC连接请求消息可携带有 UE的 终端或业务信息和建立原因。 终端或业务信息包括下列信息中的一项： 指示是否为低优先 级接入终端或业务； 指示是否是漫游终端以及具体的漫游子类信息； 指示是否为时间容忍 终端或业务； 指示是否是时间可控终端或业务； 指示是否为小数据量终端或业务。 终端或 业务信息还可以包括其它与终端或业务有关的信息， 此处不——列举。 建立原因包括下列 原因中的一项： UE发起的紧急呼叫 （ emergency )、 UE被叫接入（ mt- Access )、 高优先级 接入（ highPriority Access )、 UE发起的信令（ mo-Signalling )、 数据传输（ mo-Data )和低优 先级接入（ lowPriority Access )。 其中， 不同的建立原因可以对应不同的接入优先级。
步骤 302: RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的当前网络 的负荷信息， 判断是否允许 UE接入 RAN和 CN, 当不允许接入 RAN和 CN中至少一个 网络时，继续步骤 303 ,否则继续步骤 304。 RAN中已获得的当前网络的负荷信息包括 RAN 负荷信息和 CN负荷信息， 即 RAN和 CN的负荷情况， CN负荷信息可以由移动性管理实 体（ Mobility Management Entity, MME )通过过载控制 ( OVERLOAD START ) 消息发送 给 RAN或由 OAM ( Operations, Administration and Maintenance, 运行、 管理和维护） 配置 给 RAN。 CN负荷信息如： 针对非紧急呼叫， 拒绝所有低优先级接入设备或业务； 拒绝所 有主叫数据业务以及低优先级接入设备或业务； 针对非紧急呼叫， 拒绝所有主叫信令业务 以及低优先级接入设备或业务； 只允许紧急业务和被叫接入。 本实施例中 CN负荷信息还 包括针对 CN过载的退避时间， 该退避时间可以与拒绝原因相对应。
步骤 303: RAN向 UE返回携带有与不允许接入的网络对应的退避时间的 RRC连接拒 绝（ RRCConnectionReject ) 消息。 继续步骤 305。
在步骤 303之前， RAN在确定有网络过载时， 需要针对与不允许接入的网络对应确定 退避时间。 MME通过过载初始消息向 RAN发送退避时间的参考值， 或 OAM配置退避时 间的参考值给 RAN。 RAN根据该参考值确定最终的退避时间。 此处有多种实现方式， 例 如， RAN直接将参考值作为退避时间； 或者， RAN产生一个随机数， 将以参考值为底的 随机数的幂作为退避时间； 或者， 参考值为一个范围， 如 1-3600, RAN产生一个中参考范 围内的随机数， 将该随机数作为退避时间； 或者， RAN产生一个不小于参考值的随机数， 将该随机数作为退避时间。 还可以有其它方式确定退避时间， 能达到緩解网络侧负荷压力 的目的即可， 均适用于本实施例。 确定 RAN和针对 CN过载的退避时间均可釆用上述方 式。 较佳的， 本实施例中退避时间以秒为单位。
步骤 304: RAN向 UE返回 RRC连接建立消息。 继续步骤 306。
步骤 305: UE根据与不允许接入的网络对应的退避时间进行接入网络控制， 如不允许 再次接入网络。
步骤 306: UE向 RAN返回 RRC连接建立完成（ RRC ConnectionSetup Complete ) 消 息。
在步骤 305中， 如果 UE收到的 RRC连接拒绝消息中携带有 CN的有效退避时间， 则 UE需将针对 CN过载的退避时间交由内部的 NAS ( Non- Access Stratum, 非接入层）层处 理。 如果 UE收到的 RRC连接拒绝消息中携带有针对 RAN过载的退避时间， 则根据针对 RAN过载的退避时间启动及设置 T302定时器。 UE通过 NAS层和 T302定时器来控制暂 停接入。 T302定时器是标准中规定的定时器， 现有标准中， 连接拒绝消息中只有一个 Wait Time, UE 收到 RRC Connection Reject消息时， 需要按照 Wait Time启动定时器 T302, 超 时前不能再次发起接入尝试。 本发明中在这个消息中新增加了一个退避时间。 而原来的 Wait Time还是对应于定时器 T 302。
本实施例还可以有另外一种实现方式， RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的当前网络的负荷信息， 进行关于 RAN的接入控制的判断， 若不允许接 入， 则向 UE发送携带有针对 RAN过载的退避时间的 RRC连接拒绝消息， 然后 UE进行 退避处理； 若允许接入， 则向 UE发送 RRC连接建立消息， 与 UE完成 RRC连接建立， 在完成建立后， 进行关于 CN的接入控制的判断， 若不允许接入 CN, 则向 UE发送 RRC 连接释放消息， 与 UE断开 RRC连接， 否则完成向 CN的注册过程。
由于 RAN可以在不同阶段进行接入控制的判断， 并且关于 RAN和 CN的是否允许接 入有多种指示方式， 以及在接入控制的判断时可以需要区分单 CN节点过载或者不需要区 分单 CN节点过载，使得整个接入过程有多种实现方式， 下面通过几个实施例来详细说明。 其中， 不需要区分单 CN节点过载是指： CN过载不需要区分是整个 MME Pool内 MME均 发生过载还是只有部分 MME发生过载， 即 RAN收到 n个 MME的负荷信息时，确定整个 CN过载， 预先配置的参数 n所表示的数量低于与 RAN连接的 MME池内 MME的总数。 需要区分单 CN节点过载是指： RAN收到 MME的负荷信息， 则确定该 MME过载， 未收 到 MME池（ Pool ) 内的其它 MME的负荷信息， 则确定其它 MME未过载。
参见图 4 , 本实施例中不需要区分单 CN节点过载且仅通过退避时间进行接入控制的 方法 ¾ ^程 ¾口下：
步骤 401 : UE向 RAN发送 RRC连接请求消息， RRC连接请求消息可携带有 UE的 终端或业务信息和建立原因。
步骤 402: RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的当前网络 的负荷信息， 判断是否允许接入 RAN和 CN, 当不允许接入 RAN和 CN中至少一个网络 时， 继续步骤 403 , 否则继续步骤 404。 其中， 只要 RAN中已获得的当前网络的负荷信息 包括任一 MME的过载控制信息， 则确定整个 CN过载， 如果 UE的建立原因满足该 MME 的过载控制信息中拒绝接入的接入原因， 则拒绝 UE的接入请求。 本实施例中 MME的负 荷信息包括 MME的过载控制信息。
步骤 403: RAN向 UE返回携带有针对 RAN过载的退避时间、或携带有分别针对 RAN 过载和针对 CN过载的退避时间的 RRC连接拒绝消息。 继续步骤 405。
步骤 404: RAN向 UE返回 RRC连接建立消息。 继续步骤 406。 步骤 405 : UE解析 RRC连接拒绝消息， 并根据针对 RAN和针对 CN过载的退避时间 不允许再次接入网络。
步骤 406: UE向 RAN返回 RRC连接建立完成消息。
在步骤 403中，若 CN未过载（即允许接入 CN ), 而 RAN过载（即不允许接入 RAN ), 则 RRC连接拒绝消息中不携带针对 CN过载的退避时间， 只携带针对 RAN过载的退避时 间。 则在步骤 405 中， UE发现仅有针对 RAN过载的退避时间时， 确定 CN未过载， 而 RAN过载， 只需对针对 RAN过载的退避时间进行处理， 如启动和设置 T302定时器等。
若 CN过载， 则 RRC连接拒绝消息中携带针对 CN过载的退避时间。 在步骤 405中， UE发现携带有针对 CN过载的退避时间时， 将针对 CN过载的退避时间交由内部的 NAS 层处理。
CN和 RAN都过载的情况下， 则可以将针对 RAN过载的退避时间设置为指定值， UE发现针对 RAN过载的退避时间为指定值时， 忽略针对 RAN过载的退避时间， 或者对 针对 RAN过载的退避时间进行退避， 该指定值可以设置为系统规定的最小退避时间值， 不同系统可能规定的最小退避时间值不同。
CN过载的情况下， RAN也过载， 则针对 RAN过载的退避时间不为指定值， UE对针 对 RAN过载的退避时间进行处理。 CN和 RAN均过载时， UE获得针对 RAN和 CN过载 的退避时间， UE中 RRC层维护 T302定时器， NAS层维护针对 CN过载的退避时间对应 的定时器。 RRC层通知 NAS层 T302定时器开启或超时。 当 T302定时器有效时， NAS层 禁止所有需发起的接入请求。 当 T302定时器无效（未开启或超时） 时， NAS层根据针对 CN过载的退避时间对应的定时器和建立原因来决定是否禁止发起接入。 具体地， 允许 UE 在 NAS层接入， UE最终能否允许接入还需要根据 AS 层规则来决定。
为了緩解网络侧接入负荷， 还可以在 UE 侧做是否允许发起接入的判断。 例如， UE 收到指示消息且通过指示消息获知 CN过载时，记录与该指示消息对应 RRC连接所对应的 建立原因。 在退避时间范围内， 需要再次进行接入时， 若本次接入请求的建立原因的接入 优先级不高于已记录的建立原因的接入优先级， 禁止接入， 若本次接入请求的建立原因的 接入优先级高于已记录的建立原因的优先级， 所有退避时间对应的定时器失效， 发送接入 请求。
参见图 5 ,本实施例中不需要区分单 CN节点过载且通过退避时间和 RAN过载指示进 行接入控制的方法流程如下：
步骤 501： UE向 RAN发送 RRC连接请求消息， RRC连接请求消息可携带有 UE的 终端或业务信息和建立原因。 步骤 502: RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的当前网络 的负荷信息， 判断是否允许接入 RAN和 CN, 当不允许接入 RAN和 CN中至少一个网络 时， 继续步骤 503 , 否则继续步骤 504。 其中， 只要 RAN中已获得的当前网络的负荷信息 包括任一 MME的过载控制信息， 则确定整个 CN过载， UE的建立原因满足该 MME的过 载控制信息所拒绝的接入原因， 则拒绝 UE的接入请求。
步骤 503: RAN向 UE返回携带有针对 RAN过载的退避时间、 RAN过载指示及 CN 过载时针对 CN过载的退避时间的 RRC连接拒绝消息。 继续步骤 505。 其中， RAN过载 指示既可以表示 RAN是否过载，还可以表示针对 RAN过载的退避时间是否有效， 当 RAN 过载指示为表示 RAN过载的 RAN过载指示时， 同时表示携带的针对 RAN过载的退避时 间有效； 当 RAN过载指示为表示 RAN未过载的 RAN过载指示时， 同时表示携带的针对 RAN过载的退避时间无效。
步骤 504: RAN向 UE返回 RRC连接建立消息。 继续步骤 506。
步骤 505: UE解析 RRC连接拒绝消息， 并根据 RAN过载指示、 针对 RAN过载和针 对 CN过载的退避时间不允许再次接入网络。
步骤 506: UE向 RAN返回 RRC连接建立完成消息。
在步骤 503中， 当 CN过载且 RAN未过载时，携带的退避时间包括针对 CN过载的退 避时间， RAN过载指示为表示 RAN未过载的 RAN过载指示。 此时 RRC连接拒绝消息也 可以携带针对 RAN过载的退避时间，但针对 RAN过载的退避时间无效。则在步骤 505中， UE发现携带有针对 CN过载的退避时间时， 将针对 CN过载的退避时间交由内部的 NAS 层处理，发现 RAN过载指示为表示 RAN未过载的 RAN过载指示时， 忽略针对 RAN过载 的退避时间。当 RAN过载且 CN未过载时，退避时间包括针对 RAN过载的退避时间， RAN 过载指示为表示 RAN过载的 RAN过载指示。 此时 RRC连接拒绝消息不携带针对 CN过 载的退避时间。则在步骤 505中， UE发现 RAN过载指示为表示 RAN过载的 RAN过载指 示时， 按照针对 RAN过载的退避时间进行处理， 未发现有针对 CN过载的退避时间时， 也就不需要进行关于针对 CN过载的退避时间的处理。
当 RAN和 CN均过载时， 携带的退避时间包括针对 RAN过载和针对 CN过载的退避 时间， RAN过载指示为表示 RAN过载的 RAN过载指示。 则在步骤 505中， UE发现 RAN 过载指示为表示 RAN过载的 RAN过载指示时，按照针对 RAN过载的退避时间进行处理， 发现有针对 CN过载的退避时间时， 将针对 CN过载的退避时间交由内部的 NAS层处理。 此时 UE获得针对 RAN过载和 CN过载的退避时间， UE中 RRC层维护针对 RAN过载的 退避时间对应的 T302定时器， NAS层维护针对 CN过载的退避时间对应的定时器。 RRC 层通知 NAS层 T302定时器开启或超时。 当 T302定时器有效时， NAS层禁止所有需发起 的接入请求。 当 T302定时器无效（未开启或超时） 时， NAS层根据针对 CN过载的退避 时间对应的定时器和建立原因来决定是否禁止发起接入。
当需要区分单 CN节点过载时， RAN需要确定 UE对应的 MME是否过载， 因此接入 控制过程会略有不同。 并且， RAN 可以通过 RRC 连接请求消息中的 S-TMSI ( SAE-Temporary Mobile Subscriber Identify, SAE ( System Architecture Evolution, 系统架 构演进） -临时移动签约用户标识）确定对应的 MME, 或者通过 RRC连接建立完成消息中 的 GUMMEI (全球唯一 MME标识）确定对应的 MME, 下面通过两个实施例针对这两种 情况来分别介绍。
参见图 6,本实施例中需要区分单 CN节点过载且上报 S-TMSI时进行接入控制的方法 流程如下：
步骤 601： UE向 RAN发送 RRC连接请求消息， RRC连接请求消息可携带有 S-TMSI、 UE的终端或业务信息和建立原因。
步骤 602: RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的当前网络 (包括 RAN和 CN ) 的负荷信息， 进行 RAN的接入控制的判断， 以及进行关于 S-TMSI 指示的 MME的接入控制的判断， 若该 MME过载且禁止该 UE的 RRC建立原因的接入， 则确定 CN过载， 否则确定 CN未过载， 当 RAN和 CN中至少一个不允许接入时， 继续步 骤 603 , 否则继续步骤 604。
步骤 603: RAN向 UE返回携带有与不允许接入的网络对应的退避时间的 RRC连接拒 绝消息。 继续步骤 605。 其中， RRC连接拒绝消息的内容和解析过程可参见图 5所示的实 施例。
步骤 604: RAN向 UE返回 RRC连接建立消息。 继续步骤 606。
步骤 605: UE解析 RRC连接拒绝消息， 并根据与不允许接入的网络对应的退避时间 不允许再次接入网络。
步骤 606: UE向 RAN返回 RRC连接建立完成消息。
参见图 7,本实施例中需要区分单 CN节点过载且上报 GUMMEI时进行接入控制的方 法流程如下：
步骤 701 : UE向 RAN发送 RRC连接请求消息， RRC连接请求消息可携带有 UE的 终端或业务信息和建立原因。
步骤 702: RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的 RAN的 负荷信息， 进行 RAN的接入控制的判断， 当 RAN发生过载时， 继续步骤 703 , 否则继续 步骤 705。
步骤 703: RAN向 UE返回携带有针对 RAN过载的退避时间的 RRC连接拒绝消息。 步骤 704: UE解析 RRC连接拒绝消息，并根据针对 RAN过载的退避时间不允许再次 接入网络。
步骤 705： RAN向 UE返回 RRC连接建立消息。
步骤 706: UE向 RAN返回携带有 GUMMEI的 RRC连接建立完成消息。
步骤 707: RAN根据 UE的终端或业务信息和建立原因， 以及根据已获得的 CN的负 荷信息， 进行 CN的接入控制的判断， 当 CN发生过载时， 继续步骤 708, 否则继续步骤
709。
步骤 708: RAN向 UE返回携带有针对 CN过载的退避时间的 RRC连接释放消息。 继 续步骤 710。
步骤 709: RAN向 CN进行注册。
在步骤 707中， RAN判断 GUMMEI对应的 MME与该 RAN之间是否有 S 1接口以及 该 MME是否允许该 UE接入。
RAN首先判断 GUMMEI对应的 MME与自身之间是否有 S1接口， 若有 S1接口， 再 判断是否有该 MME的过载控制信息， 若有过载控制信息， 再判断 UE请求的建立原因是 否属于过载控制信息中拒绝接入的建立原因， 若是， 则继续步骤 708。 若有 S1接口且没有 过载控制信息，也就是说该 MME未过载， 则针对该 MME继续步骤 709。若没有 S1接口， 则从 MME Pool中查找一个未过载的 MME继续步骤 709, 或者找出虽然过载但未拒绝该 UE的建立原因的 MME, 若 MME Pool中的 MME均过载且拒绝该 UE的建立原因， 则继 续步骤 708。
步骤 710: UE解析 RRC连接释放消息， 并根据针对 CN过载的退避时间不允许再次 接入网络。
通过以上描述了解了接入控制的实现过程， 该过程主要由 RAN和 UE实现， 下面对 RAN和 UE的内部结构和功能进行介绍。
参见图 8, 本实施例中接入网设备包括： 控制模块 801和接口模块 802。 接入网设备 可以具体为基站（如演进基站（ e B ) )或 RNC (无线网络控制）等接入设备。
控制模块 801用于生成各种消息， 以及在随机接入过程中， 根据当前 RAN和 CN的 负荷情况以及 UE上报的终端或业务信息， 判断是否允许接入 RAN和 CN。 控制模块 801 还用于需要确定针对 CN过载的退避时间时， 根据当前网络负荷情况以及终端上报的信息 自行为 UE确定针对 CN过载的退避时间，或者参考 MME或者 OAM指示的退避时间并做 随机化处理来为 UE确定针对 CN过载的退避时间， 需确定针对 RAN过载的退避时间时， 自行为 UE确定针对 RAN过载的退避时间。 具体的，接入请求携带有 UE的终端或业务信 息和建立原因。控制模块 801判断 RAN是否过载，若是则确定 RAN过载， 否则确定 RAN 未过载； 以及根据 UE的终端或业务信息和建立原因及关于 CN的过载指示， 判断是否允 许 UE接入 CN, 若是， 则确定 CN未过载， 否则确定 CN过载。
终端或业务信息包括下列信息中的一项： 指示是否为低优先级接入终端或业务； 指示 是否是漫游终端以及具体的漫游子类信息； 指示是否为时间容忍终端或业务； 指示是否是 时间可控终端或业务； 指示是否为小数据量终端或业务。 终端或业务信息还可以包括其它 与终端或业务有关的信息。
接口模块 802 ,与 UE及 CN连接，用于当不允许接入 RAN和 CN中至少一个网络时， 向 UE发送带有与不允许接入的网络对应的退避时间的指示消息。
当不需要区分单 CN节点过载时， RAN通过 RRC连接拒绝消息发送带有与不允许接 入的网络对应的退避时间的指示消息。 当需要区分单 CN节点过载时， 若接入请求未携带 与 UE注册的 MME对应的用户标识，则还包括步骤：接收 UE发送的 RRC连接完成消息， 若 RRC连接建立完成消息中携带与 UE注册的 MME对应的用户标识，且该用户标识对应 的 MME过载且与 RAN有 S I接口， 或者 MME池内所有 MME过载， 则 RAN通过 RRC 连接释放消息发送带有与不允许接入的网络对应的退避时间的指示消息； 若接入请求携带 与 UE注册的 MME对应的用户标识， 则 RAN通过 RRC连接拒绝消息发送带有与不允许 接入的网络对应的退避时间的指示消息。
指示消息有多种形式， 可以通过不同的信息元（ IE )来指示 UE是哪个网络发生过载， 及指示相应的退避时间。例如， RRC连接拒绝消息还包括表示 RAN是否过载的 RAN过载 指示； 当 CN过载且 RAN未过载时， 与不允许接入的网络对应的退避时间包括针对 CN过 载的退避时间， RAN过载指示为表示 RAN未过载的 RAN过载指示； 当 RAN过载且 CN 未过载时， 退避时间包括针对 RAN过载的退避时间， RAN过载指示为表示 RAN过载的 RAN过载指示；当 RAN和 CN均过载时，退避时间包括 RAN和针对 CN过载的退避时间， RAN过载指示为表示 RAN过载的 RAN过载指示。
或者， RRC连接拒绝消息还包括 RAN未过载时针对 RAN过载的退避时间， 该针对 RAN过载的退避时间为指定值。 也就是说， 若 CN未过载（即允许接入 CN ), 而 RAN过 载（即不允许接入 RAN ), 则 RRC连接拒绝消息中不携带针对 CN过载的退避时间， 只携 带针对 RAN过载的退避时间。 若 CN过载， 而 RAN未过载， 则 RRC连接拒绝消息中携 带针对 CN过载的退避时间和针对 RAN过载的退避时间， 但针对 RAN过载的退避时间为 指定值。 若 CN和 RAN均过载， 则 RRC连接拒绝消息中携带针对 CN过载的退避时间和 针对 RAN过载的退避时间， 针对 RAN过载的退避时间不为指定值。
参见图 9, 本实施例中用户设备包括： 接口模块 901、 解析模块 902和控制模块 903。 接口模块 901用于发送接入请求后， 接收带有与不允许接入的网络对应的退避时间的 指示消息。 与不允许接入的网络对应的退避时间包括针对 RAN过载的退避时间、针对 CN 过载的退避时间、 或针对 RAN过载的退避时间和针对 CN过载的退避时间。接口模块 901 通过 RRC 连接拒绝消息接收带有与不允许接入的网络对应的退避时间的指示消息； 接口 模块 901还用于发送 RRC连接完成消息； RRC连接建立完成消息中可携带与 UE注册的 MME对应的用户标识， 则接口模块 901可通过 RRC连接释放消息接收带有与不允许接入 的网络对应的退避时间的指示消息；若接入请求携带与 UE注册的 MME对应的用户标识， 则接口模块 901通过 RRC连接拒绝消息接收带有与不允许接入的网络对应的退避时间的 指示消息。
解析模块 902用于对指示消息进行解析， 获得与不允许接入的网络对应的退避时间。 控制模块 903用于根据与不允许接入的网络对应的退避时间不允许再次接入网络。 具 体的， 控制模块 903可以根据针对 RAN过载的退避时间启动和设置 T302定时器， 以及控 制模块 903中的 NAS层部分可以根据针对 CN过载的退避时间进行相应的退避处理。
具体的， 控制模块 903发现 RRC连接拒绝消息仅有针对 RAN过载的退避时间时， 确 定 CN未过载， 而 RAN过载， 只需对针对 RAN过载的退避时间进行处理， 如启动和设置 T302定时器等， 在 T302定时器启动期间不允许该 UE进行接入网络尝试。
控制模块 903发现 RRC连接拒绝消息携带有针对 CN过载的退避时间时， 将针对 CN 过载的退避时间交由内部的 NAS层处理，在针对 CN过载的退避时间对应的定时器启动期 间不允许该 UE进行接入网络尝试。
控制模块 903发现 RRC连接拒绝消息携带有针对 RAN过载的退避时间且该退避时间 为指定值时，忽略针对 RAN过载的退避时间，或者对针对 RAN过载的退避时间进行处理。
控制模块 903发现 RRC连接拒绝消息携带有针对 CN过载的退避时间和针对 RAN过 载的退避时间， 且针对 RAN过载的退避时间不为指定值时， 控制模块 903中 RRC层维护 T302定时器， NAS层维护针对 CN过载的退避时间对应的定时器。 RRC层通知 NAS层 T302定时器开启或超时。 当 T302定时器有效时， NAS层禁止所有需发起的接入请求。 当 T302定时器无效（未开启或超时） 时， NAS层#>据针对 CN过载的退避时间对应的定时 器和建立原因来决定是否禁止发起接入。
接口模块 901可接收可通过 RRC连接释放消息接收带有针对 CN过载的退避时间的指 示消息。控制模块 903发现 RRC连接释放消息携带有针对 CN过载的退避时间时，将针对
CN过载的退避时间交由内部的 NAS层处理， 在针对 CN过载的退避时间对应的定时器启 动期间不允许该 UE进行接入网络尝试。
RRC连接拒绝消息还包括表示 RAN是否过载的 RAN过载指示。控制模块 903发现携 带有针对 CN过载的退避时间时， 将针对 CN过载的退避时间交由内部的 NAS层处理， 发 现 RAN过载指示为表示 RAN未过载的 RAN过载指示时，忽略针对 RAN过载的退避时间。
控制模块 903发现 RAN过载指示为表示 RAN过载的 RAN过载指示时，按照针对 RAN 过载的退避时间进行处理， 未发现有针对 CN过载的退避时间时， 也就不需要进行关于针 对 CN过载的退避时间的处理。
控制模块 903发现 RAN过载指示为表示 RAN过载的 RAN过载指示时，按照针对 RAN 过载的退避时间进行处理，在 T302定时器启动期间不允许该 UE进行接入网络尝试，发现 有针对 CN过载的退避时间时， 将针对 CN过载的退避时间交由内部的 NAS层处理。 此时 控制模块 903获得针对 RAN和 CN过载的退避时间， 控制模块 903中 RRC层维护 T302 定时器， NAS层维护针对 CN过载的退避时间对应的定时器。 RRC层通知 NAS层 T302 定时器开启或超时。 当 T302定时器有效时， NAS层禁止所有需发起的接入请求。 当 T302 定时器无效（未开启或超时）时， NAS层#>据针对 CN过载的退避时间对应的定时器和建 立原因来决定是否禁止发起接入。
较佳的， 针对 CN过载时， 用户设备还包括： 记录模块 904, 参见图 10。 记录模块 904 用于发现指示消息携带有针对 CN过载的退避时间时，记录与该指示消息对应 RRC连接所 对应的建立原因。 控制模块 903在针对 CN过载的退避时间对应的定时器启动期间， 需要 再次进行接入时， 若本次接入请求的建立原因的接入优先级不高于已记录的建立原因的接 入优先级， 则禁止接入， 若本次接入请求的建立原因的接入优先级高于已记录的建立原因 的优先级， 针对 CN过载的退避时间对应的定时器失效， 允许发送接入请求。
参见图 11 , 本实施例中核心网设备包括： 控制模块 1101和接口模块 1102。 核心网设 备可具体为 MME或 OAM。
控制模块 1101用于确定自身是否发生过载， 若是， 则确定针对过载的退避时间。控制 模块 1101可以根据自身过载情况拒绝某些建立原因接入，并根据拒绝的这些建立原因确定 一个合适的退避时间。
接口模块 1102用于向 RAN发送携带有针对过载的退避时间的过载控制消息。
MME可以根据自身及其它核心网节点的过载情况来确定退避时间， 并发送给 RAN。
OAM可以获得各 MME的负荷情况， 并据此确定针对过载的退避时间， 然后发送给 RAN。 RAN可能获得关于多个 MME的多个针对过载的退避时间。 当不区分单 CN节点时， RAN 可根据获得的多个针对过载的退避时间综合确定一个针对 CN的退避时间，如选择最大值， 或平均值等方式。 当区分单 CN节点时， RAN根据 UE注册的 MME的针对过载的退避时 间确定针对 CN的退避时间。
本发明实施例中无线接入网 （ RAN )在接入过程中进行关于 RAN和 CN (核心网）的 接入控制的判断， 若有不允许接入的网络， 即该网络过载， 则在给 UE的指示消息中携带 与不允许接入的网络对应的退避时间。也就是说， RAN可以针对 RAN和 CN的过载情况， 分别有针对性的设置退避时间， 更好的进行接入控制， 从而尽可能避免网络拥塞以及终端 接入时延过大。本发明实施例提供了指示消息的多种结构，可以通过该多种结构来通知 UE 哪个网络发生过载以及相应的退避时间， 有利于灵活配置。 并且， 针对各种接入控制的判 断方式， 提供了相应的实现方案， 适用于多种网络需求。
本领域内的技术人员应明白， 本发明的实施例可提供为方法、 系统、 或计算机程序产 品。 因此， 本发明可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且， 本发明可釆用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介盾 (包括但不限于磁盘存储器和光学存储器等）上实施的计算机程序产品的形 式。
本发明是参照根据本发明实施例的方法、 设备（系统）、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器， 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中， 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品， 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理， 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。 显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和 范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种接入控制的方法， 其特征在于， 包括以下步骤：
在随机接入过程中， 无线接入网络 RAN根据当前 RAN和核心网 CN的负荷情况以及 UE上报的终端或业务信息， 判断是否允许所述 UE接入 RAN和 CN;
当不允许接入 RAN和 CN中至少有一个网络时， RAN向 UE发送带有与不允许接入 的网络对应的退避时间的指示消息。
2、 如权利要求 1所述的方法， 其特征在于， 终端或业务信息包括下列信息中的一项： 指示是否为低优先级接入终端或业务；
指示是否是漫游终端以及具体的漫游子类信息；
指示是否为时间容忍终端或业务；
指示是否是时间可控终端或业务；
指示是否为小数据量终端或业务。
3、 如权利要求 1或 2所述的方法， 其特征在于， 与不允许接入的网络对应的退避时 间包括： 针对 RAN过载的退避时间、 针对 CN过载的退避时间、 或针对 RAN过载的退避 时间和针对 CN过载的退避时间。
4、 如权利要求 3所述的方法， 其特征在于， 当不需要区分单 CN节点过载时， RAN 通过 RRC连接拒绝消息发送带有与不允许接入的网络对应的退避时间的指示消息；
当需要区分单 CN节点过载时， 若接入请求未携带与 UE注册的 MME对应的用户标 识， 则还包括步骤： 接收 UE发送的 RRC连接建立完成消息； RAN向 UE发送带有与不 允许接入的网络对应的退避时间的指示消息的步骤包括： 若 RRC 连接建立完成消息中携 带有与 UE注册的 MME对应的用户标识， 且该用户标识对应的 MME与 RAN有 S 1接口 且过载， 或者 MME池内所有 MME过载， 则 RAN通过 RRC连接释放消息发送带有针对 CN过载的退避时间的指示消息； 若接入请求携带与 UE注册的 MME对应的用户标识， 则 RAN通过 RRC连接拒绝消息发送带有与不允许接入的网络对应的退避时间的指示消息。
5、 如权利要求 4所述的方法， 其特征在于， RRC连接拒绝消息还包括： 表示 RAN是 否过载的 RAN过载指示，或 RAN未过载时针对 RAN过载的退避时间，该针对 RAN过载 的退避时间为指定值。
6、 如权利要求 1所述的方法， 其特征在于， RAN向 UE发送带有与不允许接入的网 络对应的退避时间的指示消息之前， 还包括步骤： 需要确定针对 CN过载的退避时间时， RAN根据当前网络负荷情况以及终端上报的信息自行为 UE确定针对 CN过载的退避时间， 或者参考 MME或者 OAM指示的退避时间并做随机化处理来为 UE确定针对 CN过载的退 避时间， 需确定针对 RAN过载的退避时间时， RAN自行为 UE确定针对 RAN过载的退避 时间。
7、 一种接入过程中的消息处理的方法， 其特征在于， 包括以下步骤：
UE发送接入请求后， 接收带有与不允许接入的网络对应的退避时间的指示消息； 与 不允许接入的网络对应的退避时间包括针对 RAN过载的退避时间、 针对 CN过载的退避 时间、 或针对 RAN过载的退避时间和针对 CN过载的退避时间；
UE对指示消息进行解析 , 获得与不允许接入的网络对应的退避时间；
UE根据与不允许接入的网络对应的退避时间不允许再次接入网络。
8、 如权利要求 7所述的方法， 其特征在于， 还包括步骤： UE上报终端或业务信息， 终端或业务信息包括下列信息中的一项：
指示是否为低优先级接入终端或业务；
指示是否是漫游终端以及具体的漫游子类信息；
指示是否为时间容忍终端或业务；
指示是否是时间可控终端或业务；
指示是否为小数据量终端或业务。
9、如权利要求 7或 8所述的方法，其特征在于，指示消息为 RRC连接拒绝消息或 RRC 连接释放消息。
10、 如权利要求 7或 8所述的方法， 其特征在于， UE根据与不允许接入的网络对应 的退避时间不允许再次接入网络的步骤包括：
UE发现指示消息携带有针对 RAN过载的退避时间时， 启动和设置针对 RAN过载的 退避时间对应的 T302定时器， 在 T302定时器启动期间不允许该 UE进行接入网络尝试， UE发现指示消息携带有针对 CN过载的退避时间时， UE内的 NAS层启动和设置针对 CN 过载的退避时间对应的定时器， 在针对 CN过载的退避时间对应的定时器启动期间不允许 该 UE进行接入网络尝试。
11、 如权利要求 10所述的方法， 其特征在于， 指示消息为 RRC连接拒绝消息， 所述
RRC连接拒绝消息携带有针对 RAN过载的退避时间；
UE发现 RRC连接拒绝消息还携带有表示 RAN过载的 RAN过载指示，则启动和设置 针对 RAN过载的退避时间对应的 T302定时器， 在 T302定时器启动期间不允许该 UE进 行接入网络尝试； 或者
UE发现 RRC连接拒绝消息还携带有表示 RAN未过载的 RAN过载指示，则忽略指示 消息中针对 RAN过载的退避时间； 或者
UE发现指示消息中针对 RAN过载的退避时间为指定值时， 忽略该退避时间。
12、 如权利要求 10所述的方法， 其特征在于， 还包括步骤： UE发现指示消息携带有 针对 CN过载的退避时间时， 记录与该指示消息对应的 RRC连接的建立原因； 在针对 CN过载的退避时间对应的定时器启动期间， 不允许 UE进行接入网络尝试的 步骤包括： 在针对 CN过载的退避时间对应的定时器启动期间， 若 UE需要再次进行接入 时， 首先需要进行判断， 如果本次接入请求的建立原因的接入优先级不高于已记录的建立 原因的接入优先级， 则针对 CN过载的退避定时器继续运行， 禁止接入， 如果本次接入请 求的建立原因的接入优先级高于已记录的建立原因的优先级， 针对 CN过载的退避时间对 应的定时器失效。
13、 一种接入网设备， 其特征在于， 包括：
控制模块， 用于收到 UE的接入请求后， 根据当前 RAN和 CN的负荷情况以及 UE上 报的终端或业务信息， 判断是否允许所述 UE接入 RAN和 CN;
接口模块， 用于当不允许接入 RAN和 CN中至少有一个网络时， 向 UE发送带有与不 允许接入的网络对应的退避时间的指示消息。
14、 如权利要求 13 所述的接入网设备， 其特征在于， 终端或业务信息包括下列信息 中的一项：
指示是否为低优先级接入终端或业务；
指示是否是漫游终端以及具体的漫游子类信息；
指示是否为时间容忍终端或业务；
指示是否是时间可控终端或业务；
指示是否为小数据量终端或业务。
15、 如权利要求 13或 14所述的接入网设备， 其特征在于， 与不允许接入的网络对应 的退避时间包括： 针对 RAN过载的退避时间、 针对 CN过载的退避时间、 或针对 RAN过 载的退避时间和针对 CN过载的退避时间。
16、 如权利要求 15所述的接入网设备， 其特征在于， 当不需要区分单 CN 节点过载 时， RAN通过 RRC连接拒绝消息发送带有与不允许接入的网络对应的退避时间的指示消 息；
当需要区分单 CN 节点过载时， 若接入请求未携带与 UE注册的 MME对应的用户标 识， 则还包括步骤： 接收 UE发送的 RRC连接建立完成消息， 若 RRC连接建立完成消息 中携带有与 UE注册的 MME对应的用户标识， 且该用户标识对应的 MME与 RAN有 S 1 接口且过载， 或者 MME池内所有 MME过载， 则 RAN通过 RRC连接释放消息发送带有 与不允许接入的网络对应的退避时间的指示消息； 若接入请求携带与 UE注册的 MME对 应的用户标识， 则 RAN通过 RRC连接拒绝消息发送带有与不允许接入的网络对应的退避 时间的指示消息。
17、 如权利要求 16所述的接入网设备， 其特征在于， RRC连接拒绝消息还包括： 表 示 RAN是否过载的 RAN过载指示，或 RAN未过载时针对 RAN过载的退避时间，该针对 RAN过载的退避时间为指定值。
18、 如权利要求 13 所述的接入网设备， 其特征在于， 控制模块还用于需要确定针对 CN过载的退避时间时， 根据当前网络负荷情况以及终端上报的信息自行为 UE确定针对 CN过载的退避时间， 或者参考 MME或者 OAM指示的退避时间并做随机化处理来为 UE 确定针对 CN过载的退避时间，需确定针对 RAN过载的退避时间时， 自行为 UE确定针对 RAN过载的退避时间。
19、 一种用户设备， 其特征在于， 包括：
接口模块， 用于发送接入请求后， 接收带有与不允许接入的网络对应的退避时间的指 示消息； 与不允许接入的网络对应的退避时间包括针对 RAN过载的退避时间、 针对 CN 过载的退避时间、 或针对 RAN过载的退避时间和针对 CN过载的退避时间；
解析模块， 用于对指示消息进行解析， 获得与不允许接入的网络对应的退避时间； 控制模块， 用于根据与不允许接入的网络对应的退避时间不允许再次接入网络。
20、 如权利要求 19所述的用户设备， 其特征在于， 指示消息为 RRC连接拒绝消息或 RRC连接释放消息。
21、 如权利要求 19 所述的用户设备， 其特征在于， 控制模块发现指示消息携带有针 对 RAN过载的退避时间时， 启动和设置针对 RAN过载的退避时间对应的 T302定时器， 在 T302定时器启动期间不允许该 UE进行接入网络尝试，控制模块发现指示消息携带有针 对 CN过载的退避时间时，控制模块内的 NAS层启动和设置针对 CN过载的退避时间对应 的定时器， 在针对 CN过载的退避时间对应的定时器启动期间不允许该用户设备进行接入 网络尝试。
22、 如权利要求 21所述的用户设备， 其特征在于， 指示消息为 RRC连接拒绝消息， 所述 RRC连接拒绝消息携带有针对 RAN过载的退避时间；
控制模块发现 RRC连接拒绝消息还携带有表示 RAN过载的 RAN过载指示， 则启动 和设置针对 RAN过载的退避时间对应的 T302定时器， 在 T302定时器启动期间不允许该
UE进行接入网络尝试； 或者
控制模块发现 RRC连接拒绝消息还携带有表示 RAN未过载的 RAN过载指示， 则忽 略指示消息中针对 RAN过载的退避时间； 或者
控制模块发现指示消息中针对 RAN过载的退避时间为指定值时， 忽略该退避时间。
23、 如权利要求 19 所述的用户设备， 其特征在于， 还包括： 记录模块， 用于发现指 示消息携带有针对 CN过载的退避时间时， 记录与该指示消息对应 RRC连接的建立原因； 控制模块在针对 CN过载的退避时间对应的定时器启动期间， 需要再次进行接入时， 若本次接入请求的建立原因的接入优先级不高于已记录的建立原因的接入优先级， 则禁止 接入，若本次接入请求的建立原因的接入优先级高于已记录的建立原因的优先级，针对 CN 过载的退避时间对应的定时器失效， 允许发送接入请求。
24、 一种核心网设备， 其特征在于， 包括：
控制模块， 用于确定自身是否发生过载， 若是， 则确定针对过载的退避时间； 接口模块， 用于向 RAN发送携带有针对过载的退避时间的过载控制信息。
PCT/CN2012/070176 2011-01-10 2012-01-10 一种接入控制的方法及装置 Ceased WO2012094982A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/978,402 US9220031B2 (en) 2011-01-10 2012-01-10 Access control method and device
EP12733875.4A EP2665310B1 (en) 2011-01-10 2012-01-10 Access control method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110003807.7 2011-01-10
CN2011100038077A CN102111847B (zh) 2011-01-10 2011-01-10 一种接入控制的方法及装置

Publications (1)

Publication Number Publication Date
WO2012094982A1 true WO2012094982A1 (zh) 2012-07-19

Family

ID=44175832

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/070176 Ceased WO2012094982A1 (zh) 2011-01-10 2012-01-10 一种接入控制的方法及装置

Country Status (4)

Country Link
US (1) US9220031B2 (zh)
EP (1) EP2665310B1 (zh)
CN (1) CN102111847B (zh)
WO (1) WO2012094982A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014078604A3 (en) * 2012-11-15 2014-07-10 Blackberry Limited System and method for resource management in a wireless network

Families Citing this family (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111847B (zh) * 2011-01-10 2013-07-24 大唐移动通信设备有限公司 一种接入控制的方法及装置
CN102098759A (zh) * 2011-02-18 2011-06-15 电信科学技术研究院 一种接入控制的方法及装置
CN102905344A (zh) * 2011-07-26 2013-01-30 中兴通讯股份有限公司 接入控制的方法及系统、网络侧网元、用户设备
EP2742736B1 (en) * 2011-08-11 2020-02-26 Intel Corporation Extended access barring
KR101771260B1 (ko) * 2011-10-04 2017-08-24 삼성전자주식회사 이동 통신 시스템에서 사용자 단말의 접속 제어 방법 및 장치
CN102547912B (zh) * 2012-01-17 2015-08-05 电信科学技术研究院 一种接入控制方法及装置
KR20140116409A (ko) * 2012-01-18 2014-10-02 엘지전자 주식회사 무선 통신 시스템에서 다중 우선순위 제어 방법 및 장치
CN103298027B (zh) * 2012-02-24 2016-09-14 华为技术有限公司 一种控制网络拥塞的方法、装置和网络系统
CN103313344B (zh) * 2012-03-07 2017-04-05 中兴通讯股份有限公司 融合的核心网及其接入方法
CN108966280B (zh) * 2012-03-30 2021-12-03 索尼移动通讯有限公司 移动终端和网络负载控制方法
WO2013170444A1 (zh) * 2012-05-15 2013-11-21 华为技术有限公司 接入控制方法及终端、接入网设备
CN108064067A (zh) 2012-09-29 2018-05-22 华为终端有限公司 控制用户设备与网络连接的方法及移动管理设备
US9854381B2 (en) * 2012-11-02 2017-12-26 Lg Electronics Inc. Method for transmitting data of MTC device
CN103095605A (zh) * 2013-01-25 2013-05-08 电子科技大学 一种移动物联网中融合路由器的数据传输方法及系统
ITTO20130189A1 (it) * 2013-03-08 2014-09-09 Sisvel Technology Srl Apparato d'utente per telecomunicazioni mobili e metodo per accedere ad una rete di telecomunicazioni
US9294980B2 (en) * 2013-03-14 2016-03-22 At&T Mobility Ii Llc Apparatus and method for management of service requests in an overload environment
GB2512393A (en) 2013-03-28 2014-10-01 Nec Corp Apparatus and methods for small data transmission
WO2015005842A1 (en) * 2013-07-09 2015-01-15 Telefonaktiebolaget L M Ericsson (Publ) Core network node, radio access network node and methods therein for contrail overload in core network
US9730218B2 (en) * 2013-11-01 2017-08-08 Qualcomm Incorporated Systems and methods for group access to the wireless medium of a wireless network
EP3226622B1 (en) * 2014-01-31 2018-06-13 Fujitsu Limited Access method of wireless communication network
WO2015152681A1 (en) * 2014-04-03 2015-10-08 Lg Electronics Inc. A method and appartus for supporting an iops in a wireless access system
CN106165520B (zh) * 2014-12-19 2019-11-15 华为技术有限公司 一种触发退避的方法、基站设备、用户设备及系统
HK1252002A1 (zh) * 2015-08-13 2019-05-10 苹果公司 用於蜂窝物联网的轻量级s-1 lite协议设计
GB2541247A (en) * 2015-08-14 2017-02-15 Nec Corp Communication system
JP2019068111A (ja) * 2016-02-09 2019-04-25 株式会社Ｎｔｔドコモ ユーザ装置及び通信方法
US10616114B2 (en) * 2016-07-14 2020-04-07 Mediatek Singapore Pte. Ltd. Congestion control handling between communication apparatus and network
CN108811168B (zh) * 2016-08-12 2020-01-17 华为技术有限公司 无线网络的接入控制方法及装置
EP3934365B1 (en) * 2016-08-16 2024-01-17 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Methods and devices for transmitting information
US12114283B2 (en) 2016-08-21 2024-10-08 Qualcomm Incorporated Methods and systems for support of location for the internet of things
CN109923879B (zh) * 2016-09-30 2022-03-22 苹果公司 控制平面演进分组系统的核心网过载控制
US11405863B2 (en) 2016-10-05 2022-08-02 Qualcomm Incorporated Systems and methods to enable combined periodic and triggered location of a mobile device
US11323335B2 (en) 2016-10-18 2022-05-03 Telefonaktiebolaget Lm Ericsson (Publ) SLA handling in network slices
CN108616956B (zh) * 2017-01-16 2020-10-20 普天信息技术有限公司 一种电力无线专网中业务隔离的方法
US10159033B2 (en) * 2017-01-24 2018-12-18 Verizon Patent And Licensing Inc. System and method for controlling usage of priority access in networks
CN108696911B (zh) * 2017-04-11 2020-12-01 中国移动通信集团设计院有限公司 一种物联网数据传输方式的选择方法和装置
CN109891939B (zh) * 2017-11-06 2020-08-18 Oppo广东移动通信有限公司 一种接入控制的方法、设备及计算机可读介质
WO2019113753A1 (zh) * 2017-12-11 2019-06-20 北京小米移动软件有限公司 用于缩短接入时延的方法、装置、用户设备及基站
WO2019119447A1 (en) * 2017-12-22 2019-06-27 Qualcomm Incorporated Expedited release of a user equipment
EP3782433B1 (en) 2018-04-16 2024-01-17 Telefonaktiebolaget LM Ericsson (publ) Methods and apparatuses for handling of reject wait time
CN109167793B (zh) * 2018-09-20 2021-06-15 上海上源泵业制造有限公司 一种基于物联网的水利监测系统
CN111757531A (zh) * 2019-03-27 2020-10-09 普天信息技术有限公司 随机接入的回退方法及装置
CN113692032A (zh) * 2020-05-19 2021-11-23 华为技术有限公司 通信方法和通信装置
CN113905338A (zh) * 2020-07-06 2022-01-07 中国移动通信有限公司研究院 一种指定漫回的方法、漫回的方法、网络设备及终端
US12108305B2 (en) 2020-09-29 2024-10-01 Qualcomm Incorporated System and methods for power efficient positioning of a mobile device
WO2025122038A1 (en) * 2023-12-06 2025-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Methods and network node for handling a connection establishment procedure

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060698A (zh) * 2006-04-17 2007-10-24 大唐移动通信设备有限公司 移动通信系统中实现负荷均衡的方法及其通信设备
CN101237694A (zh) * 2007-01-31 2008-08-06 日本电气株式会社 移动无线通信系统、基站、移动终端及随机接入控制方法
CN101547492A (zh) * 2008-03-24 2009-09-30 华为技术有限公司 一种限制接入类型的方法
CN102111847A (zh) * 2011-01-10 2011-06-29 大唐移动通信设备有限公司 一种接入控制的方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050024085A (ko) * 2003-09-04 2005-03-10 삼성전자주식회사 광대역 이동통신 시스템에서 상향 억세스 접속 방법
US8996005B2 (en) * 2009-01-23 2015-03-31 Htc Corporation Method of handling cell change and related apparatus
US20120069737A1 (en) * 2009-03-27 2012-03-22 Telefonaktiebolaget L M Ericsson (Publ) Overload avoidance with home node b gateway (henb gw) in lte
US20100302950A1 (en) * 2009-05-30 2010-12-02 Zhao Ray R Timer adjustment for load control
CN106028270B (zh) * 2010-02-12 2020-08-04 交互数字专利控股公司 从wtru执行随机接入信道传输的方法、wtru、以及节点b
US9042221B2 (en) * 2010-04-28 2015-05-26 Lg Electronics Inc. Method of controlling congestion of MTC data in a mobile communication system
EP2469958B1 (en) * 2010-12-21 2017-11-01 Innovative Sonic Corporation Method and apparatus for improving wait time in a wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060698A (zh) * 2006-04-17 2007-10-24 大唐移动通信设备有限公司 移动通信系统中实现负荷均衡的方法及其通信设备
CN101237694A (zh) * 2007-01-31 2008-08-06 日本电气株式会社 移动无线通信系统、基站、移动终端及随机接入控制方法
CN101547492A (zh) * 2008-03-24 2009-09-30 华为技术有限公司 一种限制接入类型的方法
CN102111847A (zh) * 2011-01-10 2011-06-29 大唐移动通信设备有限公司 一种接入控制的方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014078604A3 (en) * 2012-11-15 2014-07-10 Blackberry Limited System and method for resource management in a wireless network

Also Published As

Publication number Publication date
US20130279330A1 (en) 2013-10-24
CN102111847B (zh) 2013-07-24
EP2665310A4 (en) 2016-12-21
EP2665310A1 (en) 2013-11-20
US9220031B2 (en) 2015-12-22
EP2665310B1 (en) 2019-03-13
CN102111847A (zh) 2011-06-29

Similar Documents

Publication Publication Date Title
WO2012094982A1 (zh) 一种接入控制的方法及装置
US11641601B2 (en) Method, apparatus and device for allowing terminal to move between 4G and 5G networks
RU2768363C2 (ru) Способ передачи данных и устройство
CN110958688B (zh) 用户设备及其执行的方法、基站及其执行的方法
US10674363B2 (en) Access control method, user equipment, and network device
CN102448117B (zh) 一种负荷控制的方法和设备
EP2785125B1 (en) Method and system for determining accessibility of terminal group
CN101888705B (zh) 长期演进网络中的业务建立控制方法、系统和终端设备
CN110475388B (zh) 处理无线资源控制讯息中恢复原因的装置及方法
WO2012110002A1 (zh) 一种接入控制的方法及装置
CN108464057A (zh) 用于窄带物联网的用户平面优化
WO2014176863A1 (zh) 接入控制方法及装置
WO2012041197A1 (zh) 一种移动性管理过程的处理方法及网络侧装置
JP7655405B2 (ja) ユーザ装置、及びユーザ装置の方法
WO2012079518A1 (zh) 一种获取终端位置信息的方法、系统和设备
WO2012041185A1 (zh) 一种通知能力的方法和网络拥塞控制的方法、系统及设备
WO2012109823A1 (zh) 一种机器类型通信设备的拥塞控制方法及系统
TWI783715B (zh) 5gsm擁塞定時器的處理
CN103379578B (zh) 一种网络拥塞控制方法及终端
CN102123436B (zh) 一种用户设备的监测方法和装置
CN101998575A (zh) 一种接入控制的方法、装置和系统
WO2012041156A1 (zh) 一种mtc设备接入网络的方法和设备
CN107018555B (zh) 网络接入方法、网络接入控制方法、用户终端及基站
CN107078914A (zh) 电信系统与方法
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置

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: 12733875

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13978402

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012733875

Country of ref document: EP