5G Satellite Networks Guide
5G Satellite Networks Guide
Contents
Contents
Executive Summary..............................................................................................3
1. Overview............................................................................................................4
Conclusion ............................................................................................................32
Acronyms...............................................................................................................33
Acknowledgments.................................................................................................34
Endnotes................................................................................................................35
3 5G & Non-Terrestrial Networks | February 2022
Executive Summary
1. Overview
After this initial study, the 3GPP SA (Systems Aspects) workgroup started to
discuss the use cases for Satellite-based NTN as part of the Study Item on
Satellite Access in 5G [SP-170788]. The study identified three main categories
of use cases for satellite-based NTN:
The work in Release-16 also included aspects such as the adjustment • Delay in satellite
a study in Radio Access Network of allowed values for timers • QoS with satellite access and
(RAN) working groups on solutions to take into consideration with satellite backhaul
for New Radio (NR) to support non- larger latency, improvements
• RAN mobility with Non-
terrestrial networks with the objective on Random Access Channel
geostationary (NGSO)
to determine the necessary features (RACH) access procedure,
regenerative-based satellite
to enable NR support for NTN [RP- and enhancement of uplink
access
1907102]. Key aspects are discussed scheduling. In the control
in this white paper in Chapters 4 plane, mobility procedures are • Regulatory services with super-
through 6. enhanced to better support national satellite ground station
satellite use cases. SA WG5 addressed management and
These studies provided a baseline for
• RAN WG3 is considering orchestration aspects in their study
NR functionalities needed to support
architectural enhancements [SP-1901389], with results captured in
LEO and GEO satellites. Using that as TR 28.80810.
a baseline, 3GPP is now concentrating such as feed link switch over, as
on the normative work for support of well as cell related aspects, such 3GPP Core and Terminals workgroups
LEO and GEO satellites using 5G. The as Automatic Neighbor Relation CT WG1, WG3, and WG4 created a
following assumptions, which will be (ANR), User Equipment (UE) study item [CP-20323511] to address
covered in further detail throughout registration and paging. aspects of 5GC (5G core network)
the remaining chapters of this • RAN WG4 is specifying UE Radio architecture for satellite networks.
white paper, are now being made in Resource Management (RRM) The work in CT working groups
standards: and RF requirements concentrates on aspects related to
In SA, WG1 is specifying the Stage 1 Public Land Mobile Network (PLMN)
• 5G-NR Frequency Division Duplex
requirements when considering the selection, and the results are captured
(FDD) is used.
use cases described in TR 22.8224. in Technical Report TR 24.82112. The
• Earth fixed Tracking area is study phase is completed and the
These requirements are being
assumed with Earth fixed and normative work will follow, with the
added directly to the existing SA1 5G
moving cells. Stage 2 solutions and requirements
specification, TS 22.2615: Service
• UEs with Global Navigation Requirements for the 5G System. for public land mobile network (PLMN)
Satellite Systems (GNSS) selection for satellite access.
capabilities are assumed. SA WG2, which encompasses the
system architecture, started their 3GPP also approved a study item for
• Transparent payload is assumed. enabling the operation of the Internet
satellite study in Release-17, with
In 3GPP RAN, the Work Item on the creation of the Study Item on of Things (IoT) NTN [RP-19323513].
Solutions for NR to Support Non- Architecture Aspects for Using Satellite This work is based on the existing
Terrestrial Networks (NTN) [RP- Access in 5G [SP-1812536]. The 3GPP features of Narrowband IoT
2117843] is specifying feature scope of this work was to identify key (NB-IoT) and enhanced Machine
enhancements such as: issues for satellite-based NTN in the Type Communication (eMTC), which
5G system architecture and provide were introduced in Release-13, over
• In RAN WG1 and WG2, feature
solutions for both direct satellite satellite communications. The study
enhancements to address
access and satellite backhaul. The assumes that the bands utilized are
issues related to satellite’s
result of the work is captured in the in the sub-6 GHz frequency range,
long propagation delays, large
Release-17 Technical Report TR with both LEO or GEO satellite orbits,
Doppler effects, and moving
23.7377. In November of 2019, SA2 assuming a transparent payload. The
cells are being specified. These
approved the Release-17 normative following scenarios are considered:
involve enhancements on timing
relationships, Hybrid Automatic work associated with this TR [SP- • Scenario A: GEO based
Repeat Request (HARQ), and 1913358]. The aspects that are being
• Scenario B: LEO based, altitude
uplink synchronization. addressed by SA2 in the normative
of 600km and 1200km, with
work are as follows:
• Some protocol stack functionality steerable beams
is also being enhanced in • Mobility Management with large • Scenario C: LEO based, altitude
RAN WG2. In the user plane, coverage areas and with moving of 600km and 1200km, with
normative changes involve coverage areas fixed beams
7 5G & Non-Terrestrial Networks | February 2022
Chapter 3 summarizes potential use cases and scenarios for satellite service for non-terrestrial networks. Those use
cases are identified in the following table below:
Figure 4.1-2 Satellite NTN typical scenario based on transparent payload (source: 3GPP TR 38.821-g00)
Figure 4.1-3 Satellite-based NTN typical scenario based on regenerative payload (source: 3GPP TR 38.821-g00)
• A satellite which may implement either a transparent or a regenerative (with on board processing) payload. The
satellite typically generate several beams over a given service area bounded by its field of view. The footprints of the
beams are typically of elliptical shape. The field of view of a satellite depends on the on-board antenna diagram and
minimum elevation angle.
» A transparent payload: Radio frequency filtering, frequency conversion and amplification only at the satellite.
Hence, the waveform signal repeated by the payload is unchanged.
»
A regenerative payload: Radio frequency filtering, frequency conversion and amplification as well as demodulation/
decoding, switch and/or routing, coding/modulation at the satellite. This is effectively equivalent to having all or
part of base station functions (e.g., gNodeB or “gNB”) on board the satellite.
• Inter-satellite links (ISL) are optional in case of a constellation of satellites. This will require regenerative payloads on
board the satellites. ISL may operate in RF frequency or optical bands.
• User Equipment are served by the satellite within the targeted service area.
The different types of satellites are listed here:
For more details on satellite-based NTN reference scenarios, see 3GPP 38.82119 section 4.2.
3GPP Release-16 included studies on both architecture options (transparent and regenerative payload). The workgroup
decided to work on standardization of the transparent payload option, and not to standardize the regenerative payload
option in Release-17 due to various technical reasons. Thus this white paper focuses on the transparent payload option.
This regenerative payload option is under consideration for standardization for Release-18 with three potential design
options: 1) full gNB on board 2) gNodeB Centralized Unit (gNB-CU) on the ground, gNodeB Distributed Unit (gNB-DU) on
board, which face challenges in handling the F1 interface, as defined in 3GPP between CU and DU) 3) gNB on the ground,
LLS (Low layer split), RU (Radio Unit) on satellite, which is faced with challenges in the Common Public Radio Interface
(CPRI) interface that is not standardized in 3GPP.
“the electromagnetic wave that are transmitted from Earth surface are converted by a satellite receive antenna
into an electric signal which is channel filtered and amplified by low-noise amplifier (LNA). The signal is then
frequency converted. A high-power amplifier (HPA) delivers finally the signal to a transmitting antenna generating
a reconditioned electromagnetic wave towards the Earth surface where receive station are located”
Figure 4.2 Networking-RAN architecture with transparent satellite (source: 3GPP TR 38.821-g00)
Hence the satellite repeats the NR-Uu radio interface from the feeder link (between the satellite-based NTN gateway and
the satellite) to the service link (between the satellite and the UE) and vice versa. The Satellite Radio Interface (SRI) on
the feeder link is the NR-Uu. In other words, the satellite does not terminate NR-Uu. The satellite-based NTN Gateway (GW)
supports all necessary functions to forward the signal of NR-Uu interface.
Different transparent satellites may be connected to the same gNB on the ground. Note: While several gNBs may access
a single satellite payload, the description has been simplified to a unique gNB accessing the satellite payload, without loss
of generality.
Figure 4.2-1 Satellite payload + feeder link + GW + Non-NTN infrastructure gNB (3GPP R4-2115640)21
16 5G & Non-Terrestrial Networks | February 2022
NR-Uu timers may have to be extended to cope with the long delay of the feeder
link and service link. In the context of a LEO scenario with ISL, the delay to be
considered shall encompass at least the feeder link (SRI) and one or several
ISLs.
Both CP (control plane) and UP (user plane) protocols are terminated on the
ground.
• With respect to CP, this scenario does not pose any particular issue, but
there is a need to adapt to the much longer roundtrip times of the Uu that
can be addressed by implementation.
• Concerning UP, apart from issues arising from the longer roundtrip time for
UP packets, the UP protocol itself is unaffected. The longer delay on the Uu
interface will, however, require more buffering for the UP packets into the
gNB.
Satellite-based NTN will implement position-based and fixed tracking area (TA)
satellite access. It is also assumed that UEs have the capability to determine
their location.
According to 3GPP SA2 Study Report 23.73722, the following principles will be
applied in satellite-based NTN networks:
For reference, figure 4.2-1 below is an illustration of a fixed tracking area and
mobility for NGEO satellite:
17 5G & Non-Terrestrial Networks | February 2022
Figure 4.2-2 Non-Geostationary Satellite Beam steering and Handover (source: 3GPP SA2 study report 23.737)
In principle, NSA (Non standalone) operation between NTN and TN, such as
running one leg connection with NTN and another leg connection with TN,
is not precluded in standards, it can be potentially challenging. Running Xn
connections between an NTN gNB and a terrestrial gNB is itself very challenging
due to the many constraints like UP flow control and other factors.
It is expected the next generation (NG) based mobility should work to transition
between NTN and TN. It is anticipated that NTN can interact with 5G, 4G or
even 3G terrestrial networks via legacy inter-RAT (radio access technology)
procedures. Detailed idle mode and connected mode procedures are currently
left for vendor implementation.
Increased delays can also cause Channel Quality Indicator (CQI) reporting and
Modulation Coding Scheme (MCS) assignment delays as channel conditions like
rain fade on DL and UL can change. Therefore, the gNB needs to have robust
algorithms to maintain the throughput performance to compensate for higher
Block Error Rate (BLER) at the UE or gNB. The scheduler needs to compensate
MCS and resource block (RB) assignment for various signal to noise (SNR)
conditions.
In higher layers like the Media Access Control (MAC), Radio Link Control (RLC),
and Packet Data Convergence Protocol (PDCP), idle mode and connected
mode related procedures and signaling including system information,
registration, paging, use of satellite ephemeris information, location information,
measurement configuration, RRM (Radio resource management), and hand over
procedures all need to be updated. These are part of ongoing Release-17 work
item activities to update normative work, such as update specifications.
and RAs, so no impacts are identified on the core network’s (CN)’s procedures
or functional elements with regards to TA Update and RA updates.
However, to cope with longer delay introduced with satellite access, certain
timers in session management and mobility management need to allow much
longer values. These values will depend on “RAT type,” which will have a new
value in RAT types indicating the UE is accessing the Core network via satellite.
It is proposed that UE capable only of connectivity via NTN RAN use extended
timers defined to handle satellite delays. For UEs that can use both NTN RAT and
terrestrial RAT, it is proposed that the UE uses regular timers or extended timers
based on the RAT Type in use.
The table below is taken from 3GPP 23.73725 (table 6.10.1.3-1), summarizing
the timer impacted:
Table 4.2 Summary of timers impacted by satellite RTT and suggested timer value increase
Network Slicing can be handled using the existing terrestrial network framework.
There is expected to be no new elements added to 3GPP Network Slicing
standard. Operators may create new slice based on NTN characteristics
(coverage, speed, delay) and charge accordingly.
Traditionally with 3G/4G backhaul over the existing MEO/GEO satellites have
been challenging due to the larger latency associated with the distance of
satellites, as depicted below:
Figure 5.1 LEO, MEO and GEO satellite altitudes and latencies
22 5G & Non-Terrestrial Networks | February 2022
These large latencies (125 – 800 ms) provide an inadequate user experience for
real-time applications such as voice, video and gaming. MEO and GEO satellites
require higher power on return link (RL/UL) thereby requiring robust end user
devices.
With Release-17 and direct connectivity planned to UEs, the user experience
should significantly improve when LEO satellites with lower latencies are
deployed with 5G, compared to with MEO/GEO based.
Other issues to consider with LEO compared to MEO and GEO include an
increase of handoffs across satellites and possible beams depending on
number of beams from a satellite to UE. For a LEO satellite, inter-satellite
handoffs can be expected every 3 to 10 mins between 60 degrees latitude,
depending on number of satellites that are visible and power constraints.
Therefore, it is critical that the UE’s know the ephemeris of the satellites and
frequencies to use in a timely manner with precise time syncing. These are
technical challenges that can be solved as satellite trajectories are quite
predictable. Thus, there are tradeoffs between different satellite deployment
considerations and the choice depends on the use case being considered.
However, defining these bands in 3GPP does not mean such spectrum will be
used in commercial NTN networks. There are countries in different regions
that want to use these bands for terrestrial use, so it still requires coordination
between different countries and between countries and satellite operators to
allow use of these bands for certain NTN networks. Such coordination should be
done via the ITU.
For instance, there is a need to ensure that cross-border issues are solved
between those countries that choose the NTN and those that choose the TN for
spectrum in 3GPP frequency band 1 and band 65/n65. This frequency band
23 5G & Non-Terrestrial Networks | February 2022
Similarly, B7 defined in ITU with frequency range 2000-2020 Mhz (UL) and
2180-2200Mhz (DL) overlaps completely with Band 23 defined in 3GPP for ITU
Region 2 (America). Spectrum coordination would be needed if such band is
added to NR band list in 3GPP for terrestrial use and some satellite operators
want to use it for non terrestrial network in the future.
During the WRC-19 an agreement was made with the development of Resolution
212 (Rev. WRC-19)27
“Implementation of IMT in the frequency bands 1 885-2 025 MHz and 2 110-2
200 MHz” and in the Annex of this Resolution “Guidance on the implementation
of technical and operational measures to facilitate coexistence between
terrestrial and satellite components of IMT in the frequency bands 1 980-2 010
MHz and 2 170-2 200 MHz” is given.
FR2 spectrum use for NTN is still being discussed and no agreement has been
reached at the time of this document.
For higher frequencies above 24Ghz Lawful interception should be MCC hint received from the network
(FR2 range), there is possibility for supported in the roaming case, like into account in this fallback to another
co-existence with certain limitations, typical roaming operation among PLMN of the indicated MCC.
but this is to be studied further in different MNOs. Emergency calls
In addition, the UE also needs to pre-
3GPP. It is too early at this stage to may be better handled by the SNO
compensate for the Doppler shift and
determine how feasible it is. Even if to avoid delay in call setup. Special
propagation delay, in order to align
it is technically possible, co-channel consideration needs to be given for
the forward link waveform and reverse
or coexistence with adjacent services QoS and SLA (service level agreement)
link waveform at a specific point of
studies should be managed and due to the difference in user
the communication link such as at the
regulated by regional regulators. performance (throughput, latency)
satellite. A UE with GNSS capability
between NTN and TN.
In 3GPP, the RAN4 Working Group will can determine its frequency and time
run coexistence studies on adjacent It should be noted the definition of compensation through its location and
channels only (NTN-TN and NTN- the PLMN ID for the SNO operator the System Information Block (SIB)-
NTN) and this work is expected to be is up to the SNO operator itself and broadcast satellite ephemeris. As a
completed by March 2022. is outside scope of this white paper. result, 3GPP Release-17 has focused
Optionally for the SNO, it could on UE with GNSS capability. Having
5.4 Roaming and choose to broadcast the MNO’s GNSS capability could also help for
RAN sharing PLMN as Equivalent Home PLMN radio link synchronization, Tracking
(EHPLMN) from its satellite network, Area Code (TAC) assignment and
NTN and TN can operate in either
while defining its HPLMN as a lower paging, Tracking Area Identifier (TAI),
roaming mode or sharing mode
priority PLMN than the MNO’s PLMN forbidden PLMN list, etc.
between Satellite Network Operator
ID in the EHPLMN List. Per 3GPP
(SNO) and Terrestrial Mobile Network Handheld devices in FR1 are
standard (23.122 and 31.10228), the
Operator (MNO). Satellite based NTN supported (e.g., power Class 3 UE).
SNO subscriber will treat the MNO’s
can extend a TN’s coverage to where
network as higher priority network
an MNO does not have presence and 5.6 County specific
to camp, so the SNO subscriber
service backup, for example in the PLMN selection
can access the MNO’s network to
case where a TN loses coverage due
benefit from the greater speed and Per 3GPP 23.73729, system
to a natural disaster.
lower latency and only use the SNO’s complexities can be expected
In roaming situations, a SNO satellite network when it’s outside when a satellite’s coverage crosses
maintains its own 5G NTN network of the MNO’s terrestrial network country borders and/or the UE’s
(satellite, gNB, core network) but coverage. communications use terrestrial
allows MNO users to connect to equipment (e.g., Earth stations) that
the SNO’s network when there is 5.5 UE eco-system are in a different country to the UE.
no terrestrial coverage. MNO users and availability This is illustrated in figure 5.3.
still prioritize the MNO’s TN and only
Ideally, UE should be capable of Another similar situation may arise
use the SNO’s NTN when there is no
knowing its location within a certain with the use of satellite backhaul. A
terrestrial network coverage.
country so it can limit its PLMN satellite transport would in this case
The MNO’s network should configure selection to PLMNs broadcasting the interconnect a RAN with a 5GC. The
the SIMs of its users with SNO’s PLMN Mobile Country Code (MCC) of a given satellite’s coverage could overlap more
ID so the mobile users can scan and country. This requires the UE to have than one country. This is illustrated in
access the SNO’s network when it GNSS capability, especially for the Figure 5.3-1.
travels outside of the MNO’s terrestrial GEO satellite case. If the UE receives
This creates issues related to
network and be covered by SNO’s a REGISTRATION REJECT message
emergency call, lawful interception,
NTN network. The MNO subscribers indicating that the requested PLMN is
charging & billing, and public warning
would re-register to its original MNO not allowed in the present UE location,
notification. The current solution
home network once it returns to the then the UE attempts to select another
proposed in 3GPP (described in
coverage of home network. PLMN instead. The UE may take the
23.737 chapter 6.13) uses county
specific PLMN selection to address
these issues.
25 5G & Non-Terrestrial Networks | February 2022
On the UE side: if the UE is Figure 5.3 Satellite access with satellite beams overlapping several countries
aware of its present location
inside certain country, the UE
should use that knowledge to
limit its PLMN selection to only
PLMNs of the country of the
present UE location. In case
of Visiting Public Land Mobile
Networks (VPLMN), if the UE is X
aware that it has moved away
from the country of the current
registered VPLMN, then the UE
should use that information to
perform background scanning
of higher priority PLMNs among
those PLMN candidates that are
available in the country of the
present UE location.
Satellites in LEO orbits move with high-speed relative to a fixed position on Earth.
The satellite beam towards the Earth defines the area on Earth that the satellite
can provide services to the users. There are two cases on how the satellite
beams can operate:
The times the UE remains under the coverage area of the same satellite for the
moving-beam scenario are illustrated in the table below. The table shows that
this time is dependent on the UE speed, the direction of the UE movement (i.e.,
same direction or opposite directions of the satellite movement), and the cell
size (which is determined based on the satellite beam width: larger beam widths
yield in larger cell sizes).
27 5G & Non-Terrestrial Networks | February 2022
Table 6.1 Time the UE Remains in a Cell for a Moving-Beam Scenario • The main concern for proving
the satellite level orbital
parameters is about the size of
such information. The following
solutions can be considered to
provide orbital parameters per
satellite:
• Pre-provision satellite level
orbital parameters for all the
satellites that may serve the
UE in the UE uSIM, including a
satellite ID or index. The satellite
ID of the serving satellite is
then broadcast in the System
Information so that the UE can
find the ephemeris data stored
in uSIM.
• Broadcast satellite level orbital
parameters of the serving
satellite in system information
and the UE derives the position
coordinates of the serving
satellite.
• Information of the neighbouring
satellites can also be provided
• For the smallest cell diameter 6.1 Initial Cell Selection to UE via system information
(50km), the time a stationary or dedicated RRC signalling to
This is a summary of the steps
UE remains under the coverage assist mobility handling.
undertaken by an NTN in selecting an
area of the same satellite is
approximately 6.6 seconds.
initial cell: 6.2 Mobility in Idle Mode
For the largest cell diameter, • When the UE powers-on, it During idle mode, the UE location is
this time is increased to searches for the first satellite- known at the Tracking Area level. The
approximately 132 seconds. The based NTN cell that it can camp Tracking Area is defined as a set of
table shows that the variation of on. If the UE has the satellite cells, each cell belonging to a Tracking
this time as a function of the UE orbital information (I.e., the Area identified by a Tracking Area
speed is relatively small (+/- 4%), ephemeris data), the cell search Code (TAC). The TAC is sent in the
so for analysis purposes, UE can be optimized and take lesser System Information in the Broadcast
speeds can be neglected. time. It is also beneficial if the channel. Multiple cells may belong to
• The time the UE remains in UE knows the Round Trip Time the same tracking area, in which case
the cell for the moving-beam (RTT) well enough to be able they broadcast the same TAC.
scenario is quite short when to do random access. For this,
The UE location is known to the
compared to the fixed beam the initial system information
network as the UE performs the
scenario or to the terrestrial may need to contain further
Registration procedure when it first
systems. The implications in idle ephemeris information on the
turns on. The Registration Request
mode and connected mode UEs exact location of the cell (or
message includes the TAC of the cell
are discussed in the following the satellite broadcasting the
the UE is currently camped on. As the
sub-sections. cell). This information can be
UE moves around and changes cells,
given with respect to the orbital
it reads the System Information in the
plane that the UE already has
new cell to determine the Tracking
information about.
Area of that cell. The UE is allowed to
28 5G & Non-Terrestrial Networks | February 2022
move within the same Tracking Area Figure 6.1 An example for Fixed Tracking Areas [TR 38.821]30
without performing any updates. If the
UE enters a new cell with a different
TAC, the UE must perform Registration
in the new cell and send the new
TAC in order to update the network
of its location. Therefore, the larger
the tracking area, the lesser is the
signalling from the UE to the network,
minimizing the UE power consumption.
RRC Reconfiguration Complete. For the LEO, however the latter requires conditional HO in LEO scenarios
uplink, the UE can potentially continue consideration of satellite movement. should consider deterministic
sending data to the source gNB until To avoid extended service interruption, satellite movement.
RRC Reconfiguration with sync is latency associated with mobility • Timing advance based triggering:
received, the interruption time can be signalling should be addressed for Triggering based on the timing
defined as the time from UE receiving both cases. advance value to the target cell.
RRC Reconfiguration with sync (Step
Adding Other Handover Triggers • Elevation angles of source and
3) until the target gNB receives the
target cells-based triggering:
RRC Reconfiguration Complete (Step Besides measurement triggered
additional triggering conditions
6). handovers, other triggers can be
based on elevation angles of
considered for handover decisions, as
Propagation delay in satellite-based source and target cells can be
follows:
NTN is orders of magnitude higher considered in satellite-based
than terrestrial systems, introducing • Triggering based on location of NTN.
additional latency to mobility signalling the UE and the satellite: Location • These triggering conditions may
such as measurement reporting, triggering condition may be be considered independently or
reception of the HO command, and expressed as distance between jointly.
HO request/ACK (if the target cell the UE and the satellite. Conditional Handover
originates from a different satellite). • Timer-based triggering:
The deterministic satellite movement
GEO scenarios are characterized by Triggering conditions based
can also be considered in the
much larger propagation delay than on the time a region is served
handover decision. Configurations
can be considered. Time-based
30 5G & Non-Terrestrial Networks | February 2022
related to the target gNB can be provided to the UE in advance, as the satellite
orbit is known. This solution is referred to as conditional handover: The handover
configuration (i.e., configuration in the new cell) is provided in advance, together
with a condition that will trigger such handover before the radio conditions get
too poor. The UE monitors the condition and performs the handover when the
condition is met.
Another benefit of knowing the satellite ephemeris is that if the UE knows its
own location. In this case, it can estimate the required Timing Advance value
of the target gNB. The UE then can perform pre-compensation of delay and
Doppler shift for all UL transmissions using that information.
As GEO satellites are relatively static, dynamic neighbor cell set is not anticipated
to be a challenge.
Configuration Considerations
It is important to note that the received signal strength in a satellite cell does not
vary much throughout the cell, as it is illustrated in the figure below. Therefore,
the difference of the signal strength measured at the center of the cell versus
the edge of the cell is small, and this should be taken into consideration when
configuring the measurement triggering and measurement reporting thresholds.
Measurement Optimizations
There are some optimizations that can be done to optimize the UE measurement
performance by taking advantage of the fact that the UE is being serviced by a
satellite with known orbit.
31 5G & Non-Terrestrial Networks | February 2022
Conclusion
There is much more work to be done regarding NTN in future releases at 3GPP.
3GPP Release 17 will introduce new network topologies into the 3GPP specs
that include high-altitude platforms and Low Earth Orbit and geosynchronous
orbit satellites.
Acronyms
A-GNSS: Assisted GNSS ISL: Inter Satellite Links PLMN: Public Land Mobile Network
ATG: Air to Ground LCS: Location Services RLC: Radio Link Control
Acknowledgments
5G Americas’ Mission Statement: 5G Americas facilitates and advocates for
the advancement and transformation of LTE, 5G and beyond throughout the
Americas.
Endnotes
1
RP-171450
2
RP-190710
3
RP-211784
4
TR 22.822
5
TS 22.261
6
SP-181253
7
TR 23.737
8
SP-191335
9
SP-190138
10
TR 28.808
11
CP-203235
12
TR 24.821
13
[RP-193235]
14
TR 36.763
X. Lin, S. Rommer, S. Euler, E. A. Yavuz, and R. S. Karlsson, “5G from space: An overview of 3GPP non-terrestrial
15
X. Lin, S. Rommer, S. Euler, E. A. Yavuz, and R. S. Karlsson, “5G from space: An overview of 3GPP non-terrestrial
16