WO2012058969A1 - Method and device for controlling radio resources - Google Patents

Method and device for controlling radio resources Download PDF

Info

Publication number
WO2012058969A1
WO2012058969A1 PCT/CN2011/078597 CN2011078597W WO2012058969A1 WO 2012058969 A1 WO2012058969 A1 WO 2012058969A1 CN 2011078597 W CN2011078597 W CN 2011078597W WO 2012058969 A1 WO2012058969 A1 WO 2012058969A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
information
network side
service
rrc connection
Prior art date
Application number
PCT/CN2011/078597
Other languages
French (fr)
Chinese (zh)
Inventor
戴谦
邓云
艾建勋
毛磊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012058969A1 publication Critical patent/WO2012058969A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/06Access restriction performed under specific conditions based on traffic conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • H04W76/34Selective release of ongoing connections
    • H04W76/36Selective release of ongoing connections for reassigning the resources associated with the released connections

Definitions

  • a third-generation mobile communication Long Term Evolution (LTE) system consists of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a User Equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • UE User Equipment
  • the Evolved Packet Core (EPC) is an evolved packet core network.
  • the E-UTRAN is composed of an enhanced base station (e B) of the access network element.
  • the e B is connected to the terminal UE through the Uu interface, and is connected to the core network element, such as a Mobility Management Entity (MME), through the S1 interface.
  • MME Mobility Management Entity
  • the network side has a multi-level access control processing mechanism for the access of the user equipment, so as to ensure that the network side does not overload due to excessive user equipment access.
  • the user equipment accesses the network side and needs to complete several processes as shown in FIG. 1.
  • the network side access device is set as the mobility management entity MME: Step 102: Random access procedure: The user equipment completes through the process. Synchronization with the network side; Step 104: Radio Resource Control (RRC) connection establishment process: establishing a signaling bearer of the user equipment and the access network network element; Step 106, attaching (Attach) process: completing the user equipment Identification information acquisition, authentication process, and security setup (Security Setup).
  • RRC Radio Resource Control
  • the network side sets 15 access levels (ACs) for different call types.
  • the normal calls belong to AC0 ⁇ 9, and the emergency calls belong to AC10.
  • Other high-priority calls belong to AC11 ⁇ 15.
  • the network side sets a control factor for AC0 9 and sets the "No Forbidden" flag for AC10 and AC11 15 and broadcasts it to the user equipment to control the random access behavior of these call types.
  • the signaling interaction between the user equipment and the access network element is as shown in FIG. 2, FIG. 3 and FIG. 4, and there are three processes of connection establishment, connection rejection and connection release, in FIG. 2 and FIG. 3
  • the network side access device is a base station. As shown in FIG.
  • the connection setup includes the following steps: Step 202: The user equipment initiates an RRC connection setup request. Step 204: The base station feeds back an RRC connection setup message to the user equipment. Step 206: The user equipment sends an RRC connection setup complete message to the base station.
  • the connection rejection includes the following process: Step 302: The user equipment initiates an RRC connection establishment request.
  • the connection release includes the following process: Step 402: The base station sends an RRC connection release message to the user equipment.
  • the network side can "accept”, “reject” and “release” the RRC connection establishment request of the user equipment according to its own data load capacity and signaling load capacity, and air interface load capability. "The judgment.” Considering that the connection request initiated by the user equipment may be based on different types of services, and the priorities of the services may be different, in order to implement more flexible and efficient admission control, in the current RRC layer protocol, the user equipment is required to be in the RRC.
  • the connection establishment request (RRC Connection Request) carries the reason information of the connection establishment.
  • the existing connection establishment information includes the following: Emergency (emergency, indicating that the user equipment initiates an emergency call);
  • High Priority Access (high priority access, indicating that the user equipment initiates a high priority service class call); mt-Access (indicating that the user equipment is applying for a connection due to the called party); mo-Signalling (indicating that the user equipment is the initiator) Called signaling class); mo-Data (indicating that the user equipment is the originating caller data type call).
  • mt-Access indicating that the user equipment is applying for a connection due to the called party
  • mo-Signalling (indicating that the user equipment is the initiator) Called signaling class
  • mo-Data indicating that the user equipment is the originating caller data type call.
  • M2M Machine to Machine communication
  • machine type communication in 3GPP, or MTC
  • M2M In the application of M2M, the business types are very wide, such as household meter reading, industrial production instrumentation automation, water quality monitoring, intelligent transportation and asset tracking, etc. M2M applications will enter all walks of life, thousands of households, and M2M business types also There will be tens of thousands, and the QoS (Quality of Service) requirements for the network side and for operators will also be varied. The number of M2M user devices will also far exceed the current mobile phone terminals, which poses a huge pressure on the current and future wireless networks. Due to the huge number of M2M user equipments, 3Gpp currently proposes the concept of managing user equipments in a group manner. In the context of M2M applications, how to protect the network and how to prevent network overload has become a primary problem.
  • the user equipment may perform access control on the random access procedure or the user equipment in the RRC layer during the process of establishing a connection with the network and completing the attachment.
  • the RRC connection establishment request is controlled, but the flexibility of the current control mechanism cannot meet the admission control of the high-density, multi-service user equipment.
  • the current statistics of operators show that the load of data services (such as Internet access, video call port, FTP (File Transfer Protocol) download) in wireless communication has exceeded the load of voice services.
  • data services such as Internet access, video call port, FTP (File Transfer Protocol) download
  • the voice service is the basis of the network operation, but according to the current Protocol standard, when the user equipment initiates a voice call and a data service call, the connection establishment cause information in the RRC connection establishment request is the same data model mo-Data, and the network side cannot distinguish between voice or data service, and thus cannot be flexible. Admission control.
  • different M2M applications have different business models.
  • the business model refers to the data transmission model when the user equipment and the network side exchange data.
  • the elements of the business model include: data interaction periodicity, data interaction frequency, data size, Data interaction direction (refer to the above line data, or the following line data, or up and down The traffic is similar).
  • Data interaction periodicity Take smart meters as an example. Some power companies require each smart meter to report meter reading data every 5 minutes. Some power companies require each smart meter to report meter reading data every hour. Some power companies even only require intelligence. The meter reports the meter reading data once a day, and the traffic of each meter reading data is small. This constitutes three different business models, which can be called high frequency periodic small data reporting, low frequency periodic small data reporting, Very low frequency periodic small data is reported. Another example is a normal voice service, which can be called an extremely high frequency periodic small data interaction model.
  • the Internet service (usually clicking on a web page for several tens of seconds, the following line data is dominant, and the data traffic is large) may be referred to as an intermediate frequency non-periodic big data downlink model.
  • These different business models clearly have different pressures on the network, and the current mechanism is unable to distinguish the models of these services.
  • Different services also have different QoS requirements.
  • the QoS requirements related to admission control include: access delay tolerance. For example, some services are very sensitive to access delay (such as fire alarm, security, medical monitoring, etc.). The business is less sensitive to access delays (such as meter reading), and the current mechanism is unable to distinguish between these differences.
  • Different services or user equipments also have different priorities.
  • a primary object of the present invention is to provide a radio resource control method and apparatus to solve at least the problem that the flexibility of the current control mechanism cannot meet the admission control of a high-density, multi-service user equipment.
  • a radio resource control method including: when an RRC connection is established between a user equipment and a network side, the network side receives an RRC connection setup complete message sent by the user equipment, where The RRC connection setup complete message carries the access information; and the network side determines whether to maintain the RRC connection according to the load situation of the network side and the access information.
  • the access information includes any one or more of the following combinations: the type information of the user equipment, the group information of the user equipment, the priority information of the user equipment, and the user equipment.
  • the PLMN type information The PLMN type information, the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, and the pre-agreed service of the user equipment and the network side
  • the priority information the type information of the service model pre-agreed by the user equipment and the network side, and the service quality requirement type information of the service that the user equipment and the network side pre-agreed.
  • the grouping information of the user equipment includes a sequence number or an identifier of the user equipment group;
  • the priority information of the user equipment includes a priority of the user equipment pre-agreed by the network side and the user equipment.
  • the serial number or the identifier; the PLMN type information of the user equipment includes any one or more of the following combinations: whether the user equipment is identification information on its HPLMN, whether the user equipment is on a PLMN equivalent to its HPLMN.
  • the access level information of the user equipment on the network side includes an access level sequence number pre-agreed by the network side and the user equipment or Identifying; the type information of the service pre-agreed by the user equipment and the network side, including the classification by call service
  • the priority information of the pre-agreed service of the user equipment and the network side includes a priority sequence number or identifier of the service pre-agreed by the network side and the
  • the method before the establishment of the RRC connection between the user equipment and the network side, the method further includes: determining, by the user equipment, the access information according to the type of the user equipment and the service type of the service to be established, and connecting the The incoming information is added to the RRC Connection Setup Complete message.
  • the network side determines whether to maintain the RRC connection according to the access information, and further includes: when the determination result is yes, the RRC connection release procedure is not triggered, and the user equipment is connected to the network side. Maintaining the RRC connection; when the determination result is no, triggering an RRC connection release procedure, releasing the RRC connection.
  • a radio resource control apparatus which is applied to a network side, and includes: a receiving module, configured to receive an RRC connection sent by a user equipment when the network side establishes an RRC connection with a user equipment. a setup completion message, where the RRC connection setup complete message carries the access information, and the determining module is configured to determine whether to maintain the RRC connection according to the load situation of the network side and the access information.
  • the access information received by the receiving module is determined by a combination of any one or more of the following: type information of the user equipment, group information of the user equipment, priority information of the user equipment, The PLMN type information of the user equipment, the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, the user equipment and the network side.
  • the priority information of the pre-agreed service, the type information of the user equipment and the pre-agreed service model of the network side, and the service quality requirement type information of the service that the user equipment and the network side pre-agreed is determined by a combination of any one or more of the following: type information of the user equipment, group information of the user equipment, priority information of the user equipment, The PLMN type information of the user equipment, the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, the user equipment and the network side.
  • the receiving module is further configured to receive the access information that includes the following parameters: the packet information of the user equipment includes a sequence number or identifier of the user equipment group; and the priority information of the user equipment includes the network. And a priority sequence number or identifier of the user equipment that is pre-agreed by the user equipment; the PLMN type information of the user equipment includes a combination of any one or more of the following: whether the user equipment is an identifier on the HPLMN Information, whether the user equipment is in the identity information on the PLMN equivalent to its HPLMN, whether the user equipment is in its user identity module or the identity information on the PLMN in the preferred PLMN list included in the global subscriber identity module, Whether the user equipment is the identification information of the roaming user equipment, the identification information of the HPLMN of the user equipment, and the identifier information of the equivalent HPLMN of the user equipment; the access level information of the user equipment on the network side includes An access level sequence number or identifier pre-agreed by the network side
  • the priority serial number or the identifier; the type information of the service model pre-agreed by the user equipment and the network side includes the data communication model information of the service, where the data communication model information includes any one or more of the following combinations : Data interaction periodicity, data interaction frequency, data volume size, or data interaction direction.
  • the determining module further includes: a connection submodule, configured to: when the determination result is yes, does not trigger an RRC connection release procedure, so that the user equipment maintains the RRC connection with the network side; releasing the submodule And setting, when the determination result is no, triggering an RRC connection release procedure, releasing the RRC connection.
  • the radio resource control system is integrated in the access network device.
  • the RRC connection setup complete message carries the access information in the RRC connection setup complete message, and the network side can determine whether to maintain the RRC connection according to the network side load condition and the access information, so that the network side can be more accurate. Master the information of the user equipment to ensure that the network side implements precise control of the reception of high-density, multi-service user equipment.
  • FIG. 1 is a flowchart of a user equipment accessing a network side according to the related art
  • FIG. 2 is a schematic diagram of a connection establishment process of a user equipment and an access network network element according to the related art
  • 3 is a schematic diagram of a connection denial procedure of a user equipment and an access network element according to the related art
  • FIG. 4 is a schematic diagram of a connection release procedure of a user equipment and an access network element according to the related art
  • FIG. 5 is a schematic diagram of a connection according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a process for requesting an RRC connection establishment by a user equipment accessing a network side according to an embodiment of the present invention
  • FIG. 7 is a structure of a radio resource control apparatus according to an embodiment of the present invention
  • FIG. 8 is a schematic structural diagram of a determining module according to an embodiment of the present invention.
  • the method includes the following steps: Step 502: When establishing a radio resource control RRC connection between the user equipment and the network side, the network side receives the RRC connection setup complete message sent by the user equipment, where the RRC connection setup complete message is carried. There is access information; Step 504: The network side determines whether to maintain the RRC connection according to the load condition of the network side and the access information.
  • the RRC connection setup complete message carries the access information in the RRC connection setup complete message, and the network side can determine whether to maintain the RRC connection according to the network side load condition and the access information, so that the network side can be more accurate. Master the information of the user equipment to ensure that the network side implements precise control of the reception of high-density, multi-service user equipment.
  • the access information may include any one or more of the following combinations: type information of the user equipment, group information of the user equipment, priority information of the user equipment, and public land mobile network of the user equipment (Public Land Mobile Network, PLMN) type information, access level information of the user equipment on the network side, type information of the service pre-agreed by the user equipment and the network side, priority information of the pre-agreed service of the user equipment and the network side, user equipment and network side advance The type information of the agreed service model and the type of service quality requirement type of the service agreed by the user equipment and the network side.
  • PLMN Public Land Mobile Network
  • each option of the access information may include a plurality of specific parameters, for example, the group information of the user equipment may include a sequence number or identifier of the user equipment group; the priority information of the user equipment may include the network side and the user equipment in advance.
  • the priority sequence number or identifier of the agreed user equipment; the PLMN type information of the user equipment may include any one or more of the following combinations: whether the user equipment is on its local Public Land Mobile Network (HPLMN) Identification information, whether the user equipment is on the PLMN equivalent to its HPLMN, whether the user equipment is in its user identity module or the identification information on the PLMN in the preferred PLMN list included in the global subscriber identity module, whether the user equipment is roaming
  • the identification information of the user equipment, the identification information of the HPLMN of the user equipment, and the identifier information of the equivalent HPLMN of the user equipment; the access level information of the user equipment on the network side may include the access level sequence number pre-agreed by the network side and the user equipment or Identification; user equipment and network side pre-agreed
  • the type information of the service may include the type information classified according to the call service; the priority information of the service pre-agreed by the user equipment and the network side may include the priority number or identifier of the service pre
  • the call service type information refers to information classified by call service, including one or more of the following: a voice call of the calling party or the called party, a video stream call of the calling party or the called party, an interactive voice call of the calling party or the called party. , the calling or called data call, the calling or called signaling service, etc.
  • the data call can be only a simple one, or can be further divided into more detailed categories, such as: HyperText Transfer Protocol (Http) Internet service, FTP download service, meter reading service, monitoring service, intelligent traffic service , asset tracking business, etc.
  • Http HyperText Transfer Protocol
  • the type information of the user equipment refers to information classified by the user equipment, including one or more of the following: H2H user equipment, M2M user equipment, and other types of user equipment.
  • the group information of the user equipment refers to the identifier of the user equipment group, including: the serial number or identifier of the user equipment group (Group).
  • the Group-RNTI Radio Network Temporary Indicator
  • the group information of the user equipment can be directly used by the Group-RNTI, and the network can also be used.
  • a serial number pre-agreed by the side, and the network side establishes a one-to-one correspondence between the serial number and the group in advance.
  • the priority information of the user equipment refers to the priority of the user equipment agreed by the network side and the user equipment in advance, including: the priority number or the priority identifier.
  • the priority can be 1 or more, which can be higher than the existing H2H (Human To Human) device, or lower than the existing H2H device.
  • the existing H2H device refers to the RRC connection establishment reason already included in the existing protocol
  • it can include the following types: Simple level 1: H2H device, low priority device (relative to H2H equipment); or
  • Level 2 High priority equipment, H2H equipment, low priority equipment; or multiple levels: H2H equipment, low priority level 1 equipment, low priority level 2 equipment, ..., low priority N level equipment (N is a positive integer); Another multi-level: high priority level 1 equipment, high priority level 2 equipment, ..., high priority M level equipment, H2H equipment, low priority level 1 equipment, low priority level 2 equipment, ..., low priority N Level device (M and N are positive integers); The correspondence between the specific device type and device priority is pre-agreed by the network side and the user equipment. For example, an H2H device belongs to a common priority, and an M2M device belongs to a low priority.
  • the priority information of the service refers to the service priority agreed by the network side and the user equipment in advance, including: the priority sequence number or the priority identifier. Due to the introduction of smart phones and M2M devices, the types of wireless communication services are greatly increased.
  • the reasons for the establishment of RRC connections in the existing protocols include: Emergency, indicating that the user equipment initiates an emergency call; highPriorityAccess indicates that the user equipment initiates a high priority. Service-type call; mt-Access, indicating that the user equipment is applying for establishing a connection due to the called party; mo-Signalling, indicating that the user equipment is a caller signaling type call; mo-Data, indicating that the user equipment is calling the calling data type call .
  • H2H service refers to the RRC connection establishment reason already included in the existing protocol
  • Level 2 High-priority service, H2H service, low-priority service; or multi-level: H2H service, low priority level 1 service, low priority level 2 service, ..., low priority N level service (N is a positive integer); Another multi-level: high priority level 1 service, high priority level 2 service, ..., high priority M level service, H2H service, low priority level 1 service, low priority level 2 service, ..., low priority N Class service (M and N are positive integers); The correspondence between the specific service type and the service priority is pre-agreed by the network side and the user equipment.
  • the type information of the business model refers to the data communication model of the service, including one or more combinations of the following features: data interaction periodicity (whether it is periodic data interaction), data interaction frequency, data volume size, data interaction Direction (refer to the above data, or the following data, or the upstream and downstream traffic are similar).
  • a business model including only a simple feature information includes: a small data service model, or a high frequency business model, or a periodic business model, etc.; a business model including information of a plurality of characteristics includes: Data service model, low-frequency periodic small data reporting, very low-frequency periodic small data reporting, extremely high-frequency periodic small data interaction model, medium-frequency aperiodic big data downlink model, and so on.
  • the correspondence between the service type and the service model is usually pre-agreed by the network side and the user equipment.
  • the PLMN type information is the PLMN type information agreed by the network side and the user equipment in advance, including one or more of the following: whether the user equipment is on the HPLMN, whether the user equipment is in its equivalent. Identification information on the HPLMN, whether the user equipment is in the identification information of a PLMN in the preferred PLMN list included in its SIM (Subscriber Identity Module) or USIM (Universal Subscriber Identity Module) Whether it is the identification information of the roaming user equipment, the identification information of the HPLMN of the user equipment, or the identification information of the equivalent HPLMN of the user equipment.
  • SIM Subscriber Identity Module
  • USIM Universal Subscriber Identity Module
  • the Access Class information of the user equipment on the network side refers to the access level agreed by the network side and the user equipment in advance, including: the access level sequence number or the access level identifier; for example: Access Class N (N is greater than A positive number equal to 0).
  • the QoS requirement type information of the service includes a combination of one or more of various QoS requirements, such as: access delay tolerance, guaranteed traffic, allowable bit error rate, and the like.
  • the access delay can be set to: Simple Level 2: Sensitive to access delay and insensitive to access delay; Multi-level: High access delay sensitivity, access delay sensitivity, and access delay sensitivity Low; can also be a combination of multiple QoS requirements, for example: High access delay sensitivity + low guaranteed traffic + low error rate requirements; or access delay sensitivity + high guaranteed traffic + low error rate requirements.
  • the QoS requirements can also be divided into smaller levels than the enumerated examples, depending on the circumstances.
  • the list may clearly indicate the access information of the RRC connection, and the list may be one or more of the various feature information described above, or a combination of one or more.
  • Table 1 is an embodiment of the RRC connection access nature information list (which is a combination of priority information, service type information, and user equipment type information): Table 1
  • Table 2 is another embodiment of the RRC Connection Access Property Information List (which is a combination of service model information and QoS requirement information): Table 2
  • the access information list may also contain more or less than seven access information, for example, one, two, three. Item, ten or any natural number.
  • the RRC connection is established between the user equipment and the network side.
  • the method may further include: determining, by the user equipment, the access information according to the type of the user and the service type of the service to be established, and connecting The incoming information is added to the RRC Connection Setup Complete message.
  • the network side determines whether to maintain the RRC connection according to the access information, different execution results may be selected.
  • the network side may choose not to trigger the RRC connection release process, so that the user equipment and the network side maintain RRC connection; or, when the determination result is no, the network side may choose to trigger an RRC connection release procedure to release the RRC connection.
  • the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.
  • the embodiment of the present invention is applicable to an LTE system or a UMTS (Universal Mobile Telecommunications System).
  • the user equipment accesses the network side and applies for RRC connection establishment.
  • the processing flow is as shown in FIG. 6, in this example.
  • the network side access device takes the base station as an example, and the steps are as follows: Step 602: The user equipment and the base station establish synchronization; Step 604: The user equipment sends an RRC connection setup request message to the base station. Step 606: The base station feeds back the RRC connection establishment to the user equipment. The message is: Step 608: The user equipment selects the corresponding access property information according to the current connection establishment property, and includes the information in the RRC connection setup complete message. Step 610: The user equipment sends an RRC connection setup complete message to the base station.
  • Step 612 The base station determines whether the current RRC connection of the user equipment can be maintained according to the load status of the network side of the user equipment, if yes, go to step 614, if not, go to step 606; 614. If the base station agrees that the user equipment maintains the RRC connection, Send an RRC connection release procedure, the user equipment continues the subsequent connection process and a core network; Step 616: If the base station does not agree that the user equipment maintains the RRC connection, the RRC connection release procedure is triggered, and the RRC connection of the user equipment is released. Based on the same inventive concept, the embodiment of the present invention further provides a radio resource control apparatus, which is applied to the network side. The schematic diagram of the structure is shown in FIG. 7.
  • the method includes: a receiving module 701, configured to establish a radio resource control RRC with the user equipment on the network side.
  • a receiving module 701 configured to establish a radio resource control RRC with the user equipment on the network side.
  • the RRC connection setup complete message sent by the user equipment is received, where the RRC connection setup complete message carries the access information
  • the determining module 702 is configured to determine whether to maintain the RRC connection according to the load situation of the network side and the access information.
  • the access information received by the receiving module 701 is determined by a combination of any one or more of the following: type information of the user equipment, group information of the user equipment, priority information of the user equipment, public land of the user equipment
  • the PLMN type information of the mobile network the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, the priority information of the pre-agreed service of the user equipment and the network side, the user equipment and the network side advance
  • the type information of the agreed service model and the type of service quality requirement type of the service agreed by the user equipment and the network side are examples of the agreed service model and the type of service quality requirement type of the service agreed by the user equipment and the network side.
  • the receiving module 701 is configured to receive the access information including the following parameters: the group information of the user equipment includes a sequence number or identifier of the user equipment group; the priority information of the user equipment includes a user pre-agreed by the network side and the user equipment.
  • the priority number or identifier of the device; the PLMN type information of the user equipment includes any combination of one or more of the following: whether the user equipment is identified on its local public land mobile network HPLMN, whether the user equipment is equivalent to its HPLMN
  • the access level information of the user equipment on the network side includes the access level sequence number or identifier pre-agreed by the network side and the user equipment;
  • the type of the service pre-agreed by the user equipment and the network side Information includes classes classified by call service Information;
  • the priority information of the pre-agreed service of the user equipment and the network side includes the priority number or identifier of the service pre-agre
  • the data communication model information includes any one or more of the following combinations: data interaction periodicity, data interaction frequency, data volume size, or data interaction direction.
  • the determining module 702 may further include: a connection submodule 801, configured to: when the determination result is yes, does not trigger an RRC connection release procedure, so that the user equipment maintains an RRC connection with the network side;
  • the module 802 is configured to trigger an RRC connection release procedure to release the RRC connection when the determination result is no.
  • the radio resource control system can be integrated with an access network device, such as a base station.
  • the RRC connection setup complete message carries the access information, and the network side can load according to the network side by using the radio resource control method provided by the embodiment of the present invention.
  • the situation and the access information determine whether to maintain the RRC connection, so that the network side can more accurately grasp the information of the user equipment, so as to ensure that the network side implements precise control of the reception of the high-density, multi-service user equipment.
  • 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.
  • the computing device 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.
  • 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.

Landscapes

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

Abstract

Disclosed are a method and a device for controlling radio resources. According to the method: when an RRC connection is established between a UE and a network, the network receives an RRC connection-established message from the UE, said message carrying access information; and the network determines whether to maintain the RRC connection according to network load status and to the access information. The present invention solves the problem of admission control being unable to meet the high density of multi-service UEs due to insufficient flexibility of existing control mechanisms.

Description

无线资源控制方法及装置 技术领域 本发明涉及通信领域, 具体而言, 涉及一种无线资源控制方法及装置。 背景技术 第三代移动通信长期演进 (Long Term Evolution, 简称 LTE) 系统由演进的通用 陆地无线接入网(Evolved Universal Terrestrial Radio Access Network,简称 E-UTRAN)、 用户设备 (User Equipment, 简称 UE)、 演进的分组核心网 (Evolved Packet Core, 简 称 EPC) 组成。 其中, E-UTRAN由接入网网元的增强型基站 (e B) 组成。 e B通 过 Uu接口与终端 UE连接, 通过 S1接口与核心网网元, 如移动性管理实体(Mobility Management Entity, 简称 MME) 连接。 目前, 网络侧对于用户设备的接入有多层次的接入控制处理机制, 以保证网络侧 不会因为过量的用户设备接入而发生过载等情况。 用户设备接入网络侧需要完成如图 1所示的几个过程, 在本例中, 网络侧接入设 备设为移动性管理实体 MME: 步骤 102、 随机接入过程: 用户设备通过该过程完成和网络侧的同步; 步骤 104、 无线资源控制 (Radio Resource Control, 简称 RRC) 连接建立过程: 建立用户设备和接入网网元的信令承载; 步骤 106、 附着 (Attach)过程: 完成用户设备标识信息的获取、 鉴权过程以及安 全建立 ( Security Setup )。 在现有协议中, 网络侧为不同的呼叫类型设置了 15个接入级别 (Access Class, 简称 AC), 其中普通的呼叫均属于 AC0~9, 紧急呼叫属于 AC10, 其他高优先级的呼 叫属于 AC11~15。 网络侧为 AC0 9设置了一个控制因子, 为 AC10和 AC11 15设置 了"是否禁止"的标识, 并广播给用户设备, 以控制这些呼叫类型的随机接入行为。 在 RRC连接建立过程中, 用户设备和接入网网元的信令交互如图 2、 图 3和图 4 所示, 有连接建立、 连接拒绝和连接释放三种流程, 在图 2、 图 3及图 4的示意图中, 网络侧接入设备为基站。 如图 2所示, 连接建立包括如下流程: 步骤 202、 用户设备发起 RRC连接建立请示; 步骤 204、 基站向用户设备反馈 RRC连接建立消息; 步骤 206、 用户设备向基站发送 RRC连接建立完成消息。 如图 3所示, 连接拒绝包括如下流程: 步骤 302、 用户设备发起 RRC连接建立请示; 步骤 304、 基站向用户设备反馈 RRC连接拒绝消息。 如图 4所示, 连接释放包括如下流程: 步骤 402、 基站向用户设备发送 RRC连接释放消息。 网络侧通过这 3个流程, 就能够根据自身的数据负载能力和信令负载能力, 以及 空中接口负载能力等信息,对用户设备的 RRC连接建立请求做出"接受"、 "拒绝 "和"释 放"的判断。 考虑到用户设备发起的连接请求可能是基于不同种类的业务, 而业务的优先级可 能是不同的, 因此为了实现更灵活更高效的接纳控制, 在目前的 RRC层协议中, 要求 用户设备在 RRC连接建立请求 (RRC Connection Request) 中携带连接建立的原因信 息。 现有的连接建立原因信息 (establishment Cause) 包括下述内容: Emergency (紧急, 说明用户设备发起的是紧急呼叫); TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a radio resource control method and apparatus. A third-generation mobile communication Long Term Evolution (LTE) system consists of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a User Equipment (UE). The Evolved Packet Core (EPC) is an evolved packet core network. The E-UTRAN is composed of an enhanced base station (e B) of the access network element. The e B is connected to the terminal UE through the Uu interface, and is connected to the core network element, such as a Mobility Management Entity (MME), through the S1 interface. At present, the network side has a multi-level access control processing mechanism for the access of the user equipment, so as to ensure that the network side does not overload due to excessive user equipment access. The user equipment accesses the network side and needs to complete several processes as shown in FIG. 1. In this example, the network side access device is set as the mobility management entity MME: Step 102: Random access procedure: The user equipment completes through the process. Synchronization with the network side; Step 104: Radio Resource Control (RRC) connection establishment process: establishing a signaling bearer of the user equipment and the access network network element; Step 106, attaching (Attach) process: completing the user equipment Identification information acquisition, authentication process, and security setup (Security Setup). In the existing protocol, the network side sets 15 access levels (ACs) for different call types. The normal calls belong to AC0~9, and the emergency calls belong to AC10. Other high-priority calls belong to AC11~15. The network side sets a control factor for AC0 9 and sets the "No Forbidden" flag for AC10 and AC11 15 and broadcasts it to the user equipment to control the random access behavior of these call types. In the RRC connection establishment process, the signaling interaction between the user equipment and the access network element is as shown in FIG. 2, FIG. 3 and FIG. 4, and there are three processes of connection establishment, connection rejection and connection release, in FIG. 2 and FIG. 3 And in the schematic diagram of FIG. 4, the network side access device is a base station. As shown in FIG. 2, the connection setup includes the following steps: Step 202: The user equipment initiates an RRC connection setup request. Step 204: The base station feeds back an RRC connection setup message to the user equipment. Step 206: The user equipment sends an RRC connection setup complete message to the base station. As shown in FIG. 3, the connection rejection includes the following process: Step 302: The user equipment initiates an RRC connection establishment request. Step 304: The base station feeds back an RRC connection rejection message to the user equipment. As shown in FIG. 4, the connection release includes the following process: Step 402: The base station sends an RRC connection release message to the user equipment. Through the three processes, the network side can "accept", "reject" and "release" the RRC connection establishment request of the user equipment according to its own data load capacity and signaling load capacity, and air interface load capability. "The judgment." Considering that the connection request initiated by the user equipment may be based on different types of services, and the priorities of the services may be different, in order to implement more flexible and efficient admission control, in the current RRC layer protocol, the user equipment is required to be in the RRC. The connection establishment request (RRC Connection Request) carries the reason information of the connection establishment. The existing connection establishment information includes the following: Emergency (emergency, indicating that the user equipment initiates an emergency call);
High Priority Access (高优先接入, 说明用户设备发起的是高优先的服务类呼叫); mt-Access (说明用户设备是由于被叫而申请建立连接); mo-Signalling (说明用户设备是发起主叫信令类呼叫); mo-Data (说明用户设备是发起主叫数据类呼叫)。 需要说明的是,上述连接建立原因信息仅适用于 3GPP release 9及以前版本的用户 设备。 由于目前 RRC连接建立请求消息是在随机接入过程的 message消息中携带, 而 message 3消息的大小是受限的, 因此 RRC连接建立请求消息中已经无法再增加较多 新的信息。 随着物联网概念的发展, M2M (Machine to Machine, 机器到机器) 的通讯 (在 3GPP中称之为机器类型通讯, 即 MTC)将逐步引入整个社会。 M2M狭义上的定义是 机器到机器的通信, 广义上的定义是以机器终端智能交互为核心的、 网络化的应用与 服务。 其基于智能机器终端, 以多种通信方式为接入手段, 为客户提供的信息化解决 方案, 用于满足客户对监控、 指挥调度、 数据采集和测量等方面的信息化需求。 High Priority Access (high priority access, indicating that the user equipment initiates a high priority service class call); mt-Access (indicating that the user equipment is applying for a connection due to the called party); mo-Signalling (indicating that the user equipment is the initiator) Called signaling class); mo-Data (indicating that the user equipment is the originating caller data type call). It should be noted that the above connection establishment reason information is only applicable to user equipments of 3GPP release 9 and previous versions. Since the current RRC connection setup request message is carried in the message of the random access procedure, and the size of the message 3 message is limited, it is no longer possible to add more new information in the RRC connection setup request message. With the development of the concept of Internet of Things, M2M (Machine to Machine) communication (called machine type communication in 3GPP, or MTC) will gradually be introduced to the whole society. The definition of M2M in a narrow sense is machine-to-machine communication. Broadly defined is a networked application and service centered on intelligent interaction of machine terminals. It is based on intelligent machine terminals and uses multiple communication methods as access means to provide customers with information solutions to meet customers' information needs in monitoring, command and dispatch, data acquisition and measurement.
M2M的应用中, 业务类型非常广泛, 例如家庭抄表、 工业生产仪表自动化、水质 监控、智能交通以及资产追踪等等, M2M的应用将进入各行各业、千家万户,而 M2M 的业务类型也将是成千上万, 对网络侧和对运营商的 QoS (服务质量, Quality of Service)要求也将是多种多样的。 M2M的用户设备的数量也将会远远超过目前手机终 端, 这就对当前乃至未来的无线网络构成了业务负载的巨大压力。 由于 M2M用户设 备数量巨大, 因此目前 3Gpp提出了按照分组 (Group)方式对用户设备进行管理的概 念。 在 M2M应用的背景下, 如何保护网络, 如何防止网络出现过载, 目前已成为首 要解决的一个问题。 当前的协议中, 用户设备可以在随机接入在和网络建立连接, 并完成附着的过程 中, 接入网网元可以对随机接入过程进行接入控制, 也可以在 RRC 层对用户设备的 RRC连接建立请求进行控制, 但目前的控制机制的灵活度已经不能满足对高密度、 多 业务的用户设备的接纳控制了。 例如: 目前运营商的统计结果显示, 无线通信中的数据业务 (例如上网, 视频呼 口 , FTP (File Transfer Protocol, 文件传送协议)下载等) 的负载已经超过了语音业务 的负载。当网络面临过载压力时, 比较合适的做法是对数据业务进行一定的接纳限制, 而保证语音业务的正常服务, 因为通常从运营商角度来说, 语音业务是网络运营的基 础, 但是按照目前的协议标准, 用户设备发起语音呼叫和数据业务呼叫时, 在 RRC连 接建立请求中的连接建立原因信息都是同样的数据模型 mo-Data, 网络侧无法区分是 语音还是数据业务, 因此无法进行灵活的接纳控制。 此外, 不同的 M2M的应用具有不同的业务模型, 业务模型是指用户设备和网络 侧交互数据时的数据传输模型, 表述业务模型的要素包括: 数据交互周期性、 数据交 互频度、 数据大小、 数据交互方向 (指以上行数据为主、 或以下行数据为主、 或上下 行流量相近)。 以智能电表为例,有的电力公司要求每台智能电表每 5分钟上报一次抄 表数据, 有的电力公司要求每台智能电表每 1小时上报一次抄表数据, 有的电力公司 甚至只要求智能电表每天上报一次抄表数据, 每次抄表数据的流量较小, 这就构成了 3 种不同的业务模型, 可以分别称为高频度周期性小数据上报、 低频度周期性小数据 上报、 极低频度周期性小数据上报。 又例如普通的语音业务, 可称为极高频度周期性 小数据交互模型。 又例如上网业务 (通常几十秒点击一次网页, 以下行数据为主, 且 数据流量较大),可称为中频度非周期性大数据下传模型。这些不同的业务模型很明显 对于网络的压力是不同的, 而目前的机制是无法区分这些业务的模型的。 不同的业务还具有不同的 QoS要求,与接纳控制比较相关的 QoS要求包括:接入 延迟的容忍度, 例如有的业务对接入延迟非常敏感 (例如火警、 安防、 医疗监护等业 务), 有的业务对接入延迟敏感度较低(例如抄表), 目前的机制是无法区分这些不同。 不同的业务或者用户设备还具有不同的优先级, 例如和金融、 安防、 医疗相关的 业务的优先级应当高于普通的业务, 而目前的机制无法区分。 上述缺陷在 M2M广泛应用后, 将变得更加严重。 针对相关技术中目前的控制机制的灵活度已经不能满足对高密度、 多业务的用户 设备的接纳控制的问题, 目前尚未提出有效的解决方案。 发明内容 本发明的主要目的在于提供一种无线资源控制方法及装置, 以至少解决上述目前 的控制机制的灵活度已经不能满足对高密度、 多业务的用户设备的接纳控制的问题。 根据本发明的一个方面, 提供了一种无线资源控制方法, 包括: 在用户设备与网 络侧之间建立 RRC连接时, 所述网络侧接收到用户设备发送的 RRC连接建立完成消 息, 其中, 所述 RRC连接建立完成消息中携带有接入信息; 以及, 所述网络侧根据所 述网络侧的负载情况以及所述接入信息确定是否维持所述 RRC连接。 较优的, 所述接入信息包括下列任意一项或多项的组合: 所述用户设备的类型信 息、 所述用户设备的分组信息、 所述用户设备的优先级信息、 所述用户设备的 PLMN 类型信息、 所述用户设备在所述网络侧的接入级别信息、 所述用户设备与所述网络侧 预先约定的业务的类型信息、 所述用户设备与所述网络侧预先约定的业务的优先级信 息、 所述用户设备与所述网络侧预先约定的业务模型的类型信息以及所述用户设备与 所述网络侧预先约定的业务的服务质量要求类型信息。 较优的, 所述用户设备的分组信息包括所述用户设备分组的序号或标识; 所述用 户设备的优先级信息包括所述网络侧和所述用户设备预先约定的所述用户设备的优先 级序号或标识; 所述用户设备的 PLMN类型信息包括下列任意一项或多项的组合: 所 述用户设备是否在其 HPLMN上的标识信息、 所述用户设备是否在与其 HPLMN等效 的 PLMN上的标识信息、所述用户设备是否在其用户身份模块或者全球用户身份模块 所包含的优选 PLMN列表中的 PLMN上的标识信息、所述用户设备是否是漫游的用户 设备的标识信息、 所述用户设备的 HPLMN 的标识信息以及所述用户设备的等效 HPLMN 的标识信息; 所述用户设备在所述网络侧的接入级别信息包括所述网络侧和 所述用户设备预先约定的接入级别序号或标识; 所述用户设备与所述网络侧预先约定 的业务的类型信息包括按呼叫业务分类的类型信息; 所述用户设备与所述网络侧预先 约定的业务的优先级信息包括所述网络侧和所述用户设备预先约定的业务的优先级序 号或标识; 所述用户设备与所述网络侧预先约定的业务模型的类型信息包括业务的数 据通讯模型信息, 其中, 所述数据通讯模型信息包括下述任意一项或多项的组合: 数 据交互周期性、 数据交互频度、 数据量大小或数据交互方向。 较优的, 所述在用户设备与网络侧之间建立 RRC连接之前, 还包括: 所述用户设 备根据自身的类型以及即将建立的业务的业务类型确定所述接入信息, 并将所述接入 信息添加到所述 RRC连接建立完成消息中。 较优的,所述网络侧根据所述接入信息确定是否维持所述 RRC连接之后,还包括: 当确定结果为是时, 不触发 RRC连接释放流程,令所述用户设备与所述网络侧维持所 述 RRC连接; 当确定结果为否时, 触发 RRC连接释放流程, 释放所述 RRC连接。 根据本发明的另一方面, 提供了一种无线资源控制装置, 应用于网络侧, 包括: 接收模块, 设置为在所述网络侧与用户设备建立 RRC 连接时, 收到用户设备发送的 RRC连接建立完成消息, 其中, 所述 RRC连接建立完成消息中携带有接入信息; 确 定模块, 设置为根据所述网络侧的负载情况以及所述接入信息确定是否维持所述 RRC 连接。 较优的, 所述接收模块接收的接入信息由下列任意一项或多项的组合确定: 所述 用户设备的类型信息、 所述用户设备的分组信息、 所述用户设备的优先级信息、 所述 用户设备的 PLMN类型信息、 所述用户设备在所述网络侧的接入级别信息、 所述用户 设备与所述网络侧预先约定的业务的类型信息、 所述用户设备与所述网络侧预先约定 的业务的优先级信息、 所述用户设备与所述网络侧预先约定的业务模型的类型信息以 及所述用户设备与所述网络侧预先约定的业务的服务质量要求类型信息。 较优的, 所述接收模块还设置为接收包含如下参数的接入信息: 所述用户设备的 分组信息包括所述用户设备分组的序号或标识; 所述用户设备的优先级信息包括所述 网络侧和所述用户设备预先约定的所述用户设备的优先级序号或标识; 所述用户设备 的 PLMN类型信息包括下列任意一项或多项的组合: 所述用户设备是否在其 HPLMN 上的标识信息、 所述用户设备是否在与其 HPLMN等效的 PLMN上的标识信息、 所述 用户设备是否在其用户身份模块或者全球用户身份模块所包含的优选 PLMN列表中的 PLMN上的标识信息、 所述用户设备是否是漫游的用户设备的标识信息、 所述用户设 备的 HPLMN的标识信息以及所述用户设备的等效 HPLMN的标识信息; 所述用户设 备在所述网络侧的接入级别信息包括所述网络侧和所述用户设备预先约定的接入级别 序号或标识; 所述用户设备与所述网络侧预先约定的业务的类型信息包括按呼叫业务 分类的类型信息; 所述用户设备与所述网络侧预先约定的业务的优先级信息包括所述 网络侧和所述用户设备预先约定的业务的优先级序号或标识; 所述用户设备与所述网 络侧预先约定的业务模型的类型信息包括业务的数据通讯模型信息, 其中, 所述数据 通讯模型信息包括下述任意一项或多项的组合: 数据交互周期性、 数据交互频度、 数 据量大小或数据交互方向。 较优的, 所述确定模块还包括: 连接子模块, 设置为当确定结果为是时, 不触发 RRC连接释放流程, 令所述用户设备与所述网络侧维持所述 RRC连接; 释放子模块, 设置为当确定结果为否时, 触发 RRC连接释放流程, 释放所述 RRC连接。 较优的, 所述无线资源控制系统集成于接入网设备。 采用本发明实施例提供的无线资源控制方法,在 RRC连接建立完成消息中携带接 入信息, 网络侧能够根据网络侧的负载情况及接入信息确定是否维持 RRC连接, 使得 网络侧能够更准确的掌握用户设备的信息, 以保证网络侧实现了对高密度、 多业务的 用户设备的接纳的精确控制。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中: 图 1是根据相关技术的用户设备接入网络侧的流程图; 图 2根据相关技术的用户设备和接入网网元的连接建立流程的示意图; 图 3根据相关技术的用户设备和接入网网元的连接拒绝流程的示意图; 图 4根据相关技术的用户设备和接入网网元的连接释放流程的示意图; 图 5是根据本发明实施例的无线资源控制方法的处理流程图; 图 6是根据本发明实施例的用户设备接入网络侧,申请 RRC连接建立的处理流程 图; 图 7是根据本发明实施例的无线资源控制装置的结构示意图; 图 8是根据本发明实施例的确定模块的结构示意图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 相关技术中提到, 目前的控制机制的灵活度已经不能满足对高密度、 多业务的用 户设备的接纳控制, 为解决上述技术问题, 本发明实施例提供了一种无线资源控制方 法, 处理流程如图 5所示, 包括: 步骤 502、 在用户设备与网络侧之间建立无线资源控制 RRC连接时, 网络侧接收 到用户设备发送的 RRC连接建立完成消息, 其中, RRC连接建立完成消息中携带有 接入信息; 步骤 504、 网络侧根据网络侧的负载情况以及接入信息确定是否维持 RRC连接。 采用本发明实施例提供的无线资源控制方法,在 RRC连接建立完成消息中携带接 入信息, 网络侧能够根据网络侧的负载情况及接入信息确定是否维持 RRC连接, 使得 网络侧能够更准确的掌握用户设备的信息, 以保证网络侧实现了对高密度、 多业务的 用户设备的接纳的精确控制。 实施时, 接入信息可以包括下列任意一项或多项的组合: 用户设备的类型信息、 用户设备的分组信息、 用户设备的优先级信息、 用户设备的公共陆地移动网 (Public Land Mobile Network, 简称 PLMN) 类型信息、 用户设备在网络侧的接入级别信息、 用户设备与网络侧预先约定的业务的类型信息、 用户设备与网络侧预先约定的业务的 优先级信息、 用户设备与网络侧预先约定的业务模型的类型信息以及用户设备与网络 侧预先约定的业务的服务质量要求类型信息。 较优的, 接入信息的每个选项可以包括多个具体的参数, 例如, 用户设备的分组 信息可以包括用户设备分组的序号或标识; 用户设备的优先级信息可以包括网络侧和 用户设备预先约定的用户设备的优先级序号或标识; 用户设备的 PLMN类型信息可以 包括下列任意一项或多项的组合: 用户设备是否在其本地公共陆地移动网 (Home Public Land Mobile Network, HPLMN) 上的标识信息、 用户设备是否在与其 HPLMN 等效的 PLMN上的标识信息、用户设备是否在其用户身份模块或者全球用户身份模块 所包含的优选 PLMN列表中的 PLMN上的标识信息、用户设备是否是漫游的用户设备 的标识信息、 用户设备的 HPLMN的标识信息以及用户设备的等效 HPLMN的标识信 息; 用户设备在网络侧的接入级别信息可以包括网络侧和用户设备预先约定的接入级 别序号或标识; 用户设备与网络侧预先约定的业务的类型信息可以包括按呼叫业务分 类的类型信息; 用户设备与网络侧预先约定的业务的优先级信息可以包括所述网络侧 和所述用户设备预先约定的业务的优先级序号或标识; 用户设备与网络侧预先约定的 业务模型的类型信息可以包括业务的数据通讯模型信息, 其中, 数据通讯模型信息可 以包括任意一项或多项的组合: 数据交互周期性、 数据交互频度、 数据量大小或数据 交互方向。 下面对各种接入信息进行具体的说明, 在下文的论述中, 列举了各项接入信息的 具体实例。 呼叫业务类型信息是指按呼叫业务分类的信息, 包括以下的一种或者多种: 主叫 或者被叫的语音呼叫、 主叫或者被叫的视频流呼叫、 主叫或者被叫的互动语音呼叫、 主叫或者被叫的数据呼叫、 主叫或者被叫的信令业务等。 其中, 数据呼叫可以只有简 单的一类, 也可以进一步分成更细的种类, 例如: 超文本传送协议(HyperText Transfer Protocol, Http) 上网业务、 FTP下载业务、 抄表业务、 监控业务、 智能交通业务、 资 产追踪业务等。 而用户设备的类型信息是指按用户设备分类的信息, 包括以下的一种或者多种: H2H用户设备, M2M用户设备, 其他类型用户设备。 用户设备的分组信息是指用户设备分组 (Group) 的标识, 包括: 用户设备分组 (Group) 的序号或者标识。 根据目前分组 (Group) 的机制, 分组标识 Group-RNTI (Radio Network Temporary Indicator, 无线网络临时标识) 已经在 3gpp会议上提出, 因此用户设备的分组信息可以直接使用 Group-RNTI,也可以使用和网络侧预先约定的 一个序号, 网络侧事先建立该序号和分组的一一对应关系。 用户设备的优先级信息是指网络侧和用户设备事先约定的用户设备的优先级, 包 括: 优先级的序号、 或者优先级标识。 优先级可以是 1级或者多级, 可以高于现有的 H2H (Human To Human, 即指人到人的通信) 设备, 也可以低于现有的 H2H设备。 例如: 以现有的 H2H设备为基准 (下述的" H2H设备"指现有协议中已经包括的 RRC 连接建立原因), 可以包括下面的种类: 简单的 1级: H2H设备、 低优先级设备 (相对于 H2H设备); 或者 In the application of M2M, the business types are very wide, such as household meter reading, industrial production instrumentation automation, water quality monitoring, intelligent transportation and asset tracking, etc. M2M applications will enter all walks of life, thousands of households, and M2M business types also There will be tens of thousands, and the QoS (Quality of Service) requirements for the network side and for operators will also be varied. The number of M2M user devices will also far exceed the current mobile phone terminals, which poses a huge pressure on the current and future wireless networks. Due to the huge number of M2M user equipments, 3Gpp currently proposes the concept of managing user equipments in a group manner. In the context of M2M applications, how to protect the network and how to prevent network overload has become a primary problem. In the current protocol, the user equipment may perform access control on the random access procedure or the user equipment in the RRC layer during the process of establishing a connection with the network and completing the attachment. The RRC connection establishment request is controlled, but the flexibility of the current control mechanism cannot meet the admission control of the high-density, multi-service user equipment. For example, the current statistics of operators show that the load of data services (such as Internet access, video call port, FTP (File Transfer Protocol) download) in wireless communication has exceeded the load of voice services. When the network is under overload pressure, it is more appropriate to impose certain acceptance restrictions on the data service to ensure the normal service of the voice service, because usually from the perspective of the operator, the voice service is the basis of the network operation, but according to the current Protocol standard, when the user equipment initiates a voice call and a data service call, the connection establishment cause information in the RRC connection establishment request is the same data model mo-Data, and the network side cannot distinguish between voice or data service, and thus cannot be flexible. Admission control. In addition, different M2M applications have different business models. The business model refers to the data transmission model when the user equipment and the network side exchange data. The elements of the business model include: data interaction periodicity, data interaction frequency, data size, Data interaction direction (refer to the above line data, or the following line data, or up and down The traffic is similar). Take smart meters as an example. Some power companies require each smart meter to report meter reading data every 5 minutes. Some power companies require each smart meter to report meter reading data every hour. Some power companies even only require intelligence. The meter reports the meter reading data once a day, and the traffic of each meter reading data is small. This constitutes three different business models, which can be called high frequency periodic small data reporting, low frequency periodic small data reporting, Very low frequency periodic small data is reported. Another example is a normal voice service, which can be called an extremely high frequency periodic small data interaction model. For example, the Internet service (usually clicking on a web page for several tens of seconds, the following line data is dominant, and the data traffic is large) may be referred to as an intermediate frequency non-periodic big data downlink model. These different business models clearly have different pressures on the network, and the current mechanism is unable to distinguish the models of these services. Different services also have different QoS requirements. The QoS requirements related to admission control include: access delay tolerance. For example, some services are very sensitive to access delay (such as fire alarm, security, medical monitoring, etc.). The business is less sensitive to access delays (such as meter reading), and the current mechanism is unable to distinguish between these differences. Different services or user equipments also have different priorities. For example, financial, security, and medical-related services should have higher priority than ordinary services, and the current mechanism cannot be distinguished. The above defects will become more serious after the widespread use of M2M. The flexibility of the current control mechanism in the related art has been unable to meet the problem of admission control for high-density, multi-service user equipment, and no effective solution has been proposed yet. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a radio resource control method and apparatus to solve at least the problem that the flexibility of the current control mechanism cannot meet the admission control of a high-density, multi-service user equipment. According to an aspect of the present invention, a radio resource control method is provided, including: when an RRC connection is established between a user equipment and a network side, the network side receives an RRC connection setup complete message sent by the user equipment, where The RRC connection setup complete message carries the access information; and the network side determines whether to maintain the RRC connection according to the load situation of the network side and the access information. Preferably, the access information includes any one or more of the following combinations: the type information of the user equipment, the group information of the user equipment, the priority information of the user equipment, and the user equipment. The PLMN type information, the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, and the pre-agreed service of the user equipment and the network side The priority information, the type information of the service model pre-agreed by the user equipment and the network side, and the service quality requirement type information of the service that the user equipment and the network side pre-agreed. Preferably, the grouping information of the user equipment includes a sequence number or an identifier of the user equipment group; the priority information of the user equipment includes a priority of the user equipment pre-agreed by the network side and the user equipment. The serial number or the identifier; the PLMN type information of the user equipment includes any one or more of the following combinations: whether the user equipment is identification information on its HPLMN, whether the user equipment is on a PLMN equivalent to its HPLMN. The identification information, the identification information of the user equipment on the PLMN in the preferred PLMN list included in the user identity module or the global user identity module, the identification information of the user equipment that is the roaming user equipment, the user equipment The identification information of the HPLMN and the identifier information of the equivalent HPLMN of the user equipment; the access level information of the user equipment on the network side includes an access level sequence number pre-agreed by the network side and the user equipment or Identifying; the type information of the service pre-agreed by the user equipment and the network side, including the classification by call service The priority information of the pre-agreed service of the user equipment and the network side includes a priority sequence number or identifier of the service pre-agreed by the network side and the user equipment; the user equipment and the network The type information of the pre-agreed business model includes the data communication model information of the service, where the data communication model information includes any one or more of the following combinations: data interaction periodicity, data interaction frequency, data volume size Or the direction of data interaction. Preferably, before the establishment of the RRC connection between the user equipment and the network side, the method further includes: determining, by the user equipment, the access information according to the type of the user equipment and the service type of the service to be established, and connecting the The incoming information is added to the RRC Connection Setup Complete message. Preferably, the network side determines whether to maintain the RRC connection according to the access information, and further includes: when the determination result is yes, the RRC connection release procedure is not triggered, and the user equipment is connected to the network side. Maintaining the RRC connection; when the determination result is no, triggering an RRC connection release procedure, releasing the RRC connection. According to another aspect of the present invention, a radio resource control apparatus is provided, which is applied to a network side, and includes: a receiving module, configured to receive an RRC connection sent by a user equipment when the network side establishes an RRC connection with a user equipment. a setup completion message, where the RRC connection setup complete message carries the access information, and the determining module is configured to determine whether to maintain the RRC connection according to the load situation of the network side and the access information. Preferably, the access information received by the receiving module is determined by a combination of any one or more of the following: type information of the user equipment, group information of the user equipment, priority information of the user equipment, The PLMN type information of the user equipment, the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, the user equipment and the network side The priority information of the pre-agreed service, the type information of the user equipment and the pre-agreed service model of the network side, and the service quality requirement type information of the service that the user equipment and the network side pre-agreed. Preferably, the receiving module is further configured to receive the access information that includes the following parameters: the packet information of the user equipment includes a sequence number or identifier of the user equipment group; and the priority information of the user equipment includes the network. And a priority sequence number or identifier of the user equipment that is pre-agreed by the user equipment; the PLMN type information of the user equipment includes a combination of any one or more of the following: whether the user equipment is an identifier on the HPLMN Information, whether the user equipment is in the identity information on the PLMN equivalent to its HPLMN, whether the user equipment is in its user identity module or the identity information on the PLMN in the preferred PLMN list included in the global subscriber identity module, Whether the user equipment is the identification information of the roaming user equipment, the identification information of the HPLMN of the user equipment, and the identifier information of the equivalent HPLMN of the user equipment; the access level information of the user equipment on the network side includes An access level sequence number or identifier pre-agreed by the network side and the user equipment; the user equipment and the The type information of the service that is pre-agreed by the network side includes the type information classified by the call service; the priority information of the service that is pre-agreed by the user equipment and the network side includes the service that is pre-agreed by the network side and the user equipment. The priority serial number or the identifier; the type information of the service model pre-agreed by the user equipment and the network side includes the data communication model information of the service, where the data communication model information includes any one or more of the following combinations : Data interaction periodicity, data interaction frequency, data volume size, or data interaction direction. Preferably, the determining module further includes: a connection submodule, configured to: when the determination result is yes, does not trigger an RRC connection release procedure, so that the user equipment maintains the RRC connection with the network side; releasing the submodule And setting, when the determination result is no, triggering an RRC connection release procedure, releasing the RRC connection. Preferably, the radio resource control system is integrated in the access network device. The RRC connection setup complete message carries the access information in the RRC connection setup complete message, and the network side can determine whether to maintain the RRC connection according to the network side load condition and the access information, so that the network side can be more accurate. Master the information of the user equipment to ensure that the network side implements precise control of the reception of high-density, multi-service user equipment. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the accompanying drawings: FIG. 1 is a flowchart of a user equipment accessing a network side according to the related art; FIG. 2 is a schematic diagram of a connection establishment process of a user equipment and an access network network element according to the related art; 3 is a schematic diagram of a connection denial procedure of a user equipment and an access network element according to the related art; FIG. 4 is a schematic diagram of a connection release procedure of a user equipment and an access network element according to the related art; FIG. 5 is a schematic diagram of a connection according to an embodiment of the present invention; FIG. 6 is a flowchart of a process for requesting an RRC connection establishment by a user equipment accessing a network side according to an embodiment of the present invention; FIG. 7 is a structure of a radio resource control apparatus according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of a determining module 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. It is mentioned in the related art that the flexibility of the current control mechanism cannot meet the admission control of the high-density, multi-service user equipment. To solve the above technical problem, the embodiment of the present invention provides a radio resource control method, and the processing procedure. As shown in FIG. 5, the method includes the following steps: Step 502: When establishing a radio resource control RRC connection between the user equipment and the network side, the network side receives the RRC connection setup complete message sent by the user equipment, where the RRC connection setup complete message is carried. There is access information; Step 504: The network side determines whether to maintain the RRC connection according to the load condition of the network side and the access information. The RRC connection setup complete message carries the access information in the RRC connection setup complete message, and the network side can determine whether to maintain the RRC connection according to the network side load condition and the access information, so that the network side can be more accurate. Master the information of the user equipment to ensure that the network side implements precise control of the reception of high-density, multi-service user equipment. In implementation, the access information may include any one or more of the following combinations: type information of the user equipment, group information of the user equipment, priority information of the user equipment, and public land mobile network of the user equipment (Public Land Mobile Network, PLMN) type information, access level information of the user equipment on the network side, type information of the service pre-agreed by the user equipment and the network side, priority information of the pre-agreed service of the user equipment and the network side, user equipment and network side advance The type information of the agreed service model and the type of service quality requirement type of the service agreed by the user equipment and the network side. Preferably, each option of the access information may include a plurality of specific parameters, for example, the group information of the user equipment may include a sequence number or identifier of the user equipment group; the priority information of the user equipment may include the network side and the user equipment in advance. The priority sequence number or identifier of the agreed user equipment; the PLMN type information of the user equipment may include any one or more of the following combinations: whether the user equipment is on its local Public Land Mobile Network (HPLMN) Identification information, whether the user equipment is on the PLMN equivalent to its HPLMN, whether the user equipment is in its user identity module or the identification information on the PLMN in the preferred PLMN list included in the global subscriber identity module, whether the user equipment is roaming The identification information of the user equipment, the identification information of the HPLMN of the user equipment, and the identifier information of the equivalent HPLMN of the user equipment; the access level information of the user equipment on the network side may include the access level sequence number pre-agreed by the network side and the user equipment or Identification; user equipment and network side pre-agreed The type information of the service may include the type information classified according to the call service; the priority information of the service pre-agreed by the user equipment and the network side may include the priority number or identifier of the service pre-agreed by the network side and the user equipment; The type information of the service model pre-agreed by the device and the network side may include data communication model information of the service, where the data communication model information may include any one or more combinations: data interaction periodicity, data interaction frequency, data volume Size or data interaction direction. The various access information will be specifically described below. In the following discussion, specific examples of various access information are listed. The call service type information refers to information classified by call service, including one or more of the following: a voice call of the calling party or the called party, a video stream call of the calling party or the called party, an interactive voice call of the calling party or the called party. , the calling or called data call, the calling or called signaling service, etc. Among them, the data call can be only a simple one, or can be further divided into more detailed categories, such as: HyperText Transfer Protocol (Http) Internet service, FTP download service, meter reading service, monitoring service, intelligent traffic service , asset tracking business, etc. The type information of the user equipment refers to information classified by the user equipment, including one or more of the following: H2H user equipment, M2M user equipment, and other types of user equipment. The group information of the user equipment refers to the identifier of the user equipment group, including: the serial number or identifier of the user equipment group (Group). According to the mechanism of the current group, the Group-RNTI (Radio Network Temporary Indicator) has been proposed at the 3gpp conference. Therefore, the group information of the user equipment can be directly used by the Group-RNTI, and the network can also be used. A serial number pre-agreed by the side, and the network side establishes a one-to-one correspondence between the serial number and the group in advance. The priority information of the user equipment refers to the priority of the user equipment agreed by the network side and the user equipment in advance, including: the priority number or the priority identifier. The priority can be 1 or more, which can be higher than the existing H2H (Human To Human) device, or lower than the existing H2H device. For example: Based on the existing H2H device (the "H2H device" refers to the RRC connection establishment reason already included in the existing protocol), it can include the following types: Simple level 1: H2H device, low priority device (relative to H2H equipment); or
2级: 高优先级设备、 H2H设备、 低优先级设备; 或者 多级: H2H设备、 低优先 1级设备、 低优先 2级设备、 ...、 低优先 N级设备 (N 是正整数); 另一种多级: 高优先 1级设备、 高优先 2级设备、 ...、 高优先 M级设备、 H2H 设备、 低优先 1级设备、 低优先 2级设备、 ...、 低优先 N级设备(M和 N是正整数); 具体的设备类型和设备优先级之间的对应关系由网络侧和用户设备预先约定。 例 如 H2H设备属于普通优先级, M2M设备属于低优先级。 业务的优先级信息是指网络侧和用户设备事先约定的业务优先级, 包括: 优先级 的序号、 或者优先级标识。 由于智能手机、 M2M设备的引入, 无线通讯的业务种类大 大增加, 现有协议中的 RRC连接建立原因包括: Emergency, 说明用户设备发起的是 紧急呼叫; highPriorityAccess , 说明用户设备发起的是高优先的服务类呼叫; mt- Access, 说明用户设备是由于被叫而申请建立连接; mo-Signalling, 说明用户设备 是发起主叫信令类呼叫; mo-Data, 说明用户设备是发起主叫数据类呼叫。 除此之外, 还可以引入新的业务优先级, 例如 (下述的 "H2H业务"指现有协议中 已经包括的 RRC连接建立原因), 可以包括下面种类: 简单的 1级: H2H业务、 低优先级业务 (相对于 H2H设备); 或者 Level 2: High priority equipment, H2H equipment, low priority equipment; or multiple levels: H2H equipment, low priority level 1 equipment, low priority level 2 equipment, ..., low priority N level equipment (N is a positive integer); Another multi-level: high priority level 1 equipment, high priority level 2 equipment, ..., high priority M level equipment, H2H equipment, low priority level 1 equipment, low priority level 2 equipment, ..., low priority N Level device (M and N are positive integers); The correspondence between the specific device type and device priority is pre-agreed by the network side and the user equipment. For example, an H2H device belongs to a common priority, and an M2M device belongs to a low priority. The priority information of the service refers to the service priority agreed by the network side and the user equipment in advance, including: the priority sequence number or the priority identifier. Due to the introduction of smart phones and M2M devices, the types of wireless communication services are greatly increased. The reasons for the establishment of RRC connections in the existing protocols include: Emergency, indicating that the user equipment initiates an emergency call; highPriorityAccess indicates that the user equipment initiates a high priority. Service-type call; mt-Access, indicating that the user equipment is applying for establishing a connection due to the called party; mo-Signalling, indicating that the user equipment is a caller signaling type call; mo-Data, indicating that the user equipment is calling the calling data type call . In addition, new service priorities can be introduced, for example ("H2H service" refers to the RRC connection establishment reason already included in the existing protocol), and can include the following types: Simple level 1: H2H service, Low priority service (as opposed to H2H equipment); or
2级: 高优先级业务、 H2H业务、 低优先级业务; 或者 多级: H2H业务、 低优先 1级业务、 低优先 2级业务、 ...、 低优先 N级业务 (N 是正整数); 另一种多级: 高优先 1级业务、 高优先 2级业务、 ...、 高优先 M级业务、 H2H 业务、 低优先 1级业务、 低优先 2级业务、 ...、 低优先 N级业务(M和 N是正整数); 具体的业务类型和业务优先级之间的对应关系由网络侧和用户设备预先约定。 例 如: 对接入时间容忍度较高的业务 (例如智能电表) 属于较低的业务优先级, 而对接 入时间容忍度较低的业务 (例如移动 POS机、 报警类 M2M设备等) 属于较高的业务 优先级。 还可以有其他的业务类型和业务优先级之间的对应关系设置,这里不再一一举例。 业务模型的类型信息是指业务的数据通讯模型, 包括下述特征的一种或多种的组 合: 数据交互周期性(是否是周期性数据交互)、 数据交互频度、 数据量大小、 数据交 互方向 (指以上行数据为主、 或以下行数据为主、 或上下行流量相近)。 例如, 只包括 简单的一种特征的信息的业务模型包括: 小数据业务模型、 或者高频度业务模型、 或 者周期性业务模型等等; 包括多种特征的信息的业务模型包括: 周期性小数据业务模 型、 低频度周期性小数据上报、 极低频度周期性小数据上报、 极高频度周期性小数据 交互模型、 中频度非周期性大数据下传模型等等。 在实施时, 业务类型和业务模型之 间的对应关系通常由网络侧和用户设备预先约定。 在本发明实施例中, PLMN类型信息是网络侧和用户设备事先约定的 PLMN类型 信息, 包括以下的一种或多种: 用户设备是否在其 HPLMN上的标识信息、 用户设备 是否在其等效的 HPLMN上的标识信息、 用户设备是否在其 SIM ( Subscriber Identity Module, 用户身份模块) 或者 USIM (Universal Subscriber Identity Module, 全球用户 身份模块)所包含的优选 PLMN列表中的某个 PLMN上的标识信息、是否是漫游的用 户设备的标识信息、 用户设备的 HPLMN的标识信息或者用户设备的等效 HPLMN的 标识信息。 用户设备在网络侧的接入级别 (Access Class)信息是指网络侧和用户设备事先约 定的接入级别, 包括: 接入级别序号、 或者接入级别标识; 例如: Access Class N (N 为大于等于 0的正数)。 业务的 QoS要求类型信息包括各种 QoS要求的一种或多种的组合, 上述的 QoS 要求例如: 接入延迟的容忍度、 保证的流量、 容许的误码率等。 以接入延迟为例, 可 以设置为: 简单的 2级: 对接入延迟敏感、 对接入延迟不敏感; 多级: 接入延迟敏感度高、 接入延迟敏感度中、 接入延迟敏感度低; 也可以是多种 QoS要求的组合, 例如: 接入延迟敏感度高 +低保证流量 +低误码率要求; 或者 接入延迟敏感度中 +高保证流量 +低误码率要求。 在实施中, QoS要求也可以分为比列举的实例更细的级数, 根据具体情况而定。 在一个实施例中,可以利用列表清楚地表示 RRC连接的接入信息, 列表可以是上 述的各种特征信息一种或多种, 或者一种或者多种的合并。 例如, 表 1是 RRC连接接入性质信息列表的一个实施例(是优先级信息、业务类 型信息和用户设备类型信息的组合): 表 1 Level 2: High-priority service, H2H service, low-priority service; or multi-level: H2H service, low priority level 1 service, low priority level 2 service, ..., low priority N level service (N is a positive integer); Another multi-level: high priority level 1 service, high priority level 2 service, ..., high priority M level service, H2H service, low priority level 1 service, low priority level 2 service, ..., low priority N Class service (M and N are positive integers); The correspondence between the specific service type and the service priority is pre-agreed by the network side and the user equipment. For example, services with higher access time tolerance (such as smart meters) belong to lower service priorities, while services with lower access time tolerance (such as mobile POS machines, alarm M2M devices, etc.) are High business priority. There may also be correspondences between other service types and service priorities, which are not exemplified herein. The type information of the business model refers to the data communication model of the service, including one or more combinations of the following features: data interaction periodicity (whether it is periodic data interaction), data interaction frequency, data volume size, data interaction Direction (refer to the above data, or the following data, or the upstream and downstream traffic are similar). For example, a business model including only a simple feature information includes: a small data service model, or a high frequency business model, or a periodic business model, etc.; a business model including information of a plurality of characteristics includes: Data service model, low-frequency periodic small data reporting, very low-frequency periodic small data reporting, extremely high-frequency periodic small data interaction model, medium-frequency aperiodic big data downlink model, and so on. In implementation, the correspondence between the service type and the service model is usually pre-agreed by the network side and the user equipment. In the embodiment of the present invention, the PLMN type information is the PLMN type information agreed by the network side and the user equipment in advance, including one or more of the following: whether the user equipment is on the HPLMN, whether the user equipment is in its equivalent. Identification information on the HPLMN, whether the user equipment is in the identification information of a PLMN in the preferred PLMN list included in its SIM (Subscriber Identity Module) or USIM (Universal Subscriber Identity Module) Whether it is the identification information of the roaming user equipment, the identification information of the HPLMN of the user equipment, or the identification information of the equivalent HPLMN of the user equipment. The Access Class information of the user equipment on the network side refers to the access level agreed by the network side and the user equipment in advance, including: the access level sequence number or the access level identifier; for example: Access Class N (N is greater than A positive number equal to 0). The QoS requirement type information of the service includes a combination of one or more of various QoS requirements, such as: access delay tolerance, guaranteed traffic, allowable bit error rate, and the like. Taking the access delay as an example, it can be set to: Simple Level 2: Sensitive to access delay and insensitive to access delay; Multi-level: High access delay sensitivity, access delay sensitivity, and access delay sensitivity Low; can also be a combination of multiple QoS requirements, for example: High access delay sensitivity + low guaranteed traffic + low error rate requirements; or access delay sensitivity + high guaranteed traffic + low error rate requirements. In implementation, the QoS requirements can also be divided into smaller levels than the enumerated examples, depending on the circumstances. In one embodiment, the list may clearly indicate the access information of the RRC connection, and the list may be one or more of the various feature information described above, or a combination of one or more. For example, Table 1 is an embodiment of the RRC connection access nature information list (which is a combination of priority information, service type information, and user equipment type information): Table 1
Figure imgf000013_0001
Figure imgf000013_0001
表 2是 RRC连接接入性质信息列表的另一个实施例 (是业务模型信息和 QoS要 求信息的组合): 表 2 Table 2 is another embodiment of the RRC Connection Access Property Information List (which is a combination of service model information and QoS requirement information): Table 2
Figure imgf000013_0002
在实际应用中,还可以有其他的组合方式构成 RRC连接的接入信息列表,接入信 息列表中包含的接入信息也可能多于或少于七项, 例如, 一项、 两项、 三项、 十项或 者任意自然数项。 实施时, 步骤 502中, 用户设备与网络侧之间建立 RRC连接, 在步骤 502实施之 前, 还可以包括: 用户设备根据自身的类型以及即将建立的业务的业务类型确定接入信息, 并将接 入信息添加到所述 RRC连接建立完成消息中。 实施时, 网络侧根据接入信息确定是否维持 RRC连接之后,可以选择不同的执行 结果, 例如, 当确定结果为是时, 网络侧可以选择不触发 RRC连接释放流程, 令用户 设备与网络侧维持 RRC连接; 或者, 当确定结果为否时, 网络侧可以选择触发 RRC 连接释放流程, 释放 RRC连接。 为使本发明实施例的目的、 技术方案和优点更加清楚明白, 以下举实施例并参照 附图, 对本发明实施例进一步详细说明。 本发明实施例适用于 LTE系统或者 UMTS (Universal Mobile Telecommunications System, 环球移动通信系统), 在本例中, 用户设备接入网络侧, 申请 RRC连接建立, 处理流程如图 6所示, 在本例中, 网络侧接入设备以基站为例, 步骤如下: 步骤 602、 用户设备和基站建立同步; 步骤 604、 用户设备向基站发送 RRC连接建立请求消息; 步骤 606、 基站向用户设备反馈 RRC连接建立消息; 步骤 608、 用户设备根据本次连接建立性质, 选择对应的接入性质信息, 将其包 含在 RRC连接建立完成消息中; 步骤 610、 用户设备向基站发送 RRC连接建立完成消息; 步骤 612、基站根据网络侧的负载情况,结合用户设备的 RRC连接接入性质信息, 判断是否可以保持该用户设备的本次 RRC连接, 若可以, 则转步骤 614, 若不可以, 则转步骤 606; 步骤 614、 若基站同意用户设备保持此次 RRC连接, 则不触发 RRC连接释放流 程, 用户设备继续进行后续的和核心网的连接过程; 步骤 616、 若基站不同意用户设备保持此次 RRC连接, 则触发 RRC连接释放流 程, 释放该用户设备的 RRC连接。 基于同一发明构思, 本发明实施例还提供了一种无线资源控制装置, 应用于网络 侧, 其结构示意图参见图 7, 包括: 接收模块 701, 设置为在网络侧与用户设备建立无线资源控制 RRC连接时, 收到 用户设备发送的 RRC连接建立完成消息, 其中, RRC连接建立完成消息中携带有接 入信息; 确定模块 702, 设置为根据网络侧的负载情况以及接入信息确定是否维持 RRC连 接。 在一个实施例中, 接收模块 701接收的接入信息由下列任意一项或多项的组合确 定: 用户设备的类型信息、 用户设备的分组信息、 用户设备的优先级信息、 用户设备 的公共陆地移动网 PLMN类型信息、 用户设备在网络侧的接入级别信息、 用户设备与 网络侧预先约定的业务的类型信息、用户设备与网络侧预先约定的业务的优先级信息、 用户设备与网络侧预先约定的业务模型的类型信息以及用户设备与网络侧预先约定的 业务的服务质量要求类型信息。 在一个实施例中, 接收模块 701设置为接收包含如下参数的接入信息: 用户设备的分组信息包括用户设备分组的序号或标识; 用户设备的优先级信息包括网络侧和用户设备预先约定的用户设备的优先级序号 或标识; 用户设备的 PLMN类型信息包括下列任意一项或多项的组合: 用户设备是否在其 本地公共陆地移动网 HPLMN 上的标识信息、 用户设备是否在与其 HPLMN等效的 PLMN上的标识信息、 用户设备是否在其用户身份模块或者全球用户身份模块所包含 的优选 PLMN列表中的 PLMN上的标识信息、用户设备是否是漫游的用户设备的标识 信息、 用户设备的 HPLMN的标识信息以及用户设备的等效 HPLMN的标识信息; 用户设备在网络侧的接入级别信息包括网络侧和用户设备预先约定的接入级别序 号或标识; 用户设备与网络侧预先约定的业务的类型信息包括按呼叫业务分类的类型信息; 用户设备与网络侧预先约定的业务的优先级信息包括网络侧和用户设备预先约定 的业务的优先级序号或标识; 用户设备与网络侧预先约定的业务模型的类型信息包括业务的数据通讯模型信 息, 其中, 数据通讯模型信息包括下述任意一项或多项的组合: 数据交互周期性、 数 据交互频度、 数据量大小或数据交互方向。 在一个实施例中, 参见图 8, 确定模块 702还可以包括: 连接子模块 801, 设置为当确定结果为是时, 不触发 RRC连接释放流程, 令用户 设备与网络侧维持 RRC连接; 释放子模块 802, 设置为当确定结果为否时, 触发 RRC连接释放流程, 释放 RRC 连接。 在一个实施例中, 无线资源控制系统可以集成于接入网设备, 例如, 基站。 从以上的描述中, 可以看出, 本发明实现了如下技术效果: 采用本发明实施例提供的无线资源控制方法,在 RRC连接建立完成消息中携带接 入信息, 网络侧能够根据网络侧的负载情况及接入信息确定是否维持 RRC连接, 使得 网络侧能够更准确的掌握用户设备的信息, 以保证网络侧实现了对高密度、 多业务的 用户设备的接纳的精确控制。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Figure imgf000013_0002
In practical applications, there may be other combinations to form an access information list of the RRC connection, and the access information list may also contain more or less than seven access information, for example, one, two, three. Item, ten or any natural number. In the implementation, in step 502, the RRC connection is established between the user equipment and the network side. Before the implementation in step 502, the method may further include: determining, by the user equipment, the access information according to the type of the user and the service type of the service to be established, and connecting The incoming information is added to the RRC Connection Setup Complete message. When the network side determines whether to maintain the RRC connection according to the access information, different execution results may be selected. For example, when the determination result is yes, the network side may choose not to trigger the RRC connection release process, so that the user equipment and the network side maintain RRC connection; or, when the determination result is no, the network side may choose to trigger an RRC connection release procedure to release the RRC connection. In order to make the objects, the technical solutions and the advantages of the embodiments of the present invention more clearly, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. The embodiment of the present invention is applicable to an LTE system or a UMTS (Universal Mobile Telecommunications System). In this example, the user equipment accesses the network side and applies for RRC connection establishment. The processing flow is as shown in FIG. 6, in this example. The network side access device takes the base station as an example, and the steps are as follows: Step 602: The user equipment and the base station establish synchronization; Step 604: The user equipment sends an RRC connection setup request message to the base station. Step 606: The base station feeds back the RRC connection establishment to the user equipment. The message is: Step 608: The user equipment selects the corresponding access property information according to the current connection establishment property, and includes the information in the RRC connection setup complete message. Step 610: The user equipment sends an RRC connection setup complete message to the base station. Step 612 The base station determines whether the current RRC connection of the user equipment can be maintained according to the load status of the network side of the user equipment, if yes, go to step 614, if not, go to step 606; 614. If the base station agrees that the user equipment maintains the RRC connection, Send an RRC connection release procedure, the user equipment continues the subsequent connection process and a core network; Step 616: If the base station does not agree that the user equipment maintains the RRC connection, the RRC connection release procedure is triggered, and the RRC connection of the user equipment is released. Based on the same inventive concept, the embodiment of the present invention further provides a radio resource control apparatus, which is applied to the network side. The schematic diagram of the structure is shown in FIG. 7. The method includes: a receiving module 701, configured to establish a radio resource control RRC with the user equipment on the network side. When the connection is received, the RRC connection setup complete message sent by the user equipment is received, where the RRC connection setup complete message carries the access information, and the determining module 702 is configured to determine whether to maintain the RRC connection according to the load situation of the network side and the access information. . In an embodiment, the access information received by the receiving module 701 is determined by a combination of any one or more of the following: type information of the user equipment, group information of the user equipment, priority information of the user equipment, public land of the user equipment The PLMN type information of the mobile network, the access level information of the user equipment on the network side, the type information of the service pre-agreed by the user equipment and the network side, the priority information of the pre-agreed service of the user equipment and the network side, the user equipment and the network side advance The type information of the agreed service model and the type of service quality requirement type of the service agreed by the user equipment and the network side. In an embodiment, the receiving module 701 is configured to receive the access information including the following parameters: the group information of the user equipment includes a sequence number or identifier of the user equipment group; the priority information of the user equipment includes a user pre-agreed by the network side and the user equipment. The priority number or identifier of the device; the PLMN type information of the user equipment includes any combination of one or more of the following: whether the user equipment is identified on its local public land mobile network HPLMN, whether the user equipment is equivalent to its HPLMN The identification information on the PLMN, whether the user equipment is in the identity information module or the identification information on the PLMN in the preferred PLMN list included in the global user identity module, whether the user equipment is the identity information of the roaming user equipment, the HPLMN of the user equipment The identification information and the identifier information of the equivalent HPLMN of the user equipment; the access level information of the user equipment on the network side includes the access level sequence number or identifier pre-agreed by the network side and the user equipment; the type of the service pre-agreed by the user equipment and the network side Information includes classes classified by call service Information; The priority information of the pre-agreed service of the user equipment and the network side includes the priority number or identifier of the service pre-agreed by the network side and the user equipment; the type information of the service model pre-agreed by the user equipment and the network side includes the data communication model information of the service. The data communication model information includes any one or more of the following combinations: data interaction periodicity, data interaction frequency, data volume size, or data interaction direction. In an embodiment, referring to FIG. 8, the determining module 702 may further include: a connection submodule 801, configured to: when the determination result is yes, does not trigger an RRC connection release procedure, so that the user equipment maintains an RRC connection with the network side; The module 802 is configured to trigger an RRC connection release procedure to release the RRC connection when the determination result is no. In one embodiment, the radio resource control system can be integrated with an access network device, such as a base station. From the above description, it can be seen that the following technical effects are achieved by the present invention: The RRC connection setup complete message carries the access information, and the network side can load according to the network side by using the radio resource control method provided by the embodiment of the present invention. The situation and the access information determine whether to maintain the RRC connection, so that the network side can more accurately grasp the information of the user equipment, so as to ensure that the network side implements precise control of the reception of the high-density, multi-service user equipment. 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
1. 一种无线资源控制方法, 包括: A radio resource control method, comprising:
在用户设备与网络侧之间建立无线资源控制 RRC连接时,所述网络侧接收 到用户设备发送的 RRC连接建立完成消息, 其中, 所述 RRC连接建立完成消 息中携带有接入信息; 以及  When the RRC connection is established between the user equipment and the network side, the network side receives the RRC connection setup complete message sent by the user equipment, where the RRC connection setup complete message carries the access information;
所述网络侧根据所述网络侧的负载情况以及所述接入信息确定是否维持所 述 RRC连接。  The network side determines whether to maintain the RRC connection according to the load condition of the network side and the access information.
2. 根据权利要求 1所述的方法, 其中, 所述接入信息包括下列任意一项或多项的 组合: 2. The method according to claim 1, wherein the access information comprises a combination of any one or more of the following:
所述用户设备的类型信息、 所述用户设备的分组信息、 所述用户设备的优 先级信息、所述用户设备的公共陆地移动网 PLMN类型信息、所述用户设备在 所述网络侧的接入级别信息、 所述用户设备与所述网络侧预先约定的业务的类 型信息、 所述用户设备与所述网络侧预先约定的业务的优先级信息、 所述用户 设备与所述网络侧预先约定的业务模型的类型信息以及所述用户设备与所述网 络侧预先约定的业务的服务质量要求类型信息。  The type information of the user equipment, the grouping information of the user equipment, the priority information of the user equipment, the public land mobile network PLMN type information of the user equipment, and the access of the user equipment on the network side The level information, the type information of the service that the user equipment and the network side pre-agreed, the priority information of the service that the user equipment and the network side pre-agreed, and the pre-agreed by the user equipment and the network side The type information of the service model and the quality of service requirement type information of the service that the user equipment and the network side pre-agreed.
3. 根据权利要求 2所述的方法, 其中: 所述用户设备的分组信息包括所述用户设备分组的序号或标识; 所述用户设备的优先级信息包括所述网络侧和所述用户设备预先约定的所 述用户设备的优先级序号或标识; The method according to claim 2, wherein: the group information of the user equipment includes a sequence number or an identifier of the user equipment group; the priority information of the user equipment includes the network side and the user equipment in advance The agreed priority serial number or identifier of the user equipment;
所述用户设备的 PLMN类型信息包括下列任意一项或多项的组合:所述用 户设备是否在其本地公共陆地移动网 HPLMN上的标识信息、 所述用户设备是 否在与其 HPLMN等效的 PLMN上的标识信息、所述用户设备是否在其用户身 份模块或者全球用户身份模块所包含的优选 PLMN列表中的 PLMN上的标识 信息、 所述用户设备是否是漫游的用户设备的标识信息、 所述用户设备的 HPLMN的标识信息以及所述用户设备的等效 HPLMN的标识信息;  The PLMN type information of the user equipment includes a combination of any one or more of the following: whether the user equipment is identification information on its local public land mobile network HPLMN, whether the user equipment is on a PLMN equivalent to its HPLMN. Identification information, whether the user equipment is in the user identity module or the identifier information on the PLMN in the preferred PLMN list included in the global user identity module, whether the user equipment is the roaming user equipment identity information, the user Identification information of the HPLMN of the device and identification information of the equivalent HPLMN of the user equipment;
所述用户设备在所述网络侧的接入级别信息包括所述网络侧和所述用户设 备预先约定的接入级别序号或标识;  The access level information of the user equipment on the network side includes an access level sequence number or identifier pre-agreed by the network side and the user equipment;
所述用户设备与所述网络侧预先约定的业务的类型信息包括按呼叫业务分 类的类型信息; 所述用户设备与所述网络侧预先约定的业务的优先级信息包括所述网络侧 和所述用户设备预先约定的业务的优先级序号或标识; The type information of the service pre-agreed by the user equipment and the network side includes type information classified by call service; The priority information of the pre-agreed service of the user equipment and the network side includes a priority serial number or identifier of the service pre-agreed by the network side and the user equipment;
所述用户设备与所述网络侧预先约定的业务模型的类型信息包括业务的数 据通讯模型信息, 其中, 所述数据通讯模型信息包括下述任意一项或多项的组 合: 数据交互周期性、 数据交互频度、 数据量大小或数据交互方向。  The type information of the service model pre-agreed by the user equipment and the network side includes the data communication model information of the service, where the data communication model information includes any one or more of the following combinations: Data interaction frequency, data volume size or data interaction direction.
4. 根据权利要求 1至 3任一项所述的方法, 其中, 所述在用户设备与网络侧之间 建立无线资源控制 RRC连接之前, 还包括: The method according to any one of claims 1 to 3, wherein before the establishing a radio resource control RRC connection between the user equipment and the network side, the method further includes:
所述用户设备根据自身的类型以及即将建立的业务的业务类型确定所述接 入信息, 并将所述接入信息添加到所述 RRC连接建立完成消息中。  The user equipment determines the access information according to its type and the service type of the service to be established, and adds the access information to the RRC connection setup complete message.
5. 根据权利要求 1至 3任一项所述的方法, 其中, 所述网络侧根据所述接入信息 确定是否维持所述 RRC连接之后, 还包括: The method according to any one of claims 1 to 3, wherein, after determining, by the network side, whether to maintain the RRC connection according to the access information, the method further includes:
当确定结果为是时,不触发 RRC连接释放流程,令所述用户设备与所述网 络侧维持所述 RRC连接;  When the determination result is yes, the RRC connection release procedure is not triggered, so that the user equipment maintains the RRC connection with the network side;
当确定结果为否时, 触发 RRC连接释放流程, 释放所述 RRC连接。  When the determination result is no, the RRC connection release procedure is triggered, and the RRC connection is released.
6. 一种无线资源控制装置, 应用于网络侧, 包括: A radio resource control device, applied to the network side, includes:
接收模块, 设置为在所述网络侧与用户设备建立无线资源控制 RRC 连接 时, 收到用户设备发送的 RRC连接建立完成消息, 其中, 所述 RRC连接建立 完成消息中携带有接入信息;  The receiving module is configured to: when the network side establishes a radio resource control RRC connection with the user equipment, the RRC connection setup complete message sent by the user equipment is received, where the RRC connection setup complete message carries the access information;
确定模块, 设置为根据所述网络侧的负载情况以及所述接入信息确定是否 维持所述 RRC连接。  And a determining module, configured to determine whether to maintain the RRC connection according to the load condition of the network side and the access information.
7. 根据权利要求 6所述的装置, 其中, 所述接收模块接收的接入信息由下列任意 一项或多项的组合确定: The device according to claim 6, wherein the access information received by the receiving module is determined by a combination of any one or more of the following:
所述用户设备的类型信息、 所述用户设备的分组信息、 所述用户设备的优 先级信息、所述用户设备的公共陆地移动网 PLMN类型信息、所述用户设备在 所述网络侧的接入级别信息、 所述用户设备与所述网络侧预先约定的业务的类 型信息、 所述用户设备与所述网络侧预先约定的业务的优先级信息、 所述用户 设备与所述网络侧预先约定的业务模型的类型信息以及所述用户设备与所述网 络侧预先约定的业务的服务质量要求类型信息。 根据权利要求 7所述的装置, 其中, 所述接收模块还设置为接收包含如下参数 的接入信息: The type information of the user equipment, the grouping information of the user equipment, the priority information of the user equipment, the public land mobile network PLMN type information of the user equipment, and the access of the user equipment on the network side The level information, the type information of the service that the user equipment and the network side pre-agreed, the priority information of the service that the user equipment and the network side pre-agreed, and the pre-agreed by the user equipment and the network side The type information of the service model and the quality of service requirement type information of the service that the user equipment and the network side pre-agreed. The apparatus according to claim 7, wherein the receiving module is further configured to receive access information including the following parameters:
所述用户设备的分组信息包括所述用户设备分组的序号或标识; 所述用户设备的优先级信息包括所述网络侧和所述用户设备预先约定的所 述用户设备的优先级序号或标识;  The grouping information of the user equipment includes a sequence number or an identifier of the user equipment group; the priority information of the user equipment includes a priority serial number or identifier of the user equipment that is pre-agreed by the network side and the user equipment;
所述用户设备的 PLMN类型信息包括下列任意一项或多项的组合:所述用 户设备是否在其本地公共陆地移动网 HPLMN上的标识信息、 所述用户设备是 否在与其 HPLMN等效的 PLMN上的标识信息、所述用户设备是否在其用户身 份模块或者全球用户身份模块所包含的优选 PLMN列表中的 PLMN上的标识 信息、 所述用户设备是否是漫游的用户设备的标识信息、 所述用户设备的 HPLMN的标识信息以及所述用户设备的等效 HPLMN的标识信息;  The PLMN type information of the user equipment includes a combination of any one or more of the following: whether the user equipment is identification information on its local public land mobile network HPLMN, whether the user equipment is on a PLMN equivalent to its HPLMN. Identification information, whether the user equipment is in the user identity module or the identifier information on the PLMN in the preferred PLMN list included in the global user identity module, whether the user equipment is the roaming user equipment identity information, the user Identification information of the HPLMN of the device and identification information of the equivalent HPLMN of the user equipment;
所述用户设备在所述网络侧的接入级别信息包括所述网络侧和所述用户设 备预先约定的接入级别序号或标识;  The access level information of the user equipment on the network side includes an access level sequence number or identifier pre-agreed by the network side and the user equipment;
所述用户设备与所述网络侧预先约定的业务的类型信息包括按呼叫业务分 类的类型信息;  The type information of the service pre-agreed by the user equipment and the network side includes type information classified by call service;
所述用户设备与所述网络侧预先约定的业务的优先级信息包括所述网络侧 和所述用户设备预先约定的业务的优先级序号或标识;  The priority information of the pre-agreed service of the user equipment and the network side includes a priority serial number or identifier of a service pre-agreed by the network side and the user equipment;
所述用户设备与所述网络侧预先约定的业务模型的类型信息包括业务的数 据通讯模型信息, 其中, 所述数据通讯模型信息包括下述任意一项或多项的组 合: 数据交互周期性、 数据交互频度、 数据量大小或数据交互方向。 根据权利要求 6至 8任一项所述的装置, 其中, 所述确定模块还包括:  The type information of the service model pre-agreed by the user equipment and the network side includes the data communication model information of the service, where the data communication model information includes any one or more of the following combinations: Data interaction frequency, data volume size or data interaction direction. The device according to any one of claims 6 to 8, wherein the determining module further comprises:
连接子模块, 设置为当确定结果为是时, 不触发 RRC连接释放流程, 令所 述用户设备与所述网络侧维持所述 RRC连接;  The connection sub-module is configured to: when the determination result is yes, the RRC connection release procedure is not triggered, so that the user equipment maintains the RRC connection with the network side;
释放子模块, 设置为当确定结果为否时, 触发 RRC连接释放流程, 释放所 述 RRC连接。 根据权利要求 6至 8任一项所述的装置, 其中所述无线资源控制系统集成于接 入网设备。  The release submodule is set to trigger an RRC connection release procedure to release the RRC connection when the determination result is no. The apparatus according to any one of claims 6 to 8, wherein said radio resource control system is integrated in an access network device.
PCT/CN2011/078597 2010-11-04 2011-08-18 Method and device for controlling radio resources WO2012058969A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2010105330480A CN102469551A (en) 2010-11-04 2010-11-04 Radio resource control (RRC) method and apparatus thereof
CN201010533048.0 2010-11-04

Publications (1)

Publication Number Publication Date
WO2012058969A1 true WO2012058969A1 (en) 2012-05-10

Family

ID=46023988

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/078597 WO2012058969A1 (en) 2010-11-04 2011-08-18 Method and device for controlling radio resources

Country Status (2)

Country Link
CN (1) CN102469551A (en)
WO (1) WO2012058969A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11991525B2 (en) 2021-12-02 2024-05-21 T-Mobile Usa, Inc. Wireless device access and subsidy control

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014069856A1 (en) * 2012-10-29 2014-05-08 Lg Electronics Inc. Method and apparatus for releasing connection in wireless communication system
CN103974205A (en) * 2013-01-31 2014-08-06 中兴通讯股份有限公司 Cluster business control method, network-side equipment and user equipment
CN106664730B (en) 2014-12-10 2020-09-25 华为技术有限公司 Management method and related device of wireless communication system
EP3261386B1 (en) 2015-03-13 2019-12-18 Huawei Technologies Co., Ltd. Service processing method, related device and system
CN108307481A (en) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 RRC connections control method and device, system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101801044A (en) * 2009-02-10 2010-08-11 鼎桥通信技术有限公司 Intersystem cell switching method, system, user equipment and wireless network controller

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101801044A (en) * 2009-02-10 2010-08-11 鼎桥通信技术有限公司 Intersystem cell switching method, system, user equipment and wireless network controller

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ALCATEL-LUCENT: "Discussion on LTE solutions for MTC", 3GPP TSG-RAN WG2 MEETING #71B R2-105660, 15 October 2010 (2010-10-15), XI'AN, CHINA *
CATT: "RRC Connection Control for MTC Device", 3GPP TSG RAN WG2 MEETING #71BIS R2-105387, 15 October 2010 (2010-10-15), XI' AN, CHINA *
INTEL CORPORATION: "MTC indication in RRC signalling for overload prevention", 3GPP TSG RAN WG2 MEETING #71BIS R2-105609, 15 October 2010 (2010-10-15), XI'AN, CHINA *
VODAFONE: "On the Need for New Establishment Causes for Devices Configured for MTC-LTE", 3GPP TSG RAN WG2 #71BIS R2-105484, 15 October 2010 (2010-10-15), XI'AN, CHINA *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11991525B2 (en) 2021-12-02 2024-05-21 T-Mobile Usa, Inc. Wireless device access and subsidy control

Also Published As

Publication number Publication date
CN102469551A (en) 2012-05-23

Similar Documents

Publication Publication Date Title
JP5690405B2 (en) Radio resource control method and system
US20190289455A1 (en) Data feeds for a subscription management service
US9264975B2 (en) Post access policing in a mobile communication network
WO2012058969A1 (en) Method and device for controlling radio resources
WO2012058970A1 (en) Method, terminal, and system for controlling terminal access
WO2011041979A1 (en) Method, device and system for network access of machine type communications terminal equipment
CN103748811A (en) System and method for applying extended accessing barring in wireless communication system
CN113676924B (en) Communication method, device and system
CN104410982B (en) Terminal polymerization and reconstructing method in a kind of Wireless Heterogeneous Networks
WO2012058997A1 (en) Terminal and method for terminal to access network
WO2012126300A1 (en) Method and system for controlling wireless resources
WO2012058965A1 (en) Method and terminal for terminal to access network
WO2012109823A1 (en) Congestion control method and system of machine type communication equipments
CN113923682B (en) Communication method, device and system
WO2012126247A1 (en) Method and system for controlling wireless resource
WO2013013531A1 (en) Method and system for access barring, and network side network element
TWI751265B (en) Access method and terminal
CN102740297A (en) Paging method, device and system
WO2011147362A1 (en) Method and apparatus for selecting public land mobile-communication network access network
US11582677B2 (en) Method and apparatus for terminating cellular network connection of unauthenticated terminal
KR20210054967A (en) Method and apparatus for controlling network slices in wireless communication system
WO2012146022A1 (en) Access control method, system and ue
WO2023000305A1 (en) Qos adjustment method and apparatus, device, and medium
KR20230020870A (en) Method and apparatus for applying user plane security policy for pdu session
CN116746207A (en) Resource allocation status subscription for application related functions

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11837495

Country of ref document: EP

Kind code of ref document: A1