top of page

UE Capability Exchange in NR-NTN: Complete RRC Signaling Procedure and NTN-Specific UE Capabilities Explained

3 minutes ago
15 min read
  1. Introduction to UE Capability Exchange in NR-NTN

UE Capability Exchange in NR-NTN The evolution of 5G Non-Terrestrial Networks (NTN) is enabling mobile connectivity through satellites, High Altitude Platform Systems (HAPS), and other non-terrestrial platforms. Unlike conventional Terrestrial Networks (TN), NTN introduces unique radio communication challenges, including long propagation delays, high Doppler shifts, extended Round-Trip Time (RTT), and satellite mobility.UE Capability Exchange in NR-NTN

To ensure successful communication between the network and the User Equipment (UE), the NR-NTN gNB must understand the capabilities supported by the UE before configuring and utilizing different radio access features.

For this purpose, 3GPP defines a procedure known as UE Capability Transfer, which allows the gNB to request and obtain the radio access capabilities supported by the UE through Radio Resource Control (RRC) signaling.

The UE Capability Exchange procedure is particularly important in NR-NTN because not every conventional 5G NR UE supports the additional functionalities required for satellite-based communication.

Through this procedure, the network can identify whether the UE supports relevant NR features and NTN-specific capabilities.

The procedure mainly involves two RRC messages:

  • UE Capability Enquiry

  • UE Capability Information

The NR-NTN gNB initiates the procedure by transmitting a UE Capability Enquiry message. The UE responds with a UE Capability Information message containing its supported capabilities for the requested Radio Access Technology (RAT).

Since NR-NTN is a special case of NR, the network uses RAT-Type = nr to request the UE's NR capabilities, including applicable NTN-specific capability parameters.

This article explains the complete UE Capability Exchange procedure in NR-NTN, including RRC signaling, important Information Elements (IEs), capability request filters, UE-NR-Capability, Release 17 extensions, and practical protocol testing considerations.


UE Capability Exchange in NR-NTN
UE Capability Exchange in NR-NTN

  1. Table of Contents

  2. Introduction to UE Capability Exchange in NR-NTN

  3. Importance of UE Capability Exchange in NR-NTN

  4. Overview of UE Capability Transfer Procedure

  5. RRC Signaling Flow Between NR-NTN UE and gNB

  6. Step 1: UE Capability Enquiry Message

  7. UE-CapabilityRAT-RequestList

  8. UE-CapabilityEnquiryExt

  9. UE-CapabilityRequestFilterNR

  10. Understanding RAT-Type in NR-NTN

  11. Step 2: UE Capability Information Message

  12. UE-CapabilityRAT-ContainerList

  13. UE-NR-Capability in NR-NTN

  14. UE-NR-Capability-v1700

  15. NTN-Specific UE Radio Access Capabilities

  16. Difference Between Terrestrial NR and NR-NTN Capabilities

  17. Practical UE Capability Exchange Example

  18. NR-NTN UE Capability Exchange Protocol Testing

  19. Common Troubleshooting Scenarios

  20. Key Technical Takeaways

  21. Frequently Asked Questions

  22. Conclusion

  23. References and Further Reading


  1. Importance of UE Capability Exchange in NR-NTN

UE Capability Exchange plays an important role in ensuring compatibility between the NR-NTN UE and the gNB.

In terrestrial 5G networks, the UE generally operates under conventional NR radio conditions. However, satellite-based communication introduces additional requirements that must be supported by both the network and the UE.

For example, NR-NTN communication may require:

  • Extended timing requirements to accommodate long propagation delays.

  • Random Access Channel (RACH) adaptations.

  • Extended MAC, RLC, and PDCP timers.

  • NTN-specific System Information acquisition.

  • Satellite-related mobility support.

  • Frequency and Doppler compensation mechanisms.

  • Support for applicable GSO and NGSO deployment scenarios.

The gNB must identify whether the UE supports these functionalities before using the corresponding network features.

3.1 Key Objectives of UE Capability Exchange

Objective

Description

Capability Identification

Identifies the radio access capabilities supported by the UE.

NTN Support Verification

Determines whether the UE supports NR-NTN functionalities.

RAT Compatibility

Identifies capabilities associated with different RAT types.

Frequency Band Support

Helps identify supported NR frequency bands.

Network Configuration

Helps the gNB select compatible radio configurations.

Interoperability

Supports compatibility between different UE and network implementations.

Therefore, UE Capability Exchange is an essential part of NR-NTN operation because it allows the network to make capability-aware configuration decisions.


  1. Overview of UE Capability Transfer Procedure

The UE Capability Transfer procedure follows a request-response mechanism between the NR-NTN gNB and UE.

The procedure begins when the gNB sends a UE Capability Enquiry message requesting specific capability information.

After receiving the request, the UE processes the requested RAT types and capability filters. It then prepares and transmits a UE Capability Information message containing the requested capability information.

The procedure consists of two primary steps.

Step

Sender

RRC Message

Purpose

Step 1

NR-NTN gNB

UE Capability Enquiry

Requests UE radio access capabilities.

Step 2

NR-NTN UE

UE Capability Information

Reports supported UE capabilities.

The capability information received by the gNB helps determine which NR and NTN-related functionalities are supported by the UE.


  1. RRC Signaling Flow Between NR-NTN UE and gNB

The following signaling flow illustrates the UE Capability Exchange procedure.

Step 1: UE Capability Enquiry

The NR-NTN gNB transmits a UE Capability Enquiry message to the UE.

The message includes the RAT types and capability filters for which the network requires capability information.

Step 2: UE Capability Information

The UE processes the enquiry and sends a UE Capability Information message containing the corresponding capability information.

RRC Signaling Flow:

NR-NTN gNB

↓

UE Capability Enquiry

↓

NR-NTN UE

↓

Capability Request Processing

↓

UE Capability Information

↓

NR-NTN gNB

↓

UE Capability Evaluation

This exchange allows the gNB to understand the supported UE features and determine compatible network configurations.


  1. Step 1: UE Capability Enquiry Message

The first step of the UE Capability Transfer procedure begins when the NR-NTN gNB sends a UE Capability Enquiry message to the UE.

The purpose of this message is to request information about the UE's supported radio access capabilities.

The gNB can request capabilities associated with one or more RAT types, such as:

  • NR

  • E-UTRA-NR

  • E-UTRA

  • Other supported RAT-related capabilities

The UE Capability Enquiry message includes important Information Elements that define the requested capability information.

Two important IEs are:

  1. UE-CapabilityRAT-RequestList

  2. UE-CapabilityEnquiryExt

These IEs help the gNB specify which RAT-related capabilities and additional capability filters should be included in the UE's response.


  1. Understanding UE-CapabilityRAT-RequestList

The Information Element UE-CapabilityRAT-RequestList is used by the gNB to identify the RAT types for which UE capability information is required.

It contains a list of UE-CapabilityRAT-Request entries.

Each entry specifies a RAT-Type and an associated capabilityRequestFilter.

The RAT-Type identifies the Radio Access Technology for which the UE must provide capability information.

The following are examples of RAT-Type values:

RAT-Type

Description

nr

New Radio (5G NR)

eutra-nr

E-UTRA and NR capabilities

eutra

E-UTRA (LTE)

utra-fdd-v1610

UMTS FDD-related capability reporting

The capabilityRequestFilter allows the gNB to request a filtered set of UE capabilities.

For example, when RAT-Type is NR, the gNB can use UE-CapabilityRequestFilterNR to specify the NR capability information required from the UE.

7.1 Why RAT-Type = nr Is Used for NR-NTN

An important aspect of NR-NTN capability exchange is that NR-NTN is not treated as an entirely separate Radio Access Technology.

Instead, it is based on the existing NR radio access technology with additional functionalities to support non-terrestrial communication.

Therefore, the NR-NTN gNB can set:

RAT-Type = nr

This instructs the UE to provide its NR capability information.

The NR-NTN UE then reports its typical NR capabilities and applicable NTN-specific capabilities within the UE-NR-Capability structure.

This approach allows the network to reuse the existing NR capability reporting framework instead of introducing an entirely separate RAT-Type exclusively for NR-NTN.


  1. Understanding UE-CapabilityEnquiryExt

The UE Capability Enquiry message can also include the UE-CapabilityEnquiryExt Information Element.

This extension supports additional capability request information.

One important component is:

ue-CapabilityRequestFilterCommon

This information allows the gNB to request common capability-related information.

It may include parameters such as:

  • mrdc-Request

  • codebookTypeRequest

These parameters help the network request specific UE capability information.

8.1 mrdc-Request

The mrdc-Request parameter is associated with Multi-Radio Dual Connectivity (MR-DC) capability reporting.

It allows the network to request information about the UE's multi-RAT capabilities.

This is useful when the network needs to understand whether a UE supports combinations involving multiple radio access technologies.

For example, the network may need to identify whether the UE supports E-UTRA-NR Dual Connectivity configurations.

8.2 codebookTypeRequest

The codebookTypeRequest parameter is used to request information about the MIMO codebook types supported by the UE.

Multiple-Input Multiple-Output (MIMO) technology plays an important role in improving spectral efficiency and radio performance in 5G NR.

The supported codebook information helps the network understand the UE's capabilities for applicable MIMO transmission configurations.

Although these parameters are not exclusively NTN-related, they are part of the broader UE capability reporting framework that can also be used in NR-NTN.


  1. Role of UE-CapabilityRequestFilterNR

When the requested RAT-Type is NR, the gNB can use the UE-CapabilityRequestFilterNR Information Element.

This filter specifies the NR capability information that the network wants the UE to report.

One important parameter within this structure is:

FreqBandList

The FreqBandList helps identify the frequency bands for which capability information is requested.

Frequency band support is particularly important in NR-NTN because satellite communication can operate across different frequency ranges and deployment configurations.

The gNB needs to understand whether the UE supports the relevant frequency bands before selecting an appropriate radio configuration.

9.1 Importance of Frequency Band Filtering

Consider a network supporting multiple NR frequency bands.

The UE may support only a subset of these bands.

By using the capability request filter, the gNB can request the capability information associated with the relevant frequency bands instead of requesting unrelated information.

This allows the network to obtain the capability information required for its intended operation.

  1. Step 2: UE Capability Information Message

After receiving the UE Capability Enquiry message, the NR-NTN UE processes the request and prepares its response.

The UE sends a UE Capability Information message to the gNB.

This message contains the UE's capabilities associated with the RAT types specified in the enquiry.

An important Information Element included in this message is:

UE-CapabilityRAT-ContainerList

This IE carries a list of capability containers.

Each container identifies a particular RAT-Type and includes the corresponding capability information.

For example:

RAT-Type

Associated Capability Information

nr

UE-NR-Capability

eutra-nr

UE-MRDC-Capability

eutra

UE-EUTRA-Capability

The actual containers depend on the RAT types requested by the network and the capabilities supported by the UE.

Since NR-NTN is a special case of NR, the NR-NTN UE provides its NR-related capabilities using the UE-NR-Capability structure.

This structure also carries applicable NTN-specific capability information.


  1. Understanding UE-CapabilityRAT-ContainerList

The UE-CapabilityRAT-ContainerList is a central component of the UE Capability Information message.

It provides a structured method for reporting capability information associated with different RAT types.

Each UE-CapabilityRAT-Container contains two important elements:

  1. RAT-Type

  2. The corresponding RAT-specific capability container

The RAT-Type identifies the technology associated with the capability information.

The associated capability container carries the detailed radio access capability parameters.

11.1 Example of Capability Container Mapping

RAT-Type

Capability Container

Purpose

nr

UE-NR-Capability

Reports NR radio access capabilities, including applicable NTN capabilities.

eutra-nr

UE-MRDC-Capability

Reports multi-RAT dual connectivity capabilities.

eutra

UE-EUTRA-Capability

Reports LTE radio access capabilities.

For an NR-NTN capability request using RAT-Type = nr, the UE provides the relevant NR capability information.

The gNB can then evaluate the reported capabilities to determine which supported NR and NTN functionalities are applicable.


  1. Role of UE-NR-Capability in NR-NTN

The UE-NR-Capability Information Element contains the NR UE Radio Access Capability Parameters.

It provides information about the NR features and functionalities supported by the UE.

In conventional NR, these capabilities include information related to:

  • Supported frequency bands.

  • MIMO capabilities.

  • Physical-layer capabilities.

  • MAC-layer capabilities.

  • Measurement capabilities.

  • Mobility-related functionalities.

  • Other NR radio access features.

In NR-NTN, the same NR capability framework is extended to include NTN-specific capability information.

This is important because the network must identify not only whether a UE supports NR but also whether it supports the additional features required for satellite-based communication.

12.1 Typical NR Capabilities and NTN-Specific Capabilities

Capability Category

Information

Frequency Band Support

Supported NR operating bands.

MIMO Capabilities

Supported MIMO and codebook-related features.

PHY Capabilities

Physical-layer feature support.

MAC Capabilities

Medium Access Control-related feature support.

Measurement Capabilities

Supported radio measurement functionality.

Mobility Capabilities

Supported mobility-related functionalities.

NTN Capabilities

Specific radio access capabilities required for NTN operation.

The gNB uses this information to determine whether the UE supports the required features for the intended NR-NTN deployment.


  1. Understanding UE-NR-Capability-v1700

The UE Capability Information message may include the IE:

UE-NR-Capability-v1700

This is a versioned extension of the NR UE capability structure associated with Release 17.

It is relevant to NR-NTN because Release 17 introduced the initial standardized NR-NTN radio access capabilities.

The capability structure allows the UE to report additional radio access parameters introduced or extended in the relevant 3GPP release.

The important point is that UE-NR-Capability-v1700 is not a completely independent capability container. It forms part of the versioned NR UE capability framework.

The UE reports the applicable capability information through the standardized NR capability structure.

13.1 Why Release 17 Is Important for NR-NTN

3GPP Release 17 introduced the initial standardized NR-NTN framework.

It addressed several technical challenges associated with satellite-based NR communication.

These include:

  • Long propagation delays.

  • Extended timing requirements.

  • Random access adaptations.

  • NTN-specific system information.

  • Satellite-related frequency and Doppler considerations.

  • Protocol timer enhancements.

As a result, the UE capability framework needed additional parameters to identify whether the UE supports the features required for NR-NTN.

The Release 17 capability extensions help the gNB distinguish an NTN-capable NR UE from a UE that supports only conventional terrestrial NR operation.


  1. NTN-Specific UE Radio Access Capabilities

One of the most important aspects of UE Capability Exchange in NR-NTN is the reporting of NTN-specific capabilities.

A UE may support conventional NR functionalities without supporting all the features necessary for satellite communication.

Therefore, the network needs to identify the additional capabilities required for NTN operation.

3GPP TS 38.306 defines NR UE radio access capabilities, including NTN-related capability parameters.

14.1 nonTerrestrialNetwork-r17

One important Release 17 capability parameter is:

nonTerrestrialNetwork-r17

This parameter indicates whether the UE supports NR NTN access.

When the UE indicates support for this capability, it must support the essential NTN features specified by 3GPP.

These include:

  • Timer extensions in MAC, RLC, and PDCP layers.

  • Random Access Channel adaptations to handle long Round-Trip Time (RTT).

  • Acquisition of NTN-specific System Information Blocks (SIBs).

  • Support for more than one Tracking Area Code (TAC) per PLMN broadcast in one cell.

This capability is fundamental because it indicates whether the UE can support the essential requirements associated with NR-NTN access.

14.2 ntn-ScenarioSupport-r17

Another important parameter is:

ntn-ScenarioSupport-r17

This parameter indicates which NTN deployment scenarios are supported by the UE.

It is associated with two important satellite deployment categories:

  1. Geostationary Satellite Orbit (GSO).

  2. Non-Geostationary Satellite Orbit (NGSO).

GSO and NGSO deployments have different orbital characteristics, which affect satellite movement, propagation delay, Doppler conditions, and mobility behavior.

The ntn-ScenarioSupport-r17 parameter helps the network identify the NTN scenarios supported by the UE.

An important specification detail is that if the UE includes nonTerrestrialNetwork-r17 but does not include ntn-ScenarioSupport-r17, it is considered to support NTN features for both GSO and NGSO scenarios, including mobility between these scenarios.

14.3 Why These Capabilities Matter

The network cannot assume that all NTN-capable UEs support identical satellite deployment scenarios.

For example, a UE may support a particular NTN operating scenario but may have limitations when operating across different satellite configurations.

The capability information helps the gNB determine the supported operating conditions and configure the network accordingly.


  1. Difference Between Terrestrial NR and NR-NTN UE Capabilities

Although NR-NTN uses the NR radio access technology, satellite communication introduces additional requirements that are not generally encountered in conventional terrestrial deployments.

The UE capability framework therefore includes both common NR capabilities and additional NTN-related capabilities.

Parameter

Terrestrial NR

NR-NTN

RAT-Type

nr

nr

Main Capability Structure

UE-NR-Capability

UE-NR-Capability

Radio Access

Terrestrial gNB

NTN access architecture

Propagation Delay

Generally lower

Higher due to satellite distance

RTT Requirements

Conventional NR timing

NTN-specific timing considerations

MAC/RLC/PDCP Timers

Terrestrial requirements

NTN-related timer extensions

Random Access

Conventional NR procedures

NTN-specific RACH adaptations

System Information

Conventional NR system information

Includes NTN-specific information

Satellite Scenario Support

Not applicable

GSO/NGSO support where applicable

NTN Capability Indicator

Not required for ordinary TN access

nonTerrestrialNetwork-r17

The key difference is that NR-NTN retains the common NR capability reporting mechanism while adding parameters to identify support for non-terrestrial communication.


  1. Practical Example of UE Capability Exchange in NR-NTN

Consider an NR-NTN network in which a satellite provides 5G connectivity to a UE located in a remote geographical region.

The UE successfully establishes the initial RRC connection with the network.

However, the gNB needs to determine whether the UE supports the NTN-specific functionalities required for continued communication.

The gNB therefore initiates the UE Capability Transfer procedure.

Step 1: gNB Sends UE Capability Enquiry

The NR-NTN gNB transmits a UE Capability Enquiry message.

The message includes:

  • UE-CapabilityRAT-RequestList.

  • RAT-Type = nr.

  • Relevant NR capability request filters.

  • Additional capability request information, where required.

The purpose is to request NR radio access capabilities from the UE.

Step 2: UE Processes the Request

The UE receives the enquiry and identifies the requested RAT type.

Since RAT-Type is set to nr, the UE prepares its NR capability information.

It identifies the applicable NR capabilities and NTN-related capability parameters supported by its implementation.

Step 3: UE Sends UE Capability Information

The UE responds with a UE Capability Information message.

The message includes UE-CapabilityRAT-ContainerList.

The relevant capability container identifies RAT-Type = nr and carries UE-NR-Capability information.

The NR capability structure includes applicable NTN-specific parameters, such as nonTerrestrialNetwork-r17 and ntn-ScenarioSupport-r17.

Step 4: gNB Evaluates UE Capabilities

The gNB processes the received capability information.

It can identify whether the UE supports NR-NTN access and which relevant NTN scenarios and features are supported.

The network can then use this information when determining compatible configurations and feature usage.

16.1 Example Capability Evaluation

Capability Parameter

Example UE Report

Network Interpretation

RAT-Type

nr

UE reports NR capabilities.

nonTerrestrialNetwork-r17

Supported

UE supports NR-NTN access.

ntn-ScenarioSupport-r17

Reported

Identifies supported NTN scenarios.

NR Frequency Band

Supported band information

Helps evaluate frequency compatibility.

NTN Protocol Features

Supported capabilities

Helps determine compatible NTN operation.

This example illustrates how capability information helps the network identify whether the UE can support the intended NTN deployment.


  1. NR-NTN UE Capability Exchange Protocol Testing

UE Capability Exchange is an important area of 5G NR and NR-NTN protocol testing.

During protocol testing, engineers must verify that the UE correctly processes capability requests and reports the expected capability information.

The procedure involves multiple RRC Information Elements and capability structures that must be validated.

A protocol tester should understand both the signaling sequence and the actual capability information carried in the messages.

17.1 Important Test Cases

Test Case

Validation Objective

UE Capability Enquiry Reception

Verify that the UE correctly receives the enquiry message.

RAT-Type Validation

Verify correct processing of RAT-Type = nr.

Capability Filter Processing

Check whether the UE processes requested capability filters correctly.

UE Capability Information

Verify the UE's response to the capability enquiry.

RAT Container Validation

Check the UE-CapabilityRAT-ContainerList structure.

UE-NR-Capability Validation

Verify the reported NR capability information.

NTN Capability Validation

Check nonTerrestrialNetwork-r17 support indication.

NTN Scenario Validation

Verify the reported GSO/NGSO scenario support information.

Capability Consistency

Check consistency between reported capabilities and supported UE features.

17.2 Protocol Log Analysis Using QXDM and QCAT

Engineers working with 5G protocol testing tools such as QXDM and QCAT can analyze RRC signaling messages to validate the UE Capability Exchange procedure.

Important parameters to inspect include:

  • UE Capability Enquiry.

  • UE Capability Information.

  • UE-CapabilityRAT-RequestList.

  • UE-CapabilityEnquiryExt.

  • UE-CapabilityRequestFilterNR.

  • RAT-Type.

  • UE-CapabilityRAT-ContainerList.

  • UE-NR-Capability.

  • UE-NR-Capability-v1700.

  • nonTerrestrialNetwork-r17.

  • ntn-ScenarioSupport-r17.

The objective is to confirm that the UE responds correctly to the network's capability request and that the reported capability information matches the UE's supported functionality.

17.3 Common Troubleshooting Scenarios

Scenario 1: UE Does Not Report NTN Capability

If the UE does not indicate nonTerrestrialNetwork-r17, the engineer should investigate whether the UE implementation supports NR-NTN access and whether the capability information is being reported correctly.

Scenario 2: Incorrect RAT-Type

If the network requests NR capability information, RAT-Type must be correctly specified as nr.

The engineer should verify the UE Capability Enquiry and corresponding response.

Scenario 3: Missing Capability Information

If expected capability information is missing, engineers should inspect the capability request filters, RAT container structure, and relevant UE capability release support.

Scenario 4: NTN Scenario Mismatch

If the UE reports NTN support but the expected satellite scenario is not supported, engineers should examine ntn-ScenarioSupport-r17 and the applicable capability requirements.

Scenario 5: Capability and Configuration Mismatch

The gNB should not configure or rely on a feature that the UE has not indicated it supports when that feature requires UE capability support.

Engineers should correlate the capability response with subsequent RRC configuration and protocol behavior.


  1. Frequently Asked Questions (FAQs)

Q1. What is UE Capability Exchange in NR-NTN?

UE Capability Exchange is an RRC signaling procedure through which the NR-NTN gNB obtains information about the radio access capabilities supported by the UE. It helps the network identify whether the UE supports the required NR and NTN functionalities.


Q2. Which RRC messages are used for UE Capability Transfer?

Two main RRC messages are used: UE Capability Enquiry and UE Capability Information. The gNB sends the enquiry, and the UE responds with its capability information.


Q3. Why does the NR-NTN gNB use RAT-Type = nr?

NR-NTN is based on the NR radio access technology. Therefore, the gNB uses RAT-Type = nr to request the UE's NR capability information, including applicable NTN-specific capabilities.


Q4. What is UE-CapabilityRAT-RequestList?

It is an Information Element included in the UE Capability Enquiry message. It identifies the RAT types for which the gNB requests UE capability information and includes associated capability request filters.


Q5. What is UE-CapabilityRAT-ContainerList?

It is an Information Element included in the UE Capability Information message. It contains a list of capability containers, each associated with a particular RAT-Type and its corresponding capability information.


Q6. What is UE-NR-Capability?

UE-NR-Capability is the NR UE radio access capability structure that carries information about the NR features supported by the UE. For NR-NTN, it also includes applicable NTN-specific capability information.


Q7. What is nonTerrestrialNetwork-r17?

It is a Release 17 UE capability parameter that indicates whether the UE supports NR-NTN access. It is associated with essential NTN features, including protocol timer extensions, RACH adaptations, and NTN-specific system information acquisition.


Q8. What is ntn-ScenarioSupport-r17?

It is a capability parameter that indicates support for GSO and NGSO NTN scenarios. It helps the network identify the satellite deployment scenarios supported by the UE.


Q9. What is the difference between UE-NR-Capability and UE-NR-Capability-v1700?

UE-NR-Capability is the overall NR UE radio access capability structure. UE-NR-Capability-v1700 is a versioned extension associated with Release 17 capability information.


Q10. Which 3GPP specifications are important for UE Capability Exchange in NR-NTN?

The most relevant specifications include:

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

  • 3GPP TS 38.306 – NR; User Equipment (UE) Radio Access Capabilities.

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

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


    Conclusion

UE Capability Exchange is an essential procedure for enabling compatible operation between the NR-NTN gNB and the UE.

Although NR-NTN uses the existing NR radio access technology, satellite-based communication introduces additional technical requirements that must be supported by the UE.

Through the UE Capability Enquiry and UE Capability Information messages, the gNB can request and obtain the UE's supported NR capabilities.

The use of RAT-Type = nr allows the network to request NR capability information, while the UE-NR-Capability structure carries the corresponding radio access parameters, including applicable NTN-specific capabilities.

Parameters such as nonTerrestrialNetwork-r17 and ntn-ScenarioSupport-r17 help identify whether the UE supports NR-NTN access and the relevant satellite deployment scenarios.

For 5G protocol engineers, understanding this procedure is important not only for learning the NR-NTN architecture but also for practical RRC message analysis, capability validation, interoperability testing, and troubleshooting.

As 5G NTN deployments continue to evolve, UE capability reporting will remain an important part of ensuring that network features are correctly matched with UE capabilities.


  1. References and Further Reading

For a deeper understanding of UE Capability Exchange and NR-NTN, refer to the following official 3GPP and ETSI specifications.

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

  1. 3GPP TS 38.306 – NR; User Equipment (UE) Radio Access Capabilities

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

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

  1. ETSI – 3GPP TS 38.306 Release 17

 

Comments


  • Facebook
  • Twitter
  • LinkedIn

©2022 by Apeksha Telecom-The Telecom Gurukul . 

bottom of page