Rach:: From Power-On To PRACH
Rach:: From Power-On To PRACH
Rach:: From Power-On To PRACH
i) UE is Off
ii) Power On UE
iii) < Frequency Search >
iv) Time and Frame Synchronization : In this process, PSS and SSS will be
decoded as well.
v) PCI (Physical Cell ID) detection
vi) MIB decoding : UE can figure out System Bandwidth and Transmission Mode in
this process. (As you see in Downlink Framestructure, MIB/PBCH is located at the
6 RBs around the center frequency. So the success of MIB decoding does not
guarantee that signal quality across the whole band is good)
vii) Detect CSR (Cell Specific Reference Signal) and perform Channel Estimation
and Equalization. In this process, UE will detect/measure reference signal across
the whole system bandwidth. So RSRP/RSRQ measured at this step can be a
good indicator for overall signal quality.
viii) Decode PDCCH and extract DCI information for SIB. PDCCH is spread across
the whole bandwidth, so the signal quality across the whole bandwidth should be
good enough for this step.
viii) SIB deconding (SIB1 should be decoded first and then SIB2 and then
remaining SIBs)
ix) < Cell Selection > : UE may find multiple suitable cells, but it try camp on to
HPLM cell with the highest priority
x) < Initial RACH Process >
Note 1: UE may repeat the step iii) ~viii) multiple times before it finds a suitable cell.
This sequence is part of Cell Search process.
Note 2: PCI (step v) will be automatically derived as a result of step iv).
In this kind of contention based RACH process, Network would go through additional
process at later step to resolve these contention and this process is called "Contention
Resolution" step.
But there is some cases that these kind of contention is not acceptable due to some
reason (e.g, timing restriction) and these contention can be prevented. Usually in this
case, the Network informs each of the UE of exactly when and which preamble signature
it has to use. Of course, in this case Network will allocate these preamble signature so
that it would not collide. This kind of RACH process is called "Contention Free" RACH
procedure. To initiate the "Contention Free" RACH process, UE should be in Connected
Mode before the RACH process as in Handover case.
To answer to this question, you need to refer to 3GPP specification TS36.211 - Table
5.7.1-2. This table would give you at which frame and subframe that UE is allowed to
transmit a PRACH Preamble. As you see at this table, the prach preamble timing and
prach preamble type is determined by PRACH Configuration Index. The, how PRACH
Configuration Index is determined ? It is determined by SIB2 parameter prach-
ConfigIndex.
How does Network knows exactly when UE will transmit the RACH?
It is simple. Network knows when UE will send the RACH even before UE sends it
because Network tells UE when the UE is supposed to transmit the RACH. (If UE fails to
decode properly the network information about the RACH, Network will fail to detect it
even though UE sends RACH).
How to Generate 64 PRACH Preamble Sequences?
s described above, the maximum number of PRACH Sequence a UE can use in a cell is
64. How these 64 different types of PRACH Sequence can be generated? The procedure
is as follows.
i) Generate a Zaddoff Chu sequence (849 samples) using rootSequenceIndex (let's call
this sequence as 'base sequence')
ii) Generate 64 different sequency by doing cyclic shift of the base sequence. The cyclic
shift interval is determined by Ncs and the Ncs is determined
by zeroCorrelationZoneConfig and Highspeedflag.
rootSequenceIndex
there are 838 root Zadoff-Chu sequences available for preambles. The length of each
root sequence is 839. RootConfigurationIndex informs the UE on which sequence to use
via SIB2 as shown below.
sib2
radioResourceConfigCommon
rach-ConfigCommon
preambleInfo
numberOfRA-Preambles: n52 (12)
powerRampingParameters
powerRampingStep: dB2 (1)
preambleInitialReceivedTargetPower: dBm-104 (8)
ra-SupervisionInfo
preambleTransMax: n6 (3)
ra-ResponseWindowSize: sf10 (7)
mac-ContentionResolutionTimer: sf48 (5)
maxHARQ-Msg3Tx: 4
...
prach-Config
rootSequenceIndex: 22
prach-ConfigInfo
prach-ConfigIndex: 3
..0. .... highSpeedFlag: False
zeroCorrelationZoneConfig: 5
prach-FreqOffset: 4
...
additionalSpectrumEmission: 1
timeAlignmentTimerCommon: infinity (7)
This rootSequenceIndex is a logical value. The real number (physical number) is called
'u' which is a variable used to generate PRACH ZaddOff-Chu Sequence.
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). It's important to understand
those terminologies first.
You can also refer LTE(Long Term Evolution) SIB2 parameters section.
1. RACH Configurations
2. 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 PRB's starting from PRB 10 for RACH
Request.
numberofRaPreambles :- eNodeB sends this value in SIB2 which denotes the total number of preambles
available for UE to send a Rach Request.
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 ).
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.
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
UE will send the RACH Request containing these values in the specified subframe by using the specified
resources.
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.
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) .
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 RB's 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 UE's in SIB2 which are needed for performing frequency hopping at UE.
For Example:-
Suppose eNodeB has allocated 5 RB's to a particular UE in uplink as shown below.
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.
If NULRB <= 44
Truncate the fixed size resource block assignment to its b least significant bits where,
b = ceiling ( log2(NULRB * (NULRB + 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 ( log2(NULRB * (NULRB + 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 RB's in system = 100
= 13 -10
= 3
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.
RAR Response Window is the value transmitted in SIB2. You can refer the LTE basic section for more
details. Its value is in subframes.