VoNR

Contents
5.1 VoNR

5G RAN
VoNR Feature Parameter Description

Issue 02
Date 2020-05-21
 HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

 No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
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.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: https:/

Email: [email protected]

5.1 Contents
1 Change History
1.1 5G RAN3.1 02 (2020-05-21)
1.2 5G RAN3.1 01 (2020-04-07)
1.3 5G RAN3.1 Draft B (2020-03-09)
1.4 5G RAN3.1 Draft A (2020-01-20)

2 About This Document

2.1 General Statements
2.2 Features in This Document
2.3 Differences Between NR FDD and NR TDD
2.4 Differences Between NSA and SA
2.5 Differences Between High Frequency Bands and Low Frequency Bands

3 Overview

4 Basic VoNR Functions

4.1 Principles
 4.1.1 Operator-level VoNR
4.1.2 VoNR Emergency Call
4.1.3 VoNR Blacklist
4.1.4 EVS Codec
4.1.5 MAC CE-based Rate Adjustment
4.1.6 Uplink Coverage Optimization Based on an Increased Number of Retransmissions
4.1.7 Uplink RB Reservation
4.1.8 ROHC
4.2 Network Analysis
4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the MAE-Deployment
4.4.2 Activation Verification
4.4.3 Network Monitoring

5 Parameters

6 Counters

7 Glossary

8 Reference Documents

1 Change History

This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
• Technical changes
Changes in functions and their corresponding parameters
 • Editorial changes
Improvements or revisions to the documentation
1.1 5G RAN3.1 02 (2020-05-21)

This issue includes the following changes.

Technical Changes

None

Editorial Changes

• Revised the description of recommended bit rates for MAC CE-based rate adjustment.
For details, see 4.1.5 MAC CE-based Rate Adjustment.
• Revised descriptions in the document.
1.2 5G RAN3.1 01 (2020-04-07)

This issue includes the following changes.

Technical Changes

None

Editorial Changes

• Optimized figures in 3 Overview and 4.1 Principles.

• Revised descriptions of the voice bearer setup and release process. For details, see 4.1
Principles.

• Revised descriptions of operator-level VoNR. For details, see 4.1.1 Operator-level VoNR.
• Revised descriptions of VoNR emergency call. For details, see 4.1.2 VoNR Emergency
Call.

• Revised descriptions of VoNR blacklist. For details, see 4.1.3 VoNR Blacklist.
• Revised descriptions of EVS codec schemes. For details, see 4.1.4 EVS Codec.
• Revised descriptions of MAC CE-based rate adjustment. For details, see 4.1.5 MAC CE-
based Rate Adjustment.

• Revised descriptions of uplink coverage optimization based on an increased number of

retransmissions. For details, see 4.1.6 Uplink Coverage Optimization Based on an Increased
Number of Retransmissions.

• Added the cell requirements of uplink RB reservation. For details, see 4.3.3 Hardware.
• Revised descriptions of data preparation and activation command examples. For
details, see 4.4.1.1 Data Preparation and 4.4.1.2 Using MML Commands.
 • Added descriptions about VoNR codec schemes and coding rates applicable to voice
quality monitoring and the mapping between VQI values and voice quality levels. For
details, see 4.4.3 Network Monitoring.
1.3 5G RAN3.1 Draft B (2020-03-09)

This issue includes the following changes.

Technical Changes

None

Editorial Changes

• Revised the description of recommended scenarios for enabling uplink RB reservation.

For details, see 4.1.7 Uplink RB Reservation.
• Added the description of mutual impacts between uplink RB reservation and LTE
FDD and NR Flash Dynamic Spectrum Sharing. For details, see 4.2.2 Impacts.
• Revised the description of requirements on RF modules. For details, see 4.3.3 Hardware.
• Revised descriptions in the document.
1.4 5G RAN3.1 Draft A (2020-01-20)

This is the first release of this document.

2 About This Document

2.1 General Statements

Purpose

Feature Parameter Description documents are intended to acquaint readers with:

• The technical principles of features and their related parameters
• The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
• Requirements of the operating environment that must be met before feature activation
• Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
 This document only provides guidance for feature activation. Feature deployment and feature gains
depend on the specifics of the network scenario where the feature is deployed. To achieve the desired
gains, contact Huawei professional service engineers.

Software Interfaces

Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter
Description documents apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.

Trial Features

Trial features are features that are not yet ready for full commercial release for certain reasons.
For example, the industry chain (terminals/CN) may not be sufficiently compatible. However,
these features can still be used for testing purposes or commercial network trials. Anyone who
desires to use the trial features shall contact Huawei and enter into a memorandum of
understanding (MoU) with Huawei prior to an official application of such trial features. Trial
features are not for sale in the current version but customers may try them for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk due to
absence of commercial testing. Before using them, customers shall fully understand not only the
expected benefits of such trial features but also the possible impact they may exert on the
network. In addition, customers acknowledge and undertake that since trial features are free,
Huawei is not liable for any trial feature malfunctions or any losses incurred by using the trial
features. Huawei does not promise that problems with trial features will be resolved in the
current version. Huawei reserves the rights to convert trial features into commercial features in
later R/C versions. If trial features are converted into commercial features in a later version,
customers shall pay a licensing fee to obtain the relevant licenses prior to using the said
commercial features. If a customer fails to purchase such a license, the trial feature(s) will be
invalidated automatically when the product is upgraded.
2.2 Features in This Document

This document describes the following feature.

Feature ID Feature Name Chapter/Section

FOFD-031203 VoNR (Trial) 4 Basic VoNR Functions

2.3 Differences Between NR FDD and NR TDD

Function Name Difference Chapter/Section

Basic VoNR functions Uplink coverage optimization 4 Basic VoNR Functions

based on an increased
number of retransmissions is
supported only by NR TDD.
Other functions work the same
way in NR FDD and NR TDD.
2.4 Differences Between NSA and SA

Function Name Difference Chapter/Section

Basic VoNR functions This function is supported only 4 Basic VoNR Functions
in SA networking.

2.5 Differences Between High Frequency Bands and Low Frequency Bands

In this document, low frequency bands refer to those belonging to FR1 (410–7125 MHz), and
high frequency bands refer to those belonging to FR2 (24250–52600 MHz). For details about
FR1 and FR2, see section 5.1 "General" in 3GPP TS 38.104 V15.5.0.

Function Name Difference Chapter/Section

Basic VoNR functions This function is supported only 4 Basic VoNR Functions
in low frequency bands.

3 Overview

Provisioning of voice services is a fundamental requirement for wireless communications

networks. At the early stage of 5G network deployment, voice services are generally provided by
LTE networks due to low coverage rate of 5G base stations and low penetration rate of 5G
terminals.
• In non-standalone (NSA) networking, voice services are directly set up on an LTE
network using the voice over LTE (VoLTE) solution, as shown in Figure 3-1. For details
about VoLTE, see VoLTE in eRAN Feature Documentation.
• In standalone (SA) networking, voice services fall back from an NR network to an
LTE network using the evolved packet system (EPS) fallback solution, as shown in
Figure 3-2. For details about EPS fallback, see Interoperability Between E-UTRAN and NG-RAN.
 Figure 3-1 Voice solution in NSA networking

Figure 3-2 Voice solution in SA networking

Using the EPS fallback solution in SA networking, both voice and data services of NR UEs fall
back to the LTE network. This prolongs the voice call setup delay and decreases the data service
rate from that provided by an NR network to that provided by an LTE network. Therefore, with
 the large-scale 5G deployment, the voice over NR (VoNR) solution can be used, as shown in
Figure 3-3. NR UEs can directly perform voice services on an NR network without falling back to
the LTE network. This solution improves both voice service quality and data service rates.
Figure 3-3 VoNR solution

4 Basic VoNR Functions

4.1 Principles

Basic VoNR functions are controlled by the VONR_SW option of the

NRCellAlgoSwitch.VonrSwitch parameter. When this option is selected, IP-based dedicated voice
bearers are set up between UEs and the IP multimedia subsystem (IMS) on the NR network. In
this way, NR UEs can directly perform voice services on the NR network. Figure 4-1 shows the
process of setting up and releasing a voice bearer between two UEs.
Figure 4-1 Voice bearer setup and release process

The specific process is as follows:

1. When a calling UE initiates a call, an RRC connection is set up between the calling
UE and its serving gNodeB.
2. The 5G core network (5GC) sets up a quality of service (QoS) flow with a 5G QoS
Identifier (5QI) of 5 for the calling UE to carry Session Initiation Protocol (SIP)
signaling, and the gNodeB sets up the corresponding data radio bearer (DRB).
3. An RRC connection is set up between the called UE and its serving gNodeB.
4. The 5GC sets up a QoS flow with a 5QI of 5 for the called UE to carry SIP signaling,
and the gNodeB sets up the corresponding DRB.
5. The UE and the IMS perform SIP negotiation on the codec scheme, IP address, port
number, calling and called UEs' information, and other voice service information.
 6. After the SIP negotiation is successful, the 5GC sets up QoS flows with a 5QI of 1
for both the calling and called UEs to carry Real-Time Transport Protocol (RTP) and
Real-Time Transport Control Protocol (RTCP) data flows, and the gNodeBs set up
the corresponding DRBs.
7. After the call ends, the calling and called UEs release their QoS flows with a 5QI of
1, and the gNodeBs release the corresponding DRBs. The default bearers with a 5QI
of 5 are released only when the UEs enter the idle state.
If a UE enters a weak coverage area during the call, it is preferentially handed over to a
neighboring NR cell with good coverage. For details about this handover procedure, see
coverage-based intra-frequency and inter-frequency handovers described in Mobility Management. If
no neighboring NR cell meets the requirements, the UE will be handed over to a neighboring
LTE cell with good coverage. For details about this handover procedure, see coverage-based
inter-RAT mobility from NG-RAN to E-UTRAN described in Interoperability Between E-UTRAN and
NG-RAN.

Basic VoNR functions also support operator-level VoNR, emergency calls, blacklists, enhanced
voice services (EVS) codec, rate adjustment based on Media Access Control control element
(MAC CE), uplink coverage optimization based on an increased number of retransmissions,
uplink RB reservation, and robust header compression (ROHC). For details about related
parameters and principles, see 4.1.1 Operator-level VoNR, 4.1.2 VoNR Emergency Call, 4.1.3 VoNR Blacklist,
4.1.4 EVS Codec, 4.1.5 MAC CE-based Rate Adjustment, 4.1.6 Uplink Coverage Optimization Based on an
Increased Number of Retransmissions, 4.1.7 Uplink RB Reservation, and 4.1.8 ROHC.

4.1.1 Operator-level VoNR

In RAN sharing with common carrier, VoNR can be configured for each operator in a shared
cell. To enable operator-level VoNR, select the OPERATOR_VONR_SW option of the
NRCellOPPolicy.VoicePolicySwitch parameter.
• When the cell-level VoNR switch (specified by the VONR_SW option of the
NRCellAlgoSwitch.VonrSwitch parameter) is turned on, the gNodeB determines
whether VoNR takes effect for an operator according to the setting of the operator-
level VoNR switch (specified by the OPERATOR_VONR_SW option of the
NRCellOPPolicy.VoicePolicySwitch parameter).
• When the cell-level VoNR switch is turned off, VoNR does not take effect for cells
and operators regardless of whether the operator-level VoNR switch is turned on.
• If the NRCellOPPolicy MO is not configured for the cell, the gNodeB determines
whether VoNR takes effect for the cell according to the setting of the cell-level VoNR
switch.
For details about multi-operator sharing, see Multi-Operator Sharing.
4.1.2 VoNR Emergency Call

Emergency calls refer to voice services between UEs and an emergency call center (the IMS
module handling emergency calls) in scenarios of terrorism, medical urgency, fire, natural
disasters, and other emergencies. Subscribers can initiate emergency calls to seek assistance in
emergencies.
An emergency call is generally made by the following types of UEs:
• Normal UE: a UE who has a valid subscription and an authenticated subscriber
identity module (SIM) card and can access voice services normally.
• Limited UE: is classified into normal limited UE, limited UE with an unauthenticated
SIM card, and limited UE without a SIM card.
▪ Normal limited UE: a UE who has an authenticated SIM card but cannot
access services normally for reasons such as the UE is not in the coverage
area provided by its serving operator or the telephone bill is overdue. This
type of UE makes an emergency call by using its international mobile
subscriber identity (IMSI).
▪ Limited UE with an unauthenticated SIM card: a UE whose SIM card fails
authentication. This type of UE makes an emergency call using its
international mobile equipment identity (IMEI).
▪ Limited UE without a SIM card: a UE who does not have a SIM card. This
type of UE makes an emergency call by using its IMEI.
For a normal UE or a normal limited UE, VoNR emergency calls can be enabled by selecting the
VONR_SW option of the NRCellAlgoSwitch.VonrSwitch parameter and are processed in the
same way as normal calls. For a limited UE with an unauthenticated SIM card or a limited UE
without a SIM card, the gNBAirIntfSecParam.UnauthEmergencyCallSwitch parameter must also
be set to ENABLE to enable VoNR emergency calls which are processed as follows:
1. The gNodeB notifies a UE of whether IMS-based emergency calls are supported
through the IE ims-EmergencySupport contained in system information block type 1
(SIB1). If the value of this IE is true, the UE can initiate IMS-based emergency calls.
2. The UE sends an emergency call attach request to the 5GC.
3. After the emergency call attach procedure is successful, the UE sends an RRC
connection setup request for emergency calls (through the RRC Setup Request
message with the EstablishmentCause IE value set to emergency) to the gNodeB.
4. The gNodeB processes the RRC connection setup request sent by the emergency UE.
5. The UE initiates emergency call registration to the IMS and registers with the
emergency call center of the IMS.
6. The 5GC establishes a protocol data unit (PDU) session for emergency calls.
7. The UE makes an emergency call.
The process of emergency call services is the same as that of normal voice services.
4.1.3 VoNR Blacklist

A VoNR blacklist enables the gNodeB to filter out the cells with tracking area codes (TACs) that
do not support VoNR when selecting a target cell. This prevents UEs performing VoNR services
from being handed over to the cells that do not support VoNR.
 This function can be enabled by deselecting the VONR_SUPPORT_INDICATOR option of
the gNBServiceBlacklist.ImsServiceIndicator parameter after a TAC is added to a VoNR blacklist
by running the ADD GNBSERVICEBLACKLIST command.
If all cells with blacklisted TACs subsequently support VoNR, the blacklist can be removed by
running the RMV GNBSERVICEBLACKLIST command.
4.1.4 EVS Codec

Codec Scheme

VoNR uses the EVS codec. EVS codec can provide higher voice quality than alternative
commonly used voice codec schemes, such as adaptive multi-rate wideband (AMR-WB), with
equivalent coding rates. It can also provide equivalent voice quality using lower coding rates,
thereby increasing system capacity.
EVS codec schemes include EVS narrowband (EVS-NB), EVS wideband (EVS-WB), EVS
superwideband (EVS-SWB), EVS fullband (EVS-FB), and AMR-WB input/output (AMR-WB
I/O). Table 4-1 lists the voice coding rates supported by these schemes. The specific EVS coding
rate is negotiated between the UEs and the IMS through SIP signaling.
Table 4-1 Voice coding rates supported by different EVS codec schemes

Codec Scheme Supported Voice Coding Rates (kbit/s)

EVS-NB 5.9, 7.2, 8.0, 9.6, 13.2, 16.4, and 24.4

EVS-WB 5.9, 7.2, 8.0, 9.6, 13.2, 16.4, 24.4, 32, 48, 64, 96, and 128

EVS-SWB 9.6, 13.2, 16.4, 24.4, 32, 48, 64, 96, and 128

EVS-FB 16.4, 24.4, 32, 48, 64, 96, and 128

AMR-WB I/Oa 6.6, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05, and 23.85

a: If only a calling or called UE supports AMR rather than EVS, AMR-WB I/O is used by VoNR.

During a call, one or both of UEs that support AMR rather than EVS can use VoNR with degraded voice quality.

Traffic Model

Figure 4-2 illustrates the traffic model when the EVS codec is used.
Figure 4-2 Traffic model using EVS codec

Voice services have two states:

• Talk spurts: During talk spurts, UEs transmit voice frames in the uplink or receive
voice frames in the downlink. Voice frames are transmitted at 20 ms intervals, and
their sizes are determined by the voice coding rate.
• Silent periods: During silent periods, UEs transmit silence insertion descriptor (SID)
frames in the uplink or receive SID frames in the downlink. SID frames are
transmitted at 160 ms intervals. For the EVS codec, the SID frame sizes are always 64
bits.
4.1.5 MAC CE-based Rate Adjustment

This function enables the gNodeB to provide information about recommended bit rates for UEs
through a MAC CE based on the uplink air interface capability. In addition, it allows UEs to
query a recommended bit rate provided by the gNodeB when the air interface capability is
improved. This helps UEs adjust voice rates. This function is enabled when the ANBR_SW
option of the NRCellAlgoSwitch.VonrSwitch parameter is selected.
This function supports voice rate decrease or increase.
• When detecting that the air interface rate of a UE is lower than the threshold (64
kbit/s), the gNodeB sends a MAC CE to notify the UE of a recommended air interface
rate of 40 kbit/s. The UE then determines whether to decrease the voice coding rate
based on the recommended air interface rate. When detecting that the air interface rate
of a UE is higher than the threshold, the gNodeB sends a MAC CE to notify the UE of
a recommended air interface rate of 72 kbit/s. The UE then determines whether to
increase the voice coding rate based on the recommended air interface rate.
• When the uplink air interface capability of a UE is improved, the UE sends a MAC CE
to the gNodeB to query a recommended rate. In this case, after detecting that the air
interface rate of the UE is higher than the threshold (64 kbit/s), the gNodeB will send a
MAC CE to instruct the UE to adjust the recommended rate to 72 kbit/s. The UE then
determines whether to increase the voice coding rate based on the recommended air
interface rate.
The recommended bit rates for this function are defined in 3GPP specifications. For details, see
section 6.1.3.20 "Recommended bit rate MAC CE" in 3GPP TS 38.321 V15.5.0.
4.1.6 Uplink Coverage Optimization Based on an Increased Number of Retransmissions

When a 5QI-1 bearer works in unacknowledged mode (UM), the gNodeB performs a maximum
of four hybrid automatic repeat request (HARQ) retransmissions at the MAC layer for voice
service UEs. If a UE is located at the cell edge, four HARQ retransmissions may be not enough
to ensure accurate uplink data transmission. This function allows for a maximum of eight HARQ
retransmissions to increase the uplink data transmission success rate in weak coverage scenarios.

When a 5QI-1 bearer works in acknowledged mode (AM) and four consecutive HARQ retransmissions fail,
sufficient automatic repeat request (ARQ) retransmissions will be performed at the Radio Link Control (RLC) layer.
In this case, this function is not required.

This function is enabled when the UL_DELAY_COV_OPT_SW option of the

NRCellAlgoSwitch.VonrSwitch parameter is selected. Currently, it applies only to TDD cells.
4.1.7 Uplink RB Reservation

This function allows the reservation of a certain number of RBs at a specified position for voice
service UEs. Voice service UEs can preferentially use reserved RB resources. If the reserved RB
resources are all occupied, voice service UEs can use non-reserved RB resources that are
allocated according to the normal scheduling procedure. However, non-voice service UEs cannot
use the RB resources reserved by this function.
This function is enabled when the UL_RB_RSV_SW option of the
NRCellAlgoSwitch.VonrSwitch parameter is selected. The
NRDUCellPusch.UlVonrRsvdRbStartPos parameter specifies the start position of reserved RBs,
and the NRDUCellPusch.UlVonrRsvdRbNum parameter specifies the number of reserved RBs.
Some of the reserved RBs may be occupied by the physical random access channel (PRACH),
physical uplink control channel (PUCCH), or uplink data services (when the PRB usage of a UE
remains greater than 30%).
This function requires that the system bandwidth be greater than or equal to 20 MHz. It is
recommended that this function be enabled to optimally ensure the quality of voice services
when both of the following conditions are met:
• The PRB usage of the cell is greater than or equal to 60% or the proportion of voice
service UEs is greater than or equal to 10%.
• The average interference and noise detected on PRBs corresponding to the entire cell
bandwidth in the uplink (measured by counters N.UL.NI.Avg.PRB0 through
N.UL.NI.Avg.PRB272) must be higher than –110 dBm.

4.1.8 ROHC

VoNR can use ROHC to compress the headers of voice packets. ROHC helps reduce the header
overheads of voice packets on radio links, thereby lowering bit error rates (BERs), shortening
delay, and reducing consumption of radio resources. ROHC can be used for Internet Protocol
version 4 (IPv4) and Internet Protocol version 6 (IPv6) headers.
This function is enabled when the ROHC_SW option of the NRCellAlgoSwitch.RohcSwitch
parameter is selected. Data streams that comply with different network layer protocols use
different header compression schemes. Header compression schemes are defined by profiles
specified by different options of the NRCellAlgoSwitch.RohcProfiles parameter.
• If the PROFILE0X0001 option of this parameter is selected, profile 0x0001 is used to
support RTP, UDP, and IP.
• If the PROFILE0X0002 option of this parameter is selected, profile 0x0002 is used to
support UDP and IP.
With this function enabled, the gNodeB starts the ROHC procedure as shown in Figure 4-3 when a
UE initiates voice services. The gNodeB determines the common profiles supported by the UE
before negotiating the maximum number of ROHC contexts (including compression and
decompression characteristics) with the UE.
Figure 4-3 Procedure for starting ROHC

After ROHC is started, the compressor at the transmit (TX) end compresses the headers of voice
packets, and the decompressor at the receive (RX) end restores the headers. Figure 4-4 shows the
process of ROHC that uses profile 0x0001.
 Figure 4-4 ROHC process

The specific process is as follows:

1. The compressor sends header-compressed data packets.
2. The compressor and decompressor maintain the context at the TX and RX ends
respectively to ensure the context consistency through negotiation.
3. The decompressor restores the packet headers based on the context.
This function enables the decompressor to inform the compressor of successful or failed context
synchronization. If context synchronization fails, the compressor sends the packet carrying the
context repeatedly until context synchronization is successful. If the number of consecutive
cyclic redundancy check (CRC) error packets received by the decompressor is greater than the
threshold for exiting ROHC (fixed at 6), ROHC is disabled.
If a handover occurs after the preceding ROHC procedure upon initial access:
• For an intra-cell handover, ROHC parameters remain unchanged and do not need to be
renegotiated.
• For an intra-gNodeB inter-cell handover, ROHC parameters must be renegotiated. The
source cell informs the UE of the new ROHC parameters of the target cell through
RRC reconfiguration.
• For an inter-gNodeB inter-cell handover, ROHC parameters must be renegotiated as
follows:
1. The source gNodeB sends a Handover Request message carrying the UE's
ROHC capability information to the target gNodeB.
2. The target gNodeB sends a Handover Request Acknowledge message
carrying new ROHC parameters to the source gNodeB.
3. The source gNodeB informs the UE of the new ROHC parameters sent by
the target gNodeB through RRC reconfiguration.
4.2 Network Analysis

4.2.1 Benefits

Enabling VoNR functions provides the following benefits:

• The mean opinion score (MOS) of voice quality increases by approximately 0.1 to 0.3.
 • The uplink coverage improves by approximately 0.1 dB to 1.5 dB.
The preceding quality and coverage gains can be obtained by fixed-point quality tests near the
cell center and remote coverage tests, respectively, using a third-party MOS tester approved by
the operator.
4.2.2 Impacts

Network Impacts

After VoNR is enabled, VoNR services and data services share NR air interface resources. If the
VoNR traffic volume increases, there will be fewer resources available for data services and their
peak traffic volume will drop.
The following functions have additional impacts:
Enabling uplink coverage optimization based on an increased number of retransmissions to
increase the number of HARQ retransmissions may prolong the end-to-end delay of voice and
data packets and consume more air interface resources.
Enabling uplink RB reservation to reserve RBs for voice service UEs decreases both the number
of RBs available for uplink data services and the uplink peak traffic volume of data services in
the cell.

Function Impacts

RAT Function Function Switch Reference Description

Name

FDD DRX BASIC_DRX_SW option of the DRX When a group of discontinuou

Low- NRDUCellUePwrSaving.NrDuCellDrxAlgoSwitch parameters is associated with
frequency parameter bearers:
TDD • If the
NRDUCellQciBear
parameter is set to
255, DRX does not
VoNR services are
• If the
NRDUCellQciBear
is set to a value oth
transmission delay
prolongs. This affec
of downlink VoNR s
impact on DRX.

Low- Power BWP2_SWITCH option of the UE Power When synchronization signal

frequency saving NRDUCellUePwrSaving.BwpPwrSavingSw Saving (SSBs) are configured at two
TDD BWP parameter center frequency) of the band
recommended that uplink RB
power saving bandwidth part
enabled at the same time. If b
 RAT Function Function Switch Reference Description
Name

enabled and the reserved RB

power saving BWP (BWP2), t
resources cannot be used. W
resources are in BWP2, the n
RBs in BWP2 for UEs perform
services decreases.

FDD LTE FDD LTE_NR_FDD_SPCT_SHR_SW option of the LTE FDD It is not recommended that up
and NR NRDuCellAlgoSwitch.SpectrumCloudSwitch and NR be enabled together with LTE
Spectrum
Flash parameter Sharing Dynamic Spectrum Sharing. T
Dynamic reserved RBs are configured
Spectrum spectrum and some of the sha
Sharing occupied by LTE, interference
voice service UEs that occupy
neighboring NR cells.

4.3 Requirements

4.3.1 Licenses

There are currently no license requirements for trial functions.

4.3.2 Software

Prerequisite Functions

None

Mutually Exclusive Functions

None
4.3.3 Hardware

Base Station Models

3900 and 5900 series base stations. 3900 series base stations must be configured with the
BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be configured with the
BBU3910.

Boards

All NR-capable main control boards and baseband processing units support this function. To
learn which main control boards and baseband processing units are NR-capable, see the related
BBU technical specifications in 3900 & 5900 Series Base Station Product Documentation.
RF Modules

This function does not depend on RF modules.

Cells

Uplink RB reservation requires that the cell bandwidth be 20 MHz or higher. Other functions
have no requirements for the cell bandwidth.
4.3.4 Networking

The following networking requirements must be met:

• The SA networking must be supported.
• The transmission delay between the gNodeB and the 5GC must be less than 20 ms.
4.3.5 Others

This function also has the following requirements:

• UE requirements
▪ UEs must support VoNR. If the value of the voiceOverNR IE in the ims-
ParametersFRX-Diff message indicating the UE capability information is
supported, the UE supports VoNR. For details about whether a UE
supports VoNR, see section 4.2.13 "IMS Parameters" in 3GPP TS 38.306
V15.5.0.
▪ If ROHC is required, UEs must also support ROHC. If the value of the
profile0x0001 or profile0x0002 IE in the supportedROHC-Profiles message
indicating the UE capability information is TRUE, the UE supports ROHC.
For details about whether a UE supports ROHC, see section 4.2.4 "PDCP
Parameters" in 3GPP TS 38.306 V15.5.0.
▪ If MAC CE-based rate adjustment is required, UEs must also support access
network bitrate recommendation (ANBR) and access network bitrate
recommendation query (ANBRQ). If the value of the recommendedBitRate
or recommendedBitRateQuery IE in the mac-ParametersCommon message
indicating the UE capability information is supported, the UE supports
ANBR or ANBRQ, respectively. For details about whether a UE supports
ANBR and ANBRQ, see section 4.2.6 "MAC Parameters" in 3GPP TS
38.306 V15.5.0.
• Operators must have deployed the IMS, and the 5GC must support IMS-based voice
services.
4.4 Operation and Maintenance

4.4.1 Data Configuration

4.4.1.1 Data Preparation

 describes the parameters used for function activation. This section does not describe
Table 4-2
parameters related to cell establishment.
Table 4-2 Parameters used for activation
Parameter Name Parameter ID Option Setting No

VoNR Switch NRCellAlgoSwitch.VonrSwitch VONR_SW Select thi

option.

Voice Policy NRCellOPPolicy.VoicePolicySwitch OPERATOR_VONR_SW Select thi

Switch option if
operator-
VoNR is
required i
sharing w
common
according
network p

Unauthenticated gNBAirIntfSecParam.UnauthEmergencyCallSwitch None Set this

Emergency Call paramete
Switch ENABLE
emergenc
calls are
required f
limited UE
an
unauthen
SIM card
limited UE
without S
card acco
to the net
plan.

IMS Service gNBServiceBlacklist.ImsServiceIndicator VONR_SUPPORT_INDICATOR Deselect

Indicator option if a
VoNR bla
is require
according
network p

VoNR Switch NRCellAlgoSwitch.VonrSwitch ANBR_SW Select thi

option if M
CE-based
adjustme
required
according
network p
Parameter Name Parameter ID Option Setting No

VoNR Switch NRCellAlgoSwitch.VonrSwitch UL_DELAY_COV_OPT_SW Select thi

option if u
coverage
optimizat
based on
increased
number o
retransmi
is require
according
network p

Uplink PDCP gNBPdcpParamGroup.UlPdcpDiscardTimer None Set this

Discard Timer paramete
MS300(3

RLC gNBRlcParamGroup.gNBRlcReassemblyTimer None Set this

Reassembly paramete
Timer for MS100(1
gNodeB

gNodeB PDCP gNBPdcpParamGroup.gNBPdcpReorderingTimer None Set this

Reordering paramete
Timer MS100(1

VoNR Switch NRCellAlgoSwitch.VonrSwitch UL_RB_RSV_SW Select thi

option if u
RB reserv
is require
according
network p

UL VoNR NRDUCellPusch.UlVonrRsvdRbNum None Set this

Reserved RB paramete
Numbera based on
network p

UL VoNR NRDUCellPusch.UlVonrRsvdRbStartPos None Set this

Reserved RB paramete
Start Positiona based on
network p

ROHC Switch NRCellAlgoSwitch.RohcSwitch ROHC_SW Select thi

option if R
is require
according
network p
 Parameter Name Parameter ID Option Setting No

ROHC Profiles NRCellAlgoSwitch.RohcProfiles • PROFILE0X0001 Select bo

• PROFILE0X0002 options if
ROHC fo
services i
required
according
network p

a: The same RBs must be reserved in the serving cell and its neighboring cells. In addition, it is recommended
RBs at higher frequencies be reserved to minimize the impact of VoNR services on data services.

4.4.1.2 Using MML Commands

Activation Command Examples

//Turning on the cell-level VoNR switch

MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=VONR_SW-1;
//(Optional) Enabling operator-level VoNR according to the network plan
ADD NRCELLOPPOLICY: NrCellId=7, OperatorId=0,
VoicePolicySwitch=OPERATOR_VONR_SW-1;
//(Optional) Enabling unauthenticated VoNR emergency calls according to the
network plan
MOD GNBAIRINTFSECPARAM: UnauthEmergencyCallSwitch=ENABLE;
//(Optional) Adding a VoNR blacklist according to the network plan
ADD GNBSERVICEBLACKLIST: Mcc="302", Mnc="220", Tac=1,
ImsServiceIndicator=VONR_SUPPORT_INDICATOR-0;
//(Optional) Enabling MAC CE-based rate adjustment according to the network
plan
MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=ANBR_SW-1;
//(Optional) Enabling uplink coverage optimization based on an increased
number of retransmissions according to the network plan
MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=UL_DELAY_COV_OPT_SW-1;
//(Optional) Configuring the gNodeB's uplink PDCP discard timer and PDCP
reordering timer when uplink coverage optimization based on an increased
number of retransmissions is enabled
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=0, UlPdcpDiscardTimer=MS300,
gNBPdcpReorderingTimer=MS100;
//(Optional) Configuring the gNodeB's RLC reassembly timer when uplink
coverage optimization based on an increased number of retransmissions is
enabled
MOD GNBRLCPARAMGROUP: RlcParamGroupId=0, gNBRlcReassemblyTimer=MS100;
//(Optional) Associating the gNodeB's PDCP parameter group with the 5QI-1
bearer when uplink coverage optimization based on an increased number of
retransmissions is enabled
MOD NRCELLQCIBEARER: NrCellId=7, Qci=1, UmPdcpParamGroupId=0, RlcMode=UM;
//(Optional) Associating the gNodeB's RLC parameter group with the 5QI-1
bearer when uplink coverage optimization based on an increased number of
retransmissions is enabled
MOD NRDUCELLQCIBEARER: NrDuCellId=7, Qci=1, UmRlcParamGroupId=0;
//(Optional) Enabling uplink RB reservation according to the network plan
 MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=UL_RB_RSV_SW-1;
//(Optional) Configuring the number of reserved uplink RBs and the start
position of reserved uplink RBs when uplink RB reservation is enabled
MOD NRDUCELLPUSCH: NrDuCellId=7, UlVonrRsvdRbNum=N10,
UlVonrRsvdRbStartPos=10;
//(Optional) Enabling ROHC and ROHC profiles according to the network plan
MOD NRCELLALGOSWITCH: NrCellId=7, RohcSwitch=ROHC_SW-1,
RohcProfiles=PROFILE0X0001-1&PROFILE0X0002-1;

Deactivation Command Examples

//Turning off the VoNR switch (After this switch is turned off, all VoNR
functions become invalid.)
MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=VONR_SW-0;
//Turning off the operator-level VoNR switch
ADD NRCELLOPPOLICY: NrCellId=7, OperatorId=0,
VoicePolicySwitch=OPERATOR_VONR_SW-0;
//Setting the UnauthEmergencyCallSwitch parameter to DISABLE
MOD GNBAIRINTFSECPARAM: UnauthEmergencyCallSwitch=DISABLE;
//Removing the VoNR blacklist
RMV GNBSERVICEBLACKLIST: Mcc="302", Mnc="220", Tac=1;
//Disabling MAC CE-based rate adjustment
MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=ANBR_SW-0;
//Disabling uplink coverage optimization based on an increased number of
retransmissions
MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=UL_DELAY_COV_OPT_SW-0;
//(Optional) Restoring the default value of the uplink PDCP discard timer
when uplink coverage optimization based on an increased number of
retransmissions is disabled
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=0, UlPdcpDiscardTimer=MS150;
//(Optional) Restoring the default value of the gNodeB's RLC reassembly
timer when uplink coverage optimization based on an increased number of
retransmissions is disabled
MOD GNBRLCPARAMGROUP: RlcParamGroupId=0, gNBRlcReassemblyTimer=MS40;
//(Optional) Restoring the default value of the gNodeB's PDCP reordering
timer when uplink coverage optimization based on an increased number of
retransmissions is disabled
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=0, gNBPdcpReorderingTimer=MS50;
//Disabling uplink RB reservation
MOD NRCELLALGOSWITCH: NrCellId=7, VonrSwitch=UL_RB_RSV_SW-0;
//Disabling ROHC and ROHC profiles (valid only for newly admitted UEs)
MOD NRCELLALGOSWITCH: NrCellId=7, RohcSwitch=ROHC_SW-0,
RohcProfiles=PROFILE0X0001-0&PROFILE0X0002-0;

4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.4.2 Activation Verification

Before verifying the activation of this function, run the MOD GNB5QICONFIG or ADD
GNB5QICONFIG command with the gNB5qiConfig.Nr5qi parameter set to 1 and the
 gNB5qiConfig.CounterObjSubscriptionInd parameter set to YES to take 5QI 1 as the measurement
object.
After the preceding configurations are complete, you can observe related counters to check
whether this function has been activated. If the value of any of the counters listed in Table 4-3 is
not 0, this function has been activated.
Table 4-3 Counters for VoNR activation verification
Counter ID Counter Name

1911820520 N.QosFlow.Max.Cell5QI

1911820521 N.QosFlow.Avg.Cell5QI

1911820488 N.User.RRCConn.Active.DuCell5QI.Max

1911820489 N.User.RRCConn.Active.DuCell5QI.Avg

1911820510 N.QosFlow.Est.Att.Cell5QI

1911820511 N.QosFlow.Est.Succ.Cell5QI

4.4.3 Network Monitoring

After this function is enabled, you can monitor the activation status of this function based on
voice quality-related counters and voice service-related KPIs. Before network monitoring, you
can configure the measurement object to 5QI 1 or 5 as required.
• Configuring the measurement object to 5QI 1
Run the MOD GNB5QICONFIG or ADD GNB5QICONFIG command with the
gNB5qiConfig.Nr5qi parameter set to 1 and the
gNB5qiConfig.CounterObjSubscriptionInd parameter set to YES to configure the
measurement object to 5QI 1.
• Configuring the measurement object to 5QI 5
Run the MOD GNB5QICONFIG or ADD GNB5QICONFIG command with the
gNB5qiConfig.Nr5qi parameter set to 5 and the
gNB5qiConfig.CounterObjSubscriptionInd parameter set to YES to configure the
measurement object to 5QI 5.

Counters Related to Voice Quality

Table 4-4 lists the VoNR codec schemes and coding rates applicable to voice quality monitoring.
Table 4-5 lists the counters to be monitored.

Table 4-4 Codec schemes and coding rates applicable to voice quality monitoring

Codec Scheme Supported Voice Coding Rates (kbit/s)

EVS-WB 7.2, 8.0, 9.6, 13.2, 16.4, 24.4

Codec Scheme Supported Voice Coding Rates (kbit/s)

EVS-SWB 9.6, 13.2, 16.4, 24.4

AMR-WB I/O 6.6, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05, 23.85

AMR-NB 4.75, 5.15, 5.9, 6.7, 7.4, 7.95, 10.2, 12.2

AMR-WB 6.6, 8.85, 12.65, 14.25, 15.85, 18.25, 19.85, 23.05, 23.85

Table 4-5 Counters related to voice quality of VoNR services

Counter ID Counter Name

1911822846 N.VoNR.VQI.UL.Total

1911822845 N.VoNR.VQI.DL.Total

1911822856 N.VoNR.VQI.UL.Excellent.Times

1911822855 N.VoNR.VQI.UL.Good.Times

1911822854 N.VoNR.VQI.UL.Accept.Times

1911822853 N.VoNR.VQI.UL.Poor.Times

1911822852 N.VoNR.VQI.UL.Bad.Times

1911822851 N.VoNR.VQI.DL.Excellent.Times

1911822850 N.VoNR.VQI.DL.Good.Times

1911822849 N.VoNR.VQI.DL.Accept.Times

1911822848 N.VoNR.VQI.DL.Poor.Times

1911822847 N.VoNR.VQI.DL.Bad.Times

1911822857 N.VoNR.VQI.Codec.AMRNB.Times

1911822858 N.VoNR.VQI.Codec.AMRWB.Times

1911822859 N.VoNR.VQI.Codec.EVSIO.Times

1911822860 N.VoNR.VQI.Codec.EVSPriWB.Times

1911822861 N.VoNR.VQI.Codec.EVSPriSWB.Times

Voice quality indicator (VQI) is a P.863 standard–based estimation method using mathematical
formulas fitting. It differs from tool-based objective evaluation because they have different
working principles and measurement scopes. The MOSs provided by specialized tools are
subject to factors such as test equipment, UE codec scheme, and jitter buffer algorithm and may
 fluctuate greatly. However, VQI values are immune to UE factors. Table 4-6 lists the mapping
between VQI values and voice quality levels defined by the Huawei VQI algorithm.
Table 4-6 Mapping between VQI values and voice quality levels

VQI Value Voice Quality Level

VQI > 400 Excellent

300 < VQI ≤ 400 Good

200 < VQI ≤ 300 Accept

100 < VQI ≤ 200 Poor

VQI = 100a Bad

a: When the VQI value ranges from 0 to 100, the value 100 is used.

KPIs Related to Voice Services

• Voice bearer setup success rate = (N.QosFlow.Est.Succ.Cell5QI/N.QosFlow.Est.Att.Cell5QI) x

100%
• Voice service drop rate = N.QosFlow.AbnormRel.Cell5QI/(N.QosFlow.NormRel.Cell5QI +
N.QosFlow.AbnormRel.Cell5QI) x 100%

• Voice packet loss rate

▪ Uplink voice packet loss rate =
N.PDCP.UL.TrfSDU.RxPacket.Loss.Cell5QI/(N.PDCP.UL.TrfSDU.RxPacket.Loss.Cell5
QI + N.PDCP.UL.TrfPDU.RxPackets.Cell5QI) x 100%
▪ Downlink voice packet loss rate =
N.RLC.DL.TrfSDU.PktUuTrans.Loss.DuCell5QI/N.RLC.DL.TrfSDU.RxPackets.DuCell5
QI x 100%

5 Parameters

The following hyperlinked EXCEL files of parameter reference match the software version with
which this document is released.
• Node Parameter Reference: contains device and transport parameters.
 • gNodeBFunction Parameter Reference:contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.

You can find the EXCEL files of parameter reference for the software version used on the live network from the
product documentation delivered with that version.

FAQ: How do I find the parameters related to a certain feature from parameter reference?
1. Open the EXCEL file of parameter reference.
2. On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
3. Click OK. All parameters related to the feature are displayed.

6 Counters

The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
• Node Performance Counter Summary: contains device and transport counters.
• gNodeBFunction Performance Counter Summary:
contains all counters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.

You can find the EXCEL files of performance counter reference for the software version used on the live network
from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from performance counter
reference?
1. Open the EXCEL file of performance counter reference.
2. On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, FBFD-020100.
3. Click OK. All counters related to the feature are displayed.
7 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

8 Reference Documents

• 3GPP TS 38.306, "NR; User Equipment (UE) radio access capabilities"

• Interoperability Between E-UTRAN and NG-RAN

• Mobility Management

• DRX

• UE Power Saving

• Multi-Operator Sharing

• LTE FDD and NR Spectrum Sharing

• VoLTE in eRAN Feature Documentation

• Technical Specifications in 3900 & 5900 Series Base Station Product Documentation