LTE RRC建立原因!

在LTE中,3GPP 36.331中规定了RRC建立的原因,截止到R10版本,主要有如下几种原因:

 

EstablishmentCause::=               ENUMERATED {

                                          emergency, highPriorityAccess, mt-Access,mo-Signalling,

                                          mo-Data, delayTolerantAccess-v1020, spare2,spare1}

 

--ASN1STOP

 

emergency---拨打紧急号码

HighPriorityAccess---高优先级接入

mt-access--被叫接入

mo-Signalling--发送信令时

mo-Data---发送数据时

DelayTolerantAccess-v1020---R10中新增原因,延迟容忍接入

 

在3GPP36.331中,并没有什么时候用什么原因进行具体介绍,因为RRC建立原因原因与上层业务有关系,相关介绍在3GPP 24.301NAS层的协议中。在3GPP 36.301 D.1 Mapping of NAS procedure to RRC establishmentcause (S1 mode only)中给出了相关的映射关系

NASprocedure

RRC establishment cause (according 3GPP TS 36.331[22])

Call type

Attach

If an ATTACH REQUEST has EPSattach type not set to "EPS emergency attach", the RRCestablishment cause shall be set to MO signallingexcept when the UEinitiates attach procedure to establish emergency bearerservices.(See Note 1)

 

"originatingsignalling"

If an ATTACH REQUEST has EPSattach type not set to "EPS emergency attach", the attach procedure is nottriggered due to paging with IMSI, and UE isconfigured for NAS signalling low priority, the RRC establishmentcause shall be set to Delay tolerant. (SeeNote 1)

 

"originatingsignalling"

 

If an ATTACH REQUEST has EPSattach type set to "EPS emergency attach" or if the ATTACH REQUESThas EPSattach type not set to "EPS emergency attach"but the UEinitiates the attach procedure on receiving request fromupper layer to establish emergency bearer services, the RRCestablishment cause shall be set to Emergencycall.(See Note 1)

 

"emergencycalls"

 

Tracking AreaUpdate

If the UE does not have a PDNconnection established for emergency bearer servicesand is notinitiating a PDN CONNECTIVITY REQUEST that has requesttype set to "emergency, the RRC establishment cause shallbe set to MO signalling. (SeeNote 1)

"originatingsignalling"

If the UE does not have a PDN connectionestablished for emergency bearer services and is not initiating aPDN CONNECTIVITY REQUEST that has request type set to "emergency",the tracking area update procedure is not triggered due to paging,and UE is configured for NAS signalling low priority, the RRCestablishment cause shall be set to Delay tolerant. (SeeNote 1)

"originatingsignalling"

If the UE has a PDN connectionestablished for emergency bearer services or is initiating a PDNCONNECTIVITY REQUEST that has request type set to"emergency", theRRC establishment cause shall be set to Emergencycall.(See Note 1)

"emergencycalls"

Detach

MO signalling (SeeNote 1)

"originatingsignalling"

ServiceRequest

If a SERVICE REQUEST is torequest user plane radio resources, the RRC establishment causeshall be set to MO data. (SeeNote 1)

 

"originatingcalls"

 

If a SERVICE REQUEST is torequest user plane radio resources for emergency bearerservices, the RRC establishment cause shall be set toEmergency call. (See Note 1)

 

"emergencycalls"

 

If a SERVICE REQUEST is torequest resources for UL signalling, the RRC establishment causeshall be set to MO data. (SeeNote 1)

 

"originatingcalls"

 

If a SERVICE REQUEST istriggered by a PDN CONNECTIVITY REQUEST that has request type setto "emergency", the RRC establishment cause shall be set toEmergency call. (See Note 1)

 

"emergencycalls"

 

If a SERVICE REQUEST is torequest user plane radio resources or to request resourcesfor UL signalling and the UE is configured for NASsignalling low priority, the RRC establishment causeshall be set to Delay tolerant. (SeeNote 1)

 

"originatingcalls"

 

If a SERVICE REQUEST is aresponse to paging where the CN domain indicator is set to "PS",the RRC establishment cause shall be set to MT access. (SeeNote 1)

 

"terminatingcalls"

 

If an EXTENDED SERVICEREQUEST has service type set to"packet services via S1" and is to request userplane radio resources or to request resourcesfor UL signalling and the UE is configured for NAS signalling lowpriority, the RRC establishment cause shall be set to Delaytolerant. (See Note 1)

 

"originatingcalls"

If an EXTENDED SERVICEREQUEST has service type set to"packet services via S1" and is to request userplane radio resources for emergency bearerservices, the RRC establishment cause shall be set toEmergency call. (See Note 1)

 

"emergencycalls"

 

If an EXTENDED SERVICEREQUEST has service type set to"packet services via S1" and is triggered by aPDN CONNECTIVITY REQUEST that has request type set to "emergency",the RRC establishment cause shall be set to Emergency call. (SeeNote 1)

 

"emergencycalls"

 

If an EXTENDED SERVICEREQUEST has service type set to"packet services via S1" and is a response topaging where the CN domain indicator is set to "PS", the RRCestablishment cause shall be set to MT access. (SeeNote 1)

 

"terminatingcalls"

 

If an EXTENDED SERVICEREQUEST has service type set to "mobile originating CSfallback or 1xCSfallback" and is to request mobile originating1xCS fallback, the RRC establishment cause shall beset to MO data. (See Note 1).

 

"originatingcalls"

 

If an EXTENDED SERVICEREQUEST has service type set to "mobile originating CSfallback or 1xCSfallback" and is torequest mobile originating CS fallback, the RRC establishment causeshall be set to MO data. (SeeNote 1).

"mobile originating CSfallback"

If an EXTENDED SERVICEREQUEST is a response to paging for CS fallback, service type setto "mobile terminating CS fallback or 1xCS fallback", the RRCestablishment cause shall be set to MT access. (See Note1,Note 2).

"terminatingcalls"

 

If an EXTENDED SERVICEREQUEST has service type set to "mobile originating CS fallbackemergency call or1xCS fallback emergency call", the RRC establishment cause shall be set toEmergency call.
(See Note 1).

"emergencycalls"

 

If an EXTENDED SERVICEREQUEST has service type set to"mobile originating CS fallback or 1xCS fallback " and UE isconfigured for NAS signalling low priority, the RRC establishmentcause shall be set to Delay tolerant. (SeeNote 1).

"originatingcalls"

 

 

参考文档:

3GPP 36.331

3GPP 24.301

  • 5
    点赞
  • 49
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: nbiot相比LTErrc层精简了一些信令,如SIB(System Information Block)和RRC Connection Setup等。此外,nbiot还采用了更简单的授权过程,以提高设备的电池寿命和网络的容量。 ### 回答2: NBIoT(窄带物联网)相较于LTE(长期演进)在RRIU(无线资源控制)层精简了许多信令。 首先,在连接建立阶段,NBIoT相比LTE的信令数量大大减少。在LTE中,通常需要多个信令进行连接建立,如寻呼、随机接入、认证等,而NBIoT只需要一条非配额消息(NAS)信令就可以完成连接建立过程。 其次,在连接保持阶段,NBIoT在每次数据传输后不需要释放资源,可以持续保持连接。而LTE中,在每次数据传输后都需要释放资源,需要使用RRC连接重建信令对连接进行重新建立。 此外,NBIoT还可以通过使用周期性发送的信令来减少额外的切换和重建信令。在LTE中,为了确保移动性,会进行频繁的切换和重建信令,而NBIoT可以根据网络条件进行合适的周期性访问,减少了信令的次数,从而提高了效率。 综上所述,NBIoT通过减少连接建立和保持过程中的信令数量以及周期性发送的信令来精简了RRU(无线资源控制)层的信令。这些优化不仅提高了NBIoT的性能和效率,还降低了功耗,延长了设备的续航时间。 ### 回答3: NB-IoT(Narrowband Internet of Things)和LTE(Long-Term Evolution)是两种不同的通信技术标准。在RRC(Radio Resource Control)层面,NB-IoT相比LTE精简了一些信令,具体如下: 1. 连接建立过程简化:NB-IoT在RRC连接建立过程中减少了一些冗余信令。相比于传统的LTE连接建立流程,NB-IoT采用更简单的过程来建立和维护设备与网络之间的连接。 2. 状态变更信令精简:NB-IoT减少了状态变更时的信令交换。传统的LTE网络在设备状态变更时需要通过一系列的信令交互来实现,而NB-IoT通过减少不必要的信令来简化设备状态变更的过程,提高了系统的效率。 3. 控制信道优化:NB-IoT相对于传统的LTE采用了低功耗机制,使得设备在待机状态下功耗更低。这意味着在设备不活动的情况下,NB-IoT可以更有效地利用控制信道,减少功耗并延长设备的续航时间。 4. 特定的物联网需求:NB-IoT是专门为物联网应用而设计的通信技术,因此在RRC层面采取了一些针对物联网需求的优化措施。例如,NB-IoT支持设备漫游是通过简化信令过程和降低交互频率来实现的。 总的来说,NB-IoT通过精简信令和优化控制信道等方式,在RRC层面提高了物联网设备的性能,并满足了物联网应用中对低功耗、低成本和长续航时间的需求。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值