Professional Documents
Culture Documents
RRC Procedures in Lte: Revision History
RRC Procedures in Lte: Revision History
Version 0.1
Revision History:
Version
0.1
0.2
Date
22-APR-2008
23-APR-2008
Description
Initial Draft
Incorporated
pradeeps comment
ntents
Author
Praveen Kumar
Praveen Kumar
1 Introduction.......................................................................................................................6
2 Purpose..............................................................................................................................6
3 Important Changes in RRC specification for LTE and its difference with legacy 3GRNC system.........................................................................................................................6
4 Architecture.......................................................................................................................9
4.1 RRC State...................................................................................................................9
4.2 Signaling Radio Bearers............................................................................................9
4.3 RRC Functions.........................................................................................................10
4.4 RRC Procedures.......................................................................................................11
4.4.1 Paging...............................................................................................................11
4.4.2 RRC Connection establishment........................................................................12
4.4.3 RRC Connection Reconfiguration....................................................................14
4.4.4 RRC Connection Re-establishment .................................................................16
4.4.5 Initial Security Activation.................................................................................17
4.4.6 RRC Connection Release..................................................................................18
4.4.7 DL Information Transfer...................................................................................18
4.4.8 UL Information Transfer...................................................................................19
4.4.9 Handover Procedure..........................................................................................20
..........................................................................................................................................22
Reference
Document Name
RRC Specification
References in Document
Date
Version
33.331 v
from 3GPP
Release 8
8.1.0
Abbreviations:
ARQ
HARQ
AM
ASN.1
ARQ
AS
BCCH
BCH
CCCH
CCO
CP
C-RNTI
CSG
DCCH
DRB
DRX
DTCH
DTX
DL
DL-SCH
E-UTRA
E-UTRAN
ENB
EPC
EPS
FDD
FFS
GERAN
GSM
HARQ
HRPD
IE
IMEI
IMSI
L1
L2
L3
MAC
MBMS
MCCH
MIB
MTCH
N/A
NACC
NAS
PCCH
PDU
PDCP
PLMN
PTM-MC
PTM-SC
PTP
QoS
RACH
RA-RNTI
RAT
RB
RLC
RNTI
RRC
RSCP
RSRP
RSSI
SAE
SAP
SI
SIB
SI-RNTI
SI-RNTI
SRB
S-TMSI
TA
TDD
TM
UE
UICC
UL
UM
UL-SCH
UP
1 Introduction
This document provides the details of RRC procedures as specified in 3GPP 36.331
for LTE.
2 Purpose
The purpose of this document is to understand RRC Procedures and RRC IEs for
LTE. It will help developers and testing engineer to understand the feature better and
utilize their knowledge in various customer sites. This document will also help developer
to start thinking design of RRC in LTE.
RRC State: - In LTE there is only 2 RRC states i.e. RRC_IDLE and
RRC_CONNECTED whereas in 3G-RNC system RRC has a 5 state i.e.
IDLE, CELL_FACH, CELL_DCH, CELL_PCH, URA_PCH. In LTE, there
is no concept of common and dedicated transport channel, thats why there is
no need of CELL_FACH and CELL_DCH state. In LTE there is only shared
transport channel are defined. CELL_PCH and URA_PCH is also removed
because in LTE. Therefore this will simplifies the RRC State machine
handling and improves RRC performance. This will also simplify the RRM
algorithm which decides RRC states.
Signaling Radio Bearers: - In LTE there is only three SRB is defined i.e.
SRB0, SRB1 and SRB2. Still SRB2 is on FFS, whereas in 3G-RNC system
RRC has 4 SRBs i.e. SRB0, SRB1, SRB2 and SRB3 (optional).
SRB 0: - In LTE SRB 0 is used RLC TM entity over CCCH logical channel
in DL whereas in 3G-RNC system RLC UM entity over CCCH logical
channel in DL.
MAC entity: - In LTE there is only one MAC entity which needs to
configured whereas in 3G-RNC system there is 4 different MAC entity based
on different type of transport channel i.e MAC-d (DCH), MAC-c/sh (FACH,
DSCH), MAC-hs (HS-DSCH) and MAC-e (E-DCH). In 3G-RNC system the
state machine which is handling MAC configuration is quite complex. During
state transition CELL_FACH->CELL_DCH or CELL_DCH->CELL_FACH
lots of signaling was involved. In LTE, since there is only one MAC entity
which is easier and simple to configure and have very simple State Machine.
4 Architecture
4.1 RRC State
UE has two RRC state
RRC_IDLE:- This state indicates that there is not signaling radio bearer is
established i.e. no RRC connection is established. RRC_IDLE state can
further characterized as follows
o Transfer of broadcast/multicast data to UE.
o A UE specific DRX may be configured by upper layers.
o UE controlled mobility.
o The UE:
Monitors control channels associated with the shared data
channel to determine if data is scheduled for it.
Performing neighboring cell measurements and measurement
reporting.
Acquires system information.
CCCH
TMUL
SRB 0
DCCH
TMDL
AMDL
SRB 1
DCCH
AMUL
AMDL
SRB 2
AMUL
Figure 1 shows the SRB configuration CCCH, DCCH are the logical channel between the
RRC and RLC layer. TM-UL is the transparent mode RLC entity used in uplink, UM-DL
is the unacknowledgement mode RLC entity used in DL, AM DL is the
acknowledgement entity used in DL, AL-UL is the acknowledgement entity used in
uplink.
EUTRAN
PAGING
Figure 2 Paging Procedure
EUTRAN
If upper layer provides an S-TMSI. Upper layer will provide the S-TMSI if
the UE is registered in the TA of the current cell.
o Set Identity Type to S-TMSI
o Set the S-TMSI to the value received from upper layer.
Else
o Set the identity type to random number
o Draw a random value and set the Random number to the selected value.
UE
EUTRAN
ENB can reject the RRC connection establishment based on its admission control
algorithm. In this case ENB sends RRC Connection Reject message to the UE.
RRC Connection Request is very small in size in LTE as compared to 3GRNC. The main difference in both cases is the usage of UE identity. In LTE
UE identity is used as contention resolution identity because this is first
message from UE on the shared uplink channel where as in 3G RNC UE
identity is the initial UE identity. In LTE many IE have been removed from
RRC Connection Request message i.e. CN Domain Identity, Call type, HSPDSCH in CELL_FACH, MAC-ehs support, Access Stratum release
indicator, support of F-DPCH, UE mobility state indicator, Measured result
on RACH.
In LTE UE identity is used as contention resolution identity. It is possible
that contention failure can happen; in this case UE will try again the RRC
connection request based on its timer and counter. RRC will come to know
about the contention result from random access response message from peer
MAC layer. In this procedure there is interaction with the MAC layer where
as in 3G-RNC there is no such interaction with the MAC layer.
In LTE C-RNTI is indirectly allocated by MAC layer where as in 3G-RNC
system C-RNTI is allocated by the RRC layer and indicates to the MAC
layer. During random access procedure MAC Layer provides T-CRNTI to
the UE and UE uses this T-CRNTI as a CRNTI after successfully
completion of the RRC Connection establishment procedure.
Question
In LTE the default configuration is used for the radio bearer parameters.
There is no explicit configuration possible for RB where as in 3G-RNC
system explicit configuration is possible. The number of default
configuration in LTE is under FFS.
RRC Connection Setup Complete message include the
nasDedicationInfomation IE which will reduce the NAS signalling delay. In
3G-RNC system the nas information is sent via uplink direct transfer
message.
Why there is no UE capabilities information in RRC Connection Setup
Complete message
There is no START value defined in RRC Connection Setup Complete. In
3G-RNC system START value is defined for each domain. But I do not
know how this is handled in the LTE.
UE
EUTRAN
UE
EUTRAN
RRC Connection Reconfiguration message is used to establish one or more RBs. In this
procedure following broad level IEs are included.
Measurement Configuration
Nas dedicated information.
Radio Resource Configuration.
Mobility Control information.
Security Configuration
UE Related Information.
If UE successfully applied the configuration, It sends RRC Connection Reconfiguraion
Complete, otherwise RRC Connection Reconfiguration Fail
In LTE, the prioritized bit rate is introduced in Uplink. The UE has an uplink
rate control function which manages the sharing of uplink resources between
radio bearers. RRC controls the uplink rate control function by giving each
bearer a priority and a prioritized bit rate (PBR). PBR is a parameter set
internal to the ENodeB and is not signaled over the S1 interface as QoS
parameter. The uplink rate control function ensures that the UE serves its
radio bearer(s) in the following sequence:
o All the radio bearer(s) in decreasing priority order up to their PBR;
o All the radio bearer(s) in decreasing priority order for the remaining
resources assigned by the grant
NOTE:
In case the PBRs are all set to zero, the first step is skipped and the
radio bearer(s) are served in strict priority order: the UE maximizes the
transmission of higher priority data
Since LTE is having only one state in RRC connected mode i.e.
RRC_CONNECTED, thats why the complexity is reduced significantly as
compared to the 3G-RNC.
In LTE there is only one message define for the reconfiguration where as in
3G-RNC system 3 procedures are there to change the radio bearer
UE
EUTRAN
UE
EUTRAN
The UE shall initiate this procedure when security as been activated. The UE initiates the
procedure when one of the following conditions is met:
Upon re-entry of the service area after having detected radio link failure;
Upon handover failure
When lower layers detect problems, as specified in TS 36.322 [7];
In 3G-RNC System, for indicating radio link failure and lower layers failure
CELL UPDATE procedure is used where as in LTE RRC Connection
reestablishment procedure is used.
The handling of Radio Link Failure case is still FFS. There are various
proposals for handling radio link failure going on.
UE
EUTRAN
UE
EUTRAN
RRC Specification for LTE does not specify about the START value. The security
specification is also under FFS.
EUTRAN
UE
DL INFORMATION TRANSFER
EUTRAN
UE
EUTRAN
UL INFORMATION TRANSFER
E-UTRA
MME
Inter RAT
AS
Inter RAT
NAS
Decision for HO
HO Required
UN known Message?
Relocation Request
Relocation Request Ack
Un known Message?
HO Command
HO Preparation failure
Forwarding of Data
Figure 12Protocol Message Flow between UE, ENB and MME in case of HO
E-UTRA
MME
Inter RAT
AS
Inter RAT
NAS
Decision for HO
Relocation Request
Un known Message ?
HO Request
HO Request Ack
HO Failure
Un known Message ?
Relocation Command
Forwarding of Data
Figure 13 Protocol Message Flow between UE, ENB and MME in case of HO
The purpose of this procedure is to, under the control of the network; transfer a
connection between the UE and another Radio Access Network (e.g. GERAN or
UTRAN) to E-UTRAN. The handover to E-UTRA procedure applies when signaling
radio bearers are established, possibly in combination with (EPS) bearers. In case only
signaling radio bearers are established, it is FFS if the default EPS bearer is established
during handover. It is FFS if handover to E-UTRAN may be initiated while security is
not activated in the other RAT.
UE
eNB target
sector
UL allocation
1. Measurement reports
eNB source sector makes
HO decision to move UE to a
eNB target sector
2. Context data (UE RAN
context + intra-eNB flag)
Intra-eNB
handover
(proprietary)
DL allocation
4. Handover command
(new C-RNTI etc. + intraeNB flag)
Detach from old cell and
synchronize to new cell