Professional Documents
Culture Documents
Version 0.1
Revision History:
ntents
Reference
Document Name References in Document Date Version
RRC Specification 33.331 v
Abbreviations:
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, that’s 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.
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.
4.4.1 Paging
UE EUTRAN
PAGING
Paging message include paging records for UE which is to be paged. RRC needs
to configure the one TM RLC entity over PCCH logical channel to send the
paging message to the UE.
UE EUTRAN
Ue-identity = UE_CONTENTION_RESOLUTION_IDENTITY.
Setting of UE_CONTENTION_RESOLUTION_IDENTITY
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.
Question
• 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.
If AS-Security is enabled then only include Mobility Control Information IE and IEs
related to the RB establishment.
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.
• 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, that’s 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
The purpose of this procedure is re-establish the RRC connection, which involved
resumption of SRB1 operation and re-activation of security.
A UE in RRC_CONNECTED, for which security has been activated, may initiate
the procedure in order to continue the RRC connection. The connection re-establishment
succeeds only if the concerned cell is prepared i.e. has a valid UE context. In case E-
UTRAN accepts the re-establishment, SRB1 operation resumes while the operation of
other radio bearers remains suspended. E-UTRAN applies the procedure as follows:
- to reconfigure SRB1 and to resume data transfer only for this RB;
- to re-activate security without changing algorithms.
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];
UE EUTRAN
RRC Specification for LTE does not specify about the START value. The security
specification is also under FFS.
UE EUTRAN
UE EUTRAN
DL INFORMATION TRANSFER
UE EUTRAN
UL INFORMATION TRANSFER
HO Required
UN known Message?
Relocation Request
Un known Message?
HO Command
HO Preparation failure
Forwarding of Data
Figure 12Protocol Message Flow between UE, ENB and MME in case of HO
The purpose of this procedure is to move a UE in RRC_CONNECTED to a cell using
another Radio Access Technology (RAT), e.g. GERAN, UTRA or CDMA2000 systems.
The mobility from E-UTRA procedure covers both:
- Handover, i.e. the MOBILITY FROM E-UTRA message includes radio resources
that have been allocated for the UE in the target cell and
- Cell change order, i.e. the MOBILITY FROM E-UTRA message may include
information facilitating access of and/ or connection establishment in the target cell, e.g.
system information. Cell change order is applicable only to GERAN.
The mobility from E-UTRA procedure applies when signaling radio bearers are
established, possibly in combination with EPS bearers.
Decision for HO
Relocation Request
Un known Message ?
HO Request
HO Request Ack
HO Failure
Un known Message ?
Relocation Command
Forwarding of Data
HO Notify
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.
UL allocation
1. Measurement reports
Intra-eNB
handover Store UE RAN context,
(proprietary) reserve C-RNTI
3. Context confirm
(new C-RNTI...)
DL allocation
4. Handover command
(new C-RNTI etc. + intra-
eNB flag)
Deliver data
Synchronisation
UL allocation + TA for UE
6. Handover confirm
7. Handover completed