CS Call setup message flow.

1. System Information (BCCH)

The UE reads the System Information that is broadcast on BCCH. The information is not read
continuously. It is only read if the information changes
2. RRC: RRC Connection Request (CCCH)
The Mobile user decides to initiate a voice call. The first message the UE will send on CCCH is
RRC Connection Request. This will contain among other things, Initial UE Identity and
Establishment Cause
3. NBAP: Radio Link Setup Request
The SRNC sends this message to Node B. It will pass the Cell Id, TFS, TFCS, frequency, UL
Scrambling code, etc to Node B.
4. NBAP: Radio Link Setup Response
Node B allocates the resources and starts PHY Reception. While transmitting the response it
includes the Transport layer addressing information that includes the Binding Identity of the
AAL2 for Iub data transport bearer
5. ALCAP: Establish REQ
The AAL2 binding identity (Iub Data Transport Bearer Id) is passed to ALCAP protocol in Node
B. The Iub Data Transport bearer is now bounce to DCH.
6. ALCAP: Establish CNF
Establish confirm from ALCAP in Node B
7: DCH-FP: Downlink Synchronization
The Node B and SRNC establishes synchronization for the Iub Data Transport bearer by means
of exchange of the appropriate DCH Frame Protocol frames.
8: DCH-FP: Uplink Synchronization
Once the UL synchronization is achieved, Node B starts DL transmission.
9: RRC: RRC Connection Setup (CCCH)
RRC Connection Setup message is sent on CCCH with the parameters required to establish
DCH. Also the state indicator will be set to DCH for the voice (or CS) call.
10: NBAP: Radio Link Restore Indication
Once the UE establishes Radio Link, Node B will send RL Restore indication to the SRNC.
11: RRC: RRC Connection Setup Complete (DCCH)
RRC Connection Setup complete will be sent on DCCH. Integrity and Ciphering related
parameters and UE capability information will be sent back to SRNC
12: RRC: Initial Direct Transfer (CM Service Request)
First NAS message is now sent by the UE. It indicates that a UE originated Voice call is
required. The UE identity (TMSI) will also be passed in this message
13: RANAP: Initial UE Message (CM Service Request)
The NAS message will be forwarded to appropriate CN Domain (CS Domain in this case).
Along with the CM service request, it will also include LAI and SAI.
14: RANAP: Direct Transfer (Authentication Request)
MSC/VLR needs to perform authentication to make sure that the UE is genuine. For this reason
it will challenge the UE with a Authentication token and RAND (random number)
15: RRC: Downlink Direct Transfer (Authentication Request)
SRNC transfers the NAS message to the UE
16: RRC: Uplink Direct Transfer (Authentication Response)
UE computes the response (RES) and sends it back in the NAS message
17: RANAP: Direct Transfer [Authentication Response]
SRNC relays the response to the MSC/VLR. The MSC/VLR will compare the response RES
with the expected response XRES. If they are the same then the procedure will continue.
18: RANAP: Security Mode Command
MSC/VLR sends the Security Mode Command to start Ciphering and Integrity Protection.
Ciphering is optional while Integrity Protection is mandatory. The Algorithms, etc are known to
the MSC/VLR and the UE and only the ones that are common between them are used.
19: RRC: Security Mode Command
RRC Forwards the Security Mode command received from MSC/VLR to the UE.
20: RRC: Security Mode Complete
The UE configures the Ciphering and Integrity Protection and responds back to the network. The
response message is Integrity Protected for further safety. Ciphering is started at Ciphering
activation time. Since this is a Circuit switched call, the Ciphering will be started in MAC. In
case of AM and UM bearers it is started in RLC.
21: RANAP: Security Mode Complete
The network forwards the Security Mode Complete message to MSC/VLR.
22: RANAP: Direct Transfer (TMSI Reallocation Command)
The network may decide to re-allocate the TMSI to the UE. It sends a DT message which
includes the NAS TMSI Reallocation Command.
23: RRC: DL Direct Transfer (TMSI Reallocation Command)
The RNC relays the DT message to the UE.
24: RRC: UL Direct Transfer (TMSI Reallocation Complete)
The UE takes the new TMSI and responds with the Complete message
25: RANAP: Direct Transfer (TMSI Reallocation Complete)
The RNC relays the message to the CN domain
26: RRC: UL Direct Transfer (Setup)
The UE now sends the 'Setup' message in UL Direct Transfer message. This will include all the
required parameters for setting up the voice call. It will include the number that UE wishes to be
contacted and the bearer capability
27: RANAP: Direct Transfer (Setup)
The network relays the message to the MSC/VLR
28: RANAP: Direct Transfer (Call Proceeding)
The MSC/VLR sends Call Proceeding to the UE indicating that it is now starting with the RAB
establishment procedure.
29: RRC: DL Direct Transfer (Call Proceeding)
The network relays it to the UE.
30: RANAP: RAB Assignment Request
The CN initiates establishment of the Radio Access Bearer using the RAB Assignment Request
message. This message includes the QoS of the call being established, the Transport Address, Iu
Transport association, etc.
31: ALCAP: Establish REQ
SRNC initiates the set-up of Iu Data Transport bearer using ALCAP protocol. The request
contains the AAL2 Binding Identity to Bind the Iu Data Transport Bearer to the RAB. (Note that
this is not done in case of PS RAB)
32: ALCAP: Establish CNF
The CN responds with the ALCAP Establish CNF
33: NBAP: Radio Link Reconfiguration Prepare
SRNC requests Node B to prepare establishment of DCH to carry the RAB. It passes the TFS,
TFCS and Power Control Information in the message.
34: NBAP: Radio Link Reconfiguration Ready
Node B allocates the resources and responds with the Ready message. It sends back the AAL2
address and the AAL2 binding Id for the Iub data transport bearer.
35: ALCAP: Establish REQ
SRNC initiates setup of Iub Data Transport Bearer using ALCAP protocol. The request contains
the AAL2 Binding Identity to bind the Iub Data Transport Bearer to DCH.
36: ALCAP: Establish CNF
The Node B responds with the Establish Confirm.
37: DCH-FP: Downlink Synchronization
The Node B and SRNC establish synchronism for the Iub Data Transport Bearer by means of
exchange of the appropriate DCH frame protocol frames. SRNC sends the DL Synchronization
frames.
38: DCH-FP: Uplink Synchronization
The Node B responds with the UE Synchronization frames.
39: NBAP: Radio Link Reconfiguration Complete
Finally the SRNC instructs the Node B of the CFN at which the new configuration will come
into effect.
40: RRC: Radio Bearer Setup
SRNC sends the RB Setup message to add the new DCH's. The message will be received using
the old configuration.
41: RRC: Radio Bearer Setup Response
After the activation time the UE will respond with complete message using the new
configuration.
42: RANAP: RAB Assignment Response
The SRNC responds with the response to the MSC/VLR.
43: ISUP: Initial Address Message
MSC/VLR sends the Initial Address Message to the PSTN. The message tells the PSTN to
reserve an idle trunk circuit from originating switch to the destination switch.
44: ISUP: Address Complete Message
The ACM message is sent to indicate that the remote end of the trunk circuit has been reserved.
45: RANAP: Direct Transfer (Alert)
The Alert message is sent to the SRNC. This message contains the ACM received from the
PSTN.
46: RRC: Direct Transfer (Alert)
The Alert message is forwarded to the UE. The Alert message will initiate the ringing tone on the
handset.
47: ISUP: Answer Message
When the person that is being called picks up his phone, an Answer message is sent to the
MSC/VLR.
48: RANAP: Direct Transfer (Connect)
The MSC/VLR sends the Connect message to the SRNC via Direct Transfer message. The
Connect message indicates that the End User has answered the call.
49: RRC: DL Direct Transfer (Connect)
The SRNC forwards the Connect message to the UE.
50: RRC: UL Direct Transfer (Connect Acknowledge)
The UE confirms the reception of the Connect message using the Connect Acknowledge and
sending it via Direct Transfer
51: RANAP: Direct Transfer (Connect Acknowledge)
The Network forwards the Connect Acknowledge to the MSC/VLR. The call has now been
successfully established.






SlideShare

Upload
Browse
Go Pro
Login
Signup
Email
Like
Save
Embed
Loading























rrc-procedures-in-lte Document Transcript
1. RRC PROCEDURES IN LTE Version 0.1Revision History: Hughes Systique India
Private Limited, India
2. Version Date Description Author 0.1 22-APR-2008 Initial Draft Praveen Kumar 0.2
23-APR-2008 Incorporated Praveen Kumar pradeeps comment ntents Hughes Systique
India Private Limited, India
3. 1
Introduction.......................................................................................................................62
Purpose..............................................................................................................................63
Important Changes in RRC specification for LTE and its difference with legacy 3G-RNC
system.........................................................................................................................64
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 References in Document Date VersionRRC Specification
33.331 v Hughes Systique India Private Limited, India
4. from 3GPP 8.1.0Release 8Abbreviations:ARQ Automatic Repeat QueryHARQ
Hybrid Automatic Repeat QueryAM Acknowledged ModeASN.1 Abstract Syntax
Notation.1ARQ Automatic Repeat RequestAS Access StratumBCCH Broadcast Control
ChannelBCH Broadcast ChannelCCCH Common Control ChannelCCO Cell Change
OrderCP Control PlaneC-RNTI Cell RNTICSG Closed Subscriber GroupDCCH
Dedicated Control ChannelDRB (user) Data Radio BearerDRX Discontinuous
ReceptionDTCH Dedicated Traffic ChannelDTX Discontinuous TransmissionDL
DownlinkDL-SCH Downlink Shared ChannelE-UTRA Evolved Universal Terrestrial
Radio AccessE-UTRAN Evolved Universal Terrestrial Radio Access NetworkENB
Evolved Node BEPC Enhanced Packet CoreEPS Enhanced Packet SystemFDD
Frequency Division DuplexFFS For Further StudyGERAN GSM/EDGE Radio Access
NetworkGSM Global System for Mobile CommunicationsHARQ Hybrid Automatic
Repeat RequestHRPD CDMA2000 High Rate Packet DataIE Information elementIMEI
International Mobile Equipment IdentityIMSI International Mobile Subscriber IdentityL1
Layer 1L2 Layer 2L3 Layer 3MAC Media Access ControlMBMS Multimedia Broadcast
Multicast ServiceMCCH MBMS point-to-multipoint Control ChannelMIB Master
Information Block Hughes Systique India Private Limited, India
5. MTCH MBMS point-to-multipoint Traffic ChannelN/A Not ApplicableNACC
Network Assisted Cell ChangeNAS Non Access StratumPCCH Paging Control
ChannelPDU Protocol Data UnitPDCP Packet Data Convergence ProtocolPLMN Public
Land Mobile NetworkPTM-MC Point-to-Multipoint, Multi-CellPTM-SC Point-to-
Multipoint, Single-CellPTP Point-to-PointQoS Quality of ServiceRACH Random Access
ChannelRA-RNTI Random Access RNTIRAT Radio Access TechnologyRB Radio
BearerRLC Radio Link ControlRNTI Radio Network Temporary IdentifierRRC Radio
Resource ControlRSCP Received Signal Code PowerRSRP Reference Signal Received
PowerRSSI Received Signal Strength IndicatorSAE System Architecture EvolutionSAP
Service Access PointSI Scheduling InformationSIB System Information BlockSI-RNTI
Scheduling Information Change RNTISI-RNTI Scheduling Information RNTISRB
Signaling Radio BearerS-TMSI SAE Temporary Mobile Station IdentifierTA Tracking
AreaTDD Time Division DuplexTM Transparent ModeUE User EquipmentUICC
Universal Integrated Circuit CardUL UplinkUM Unacknowledged ModeUL-SCH Uplink
Shared ChannelUP User Plane Hughes Systique India Private Limited, India
6. 1 Introduction This document provides the details of RRC procedures as specified in
3GPP 36.331for LTE.2 Purpose The purpose of this document is to understand RRC
Procedures and RRC IEs forLTE. It will help developers and testing engineer to
understand the feature better andutilize their knowledge in various customer sites. This
document will also help developerto start thinking design of RRC in LTE.3 Important
Changes in RRC specification for LTE and its difference with legacy 3G-RNC system
Following is the important changes in RRC specification for LTE and its differencewith
legacy 3G-RNC system. Procedure specific difference is mentioned in specificprocedure
section. 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.
Hughes Systique India Private Limited, India
7. Radio Bearer mapping: - In LTE Radio bearer mapping would be much simpler than
the 3G-RNC system because of there is no common and transport channel defined in
LTE. In LTE there is no RRC connection mobility defined like cell update and ura
update. Domain Identity: - In LTE, there is only one domain identity i.e. PS domain and
which is implicit no need to specify anywhere in signaling where as in 3G-RNC system
there is two domain identity i.e. CS domain and PS domain identity. Because of these two
identities, there was lot of signaling overhead and complexity in RRC design. Now in
LTE, there is no Initial UE Message is defined because only one domain identity is there.
System Broadcast Information:- In LTE, MIB includes a limited number of most
frequently transmitted parameters and SIB Type 1containing the scheduling information
that mainly indicates when the SI messages are transmitted where as in 3G-RNC system,
MIB includes the frequently transmitted parameters was well as scheduling information.
In LTE, only shared channel is defined, so UE is always listening/decoding to the radio
frame at L1 and L2 layer, there is no need to define the downlink transport channel
configuration in the RRC Reconfiguration message. This will reduce signaling message
size effectively. All DL-SCH transport channel information is broadcasted in system
information. The above point introduces another very critical feature of DRX
calculation since all DL data is on the shared channel. ENB can tell the UE when to
decode/listen over the radio frame. This will optimize UE power consumtion. Paging
Type: - In LTE there is only one type of paging required where as in 3G-RNC system
there is two type of paging defined. This is because there is no CELL_FACH and
CELL_DCH state in LTE. Less signaling message in case of Reconfiguration: - In LTE
there is only one reconfiguration message to reconfigure all logical, transport and
physical channel where as in 3G-RNC system there are number of reconfiguration
message i.e. RB reconfiguration , TRCH configuration, PHY configuration. In LTE
there is no NBAP protocol, this reduces the latency of the RRC connection establishment
and RB management procedure. There is no need to define URNTI, ERNTI, HRNTI,
SRNTI in LTE, since there is only one shared MAC entity. In LTE, there in no need to
define activation time. Because of this there are lots of synchronizing complexity in 3G-
RNC systems i.e. Synchronizing Radio link procedure based on activation time,
synchronizing between the various MAC entity. This reduces significantly latency during
establishment and reconfiguration of radio bearers. In LTE, there in no need to specify
the RRC State in RRC message. For network control mobility, there is one feature
which become very important and critical i.e. CQI Reporting. CQI reporting should be
fast and correct for taking decision for mobility. Hughes Systique India Private
Limited, India
8. There is no signaling connection release procedure in LTE, since there is only one
domain i.e. PS domain and the UE context is shared between the MME and ENB and if
UE is active in ENB then it should be active in MME also. Hughes Systique India
Private Limited, India
9. 4 Architecture4.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.
RRC_CONNECTED: - This state indicates that there is signaling radio bearer established
i.e. RRC connection is established. RRC_CONNECTED state can be further
characterized as follows o Transfer of unicast data to/from an UE, transfer of
broadcast/multicast data to UE. o At the lower layers, the UE may configure with a UE
specific DRX/DTX. o Network Control Mobility, i.e. handover and cell change order
with network assistance (NACC) to GEREN. o The UE: Monitors control channels
associated with the shared data channel to determine if data is scheduled for it Provides
channel quality and feedback information. Performing neighboring cell measurements
and measurement reporting. Acquires system information.4.2 Signaling Radio
Bearers"Signaling Radio Bearers" (SRBs) are defined as Radio Bearers (RB) that are
used onlyfor the transmission of RRC and NAS messages. More specifically, the
following threeSRBs are defined:- SRB0 is for RRC messages using the CCCH logical
channel;- SRB1 is for NAS messages and for most RRC messages, all using DCCH
logical channel;- SRB2 is for high-priority RRC messages, using DCCH logical
channel. Hughes Systique India Private Limited, India
10. CCCH DCCH DCCH TM- SRB 0 TM- AM- SRB 1 AM- AM- SRB 2 AM- UL DL
DL UL DL UL Figure 1 Signalling radio Bearer ConfigurationFigure 1 shows the SRB
configuration CCCH, DCCH are the logical channel between theRRC and RLC layer.
TM-UL is the transparent mode RLC entity used in uplink, UM-DLis the
unacknowledgement mode RLC entity used in DL, AM DL is theacknowledgement
entity used in DL, AL-UL is the acknowledgement entity used inuplink.4.3 RRC
Functions The RRC protocol includes the following main functions: - Broadcast of
system information o Including NAS common information; o Information applicable to
the UEs in RRC_IDLE e.g. cell (re-selection) parameters, neighbouring cell information
and information (also) applicable for UEs in RRC_CONNECTED e.g. common channel
configuration information. - RRC Connection Control o Paging o
Establishment/Modification/release of RRC Connection, including e.g.
assignment/modification of UE identity (C-RNTI), establishment/modification/release of
SRB1 and SRB2, access class barring; o Initial security activation, i.e. initial
configuration of AS integrity protection (CP) and AS ciphering (CP, UP); o RRC
connection mobility including e.g. intra-frequency and inter- frequency handover,
associated security handling, i.e. key and/or algorithm change, specification of RRC
Context information transferred between network nodes. Hughes Systique India Private
Limited, India
11. o Establishment/modification/release of point to point RBs carrying user data. o
Radio configuration control including e.g. assignment/modification of ARQ
configuration, HARQ configuration , DRX configuration; o QoS Control including
assignment/modification of semi-persistent configuration information of DL/UL
assignment/modification of parameters for UL rate control in the UE, i.e. allocation of a
priority and a prioritized bit rate (PBR) for each RB. o Recovery from Radio link Failure.
- Inter-RAT mobility including e.g. security activation, transfer of RRC context
information. - Measurement configuration control and reporting: o
Establishment/modification/release of measurements (e.g. Intra frequency, inter
frequency and inter RAT mobility, Quality, UE internal, positioning) o Configuration and
deactivation of measurement gaps; o Measurement Reporting - Other functions including
e.g. transfer of dedicated NAS Information and non-3GPP dedicated information, transfer
of UE Radio access capability information, and support for E-UTRAN sharing (multiple
PLMN identities). - Multicast/Broadcast - Support of self configuration and self-
optimisation.4.4 RRC Procedures4.4.1 Paging UE EUTRAN PAGING Figure 2 Paging
Procedure The purpose of paging - Transmit paging information to the UE in RRC_IDLE
state. - To inform UEs in RRC_IDLE about the system information change. 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.
Hughes Systique India Private Limited, India
12. 4.4.1.1 Differences with 3G-RNC System in PagingIn 3G-RNC system, there is two
type of paging is defined i.e. paging Type 1 (idle,CELL_PCH, URA_PCH) and paging
Type 2 (CELL_DCH, CELL_FACH) and thesepaging are specific to the CN Domain. In
LTE this has become simpler because there isonly one domain and there is no state like
CELL_PCH and URA_PCH. In LTE paging ishandled in RRC_IDLE state.4.4.2 RRC
Connection establishment UE EUTRAN RRC CONNECTION REQUEST RRC
CONNECTION SETUP RRC CONNECTION SETUP COMPLETE Figure 3 Successful
Scenario of RRC Connection EstablishmentThe purpose of RRC Connection
establishment - To establish SRB1 only. This procedure is initiated by the UE when the
upper layer request the establishmentof a signalling connection while UE is in
RRC_IDLE state. UE sends RRC ConnectionRequest message to ENB on SRB 0 and the
US shall continue cell re-selection relatedmeasurement as well as cell-reselection
evaluation. If the contention resolution of theRRC Connection Request is successful, as
indicated by the lower layer, wait for RRCConnection Setup Response from ENB.
Otherwise retry to send the RRC ConnectionRequest message. ENB performs the
Admission Control based on its RRM algorithm. If ENBpermits the admission of the UE,
ENB sends the RRC Connection Setup message to theUE. RRC Connection setup
message contains all the RLC (logical channel) and MAC(transport layer) parameters to
establish the SRB1. UE applies the configuration informedin RRC Connection setup
message. UE enters into RRC_CONNTECTED state and stopthe cell-reselection
procedure. After successfully applying the configuration UE sends the RRC
Connectionsetup complete message.Ue-identity =
UE_CONTENTION_RESOLUTION_IDENTITY.Setting of
UE_CONTENTION_RESOLUTION_IDENTITY Hughes Systique India Private
Limited, India
13. - 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 RRC CONNECTION REQUEST RRC CONNECTION REJECT Figure 4
RRC connection establishment, network rejectENB can reject the RRC connection
establishment based on its admission controlalgorithm. In this case ENB sends RRC
Connection Reject message to the UE.4.4.2.1 Difference with 3G-RNC system in RRC
Connection Establishment Procedure RRC Connection Request is very small in size in
LTE as compared to 3G- RNC. 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, HS- PDSCH 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. Hughes Systique India Private
Limited, India
14. 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.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.4.4.3 RRC Connection
ReconfigurationThe purpose of this procedure - Establish/modify/release RBs, - To
perform Handover - To configure/modify measurements - NAS dedicated information
may be transferred from ENB to UE.If AS-Security is enabled then only include Mobility
Control Information IE and IEsrelated to the RB establishment. UE EUTRAN RRC
CONNECTION RECONFIGURATION RRC CONNECTION RECONFIGURATION
COMPLETE Figure 5 RRC connection reconfiguration, successful Hughes Systique
India Private Limited, India
15. UE EUTRAN RRC CONNECTION RECONFIGURATION RRC CONNECTION
RECONFIGURATION FAILURE Figure 6 RRC connection reconfiguration, failureRRC
Connection Reconfiguration message is used to establish one or more RBs. In
thisprocedure 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 ReconfiguraionComplete, otherwise RRC
Connection Reconfiguration Fail4.4.3.1 Difference with 3G-RNC system in RRC
Connection Reconfiguration Procedure 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 Hughes Systique
India Private Limited, India
16. configurations i.e radio bearer reconfiguration, transport channel reconfiguration and
physical channel reconfiguration. RB mapping Info is much simpler as compared to the
3G-RNC system. Transport channel and physical channel information IE is significantly
reduced as compared to the 3G-RNC system due to use of shared transport and physical
channel. There is no common and dedicated transport and physical channel define in
LTE. In LTE, at RRC level only one RNTI is maintained i.e. CRNTI which is generated
by MAC layer and informed to RRC Layer. In LTE, there is provision to change the
security configuration using RRC Connection Reconfiguration where as in 3G-RNC
system, it was handled using security mode command procedure. In LTE, RRC
Connection reconfiguration can be also used to send NAS dedicated signalling to the MS
to reduce the latency where as this option is not in 3G-RNC system.4.4.4 RRC
Connection Re-establishment The purpose of this procedure is re-establish the RRC
connection, which involvedresumption of SRB1 operation and re-activation of security.
A UE in RRC_CONNECTED, for which security has been activated, may initiatethe
procedure in order to continue the RRC connection. The connection re-
establishmentsucceeds 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 ofother 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 RRC CONNECTION RE-
ESTABLISHMENT REQUEST RRC CONNECTION RE-ESTABLISHMENT RRC
CONNECTION RE-ESTABLISHMENT COMPLETE Figure 7 RRC connection re-
establishment, successful Hughes Systique India Private Limited, India
17. UE EUTRAN RRC CONNECTION RE-ESTABLISHMENT REQUEST RRC
CONNECTION RE-ESTABLISHMENT REJECT Figure 8 RRC connection re-
establishment, successfulThe UE shall initiate this procedure when security as been
activated. The UE initiates theprocedure 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];4.4.4.1
Difference with 3G-RNC system in RRC Connection Reestablishment Procedure 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.4.4.5 Initial Security ActivationThe purpose of this
procedure is to activate AS security upon RRC connectionestablishment. ENB initiates
the security mode command procedure to a UE inRRC_CONNECTED. Moreover, ENB
applies the procedure as follows:- When only SRB1 is established, i.e. prior to
establishment of SRB2 and/ or DRBs. UE EUTRAN SECURITY MODE COMMAND
SECURITY MODE COMPLETE Figure 9 Security mode command, successful
Hughes Systique India Private Limited, India
18. UE EUTRAN SECURITY MODE COMMAND SECURITY MODE FAILURE
Figure 10 Security Mode command, failureRRC Specification for LTE does not specify
about the START value. The securityspecification is also under FFS.4.4.6 RRC
Connection ReleaseThe purpose of this procedure is to release the RRC connection,
which includes therelease of the signaling connection, the established EPS bearers as well
as all radioresources. E-UTRAN initiates the RRC connection release procedure to a UE
inRRC_CONNECTED. It is FFS if redirection can be done from E-UTRAN
beforesecurity is activated. UE EUTRAN RRC CONNECTION RELEASE Figure 11
RRC connection release, successful4.4.7 DL Information TransferThe purpose of this
procedure is to transfer NAS or (tunnelled) non-3GPP dedicatedinformation from E-
UTRAN to a UE in RRC_CONNECTED. E-UTRAN initiates theDL information transfer
procedure whenever there is a need to transfer NAS or non-3GPP dedicated information.
E-UTRAN initiates the DL information transfer procedureby sending the DL
INFORMATION TRANSFER message. UE EUTRAN DL INFORMATION
TRANSFER Hughes Systique India Private Limited, India
19. 4.4.8 UL Information TransferThe purpose of this procedure is to transfer NAS or
(tunnelled) non-3GPP dedicatedinformation from the UE to E-UTRAN. A UE in
RRC_CONNECTED initiates the ULinformation transfer procedure whenever there is a
need to transfer NAS or non-3GPPdedicated information. The UE initiates the UL
information transfer procedure bysending the UL INFORMATION TRANSFER
message. UE EUTRAN UL INFORMATION TRANSFER Hughes Systique India
Private Limited, India
20. 4.4.9 Handover Procedure4.4.9.1 Handover from E-UTRA to other RAT
(UTRAN/GERAN/CDMA2000) UE E-UTRA MME Inter RAT Inter RAT AS 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 1. Mobility from EUTRA in RRC Container of ENB 2. HO From E UTRA
Preparation request (CDMA 2000) in RRC Container of ENB Figure 12Protocol Message
Flow between UE, ENB and MME in case of HOThe purpose of this procedure is to
move a UE in RRC_CONNECTED to a cell usinganother 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 resourcesthat have been allocated for the UE in the target cell and- Cell
change order, i.e. the MOBILITY FROM E-UTRA message may includeinformation
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 areestablished, possibly in combination
with EPS bearers. Hughes Systique India Private Limited, India
21. 4.4.9.2 Handover From other RAT (UTRAN/GERAN/CDMA2000) to E-UTRA UE
E-UTRA MME Inter RAT Inter RAT AS NAS Decision for HO Relocation Request Un
known Message ? HO Request HO Request Ack HO Failure Un known Message ?
Relocation Command Forwarding of Data RRC Connection Reconfiguration in RRC
Container of other RAT HO Notify RRC Connection Reconfiguration Complete 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 aconnection between the
UE and another Radio Access Network (e.g. GERAN orUTRAN) to E-UTRAN. The
handover to E-UTRA procedure applies when signalingradio bearers are established,
possibly in combination with (EPS) bearers. In case onlysignaling radio bearers are
established, it is FFS if the default EPS bearer is establishedduring handover. It is FFS if
handover to E-UTRAN may be initiated while security isnot activated in the other
RAT. Hughes Systique India Private Limited, India
22. 4.4.9.3 Intra Handover A2000) to E-UTRA eNB source eNB target UE sector 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 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)
Detach from old cell and Deliver buffered and in synchronize to new cell transit packets
+ RLC, MAC, and HARQ context to target sector Deliver data Buffer packets from target
sector Synchronisation UL allocation + TA for UE 6. Handover confirm 7. Handover
completed Hughes Systique India Private Limited, India

Follow us on LinkedIn
Follow us on Twitter
Find us on Facebook
Find us on Google+
Learn About Us
About
Careers
Our Blog
Press
Contact us
Help & Support
Using SlideShare
SlideShare 101
Terms of Use
Privacy Policy
Copyright & DMCA
Community Guidelines
SlideShare on mobile
Pro & more
Go PRO
New

Business Solutions
Developers & API
Developers Section
Developers Group
Engineering Blog
Blog Widgets
2013 SlideShare Inc. All rights reserved.
RSS Feed
ENGLISH