Understanding Call Flow In-Depth

With Long Term Evolution (LTE) comes a myriad of new and exciting attributes. One of these is the
LTE call flow itself. In fact, call flow and signaling is unique for LTE, and is driven by 3GPP
standards. Call flow is how signaling and sessions are created across an LTE network.

So how does LTE call flow work exactly?

According to Wired n Wireless, the LTE call flow travels through many steps during its end-to-end
signaling between from user equipment (UE) to the evolved node B (eNB), mobility management
entity (MME), home subscribe server (HSS), serving gateway (SGW) and PDN gateway (PGW).

It begins with S1 Setup, where the eNB is initially attached to the network. The eNB supports the
LTE air interface and includes the following functions:

Functions for Radio Resource Management: Radio Bearer Control, Radio

Admission Control, Connection

Mobility Control, Dynamic allocation of resources to UEs in both uplink and

downlink (scheduling)

Selection of an MME at UE attachment when no routing to an MME can be

determined from the information provided by the UE

Routing of User Plane data towards Serving Gateway

Scheduling and transmission of paging messages (originated from the MME)

Scheduling and transmission of broadcast information (originated from the MME

or O&M)

Measurement and measurement reporting configuration for mobility and

scheduling

As long the eNB is functioning properly, the S1 setup will stay intact. Once UE comes up a radio
resource control (RRC) connection is established for communication with the network. After RRC is
established, network attached storage (NAS) signaling begins.

UE then sends an attach request along with a PDN connectivity request to the network. Attach is for
attaching to the network. Once MME receives the attach request, it queries the HSS for
authentication details. HSS then sends the authentication vectors to MME in an authentication info
answer. The next step in call flow for LTE has to do with authentication and security. The network
requests UE for authentication vectors. When the UE provides the same one, MME compares it with
what HSS has sent. If they match, the UE is authenticated. MME manages mobility, UE identities
and security parameters. It includes the following functions:

Non Access Stratum (NAS) signaling and security

Idle mode UE reachability (including control and execution of paging

retransmission)

Tracking Area list management (for UE in idle and active mode)

PDN GW and Serving GW selection;MME selection for handovers with MME

change

Roaming (terminating S6a towards home HSS)

Authentication Bearer management functions including dedicated bearer

establishment

Next security takes over and all NAS messages are encrypted using the security algorithms that
were exchanged. After the LTE call flow moves through the security step, the network creates the
EPS bearers. Then the radio bearers are created and RRC connections are modified accordingly.
Once these radio bearers are created the eNB down link addresses are sent to SGW in GTP
messages. The Serving Gateway is the node that terminates the interface towards EUTRAN. For

each UE associated with the EPS, at a given point of time, there is one single Serving Gateway.
Functions include:

Packet routing and forwarding

The local mobility anchor point for inter eNB handover

E-UTRAN idle mode downlink packet buffering and initiation of network triggered
service request procedure

E-UTRAN idle mode downlink packet buffering and initiation of network triggered
service request procedure

Accounting on user and QoS Class Identifier (QCI) granularity for inter-operator
charging

UL and DL charging per UE, PDN, and QCI

End marker handling

Packet Filtering with TFT

It seems technical, but LTE call flow is a technical process!

To further understand this process, please see the LTE call flow diagram, also created by Wired n
Wireless.

What happens while UE first time switch on?

Fig1.0 Basic Call Flow

Following is a sequence diagram showing not only the message but also basic configurations of each
layer. More detailed description of each layer in the context of full protocol stack will be explained in
Protocol Stack section.
After Power on UE

1) Frequency Search (Scan the entire frequency bands)

2) Cell Search will search for PSS Normally a UE would find multiple cells in this process
3) (a) MIB decoding (b) SIB decoding
4) Cell Selection/ Cell Reselection
5) Initial RACH Process >
6) RRC : RRC Connection Request
7) RRC : RRC Connection Setup
8) RRC : RRC Connection Setup Complete + NAS : Attach Request
9) RRC : DL Information Transfer + NAS : Authentication Request
10) RRC : UL Information Transfer + NAS : Authentication Response
11) RRC : DL Information Transfer + NAS : Security Mode Command
12) RRC : UL Information Transfer + NAS : Security Mode Complete
13) RRC : Security Mode Command
14) RRC : Security Mode Complete
15) RRC : RRC Connection Reconfiguration + NAS : Attach Accept
16) RRC : RRC Connection Reconfiguration Complete + NAS : Attach Complete
17) RRC : RRC Connection Release < MO or MT call > : In MT call, Paging should be
sent.
18) RRC : PRACH Preamble
19) RRC : RACH Response
20) RRC : RRC Connection Request
21) RRC : RRC Connection Setup
22) RRC : RRC Connection Setup Complete + NAS : Service Request
23) RRC : Security Mode Command
24) RRC : Security Mode Complete
25) RRC : RRC Connection Reconfiguration + NAS : Activate Dedicated EPS Bearer Context
Request
26) RRC : RRC Connection Reconfiguration Complete + NAS : Activate Dedicated EPS Bearer
Context Accept
27) RRC : UL Information Transfer + NAS : Deactivate Dedicated EPS Bearer Context Accept
28) RRC : RRC Connection Release
(1)Frequency Search (Scan the entire frequency bands) When the UE powers on, it
checks if it is possible to camp on the last registered PLMN (Public Land Mobile Network). If no any
stored system on the UE, UE will perform the initial cell selection:

Scan all RF frequencies band (ex 900MHz,1800MHz,1900MHz.) and which band

are using by network

Detect the operating frequency with the strongest RSRP

Fig 1.1

2) Cell Search will search for PSS Normally a UE would find multiple cells in this
process In LTE, there are two downlink synchronization signals which are used by the UE to obtain the
cell identity and frame timing.

Primary synchronization signal (PSS)

Secondary synchronization signal (SSS)

The division into two signals is aimed to reduce the complexity of the cell search process
Primary and Secondary Secondary Sync: Cell synchronization is the very first step when UE
wants to camp on any cell. From this, UE acquires physical cell id (PCI), time slot and frame
synchronization, which will enable UE to read system information blocks from a particular network. First,
the UE has to synchronize with the network at the frame and slot level.
i)Detect PSS (Primary Synchronization Signal) for symbol timing

The Primary Synchronization Signal is responsible for slot synchronization.

The Synchronization Signal are sent only on time slots (1st and 11th) of each
frame.

PSS is send at the last OFDM symbol of the 1st and 11th slot of each frame.

ii) Identification of cell ID (0,1,2) : From PSS, UE is also able to obtain physical layer identity (0
to 2).
Query_1: How does UE know to look for the PSS synchronization signal?
Well, UE doesnt need to worry much for this. As, the synchronization signal are always sent
only on the center 62 sub carriers irrespective of the channel bandwidth (1.25,3,5,10,20).
Therefore, UE will look for the central sub carriers, i.e at the last OFDM symbol of the 1st
time slot and again at the last OFDM symbol of the 11th slot. With this UE synchronizes at
the slot level.
Detect SSS (Secondary Synchronization Signal) for radio frame timing :

The Secondary Synchronization Signal is responsible

for frame synchronization.

Using both these signals, the UE derives the Physical Cell ID of

the corresponding cell.

Question_2 : How does UE know to look for the SSS synchronization signal?
Once, when the PSS is identified, SSS is always send at the slot before the PSS is present. In
other words, SSS immediately precedes the PSS.
Question_3 : Lets see how the UE derives the Cell ID using these two signals:
From PSS: PHYSICAL LAYER CELL IDENTITY is derived. It carries the value of 0, 1 and 2.
From SSS: PHYSICAL LAYER CELL IDENTITY GROUP is derived. It can take the value to 0 to
167.
i) Detection of cell ID group (0, .,167): From SSS, UE is able to obtain physical layer cell
identity group number (0 to 167).Using physical layer identity and cell identity group number, UE knows
the PCI for this cell now.
ii) physical layer cell identities (PCI) : In LTE 504 physical layer cell identities (PCI) are allowed
and are divided into unique 168 cell layer identity groups where each group consist of three physical layer
identity. As mentioned earlier, UE detects physical layer identity from PSS and physical layer cell identity
group from SSS. Assuming physical layer identity = 1 and cell identity group=2 then the PCI for given cell
is
PCI = 3*(Physical layer cell identity group)+ physical layer identity = 3*2+1 = 7
Once UE knows the PCI for a given cell, it also knows the location of cell Reference signals as shown in
figure .
Reference signals are used in channel estimation, cell selection / reselection and handover procedures.
So total number of ID become 168 x 3 = 504
Once the UE synchronizes with the network, it proceeds to read MIB and then requires the following info
for camping on a cell:

PLMN id

Tracking Area Id

Cell Id

Radio and Core n/w capabilities (for its n/w selection)

The above information is being broadcast by the network in order to help the UE for its selection process.
This broadcast is known as SYSTEM INFORMATION which is MIB and SIBs.
The call flow for the UE to read the System information is mentioned below:

3)(a)MIB Decoding
i) DL Bandwidth, Number of Transmit Antenna, Reference Signal Transmit Power
ii) System Frame Number (SFN)
iii) PHICH Configurationiv) Transmit every 40 ms(used for HARQ ACK/NACK)
iv)The MIB uses a fixed schedule with a periodicity of 40 ms and repetitions made within 40 ms.
v)The first transmission ofthe MIB is scheduled in subframe #0 of radio frames for which the SFN mod 4 =
0, and repetitions are scheduled insubframe #0 of all other radio frames.

MasterInformationBlock ::= SEQUENCE {

dl-Bandwidth ENUMERATED { n6, n15, n25, n50, n75, n100},
phich-Config PHICH-Config,
systemFrameNumber BIT STRING (SIZE (8)),
spare BIT STRING (SIZE (10))
}

Query: How does the UE read MIB?

The MIB is transmitted on physical channel (BCCH-BCH-PBCH) and it always

occupies the central 72 sub carriers in the Frequency domain irrespective of the
channel bandwidth.

The first transmission of the MIB is scheduled in sub-frame number 0 of radio

frames for which the SFN mod 4 = 0

repetitions are scheduled in sub-frame 0 of all other radio frames

(b)SIB decoding
i) Cell Access Related Information PLMN Identity List, PLMN Identity, TA Code, Cell identity
& Cell Status
ii) Cell Selection Information Minimum Receiver Level
iii) Scheduling Information SI message type & Periodicity, SIB mapping Info, SI Window
length
Till now, the UE has synchronized itself with the Cell with the help of PSS and SSS; followed by reading
the MIB. Now, UE will proceed to read SIB1 and SIB2 which carriers important information for the UE to
select a Cell. To know more about SIBs and its working, click here

After the above process the UE is synchronized with the network in the Downlink direction and have
read SIB1 and SIB 2. Now, it needs to synchronize in the Uplink direction
For this to happen, RAP (Random Access Procedure) is initiated
(5) Initial RACH Process (Random access procedure)
In order to be synchronized with the network, RACH procedure is used. Suppose a UE wants
to access the network, so first it will try to attach or syncronise with the network. In LTE a
separate channel PRACH ( Physical Random Access Channel) is provided for initial access to
the network.
When does UE need to perform Random Access Procedure :- As per specifications,
RACH can be performed in below mentioned scenarios :

Initial Access UE is trying to access the network in RRC idle state.

During RRC connection re-establishment procedure .

Handover

When uplink synchronization is lost :- It means from a certain duration network

has not received anything from UE in uplink.

When UE does not have any PUCCH resources available for SR(Scheduling
Request) .

When timing advance is needed for positioning purpose in RRC connected state
for UE.

To initiate the procedure UE lower layes will send a Random Access Request(RACH Request)
after receiving request from UE RRC. UE receives a lot of information from eNodeB in
System Information (SIB2). Its important to understand those terminologies first. You can
also refer LTE SIB2 parameters section.

RACH Configurations

PRACH Configurations

How UE decides about when and where it needs to send RACH Request:- It is
decided on the basis of parameters received in SIB2 PRACH configurations. UE can use 6
Resource blocks for sending the RACH Request.
From PRACH Config Index There is a mapping in spec 36211 table 5.7.1-2 from which
UE can find the available subframes where it can send a RACH. For example:- Prach Config
index value = 7, From table it is clear that UE can send a RACH Req in any system frame
but subframe should be 2 and 7.
From PRACH Frequency Offset This value is also received in SIB2 by UE. It governs
which frequency resource UE can use for the RACH Req. Example:- If the value of PRACH
Freq Offset is 10. UE can use the 6 PRBs starting from PRB 10 for RACH Request.
What exactly RACH Request contains:1. Preamble Index :- There are total of 64 preambles available which are divided into two
groups Group A and Group B. UE decides the preamble index from a group on the basis of
parameters received in SIB2:numberofRaPreambles :- eNodeB sends this value in SIB2 which denotes the total
number of preambles available for UE to send a Rach Request.
sizeOfRaPreamblesGroupA :- It represents the number of preambles available within
Group A.

So number of preamble in Group B

= numberofRaPreambles sizeOfRaPreamblesGroupA
MessageSizeGroupA :- It is used for selecting a preamble from a group. Its value is in
bits.
Now UE needs to decide the group from which it needs the preamble. Group is decided on
the basis of size of MSG3( RRC connection request ).
If

Msg3 size > messageSizeGroupA , preamble will be selected from GroupB else

preamble will be selected from Group A.

The actual formula for selecting a preamble is given in spec 36321 sec 5.1.2. That contain
factors other than MSG3 size as well. But mainly this is how UE decides the Group. From the
selected group, randomly UE selects a preamble index.
How UE decides the Power used for Rach request Transmission:- Now UE need to
decide the power which will be used for RACH Request transmission.
Power is decided on the factors received in SIB2 as:preambleInitialReceivedtargetPower:- Power factor which will be used for first transmission of
Rach Request.Value varies from -120dBm to -90 dBm .
powerRampingStep:- This is mainly used when eNodeB is not able to detect the Rach Request then
UE will re transmit the RACH Request by increasing the power to powerRampingStep factor.
power used for Rach Request transmission
= preambleInitialReceivedTargetPower + DELTA_PREAMBLE +
(PREAMBLE_TRANSMISSION_COUNTER 1) * powerRampingStep
DELTA_PREAMBLE = This is preamble format based delta offset. There are four formats available for
preamble which are called as preamble formats. We will be explaining them in detail later. Most of the
time preamble format 0 is used.
For Example:In Sib2, preambleInitialReceivedtargetPower = -100
powerRampingStep = 2
First Transmission of Rach Request:PREAMBLE_TRANSMISSION_COUNTER = 1
For preamble format 0, DELTA_PREAMBLE = 0
Power used = -100 + 0 + (1- 1) *2 = -100
Suppose eNodeB is not able to receive it
Second transmission of Rach request:PREAMBLE_TRANSMISSION_COUNTER = 2 Power used = -100 + 0 + (2-1) * 2

= -98

UE will send the RACH Request containing these values in the specified subframe by using the specified
resources.
What is steps followed by UE for sending a Rach request:-

Fig 1.2 Step followed by UE for sending RACH request

How eNodeB behaves after receiving Random Access Request:1. Allocation of temporary RNTI (Radio Network temporary Identifier):- After
receiving RACH Request, enodeB allocates a temporary identity to the UE which is made
permanent after successful RACH procedure. The permanent identity is called as CRNTI (Cell
RNTI). This TC-RNTI is transmitted to the UE as part of RACH Response which will be used
for further communication between the UE and the network.
2. Timing Advance: - After receiving RACH Request, eNodeB PHY (Physical layer)
calculates the timing advance which is transmitted to the UE as part of response message.
As part of Rach response, absolute Timing advance value is transmitted.
Timing advance calculation for RACH Response message:As per 3GPP spec,
Ts = 1/(15000 * 2048) seconds
NTA = TA * 16 where TA = 11 bit value for random access response varying from 0,1,2 .
1282
NTA = Amount of time alignment
So transmission of uplink radio frame from the UE shall start = (NTA + NTA offset) * Ts
NTA offset = 0 ( For type 1 frame structure) = ((NTA + 0) * 1)/ (15000 *
2048)
= (TA * 16)/(15000 * 2048 )seconds
Mainly this timing advance fundamental is used for eNodeB PHY to receive the UE message
at correct timing. It is possible that UE is far away from the eNodeB , so for eNodeB to
receive the data from UE at correct timing this timing adjustments are done.

If timing advance is received in subframe n, UE should do the adjustment from the

starting of subframe (n +6). After the Random access response message, enodeB does
not send absolute timing advance value. It will send a value which UE will use to adjust the
already stored timing advance value. We will explain this in Timing advance section later.
Refer spec 36213 sec 4.2.3 and spec 36211 sec 8.1 for details about timing adjustments
3. Allocate uplink Resources ( UL GRANT ):- eNodeB will provide the required
information in Random Access Response(RAR) message for UE to send the MSG3( RRC
Connection Request) .
UL Grant is a 20 bit message with contents from MSB to LSB as:

Hopping Flag :- This is 1 bit of information which governs whether frequency

hopping is enabled or not. If the value of the bit is 1 and resource block
assignment is type 0 , UE should perform PUSCH frequency hopping.

What is Frequency Hopping:

As we know that RB allocation is contiguous in uplink which means eNodeB

allocates continuous RBs in frequency domain. As in downlink we have multiple
resource allocation policies to achieve frequency diversity. So in uplink, to achieve
frequency diversity Frequency Hopping is used. eNodeB communicates required
parameters to UEs in SIB2 which are needed for performing frequency hopping
at UE.

For Example:Suppose eNodeB has allocated 5 RBs to a particular UE in uplink as shown below.

Fig 1.3 1subframe time domain

It is clear that the allocation in uplink in terms of RB is contiguous. But eNodeB

has enabled frequency hopping for this UE.

We are able to achieve frequency diversity in contiguous allocation as well due to

hopping. In the figure above, same color represents the hopping of UE data in
different slots for a particular RB.

There is a lot more to discuss in frequency hopping. we will be taking it later in

that particular section.

As of now,we can summarize it as :- Frequency hopping is used to provide

frequency diversity in uplink. Its main advantage is, suppose in frequency
domain at RB0 channel conditions are bad but at RB3 conditions are good. So in
that case, UE can decode the data of RB0 after combining the same colored data.

Resource Block Assignment :- It is 10 bits of information embedded in UL Grant

message.

How UE decodes the 10 bit RB Assignment :According to spec 36213 sec 6.1.1,UE decodes it as:If NULRB <= 44
Truncate the fixed size resource block assignment to its b least significant bits where,
b = ceiling ( log (N
2

UL
RB

* (N

UL
RB

+ 1)/2) )

and interpret the truncated resource block assignment according to the rules for a regular
DCI format 0
else Insert b most significant bits with value zero where, b = (ceiling ( log (N
2

UL
RB

* (N

UL
RB

+ 1)/2)

)) 10
and interpret the expanded resource block assignment according to the rules for a regular
DCI format 0
For Example :Lets assume the 10 bits of the information as :- 1 1 1 1 1 1 1 1 1 1
Assume Total number of uplink RBs in system = 100
b = (ceiling ( log (N
2

= (ceiling ( log
=

(ceiling (

UL
RB

* (N

UL
RB

+ 1)/2) )) 10

2(100 *101/2))) 10

12.3)) 10

= 13 -10
=3
So, RB assignment will be :- 0 0 0 1 1 1 1 1 1 1
RB assignment ( value in decimal) = 127
Now we need to interpret it according to the rules of DCI format 0.
Number of RBs allocated = Floor( 127 /100 ) + 1
=1+1
=2
RB start index = 127 mod 100
= 27

Modulation and Coding scheme to be used by UE:- It is 4 bits of information in

UL grant message whose value varies from 0 to 15. The modulation and coding is
determined by UE from MCS indices 0 to 15 in table 8.6.1.1 from spec 36213.

Power used by UE for PUSCH :- It is indicated in 3 bits as a TPC command whose

value varies from 0 to 7. TPC command to power mapping is mentioned in table
below

Fig 1.4

UL delay :- 1 bit of information which can be set to 0 or 1. It indicates whether

the delay of PUSCH is introduced or not.

CSI field :- This 1 bit of information determines whether an aperiodic CQI, PMI
and RI report can be included in the PUSCH transmission. For contention based
Random access CSI field is reserved.

eNodeB will prepare a response ( Random Access Response) with above discussed
fields and send it to UE. But we need to understand the timing of response
message corresponding to Rach Request. Timing w.r.t to Rach Request and
Random Access Response:- RAR Response Window is the value transmitted in SIB2.

RACH(Contention/Non-Contention)
There are two types of RAP(RACH(Contention/Non-Contention)):

Contention based RAP

Non-contention based RAP

Contention based RAP

In contention based, multiple UEs attempt to connect to the network at the same time. The
eNB is intelligent enough to tackle this situation because every UE should be unique to the
network.
The UEs can always send the same Preamble ID to the network, thereby resulting on
collisions. This kind of collision is called Contention and is known as Contention based
RACH Process. The network would go through additional process to resolve these contention
and hence this process is called Contention Resolution step.
The below mentioned call flow would explain elaborately:

1. In the first message the UE provides an indication to the network about its resource
requirement. This carries the Preamble ID, RA-RNTI
Query_4: How does UE gets or selects these parameters:
a. Most of the information is passed on to the UE through SIB2 (click here, to know more
about SIB2 parameters)
i. UE MAC layer has to select the Preamble sequence (Group A or Group B)
ii. UE will configure itself with the max retires it will try for sending RAP (if it doesnt
receive RAR)

iii. Also, after every retry, how much power level has to be increased for transmitting the
RAP
iv. UE MAC layer constructs the RAP message and passes it to the UE PHY layer. UE PHY
layer will transmit this message through PRACH
v. Once the UE has transmiited the RAP on PRACH, it will start looking for RAR immediately
after 3 sub-frames. This number i.e. 3 sub-frame is specified by 3GPP.
Query_5: How long should UE monitor the frames for RAR?
This sub-frame number is again specified in SIB2 and is known as window length; so, after
the 3 sub-frames as mentioned above, UE will start looking for RAR in the sub-frames as
mentioned by the Window length. If by that time UE doesnt receive RAR, it will go back to
transmit RAP
2. The eNB conveys the resources reserved for this UE along with the Timing Advance (TA),
Preamble ID and T-CRNTI (a number generated by eNB and asks the UE to send the RRC
connection)
3. UE sends the RRC connection Request using resources given by the eNB. It also sends the
identifier (CRI) to the eNB which is used to resolve the Contention.
4. The eNB runs an algorithm and generates C-RNTI which will be a permanent ID for the UE
till the connection is alive. The eNB sends the UE identifier. In this step, the UE which has
received the ID continues while other UEs will back off and try again.
Scenario:
Multiple UEs attempt to access the network:
1. So, the UEs initiates RACH with same Preamble sequence, RA-RNTI
2. Therefore, the UEs will receive the same T-C-RNTI and resource allocation from eNB
3. All UEs would send msg 3 (RRCconnectionRequest) message through the same resource
allocation to the Network
4. Once, when msg3 is transmitted, two Timers are started:
a. T300 : Transmission of RRCconnectionRequest
b. Contention Resolution Timer: broadcasted in SIB2. If the UE doesnt receive msg4
(Contention Resolution message) within this timer, then it go back to Step 1 i.e. transmitting
RAP. If there is a HARQ NACK for msg3 (RRCconnectionRequest) and it has to be retransmitted then this Contention Resolution Timer will be re-started
Query_6: Now the big question: How should the eNB behave?
1. One: The signals act as interference to each other and eNB decode neither of them. In
this case, none of the UE would have any response (HARQ ACK) from eNB and all UE will go
back to Step 1.
2. Second: The eNB would successfully decode the message from only one UE and fail to
decode from others. The decoded UE will get HARQ ACK from eNB
3. Third: eNB receives msg3 (RRCconnectionRequest) from both the UEs. Here, eNB will
send msg4 (Contention Resolution) with MAC CRI (Contention Resolution Identity) to both the
UEs. This CRI will carry a reflection of the RRCconnectionRequest as generated by one of the
UE. The MAC layer of the UE will match the CRI (as received from msg4) with the CRI
embedded in the RRCconnectionRequest. If it matches, then the UE will proceed to

decode RRCconnectionSetupand the other UEs will back off and return to Step1, i.e start the
RA procedure again.
Contention Resolution process is again of two types:
1. MAC based Contention Resolution
=> C-RNTI on PDCCH
=> uses the DCCH logical channel
=> used in HO scenarios
==>The rule is: if the UE has a valid C-RNTI and is going for RA procedure then it will be a
MAC based Contention Resolution procedure
2. L1 based Contention Resolution
=> CRI (Contention Resolution Identity) on DL-SCH based
=> Contention Resolution is addressed to T-CRNTI
=> uses CCCH logical channel
==>The rule is: if the UE doesnt has a valid C-RNTI and is going for RA procedure then it
will be L1 based Contention Resolution procedure
Non-contention based RAP
This procedure is always initiated from network in case of a handover. For this procedure, the
eNB reserves a set of preamble sequence. When this type of scenario is encountered the
eNB allocates the set from this reserved pool.This entire procedure is controlled by the eNB.
Hence. no question of collision.
The call flow is mentioned below:

Non Contention Based RAP

E-UTRA
band
1
2
3
4
5
6
7
8
9
10
11
12
13
14

FDL_Low
(MHz)

2110
1930
1805
2110
869
875
2620
925
1844.9
2110
1475.9
728
746
758

NDL_Offset
0
600
1200
1950
2400
2650
2750
3450
3800
4150
4750
5000
5180
5280

downlink
EARFCN(NDL)
0-599
600-1199
1200-1949
1950-2399
2400-2649
2650-2749
2750-3449
3450-3799
3800-4149
4150-4749
4750-4999
5000-5179
5180-5279
5280-5379

FUL_Low(MHz) NUL_Offset
1920
1850
1710
1710
824
830
2500
880
1749.9
1710
1427.9
698
777
788

18000
18600
19200
19950
20400
20650
20750
21450
21800
22150
22750
23000
23180
23280

uplink EARFCN
(NUL)
18000-18599
18600-19199
19200-19949
19950-20399
20400-20649
20650-20749
20750-21449
21450-21799
21800-22149
22150-22749
22750-22999
23000-23179
23180-23279
23280-23379