top of page

Timing Adjustments in NR-NTN: Understanding Timing Advance, Koffset and Uplink Synchronization in 5G NTN

17 hours ago
15 min read

Introduction  Timing Adjustments in NR-NTN

Timing synchronization is one of the most critical requirements in any cellular communication system. In terrestrial 5G New Radio (NR), the network maintains synchronization between the User Equipment (UE) and the gNB to ensure reliable uplink and downlink communication.

However, in a Non-Terrestrial Network (NTN), maintaining accurate timing synchronization becomes more challenging because communication takes place through satellites or other airborne platforms. The significantly longer propagation distances introduce additional delays, which directly affect the timing relationship between downlink reception and uplink transmission.

To address these challenges, 3GPP Release 17 introduces several enhancements to the existing 5G NR timing frameworks and a new framework for Timing Advance (TA) reporting in NR-NTN.

These enhancements help the NR-NTN UE compensate for propagation delays, maintain uplink synchronization, and perform uplink transmissions at the correct time.

The major timing-related mechanisms include:

  • NTN-specific Koffset for downlink and uplink timing relationships.

  • Uplink transmission timing adjustments.

  • Common Timing Advance (Common TA).

  • Common TA drift and drift variation.

  • Differential Koffset.

  • Timing Advance reporting by the UE.

  • NTN assistance information validity management.

This article explains how these mechanisms work, the important RRC information elements, associated MAC Control Elements, and their significance in NR-NTN protocol implementation and testing.


NR-NTN Timing Adjustments Infographic
NR-NTN Timing Adjustments Infographic

Table of Contents


  1. Why Timing Adjustments Are Required in NR-NTN

In terrestrial NR, the distance between the UE and the gNB is relatively small compared with satellite-based communication. Therefore, propagation delays are comparatively limited and can be managed through conventional timing synchronization mechanisms.

In NR-NTN, the communication path between the UE and the satellite payload introduces significantly higher propagation delays.

For example, in a satellite-based NTN:

  • The UE transmits an uplink signal toward the satellite.

  • The satellite payload receives and forwards the signal toward the NTN gNB.

  • The downlink signal follows the reverse communication path.

  • The propagation delay depends on the distance between the UE, satellite, and network reference points.

These propagation delays can affect:

  • Downlink-to-uplink scheduling relationships.

  • PUSCH transmission timing.

  • PUCCH transmission timing.

  • Random Access procedures.

  • Timing Advance estimation.

  • Uplink synchronization maintenance.

  • RRC and MAC-layer timing operations.

Therefore, NR-NTN requires additional timing mechanisms to compensate for satellite propagation delays and maintain accurate radio communication.


  1. Overview of the NR-NTN Timing Framework

The NR-NTN timing framework extends existing 5G NR timing procedures and introduces additional mechanisms to handle the unique characteristics of non-terrestrial communication.

The framework mainly addresses three important areas:

  1. Downlink and uplink timing relationships.

  2. Uplink transmission timing adjustments.

  3. Timing Advance reporting by the UE.

These mechanisms are supported through RRC information elements and MAC Control Elements.

The important components include:

Component

Function

NTN-Config

Provides NTN-specific timing assistance information

cellSpecificKoffset

Defines the scheduling offset used in NR-NTN timing relationships

Kmac

Provides an additional scheduling offset when DL and UL frame timing are not aligned at the gNB

Common TA

Provides network-configured common Timing Advance

Common TA Drift

Indicates the drift rate of Common TA

Common TA Drift Variant

Indicates the variation in Common TA drift

Differential Koffset

Supports timing offset adjustment through MAC signaling

TA Report

Supports UE Timing Advance reporting

Together, these mechanisms help the UE and network maintain accurate timing synchronization.


  1. Downlink and Uplink Timing Relationship

In NR-NTN, downlink (DL) and uplink (UL) timing are frame-aligned at the uplink timing synchronization reference point.

However, due to the satellite propagation delay, the timing relationship observed at the UE and the network may differ from conventional terrestrial NR.

The NR-NTN timing framework introduces an NTN-specific offset to account for these differences.

The timing relationship must consider:

  • Service link propagation delay.

  • Round-trip propagation time.

  • Common Timing Advance.

  • Scheduling offsets.

  • UE processing time.

  • Satellite and payload characteristics.

The network configures appropriate timing parameters so that the UE can determine when to transmit uplink signals.

This is particularly important when the UE receives downlink scheduling information and must transmit the associated uplink data at the correct time.


  1. Understanding Koffset in NR-NTN

Koffset is an important scheduling-related parameter in NR-NTN.

It supports the timing relationship between downlink and uplink transmissions by accounting for additional timing requirements introduced by satellite communication.

In terrestrial NR, scheduling relationships are designed around relatively short propagation delays.

However, in NR-NTN, the UE may need additional time between receiving downlink information and performing the associated uplink transmission.

The configured Koffset helps accommodate these NTN-specific timing requirements.

The cell-specific scheduling offset is provided through the cellSpecificKoffset-r17 information element.

It is expressed in the number of slots corresponding to a 15 kHz subcarrier spacing.

Why Is Koffset Important?

Koffset helps with:

  • DL-to-UL scheduling relationships.

  • Timing alignment between downlink reception and uplink transmission.

  • Supporting longer propagation delays.

  • Providing sufficient time for UE processing.

  • Maintaining reliable uplink scheduling.

The network configures the required offset based on the NTN deployment and timing requirements.


  1. Uplink Transmission Timing in NR-NTN

Uplink transmission timing is one of the most important aspects of NR-NTN synchronization.

The UE must transmit uplink signals at a time that allows the signals to reach the network within the expected reception window.

In satellite-based communication, the UE's uplink signal experiences a longer propagation delay than in terrestrial networks.

Therefore, the UE must adjust its transmission timing using the assistance information provided by the network.

Uplink transmission timing is influenced by:

  1. Service link propagation delay.

  2. Common Timing Advance.

  3. Timing Advance drift.

  4. Differential timing adjustments.

  5. Scheduling offsets.

  6. Satellite movement and changing propagation conditions.

The UE uses these parameters to determine the appropriate uplink transmission timing.

Accurate uplink timing is essential for maintaining synchronization and avoiding interference between transmissions from different UEs.


  1. NTN-Config Information Element

The NTN-Config information element provides important NTN-specific assistance information required by the UE.

It is included in the NTN system information, particularly in SIB19, through the NTN-Config-r17 configuration.

The information element contains several parameters that influence timing adjustments and uplink synchronization.

Important parameters include:

  • ephemerisInfo-r17

  • cellSpecificKoffset-r17

  • kmac-r17

  • ta-Info-r17

  • epochTime-r17

  • ntn-UlSyncValidityDuration-r17

  • ta-Report-r17

NTN-Config Parameter Overview

Information Element

Description

ephemerisInfo-r17

Provides satellite position, velocity, or orbital information

cellSpecificKoffset-r17

Defines the cell-specific scheduling offset

kmac-r17

Provides additional scheduling offset when DL and UL frame timing are not aligned at the gNB

ta-Info-r17

Provides common Timing Advance assistance parameters

epochTime-r17

Specifies the reference time associated with NTN assistance information

ntn-UlSyncValidityDuration-r17

Defines the validity duration of NTN uplink synchronization assistance

ta-Report-r17

Indicates whether UE Timing Advance reporting is enabled

These parameters allow the UE to maintain timing synchronization using network-provided assistance information.


  1. Ephemeris Information and Propagation Delay Estimation

Ephemeris information is essential for satellite-based NTN timing calculations.

The ephemerisInfo-r17 information element provides satellite-related orbital information that can be represented through:

  1. Satellite position and velocity information.

  2. Satellite orbital parameters.

The NR-NTN UE can use its GNSS-based position information together with satellite ephemeris information to estimate the service link propagation delay.

The estimation considers:

  • UE geographical position.

  • Satellite position.

  • Distance between the UE and satellite.

  • Speed of light.

  • Satellite movement.

How Does the UE Estimate Propagation Delay?

The basic propagation delay can be represented as:

Propagation Delay = Distance / Speed of Light

For a two-way propagation path:

Round-Trip Time (RTT) = Uplink Propagation Delay + Downlink Propagation Delay

In a simplified symmetric propagation scenario:

RTT ≈ 2 × One-Way Propagation Delay

The actual NTN timing calculation must also account for the satellite payload architecture and the relevant network timing reference points.

Accurate propagation delay estimation helps the UE determine the required timing adjustments for uplink transmission.


  1. Cell-Specific Koffset

The cellSpecificKoffset-r17 parameter defines the scheduling offset used for timing relationships in NR-NTN.

It is configured by the network and expressed in the number of slots for a 15 kHz subcarrier spacing.

This parameter helps accommodate the timing requirements associated with NTN communication.

Key Characteristics

  • It is configured through NTN assistance information.

  • It is associated with the cell-specific timing configuration.

  • It supports downlink and uplink scheduling relationships.

  • It provides an NTN-specific scheduling offset.

  • Its value is interpreted using the specified 15 kHz reference subcarrier spacing.

The UE uses the configured value when determining relevant scheduling timing relationships.


  1. Kmac Scheduling Offset

The kmac-r17 parameter provides an additional scheduling offset in NR-NTN.

It is used when downlink and uplink frame timing are not aligned at the NR-NTN gNB.

In such cases, the network can configure an additional offset to ensure that the UE has sufficient time to process downlink information and perform the associated uplink transmission.

Kmac is expressed in the number of slots corresponding to a 15 kHz subcarrier spacing.

Why Is Kmac Required?

Kmac supports timing operations where additional scheduling time is required due to NTN-specific propagation and frame alignment conditions.

It is particularly relevant for:

  • Applying downlink configuration changes.

  • Processing MAC Control Element commands.

  • Maintaining sufficient UE processing time.

  • Supporting appropriate timing relationships between DL and UL operations.

It is also used in the context of estimating UE-to-gNB round-trip timing.


  1. Common Timing Advance (Common TA)

Timing Advance is a fundamental mechanism used in cellular networks to ensure that uplink transmissions from different UEs arrive at the network with appropriate timing alignment.

In NR-NTN, Common Timing Advance provides a network-configured timing adjustment to compensate for the common propagation delay component.

The ta-Info-r17 information element provides the relevant Timing Advance parameters.

One of its important components is ta-Common-r17.

What Is ta-Common-r17?

The ta-Common-r17 parameter indicates the network-configured common Timing Advance value.

It has a granularity of:

4.072 × 10⁻³ μs

This parameter helps the UE compensate for the common timing delay associated with NTN communication.

Common TA is particularly important because satellite communication introduces much larger propagation delays than conventional terrestrial cellular networks.


  1. Common TA Drift and Drift Variation

Satellite movement continuously changes the distance between the UE and the satellite.

As a result, propagation delay also changes over time.

A fixed Common TA value may therefore become less accurate as the satellite moves.

To address this issue, NR-NTN provides additional parameters for Common TA drift and drift variation.

11.1 ta-CommonDrift-r17

The ta-CommonDrift-r17 parameter indicates the drift rate of the Common Timing Advance.

Its granularity is:

0.2 × 10⁻³ μs/s

It allows the UE to account for the time-dependent change in Common TA.

11.2 ta-CommonDriftVariant-r17

The ta-CommonDriftVariant-r17 parameter indicates the variation in the Common TA drift rate.

Its granularity is:

Dn × 10⁻⁴ μs/s²

The exact configured value and its interpretation depend on the applicable 3GPP parameter definition.

Why Are Drift Parameters Important?

These parameters help the UE account for:

  • Satellite movement.

  • Changing service link distance.

  • Time-dependent propagation delay.

  • Changes in uplink timing requirements.

  • Maintaining synchronization between assistance updates.

By using Common TA and its drift-related parameters, the UE can maintain more accurate uplink timing over the validity period of the assistance information.


  1. Differential Koffset in NR-NTN

Differential Koffset is another important mechanism used in the NR-NTN timing framework.

While the cell-specific Koffset provides a configured scheduling offset, Differential Koffset supports additional timing adjustment through MAC-layer signaling.

The relevant MAC Control Element is associated with Differential Koffset.

This allows timing-related adjustments to be communicated dynamically rather than relying only on the initial configuration.

Differential Koffset is important for supporting changes in timing requirements during network operation.

It complements the RRC-configured timing assistance and helps maintain the required timing relationship between downlink and uplink operations.


  1. Timing Advance Reporting Framework

NR-NTN introduces a framework that allows the UE to report Timing Advance information to the network.

This is important because the network needs information about the UE's timing conditions to manage uplink synchronization effectively.

The ta-Report-r17 parameter indicates whether Timing Advance reporting is enabled.

According to the NR-NTN timing framework, TA reporting can be enabled during the following procedures:

  1. Random Access performed due to RRC connection establishment.

  2. Random Access performed due to RRC connection re-establishment.

  3. RRC re-establishment-related procedures.

The framework uses a TA Report MAC Control Element to support reporting.

Why Is TA Reporting Required?

TA reporting helps the network obtain relevant timing information from the UE.

It supports:

  • Uplink synchronization management.

  • Timing-related network decisions.

  • Monitoring UE timing conditions.

  • Managing NTN-specific propagation effects.

This mechanism is especially relevant in satellite-based communication, where propagation delay changes over time.


  1. Epoch Time and Assistance Information Validity

NR-NTN assistance information is associated with a reference time known as epochTime-r17.

This parameter specifies the reference time for the NTN assistance information.

It represents the starting time of a downlink subframe, identified through the System Frame Number (SFN) and subframe number signaled along with the assistance information.

The UE uses this reference time when interpreting the time-dependent assistance parameters.

ntn-UlSyncValidityDuration-r17

The ntn-UlSyncValidityDuration-r17 parameter defines the validity duration of the NTN uplink synchronization assistance information.

It indicates the maximum time duration, measured in seconds from epochTime-r17, during which the UE can use the provided assistance information without acquiring new assistance information.

Why Is Assistance Validity Important?

Satellite movement causes propagation conditions to change continuously.

Therefore, NTN assistance information cannot always be considered valid indefinitely.

The validity duration helps the UE determine how long it can rely on the current timing assistance.

After the validity period expires, the UE needs to acquire updated assistance information to maintain accurate synchronization.


  1. Important NTN Timing Parameters

The following table summarizes the major parameters associated with timing adjustments in NR-NTN.

Parameter

Purpose

Signaling / Layer

ephemerisInfo-r17

Satellite position, velocity, or orbital information

RRC

cellSpecificKoffset-r17

Cell-specific scheduling offset

RRC

kmac-r17

Additional scheduling offset

RRC

ta-Common-r17

Common Timing Advance

RRC

ta-CommonDrift-r17

Common TA drift rate

RRC

ta-CommonDriftVariant-r17

Common TA drift variation

RRC

epochTime-r17

Reference time for assistance information

RRC

ntn-UlSyncValidityDuration-r17

Assistance validity duration

RRC

ta-Report-r17

Enables TA reporting

RRC

Timing Advance Command

Adjusts uplink timing

MAC CE

Differential Koffset

Supports additional timing offset adjustment

MAC CE

TA Report

Reports Timing Advance information

MAC CE

Note: RRC parameters are configured through NTN assistance information, while the relevant MAC Control Elements support timing-related control and reporting during operation.


  1. NR-NTN Timing Adjustment Signaling Flow

The timing adjustment process involves coordination between the NTN gNB and the UE.

A simplified signaling flow is described below.

Step 1: NTN Assistance Information Broadcast

The network provides NTN-related assistance information through SIB19, including the NTN-Config parameters.

Step 2: Satellite Ephemeris Acquisition

The UE obtains satellite ephemeris information and combines it with its GNSS-based position information.

Step 3: Propagation Delay Estimation

The UE estimates the service link propagation delay based on the relevant satellite and UE positions.

Step 4: Timing Configuration

The UE obtains configured timing parameters such as cellSpecificKoffset, Kmac, and Common TA.

Step 5: Uplink Timing Adjustment

The UE uses the available timing assistance and applicable Timing Advance mechanisms to determine the required uplink transmission timing.

Step 6: MAC Timing Updates

The network can provide timing-related commands through the relevant MAC Control Elements, including Timing Advance Command and Differential Koffset.

Step 7: Timing Advance Reporting

When enabled by the network, the UE can report Timing Advance information through the TA Report MAC CE during the supported procedures.

Step 8: Assistance Information Validity Monitoring

The UE monitors the validity duration of the assistance information and obtains updated information when required.


  1. Practical Example of Timing Adjustment

Consider an NR-NTN deployment in which a UE communicates with a satellite-based network.

The UE receives NTN assistance information through SIB19.

The assistance information includes:

  • Satellite ephemeris.

  • Cell-specific Koffset.

  • Kmac.

  • Common TA.

  • Common TA drift.

  • Epoch time.

  • Uplink synchronization validity duration.

The UE combines its GNSS-based location with satellite ephemeris information to estimate the service link propagation delay.

Based on this information, the UE determines the timing adjustments required for uplink transmission.

As the satellite moves, the service link distance changes. The Common TA drift parameters help the UE account for the changing timing conditions.

If additional timing adjustment is required, the network can use the supported MAC-layer timing mechanisms.

If TA reporting is enabled, the UE can also report the relevant Timing Advance information through the TA Report MAC CE during supported procedures.

This example demonstrates how RRC configuration, satellite assistance information, UE calculations, and MAC-layer signaling work together to maintain uplink synchronization in NR-NTN.


  1. NR-NTN vs Terrestrial NR Timing

The timing requirements of NR-NTN differ significantly from those of terrestrial NR.

Feature

Terrestrial NR

NR-NTN

Propagation Delay

Relatively low

Significantly higher

Timing Synchronization

Conventional NR mechanisms

NTN-enhanced timing framework

Satellite Ephemeris

Not required

Used for satellite-based assistance

Common TA Drift

Not a typical satellite-specific requirement

Supported through NTN assistance

Koffset

Conventional NR scheduling relationships

NTN-specific scheduling offset support

Kmac

Conventional timing configuration

Additional NTN scheduling offset support

TA Reporting

Existing NR timing procedures

NTN-specific reporting framework

Assistance Validity

Conventional synchronization management

Explicit NTN UL synchronization validity assistance

Mobility Characteristics

Terrestrial mobility

Satellite movement and changing service link distance

The main difference is that NR-NTN must account for long and time-varying propagation delays while maintaining the existing 5G NR communication framework.


  1. NR-NTN Protocol Testing and Troubleshooting

Timing adjustment mechanisms are important test areas for engineers working on NR-NTN protocol testing and log analysis.

Incorrect timing configuration can lead to uplink synchronization problems, scheduling failures, and communication interruptions.

The following test scenarios are useful when validating NR-NTN timing behavior.

19.1 NTN-Config Validation

Verify that the UE correctly receives and decodes the NTN-Config information through SIB19.

Check:

  • ephemerisInfo-r17

  • cellSpecificKoffset-r17

  • kmac-r17

  • ta-Info-r17

  • epochTime-r17

  • ntn-UlSyncValidityDuration-r17

  • ta-Report-r17

19.2 Ephemeris and Position Validation

Verify that the UE obtains the required satellite assistance information and uses the relevant GNSS-based position information for propagation delay estimation.

19.3 Koffset Validation

Check whether the UE applies the configured cell-specific scheduling offset correctly.

Validate the timing relationship between downlink reception and the associated uplink transmission.

19.4 Kmac Validation

Verify the configured Kmac value and its application in scenarios where DL and UL frame timing are not aligned at the gNB.

19.5 Common TA Validation

Check whether the UE correctly processes the Common TA information received through RRC configuration.

Validate the associated timing behavior during uplink transmission.

19.6 Common TA Drift Validation

Verify whether the UE accounts for Common TA drift and drift variation over the configured assistance validity period.

19.7 Differential Koffset Validation

Check the handling and application of Differential Koffset MAC signaling.

19.8 TA Reporting Validation

Verify whether TA reporting is enabled through the applicable configuration and whether the UE generates the TA Report MAC CE during supported procedures.

19.9 Assistance Validity Validation

Check whether the UE correctly monitors ntn-UlSyncValidityDuration-r17 and handles the expiry of the assistance information.

Common Troubleshooting Areas

Issue

Possible Area to Investigate

Uplink synchronization failure

Timing Advance configuration

Incorrect DL-to-UL timing

Koffset configuration

Scheduling timing issues

Kmac application

Timing mismatch over time

Common TA drift handling

Unexpected TA reporting behavior

ta-Report-r17 configuration

Assistance information expiry

Epoch time and validity duration

Uplink transmission timing errors

Propagation delay estimation

For practical validation, engineers should correlate RRC messages, MAC Control Elements, uplink scheduling events, and UE protocol logs.


  1. Key Engineering Takeaways

The major engineering points of NR-NTN timing adjustments are:

  1. NR-NTN enhances conventional 5G NR timing frameworks to support long satellite propagation delays.

  2. Koffset supports NTN-specific downlink and uplink scheduling relationships.

  3. Kmac provides an additional scheduling offset when DL and UL frame timing are not aligned at the gNB.

  4. Common TA compensates for the common propagation delay component.

  5. Common TA drift and drift variation help account for time-dependent timing changes.

  6. Satellite ephemeris and GNSS-based UE positioning support service link propagation delay estimation.

  7. Differential Koffset supports additional timing adjustments through MAC signaling.

  8. TA reporting allows the UE to report timing information when enabled.

  9. Epoch time provides the reference for NTN assistance information.

Uplink synchronization validity duration determines how long the UE can rely on the configured assistance information.


Frequently Asked Questions (FAQs)

Q1. What are timing adjustments in NR-NTN?

Timing adjustments in NR-NTN are mechanisms used to compensate for satellite propagation delays and maintain accurate timing relationships between downlink reception and uplink transmission.


Q2. Why is Timing Advance important in NR-NTN?

Timing Advance compensates for propagation-related timing differences so that uplink transmissions reach the network with appropriate timing alignment.


Q3. What is Koffset in NR-NTN?

Koffset is a scheduling-related offset used to support the timing relationship between downlink and uplink transmissions in NR-NTN.


Q4. What is Kmac in NR-NTN?

Kmac is an additional scheduling offset configured when downlink and uplink frame timing are not aligned at the NR-NTN gNB.


Q5. What is Common TA?

Common TA is a network-configured Timing Advance value that helps compensate for the common propagation delay component in NTN communication.


Q6. What is ta-CommonDrift-r17?

It is an RRC parameter that indicates the drift rate of the Common Timing Advance.


Q7. What is ta-CommonDriftVariant-r17?

It indicates the variation in the Common TA drift rate and helps account for changes in propagation-related timing conditions.


Q8. What is the purpose of ephemerisInfo-r17?

It provides satellite ephemeris information that the UE can use together with GNSS-based positioning to estimate service link propagation delay.


Q9. What is TA reporting in NR-NTN?

TA reporting is a mechanism through which the UE reports Timing Advance information to the network using the TA Report MAC CE when reporting is enabled.


Q10. What is ntn-UlSyncValidityDuration-r17?

It specifies the maximum validity duration of NTN uplink synchronization assistance information from the configured epoch time.


Q11. Which 3GPP release introduced these NTN timing enhancements?

The NTN timing enhancements discussed in this article are associated with 3GPP Release 17.


Q12. Which protocol layers are involved in NR-NTN timing adjustments?

Both RRC and MAC layers are involved. RRC provides timing assistance and configuration, while MAC Control Elements support timing commands and reporting.


  1. Conclusion

Timing adjustments are a fundamental part of NR-NTN because satellite communication introduces significantly longer and time-varying propagation delays compared with terrestrial 5G NR.

3GPP Release 17 enhances the existing NR timing framework through NTN-specific scheduling offsets, Common Timing Advance, drift compensation, Differential Koffset, and Timing Advance reporting.

The NTN-Config information element provides essential assistance parameters such as satellite ephemeris, cell-specific Koffset, Kmac, Common TA, epoch time, and uplink synchronization validity duration.

By combining satellite position information, propagation delay estimation, RRC configuration, and MAC-layer timing mechanisms, the UE can maintain accurate uplink synchronization in non-terrestrial networks.

For 5G protocol engineers, understanding these timing mechanisms is essential for NR-NTN implementation, protocol testing, log analysis, and troubleshooting.


  1. 3GPP References and Technical Resources

For a deeper understanding of NR-NTN timing adjustments, refer to the following official technical specifications and resources:

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

    https://www.3gpp.org/dynareport/38300.htm


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

    https://www.3gpp.org/dynareport/38331.htm


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

    https://www.3gpp.org/dynareport/38213.htm


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

    https://www.3gpp.org/dynareport/38321.htm


  5. 3GPP Technical Specifications

    https://www.3gpp.org/specifications-technologies/specifications-by-series


  6. ETSI Standards Search

    https://www.etsi.org/standards


Telecom Gurukul – India's #1 Telecom Training Institute

Learn from industry experts and gain hands-on knowledge in:

  • 4G LTE Protocol Testing and Log Analysis

  • 5G NR Protocol Testing and Log Analysis

  • 5G NTN Architecture and Protocol Procedures

  • QXDM and QCAT Log Analysis

  • RRC, NAS, PDCP, RLC, MAC and PHY

  • 5G ORAN and Telecom Cloud

  • 5G Developer Training with C and Linux


 

Comments


  • Facebook
  • Twitter
  • LinkedIn

©2022 by Apeksha Telecom-The Telecom Gurukul . 

bottom of page