MobileComm Professionals, Inc.

Your Partner for Wireless Engineering Solutions

System Access
 Preamble generation

The random access preambles are generated from: # root sequences = 838 in total
Zadoff-Chu root sequences (838 in total) with zero correlation zone # preamble sequences = 64 per cell
one or several sequences (length 839 each)
ZadoffChu sequence is known as a CAZAC sequence (Constant Amplitude Zero AutoCorrelation waveform).

There are 64 preambles sequences available in each cell. The set of 64 preamble sequences in a cell is found by
including first, in the order of increasing cyclic shift, all the available cyclic shifts of a root Zadoff-Chu sequence

Fig:
example of
preambles generation
with zero
autocorrelation zone
length equal to 279
(prachCS=14) Fig: Zadoff-Chu sequence. The real (upper) and imaginary
(lower) parts of the complex-valued output
 4

Preamble Formats
3GPP (TS36.211) specifies 4 random access formats for FDD

Difference in formats is based in the different durations for the cyclic prefix, sequence and guard time which have an
effect on the maximum cell radius
Recommendation:
Select Format0 for cell ranges
<14.53 km
Select Format1 for cell ranges
<77.34 km

Note: An additional format to these four is specified for TDD , Preamble format 2 supported
 5

PRACH Position in Frequency Domain

PRACH slot
Duration( e.g. 1ms)

PUCCH
PRACH
PRACH
Total UL Bandwidth

PRACH bandwidth
(1.08MHz)

PUSCH
PRACH slot period

PUCCH
Time
 6

PRACH Planning Principle

PRACH configuration: two cells must be different within the PRACH re-use distance to increase the RACH decoding
success rate
PRACH transmission can be separated by:
Time
PRACH-PUSCH interference: If PRACH resources are separated in time within eNB
PRACH-PRACH interference: If same PRACH resources are used for the cells of an eNodeB.
PRACH-PRACH interference is preferred to PRACH-PUSCH interference so prachConfIndex of the cells on one
site should be the same
Frequency
Allocation of PRACH area should be next to PUCCH area either at upper or lower border of frequency band,
however should not overlap with PUCCH area
Avoid separation of PUSCH in two areas by PRACH (The scheduler can only handle one PUSCH area)
For simplicity use same configuration for all cells
Sequence (PRACH CS and RootSeqIndex)
Use different sequences for all neighbour cells
PUSCH Rx power (SINR) can be very high compared to PRACH SINR in the neighbour cell and hence effectively swamp
the PRACH preambles and/or resulting in misdetections (ghost RACH).
 7

LTE Random Access Procedure

LTE random access procedure is used by the UEs to initiate a data transfer. The UEs also obtain uplink timing information from
the initial handshake.

This sequence diagram describes the tale of three UEs (UE-A, UE-B and UE-C) that are powered on at the same time:

UEs synchronize with the downlink channel by decoding the PSS and SSS signal. The UEs are synchronized to the downlink
frames after completing this procedure.

The three UEs initiate the random access procedure at exactly the same time. Two of them (UE-A and UE-B) happen to pick
the same preamble. This results in a resulting in a collision. UE-C picks a distinct preamble so it succeeds in the random
access procedure.

Contention between UE-A and UE-B is resolved in UE-A'S favor. UE-A proceeds with the RRC connection.

UE-C times out and retries the random access procedure.

 8

LTE Random Access Procedure

UE-A UE-B UE-C eNB

Random Access Procedure The UE-A randomly selects an RA preamble sequence

from the set of sequences available in the cell. The
Select Preamble 1 preamble selection is a shift in the Zadoff-Chu code
for the cell.

RACH RA Preamble 1 UE-A transmits the Preamble on an RA channel. This

transmission carries no data bits. The RA-RNTI is
RA-RNTI 1
implicitly specified by the timing of the preamble
transmission.

RACH RA Preamble 1 UE-B happens to select the same preamble as UE-A.

RA-RNTI 1
UE-B transmits the preamble at the same time. Thus
UE-B also assumes RA-RNTI 1. Two UEs transmitted
using the same preamble. In this scenario we
assume that UE-B's preamble transmission is lost.

Select Preamble 3

UE-C randomly chooses between the available

RACH RA Preamble 3 preambles. It picks Preamble 3.
RA-RNTI 1
UE-3 also transmits at the same time as UE-A and
UE-B. So UE-C also assumes the same RA-RNTI as UE-
A and UE-B. Preamble 1 and Preamble 3 Zadoff-Chu
sequences are orthogonal to each other so both of
them are received.
 9

LTE Random Access Procedure

UE-A UE-B UE-C eNB

Random Access Procedure

Process Preamble 1
Detect Preamble 1 The eNodeB detects the preamble transmission.

Estimate the Uplink Timing The eNodeB estimates the uplink transmission
timing of the UE.
Derive RA-RNTI 1 The eNodeB derives the RA-RNTI from the timeslot
number in which the preamble is received.
Allocate Temporary C-RNTI 1 A Temporary C-RNTI is assigned to the UE. This
address will be used to address the UE in
subsequent messages.

Process Preamble 3
Detect Preamble 3
The eNodeB detects the preamble transmission.
Estimate the Uplink Timing
The eNodeB estimates the uplink transmission
Derive RA-RNTI 1 timing of the UE.
The eNodeB derives the RA-RNTI from the timeslot
Allocate Temporary C-RNTI 3
number in which the preamble is received.
A Temporary C-RNTI is assigned to the UE. This
address will be used to address the UE in
subsequent messages.
 10

LTE Random Access Procedure

UE-A UE-B UE-C eNB

Random Access Procedure

The eNodeB assigns resources via the PDCCH. The
PDCCH DCI Format 1C PDCCH mesage is addressed by 'RA-RNTI 1' that is
assigned to UE-A, UE-B and UE-C.
RA-RNTI 1

The eNodeB transmits the RA Response on the UL-

SCH channel. The message carries the timing and
UL-SCH RA Response
uplink resource allocation for Preamble 1 and
MAC Header, Preamble 3. The message also includes the back off
- Backoff Indicator, indicator MAC header for controlling the backoff
- Preamble 1, duration in the event of a random access procedure
- Preamble 3, failure.
MAC RAR 1 (for Preamble 1),
- Temporary C-RNTI 1,
- Timing Advance 1,
- Uplink Resource Grant 1,
MAC RAR 3 (for Preamble 3),
- Temporary C-RNTI 3,
- Timing Advance 3,
- Uplink Resource Grant 3
 11

LTE Random Access Procedure

UE-A UE-B UE-C eNB
Random Access Procedure
UEs Process the RA Response
All three UEs receive the message as they were expecting
the message on the same RA-RNTI.
UE-A Processes RA UE-A saves the Temporary C-RNTI from the MAC
Response for Preamble 1 data for Preamble 1.
Save Temporary C-RNTI 1 After applying the correction, the UE is
synchronized in the return direction and can
Apply Timing Advance 1 transmits data bursts to the eNodeB.
The eNodeB assigned uplink resource information
Process UL Resource Grant 1 will be used to transmit the data to the eNodeB.

UE-B Processes RA UE-B mistakenly believes that the RA Response is

Response for Preamble 1
meant for it. The RA-RNTI and Preamble in the
Save Temporary C-RNTI 1 message match. UE-B has no way of knowing that
the message was really meant for UE-A only.
Apply Timing Advance 1
UE-B is continuing with the procedure even
though had been rejected. This situation will be
Process UL Resource Grant 1
resolved after the contention resolution phase.

UE-C Processes RA
Response for Preamble 3
Save Temporary C-RNTI 3 UE-C saves the Temporary C-RNTI from the MAC
data for Preamble 3 and goes ahead with the
Apply Timing Advance 3 random access procedure normally. The further
procedure for UE-C is not shown in this flow
Process UL Resource Grant 3
 12

LTE Random Access Procedure

UE-A UE-B UE-C eNB

Contention Resolution
The randomly selected RA preamble does not enable unique identification of
the UE, and it is possible that multiple UEs attempted RA with the same RA
preamble sequence on the same RA channel. The Contention Resolution
phase helps uniquely identify the UE that has been selected.

In this scenario, contention resolution will resolve the random access

procedure between UE-A and UE-B.

UE-A does not have a permanent identity, so it picks

Pick Initial UE Identity as
a random number as the UE identity.
'Random Number A'

UL-SCH RRC Connection Request The random UE identity is included in the RRC
connection request.
ue-identity = Random Number A
UE-A starts the T300 timer, awaiting the RRC
UE_A_T300 Connection Setup message.

Pick Initial UE Identity as UE-B also picks a random number as its UE identity.
'Random Number B'
UE-B transmits on the same assignment and collides
UL-SCH RRC Connection Request with the transmission of UE-A. It is likely that it's
transmission will not be received at the eNodeB as it
ue-identity = Random Number B, is transmitting with a timing advance that was not
Establishment Cause intended for the UE. In this scenario, UE-B's message
is lost.

UE_B_T300 UE-B also starts a timer awaiting the RRC Connection

Setup message.
 13

LTE Random Access Procedure

UE-A UE-B UE-C eNB

Contention Resolution The eNB accepts the transmission from the UE and
PHICH ACK acknowledges it with a Hybrid ARQ ack.

PDCCH DCI Format 1 The eNB signals a downlink assignment using the
Temporary C-RNTI 1 Temporary C-RNTI 1. Both UE-A and UE-B assume
that the assignment is for them as both UEs think
they have been assigned Temporary C-RNTI 1.

RA Contention Resolution + RRC Connection Setup *UE-A and UE-B receive the RRC Connection Setup
message, as it is addressed with the Temporary C-
initial UE Identity = Random Number A RNTI 1. The message also contains 'Random Number
A' as the initial identity.
PUCCH UCI HARQ ACK
UE-A receives the eNB's transmission so it
acknowledges the message with a Hybrid ARQ ack.
Compare received
initial UE identity
with 'Random
Number A' that was
sent in the RRC The UE, seeing its own identity echoed back,
Connection Request concludes that the RA was successful and proceeds
message. with time-aligned operation.

UE_A_T300

Compare received initial UE This comparison fails. UE-B realizes that it has lost
identity with 'Random out to another UE in the contention resolution.
Number B'
 14

LTE Random Access Procedure

UE-A UE-B UE-C eNB

RRC Connection Setup Complete handling

PUCCH UCI SR UE-A now requests uplink resources to send the RRC
Connection Setup Complete message.
PDCCH DCI Format 0
UE-A receives the resource assignment.
Temporary C-RNTI 1

RRC Connection Setup Complete UE-A sends the RRC Connection Setup message to
NAS Message initiate further signaling.

UE_B_T300 UE-B times for the random access procedure as it did

receive their own identity in the contention
resolution.

Retry Random Access Procedure

Select Preamble 4 UE-B retries the request.

RACH RA Preamble 1 UE-B retries the random access procedure.

RA-RNTI 4
 15

RRC States
UE has two RRC states: RRC _Idle and RRC_ Connected. A UE is in the RRC_Connected state when RRC
connection has been established.

RRC_Idle:
This state indicated that there is no signaling radio bearer established i.e. no RRC connection is established. RRC_Idle
state can be characterized as follows.
Transfer of broadcast multicast data to UE.
A UE specific DRX may be configured by upper layers.
UE controlled mobility.
The UE
- Monitors control channels associated with the shared data channel to
determine if the data is schedule for it.
- Performing neighboring cell measurement and measurement reporting.
- Acquires system information.
 16

RRC States

RRC_Connected:
This state indicates that there is signalling radio bearer established i.e. RRC connection
is established. RRC_Connected state can be characterized as follows:
Transfer of unicast data to / from an UE, transfer of broadcast /multicast data to
UE.
At the lower layer the UE may configure with a UE specific DRX/DTX.
Network control led mobility (Handover).
The UE:
- Monitors control channels associated with the shared data channel to
determine if data is schedule for it.
- Provides channel quality and feedback information.
- Perform neighboring cell measurements and measurement
reporting.
- Acquires system information.
 17

Signalling Radio Bearers

Signalling Radio Bearers (SRBs) are defined as Radio Bearers (RB) that are used
only for the transmission of RRC and NAS messages. The following three SRBs are
defined:

SRB0 is for the RRC messages using the CCCH logical channel.

SRB 1 is for RRC messages as well as for NAS messages prior to the establishment of
SRB 2, all using DCCH logical channel.

SRB 2 is for NAS messages, using DCCH logical channel. SRB 2 has a lower priority
than SRB 1 and is always configured by E-UTRAN after security activation.
 18

RRC Connection Establishment

RRC connection establishment is used to make the transition from RRC Idle mode to
RRC Connected mode. UE must make the transition to RRC Connected mode before
transferring any application data, or completing any signalling procedures.

The RRC connection establishment procedure is always initiated by the UE but can be
triggered by either the UE or the network.

The UE triggers RRC connection establishment if the end-user starts an application to

browse the internet, or to send an email.

The UE triggers RRC connection establishment if the UE moves into a new

Tracking Area and has to complete the Tracking Area Update signalling procedure.

The network triggers the RRC connection establishment procedure by sending a

Paging message. This could be used to allow the delivery of an incoming SMS or
notification of an incoming voice call

In the case of LTE, the initial Non-Access Stratum (NAS) message is transferred as part
of the RRC connection establishment procedure. In the case of UMTS, the initial NAS
message is transferred after the RRC connection establishment procedure. The
approach used by LTE helps to reduce connection establishment delay
 19

RRC Connection Establishment

RRC connection establishment configures Signalling Radio Bearer (SRB) 1 and allows
subsequent signalling to use the Dedicated Control Channel (DCCH) rather than the
Common Control Channel (CCCH) used by SRB 0.

The signalling for RRC connection establishment is shown in Figure . The entire
procedure is completed using only RRC signalling. A 3-way handshake is used to
move the UE into RRC connected mode.

UE eNodeB
 20

RRC Connection Establishment

The RRC Connection Request message is sent as part of the Random Access
procedure. It is transferred using SRB 0 on the Common Control Channel (CCCH)
because neither SRB 1 nor a Dedicated Control Channel (DCCH) have been setup at
this point. The uplink Resource Block allocation for the RRC Connection Request
message is signalled within the Random Access Response message
No scope for the UE to report any measurements within the RRC Connection Request
message.
The UE identity is signalled using the SAE Temporary Mobile Subscriber Identity (S-
TMSI) if the UE is registered with the Tracking Area to which the current cell belongs.
Otherwise, the UE selects a random number in the range from 0 to
- 1 to represent the UE identity.

Content of RRC Connection Request message

 21

RRC Connection Establishment

The establishment cause within the RRC Connection Request message is determined
by the Non-Access Stratum (NAS) procedure for which the connection is being
established. The relationship between establishment cause and NAS procedure is
specified by 3GPP TS 24.301. This relationship is presented in Table below. In all cases,
the RRC establishment cause is set to High Priority Access if the UE uses Access Class
(AC) 11 to 15

Relationship between higher layer establishment cause and RRC establishment cause
 22

RRC Connection Establishment

The UE starts the T300 timer after transmitting the RRC Connection Request
message. The value of T300 is broadcast within SIB 2. LTE uses the T300 timer to
define how long the UE waits for a response to the RRC Connection Request
message.

The establishment procedure fails if T300 expires before receiving an RRC

Connection Setup message. The procedure also fails if the UE completes a cell re-
selection prior to receiving the RRC Connection Setup message.

Random access contention can occur after sending the RRC Connection Request
message. contention occurs when multiple UE select the same sub frame and
preamble sequence for PRACH transmission. Contention requires the UE to repeat
transmission of the PRACH preamble and the subsequent RRC Connection Request
message. This increases the delay associated with connection establishment but
does not cause the overall procedure to fail unless the maximum number of
preamble transmissions has been reached
 23

RRC Connection Establishment

Assuming that random access contention does not occur, the UE proceeds to wait
for an RRC Connection Setup message from the eNode B. The UE has successfully
completed the random access procedure so has been allocated a C-RNTI (signalled
within the random access response message). The UE monitors the PDCCH for a
downlink allocation addressed to its C-RNTI.

The PDCCH specifies the set of PDSCH Resource Blocks used to transfer the RRC
Connection Setup message. The RRC Connection Setup message is transferred using
SRB 0 on the CCCH.

The RRC Connection Setup message contains configuration information for SRB 1.
This allows subsequent signalling to use the DCCH logical channel.

SRB 2 is always configured after security activation so the RRC Connection Setup
message does not include any information regarding SRB 2. The eNode B can
instruct the UE to apply a default configuration for SRB 1, or it can instruct the UE to
apply a specific configuration
 24

RRC Connection Establishment

The default configuration for SRB 1 and SRB 2 is presented in Table. Using the default
configuration helps to reduce the signalling requirement. SRB 2 has a lower priority
than SRB 1, i.e. a value of 3 represents a lower priority than a value of 1. Both SRB 1
and 2 always use acknowledged mode RLC

Default configurations for SRB 1 and SRB 2

 25

RRC Connection Establishment

The RRC Connection Setup message can also define configuration information for
the PDSCH, PUCCH and PUSCH physical channels. It can also include information
regarding uplink power control, CQI reporting, the Sounding Reference Signal,
antenna configuration and scheduling requests .

Upon receiving an RRC Connection Setup message, the UE stops the T300 timer
and makes the transition to RRC Connected mode. The UE then proceeds to
complete the procedure by sending an RRC Connection Setup Complete message.
The content of the RRC Connection Setup Complete message is shown in Table
below.

Content of RRC Connection Setup Complete message

 26

RRC Connection Establishment

The Transaction Identifier, combined with the message type, identifies the RRC
procedure with the UE

The Selected PLMN Identity defines a pointer to a PLMN listed within SIB1, i.e. UE
select the PLMN to which they want to connect when a cell belongs to more than a
single PLMN

The Registered MME information is optional, and is included when available. It

becomes available after a UE has registered with an MME. The MME is identified by
its Globally Unique MME Identity (GUMMEI) which is a concatenation of the PLMN
identity, MME Group Identity (MMEGI) and MME Code (MMEC). The MMEC
identifies the MME within its group.

The eNode B extracts the NAS message from the RRC Connection Setup Complete
message and forwards it to an MME using the S1 Application Protocol (S1-AP) Initial
UE Message. Forwarding this message does not form part of the RRC establishment
procedure
 27

RRC Connection Establishment

The content of the S1-AP Initial UE Message is shown in Table below. The eNode B
sends this message to the appropriate MME based upon its NAS Node Selection
Function (NNSF). In the case of a Service Request, the S-TMSI included within the
RRC Connection Request is used to identify the appropriate MME (S-TMSI includes
the MMEC).
In the case of an Attach or Tracking Area Update, the eNode B uses the GUMMEI
included within the RRC Connection Setup Complete message. The eNode B is free
to select an MME when the UE does not have an S-TMSI nor GUMMEI.

Content of S1 Application Protocol (S1-AP) Initial UE Message

 28

RRC Connection Establishment

The eNode B allocates the eNode B UE S1-AP Identity to allow the eNode B to identify
the UE within S1 signalling procedures. The MME UE S1-AP Identity (not included
within the Initial UE Message) allows the MME to identify the UE within S1 signalling
procedures

Figure below illustrates the signalling associated with the RRC connection
establishment procedure when the eNode B rejects the RRC Connection Request. The
reject message is returned to the UE using SRB 0 on the CCCH logical channel.
The eNode B may reject the connection establishment request as a result of congestion

UE eNodeB

Signalling for rejected RRC connection establishment

 29

RRC Connection Establishment

The content of the RRC Connection Reject message is presented in Table below.
The message only includes a wait time.

Content of RRC Connection Reject message

Upon receiving an RRC Connection Reject message, the UE starts the T302 timer
with its value set equal to the wait time.

Access Class barring for mobile originating calls, mobile originating signalling and
mobile terminating access is applied

The UE is not allowed to send another RRC Connection Request for those
connection types, and to the same cell, until T302 expires. T302 is stopped if the UE
completes cell reselection. In that case, the UE is permitted to send an RRC
Connection Request to the new cell
 30

RRC Connection Establishment

In contrast to UMTS, LTE requires the higher layers to initiate a new connection
establishment procedure after the UE receives an RRC Connection Reject message.
UMTS allows the RRC Connection Request message to be repeated from the RRC
layer, based upon the value of N300.
 31

RRC Connection Reconfiguration

The 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 IEs related
to the RB establishment.

RRC Connection Reconfiguration Successful

 32

RRC Connection Reconfiguration

RRC Connection Reconfiguration failure

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 the RRC Connection Reconfiguration

complete, otherwise RRC Connection Reconfiguration Fail.
 33

RRC Connection Re-establishment

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.

RRC Connection Re-establishment Successful

 34

RRC Connection Re-establishment

RRC Connection Re-establishment failure

The UE shall initiate the Re-establishment procedure when security has been activated.
The UE initiates the procedure when one of the following conditions are 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)

 35

RRC Connection Release

The purpose of this procedure is to release the RRC Connection, which includes the
release of the signaling connection, the established EPS bearers as well as all radio
resources. E-UTRAN initiates the RRC connection release procedure to a UE in
RRC_Connected.

RRC Connection Release successful

 36

Tracking Areas
 Tracking Areas
37

A Tracking Area corresponds to the Routing Area (RA) used in WCDMA and GSM/GPRS.
The TA consists of a cluster of RBSs having the same Tracking Area Code (TAC).
The TA provides a way to track UE location in idle mode. TA information is used by the MME when paging
idle UE to notify them of incoming data connections.

RBS - Radio Base Stations

 38

Tracking Area Lists

In LTE, the MME provides the UE with a list of tracking areas where the UE registration is valid.
When the MME pages a UE, a paging message is sent to all RBSs in the TA list.

RBS - Radio Base Stations

 39

The MME sends the TA list to the UE during the TA update procedure.
TA updates occur periodically, and when a UE enters a cell with a TAC not in the current TA list.
The TA list makes it possible to avoid frequent TA updates due to ping-pong effects along TA borders. This is
achieved by including the old TA in the new TA list received at TA update.
Previously, the MME includes only the current TA in the TA list. But now the operator can specify up to 15
TAs for each TA to include in the TA list. With the exception of the TAs specified by the operator, the MME
automatically includes the old TA in the TA list to avoid ping-pong updates.
 40

HAPPY LEARNING

MobileComm Professionals, Inc.

www.mcpsinc.com
www.mmentor.com