top of page

RRC Connection Setup in NR-NTN: Complete 3-Step Signaling Procedure, SRB1 Configuration and 3GPP Enhancements

15 hours ago
17 min read

Introduction to RRC Connection Setup in NR-NTN

RRC Connection Setup in NR-NTN Radio Resource Control (RRC) connection establishment is one of the fundamental procedures in a 5G New Radio (NR) network. It establishes a dedicated signaling connection between the User Equipment (UE) and the gNB, allowing both entities to exchange control-plane information and perform subsequent network procedures.

In conventional Terrestrial Networks (TN), RRC connection establishment follows a three-step signaling procedure involving RRCSetupRequest, RRCSetup, and RRCSetupComplete messages.RRC Connection Setup in NR-NTN

The same fundamental three-way handshake is also used in Non-Terrestrial Networks (NTN). However, satellite-based communication introduces additional challenges, including long propagation delays, high path loss, limited transmit power, Doppler effects, and changing radio channel conditions.

These characteristics influence the configuration of several protocol parameters during RRC connection establishment.RRC Connection Setup in NR-NTN

For example, NR-NTN supports Timing Advance reporting through a MAC Control Element (MAC CE), extended RLC reassembly timers, and appropriate physical-layer configurations to accommodate satellite communication conditions.RRC Connection Setup in NR-NTN

Another important aspect is the establishment of Signaling Radio Bearer 1 (SRB1), which provides the dedicated signaling channel used for subsequent RRC communication between the UE and gNB.RRC Connection Setup in NR-NTN

This article explains the complete RRC Connection Setup procedure in NR-NTN, covering all three signaling steps, SRB1 configuration, RLC, MAC and physical-layer parameters, MCS considerations, and important 3GPP NTN enhancements.


NR-NTN RRC Connection Setup Infographic
NR-NTN RRC Connection Setup

Table of Contents

  1. Overview of RRC Connection Setup in NR-NTN

  2. Importance of RRC Connection Setup in NTN

  3. Three-Step RRC Connection Establishment Procedure

  4. Step 1: RRCSetupRequest from NR-NTN UE

  5. Timing Advance Report MAC Control Element

  6. Step 2: RRCSetup Message from NR-NTN gNB

  7. SRB1 Configuration in NR-NTN

  8. RLC-BearerConfig and Extended Reassembly Timer

  9. MAC-CellGroupConfig Parameters

  10. PhysicalCellGroupConfig Parameters

  11. SpCellConfig and Radio Link Failure Timers

  12. MCS and CQI Considerations in NR-NTN

  13. Step 3: RRCSetupComplete Message

  14. Complete RRC Connection Setup Signaling Flow

  15. Difference Between TN and NTN RRC Connection Setup

  16. Technical Challenges and Engineering Considerations

  17. Relationship Between RRC Setup and NTN Network Access

  18. Practical Applications of NR-NTN RRC Signaling

  19. Frequently Asked Questions


1. Overview of RRC Connection Setup in NR-NTN

RRC Connection Setup is the procedure through which an NR-NTN UE establishes a dedicated signaling connection with the network.

The primary objective is to transition the UE from RRC_IDLE to RRC_CONNECTED, enabling dedicated radio resource configuration and further control-plane communication.

The procedure follows the same fundamental three-message handshake used in terrestrial 5G NR.

The three messages are:

  • RRCSetupRequest

  • RRCSetup

  • RRCSetupComplete

The RRCSetupRequest is transmitted by the UE to request connection establishment. The gNB responds with RRCSetup, which provides the UE-specific radio configuration and establishes SRB1. Finally, the UE sends RRCSetupComplete to confirm successful application of the configuration.

RRC Connection Setup Message Overview

Step

Message

Direction

Main Function

1

RRCSetupRequest

UE to gNB

Requests RRC connection establishment

2

RRCSetup

gNB to UE

Provides UE-specific configuration and establishes SRB1

3

RRCSetupComplete

UE to gNB

Confirms RRC setup and carries initial NAS information

The initial RRC messages use SRB0 for common-control signaling. After the UE applies the configuration provided by the gNB, SRB1 becomes available for dedicated RRC signaling.

Although the overall procedure remains similar to terrestrial NR, NTN requires additional considerations because of its unique propagation and radio-channel characteristics.


2. Importance of RRC Connection Setup in NTN

In terrestrial 5G networks, the communication distance between a UE and a gNB is generally much shorter than the distance involved in satellite-based communication.

In NR-NTN, communication may take place through Low Earth Orbit (LEO), Medium Earth Orbit (MEO), or Geostationary Earth Orbit (GEO) satellites.

These satellite communication environments introduce several technical challenges.

2.1 Long Propagation Delay

Satellite communication involves significantly longer signal propagation distances. Consequently, signaling messages and feedback information may require more time to reach their destinations.

2.2 High Propagation Loss

Satellite links experience substantial propagation losses, making link-budget optimization important for maintaining reliable communication.

2.3 Limited Transmit Power

The UE and satellite payload operate within limited power budgets. Appropriate transmit-power configuration is therefore essential.

2.4 Doppler Frequency Shift

Relative movement between the satellite and UE can introduce Doppler frequency shifts, affecting synchronization and radio communication.

2.5 Changing Radio Channel Conditions

Satellite movement and changing elevation angles can influence signal strength and channel quality.

Because of these challenges, NR-NTN requires suitable protocol configurations, including extended RLC timers, timing-related mechanisms, and appropriate modulation and coding configurations.


3. Three-Step RRC Connection Establishment Procedure

The RRC connection setup procedure in NR-NTN is based on a three-way handshake between the UE and the gNB.

The procedure consists of the following operations:

Step 1 – RRC Connection Request: The UE sends an RRCSetupRequest message containing its initial identity and establishment cause.

Step 2 – Network Configuration: The gNB responds with RRCSetup, providing the configuration required to establish SRB1 and other UE-specific radio parameters.

Step 3 – Connection Confirmation: The UE sends RRCSetupComplete to confirm successful configuration and can include an initial NAS Registration Request.

The successful completion of these three steps establishes the RRC connection.

The main difference between terrestrial and non-terrestrial implementations is not the basic handshake itself, but the additional configuration considerations needed to support satellite communication.


4. Step 1: RRCSetupRequest from NR-NTN UE

The first step begins when the NR-NTN UE needs to establish an RRC connection with the network.

The UE sends an RRCSetupRequest message to the NR-NTN gNB.

This message is transmitted using the following protocol configuration:

Parameter

Configuration

RRC Message

RRCSetupRequest

Signaling Radio Bearer

SRB0

RLC Mode

Transparent Mode (TM)

Logical Channel

CCCH

Direction

UE to gNB

The RRCSetupRequest message contains important information elements that identify the UE and indicate the reason for establishing the connection.

4.1 UE Identity

The UE includes an initial identity in the RRCSetupRequest message.

The identity can be represented using either:

  • The 39 rightmost bits of the 5G-S-TMSI, represented by ng-5G-S-TMSI-Part1.

  • A randomly generated 39-bit value.

If the UE does not have an available 5G-S-TMSI, it can use a randomly generated value.

This identity information helps the network distinguish connection attempts and supports subsequent access procedures.

4.2 Establishment Cause

The establishmentCause field indicates the reason why the UE wants to establish an RRC connection.

Examples include:

  • Mobile-Originated Signaling (mo-Signalling)

  • Mobile-Originated Data (mo-Data)

  • Mobile-Originated Voice Call (mo-VoiceCall)

  • Mobile-Originated SMS (mo-SMS)

  • Emergency access

  • High-priority access

The establishment cause provides information to the network about the purpose of the connection request.

4.3 Spare Field

The RRCSetupRequest message also contains a spare bit field reserved for protocol purposes.

RRCSetupRequest Information Elements

Information Element

Description

ue-Identity

Initial UE identity

ng-5G-S-TMSI-Part1

39-bit portion of 5G-S-TMSI

randomValue

Randomly generated 39-bit identity

establishmentCause

Indicates the reason for connection establishment

spare

Reserved bit

The RRCSetupRequest is the initial RRC signaling message in the connection establishment procedure.


5. Timing Advance Report MAC Control Element

One important NTN-specific aspect of the RRC connection setup procedure is Timing Advance (TA) reporting.

In conventional terrestrial networks, timing alignment is primarily managed through standard Timing Advance commands and associated synchronization procedures.

However, satellite communication introduces longer propagation delays and potentially changing propagation conditions.

To support NTN timing management, the NR-NTN gNB can enable Timing Advance reporting.

When enabled and supported, a Timing Advance Report MAC Control Element can accompany the RRCSetupRequest transmission.

An important technical distinction is that the Timing Advance Report is not an Information Element inside the RRCSetupRequest message. It is a separate MAC-layer control element transmitted alongside the request.

Why Is Timing Advance Reporting Important?

Timing Advance reporting provides timing-related information that can help the gNB manage uplink synchronization.

Its importance includes:

  • Supporting uplink timing management.

  • Providing propagation-related timing information.

  • Helping manage NTN-specific timing conditions.

  • Supporting more efficient radio resource management.

In satellite environments, timing management is particularly important because the distance between the UE and satellite infrastructure can significantly influence signal arrival times.

Engineering Insight: Timing Advance reporting is a MAC-layer mechanism and should not be confused with the three primary RRC messages used for connection establishment.


6. Step 2: RRCSetup Message from NR-NTN gNB

After receiving the RRCSetupRequest, the NR-NTN gNB processes the connection request and responds with an RRCSetup message.

The primary purpose of this message is to establish SRB1 and provide the UE-specific radio configuration.

The RRCSetup message is transmitted using the initial signaling configuration:

Parameter

Configuration

RRC Message

RRCSetup

Signaling Radio Bearer

SRB0

RLC Mode

Transparent Mode (TM)

Logical Channel

CCCH

Direction

gNB to UE

The RRCSetup message contains two major configuration elements:

  1. masterCellGroup

  2. radioBearerConfig

6.1 masterCellGroup

The masterCellGroup contains the configuration required for the Master Cell Group.

The configuration includes parameters associated with:

  • RLC-BearerConfig

  • MAC-CellGroupConfig

  • PhysicalCellGroupConfig

  • SpCellConfig

These configuration elements define the radio bearer, MAC-layer behavior, physical-layer parameters, and serving-cell configuration.

6.2 radioBearerConfig

The radioBearerConfig Information Element provides the radio bearer configuration required by the UE.

During initial RRC connection establishment, the network configures SRB1.

SRB1 is subsequently used to exchange dedicated RRC signaling messages between the UE and gNB.

The configuration of SRB1 is especially important in NTN because the signaling connection must operate reliably under long propagation delays and challenging radio conditions.


7. SRB1 Configuration in NR-NTN

Signaling Radio Bearers are responsible for carrying RRC control-plane messages between the UE and the network.

SRB1 is established during the RRC connection setup procedure.

After successful configuration, SRB1 is used to transport dedicated RRC signaling messages.

Examples include:

  • RRC Security Mode procedures.

  • RRC Reconfiguration.

  • Radio resource configuration.

  • Measurement configuration.

  • Other dedicated RRC control procedures.

The SRB1 configuration is provided through the RRCSetup message.

Main SRB1 Configuration Components

Configuration Element

Function

RLC-BearerConfig

Defines RLC bearer parameters

MAC-CellGroupConfig

Defines MAC-layer cell-group parameters

PhysicalCellGroupConfig

Defines physical-layer cell-group parameters

SpCellConfig

Defines serving-cell-specific configuration

radioBearerConfig

Provides radio bearer configuration, including SRB1

The gNB configures these parameters according to the UE requirements and NTN radio environment.


8. RLC-BearerConfig and Extended Reassembly Timer

The RLC-BearerConfig Information Element defines the RLC parameters associated with SRB1.

One of the most important NTN-related enhancements is the extension of the RLC reassembly timer.

In terrestrial networks, RLC reassembly timers are configured according to expected transmission and retransmission behavior.

However, NTN introduces longer propagation delays. As a result, conventional timer values may not always be suitable for satellite communication.

To address this challenge, NR-NTN supports extended RLC reassembly timer values.

T-ReassemblyExt-r17

The T-ReassemblyExt-r17 parameter supports the following values:

Timer Value

Configuration

210 ms

Extended timer

220 ms

Extended timer

340 ms

Extended timer

350 ms

Extended timer

550 ms

Extended timer

1,100 ms

Extended timer

1,650 ms

Extended timer

2,200 ms

Extended timer

These extended timer values provide greater flexibility when configuring RLC reassembly behavior for satellite communication.

Why Does NTN Need Extended RLC Timers?

Consider an NR-NTN UE communicating through a satellite.

When RLC data is transmitted, the receiving side may require additional time to receive and assemble the complete set of data segments.

If the reassembly timer expires too early, unnecessary reassembly-related actions may occur.

Extended timer configurations help accommodate the longer delays associated with NTN communication.

This can improve the reliability of signaling and data transfer over satellite links.

Practical Engineering Consideration: Timer selection should consider the NTN architecture, propagation characteristics, radio conditions, and applicable protocol configuration. A longer timer is not automatically better for every deployment.


9. MAC-CellGroupConfig Parameters

The MAC-CellGroupConfig Information Element contains MAC-layer parameters associated with the cell group.

During RRC connection setup, the gNB configures the relevant MAC parameters for the UE.

Important configuration areas include Discontinuous Reception (DRX), Scheduling Request (SR), and Buffer Status Reporting (BSR).

9.1 Discontinuous Reception (DRX)

DRX allows the UE to monitor the downlink channel periodically rather than continuously.

This helps reduce power consumption.

In satellite communication, efficient power management is important because many NTN devices operate with limited battery capacity.

9.2 Scheduling Request (SR)

The Scheduling Request mechanism allows the UE to request uplink resources from the gNB.

When the UE has data to transmit but does not have sufficient uplink resources, it can use the configured SR procedure.

9.3 Buffer Status Reporting (BSR)

Buffer Status Reporting informs the gNB about the amount of data waiting in the UE's uplink buffer.

This information helps the scheduler allocate uplink transmission resources more efficiently.

MAC Configuration Summary

MAC Parameter

Main Function

NTN Relevance

DRX

Reduces UE monitoring activity

Helps manage device power consumption

SR

Requests uplink scheduling resources

Supports uplink transmission requests

BSR

Reports buffered uplink data

Helps the gNB allocate resources

Together, these MAC parameters help coordinate uplink and downlink communication between the NR-NTN UE and gNB.


10. PhysicalCellGroupConfig Parameters

The PhysicalCellGroupConfig Information Element contains physical-layer configuration parameters associated with the cell group.

These parameters influence how the UE operates at the physical layer.

Important configuration areas include:

  • Transmit Power Control (TPC).

  • HARQ feedback configuration.

  • MCS-related configuration.

  • Other physical-layer cell-group parameters.

10.1 Transmit Power Control

Transmit Power Control helps regulate the UE's uplink transmission power.

In NTN, power management is particularly important because the UE operates with limited transmit power while communicating over long satellite links.

Appropriate TPC configuration helps manage uplink transmission performance.

10.2 HARQ Feedback Configuration

Hybrid Automatic Repeat Request (HARQ) improves transmission reliability through feedback and retransmission mechanisms.

The PhysicalCellGroupConfig contains relevant HARQ-related configuration.

Because of long propagation delays, NTN deployments must consider the timing and operational implications of HARQ feedback.

10.3 MCS-Related Configuration

The PhysicalCellGroupConfig also supports configuration associated with the Modulation and Coding Scheme table.

The selection of an appropriate MCS is particularly important in NTN because available SINR may be limited.

A suitable configuration helps balance throughput and transmission reliability.


11. SpCellConfig and Radio Link Failure Timers

The SpCellConfig Information Element provides configuration for the Special Cell (SpCell).

For a standalone serving-cell configuration, the Primary Cell (PCell) is the SpCell.

The configuration includes information such as:

  • Serving-cell index.

  • Physical-layer serving-cell configuration.

  • Radio Link Failure (RLF)-related timers and parameters.

Why Are RLF Timers Important in NTN?

Radio Link Failure occurs when the UE determines that the radio connection cannot be maintained according to the applicable failure criteria.

In terrestrial networks, RLF monitoring is designed around terrestrial radio conditions.

However, satellite communication introduces additional considerations, including:

  • Long propagation delays.

  • Satellite movement.

  • Changing elevation angles.

  • Doppler variations.

  • Temporary signal degradation.

Therefore, RLF-related configuration must account for NTN operating conditions.

Appropriate configuration helps prevent unnecessary connection failures while maintaining reliable radio link monitoring.


12. MCS and CQI Considerations in NR-NTN

One of the most important aspects of NR-NTN radio configuration is the selection of appropriate modulation and coding schemes.

In conventional 5G NR, the network uses Channel Quality Indicator (CQI) reports from the UE to support link adaptation.

These reports help the gNB select suitable modulation and coding configurations.

However, NR-NTN faces two major challenges.

12.1 Low SINR Conditions

Satellite communication links often experience large propagation losses.

Additionally, UE and satellite payload transmit power may be limited.

As a result, high Signal-to-Interference-plus-Noise Ratio (SINR) values cannot always be expected.

Aggressive modulation and coding schemes may therefore be unsuitable for certain NTN radio conditions.

12.2 Delayed CQI Information

Another challenge is long propagation delay.

When an NR-NTN UE measures channel quality and sends a CQI report, the information may reach the gNB after the radio channel conditions have changed.

Consequently, the reported CQI may not accurately represent the prevailing channel conditions when the network uses it for scheduling decisions.

Why Is Conservative MCS Preferred?

Conservative modulation and coding configurations can improve transmission robustness under challenging radio conditions.

The network must balance:

  • Spectral efficiency.

  • Throughput.

  • SINR availability.

  • Channel variation.

  • Transmission reliability.

  • Feedback delay.

MCS and CQI Comparison

Parameter

Terrestrial Network

NR-NTN

Propagation delay

Generally lower

Potentially much higher

Path loss

Depends on terrestrial coverage

Often significantly higher

SINR

Can support higher MCS under favorable conditions

May be limited

CQI relevance

Generally more timely

Can become outdated due to delay

MCS selection

Based on channel quality and scheduler policy

May require conservative link adaptation

Link adaptation

Terrestrial channel conditions

Must consider satellite characteristics

Engineering Insight: Conservative MCS selection does not mean NR-NTN always uses the lowest MCS. Actual selection depends on radio conditions, link adaptation algorithms, supported MCS tables, and network implementation.


13. Step 3: RRCSetupComplete Message

After receiving the RRCSetup message, the NR-NTN UE processes the configuration provided by the gNB.

It applies the SRB1 configuration and establishes the dedicated signaling bearer.

Once the configuration is successfully applied, the UE sends an RRCSetupComplete message to the NR-NTN gNB.

This message confirms successful RRC connection establishment.

The message uses the following signaling configuration:

Parameter

Configuration

RRC Message

RRCSetupComplete

Signaling Radio Bearer

SRB1

RLC Mode

Acknowledged Mode (AM)

Logical Channel

DCCH

Direction

UE to gNB

Important Information Elements in RRCSetupComplete

The RRCSetupComplete message contains several important fields.

13.1 ng-5G-S-TMSI-Value

The message can include the remaining 9-bit portion of the 5G-S-TMSI, represented by ng-5G-S-TMSI-Part2, when applicable.

This complements the identity information supplied in the initial connection request.

13.2 Selected PLMN Identity

The selectedPLMN-Identity indicates the Public Land Mobile Network selected by the UE.

This helps the network identify the PLMN chosen during network selection.

13.3 Registered AMF

The registeredAMF Information Element may be included when available.

It provides information about the previously registered Access and Mobility Management Function.

13.4 S-NSSAI List

The S-NSSAI list identifies the requested or relevant Network Slice Selection Assistance Information.

It supports network slice selection.

13.5 Dedicated NAS Message

The dedicatedNAS-Message carries the initial NAS message from the UE.

A common example is the NAS Registration Request.

This allows the UE to proceed with the 5G Core registration procedure after establishing the RRC connection.

RRCSetupComplete Configuration Summary

Information Element

Purpose

ng-5G-S-TMSI-Value

Provides the applicable 5G-S-TMSI portion

selectedPLMN-Identity

Identifies the selected PLMN

registeredAMF

Provides registered AMF information when available

s-NSSAI-List

Provides network slicing information

dedicatedNAS-Message

Carries initial NAS signaling

Important: RRCSetupComplete completes the RRC connection establishment procedure. It does not mean that NAS registration or authentication has already completed.


14. Complete RRC Connection Setup Signaling Flow

The complete RRC connection setup procedure can be summarized through the following signaling sequence.

Detailed Signaling Sequence

Sequence

Signaling / Action

Description

1

RRCSetupRequest

UE requests an RRC connection

2

Timing Advance Report MAC CE

UE provides TA information if reporting is enabled and supported

3

RRCSetup

gNB sends UE-specific configuration

4

SRB1 Configuration

UE applies RLC, MAC, PHY and serving-cell configuration

5

RRCSetupComplete

UE confirms successful RRC setup

6

Initial NAS Message

NAS Registration Request can be forwarded to the network

Simplified Protocol Flow

                 NR-NTN UE                         NR-NTN gNB
                     |                                  |
                     |                                  |
                     |-------- RRCSetupRequest -------->|
                     |                                  |
                     |---- Timing Advance Report ----->|
                     |          (MAC CE)                |
                     |                                  |
                     |<----------- RRCSetup ------------|
                     |                                  |
                     |    Apply SRB1 Configuration     |
                     |    RLC / MAC / PHY / SpCell     |
                     |                                  |
                     |-------- RRCSetupComplete ------->|
                     |                                  |
                     |      Initial NAS Message         |
                     |      Registration Request        |
                     |                                  |
                     |     RRC Connection Established   |
                     |                                  |

The diagram represents the logical signaling sequence. The Timing Advance Report is a MAC-layer transmission associated with the request, not an additional RRC message.


15. Difference Between TN and NTN RRC Connection Setup

The fundamental RRC connection establishment procedure remains similar in terrestrial and non-terrestrial networks.

Both use the same three primary RRC messages.

However, the radio environment and configuration requirements introduce important differences.

Feature

5G Terrestrial Network

5G NR-NTN

RRCSetupRequest

Supported

Supported

RRCSetup

Supported

Supported

RRCSetupComplete

Supported

Supported

SRB1 Establishment

Supported

Supported

Timing Advance Reporting

Standard timing mechanisms

NTN-specific reporting can be enabled

RLC Reassembly Timer

Conventional configuration

Extended NTN timer options

Propagation Delay

Generally lower

Higher, depending on orbit and architecture

Path Loss

Terrestrial radio conditions

Large satellite-link path losses

CQI Feedback

Generally more timely

May be affected by propagation delay

MCS Selection

Based on channel conditions

May require conservative link adaptation

RLF Configuration

Terrestrial radio conditions

Must account for NTN characteristics

The key takeaway is that NR-NTN does not introduce an entirely different RRC connection establishment handshake. Instead, it enhances the configuration and timing behavior to support satellite-based communication.


16. Technical Challenges and Engineering Considerations

Implementing RRC connection setup in NR-NTN requires careful consideration of several radio and protocol-level challenges.

16.1 Propagation Delay Management

Long propagation delays can affect the timing of signaling exchanges between the UE and gNB.

Network engineers must consider the satellite architecture and propagation characteristics when configuring protocol timers.

16.2 RLC Reassembly Optimization

Extended RLC reassembly timers help accommodate the longer delays associated with satellite links.

Incorrect timer configuration can negatively affect signaling performance.

16.3 Uplink Power Limitations

UE transmit power is limited, while the satellite communication link may experience substantial path loss.

Therefore, power control and link-budget optimization are important.

16.4 CQI and Link Adaptation

Delayed CQI information can affect scheduling decisions.

The gNB must consider the relevance of reported channel quality when selecting appropriate MCS configurations.

16.5 Radio Link Failure Management

RLF monitoring must account for satellite movement, changing radio conditions, and applicable NTN timing requirements.

16.6 Signaling Reliability

Reliable SRB1 establishment is essential because subsequent dedicated RRC procedures depend on this signaling bearer.

A failure during RRC connection setup can prevent the UE from progressing to subsequent NAS procedures.


17. Relationship Between RRC Setup and NTN Network Access

RRC connection setup is one stage of the overall NR-NTN network access procedure.

Before reaching this stage, the UE performs necessary network acquisition operations.

These include cell search, synchronization, system information acquisition, and random access.

After successful RRC connection establishment, the UE can proceed with NAS registration and subsequent session management procedures.

Overall NR-NTN Access Sequence

Stage

Procedure

Main Objective

1

Cell Search

Detect the NTN cell

2

Synchronization

Achieve time and frequency synchronization

3

System Information Acquisition

Obtain essential network configuration

4

Random Access

Establish initial uplink access

5

RRC Connection Setup

Establish SRB1 and RRC connectivity

6

NAS Registration

Register the UE with the 5G Core

7

Authentication and Security

Establish the required security context

8

PDU Session Establishment

Establish user-plane connectivity

This sequence provides an overview of the broader access process. Actual procedure details and ordering can vary depending on network configuration and deployment.


18. Practical Applications of NR-NTN RRC Signaling

Understanding RRC connection setup is important for engineers working on satellite-based 5G networks.

The procedure is relevant to several emerging NTN applications.

18.1 Direct-to-Device Satellite Connectivity

NR-NTN can support compatible devices connecting to satellite-based networks where terrestrial coverage is unavailable.

RRC signaling is essential for establishing and managing the UE's control-plane connection.

18.2 Remote and Rural Connectivity

Satellite connectivity can extend communication services to remote areas, including regions where deploying terrestrial infrastructure is difficult.

18.3 Maritime Communication

Ships operating far from terrestrial cellular coverage can benefit from satellite-based connectivity.

18.4 Aviation Connectivity

Satellite communication can support connectivity services for aircraft and passengers.

18.5 IoT-NTN Applications

Satellite-based IoT communication can support remote monitoring, asset tracking, agriculture, logistics, and industrial applications.

Although NR-NTN and IoT-NTN have different protocol characteristics and device requirements, both are important parts of the broader 3GPP NTN ecosystem.


20. Frequently Asked Questions (FAQs)


Q1. What is RRC Connection Setup in NR-NTN?

RRC Connection Setup is the procedure used to establish a dedicated signaling connection between an NR-NTN UE and the gNB. It follows a three-message handshake involving RRCSetupRequest, RRCSetup, and RRCSetupComplete.


Q2. How many steps are involved in NR-NTN RRC connection establishment?

There are three primary signaling steps: RRCSetupRequest, RRCSetup, and RRCSetupComplete. Together, these messages establish the RRC connection and SRB1.


Q3. What is the purpose of SRB1 in NR-NTN?

SRB1 carries dedicated RRC signaling messages between the UE and gNB. It is established during the RRC connection setup procedure.


Q4. What is the purpose of Timing Advance reporting in NR-NTN?

Timing Advance reporting provides timing-related information to the gNB to support uplink timing management under NTN propagation conditions.


Q5. Is Timing Advance reporting part of the RRCSetupRequest message?

No. The Timing Advance Report is a MAC Control Element. It can accompany the RRCSetupRequest transmission when the reporting mechanism is enabled and supported.


Q6. What is T-ReassemblyExt-r17?

T-ReassemblyExt-r17 is an extended RLC reassembly timer parameter introduced to accommodate longer propagation delays associated with NTN communication.

It supports values of 210, 220, 340, 350, 550, 1,100, 1,650, and 2,200 milliseconds.


Q7. Why does NR-NTN require extended RLC timers?

Satellite communication involves longer propagation delays than typical terrestrial communication. Extended timers help the RLC layer accommodate these delays during data reassembly.


Q8. What is the function of masterCellGroup in RRCSetup?

masterCellGroup provides the cell-group configuration required by the UE, including RLC bearer, MAC cell-group, physical cell-group, and serving-cell configuration.


Q9. What information is carried in RRCSetupComplete?

RRCSetupComplete can contain the selected PLMN identity, registered AMF information, S-NSSAI list, 5G-S-TMSI information, and initial NAS message.


Q10. Why is conservative MCS selection important in NR-NTN?

Satellite links may experience high path loss and limited SINR. Additionally, CQI reports can become outdated because of long propagation delays. Conservative link adaptation can help improve transmission reliability.


Q11. Does RRCSetupComplete mean that 5G Core registration is complete?

No. It confirms successful RRC connection establishment and carries the initial NAS message. NAS registration, authentication, and subsequent procedures are handled separately.


Q12. Which 3GPP specification defines NR RRC procedures?

3GPP TS 38.331 defines the NR Radio Resource Control protocol, including RRC message structures and connection establishment procedures. TS 38.300 describes the overall NR and NG-RAN architecture and procedures.


21. Conclusion

RRC Connection Setup is a fundamental procedure in 5G NR-NTN because it establishes the dedicated signaling connection required for subsequent communication between the UE and gNB.

Although the procedure follows the same three-step handshake used in terrestrial 5G NR, satellite communication introduces additional requirements for timing management, protocol configuration, and radio resource optimization.

The use of Timing Advance reporting, extended RLC reassembly timers, appropriate MAC and physical-layer configuration, and conservative MCS selection helps address the challenges associated with long propagation delays and limited radio link budgets.

For telecom engineers, understanding these mechanisms is essential when working on NR-NTN protocol development, RRC signaling analysis, UE testing, gNB integration, and satellite communication network optimization.

As 5G NTN continues to evolve, knowledge of these RRC procedures will become increasingly important for engineers developing and testing next-generation non-terrestrial communication systems.


22. 3GPP Technical References

The following specifications and technical resources are useful for understanding RRC connection establishment and NTN enhancements.

1. 3GPP TS 38.331 – NR; Radio Resource Control (RRC); Protocol Specification

Relevant topics:

  • RRCSetupRequest

  • RRCSetup

  • RRCSetupComplete

  • SRB1 configuration

  • RRC protocol procedures


2. 3GPP TS 38.300 – NR; NR and NG-RAN Overall Description

Relevant topics:

  • NR architecture

  • NG-RAN procedures

  • Radio interface

  • NTN-related operations


3. 3GPP TS 38.321 – NR; Medium Access Control (MAC) Protocol Specification

Relevant topics:

  • MAC Control Elements

  • Timing Advance procedures

  • Scheduling Request

  • Buffer Status Reporting


4. 3GPP TS 38.322 – NR; Radio Link Control (RLC) Protocol Specification

Relevant topics:

  • RLC Transparent Mode

  • RLC Acknowledged Mode

  • RLC reassembly

  • RLC timers


5. 3GPP TS 38.213 – NR; Physical Layer Procedures for Control

Relevant topics:

  • Physical-layer control procedures

  • HARQ-related procedures

  • Timing and control operations


6. 3GPP TS 38.214 – NR; Physical Layer Procedures for Data

Relevant topics:

  • MCS selection

  • Link adaptation

  • CQI-related procedures

  • Physical-layer data transmission

Comments


  • Facebook
  • Twitter
  • LinkedIn

©2022 by Apeksha Telecom-The Telecom Gurukul . 

bottom of page