WO2012013085A1 - 长期演进网络中的业务建立控制方法、系统和终端设备 - Google Patents
长期演进网络中的业务建立控制方法、系统和终端设备 Download PDFInfo
- Publication number
- WO2012013085A1 WO2012013085A1 PCT/CN2011/074790 CN2011074790W WO2012013085A1 WO 2012013085 A1 WO2012013085 A1 WO 2012013085A1 CN 2011074790 W CN2011074790 W CN 2011074790W WO 2012013085 A1 WO2012013085 A1 WO 2012013085A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- restricted
- rrc connection
- rrc
- nas
- network side
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
Definitions
- the present invention relates to a mobile communication technology, and in particular, to a service establishment control method, system, and terminal device in an LTE (Long Term Evolution) network.
- LTE Long Term Evolution
- 3rd Generation 3rd Generation
- 3GPP The 3rd Generation Partnership Project, 3rd generation mobile communication
- the Standard Partner Program has also received increasing attention.
- 3GPP radio access technology In order to make 3GPP radio access technology in a favorable position in the future fierce competition in the field of mobile communications, it is necessary to consider the long-term evolution of 3GPP radio access technology.
- the LTE network based on long-term evolution can improve and enhance the 3G air access technology. Effectively reduce business response time, increase data transmission rate, expand service capacity and coverage, and reduce operator costs.
- the LTE network is mainly divided into three components: UE 10 (User Equipment), E-UTRAN 20 (Evolution Universal Terrestrial Radio Access Network), and CN 30 (Core Network, Core). network). Both the access network 20 and the core network 30 are located on the network side, and the access network 20 is composed of a plurality of eNBs 21 (eNodeBs, evolved nodes ,), and the core network 30 is composed of a plurality of MMEs 31 (mobile management entities) and S-GWs 32. (Service Gateway) Composition.
- the devices in the LTE network use the international standard interface to communicate with each other.
- the interface between the UE 10 and the access network 20 is an air interface (Uu port), and the interface between the eNodeBs 21 in the access network 20 is an X2 interface.
- the interface between the access network 20 and the core network 30 is an S1 interface.
- the protocol stack of the air interface is divided into NAS (Non Access Stratum) and Access Sratum (AS).
- the NAS is responsible for UE 10 and the core network.
- the MME 31 in the 30 establishes a connection and performs signaling interaction
- the AS is responsible for establishing a connection between the UE and the eNodeB 21 in the access network 20 and performing signaling interaction, that is, the UE 10 and the eNodeB 21 implement RRC through different protocol layers.
- Radio Resource Control Radio Frequency Control
- PDCP Packet Data Convergence
- RLC Radio Link Control
- MAC Media Access Control
- PHY Physical Interface Transceiver
- the RRC connection between the UE 10 and the eNodeB 21 of the access network 20 needs to be established first.
- the UE 10 sends a link establishment request to the RRC layer through the NAS, and the RRC layer is responsible for establishing an RRC connection with the access network 20.
- the protocol there are four types of RRC connections between the RRC layer and the access network 20: called, emergency call, Mo (Mobile Originating) signaling, and Mo data.
- the UE 10 sends a request for establishing an RRC connection to the network side, it is required to determine whether the type of the link establishment request initiated by the NAS is restricted. If the access is restricted, the RRC layer can request to establish the network on the common channel. Type of RRC connection.
- the RRC layer determines whether a certain type of RRC connection is allowed to access according to the state of the access control cell ac-Barringlnfo cell in the system message 2 of the cell in which the UE 10 is located, and the system message 2 is from the eNodeB.
- the dedicated resources of the eNodeB 21 are limited. Therefore, the number of user equipments that are allowed to maintain the access state at the same time is limited.
- the eNodeB calculates the number of the currently allocated bearers and the current CPU usage.
- the eNodeB can modify the access control cell in the broadcasted SIB2, and notify the UE that resides in the cell under the jurisdiction of the eNodeB in time, thereby limiting certain types of services.
- the RRC layer When the RRC layer determines that a certain type of RRC connection access is restricted according to the system message, it will reject the NAS connection request and start the corresponding timer (the timing is started when the RRC connection of the Mo data type is restricted). T303, when the RRC connection of the Mo signaling type is limited, the timer T305 is started), and the RRC is not allowed before the timer expires without considering the cell reselection.
- the layer initiates a request to establish an RRC connection to the network side again.
- the NAS can repeatedly try to establish a link because the emergency call has no limited time limit, and the network side sends a RrcConnectionReject to the UE 10 when the called party is restricted. Message, so these two types of RRC connection control are not within the scope of the present invention.
- the access network 20 may release some resources due to the completion of some UE 10 services, so that the overload condition is alleviated, so the service restriction for Mo data or Mo signaling may be released.
- the RRC will only try to establish an RRC connection again after the timer expires. This situation delays the process of establishing an RRC connection between the UE 10 and the network side to some extent, which has a certain impact on the speed of establishing the communication service. Summary of the invention
- the main technical problem to be solved by the present invention is to provide a service establishment control method, system and terminal device for effectively improving service establishment speed in a long-term evolution network.
- the present invention provides a service establishment control method in a long term evolution network, which is used to control a radio resource control RRC connection between a terminal device UE and a network side, and includes the following steps:
- the UE listens to the paging message from the network side in a state where the RRC connection is restricted, and the paging message indicates that the system message of the UE changes.
- the UE reads the changed system message according to the paging message, and determines, according to the changed system message, whether the RRC connection is restricted;
- the RRC layer of the UE sends the restricted release information to the non-access stratum NAS.
- the method further includes the following steps: the UE determines that the RRC connection is restricted, and starts the chain establishment limited timer;
- the method further includes the following steps: If the chain-established limited timer does not time out, the timing is stopped. Further, after the RRC layer of the UE sends the restricted release information to the non-access stratum NAS, the following steps are further included;
- the NAS initiates a link establishment request to the RRC layer
- the RRC layer initiates a request to establish an RRC connection to the network side according to the link establishment request.
- the system message includes a system message 2, and the UE determines according to the changed system message.
- Whether the RRC connection is restricted is determined according to whether the RRC connection is restricted according to the state of the access control cell in the system message 2.
- the RRC connection includes an RRC connection of a Mo data type or an RRC connection of a Mo signaling type.
- the RRC connection of the Mo data type it is determined that the RRC connection is not restricted in any of the following conditions: the access control cell does not exist, the access control cell exists, and the Mo data access control cell does not exist, and the access control cell There is a bit corresponding to the Mo access control cell but the special access level AC available to the current UE is 0.
- the RRC layer determines that the RRC connection is not restricted in any of the following situations: the access control cell does not exist, the access control cell exists, and the Mo signaling access control cell does not exist.
- the present invention also protects a terminal device, which is used to establish a service in a long-term evolution network, where the terminal device includes an RRC layer and a non-access stratum NAS, and further includes a listening module, a judging module, and a restriction release indicating module;
- the monitoring module is configured to listen to a paging message from the network side in a state where the RRC connection is restricted, where the paging message indicates that the system message of the UE changes.
- the determining module is configured to read the changed system message according to the paging message, and determine, according to the changed system message, whether the RRC connection is restricted;
- the restricted release indication module is configured to control when the determining module determines that the RRC connection is not restricted
- the RRC layer transmits the restricted release information to the NAS.
- timing control module and a chain-building limited timer are further included;
- the timing control module is configured to control the chain-sending limited timer to stop timing if it is determined that the chain-established limited timer has not timed out before the RRC layer sends the restricted release information to the NAS.
- the RRC layer further includes a chain building module, and the chain building module is configured to initiate an RRC connection to the network side according to the link establishment request initiated by the NAS after receiving the restricted release information. Request.
- the present invention also protects a service establishment control system in a long term evolution network, including the network device and the terminal device described in any of the above.
- the present invention has the following advantages:
- the present invention detects whether the RRC connection of the UE is still restricted by monitoring the paging message on the network side, and notifies the NAS in time to determine that the RRC connection is not restricted, so that the RRC connection is not transferred.
- the restricted state so that the request to establish an RRC connection can be initiated again to the network side as soon as possible.
- the present invention enables the UE to dynamically adjust the restricted state of the RRC connection according to the load state of the access network, and can effectively accelerate the process of establishing a corresponding service between the UE and the network side, and further improve the response speed of the LTE network.
- the UE determines that the RRC connection is not restricted and sends the restricted release information to the NAS in time, so as to avoid the time caused by the UE waiting for the chain-building limited timer to time out again.
- the delay enables the UE to establish a corresponding type of RRC connection with the network side in time.
- Figure 1 is an architecture diagram of an LTE network
- FIG. 2 is a schematic diagram of signaling interaction of a hollow interface protocol stack of an LTE network
- FIG. 3 is a flowchart of a method for establishing a service in a long term evolution network according to an embodiment of the present invention
- FIG. 4 is a flowchart of a chain construction process of a Mo data type according to the present invention
- FIG. 5 is a schematic diagram showing the structure of an access control cell in a system message
- FIG. 6 is a block diagram of a terminal device according to an embodiment of the present invention. detailed description
- the service establishment control method in the long-term evolution network of the present invention is used to control the establishment of an RRC connection between the UE 10 and the network side, and the UE 10 listens to the paging message that the network side indicates that the system message is changed, and changes according to the change in the RRC connection restricted state.
- the subsequent system message determines whether the RRC connection is still restricted. If the UE 10 determines that the RRC connection is not restricted, the RRC layer sends the restricted release information to the NAS in time to initiate a request to establish an RRC connection to the network side as soon as possible, and try to connect with the network.
- the RRC connection is established on the side, thereby accelerating the service establishment process between the UE 10 and the network side.
- a service establishment method in a long term evolution network includes the following steps:
- Step S301 The RRC connection between the UE 10 and the network side is restricted.
- the RRC layer determines that the RRC connection is restricted according to the system message currently received by the UE 10.
- the RRC layer sends the chain establishment rejection information to the NAS, so that the NAS is in the restricted state of the RRC connection of the type, and the connection establishment request of the type is not initiated to the RRC layer.
- the system message includes the system information 2 and other forms of system messages, wherein the system message 2 may include a cell such as an ac-Barringlnfo cell.
- the RRC layer according to the state of the access control cell ac-Barringlnfo in the system message 2 Determine if the RRC connection is restricted.
- the RRC connection mainly includes an RRC connection of the Mo data type or an RRC connection of the Mo signaling type. For different connection types, whether the RRC connection is restricted according to the state of the ac-Barringlnfo cell in the system message 2 is not Must be the same.
- the ac-Barringlnfo cell in System Message 2 is optional, and may include ac-BarringForEmergency (acute call control) cell, ac-BarringForMo-Signalling (Mo Signaling Access Control) message. Yuanhe ac-BarringForMo-Data (Mo Data Access Control) cells such as cells, where ac-BarringForEmergency is Boolean, ac-BarringForMo-Signalling and ac-BarringForMo-Data are optional, and the latter two cells are also available.
- the parameters include ac-BarringFactor (access restricted coefficient), ac-BarringTime (access restricted time), and ac-BarringForSpecialAC (special AC blocking information).
- the specific judgment method is as follows: When ac-BarringForMo-Data cell exists When it is restricted, the RRC connection of the Mo data type of the ordinary user is restricted.
- the ac-BarringForMo-Signalling cell exists, and when ac-BarringFactor in ac-BarringForMo-Signalling is set to 0, the RRC connection of the Mo signaling type of all users is restricted.
- the common user refers to the user who has the access capability of the SIM (User Identification Module) card of AC0 - AC10. All users refer to ordinary users and high-priority users with access capabilities of AC11 ⁇ AC15. For more detailed meanings and usage of the above cells, see 3GPP 36.331.
- SIM User Identification Module
- Step S302 After determining that a certain type of RRC connection is restricted, the UE 10 starts a corresponding chain-established limited timer (for example, T303 or T305), and the RRC layer of the UE 10 waits for the link establishment without considering the cell reselection. When the limited timer expires, the NAS is allowed to initiate this type of link establishment request again.
- a chain-established limited timer for example, T303 or T305
- Step S303 The UE 10 listens to the paging message from the network side.
- the access network 20 may release some resources due to the completion of some users' services, so that the overload condition is alleviated, so the changed system is broadcast to the UE 10 in the cell through the eNodeB 21.
- a paging message is also sent to the UE 10, which is used to indicate that the system message of the UE 10 is changed. By monitoring the paging message, the UE 10 can timely determine whether the RRC connection is restricted or not.
- Step S304 The UE 10 reads the changed system message according to the paging message.
- the system message may have multiple types, which may include the system message 2, as needed.
- Step S305 The UE 10 determines, according to the changed system message, whether the RRC connection is restricted. Specifically, whether the RRC connection is restricted according to the state of the ac-Barringlnfo cell in the system message 2, for example, determining that a certain type of RRC connection is not If yes, go to step S306, otherwise go to step S303 to continue listening.
- the UE 10 determines that the RRC connection is not restricted in different ways: For example, for the RRC connection of the Mo data type, the RRC connection is not restricted in any of the following situations: the ac-Barringlnfo cell does not exist, or The ac-Barringlnfo cell exists and the ac-BarringForMo-Data cell does not exist, or the ac-BarringInfo element exists, the ac-BarringForMo-Data cell exists, but the bit corresponding to the special access level AC available to the current UE in the ac-BarringForSpecialAC Bit is 0.
- the RRC connection of the Mo signaling type it is determined that the RRC connection is not restricted in any of the following conditions: the ac-Barringlnfo cell does not exist, or the ac-Barringlnfo cell exists and the ac-BarringForMo-Signalling cell does not exist, or ac- The Barringlnfo cell exists, the ac-BarringForMo-Signalling cell exists, but the bit corresponding to the special access level AC available to the current UE in the ac-BarringForSpecialAC is 0.
- Step S306 When it is determined that the RRC connection of a certain type is not limited according to the foregoing manner, if the corresponding chain-established limited timer does not time out, the timing of the chain-established limited timer is stopped.
- Step S307 The RRC layer sends the restricted release information to the NAS, and the NAS is transferred to a state in which the RRC connection of the corresponding type is not restricted. Then, the NAS may initiate a link establishment request to the RRC layer at any time according to specific needs, and the RRC layer initiates an RRC connection to the network side according to the link establishment request. Request, thereby attempting to establish an RRC connection with the network side.
- a specific control method for an RRC connection of a Mo data type includes the following steps:
- Step 401 The NAS initiates a Mo data type connection request to the RRC layer in a state where the RRC connection of the Mo data type is not restricted.
- Step S402 The RRC layer determines, according to the state of the ac-Barringlnfo cell in the currently received system message 2, whether the RRC connection of the Mo data type is restricted. If not, perform step 403; otherwise, perform step 404.
- Step 403 The RRC sends an RrcConnectionRequest (RRC Connection Request message) to the network side, and attempts to establish an RRC connection of the Mo data type with the network side.
- RRC Connection Request message RRC Connection Request message
- Step 404 The RRC layer sends an RRC connection reject message to the NAS, where the portable rejection is caused by data link restriction. After receiving the information, the NAS enters the RRC connection restricted state of the Mo data type, and does not initiate the Mo data type connection request.
- Step 405 The RRC layer starts the chain-established limited timer T303, and is configured to notify the NAS to initiate the chain-based restriction release when the T303 times out.
- Step 406 The RRC layer listens to the paging message paging on the network side, where the paging message includes an indication that the system message is changed.
- Step 407 The RRC layer reads the changed system message, including the system information 2 and other forms of system messages.
- Step 408 Determine the state of the ac-Barringlnfo cell in the system message 2 according to the RRC layer.
- step 409 Whether the RRC connection of the Mo data type is restricted, if the judgment is not limited, step 409 is performed, otherwise, no processing is continued.
- Step 409 The timer T303 has not expired, and the RRC layer stops the timing of the timer T303.
- Step S412 The RRC layer initiates a request to establish an RRC connection of the Mo data type to the network side according to the NAS connection request, and attempts to establish an RRC connection with the network side again.
- the processing procedure is similar to the above process, except that in steps S405 and 409, the corresponding operations are performed on the T305.
- the UE 10 for establishing a service in a long term evolution network includes a listening module 11, a determining module 12, a restricted release indicating module 131, a chain building module 132, a timing control module 14, and a chain-building restriction.
- Timer 15 the UE 10 for establishing a service in a long term evolution network includes a listening module 11, a determining module 12, a restricted release indicating module 131, a chain building module 132, a timing control module 14, and a chain-building restriction.
- the monitoring module 11 is configured to listen to a paging message from the network side in a state where the RRC connection is restricted, the paging message indicates that the system message of the UE 10 is changed, and notify the determining module 11 when the paging message is monitored.
- the determining module 11 is configured to read the changed system message according to the paging message, and determine, according to the changed system message, whether the RRC connection is restricted. Specifically, the determining module 11 determines the ac-Barringlnfo cell in the system message 2. The state determines whether the RRC connection is restricted. For different types of RRC connections, the judging module 11 can use different judgment modes.
- the restricted release indication module 131 and the chain-building module 132 are disposed at the RRC layer, and other functional modules such as the chain-limited timer 15 may be set at the RRC layer as needed.
- the restricted release indication module 131 is configured to, when the determining module 12 determines that the RRC connection of the certain type is not restricted, control the RRC layer to send the type of the restricted release information to the NAS, so that the NAS is in the RRC connection of the type. status.
- the NAS may initiate the connection request of the type to the RRC layer again according to the requirement.
- the chain building module 132 is configured to initiate a request for establishing the RRC connection of the type to the network side according to the link establishment request.
- the link-established timer 15 may include T303 and T305, which are automatically started when the RRC layer determines that a certain type of RRC connection is restricted, and is used to implement Limited timing control of RRC connection of Mo data type and Mo signaling type.
- the timing control module 14 is configured to determine, when the determining module 12 determines that the RRC connection of the certain type is not restricted, before the RRC layer sends the limited release information of the type to the NAS, if it is determined that the link-established limited timer 15 has not timed out, then the control is performed.
- the chain-building limited timer 15 stops timing, so as to avoid the time delay caused by the NAS waiting until the chain-building limited timer 15 times out to attempt to establish an RRC connection again.
- the present invention detects whether the RRC connection of the UE is still restricted by monitoring the paging message on the network side, and sends the restricted release information to the NAS layer in time to determine that the RRC connection is not restricted, so that the UE according to the load of the access network
- the state dynamically adjusts the restricted state of the RRC connection.
- the UE determines that the RRC connection is not restricted and notifies the NAS to enter the unrestricted state of the RRC connection in time, so as to quickly initiate a link establishment request to the RRC layer, and avoid the UE waiting to build.
- the chain-restricted timer expires, the time delay caused by the chain-building is attempted again. Therefore, the process of establishing a corresponding communication service between the UE and the network side can be effectively accelerated, and the response speed of the LTE network is further improved.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种长期演进网络中有效提高业务建立速度的业务建立控制方法、系统和终端设备,方法包括以下步骤:UE在RRC连接受限的状态下监听来自网络侧的寻呼消息,所述寻呼消息指示所述UE的系统消息发生改变;UE按照所述寻呼消息读取改变后的系统消息,并根据所述改变后的系统消息判断RRC连接是否受限;如果UE判断RRC连接不受限,则UE的RRC层向非接入层NAS发送受限解除信息。本发明通过监听网络侧的寻呼消息,判断UE的RRC连接是否仍然受限,并在判断RRC连接不受限的状态下及时通知NAS,从而可以尽可能快地向网络侧再次发起建立RRC连接的请求。本发明能有效加速UE与网络侧建立相应业务的进程,提高LTE网络的响应速度。
Description
长期演进网络中的业务建立控制方法、 系统和终端设备 技术领域
本发明涉及移动通讯技术, 尤其涉及一种 LTE ( Long Term Evolution: 长期演进) 网络中的业务建立控制方法、 系统和终端设备。 背景技术
目前, 第三代移动通信(The 3rd Generation, 3G )技术已经得到广泛 应用, 为了满足用户对于移动数据业务不断增长的需求, 针对 3G技术启动 的 3GPP ( The 3rd Generation Partnership Project, 第三代移动通信标准伙伴 项目)也相应地受到了越来越多的关注。为了使 3GPP无线接入技术在未来 移动通信领域的激烈竟争中处于有利地位,需要考虑 3GPP无线接入技术的 长期演进, 基于长期演进的 LTE网络通过改进和增强 3G的空中接入技术, 能有效减少业务响应时间, 提高数据传输速率, 扩展业务容量和覆盖范围, 并减少运营商的耗费。
如图 1所示, LTE网络主要分为三个组成部分: UE 10(User Equipment, 用户设备)、 E-UTRAN 20(Evolution Universal Terrestrial Radio Access Network, 接入网)和 CN 30 ( Core Network, 核心网)。 接入网 20和核心 网 30都位于网络侧 , 接入网 20由多个 eNB 21 ( eNodeB , 演进型节点 Β ) 组成, 核心网 30由多个 MME 31 (移动管理实体)和 S-GW 32 (服务网关) 组成。 LTE网络中的各设备之间釆用国际标准接口通信, 如 UE 10和接入 网 20之间的接口为空中接口 (Uu口), 接入网 20中各 eNodeB 21之间的 接口为 X2接口, 接入网 20与核心网 30之间的接口为 S1接口。 如图 2所 示, LTE网络中, 空中接口的协议栈分为 NAS ( Non Access Stratum, 非接 入层)和 AS ( Access Sratum, 接入层 )两部分, NAS负责 UE 10与核心网
30中的 MME 31建立连接并进行信令交互, AS负责 UE与接入网 20中的 eNodeB 21建立连接并进行信令交互,即 UE 10与 eNodeB 21之间通过不同 的协议层,实现 RRC( Radio Resource Control,无线资源控制)协议、 PDCP (分 组数据汇聚)协议、 RLC (无线链路控制)协议、 MAC (媒体访问控制)协 议、 PHY (物理接口收发)等各种形式的信令交互。
UE 10与网络侧之间建立通讯业务时, 首先需要建立 UE 10与接入网 20的 eNodeB 21之间的 RRC连接。 通常情况下, UE 10通过 NAS向 RRC 层发出建链请求, 并由 RRC层负责与接入网 20建立 RRC连接。 根据协议 规定, RRC层与接入网 20之间具有以下四种类型的 RRC连接: 被叫、 紧 急呼叫、 Mo ( Mobile Originating, 移动主叫 )信令和 Mo数据。 当 UE 10 向网络侧发出建立 RRC连接的请求之前, 需要判断 NAS发起的建链请求 的类型是否受限, 不受限则表明允许接入, RRC层才能在公共信道上向网 络侧请求建立该类型的 RRC连接。
根据标准协议, RRC层根据 UE 10所在小区的系统消息 2中的接入控 制信元 ac-Barringlnfo信元的状态判断某种类型的 RRC连接是否允许接入, 而系统消息 2来自于 eNodeB。 eNodeB21的专用资源是有限的, 因此一个 eNodeB下允许同时保持接入状态的用户设备的个数也就有了限制, eNodeB 根据当前分配的承载的个数、当前的 CPU占用率等信息计算出其负载情况, 当负荷过载的时候 eNodeB可以修改其广播的 SIB2内的接入控制信元, 并 及时通知驻留在该 eNodeB所辖小区下的 UE, 从而对某种类型的业务进行 限制。
当 RRC层根据系统消息判断某种类型的 RRC连接接入受限时, 在接 收到 NAS的建链请求时会拒绝之, 并启动相应的定时器(Mo数据类型的 RRC连接受限时启动定时器 T303 , Mo信令类型的 RRC连接受限时启动 定时器 T305 ),在不考虑小区重选的情况下,定时器超时之前并不允许 RRC
层再次向网络侧发起建立 RRC连接的请求。 而对于紧急呼叫和被叫类型的 RRC连接, 由于紧急呼叫无受限时间限制, NAS可以反复尝试建链, 而被 叫在受限的情况下, 网络侧向 UE 10发出 RrcConnectionReject ( RRC建链 拒绝)消息,因此这两种类型的 RRC连接控制不在本发明的讨论范围之内。
实际应用中, 定时器运行期间接入网 20可能由于一些 UE 10的业务完 成而释放了部分资源,使过载状况得到了緩解, 因此可解除对于 Mo数据或 Mo信令的业务限制,然而根据现有标准, RRC只有等到定时器超时才会再 次尝试建立 RRC连接, 这种现状在一定程度上延緩了 UE 10与网络侧建立 RRC连接的过程, 对通讯业务建立的速度造成一定影响。 发明内容
本发明要解决的主要技术问题是, 提供一种长期演进网络中有效提高 业务建立速度的业务建立控制方法、 系统和终端设备。
为解决上述技术问题, 本发明提供一种长期演进网络中的业务建立控 制方法, 用于控制终端设备 UE与网络侧之间建立无线资源控制 RRC连接, 包括以下步骤:
UE在 RRC连接受限的状态下监听来自网络侧的寻呼消息, 所述寻呼 消息指示所述 UE的系统消息发生改变;
UE按照所述寻呼消息读取改变后的系统消息, 并根据所述改变后的系 统消息判断 RRC连接是否受限;
如果 UE判断 RRC连接不受限, 则 UE的 RRC层向非接入层 NAS发 送受限解除信息。
UE在 RRC连接受限的状态下监听来自网络侧的寻呼消息之前, 还包 括以下步骤: UE判断 RRC连接受限, 则启动建链受限定时器;
UE的 RRC层向 NAS发送受限解除信息之前, 还包括以下步骤: 如果 所述建链受限定时器未超时, 则停止定时。
进一步地, UE的 RRC层向非接入层 NAS发送受限解除信息后, 还包 括以下步骤;
NAS向 RRC层发起建链请求;
RRC层根据所述建链请求向网络侧发起建立 RRC连接的请求。
所述系统消息包括系统消息 2 , UE根据所述改变后的系统消息判断
RRC连接是否受限的方式为: 根据所述系统消息 2中接入控制信元的状态 判断 RRC连接是否受限。
所述 RRC连接包括 Mo数据类型的 RRC连接或 Mo信令类型的 RRC 连接。
对于 Mo数据类型的 RRC连接,以下任一状况下判断 RRC连接不受限: 接入控制信元不存在, 接入控制信元存在且 Mo数据接入控制信元不存在 , 接入控制信元存在、 Mo数据接入控制信元存在但当前 UE可用的特殊接入 等级 AC对应的比特位为 0。
对于 Mo信令类型的 RRC连接,以下任一状况下 RRC层判断所述 RRC 连接不受限:接入控制信元不存在,接入控制信元存在且 Mo信令接入控制 信元不存在, 接入控制信元存在、 Mo信令接入控制信元存在但当前 UE可 用的特殊接入等级 AC对应的比特位为 0。
本发明还保护了一种终端设备, 用于在长期演进网络中建立业务, 所 述终端设备包括 RRC层和非接入层 NAS,还包括监听模块、判断模块和受 限解除指示模块;
监听模块用于在 RRC连接受限的状态下监听来自网络侧的寻呼消息, 所述寻呼消息指示所述 UE的系统消息发生改变;
判断模块用于按照所述寻呼消息读取改变后的系统消息, 并根据所述 改变后的系统消息判断 RRC连接是否受限;
受限解除指示模块用于在所述判断模块判断 RRC连接不受限时, 控制
RRC层向 NAS发送受限解除信息。
进一步地, 还包括定时控制模块和建链受限定时器;
定时控制模块用于在 RRC层向 NAS发送受限解除信息之前, 如果判 断所述建链受限定时器未超时, 则控制所述建链受限定时器停止定时。
所述受限解除指示模块设在 RRC层, 所述 RRC层还包括建链模块; 建链模块用于根据 NAS接收所述受限解除信息后发起的建链请求, 向 网络侧发起建立 RRC连接的请求。
本发明还保护了一种长期演进网络中的业务建立控制系统, 包括网络 侧和以上任一项所述的终端设备。
本发明的有益效果是: 本发明通过监听网络侧的寻呼消息, 判断 UE 的 RRC连接是否仍然受限, 并在判断 RRC连接不受限的状态下及时通知 NAS, 使其转入 RRC连接不受限的状态, 从而可以尽可能快地向网络侧再 次发起建立 RRC连接的请求。 本发明使 UE根据接入网的负载状态动态调 整 RRC连接的受限状态,能够有效加速 UE与网络侧建立相应业务的进程, 进一步提高 LTE网络的响应速度。
一旦接入网由于释放部分资源而緩解了过载状况, UE判断 RRC连接 不受限并及时向 NAS发出受限解除信息, 避免 UE等待建链受限定时器超 时才再次尝试建链而导致的时间延误,使 UE能够及时与网络侧建立相应类 型的 RRC连接。 附图说明
图 1为 LTE网络的架构图;
图 2为 LTE网络中空口协议栈的信令交互示意图;
图 3为本发明一种实施例的长期演进网络中的业务建立方法的流程图; 图 4为本发明 Mo数据类型的建链处理流程图;
图 5为系统消息中接入控制信元的构成示意图;
图 6为本发明一种实施例的终端设备框图。 具体实施方式
下面通过具体实施方式结合附图对本发明作进一步详细说明。
本发明长期演进网络中业务建立控制方法用于控制 UE 10与网络侧之 间建立 RRC连接, UE 10在 RRC连接受限的状态下监听网络侧指示系统消 息发生改变的寻呼消息, 并根据改变后的系统消息判断 RRC连接是否仍然 受限, 如果 UE 10判断 RRC连接不受限, 则 RRC层及时向 NAS发送受限 解除信息, 使其尽快向网络侧发起建立 RRC连接的请求, 尝试与网络侧建 立 RRC连接, 从而加速了 UE 10与网络侧之间的业务建立进程。
如图 3 所示, 本发明一种实施例的长期演进网络中的业务建立方法包 括以下步骤:
步骤 S301 : UE 10与网络侧之间的 RRC连接受限,即 UE 10通过 NAS 向 RRC层发起某种类型的建链请求后, RRC层根据 UE 10当前收到的系统 消息判断 RRC连接受限, 此时 RRC层向 NAS发送建链拒绝信息,使 NAS 处于该类型的 RRC连接的受限状态, 暂时不会向 RRC层发起该类型的建 链请求。
系统消息包括系统信息 2 以及其他形式的系统消息, 其中系统消息 2 中可能包括 ac-Barringlnfo信元等信元, 本发明中, RRC层根据系统消息 2 中接入控制信元 ac-Barringlnfo的状态判断 RRC连接是否受限。 具体地, RRC连接主要包括 Mo数据类型的 RRC连接或 Mo信令类型的 RRC连接, 对于不同的连接类型, 根据系统消息 2 中 ac-Barringlnfo信元的状态判断 RRC连接是否受限的方式也不一定相同。
请参见图 5 , 根据协议规定, 系统消息 2中的 ac-Barringlnfo信元为可 选项, 可能包括 ac-BarringForEmergency ( 紧急呼叫控制 ) 信元, ac-BarringForMo-Signalling ( Mo 信 令 接 入 控 制 ) 信 元 和
ac-BarringForMo-Data ( Mo 数据接入控制 ) 信元等信元, 其中 ac-BarringForEmergency 为布尔型更量, ac-BarringForMo-Signalling 和 ac-BarringForMo-Data为可选项 ,后两种信元还可分别包含 ac-BarringFactor ( 接入 受 限 系 数 ) 、 ac-BarringTime ( 接入 受 限 时 间 ) 和 ac-BarringForSpecialAC (特殊 AC阻塞信息)等参数, 具体判断方法如下: 当 ac-BarringForMo-Data信元存在时,限制普通用户的 Mo数据类型的 RRC连接。
当 ac-BarringForMo-Data 信元存在, 且 ac-BarringForMo-Data 中的 ac-BarringFactor设置为 0时, 限制所有用户的 Mo数据类型的 RRC连接。
当 ac-BarringForMo-Signalling信元存在时,限制普通用户的 Mo信令类 型的 RRC连接。
ac-BarringForMo-Signalling信元存在 ,且 ac-BarringForMo-Signalling中 的 ac-BarringFactor设置为 0时,限制所有用户的 Mo信令类型的 RRC连接。
其中, 普通用户指的是用户的 SIM (用户识别模块)卡内接入能力为 AC0 - AC10 的用户, 所有用户指的是普通用户以及接入能力为 AC11 ~ AC15 的高优先级的用户。 以上信元更加详细的含义和使用方法可以参见 3GPP 36.331。
步骤 S302: UE 10判断某种类型的 RRC连接受限后, 启动相应的建链 受限定时器(例如 T303或 T305 ), 在不考虑小区重选的情况下, UE 10的 RRC层等待建链受限定时器超时,才允许 NAS再次发起该类型的建链请求。
步骤 S303: UE 10监听来自网络侧的寻呼消息。 在建链受限定时器运 行期间, 者接入网 20可能由于一些用户的业务完成而释放了部分资源, 从 而过载状况得到了緩解, 因此通过 eNodeB 21向小区内的 UE 10广播改变 后的系统信息, 其中修改了小区的系统消息 2中的 ac-Barringlnfo信元, 从 而解除了对 Mo数据或 Mo信令类型的 RRC连接的限制, 而 eNodeB 21在
系统消息发生改变时, 还会向 UE 10发送寻呼消息, 用于指示 UE 10的系 统消息发生改变, UE 10通过监听该寻呼消息, 能够及时判断 RRC连接是 否受限的更新状况。
步骤 S304: UE 10按照寻呼消息读取改变后的系统消息, 根据需要, 系统消息可能具有多种, 其中可能包含系统消息 2。
步骤 S305: UE 10根据改变后的系统消息判断 RRC连接是否受限, 具 体地, 根据其中系统消息 2中 ac-Barringlnfo信元的状态判断 RRC连接是 否受限, 如判断某种类型的 RRC连接不受限, 则进入步骤 S306, 否则进入 步骤 S303继续监听。
对于不同类型的 RRC连接, UE 10判断 RRC连接不受限的方式不同: 例如,对于 Mo数据类型的 RRC连接, 以下任一状况下判断 RRC连接 不受限: ac-Barringlnfo 信元不存在, 或 ac-Barringlnfo 信元存在且 ac-BarringForMo-Data 信元不存在 , 或 ac-Barringlnfo 信元存在、 ac-BarringForMo-Data信元存在但 ac-BarringForSpecialAC中当前 UE可用的 特殊接入等级 AC对应的比特位为 0。
对于 Mo信令类型的 RRC连接,以下任一状况下判断 RRC连接不受限: ac-Barringlnfo 信 元 不 存 在 , 或 ac-Barringlnfo 信 元 存 在 且 ac-BarringForMo-Signalling 信元不存在, 或 ac-Barringlnfo 信元存在、 ac-BarringForMo-Signalling信元存在但 ac-BarringForSpecialAC中当前 UE 可用的特殊接入等级 AC对应的比特位为 0。
步骤 S306: 根据以上方式判断某种类型的 RRC连接不受限时, 如果 对应的建链受限定时器未超时, 则停止该建链受限定时器定时。
步骤 S307: RRC层向 NAS发送受限解除信息, 使 NAS转入相应类型 的 RRC连接不受限的状态。 接着, NAS可根据具体需要随时向 RRC层再 次发起建链请求, RRC层再根据该建链请求向网络侧发起建立 RRC连接的
请求, 从而尝试与网络侧建立 RRC连接。
如图 4所示, 一种实施例中, 对于 Mo数据类型的 RRC连接的具体控 制方法包括以下步骤:
步骤 401 : NAS在 Mo数据类型的 RRC连接不受限的状态下, 向 RRC 层发起 Mo数据类型的建链请求。
步骤 S402: RRC层根据当前收到的系统消息 2中的 ac-Barringlnfo信 元的状态判断 Mo数据类型的 RRC连接是否受限, 如果不受限, 则执行步 骤 403 , 否则执行步骤 404。
步骤 403: RRC发送 RrcConnectionRequest ( RRC连接请求消息)到网 络侧, 尝试与网络侧建立 Mo数据类型的 RRC连接。
步骤 404: RRC层发送 RRC连接拒绝信息给 NAS, 其中可携带拒绝原 因为数据建链受限。 NAS收到该信息后进入 Mo数据类型的 RRC连接受限 状态, 暂时不会再发起 Mo数据类型的建链请求。
步骤 405: RRC层启动建链受限定时器 T303 , 用于在 T303超时时, 通知 NAS发起建链受限解除。
步骤 406: RRC层监听到网络侧的寻呼消息 paging, 该寻呼消息中包 含了系统消息发生改变的指示。
步骤 407: RRC层读取改变后的系统消息, 其中包括系统信息 2以及 其他形式的系统消息。
步骤 408: RRC层根据的系统消息 2中 ac-Barringlnfo信元的状态判断
Mo数据类型的 RRC连接是否受限, 如果判断不受限, 则执行步骤 409 , 否 则继续不做任何处理。
步骤 409:定时器 T303还未超时,则 RRC层停止定时器 T303的定时。 步骤 410: RRC层向 NAS层发送 Mo数据类型的受限解除信息, 使其 进入 Mo数据类型的 RRC连接不受限的状态。
步骤 S411 : NAS再次向 RRC层发起 Mo数据类型的建链请求。
步骤 S412: RRC层根据 NAS的建链请求向网络侧发起建立 Mo数据 类型的 RRC连接的请求, 再次尝试与网络侧建立 RRC连接。
对于 Mo信令类型或其他类型的 RRC连接, 其处理过程与以上过程类 似, 只是在步骤 S405和 409中, 对 T305进行相应的操作。
如图 6所示, 本发明用于在长期演进网络中建立业务的 UE 10包括监 听模块 11、 判断模块 12、 受限解除指示模块 131、 建链模块 132、 定时控 制模块 14以及建链受限定时器 15。
其中, 监听模块 11用于在 RRC连接受限的状态下监听来自网络侧的 寻呼消息, 寻呼消息指示 UE 10的系统消息发生改变, 并在监听到寻呼消 息时通知判断模块 11。
判断模块 11用于按照寻呼消息读取改变后的系统消息, 并根据所述改 变后的系统消息判断 RRC连接是否受限, 具体地, 判断模块 11通过判断 系统消息 2中 ac-Barringlnfo信元的状态判断 RRC连接是否受限, 对于不 同类型的 RRC连接, 判断模块 11可釆用不同的判断方式。
受限解除指示模块 131和建链模块 132设在 RRC层, 根据需要, 建链 受限定时器 15等其他功能模块也可设置在 RRC层。
受限解除指示模块 131用于在判断模块 12判断某种类型的 RRC连接 不受限时, 控制 RRC层向 NAS发送该类型的受限解除信息, 使 NAS处于 该类型的 RRC连接的不受限状态。
NAS接收受限解除信息后,可根据需要再次向 RRC层发起该类型的建 链请求,建链模块 132用于根据该建链请求向网络侧发起建立该类型的 RRC 连接的请求。
根据不同类型的 RRC连接, 建链受限定时器 15可包括 T303和 T305 , 通常在 RRC层判断某种类型的 RRC连接受限时自动启动, 分别用于实现
Mo数据类型和 Mo信令类型的 RRC连接的受限定时控制。
定时控制模块 14用于判断模块 12判断某种类型的 RRC连接不受限时, 在 RRC层向 NAS发送该类型的受限解除信息之前, 如果判断建链受限定 时器 15未超时, 则控制建链受限定时器 15停止定时, 以避免 NAS等到建 链受限定时器 15超时才会再次尝试建立 RRC连接而导致的时间延误。
本发明通过监听网络侧的寻呼消息, 判断 UE的 RRC连接是否仍然受 限, 并在判断 RRC连接不受限的状态下及时向 NAS层发出受限解除信息, 使 UE根据接入网的负载状态动态调整 RRC连接的受限状态。 一旦接入网 由于释放部分资源而緩解了过载状况, UE判断得出 RRC连接不受限并及 时通知 NAS进入 RRC连接的不受限状态, 以便快速向 RRC层发起建链请 求, 避免 UE等待建链受限定时器超时才再次尝试建链而导致的时间延误, 因此能够有效加速 UE与网络侧建立相应的通讯业务的进程, 进一步提高 LTE网络的响应速度。
以上内容是结合具体的实施方式对本发明所作的进一步详细说明, 不 能认定本发明的具体实施只局限于这些说明。 对于本发明所属技术领域的 普通技术人员来说, 在不脱离本发明构思的前提下, 还可以做出若干简单 推演或替换, 都应当视为属于本发明的保护范围。
Claims
1、 一种长期演进网络中的业务建立控制方法, 用于控制终端设备 UE 与网络侧之间建立无线资源控制 RRC连接, 其特征在于, 包括以下步骤:
UE在 RRC连接受限的状态下监听来自网络侧的寻呼消息, 所述寻呼 消息指示所述 UE的系统消息发生改变;
UE按照所述寻呼消息读取改变后的系统消息, 并根据所述改变后的系 统消息判断 RRC连接是否受限;
如果 UE判断 RRC连接不受限, 则 UE的 RRC层向非接入层 NAS发 送受限解除信息。
2、 如权利要求 1所述的方法, 其中, UE在 RRC连接受限的状态下监 听来自网络侧的寻呼消息之前, 还包括以下步骤: UE判断 RRC连接受限, 则启动建链受限定时器;
UE的 RRC层向 NAS发送受限解除信息之前, 还包括以下步骤: 如果 所述建链受限定时器未超时, 则停止定时。
3、 如权利要求 1所述的方法, 其中, UE的 RRC层向非接入层 NAS 发送受限解除信息后, 还包括以下步骤:
NAS向 RRC层发起建链请求;
RRC层根据所述建链请求向网络侧发起建立 RRC连接的请求。
4、 如权利要求 1至 3中任一项所述的方法, 其中,
所述系统消息包括系统消息 2 , UE根据所述改变后的系统消息判断 RRC连接是否受限的方式为: 根据所述系统消息 2中接入控制信元的状态 判断 RRC连接是否受限。
5、 如权利要求 4所述的方法, 其中,
所述 RRC连接包括移动主叫 Mo数据类型的 RRC连接或 Mo信令类型 的 RRC连接。
6、 如权利要求 5所述的方法, 其中,
对于 Mo数据类型的 RRC连接,以下任一状况下判断 RRC连接不受限: 接入控制信元不存在, 接入控制信元存在且 Mo数据接入控制信元不存在 , 接入控制信元存在、 Mo数据接入控制信元存在但当前 UE可用的特殊接入 等级 AC对应的比特位为 0。
7、 如权利要求 5所述的方法, 其中, 对于 Mo信令类型的 RRC连接, 以下任一状况下 RRC层判断所述 RRC连接不受限: 接入控制信元不存在, 接入控制信元存在且 Mo信令接入控制信元不存在, 接入控制信元存在、 Mo信令接入控制信元存在但当前 UE可用的特殊接入等级 AC对应的比特 位为 0。
8、 一种终端设备, 用于在长期演进网络中建立业务, 所述终端设备包 括 RRC层和非接入层 NAS , 其特征在于, 还包括监听模块、 判断模块和受 限解除指示模块;
监听模块, 设置为在 RRC连接受限的状态下监听来自网络侧的寻呼消 息, 所述寻呼消息指示所述 UE的系统消息发生改变;
判断模块, 设置为按照所述寻呼消息读取改变后的系统消息, 并根据 所述改变后的系统消息判断 RRC连接是否受限;
受限解除指示模块, 设置为在所述判断模块判断 RRC连接不受限时, 控制 RRC层向 NAS发送受限解除信息。
9、 如权利要求 8所述的终端设备, 其中, 还包括定时控制模块和建链 受限定时器;
定时控制模块, 设置为在 RRC层向 NAS发送受限解除信息之前, 如 果判断所述建链受限定时器未超时, 则控制所述建链受限定时器停止定时。
10、 如权利要求 8所述的终端设备, 其特征在于,
所述受限解除指示模块设在 RRC层, 所述 RRC层还包括建链模块; 建链模块用于根据 NAS接收所述受限解除信息后发起的建链请求, 向 网络侧发起建立 RRC连接的请求。
11、 一种长期演进网络中的业务建立控制系统, 其特征在于, 包括网 络侧和权利要求 8至 10中任一项所述的终端设备。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010239067.2 | 2010-07-28 | ||
CN201010239067.2A CN101888705B (zh) | 2010-07-28 | 2010-07-28 | 长期演进网络中的业务建立控制方法、系统和终端设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012013085A1 true WO2012013085A1 (zh) | 2012-02-02 |
Family
ID=43074367
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/074790 WO2012013085A1 (zh) | 2010-07-28 | 2011-05-27 | 长期演进网络中的业务建立控制方法、系统和终端设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101888705B (zh) |
WO (1) | WO2012013085A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018048556A1 (en) * | 2016-09-12 | 2018-03-15 | Intel IP Corporation | Emergency response for iot and/or m2m devices |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101888705B (zh) * | 2010-07-28 | 2014-12-17 | 中兴通讯股份有限公司 | 长期演进网络中的业务建立控制方法、系统和终端设备 |
AU2011358879B2 (en) | 2011-02-10 | 2016-08-04 | Nokia Technologies Oy | Method and apparatus to reduce signaling overhead in the presence of network overload condition |
GB2490968A (en) | 2011-05-20 | 2012-11-21 | Nec Corp | Sharing radio access networks fairly between multiple operators |
CN104221423B (zh) * | 2012-03-30 | 2018-09-14 | 索尼移动通讯有限公司 | 网络负载控制方法、网络负载控制装置和计算机可读介质 |
CN102781018B (zh) * | 2012-07-10 | 2015-02-18 | 大唐移动通信设备有限公司 | 一种单通检测方法、装置及rnc |
CN104158638A (zh) * | 2013-05-13 | 2014-11-19 | 中兴通讯股份有限公司 | 控制ue重发数据传输请求的方法和系统、网络侧设备和ue |
CN103826327B (zh) * | 2014-01-28 | 2018-03-23 | 大唐移动通信设备有限公司 | 一种通信业务释放的方法和装置 |
CN106936784B (zh) * | 2015-12-30 | 2020-12-29 | 青岛海信宽带多媒体技术有限公司 | Sip注册方法、终端及系统 |
EP3211961B1 (en) * | 2016-02-05 | 2023-12-06 | HTC Corporation | Handling system information |
CN110301146B (zh) * | 2017-03-01 | 2021-02-26 | 华为技术有限公司 | 网络配置方法及终端 |
CN110493889B (zh) * | 2017-08-02 | 2021-07-09 | 展讯通信(上海)有限公司 | Rrc连接重建方法、计算机可读存储介质及用户终端 |
CN111787645B (zh) * | 2020-07-02 | 2022-05-13 | Oppo广东移动通信有限公司 | 无线资源控制连接的处理方法及装置、终端和可读存储介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101541059A (zh) * | 2008-09-22 | 2009-09-23 | 美商威睿电通公司 | 解除接入限制的使用者装置与方法以及芯片组 |
CN101610588A (zh) * | 2008-06-20 | 2009-12-23 | 华为技术有限公司 | 受限网络的搜索方法、装置和系统 |
CN101888705A (zh) * | 2010-07-28 | 2010-11-17 | 中兴通讯股份有限公司 | 长期演进网络中的业务建立控制方法、系统和终端设备 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8060122B2 (en) * | 2007-05-29 | 2011-11-15 | Innovative Sonic Limited | Method and apparatus for managing downlink discontinuous reception operation in a wireless communications system |
US8838089B2 (en) * | 2008-10-20 | 2014-09-16 | Htc Corporation | Method of improving radio resource control connenction establishment in a wireless communication system and related communication device |
-
2010
- 2010-07-28 CN CN201010239067.2A patent/CN101888705B/zh active Active
-
2011
- 2011-05-27 WO PCT/CN2011/074790 patent/WO2012013085A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101610588A (zh) * | 2008-06-20 | 2009-12-23 | 华为技术有限公司 | 受限网络的搜索方法、装置和系统 |
CN101541059A (zh) * | 2008-09-22 | 2009-09-23 | 美商威睿电通公司 | 解除接入限制的使用者装置与方法以及芯片组 |
CN101888705A (zh) * | 2010-07-28 | 2010-11-17 | 中兴通讯股份有限公司 | 长期演进网络中的业务建立控制方法、系统和终端设备 |
Non-Patent Citations (1)
Title |
---|
"ETSI LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification", 3GPP TS 36.331 VERSION 8.6.0 RELEASE 8, 31 July 2009 (2009-07-31), SOPHIA-ANTIPOLIS CEDEX ; FRANCE * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018048556A1 (en) * | 2016-09-12 | 2018-03-15 | Intel IP Corporation | Emergency response for iot and/or m2m devices |
Also Published As
Publication number | Publication date |
---|---|
CN101888705B (zh) | 2014-12-17 |
CN101888705A (zh) | 2010-11-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012013085A1 (zh) | 长期演进网络中的业务建立控制方法、系统和终端设备 | |
US10389545B2 (en) | Method and device for receiving a multimedia broadcast multicast service in a mobile communication system | |
RU2642842C1 (ru) | Способ и устройство для приема службы широковещательной многоадресной передачи мультимедиа в системе мобильной связи | |
US11533661B2 (en) | Method for performing cell reselection and device supporting the same | |
WO2012041204A2 (zh) | 一种负荷控制的方法和设备 | |
WO2011095037A1 (zh) | 一种传输保活信息的方法和设备 | |
WO2012136139A1 (zh) | 一种多个终端接入的控制方法、控制设备、终端及系统 | |
WO2012055375A1 (zh) | 临时块流的延迟释放方法和装置 | |
WO2012155657A1 (zh) | 一种ue切换到混合小区的方法、系统及基站 | |
US11812494B2 (en) | Method and apparatus for multi-sim operation based on reporting on terminal state in mobile wireless communication system | |
KR102468294B1 (ko) | 무선 이동 통신 시스템에서 응용 계층 측정을 수행하고 보고하는 방법 및 장치 | |
KR102491395B1 (ko) | 무선 이동 통신 시스템에서 단말이 복수의 로지컬채널그룹 매핑 정보를 이용해서 버퍼상태를 보고하는 방법 및 장치 | |
KR20230064489A (ko) | 무선 이동 통신 시스템에서 단말이 분할된 무선자원제어 메시지를 저장하고 폐기하는 방법 및 장치 | |
KR20230064488A (ko) | 무선 이동 통신 시스템에서 인액티브 단말이 응용 계층 측정을 관리하는 방법 및 장치 | |
KR102558872B1 (ko) | 무선 이동 통신 시스템에서 단말 상태 선호에 대한 단말 지원 정보를 제공하고 rrc 연결을 해제하는 방법 및 장치 | |
KR102558863B1 (ko) | 무선 이동 통신 시스템에서 단말 상태 선호에 대한 단말 지원 정보를 제공하는 방법 및 장치 | |
KR102517303B1 (ko) | 무선 이동 통신 시스템에서 단말이 복수의 제1 로지컬채널그룹 매핑 정보와 복수의 제2 로지컬채널그룹 매핑 정보를 이용해서 버퍼상태를 보고하는 방법 및 장치 | |
KR102517309B1 (ko) | 무선 이동 통신 시스템에서 단말이 복수의 로지컬채널그룹 매핑 정보와 버퍼상태보고 설정정보를 이용해서 버퍼상태를 보고하는 방법 및 장치 | |
KR102517304B1 (ko) | 무선 이동 통신 시스템에서 단말이 복수의 로지컬채널그룹 매핑 정보와 하나의 버퍼상태보고 설정정보를 이용해서 버퍼상태를 보고하는 방법 및 장치 | |
KR102500495B1 (ko) | 무선 이동 통신 시스템에서 rrc 연결 재개 절차와 데이터 송수신을 수행하기 위해 복수의 타이머와 베어러를 제어하는 방법 및 장치 | |
KR102497630B1 (ko) | 무선 이동 통신 시스템에서 단말 지원 정보 제공 절차와 핸드 오버 절차를 수행하는 방법 및 장치 | |
KR102500493B1 (ko) | 무선 이동 통신 시스템에서 단말이 복수의 파워헤드룸설정정보를 이용해서 파워헤드룸을 보고하는 방법 및 장치 | |
KR102491977B1 (ko) | 무선 이동 통신 시스템에서 rrc_inactive 상태의 단말이 미리 정의된 설정과 저장된 설정을 사용해서 데이터를 송수신하는 방법 및 장치 | |
KR102560524B1 (ko) | 무선 이동 통신 시스템에서 상향 링크 무선자원제어 메시지를 분할하고 전송하는 방법 및 장치 | |
KR102523013B1 (ko) | 무선 이동 통신 시스템에서 안전한 rrc 연결 재개 절차와 데이터 송수신을 위한 방법 및 장치 |
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: 11811787 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: 11811787 Country of ref document: EP Kind code of ref document: A1 |