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

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值