SlideShare a Scribd company logo
1 of 14
3GPP TS 36.300 (10.1.5) & 36.211 (5.7)
Composed by –AALEKH JAIN
RACH Procedure
Content Coverage
Introduction RACH Pre-conditions When RACH occurs?
Types of RACHLayer Interaction RACHPRACH
PRACH Power
Introduction
RACH stands for Random Access Channel. This is the first message from UE to eNB when you power it on.
The main purpose of RACH can be described as follows.
i. Achieve UP link synchronization between UE and eNB
ii. Obtain the resource for Message 3 (e.g, RRC Connection Request)
In most of the communication, the most important precondition is to establish the timing synchronization
between the receiver and transmitter. In LTE, the synchronization in downlink (Transmitter = eNB, Receiver =
UE), is achieved by the special synchronization channel. This downlink sync signal gets broadcasted to
everybody and it is get transmitted all the time with a certain interval.
However in Uplink (Transmitter = UE, Receiver = eNB), it is not efficient if UE is using this kind of
broadcasting/always-on synchronization mechanism. In case of uplink, this synchronization process should meet
following criteria
i. The synchronization process should happen only when there is immediate necessity
ii. The synchronization should be dedicated to only a specific UE
Another purpose of RACH process is to obtain the resource for Msg3 (Message 3). RRC Connection Request is
one example of Msg3.
RACH Preconditions
Before UE decided to send RACH signal (RACH preamble), there are many preconditions to be met.
Following procedure is to list each steps from Power-On to Initial 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.
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.
ix. SIB deconding (SIB1 should be decoded first and then SIB2 and then remaining SIBs)
x. < Cell Selection > : UE may find multiple suitable cells, but it try camp on to HPLM cell with the highest
priority
xi. < Initial RACH Process >
When RACH occurs?
The random access procedure is performed for the following events related to the PCell:
• Initial access from RRC_IDLE
• RRC Connection Re-establishment procedure
• Handover, except for NB-IoT or when RACH-less HO is configured
• DL data arrival during RRC_CONNECTED requiring random access procedure: E.g. when UL synchronisation
status is "non-synchronised".
• UL data arrival during RRC_CONNECTED requiring random access procedure: E.g. when UL synchronisation
status is "non-synchronised" or there are no PUCCH resources for SR available.
• For positioning purpose during RRC_CONNECTED requiring random access procedure: E.g. when timing
advance is needed for UE positioning.
The random access procedure is also performed on a SCell to establish time alignment for the corresponding
sTAG. For E-UTRA connected to 5GC, the random access procedure is also performed for the transition from
RRC_INACTIVE.
In DC, the random access procedure is also performed on at least PSCell upon SCG addition/modification, if
instructed, or upon DL/UL data arrival during RRC_CONNECTED requiring random access procedure. The UE
initiated random access procedure is performed only on PSCell for SCG.
Types of RACH
the random access procedure takes two distinct forms:
o Contention
o Non-contention based (applicable to only handover, DL data arrival, positioning and obtaining timing
advance alignment for a sTAG)
When a UE transmit a PRACH Preamble, it transmits with a specific pattern and this specific pattern is called a
"Signature". In each LTE cell, total 64 preamble signatures are available and UE select randomly one of these
signatures.
There is some possibility that multiple UEs send PRACH with identical signatures. It means the same PRACH
preamble from multiple UE reaches the NW at the same time, this kind of PRACH collision is called Contention
and the RACH process that allows this type of Contention is called Contention based RACH Process. In this kind
of 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. 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
Non-Contention RACH procedure. To initiate the "Contention Free" RACH process, UE should be in Connected
Mode before the RACH process as in Handover case.
Contention based RACH
1) Random Access Preamble on RACH in uplink:
RA-RNTI, indication for L2/L3 message size
2) Random Access Response generated by MAC on DL-SCH:
Timing Advance, T_C-RNTI, UL grant for L2/L3 message
3) First scheduled UL transmission on UL-SCH:
L2/L3 message depending on RACH occurrence
4) Contention Resolution on DL:
Early contention resolution, Addressed to:
- The Temporary C-RNTI on PDCCH for initial access and after radio
link failure;
- The C-RNTI on PDCCH for UE in RRC_CONNECTED.
HARQ feedback is transmitted only by the UE which detects its own UE
identity, as provided in message 3, echoed in the Contention Resolution
message;
Non-Contention based RACH
0) Random Access Preamble assignment via dedicated signalling in DL:
eNB assigns to UE a non-contention Random Access Preamble
1) Random Access Preamble on RACH in uplink:
UE transmits the assigned non-contention Random Access Preamble
2) Random Access Response on DL-SCH:
Random Access Response (Timing Advance, C-RNTI, UL grant for
L2/L3 message)
After receiving UL grant, UE sends the L2/L3 message depending on the
RACH occurrence
Layer Interaction RACH
Random access procedure described above is modelled below from L1 and L2/3 interaction point of view. L2/L3
receives indication from L1 whether ACK is received or DTX is detected after indication of Random Access
Preamble transmission to L1. L2/3 indicates L1 to transmit first scheduled UL transmission (RRC Connection
Request in case of initial access) if necessary or Random Access Preamble based on the indication from L1.
Physical RACH Preamble (PRACH)
The physical layer random access preamble, consists of a cyclic prefix of length TCP and a sequence part of
length TSEQ. UE determines which Preamble format it has to use by following table. PRACH Configuration Index
in sib2 determines the Preamble Format to be used.
Ts is defined as 1/(15000 x 2048) seconds (=0.03255 us)
RACH information in sib2
Used in PRACH tx
Power calculations
Decides which
preamble format
will be used
Decides preamble
groups to be used
Calculates NCS -
RACH signal cycle
shift
Used in PRACH tx
Power calculations
Used in PRACH
retransmission
Power calculations
PRACH Power
The RACH Preamble (PRACH) Power (P_PRACH) is determined by the following equation.
P_PRACH = min{P_CMAX, PREAMBLE_RECEIVED_TARGET_POWER + PL}
PL stands for Path Loss between eNB Tx antenna and UE Rx Antenna. PREAMBLE_RECEIVED_TARGET_POWER is
the PRACH power that eNB expect to receive.
i. Calculate PREAMBLE_RECEIVED_TARGET_POWER + PL
ii. if the calculated value is less than P_CMAX(23 dBm), transmit the PRACH at the calculated value
iii. if the calculated value is greater than P_CMAX(23 dBm), transmit the PRACH at P_CMAX
< Case 1 > When UE send the first PRACH
PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower(in SIB2) + DELTA_PREAMBLE
< Case 2 > When UE retransmit PRACH
PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower(in SIB2) + DELTA_PREAMBLE
+ (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep
PREAMBLE_TRANSMISSION_COUNTER starts from 1 at the
first PRACH and get increased by 1 every time PRACH get
retransmitted.
DELTA_PREAMBLE is determined by which Preamble Format
is used.
PRACH Power
PL = eNB Transmitter Power - UE Reciever Power, where eNB Transmitter Power is referenceSignalPower.
Let's take an example from above shared sib2 information
preambleInitialReceivedTargetPower = -108 (dBm)
referenceSignalPower = 21
prach-ConfigIndex: 3 ==> PREAMBLE FORMAT is Format 0.
powerRampingStep = dB4
Now assume that UE measures RSRP at its receiver antenna = -90dBm
From these information,
PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower(in SIB2) + DELTA_PREAMBLE
= -108 + 0 = -108
PL = (referenceSignalPowerin SIB2) - (RSRP measuredt at UE) = 21 - (-90) = 111
Initial P_PRACH = min{23, -108+111 } = min(23, 3) = 3 dBm
First Retransmittion P_PRACH = min{23,-108+111+(2-1)*4} = min(23,7) = 7 dBm
Thanks

More Related Content

What's hot

Lte kpi accessability
Lte kpi accessabilityLte kpi accessability
Lte kpi accessabilityDheeraj Yadav
 
Lte mac presentation
Lte mac presentationLte mac presentation
Lte mac presentationPraveen Kumar
 
Radio Measurements in LTE
Radio Measurements in LTERadio Measurements in LTE
Radio Measurements in LTESofian .
 
2 g training optimization
2 g training optimization2 g training optimization
2 g training optimizationAhmed Gad
 
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentation
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentationNokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentation
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentationmohammed khairy
 
Ericsson optimization opti
Ericsson optimization optiEricsson optimization opti
Ericsson optimization optiTerra Sacrifice
 
Ericsson important optimization parameters
Ericsson important optimization parametersEricsson important optimization parameters
Ericsson important optimization parametersPagla Knight
 
395317358-LTE-Resource-Usage-Optimization.pptx
395317358-LTE-Resource-Usage-Optimization.pptx395317358-LTE-Resource-Usage-Optimization.pptx
395317358-LTE-Resource-Usage-Optimization.pptxSudheeraIndrajith
 
4 g lte_drive_test_parameters
4 g lte_drive_test_parameters4 g lte_drive_test_parameters
4 g lte_drive_test_parametersAryan Chaturanan
 
LTE Call Processing and Handover
LTE Call Processing and HandoverLTE Call Processing and Handover
LTE Call Processing and HandoverSitha Sok
 
Lte power control
Lte power controlLte power control
Lte power controlPranay Akul
 
LTE KPI and PI Formula_NOKIA.pdf
LTE KPI and PI Formula_NOKIA.pdfLTE KPI and PI Formula_NOKIA.pdf
LTE KPI and PI Formula_NOKIA.pdfVahidZibakalam3
 

What's hot (20)

Cs fallback feature
Cs fallback featureCs fallback feature
Cs fallback feature
 
Paging in LTE
Paging in LTEPaging in LTE
Paging in LTE
 
Lte kpi accessability
Lte kpi accessabilityLte kpi accessability
Lte kpi accessability
 
Lte mac presentation
Lte mac presentationLte mac presentation
Lte mac presentation
 
Radio Measurements in LTE
Radio Measurements in LTERadio Measurements in LTE
Radio Measurements in LTE
 
2 g training optimization
2 g training optimization2 g training optimization
2 g training optimization
 
Umts call-flows
Umts call-flowsUmts call-flows
Umts call-flows
 
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentation
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentationNokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentation
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentation
 
Ericsson optimization opti
Ericsson optimization optiEricsson optimization opti
Ericsson optimization opti
 
Sdcch
SdcchSdcch
Sdcch
 
Ericsson important optimization parameters
Ericsson important optimization parametersEricsson important optimization parameters
Ericsson important optimization parameters
 
GSM Idle Mode Behavior
GSM Idle Mode BehaviorGSM Idle Mode Behavior
GSM Idle Mode Behavior
 
395317358-LTE-Resource-Usage-Optimization.pptx
395317358-LTE-Resource-Usage-Optimization.pptx395317358-LTE-Resource-Usage-Optimization.pptx
395317358-LTE-Resource-Usage-Optimization.pptx
 
Channel element
Channel elementChannel element
Channel element
 
4 g lte_drive_test_parameters
4 g lte_drive_test_parameters4 g lte_drive_test_parameters
4 g lte_drive_test_parameters
 
LTE Call Processing and Handover
LTE Call Processing and HandoverLTE Call Processing and Handover
LTE Call Processing and Handover
 
gsm-kpi-optimization
 gsm-kpi-optimization gsm-kpi-optimization
gsm-kpi-optimization
 
Lte power control
Lte power controlLte power control
Lte power control
 
LTE KPI and PI Formula_NOKIA.pdf
LTE KPI and PI Formula_NOKIA.pdfLTE KPI and PI Formula_NOKIA.pdf
LTE KPI and PI Formula_NOKIA.pdf
 
RRC Vs RAB
RRC Vs RABRRC Vs RAB
RRC Vs RAB
 

Similar to LTE RACH Procedure

54495209 umts-3 g-wcdma-call-flows
54495209 umts-3 g-wcdma-call-flows54495209 umts-3 g-wcdma-call-flows
54495209 umts-3 g-wcdma-call-flowsNoppadol Loykhwamsuk
 
5G PRACH Document-KPIs Improvemnt and understanding
5G PRACH Document-KPIs Improvemnt and understanding5G PRACH Document-KPIs Improvemnt and understanding
5G PRACH Document-KPIs Improvemnt and understandingQasimQadir3
 
(SIB)System Information Blocks in LTE.docx
(SIB)System Information Blocks in LTE.docx(SIB)System Information Blocks in LTE.docx
(SIB)System Information Blocks in LTE.docxmahmoudsafaei1987
 
WCDMA Air Interface
WCDMA Air InterfaceWCDMA Air Interface
WCDMA Air InterfaceSujeet Kumar
 
56990278 umts-interview-questions-and-answer
56990278 umts-interview-questions-and-answer56990278 umts-interview-questions-and-answer
56990278 umts-interview-questions-and-answerMoses Daramola
 
Umts interview questions
Umts interview questionsUmts interview questions
Umts interview questionsKaran Singh
 
Distributed contention based mac protocol for cognitive radio
Distributed contention based mac protocol for cognitive radioDistributed contention based mac protocol for cognitive radio
Distributed contention based mac protocol for cognitive radioIffat Anjum
 
Analytical Research of TCP Variants in Terms of Maximum Throughput
Analytical Research of TCP Variants in Terms of Maximum ThroughputAnalytical Research of TCP Variants in Terms of Maximum Throughput
Analytical Research of TCP Variants in Terms of Maximum ThroughputIJLT EMAS
 
RACH procedure in LTE
RACH procedure in LTERACH procedure in LTE
RACH procedure in LTEdebamoha
 
Wcdmahelp blogspot-com 3 g interview
Wcdmahelp blogspot-com 3 g interviewWcdmahelp blogspot-com 3 g interview
Wcdmahelp blogspot-com 3 g interviewBouziane Beldjilali
 
Lte random-access-procedure
Lte random-access-procedureLte random-access-procedure
Lte random-access-procedureNdukwe Amandi
 
Lte random-access-procedure
Lte random-access-procedureLte random-access-procedure
Lte random-access-procedurePrashant Sengar
 

Similar to LTE RACH Procedure (20)

54495209 umts-3 g-wcdma-call-flows
54495209 umts-3 g-wcdma-call-flows54495209 umts-3 g-wcdma-call-flows
54495209 umts-3 g-wcdma-call-flows
 
5G PRACH Document-KPIs Improvemnt and understanding
5G PRACH Document-KPIs Improvemnt and understanding5G PRACH Document-KPIs Improvemnt and understanding
5G PRACH Document-KPIs Improvemnt and understanding
 
LTE-Prach.pptx
LTE-Prach.pptxLTE-Prach.pptx
LTE-Prach.pptx
 
Lte imp
Lte impLte imp
Lte imp
 
(SIB)System Information Blocks in LTE.docx
(SIB)System Information Blocks in LTE.docx(SIB)System Information Blocks in LTE.docx
(SIB)System Information Blocks in LTE.docx
 
WCDMA Air Interface
WCDMA Air InterfaceWCDMA Air Interface
WCDMA Air Interface
 
56990278 umts-interview-questions-and-answer
56990278 umts-interview-questions-and-answer56990278 umts-interview-questions-and-answer
56990278 umts-interview-questions-and-answer
 
Umts interview questions
Umts interview questionsUmts interview questions
Umts interview questions
 
Distributed contention based mac protocol for cognitive radio
Distributed contention based mac protocol for cognitive radioDistributed contention based mac protocol for cognitive radio
Distributed contention based mac protocol for cognitive radio
 
A Performance Comparison of TCP Protocols
A Performance Comparison of TCP Protocols A Performance Comparison of TCP Protocols
A Performance Comparison of TCP Protocols
 
Mcseminar
McseminarMcseminar
Mcseminar
 
Analytical Research of TCP Variants in Terms of Maximum Throughput
Analytical Research of TCP Variants in Terms of Maximum ThroughputAnalytical Research of TCP Variants in Terms of Maximum Throughput
Analytical Research of TCP Variants in Terms of Maximum Throughput
 
RACH procedure in LTE
RACH procedure in LTERACH procedure in LTE
RACH procedure in LTE
 
Lte mac
Lte macLte mac
Lte mac
 
IEEE 802.11
IEEE 802.11IEEE 802.11
IEEE 802.11
 
Wcdma channels
Wcdma channelsWcdma channels
Wcdma channels
 
Study
StudyStudy
Study
 
Wcdmahelp blogspot-com 3 g interview
Wcdmahelp blogspot-com 3 g interviewWcdmahelp blogspot-com 3 g interview
Wcdmahelp blogspot-com 3 g interview
 
Lte random-access-procedure
Lte random-access-procedureLte random-access-procedure
Lte random-access-procedure
 
Lte random-access-procedure
Lte random-access-procedureLte random-access-procedure
Lte random-access-procedure
 

Recently uploaded

JavaScript Usage Statistics 2024 - The Ultimate Guide
JavaScript Usage Statistics 2024 - The Ultimate GuideJavaScript Usage Statistics 2024 - The Ultimate Guide
JavaScript Usage Statistics 2024 - The Ultimate GuidePixlogix Infotech
 
Decarbonising Commercial Real Estate: The Role of Operational Performance
Decarbonising Commercial Real Estate: The Role of Operational PerformanceDecarbonising Commercial Real Estate: The Role of Operational Performance
Decarbonising Commercial Real Estate: The Role of Operational PerformanceIES VE
 
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Victor Rentea
 
Less Is More: Utilizing Ballerina to Architect a Cloud Data Platform
Less Is More: Utilizing Ballerina to Architect a Cloud Data PlatformLess Is More: Utilizing Ballerina to Architect a Cloud Data Platform
Less Is More: Utilizing Ballerina to Architect a Cloud Data PlatformWSO2
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FMESafe Software
 
Stronger Together: Developing an Organizational Strategy for Accessible Desig...
Stronger Together: Developing an Organizational Strategy for Accessible Desig...Stronger Together: Developing an Organizational Strategy for Accessible Desig...
Stronger Together: Developing an Organizational Strategy for Accessible Desig...caitlingebhard1
 
CNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In PakistanCNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In Pakistandanishmna97
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDropbox
 
Simplifying Mobile A11y Presentation.pptx
Simplifying Mobile A11y Presentation.pptxSimplifying Mobile A11y Presentation.pptx
Simplifying Mobile A11y Presentation.pptxMarkSteadman7
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfOrbitshub
 
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​Bhuvaneswari Subramani
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAndrey Devyatkin
 
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ..."I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...Zilliz
 
Platformless Horizons for Digital Adaptability
Platformless Horizons for Digital AdaptabilityPlatformless Horizons for Digital Adaptability
Platformless Horizons for Digital AdaptabilityWSO2
 
Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Zilliz
 
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 AmsterdamDEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 AmsterdamUiPathCommunity
 
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Victor Rentea
 
API Governance and Monetization - The evolution of API governance
API Governance and Monetization -  The evolution of API governanceAPI Governance and Monetization -  The evolution of API governance
API Governance and Monetization - The evolution of API governanceWSO2
 
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...Jeffrey Haguewood
 
Quantum Leap in Next-Generation Computing
Quantum Leap in Next-Generation ComputingQuantum Leap in Next-Generation Computing
Quantum Leap in Next-Generation ComputingWSO2
 

Recently uploaded (20)

JavaScript Usage Statistics 2024 - The Ultimate Guide
JavaScript Usage Statistics 2024 - The Ultimate GuideJavaScript Usage Statistics 2024 - The Ultimate Guide
JavaScript Usage Statistics 2024 - The Ultimate Guide
 
Decarbonising Commercial Real Estate: The Role of Operational Performance
Decarbonising Commercial Real Estate: The Role of Operational PerformanceDecarbonising Commercial Real Estate: The Role of Operational Performance
Decarbonising Commercial Real Estate: The Role of Operational Performance
 
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
 
Less Is More: Utilizing Ballerina to Architect a Cloud Data Platform
Less Is More: Utilizing Ballerina to Architect a Cloud Data PlatformLess Is More: Utilizing Ballerina to Architect a Cloud Data Platform
Less Is More: Utilizing Ballerina to Architect a Cloud Data Platform
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
Stronger Together: Developing an Organizational Strategy for Accessible Desig...
Stronger Together: Developing an Organizational Strategy for Accessible Desig...Stronger Together: Developing an Organizational Strategy for Accessible Desig...
Stronger Together: Developing an Organizational Strategy for Accessible Desig...
 
CNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In PakistanCNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In Pakistan
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
Simplifying Mobile A11y Presentation.pptx
Simplifying Mobile A11y Presentation.pptxSimplifying Mobile A11y Presentation.pptx
Simplifying Mobile A11y Presentation.pptx
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
 
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ..."I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
 
Platformless Horizons for Digital Adaptability
Platformless Horizons for Digital AdaptabilityPlatformless Horizons for Digital Adaptability
Platformless Horizons for Digital Adaptability
 
Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)
 
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 AmsterdamDEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
 
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
 
API Governance and Monetization - The evolution of API governance
API Governance and Monetization -  The evolution of API governanceAPI Governance and Monetization -  The evolution of API governance
API Governance and Monetization - The evolution of API governance
 
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
 
Quantum Leap in Next-Generation Computing
Quantum Leap in Next-Generation ComputingQuantum Leap in Next-Generation Computing
Quantum Leap in Next-Generation Computing
 

LTE RACH Procedure

  • 1. 3GPP TS 36.300 (10.1.5) & 36.211 (5.7) Composed by –AALEKH JAIN RACH Procedure
  • 2. Content Coverage Introduction RACH Pre-conditions When RACH occurs? Types of RACHLayer Interaction RACHPRACH PRACH Power
  • 3. Introduction RACH stands for Random Access Channel. This is the first message from UE to eNB when you power it on. The main purpose of RACH can be described as follows. i. Achieve UP link synchronization between UE and eNB ii. Obtain the resource for Message 3 (e.g, RRC Connection Request) In most of the communication, the most important precondition is to establish the timing synchronization between the receiver and transmitter. In LTE, the synchronization in downlink (Transmitter = eNB, Receiver = UE), is achieved by the special synchronization channel. This downlink sync signal gets broadcasted to everybody and it is get transmitted all the time with a certain interval. However in Uplink (Transmitter = UE, Receiver = eNB), it is not efficient if UE is using this kind of broadcasting/always-on synchronization mechanism. In case of uplink, this synchronization process should meet following criteria i. The synchronization process should happen only when there is immediate necessity ii. The synchronization should be dedicated to only a specific UE Another purpose of RACH process is to obtain the resource for Msg3 (Message 3). RRC Connection Request is one example of Msg3.
  • 4. RACH Preconditions Before UE decided to send RACH signal (RACH preamble), there are many preconditions to be met. Following procedure is to list each steps from Power-On to Initial 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. 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. ix. SIB deconding (SIB1 should be decoded first and then SIB2 and then remaining SIBs) x. < Cell Selection > : UE may find multiple suitable cells, but it try camp on to HPLM cell with the highest priority xi. < Initial RACH Process >
  • 5. When RACH occurs? The random access procedure is performed for the following events related to the PCell: • Initial access from RRC_IDLE • RRC Connection Re-establishment procedure • Handover, except for NB-IoT or when RACH-less HO is configured • DL data arrival during RRC_CONNECTED requiring random access procedure: E.g. when UL synchronisation status is "non-synchronised". • UL data arrival during RRC_CONNECTED requiring random access procedure: E.g. when UL synchronisation status is "non-synchronised" or there are no PUCCH resources for SR available. • For positioning purpose during RRC_CONNECTED requiring random access procedure: E.g. when timing advance is needed for UE positioning. The random access procedure is also performed on a SCell to establish time alignment for the corresponding sTAG. For E-UTRA connected to 5GC, the random access procedure is also performed for the transition from RRC_INACTIVE. In DC, the random access procedure is also performed on at least PSCell upon SCG addition/modification, if instructed, or upon DL/UL data arrival during RRC_CONNECTED requiring random access procedure. The UE initiated random access procedure is performed only on PSCell for SCG.
  • 6. Types of RACH the random access procedure takes two distinct forms: o Contention o Non-contention based (applicable to only handover, DL data arrival, positioning and obtaining timing advance alignment for a sTAG) When a UE transmit a PRACH Preamble, it transmits with a specific pattern and this specific pattern is called a "Signature". In each LTE cell, total 64 preamble signatures are available and UE select randomly one of these signatures. There is some possibility that multiple UEs send PRACH with identical signatures. It means the same PRACH preamble from multiple UE reaches the NW at the same time, this kind of PRACH collision is called Contention and the RACH process that allows this type of Contention is called Contention based RACH Process. In this kind of 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. 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 Non-Contention RACH procedure. To initiate the "Contention Free" RACH process, UE should be in Connected Mode before the RACH process as in Handover case.
  • 7. Contention based RACH 1) Random Access Preamble on RACH in uplink: RA-RNTI, indication for L2/L3 message size 2) Random Access Response generated by MAC on DL-SCH: Timing Advance, T_C-RNTI, UL grant for L2/L3 message 3) First scheduled UL transmission on UL-SCH: L2/L3 message depending on RACH occurrence 4) Contention Resolution on DL: Early contention resolution, Addressed to: - The Temporary C-RNTI on PDCCH for initial access and after radio link failure; - The C-RNTI on PDCCH for UE in RRC_CONNECTED. HARQ feedback is transmitted only by the UE which detects its own UE identity, as provided in message 3, echoed in the Contention Resolution message;
  • 8. Non-Contention based RACH 0) Random Access Preamble assignment via dedicated signalling in DL: eNB assigns to UE a non-contention Random Access Preamble 1) Random Access Preamble on RACH in uplink: UE transmits the assigned non-contention Random Access Preamble 2) Random Access Response on DL-SCH: Random Access Response (Timing Advance, C-RNTI, UL grant for L2/L3 message) After receiving UL grant, UE sends the L2/L3 message depending on the RACH occurrence
  • 9. Layer Interaction RACH Random access procedure described above is modelled below from L1 and L2/3 interaction point of view. L2/L3 receives indication from L1 whether ACK is received or DTX is detected after indication of Random Access Preamble transmission to L1. L2/3 indicates L1 to transmit first scheduled UL transmission (RRC Connection Request in case of initial access) if necessary or Random Access Preamble based on the indication from L1.
  • 10. Physical RACH Preamble (PRACH) The physical layer random access preamble, consists of a cyclic prefix of length TCP and a sequence part of length TSEQ. UE determines which Preamble format it has to use by following table. PRACH Configuration Index in sib2 determines the Preamble Format to be used. Ts is defined as 1/(15000 x 2048) seconds (=0.03255 us)
  • 11. RACH information in sib2 Used in PRACH tx Power calculations Decides which preamble format will be used Decides preamble groups to be used Calculates NCS - RACH signal cycle shift Used in PRACH tx Power calculations Used in PRACH retransmission Power calculations
  • 12. PRACH Power The RACH Preamble (PRACH) Power (P_PRACH) is determined by the following equation. P_PRACH = min{P_CMAX, PREAMBLE_RECEIVED_TARGET_POWER + PL} PL stands for Path Loss between eNB Tx antenna and UE Rx Antenna. PREAMBLE_RECEIVED_TARGET_POWER is the PRACH power that eNB expect to receive. i. Calculate PREAMBLE_RECEIVED_TARGET_POWER + PL ii. if the calculated value is less than P_CMAX(23 dBm), transmit the PRACH at the calculated value iii. if the calculated value is greater than P_CMAX(23 dBm), transmit the PRACH at P_CMAX < Case 1 > When UE send the first PRACH PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower(in SIB2) + DELTA_PREAMBLE < Case 2 > When UE retransmit PRACH PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower(in SIB2) + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep PREAMBLE_TRANSMISSION_COUNTER starts from 1 at the first PRACH and get increased by 1 every time PRACH get retransmitted. DELTA_PREAMBLE is determined by which Preamble Format is used.
  • 13. PRACH Power PL = eNB Transmitter Power - UE Reciever Power, where eNB Transmitter Power is referenceSignalPower. Let's take an example from above shared sib2 information preambleInitialReceivedTargetPower = -108 (dBm) referenceSignalPower = 21 prach-ConfigIndex: 3 ==> PREAMBLE FORMAT is Format 0. powerRampingStep = dB4 Now assume that UE measures RSRP at its receiver antenna = -90dBm From these information, PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower(in SIB2) + DELTA_PREAMBLE = -108 + 0 = -108 PL = (referenceSignalPowerin SIB2) - (RSRP measuredt at UE) = 21 - (-90) = 111 Initial P_PRACH = min{23, -108+111 } = min(23, 3) = 3 dBm First Retransmittion P_PRACH = min{23,-108+111+(2-1)*4} = min(23,7) = 7 dBm