5G RAN2.1 Optional Features Description - Draft 1.0 20180808
5G RAN2.1 Optional Features Description - Draft 1.0 20180808
1 Optional Features
Issue 01
Date 2018-08-13
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Contents
1 Change History..............................................................................................................................1
2 Radio & Performance....................................................................................................................2
2.1 Massive MIMO Capacity Package.................................................................................................................................2
2.1.1 FOFD-010010 MU-MIMO Basic Pairing...................................................................................................................3
2.1.1.1 Downlink MU Pairing..............................................................................................................................................3
2.1.1.2 Uplink MU Pairing...................................................................................................................................................4
2.2 Massive MIMO Coverage Package................................................................................................................................5
2.2.1 FOFD-010110 3D Coverage Pattern...........................................................................................................................5
2.2.2 FOFD-021209 Full Channel Coverage Enhancement...............................................................................................16
2.2.2.1 Downlink PMI Precise Weight...............................................................................................................................16
2.2.2.2 MIMO-based Uplink Advanced Receiver..............................................................................................................17
2.2.2.3 SSB Power Aggregation.........................................................................................................................................18
2.3 Massive MIMO User Experience Package...................................................................................................................18
2.3.1 FOFD-010020 SU-MIMO Multiple Layers..............................................................................................................18
2.3.1.1 DL SU Multiple Layers..........................................................................................................................................19
2.3.1.2 UL SU Multiple Layers..........................................................................................................................................19
2.3.1.3 Downlink Inter-Layer Power Control Optimization..............................................................................................20
2.4 UL and DL Decoupling................................................................................................................................................21
2.4.1 FOFD-010205 UL and DL Decoupling.....................................................................................................................22
2.5 High Order Modulation Package..................................................................................................................................25
2.5.1 FOFD-010050 DL 256QAM.....................................................................................................................................25
2.6 DC&CA Package..........................................................................................................................................................26
2.6.1 FOFD-020205 Intra-band CA...................................................................................................................................26
2.7 UCN..............................................................................................................................................................................28
2.7.1 FOFD-021202 CoMP................................................................................................................................................28
2.8 Interoperability.............................................................................................................................................................29
2.8.1 FOFD-021209 Inter-RAT Mobility Between NG-RAN and E-UTRAN..................................................................30
1 Change History
Summary
This feature uses the same orthogonal frequency division multiplexing (OFDM) time-
frequency resources for the uplink and downlink data transmission of multiple UEs for spatial
multiplexing, improving uplink and downlink capacity and spectral efficiency.
Benefits
This feature improves the uplink and downlink cell capacity and coverage performance.
Description
Downlink MU pairing allows the base station to use the same OFDM time-frequency
resources for the downlink data transmission of two or more UEs. This improves the spatial
multiplexing gain, spectral efficiency, and improves the downlink throughput to a certain
extent. In heavy load scenarios, this function helps relieve network load and improves user
experience.
Benefits
This function improves the spatial multiplexing gain, downlink throughput, and user
experience.
Enhancement
The MU rank adaptation is added to 5G RAN2.1.
With MU rank adaptation, each UE involved in MU MIMO pairing determines the rank to be
paired based on the channel characteristics, traffic volume, and channel correlation between
UEs. This improves spatial multiplexing gains.
Description
Uplink MU pairing allows two or more UEs to use the same OFDM time-frequency resources
for the uplink data transmission. This improves the spatial multiplexing gain, spectral
efficiency, and improves the uplink throughput to a certain extent. In heavy load scenarios,
this function helps relieve network load and improves user experience.
Benefits
This function improves the spatial multiplexing gain, uplink throughput, and user experience.
Enhancement
None
Dependency
Hardware
Base stations working in sub-6 GHz frequency bands support 8T8R or higher
specifications.
UE
None
Core network
None
Other NEs
None
Other features
None
Summary
This feature designs different broadcast beam coverage scenarios. The horizontal and vertical
coverage scopes vary according to scenarios. In certain scenarios, the tilt and horizontal
azimuth are adjustable.
This feature supports multiple scenario-based broadcast beams. When interference exists in
the horizontal direction, beams for a small horizontal coverage scope are selected to reduce
interference. For high-rise buildings, beams suitable for a large vertical coverage scope are
selected to improve vertical coverage. For squares, beams specifically designed for a large
horizontal coverage scope and a small vertical coverage scope are selected to improve
coverage at the cell edge.
In certain broadcast beam scenarios, the tilt and horizontal azimuth can be configured using
parameters. The tilt and horizontal azimuth are adjusted by 1 degree.
Benefits
Based on different networking scenarios, different scenario-based broadcast beams are
selected to reduce the difficulty in site selection planning and site optimization. This reduces
the optimization and coordination costs, and enables adjustment of the tilt and horizontal
azimuth. In the case of severe interference from neighboring cells, the tilt and horizontal
azimuth can be adjusted to ensure that beams target UEs in a local cell. This reduces the
overlapped coverage in neighboring cells. In addition, more beam directions can be used by
means of tilt and horizontal azimuth adjustment, effectively helping to meet different
coverage requirements and facilitate flexible networking.
Description
5G RAN2.0 supports a maximum of 1 default scenario and 16 coverage scenarios. The
gNodeB sets the scanning scope and tilt of the beam to different values to support the
applications in different scenarios, as listed in Table 1.1 and Table 1.2.
buildings.
The
horizontal
coverage in
this scenario
is better than
that in
scenario 2.
The
coverage
near the cell
center in this
scenario is
slightly
poorer than
that in
scenario 2.
SCE Int This scenario 90° 6° –2 – Yes No No No No
NA erf uses non- to 10
RIO ere standard 3- 9 to
_2 nc sector 10
e networking.
When strong
interference
sources exist
in
neighboring
cells, the
horizontal
coverage of a
cell can be
reduced to
mitigate the
interference
from
neighboring
cells. This
scenario
applies to
low-rise
buildings
since the
vertical
coverage
scope is
small.
SCE Int This scenario 65° 6° –2 – Yes No Yes No Yes
NA erf uses non- to 22 (Azi (Tilt:
RIO ere standard 3- 9 to mut -,
_3 nc sector 22 h: 0) Azim
e networking. uth: –
When strong 10 to
interference 10)
sources exist
in
neighboring
cells, the
horizontal
coverage of a
cell can be
reduced to
mitigate the
interference
from
neighboring
cells. This
scenario
applies to
low-rise
buildings
since the
vertical
coverage
scope is
small.
SCE Bu Low-rise 45° 6° –2 – Yes No No No Yes
NA ild building and to 32 (Tilt:
RIO in hotspot 9 to -,
_4 g coverage 32 Azim
uth: –
22 to
22)
SCE Bu Low-rise 25° 6° –2 – Yes No No No Yes
NA ild building and to 42 (Tilt:
RIO in hotspot 9 to -,
_5 g coverage 42 Azim
uth: –
32 to
32)
SCE Mi This scenario 110° 12° 0 0 Yes Yes No Yes No
NA dd uses non- to
RIO le- standard 3- 6
_6 flo sector
or networking
co and provides
ve relatively
ra large
ge horizontal
an coverage for
d scenarios
sq involving
ua middle-rise
re buildings.
SCE Mi This scenario 90° 12° 0 – Yes Yes No No No
NA dd uses non- to 10
RIO le- standard 3- 6 to
_7 flo sector 10
or networking.
co When strong
ve interference
ra sources exist
ge in
wi neighboring
th cells, the
int horizontal
erf coverage of a
ere cell can be
nc reduced to
e mitigate the
interference
from
neighboring
cells. This
scenario
applies to
middle-rise
buildings
since the
vertical
coverage
scope is
large.
SCE Mi This scenario 65° 12° 0 – Yes Yes No Yes No
NA dd uses non- to 22
RIO le- standard 3- 6 to
_8 flo sector 22
or networking.
co When strong
ve interference
ra sources exist
ge in
wi neighboring
th cells, the
int horizontal
erf coverage of a
ere cell can be
nc reduced to
e mitigate the
interference
from
neighboring
cells. This
scenario
applies to
middle-rise
buildings
since the
vertical
coverage
scope is
large.
SCE Mi This scenario 45° 12° 0 – Yes No No No No
NA dd applies to to 32
RIO le- middle-rise 6 to
_9 ris buildings 32
e and hotspot
bu coverage.
ild
in
g
SCE Mi This scenario 25° 12° 0 – Yes No No No No
NA dd applies to to 42
RIO le- middle-rise 6 to
_10 ris buildings 42
e and hotspot
bu coverage.
ild
in
g
SCE Mi This scenario 15° 12° 0 – Yes No No No No
NA dd applies to to 47
RIO le- middle-rise 6 to
_11 ris buildings 47
e and hotspot
bu coverage.
ild
in
g
SCE Sq This scenario 110° 25° - 0 Yes Yes No No No
NA ua uses non-
RIO re standard 3-
_12 +h sector
ig networking
h- and provides
ris relatively
e large
bu horizontal
ild coverage for
in scenarios
g involving
high-rise
buildings.
SCE Hi This scenario 65° 25° - – Yes Yes Yes Yes No
NA gh uses non- 22 (Azi
RIO - standard 3- to mut
_13 flo sector 22 h: 0)
or networking.
co When strong
ve interference
ra sources exist
ge in
wi neighboring
th cells, the
int horizontal
erf coverage of a
ere cell can be
nc reduced to
e mitigate the
interference
from
neighboring
cells. This
scenario
applies to
high-rise
buildings
since the
vertical
coverage
scope is the
largest
(among these
scenarios).
SCE Hi This scenario 45° 25° - – Yes Yes No No No
NA gh applies to 32
RIO - high-rise to
_14 ris buildings 32
e and hotspot
bu coverage.
ild
in
g
SCE Hi This scenario 25° 25° - – Yes Yes No Yes No
NA gh applies to 42
RIO - high-rise to
_15 ris buildings 42
e and hotspot
bu coverage.
ild
in
g
SCE Hi This scenario 15° 25° - – Yes No No No No
NA gh applies to 47
RIO - high-rise to
_16 ris buildings 47
e and hotspot
bu coverage.
ild
in
g
1. "Yes" indicates that the product supports this scenario, and "No" indicates that the product does not
support this scenario.
2: "-" indicates that the tilt cannot be adjusted. The default tilt differs depending on the AAU model. The
64T/32T AAUs use preset tilt (6°) and 16T/8T AAUs use preset tilt (0°).
The default value of the tilt equals the value of the preset downtilt for an AAU. The value
ranges in the Tilt columns in preceding tables indicate actual tilt adjusting ranges.
For scenarios 1 to 6, the default value range of the Tilt parameter is –2° to 9°.
For scenarios 7 to 11, the default value range of the Tilt parameter is 0° to 6°.
For scenarios 12 to 16, only the default preset downtilt can be configured. Other tilt values are
not available.
In general, DEFAULT is recommended to obtain relatively high gains at the cell edge
and ensure the access of cell center UEs (CCUs).
When requirements for vertical coverage are high, for example, in high-rise buildings,
SCENARIO_15 or SCENARIO_16 is recommended. The vertical coverage is large,
and vertical beam gains are high.
Note: When the azimuth is adjusted, the narrow beams on the vertical plane are
simultaneously adjusted. The following figure shows such a case when the azimuth is
adjusted from 0° to 5°.
Enhancement
In 5G RAN2.0, 10 configurable scenario-specific coverage beams are added.
Based on the existing scenario-specific beams, 5G RAN2.1 supports beam densification to the
maximum number of SSB beams. This provides 0 to 2 dB coverage gains in certain scenarios.
Dependency
Hardware
Base stations working in sub-6 GHz frequency bands support 8T8R or higher
specifications.
UE
None
Core network
None
Other NEs
None
Other features
None
Summary
This feature improves the coverage performance of the PDSCH, PUSCH/PUCCH, and SSB
through downlink PMI weight optimization, MIMO-based uplink advanced receiver, and SSB
power aggregation.
Benefits
This feature improves the uplink and downlink cell coverage performance.
Description
This feature provides the following functions to improve the coverage of each channel:
Downlink precise PMI weight, which improves the PDSCH coverage performance using
the sub-band precise weight
SSB power aggregation, which aggregates the power of some PDSCHs to the SSB to
improve the SSB coverage performance
MIMO-based uplink advanced receiver, which improves the PUSCH/PUCCH coverage
performance by adding receive beams through uplink time-domain or spatial-domain
filtering.
Enhancement
None
Dependency
Hardware
Base stations working in sub-6 GHz frequency bands support 8T8R or higher
specifications.
UE
Core network
None
Other NEs
None
Other features
None
Summary
This feature uses multi-antenna technologies to support spatial multiplexing of OFDM time-
frequency resources in uplink and downlink data transmission for a single UE. This enables
multi-layer data transmission for that UE, which boosts the single-UE peak rate. The
throughput of a 4R UE is theoretically four times that of a 1R UE.
This feature includes downlink SU multiple layers and uplink SU multiple layers.
Benefits
This feature improves the uplink and downlink experienced peak rates of a single UE.
Description
This feature uses multi-antenna technologies to support multi-layer data transmission in the
downlink for a single UE, which boosts the single-UE peak rate. The maximum number of
downlink layers for a single UE depends on either the number of base station transmit
antennas or the number of UE receive antennas, whichever is smaller. For example, when a
base station supports 64 TRXs, a 2T4R UE supports data transmission in a maximum of four
layers in the downlink.
Benefits
This feature improves the single-UE downlink experienced peak rate.
Description
This feature enables uplink multi-layer data transmission for a single UE by using multi-
antenna technologies. The maximum number of uplink layers for a single UE equals the
smaller limit provided by base station receive antennas and UE transmit antennas. For
example, when a base station supports 64 TRXs, a 2T4R UE supports data transmission over
a maximum of two uplink layers.
Benefits
This feature improves the single-UE experienced uplink peak rate.
Enhancement
None
Dependency
Hardware
None
UE
UEs must have two or more transmit antennas to support uplink multiple layers.
UEs must have two or more receive antennas to support downlink multiple layers.
Core network
None
Other NEs
None
Other features
None
Description
Power is evenly distributed among layers if inter-layer power is not processed. In addition, the
inter-layer SINRs are different in a codeword, and multiple layers in the codeword use the
same MCS index for transmission. When the SINR difference between layers is large, a high
MCS index is used for low-SINR layers. When such layers experience a transmission fault,
the entire codeword is retransmitted, reducing the transmission efficiency. Downlink inter-
layer power control optimization aims to allocate power among layers with the maximum
SINR in a codeword. This helps improve the spectral efficiency of multi-layer transmission
for UEs that are located at a medium or short distance from the cell center.
Benefits
This feature improves experience of a single UE located at a medium or short distance from
the cell center in the downlink.
Enhancement
None
Dependency
Hardware
None
UE
UEs must have two or more receive antennas to support downlink multiple layers.
Core network
None
Other NEs
None
Other features
None
Model
Summary
C-band is capable of satisfying the requirement of large bandwidth and is referred to as a gold
band for 5G Enhanced Mobile Broadband (eMBB) services. A vast majority of global
operators have selected C-band as the preferential 5G frequency band. DL coverage is favored
over UL coverage on C-band for the characteristics of large DL transmit power and
disproportion in UL and DL subframe assignment of NR. The application of technologies
such as beamforming and cell-specific reference signal (CRS)-Free further increases the
difference between C-band UL and DL coverage.
This feature defines new paired spectrum, with C-band for DL transmission and a sub-3 GHz
band (for example, 1.8 GHz) for UL transmission, thereby improving UL coverage. This
addresses the issues related to C-band UL coverage, while helping to expand the overall total
coverage.
The UL sub-3 GHz band can be the one shared by LTE FDD and NR via MRFD-131223 LTE FDD and
NR Uplink Spectrum Sharing (LTE FDD) and MRFD-131263 LTE FDD and NR Uplink Spectrum
Sharing (NR).
3GPP Release 15 introduces the supplementary uplink (SUL). SUL effectively utilizes idle
sub-3 GHz band resources, improves the uplink coverage of C-band, and enables the
provisioning of 5G services in a wider area. SUL also improves the service experience of cell
edge users (CEUs). For details on the SUL, see section 6.9 in 3GPP TS 38.300 (V15.0.0). In
this feature, SUL carriers are on the sub-3 GHz band, and non-SUL carriers are on C-band.
Benefits
Fully unleashes the DL advantages of C-band, and expands the coverage and capacity,
while enabling the continuous cost-effective deployment of 5G networks on C-band.
Fully utilizes the idle UL spectrum resources of the LTE sub-3 GHz band, improves the
spectral efficiency of low bands, and saves spectrum investment.
Description
This feature supports the decoupling between the SUL frequency band in the uplink and non-
SUL frequency band in the downlink, as shown in Figure 1.1. It is applicable to scenarios
where uplink and downlink frequency bands are deployed at the same site and cover an
identical geographical area.
For UEs located in cell center areas, C-band can satisfy uplink coverage requirements,
and both uplink and downlink data transmission are carried on C-band.
For UEs located in cell edge areas, the uplink coverage of C-band is limited. UL and DL
Decoupling is implemented in this case so that PUSCHs, PUCCHs, and PRACHs are
configured on the low frequency band, and downlink coverage is still carried on C-band.
In the current version, C-band refers to N78 (3.5 GHz/3.7 GHz)/N79 (4.9 GHz), and the sub-3
GHz band refers to N80 (1.8 GHz)/N84 (2.1 GHz)/N86 (AWS). In addition, UL and DL
Decoupling supports non-standalone (NSA) and standalone (SA) networking. The number of
antennas, subcarrier spacing, and timeslot allocation supported by these frequency bands are
as follows:
N78
− Number of antennas: 8T8R, 32T32R, and 64T64R
− Subcarrier spacing: 30 kHz
− Timeslot allocation: 4:1, 8:2, and 7:3
N79
− Number of antennas: 64T64R
− Subcarrier spacing: 30 kHz
− Timeslot allocation: 4:1, 8:2, and 7:3
N80
− Number of antennas: 2R and 4R
− Subcarrier spacing: 15 kHz. All timeslots are available.
Enhancement
SRAN15.1
− Added the support for SA networking.
− Added the SUL CoMP function, which improves the uplink throughput of the SUL.
− Added RF modules that support this feature.
− Added the support for this feature by TDM commercial terminals in NSA
networking.
Feature Evolution
SRAN13.1
N(N)
Dependency
Base station controller
None
Base station
Baseband processing boards: UBBPfw1, UBBPg3, and CBPUb
Main control boards: UMPTe, UMPTg, and CMSTa
RF modules:
− 8T8R/32T32R/64T64R RF modules support N78 (3.5 GHz/3.7 GHz). 64T64R RF
modules support N79 (4.9 GHz).
− The following existing RRUs as well as new RRUs launched after SRAN15.1 GA
(excluding RFUs and AAUs) support the N80 (1.8 GHz), N84 (2.1 GHz), and N86
(AWS) frequency bands: RRU3249, RRU3262, RRU3268, RRU3268W, RRU3269,
RRU3626, RRU3630, RRU3630m, RRU3632, RRU3632m, RRU3638, RRU3639,
Summary
In the downlink, 256QAM is supported on the sub-6 GHz and mmWave bands.
In the uplink, 256QAM is supported on the sub-6 GHz band.
Benefits
Spectral efficiency is improved in cells.
If channel condition allows, peak throughput increases through combined use of high-order
modulation (UL 256QAM and DL 256QAM) and huge bandwidth solutions.
Description
This feature includes two functions: UL 256QAM and DL 256QAM. With this feature, when
channel condition allows, high-order modulation can be used to provide higher data rates.
Enhancement
None
Dependency
Hardware
None
UE
UEs must support DL 256QAM.
Core network
None
Other NEs
None
Other features
None
Summary
gNodeBs select suitable carriers for CA UEs based on the CA capabilities reported by UEs,
cell-level algorithm switch settings, and carrier management principles. This feature allows
aggregation of up to two uplink or downlink sub-6 GHz carriers to achieve a maximum
bandwidth of 200 MHz. It allows aggregation of up to four uplink or downlink mmWave
carriers to achieve a maximum bandwidth of 800 MHz.
Benefits
Maximized resource utilization: A CA UE can use idle RBs on multiple carriers to
maximize utilization of resources.
Efficient utilization of non-contiguous spectrum chunks: With CA, an operator's non-
contiguous spectrum chunks can be aggregated for efficient utilization, especially in
spectrum refarming scenarios.
Better user experience: On a live network that serves a number of UEs, CA UEs with
activated secondary serving cells (SCells) can use idle resources in their SCells and
achieve increased throughput if the network is not overloaded.
Description
CA enables aggregation of multiple contiguous or non-contiguous carriers to provide a wider
bandwidth as required by 3GPP Release 15 and to better utilize spectrum chunks.
During CA, upper-layer data streams are mapped to individual component carriers (CCs) at
the MAC layer. Each CC uses its own hybrid automatic repeat request (HARQ) entities and
link adaptation mechanism.
During initial access, an incoming handover, or an RRC connection reestablishment of a CA
UE, a gNodeB configures SCells for the UE in a blind manner or based on a specified
frequency set. In frequency set-based CA configuration, the UE measures the configured
frequencies and reports the signal strength of cells on the frequencies. The gNodeB configures
the cells that meet specific conditions as SCells. The delivery of SCell information during CA
UE handovers is supported.
5G RAN2.1 supports the following CA band combinations:
Sub-6 GHz: 40+40 MHz, 40+60 MHz, 50+50 MHz, 60+20 MHz, 60+30 MHz, and
100+100 MHz
mmWave: 100+100+100+100 MHz, and 200+200+200+200 MHz
Enhancement
RAN2.1
The low frequency bands support the band combinations of 50+50 MHz, 60+20 MHz,
and 60+30 MHz.
Data split is implemented between CCs based on the bandwidth ratio.
Dependency
Hardware
None
UE
UEs must support the band combinations and bandwidths for CA.
Core network
None
Other NEs
None
Other features
None
2.7 UCN
Feature Package Description
This feature package aims at building user-centric networks. It includes technologies such as
CoMP to further improve cell edge user (CEU) experience.
With the CoMP feature, the base station identifies CEUs in the overlapping areas between the
serving cells and their neighboring cells and performs joint reception in the uplink in the
serving and cooperating cells to improve the uplink throughput of these UEs.
Summary
With this feature, the base station identifies cell-edge UEs in the overlapping areas between
the serving cells and their neighboring cells and performs joint reception in the uplink in the
serving and cooperating cells to improve the uplink throughput of these UEs.
Benefits
This feature improves the throughput of cell-edge UEs, which helps achieve user-centered
service experience.
Description
The UL CoMP feature enables a base station to identify UEs for which joint reception
needs to be performed. For each identified UE, the base station configures a cooperating
cell, receives data from the UE on the PUSCH in the serving and cooperating cells at the
same time, and combines the received data in the serving cell.
Enhancement
None
Dependency
Hardware
The BBU5900 supports this feature. Cells must work on C-band in 64T64R, 32T32R, or
16T16R mode. A cooperating cell must be a cell that is set up in the same BBU as the
serving cell.
UE
None
Core network
None
Other NEs
None
Other features
None
2.8 Interoperability
Feature Package Description
The inter-RAT interoperability feature package provides mobility management solutions for
data services when multiple networks overlap. The solutions cover mobility from NG-RAN to
E-UTRAN.
Summary
During initial 5G network construction, NR does not provide continuous coverage. In NR
standalone (SA) scenarios, interoperability functions between LTE and NR ensure inter-RAT
service mobility of 5G UEs.
Benefits
Continuous LTE coverage can be used as a supplement to ensure service continuity when NR
is not able to provide continuous coverage. Inter-RAT mobility management between LTE and
NR facilitates commercial use of NR SA.
Description
In NR SA scenarios where NR is not able to provide continuous coverage, LTE can be used as
a coverage supplement. That is, when a UE moves to the NR coverage edge or the NR signal
quality deteriorates, the UE is migrated to the LTE network through redirection or handover.
This helps improve the coverage continuity for 5G services.
Enhancement
None
Dependency
UE
If handover from NR to LTE is enabled, the UE must support this type of handover.
Core network
If handover from NR to LTE is enabled, the core network must support the N26
interface.
3.1 Voice
3.1 Voice
Feature Package Description
When a UE is in the overlapping coverage area of the NG-RAN and E-UTRAN, and the NG-
RAN cannot provide voice services, this feature package enables the UE to fall back to the E-
UTRAN, thereby providing voice services for the UE.
Summary
During initial NR standalone (SA) deployment, NR does not provide continuous coverage or
voice over NR (VoNR). In this case, the LTE network with continuous coverage needs to be
used as the basic coverage layer and provide VoLTE to ensure the availability and continuity
of voice services.
Benefits
If an operator's NR SA network does not support VoNR, a UE must be handed over to the LTE
network to use VoLTE during voice service setup. After the UE terminates voice services on
the LTE network, the UE can be redirected to the NR network to establish data services,
thereby improving user experience.
Description
When a UE sends a voice bearer setup request on an NR network that does not support VoNR,
the NR base station sends a bearer rejection message to the NGC and hands over the UE to an
LTE cell. The UE then establishes a voice service on the LTE network.
Enhancement
None
Dependency
UE
The UE supports handover.
Core network
The core network supports the N26 interface.
Other NEs
The LTE network supports VoLTE services.
Other features
VoLTE is enabled.
Summary
This feature consists of the following functions: IP Active Performance Measurement,
Ethernet OAM, Active/Standby OAM Channel, BFD, and Ethernet Link Aggregation. These
functions are designed for transmission network detection and reliability improvement.
Benefits
The transmission network detection capability of the base station is increased and the
transmission reliability between the base station and transmission equipment is improved.
Enhancement
None
Dependency
Other NEs
Description
This function monitors changes in quality of service (QoS) parameters on the transport
network based on the Two-Way Active Measurement Protocol (TWAMP). These parameters
include round-trip time (RTT), one-way packet loss rate, and one-way delay variation.
The measurement model defined in the TWAMP involves the Controller and Responder
functions. The Controller consists of Session-Sender and Control-Client, and the Responder
consists of Session-Reflector and Server. The Control-Client and Server exchange control
packets over TCP links for measurement task management purposes, including measurement
task negotiation (also called initialization), start, and stop. Port 862 is used to transmit control
packets in the TWAMP-based measurement.
The Session-Sender and Session-Reflector exchange test packets. The Session-Sender sends
test packets, and the Session-Reflector responds to the sent test packets. The test packets
comply with the User Datagram Protocol (UDP).
Based on the negotiation result, the Controller sends packets over a negotiated fixed data
flow. The data flow consists of the sender IP address, responder IP address, UDP port number,
and Type-P. Type-P can be the protocol type, port number, packet length, or differentiated
services code point (DSCP). A test packet carries the sending sequence number and sending
timestamp. Based on the test packet, the Sender calculates the one-way delay, one-way delay
variation, one-way packet loss rate, and RTT on a specified link.
The Responder responds to received packet. The Responder records the time when it receives
the packet, obtains the sending sequence number and timestamp from the received packet, and
generates a response packet. The response packet contains the sequence number and
timestamp information sent from the Session-Reflector.
This function supports both the Controller and Responder functions.
It works in non-authentication mode.
This function performs packet loss measurement. Based on the number of packets sent from
and received by the Sender and the number of packets sent by the Reflector, this function
calculates the packet loss rate by dividing the number of lost packets by the total number of
transmitted packets.
In addition, this function calculates the RTT based on the time when the Sender and Reflector
send and receive packets using the following formula: RTT = (T2 – T1) + (T4 – T3) = (T4 –
T1) – (T3 – T2)
This function calculates the packet delay variation based on the comparison between the
delays of two adjacent packets.
Benefits
Tests the QoS of transmission networks. Quickly locates and isolates transmission faults,
reducing the maintenance cost.
Provides long-time performance measurement, monitors the quality of transmission bearer
networks, and reduces the maintenance cost for operators.
Injects UDP packets into transmission networks, which occupy network bandwidth. For
example, if 80-byte packets are continuously sent at a rate of 10 packets per second in a
monitoring flow, a bandwidth of 6.4 kbit/s is occupied.
Description
Ethernet OAM is a mechanism at the Media Access Control (MAC) layer and implements
operation, administration, and maintenance (OAM) for the Ethernet. Ethernet OAM is
implemented using the following three protocols:
IEEE 802.3ah, which supports point-to-point OAM between two directly connected
devices
IEEE 802.1ag, which supports end-to-end OAM
ITU Y.1731, which is an enhanced protocol of IEEE 802.1ag
Ethernet OAM (IEEE 802.3ah) supports the following basic functions:
Automatic discovery: This is an OAM session establishment procedure. In this
procedure, a device periodically sends OAM packet data units (PDUs) to check whether
the peer end supports Ethernet OAM (IEEE 802.3ah).
Fault detection: A device sends OAM PDUs to inform the peer device of the fault
information when detecting a link fault, dying gasp, or key event.
Link monitoring: A device monitors the bit error rate (BER) on a link. If the BER
exceeds the specified threshold, the device sends OAM PDUs to report this event to the
peer device.
Remote loopback: A device sends a loopback control PDU to the peer end to request
loopback. Loopback facilitates fault location and link quality tests.
Ethernet OAM (IEEE 802.1ag) performs the connectivity fault management (CFM) function
specified in the IEEE 802.1ag protocol, which is an end-to-end Ethernet OAM protocol. The
CFM function is a network-level Ethernet OAM technology and consists of continuity check,
loopback, and linktrace functions. With the CFM function, the connectivity faults on the
entire network can be detected and located.
Ethernet OAM (ITU Y.1731) defines the fault management and performance monitoring
functions. The fault management functions defined in Ethernet OAM (ITU Y.1731) are
closely coupled with those in Ethernet OAM (IEEE 802.1ag). The performance monitoring
functions defined in Ethernet OAM (ITU Y.1731) include measurement of frame loss rate,
delay, and delay variation.
With Ethernet OAM (ITU Y.1731), point-to-point sessions are established to monitor Ethernet
performance based on the following detection functions:
Ethernet loss measurement (ETH-LM) collects the statistical numbers of received and
sent measurement packets. Measurement packets are sent and received in order between
the two nodes of the measurement.
Ethernet delay measurement (ETH-DM) performs on-demand measurement of frame
transfer delay and delay variation. The two-way ETH-DM is recommended because the
one-way measurement requires clock synchronization between two nodes.
Benefits
Implements Ethernet OAM between two directly connected devices.
Allows operators to monitor the transmission quality and the layer 2 network
performance.
Helps operators quickly check the connectivity and locate faults on the layer 2 network.
Provides network performance information to serve as reference for upgrades.
Description
Two OM channels are available: active and standby OM channels. Each OM channel has one
OM IP address. In most cases, only the active channel works. When the active channel
becomes faulty, the standby channel is activated and takes over.
Benefits
Improves the OM channel reliability.
4.1.1.4 BFD
Description
This function detects connectivity between two nodes by periodically transmitting
Bidirectional Forwarding Detection (BFD) packets between them. If no BFD packet is
received within a detection period, the connection is considered faulty and related recovery
actions will be automatically triggered, such as IP route switching, to avoid link
disconnection. BFD is featured by its high speed and can be used for IP-based
telecommunications services.
A gNodeB supports single-hop BFD (SBFD) and multi-hop BFD (MBFD) functions.
SBFD applies to gateway availability detection when routers are used.
MBFD applies to connectivity detection between NEs, for example, between gNodeBs,
between a gNodeB and the core network, or between the core network and a transmission
device. Figure 1.1 shows the application scenarios of SBFD and MBFD.
Benefits
Detects network faults.
Ensures the high reliability and availability of Ethernet services to provide economic,
reliable, and advanced Ethernet services for operators.
Description
Ethernet link aggregation, defined in IEEE 802.3ad, binds multiple Ethernet links into one
logical link, to achieve large bandwidth and improve Ethernet reliability. Link Aggregation
Control Protocol (LACP), also defined in IEEE 802.3ad, is used to detect the link aggregation
group status.
A gNodeB supports static LACP. With static LACP, the link aggregation group parameters are
automatically configured. and faults are detected.
Benefits
Improves the reliability of Ethernet links between gNodeBs and transmission devices.
Increases the link bandwidth usage through load balancing.
Summary
Network synchronization consists of different synchronization methods, for example,
enhanced synchronization and 1588v2 ATR.
Benefits
Diversified time synchronization methods are provided to implement network
synchronization.
Description
Enhanced synchronization is based on IEEE1588 V2. IEEE1588 V2 is a standard defining the
Precision Time Protocol (PTP) which applies only to the standard Ethernet. IEEE1588 V2
clock synchronization enables accurate synchronization of distributed and independent clocks
in measurement and control systems. IEEE 1588 messages are transferred between primary
and secondary clock equipment. To achieve frequency or time synchronization between the
equipment, accurate time stamps are used to calculate the offset of time and frequency.
Microsecond precision can be achieved. IEEE1588 V2 supports both frequency
synchronization and time synchronization.
IEEE1588 V2 clock synchronization is an alternative clock solution for GPS clock
synchronization. IEEE1588 V2 synchronization is one of the clock solutions for IP networks
and applies to the transport network of Ethernet.
The NE with the master clock sends synchronization packets to the NE with the slave clock.
The intermediate device connecting to the NE with the master clock works as a slave clock
and obtains clock information from the master clock. The intermediate device then functions
as a master clock and connects to other devices functioning as slave clocks.
gNodeBs support IEEE1588 V2 in layer 3 unicast and layer 2 multicast modes:
In layer 3 unicast mode, IEEE1588 V2 packets are contained in IPv4 User Datagram
Protocol (UDP) packets.
In layer 2 multicast mode, IEEE1588 V2 packets are contained in media access control
(MAC) packets.
The IPCLKLNK.CNM parameter determines whether the layer 3 unicast mode or layer
2 multicast mode is used.
Benefits
Enhanced synchronization reduces operators' network deployment costs and facilitates
network management and maintenance, compared with GPS clock synchronization.
Description
1588v2 Adaptive Time Recovery (ATR) is a low-cost solution based on IEEE1588 V2 clock
synchronization. With 1588v2 ATR, synchronization packets are transparently transmitted
from the clock server to gNodeBs. Intermediate transmission equipment is not required to
support the IEEE1588 V2 standard, and gNodeB clock synchronization has less dependency
on the transport network.
This function takes effect only when IEEE1588 V2 time synchronization is enabled.
Delay is inevitable during clock synchronization. This feature utilizes a clock delay
measurement mechanism, with which gNodeBs detect the delay in transmission and correct
the time carried in the clock packets.
The following figure shows the clock synchronization process in this feature.
Clock synchronization via 1588v2 ATR
Benefits
With 1588v2 ATR, synchronization packets are transparently transmitted from the clock
server to gNodeBs. Intermediate transmission equipment is not required to support the
IEEE1588 V2 standard, and gNodeB clock synchronization has less dependency on the
transport network.
Enhancement
None
Dependency
Hardware
None
UE
None
Core network
None
Other NEs
IEEE1588 V2 applies only to IP over FE/GE links.
Description
IEEE 1588v2 enables precise clock synchronization in measurement and control systems
implemented with technologies such as network communication, local computing, and
distributed objects. It is applicable to systems communicating via packet switching.
Clocks of NEs communicate with each other in a communication system. IEEE 1588v2
generates a master/slave relationship among these clocks, and all clocks derive their time
from the master clock.
This feature supports IEEE 1588v2 on an IPv6 network. The server of the master clock sends
the IEEE 1588v2 PTP messages encapsulated in IPv6 unicast packets. Then the gNodeB as
the clock client receives these messages and uses the adaptive clock algorithm to implement
frequency synchronization.
The synchronization mechanism of IEEE 1588v2 over IPv6 is the same as that of IEEE
1588v2 over IPv4. For details, see the description of FOFD-010070 Enhanced
Synchronization.
Benefits
When a gNodeB accesses an IPv6 network, IEEE 1588v2 clock synchronization can be used
as an alternative clock solution for the GPS clock synchronization in the IPv6 transport
network.
Enhancement
None
Dependency
Transport network
The peer equipment must support IPv6.
Others
The clock server must support IEEE 1588v2 over IPv6.
Other features
This feature requires FOFD-010070 Enhanced Synchronization.
Summary
This feature secures data transmission on IP networks. It involves the following functions:
IPsec, IPsec tunnel backup, IPsec redundancy among multiple SeGWs, IPsec redirection,
direct IPsec, and digital certificate whitelist management.
Benefits
IPsec provides transparent, end-to-end security services for IP networks to prevent potential
cyber-attacks.
4.1.3.1 IPsec
Description
IPsec is a protocol suite for securing IP communications. It provides high-quality,
interoperable, and cryptography-based security for IP packet transmission. Communication
parties can use the following security functions to ensure network transmission security:
Confidentiality: User data is encrypted and transmitted in cipher text.
Integrity: The received data is verified to check whether data has been tampered with.
Authentication: Data is verified to confirm the sender of the data.
Anti-replay: To prevent malicious attackers from repeatedly sending captured packets,
the receiver will reject duplicate packets.
IPsec implements the preceding objectives by using two security protocols: Authentication
Header (AH) and Encapsulation Security Payload (ESP). To simplify the use and management
of IPsec, Internet Key Exchange (IKE) is defined and provides the following functions to
enhance network security:
Performs automatic key negotiation.
Sets up and maintains security associations.
IKE supports peer identity authentication by using pre-shared keys and digital certificates to
enhance the security of IPsec negotiations.
Benefits
IPsec protects data communication security between gNodeBs and between a gNodeB and the
core network.
Description
This function enables a pair of primary and secondary IPsec tunnels to be established between
a base station to two security gateways (SeGWs). This improves the reliability of base station
transmission links protected by IPsec. In normal conditions, both IPsec tunnels are available
for data transmission. In the uplink, the base station selects the primary IPsec tunnel based on
the priorities of IPsec tunnels. In the downlink, the base station can receive data on both the
primary and secondary IPsec tunnels. The SeGWs can send data to the base station on either
IPsec tunnel.
The base station uses BFD or DPD to detect the connectivity between the base station and the
SeGWs. If the primary IPsec tunnel is broken, the base station will switch the uplink data to
the secondary IPsec tunnel, and the SeGWs should be able to switch downlink data to the
secondary IPsec tunnel. If the primary IPsec tunnel recovers, the base station can switch the
uplink data back to the primary IPsec tunnel.
In the downlink, the routers on the network must support the dynamic routing protocol to
select routes.
IPsec Tunnel Backup and IPsec Redundancy Among Multiple SeGWs are mutually exclusive
and cannot be used at the same time.
Benefits
IPsec Tunnel Backup allows the use of a pair of primary and secondary IPsec tunnels between
the base station and two SeGWs. If one IPsec tunnel is faulty, data is transmitted over the
other IPsec tunnel, improving reliability.
Description
This feature works as follows:
1. When a base station uses the dead peer detection (DPD) function to detect that an IPsec
tunnel between the base station and the primary SeGW is faulty, the base station attempts to
initiate an IKE negotiation with each secondary SeGW in descending order by priority until a
temporary IPsec tunnel is successfully set up. Then, the base station switches its services to
the temporary IPsec tunnel.
In this situation, multiple base stations may simultaneously initiate negotiations with a
secondary SeGW, causing traffic storms on the secondary SeGW. To stagger the time base
stations initiate IKE negotiations with a secondary SeGW, the IPSec Redundancy
Switchover Wait Time and IPSec Redundancy Switchover Random Delay Time
parameters have been added. The IPSec Redundancy Switch Back Random Time
parameter has been added to stagger the time base stations switch back to the primary SeGW.
2. If the IPsec tunnel between the base station and the primary SeGW is restored, the base
station switches the services back to the active IPsec tunnel and removes the temporary IPsec
tunnel.
Benefits
This feature applies to intra- or inter-city secure networks.
Description
The IPsec redirection function improves IPsec tunnel reliability by enabling a base station to
be redirected from one SeGW to another if the load decision conditions are met or if
maintenance is required.
IPsec redirection enables a base station to implement IKE negotiation with different SeGWs
using the same IKE configuration and to establish an IPsec tunnel, thereby simplifying SeGW
network configuration and reducing network configuration complexity.
Benefits
This function facilitates SeGW capacity expansion, reduces network configuration
complexity, and improves the reliability of the SeGW networking.
Description
Direct IPsec enables a direct IPsec tunnel to be established between base stations over the X2
interface, which secures data transmitted over the X2 interface and reduces X2 interface
delay.
Benefits
This function provides low-delay and secures X2 transmission paths in inter-base station
coordination scenarios.
Description
If a PKI system is deployed, a base station applies for a certificate from the PKI system, and
the PKI system performs verification. Only verified base stations can access the network. If
no PKI system is deployed, both the base station and SeGW use the digital certificate
whitelist management function to ensure that the connected devices are in the whitelist.
The base station supports the following functions:
Digital certificate whitelist configuration: The base station supports digital certificate
whitelist updates in file mode using batch whitelist configuration and single whitelist
configuration.
Access control: During an IKE negotiation, the local end verifies whether the certificate
name contained in an IKE message received from the peer end is in the digital certificate
whitelist. If the certificate name is in the whitelist, IKE negotiation and IPsec tunnel
setup are allowed. The verification is controlled by a switch. If this switch is turned on
and a digital certificate whitelist is configured, the verification is performed. If this
switch is turned off or no digital certificate whitelist is configured, the verification is not
performed.
The verification is not performed for IKE negotiations during base station deployment by plug and play
(PnP).
Benefits
This function allows operators to use the digital certificate whitelist management function to
ensure base station access security without deploying a PKI system on the network.
Enhancement
None
Dependency
Hardware
None
UE
None
Core network
None
Other NEs
A security gateway must be deployed on the network and support IPsec.
PKI must be deployed if digital certificate authentication will be used.
Other features
None
Description
Based on the IPv6 protocol stack, this feature protects the confidentiality and integrity of data
between communication parties, and provides the authentication and anti-replay functions.
IPsec for IPv6 enhances the security of base station data that is transmitted on an untrusted
IPv6 transport network.
IPsec is a protocol suite that secures Internet Protocol (IP) communications by authenticating
and encrypting each IP packet in a data stream. IPsec also includes protocols for establishing
mutual authentication between endpoints at the beginning of the session and negotiation of
cryptographic keys to be used during the session.
The key characteristics of IPsec for IPv6 are the same as IPsec for IPv4:
One encapsulation mode: tunnel mode
Two security protocols: Authentication Header (AH) and Encapsulating Security Payload
(ESP)
Main encryption methods: NULL, Advanced Encryption Standard (AES), and
Galois/Counter Mode (GCM)
Main integrity protection methods: HMAC_SHA-1 and HMAC_SHA-256 HMAC is
short for Hash message authentication code, and SHA is short for secure hash algorithm.
IPsec for IPv6 is developed specifically for IPv6, and is mandatory in all standard-compliant
implementations of IPv6 (but its implementation is an optional extension to IPv4).
When the network equipment (such as the host or SeGW) supports IPv6, IPsec for IPv6
protects data flows between a pair of hosts (such as the client and server), between a pair of
SeGWs (such as routers or firewalls), or between an SeGW and a host. SeGW is short for
security gateway.
In a network, IPsec for IPv6 protects one or more data flows between two gNodeBs, between
the gNodeB and CN, or between the SeGW and gNodeB.
Benefits
Based on the IPv6 protocol stack, this feature protects the confidentiality and integrity of data
between communication parties, and provides the authentication and anti-replay functions.
IPsec for IPv6 enhances the security of gNodeB data that is transmitted on an untrusted IPv6
transport network.
Dependency
Transport network
The IPsec peer network equipment (such as the SeGW and core network) must support
the IPv6 protocol and IPsec for IPv6.
Core network
The IPsec peer network equipment (such as the SeGW and core network) must support
IPsec for IPv6.
Other features
None
Summary
This feature provides a basic IPv4-to-IPv6 transition technology, which enables two Internet
protocol (IPv4 and IPv6) to be implemented in one operating system.
This feature supports the IPv6 protocol stack and enables the IPv4 and IPv6 protocol stacks to
work at the same time.
Benefits
The key to a successful transition to IPv6 is the compatibility with IPv4 hosts and routers.
With the compatibility with IPv4 ensured, simultaneous IPv6 deployment simplifies the
Internet protocol transition to IPv6.
Description
The most direct way to maintain compatibility between IPv6 nodes and nodes that support
only IPv4 is to provide a complete IPv4 implementation solution. IPv6 nodes that provide
complete IPv4 and IPv6 functions are called IPv6/IPv4 dual-stack nodes.
IPv6/IPv4 dual-stack nodes are capable of sending and receiving both IPv4 and IPv6 packets.
These nodes can directly use IPv4 packets to interwork with IPv4 nodes and use IPv6 packets
to interwork with IPv6 nodes.
Huawei 5G RAN base stations can work in any of the following modes:
Enabled with only the IPv4 protocol stack
Enabled with only the IPv6 protocol stack
Enabled with both IPv4 and IPv6 protocol stacks. For example, in NSA scenarios, the
S1-U interface uses an IPv6 address and the X2 interface uses an IPv4 address.
Enhancement
None
Dependency
None
Summary
Multiple operators can share a radio access network (RAN). These operators use the carriers
of a single base station.
Benefits
RAN sharing helps operators reduce capital expenditure (CAPEX) and operating
expenditure (OPEX).
Description
The RAN Sharing solution allows operators to share RAN resources, including frequency and
baseband resources. In the multi-operator core network (MOCN) solution, operators share the
same cell of a base station. In the multi-operator radio access network (MORAN) solution,
operators own separate cells of a base station. Each base station with RAN sharing enabled is
connected to the core networks of all operators that share the RAN. The system information
broadcast in each shared cell includes the PLMN IDs of up to six operators and a single
tracking area code (TAC). This TAC can be used by all PLMNs that share the RAN resources.
All 5G UEs that support RAN sharing must be able to read six PLMN IDs and select one of
them for initial attach. After a UE selects a PLMN ID, it reports the ID to the base station. The
base station needs to select a proper core network based on this PLMN ID.
The RAN Sharing solution supports the sharing of the primary operations support system
(OSS). The primary OSS is connected to different network management systems through
different interfaces.
A shared base station can be connected to a non-shared base station. In an area covered by
shared base stations, a UE can be handed over from one shared base station to another. If the
UE moves to an area covered by a non-shared base station, the base station selects an
appropriate neighboring cell for handover based on certain principles. For example, a network
of the same operator is considered first for the handover.
The RAN Sharing solution has the following characteristics:
Multiple PLMN IDs are broadcast on common carriers, and the core networks are
independent of each other.
Operator-specific icons and names can be displayed.
The shared OSS is connected to different network management systems through Itf-N
interfaces.
A maximum of six operators are allowed to share a RAN.
Enhancement
None
Dependency
None
Summary
This feature introduces the symbol power saving function, which enables base stations to turn
off power amplifiers (PAs) when symbols are empty.
Benefits
When the traffic is light, base stations can shut down PAs when symbols are empty to reduce
the static power consumption of the PAs. The power consumption of base stations is reduced.
Description
PAs consume the majority of power of all base station components. PAs require static power
consumption even when no signals are transmitted. This feature quickly shuts down and turns
on PAs of some symbols to reduce static power consumption.
In order to guarantee the integrity of data, the base station needs to control the switching on
and off time of PAs to avoid any possible impact on the network.
Enhancement
None
Dependency
Hardware
Only low-frequency C-band modules support this feature.
UE
None
Core network
None
Other NEs
None
Other features
None
5.2 SON
Feature Package Description
The self-organizing network (SON) feature package provides measures related to automatic
network management. SON features automatically optimize the network and improve network
performance, improving operation and maintenance (OM) efficiency and reducing the
manpower required by operators.
Summary
The base station uses the ANR algorithm to automatically plan, configure, and correct
neighbor relationships. This greatly reduces manual operations and therefore reduces
operators' costs.
Benefits
This feature enables base stations to identify and optimize missing or incorrect neighbor
relationships, eliminating handover failures caused by missing or incorrect neighbor
relationship configuration.
Description
ANR can automatically add neighbor relationship entries to neighboring relation tables
(NRTs) and update the entries in NRTs. The ANR process is as follows:
Enhancement
None
Dependency
Hardware
None
UE
This feature requires support from UEs.
Core network
None
Other NEs
This feature requires support from the OSS.
Other features
None
Availability
This feature is available as of 5G RAN2.1.
Summary
ANR uses the base station algorithm to automatically plan, configure, and correct neighbor
relationships. This greatly reduces manual operations and therefore reduces operators' costs.
Benefits
This feature enables base stations to identify and optimize missing or incorrect neighbor
relationships, eliminating handover failures caused by missing or incorrect neighbor
relationship configuration.
Description
ANR can automatically add neighbor relationship entries to neighboring relation tables
(NRTs) and update the entries in NRTs. The following figure shows the inter-RAT ANR
process.
The gNodeB notifies the UE of the neighboring LTE cell frequencies to be measured.
The UE reports the PCI of cell B that meets measurement configuration requirements to
the gNodeB.
If the PCI in the measurement report does not exist in the NRT of the gNodeB, the
gNodeB instructs the UE to read the ECGI of cell B through the PCI. The gNodeB may
need to schedule appropriate idle periods to ensure that the UE can read the ECGI in the
broadcast channel.
The UE reads the ECGI of cell B and reports it to the gNodeB.
The gNodeB adds a neighbor relationship with cell B.
The gNodeB supports inter-RAT event-triggered ANR. After a coverage-based handover
measurement is triggered, if the handover measurement report sent by the UE to the gNodeB
contains an unknown PCI, the gNodeB instructs the UE to read and report the ECGI of the
unknown cell.
gNodeBs support ANR in RAN sharing scenarios. In non-RAN-sharing scenarios, ANR
maintains neighboring cell lists (NCLs) and NRTs. In RAN sharing scenarios, ANR also
maintains external-cell PLMN lists.
Enhancement
None
Dependency
Hardware
None
UE
The UE must support ANR.
Core network
None
Other NEs
None
Other features
None
ACK acknowledgment
AH Authentication Header
CA Carrier aggregation
CP Cyclic Prefix
EF Expedited Forwarding
HO Handover
IP PM IP Performance Monitoring
IPsec IP Security
OI Overload Indicator
OOK On-Off-Keying
PF Proportional Fair
PM Performance Measurement
RA Random Access
RB Resource Block
RF Radio Frequency
RS Reference Signal
RV Redundancy Version
Rx Receive
Tx Transmission
UE User Equipment
7 Appendix