Network Slicing Management

Product Version: NR22.2

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P. R. China
Postcode:518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION

Copyright ©2020 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties.
Any reproduction or distribution of this document or any portion of this document, in any
form by any means, without the prior written consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by contractual confidentiality
obligations.

All company, brand and product names are trade or service marks, or registered trade or
service marks, of ZTE CORPORATION or of their respective owners.

This document is provided“as is”, and all express, implied, or statutory warranties,
representations or conditions are disclaimed, including without limitation any implied
warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE
CORPORATION and its licensors shall not be liable for damages resulting from the use of or
reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights
or applications covering the subject matter of this document. Except as expressly provided
in any written license between ZTE CORPORATION and its licensee, the user of this
document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product
without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire

related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Serial Number:2023-03-05
 Network Slicing Management

Network Slicing Management

1 About This Document

1.1 Personal Data Security Statement

Some of the features listed in this document need users’ personal data during provisioning, including the SUPI, IMSI, IMEI, MSISDN, and UEIP.
These features are used for the purpose of implementing the service procedures or location procedures specified by 3GPP, optimizing service
experience of users, and facilitating system maintenance. When activating these features, you shall comply with local laws and regulations on
personal data protection and privacy protection.For any inquiries on the legality of activating these features, please consult your legal
department.

1.2 Changes

This section describes the changes between different versions of the product, including two types of changes:
Technical changes: technical changes and parameter changes between different versions.
Description changes: description and structure changes between different versions, including content optimization and supplementation.

Change Type Change Date Description Parameter Change

Technical changes 2023-01-30 Compared with the NR22.1 version, there is no change. None

Description changes 2023-01-30 Compared with the NR22.1 version, there is no change. None

2 Document Description

2.1 Covered Features

The following table lists the features covered in this document.

Table 1 Covered Feature List

No. NR22.2 Feature ID NR22.2 Feature Name NR21.2 Feature ID& Name Scenario Refer to

1 ZNR-VS-0030 RAN Slicing ZNR03-11-011 RAN Awared Slicing SA 4 RAN Slice Management
ZNR03-11-012 RAN Slice Management 5 Slice Awareness
ZNR03-11-013 RAN SLA Guarantee 6 RAN Slice SLA Guarantee

2.2 Correlation with Other Features

Table 2 Correlation with Other Features

Feature ID Feature Name Required Feature Mutually Exclusive Feature Impacted Feature

ZNR-VS- RAN Slicing None None None

0030

2.2.1 ZNR-VS-0030：RAN Slicing

Required Feature

■ RAN Awared Slicing is the basis of RAN Slice Management.

■ RAN Awared Slicing is the basis of RAN SLA Guarantee.

Mutually Exclusive Feature

3 - 74
 Network Slicing Management

■ If the slice PRB guarantee function is enabled, the slice rate guarantee function is not supported.

■ If the slice PRB guarantee function is enabled, the 5QI PRB guarantee function is not supported.

Impacted Feature
None.

2.3 Terms and Definitions

For the related terms and definitions, refer to the following table.

Table 3 Terms and Definitions

Term Full Name Definition

5G-S- 5G-S-Temporary The 5G-S-TMSI is the shortened form of the 5G-GUTI to enable more efficient radio signalling procedures (e.g.
TMSI Mobile paging and Service Request). For paging purposes, the mobile is paged with the 5G-S-TMSI. The 5G-S-TMSI
Subscriber shall be constructed from the AMF Set ID, the AMF Pointer and the 5G-TMSI:<5G-S-TMSI> = <5G-TMSI>
Identity

AMF Access and A NE of the core network is responsible for signaling interaction, provides the UE access and mobility
Mobility management functions.
Management
Function

BN BackBone Used to connect high-speed networks in multiple areas. Each backbone network has at least one connection
Network point for interconnection with other backbone networks. Different network suppliers have their own
backbone networks to connect to the networks in different areas.

CN Core Network An architectural term relating to the part of 3GPP System which is independent of the connection technology
of the terminal (eg radio, wired).

CSMF Communication The northbound interface of the core network is directly oriented to end users, providing a friendly man-
Service machine interface. It receives communication service requirements of users (such as SLA, capacity, and
management deployment characteristics) and generates slices accordingly. It provides life-cycle operation and
Function maintenance including subscription, customization, activation, modification, deactivation, and cancellation
of communication services.

CU gNB Centralized Centralized unit. As defined in the 5G standard, the CU implements control plane and user plane functions
Unit and supports virtualization.

CUCP gNodeB It is a logical node, consisting of the RRC and PDCP control plane of the gNB or en-gNB CU.
Centralized Unit
Control Process

CUUP gNB CU User a logical node hosting the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user
Plane plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP terminates
the E1 interface connected with the gNB-CU-CP and the F1-U interface connected with the gNB-DU.

DU gNB Distributed a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by
Unit CU. One DU supports one or multiple cells. One cell is supported by only one DU. The DU terminates the F1
interface connected with the CU.

eMBB enhanced Mobile Enhanced Mobile Broadband (eMBB) refers to the use case of using 5G as an evolution to 4G LTE mobile
Broadband broadband services with faster connection with higher throughput and more capacity.

EMS Element 4G Element Management System. The EMS is connected to the OSS and BSS systems through the northbound
Management interface, and manages configurations, alarms, and performance.
System

mMTC Massive Machine Massive Machine-Type Communications (mMTC) refers to the wide area IoT use cases consisting of large
Type numbers of low-cost devices with high requirements on scalability and increased battery lifetime.
Communications

NSMF Network Slice The network slice management can use different technology domains and their segments to create an end-to-
Management end slice. It has full visibility and control to the end-to-end slice and its performance. It monitors slice specific
Function FCAPS to maintain and to expose the overall SLAs of the end-to-end slices to the tenant.

4 - 74
 Network Slicing Management

NSSMF Network Slice It includes the RAN slice sub-network management, transmission slice sub-network management, and core-
Subnet network slice sub-network management functions.
Management
Function

NSSAI Network Slice The NSSAI is a collection of S-NSSAI (Single ‒ Network Slice Selection Assistance Information) and is sent to
Selection the network by the UE to assist the network in selecting a particular Network Slice.
Assistance
Information

PDU Protocol Data Protocol data unit. It is an information unit sent from an upper protocol layer to a lower protocol layer.
Unit

PRB Physical Physical resource block.

Resource Block

QoS Quality of Comprehensively reflects the service capability of the 5G System (5GS) and determines the user satisfaction of
Service the services provided by the carrier.

RAN Radio Access Radio Access Network

Network

RRM Radio Resource It includes cell-level radio resource management, user-level radio resource management, and user mobility
Management management.

SLA Service Level A service-level agreement is a part of a standardized service contract where a service is formally defined.
Agreement Particular aspects of the service ‒ scope, quality, responsibilities ‒ are agreed between the service provider
and the service user.

UE User Equipment Device that allows users to access network services through wireless interfaces.

UPF User Plane User plane management module, an NE of the CN, used for Routing and forwarding user plane data packets.
Function

URLLC Ultra Reliable Ultra-Reliable Low-Latency Communications (URLLC) refers to the use case of 5G in mission-critical
Low Latency applications such as factory automation, where uninterrupted and robust exchange of data is of the utmost
Communications importance.

2.4 Feature Difference Descriptions

2.4.1 Difference Between FR1 FDD and FR1 TDD

Table 4 Difference Between FR1 FDD and FR1 TDD

Feature Difference Description Refer to

RAN Slice Management Support FR1 FDD and FR1 TDD，no difference. 4 RAN Slice Management

RAN Awared Slicing Support FR1 FDD and FR1 TDD，no difference. 5 Slice Awareness

RAN SLA Guarantee Support FR1 FDD and FR1 TDD，no difference. 6 RAN Slice SLA Guarantee

2.4.2 Difference Between NSA and SA Networks

Table 5 Difference Between NSA and SA Networks

Feature Difference Description Refer to

RAN Slice Management NSA Not Support Slice Management 4 RAN Slice Management

RAN Awared Slicing NSA Not Support Slice Awareness 5 Slice Awareness

RAN SLA Guarantee NSA Not Support Slice SLA Guarantee 6 RAN Slice SLA Guarantee

2.4.3 Difference Between FR1 and FR2

Here in this document, FR1 refers to 410MHz~7125MHz, FR2 refers to 24250MHz~52600MHz. For detailed definition of FR1 and FR2, refer to 5.1

5 - 74
 Network Slicing Management

General in 3GPP TS 38.104 V15.5.0.

Table 6 Difference Between FR1 and FR2

Feature Difference Description Refer to

RAN Slice Management Support FR1 only, and FR2 is not supported 4 RAN Slice Management

RAN Awared Slicing Support FR1 only, and FR2 is not supported 5 Slice Awareness

RAN SLA Guarantee Support FR1 only, and FR2 is not supported 6 RAN Slice SLA Guarantee

3 Overview
5G networks integrate the communications industry and vertical industries, with the ultimate goal of enabling digitalization of the entire
industry. To achieve this goal, the 5G network needs to meet the following three key requirements:
● Independent operation of services
● Safe isolation
● Guaranteable SLA (Service Level Agreement)
Traditional networks cannot independently operate and securely isolate services in accordance with different service requirements, and
cannot provide efficient SLA guarantee for all services. Therefore, the concept of network slicing is proposed in the industry. 16.3 Network
Slicing in 3GPP TS 38.300 V15.6.0 defines the network slicing function. The network slicing function can divide the physical network of the
operator into multiple logical networks to achieve multi-use of one network. Network slicing enables operators to build multiple end-to-end,
virtual, isolated, and customized dedicated logical networks on a physical network to meet different requirements of industry customers for
network capabilities (delay, bandwidth, number of connections, and reliability).
Network slicing provides three typical scenarios: EMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communications) and
uRLLC (ultra-Reliable and Low Latency Communications).
● eMBB: Enhanced Mobile Broadband, oriented to service applications with large bandwidth transmission rate.
● mMTC: For ultra-dense, low-power access applications.
● uRLLC: With low latency and high reliability, it is oriented to fast response, secure and highly reliable service applications.
To meet customer requirements for communication network capabilities, it is necessary to provide end-to-end guarantee from the core
network to the transport network and then to the RAN, which is called end-to-end network slicing. End-to-end network slicing involves the core
network, transport network, and RAN slice subnet, and is managed by the end-to-end slice management system. The RAN slice subnet is a key
part of End-to-end network slicing. The RAN slice subnet can be flexibly customized in accordance with the SLA requirements delivered by the
end-to-end slice orchestration management system.
This document describes the implementation of the network slicing function on the RAN side, including slice management, slice awareness,
and slice SLA guarantee.
● Slice management: provides RAN slice configuration, RAN slice subnet instance life cycle management, and slice KPI & Alarm reporting
function.
●Slice awareness: The RAN senses the slice information supported by the core network and UEs, and selects a matched AMF for a UE to access
so that the UE can obtain the corresponding service
●Slice SLA guarantee: The RAN provides SLA guarantee for network slices and provides support for end-to-end SLA guarantee.

4 RAN Slice Management

4.1 Principle

Figure 1 Slice Management

6 - 74
 Network Slicing Management

As shown in Figure 1, a UE customizes the communication service through the Communication Service Management Function (CSMF) on the
client. After receiving a service request, the Network Slice Management Function (NSMF) creates a slice meeting the SLA requirements and
decomposes the SLA requirements to the Network Slice Subnet Management Function (NSSMF) of each slice subnet.For the RAN slice subnet,
the RAN (Access Network) NSSMF is the network slice subnet management function of the access network and is responsible for the slice
management of the access network. RAN NSSMF provides users with RAN-side network slice configuration management, slice sub-instance
lifecycle management, slice KPI, and alarm reporting functions.
The network slicing deployment should first complete the network slicing configuration of the gNodeB. Since the core network configures the
network slicing according to the tracking area, the gNodeB needs to configure the tracking area network slicing. The gNodeB configures the
network slice of the tracking area through the MO NetworkSliceSubnet, and associates the gNodeB network slice with the tracking area,
including configuring the following parameters, as shown in Table 7.
Table 7 gNodeB Network Slicing Configuration

NO Parameter Descriptions Related Parameters

1 Tracking area codes SliceProfile.coverageAreaTAList

2 PLMN ID list SliceProfile.pLMNIdList

3 Slice service type NSSAI.sst

4 Slice differentiator NSSAI.sd

The slice sub-instance lifecycle management feature controls the activation and deactivation of RAN sub-slice instances, including the
configurations of the following parameters, refer toTable 8.

Table 8 RAN NSSI Parameters

NO Parameter Descriptions Related Parameters

1 Administrative state NetworkSliceSubnet.administrativeState

After the network slicing deployment is completed, the gNodeB can sense the network slicing of the core network, and the network slicing user
can perform services normally. The gNB NE can provide slice-level related KPIs and alarms to the RAN NSSMF as required to support
performance monitoring and O&M.
Note: In current version, slice-level KPI reporting control is based on the slice whitelist information parameters( SlicePmWhitelist.plmn，
SlicePmWhitelist.sst and SlicePmWhitelist.sd） configured on demand.

4.2 Network Analysis

Note:
The feature activation effect depends on the network environment. Therefore, this document only guides the feature provisioning. For network

7 - 74
 Network Slicing Management

gains pertinent contents, refer to ZTE for support.

4.2.1 Benefit Analysis

provides RAN slice configuration,RAN slice subnet instance life cycle management and slice KPI & Alarm reporting function.

4.2.2 Impact Analysis

None.

4.3 Application Scenarios

This feature is applicable to all 5G SA network scenarios.

4.4 Provisioning Guidance

4.4.1 Slice Management Provisioning Guidance

4.4.1.1 Prerequisites

Table 9 Hardware Requirement

Device Description Remark

5GC/EPC 5GC 1

BBU V9200 1

AAU/RRU/Qcell No spectial requirement on RRU 1

Table 10 Other Requirement

Other Requirement Description

CN Slicing needs to be supported

Carrier frequency bands, frequencies, and bandwidths None

UE Slicing needs to be supported

Transmission bandwidth None

FTP server None

4.4.1.2 Restrictions

Support FR1 only, and FR2 is not supported

4.4.1.3 Feature Activation

4.4.1.3.1 Feature Activation Process

After a base station is commissioned successfully, basic NSSI parameters need to be configured on the base station side for the access of UEs
with slices.
Table 11 Slice ManagementConfiguration Process and Related Parameter

No. Step Related Parameter Verification

8 - 74
 Network Slicing Management

1 Add a NetworkSliceSubnet record in network slice configuration in DU NetworkSliceSubnet.nssiId None

NetworkSliceSubnet.administrativeState
NetworkSliceSubnet.operationalState

2 Add a SliceProfile record in network slice configuration in DU SliceProfile.sliceProfileId None

SliceProfile.coverageAreaTAList
SliceProfile.pLMNIdList

3 Add a NSSAI record in network slice configuration in DU NSSAI.sst None

NSSAI.sd

4.4.1.3.2 Related Parameters and Figures

Table 12 Slice Management Feature Activation

No. Paramete Parameter Na Configura Parameter Path Configuration

r ID me tion Exa Principle
mple

1 Network NSSI ID 1 Managed Element/gNB DU function configuration/Network Slice Subnet This

SliceSub Configuration parameter is
net.nssiId configured in
accordance
with the
actual
operator
requirements.

2 Network Administrative Unlocked Managed Element/gNB DU function configuration/Network Slice Subnet To activate an
SliceSub state Configuration NSI in the
net.admi network slice
nistrative
group, set
State
this
parameter to
Unlocked.

3 Network Operational Enabled Managed Element/gNB DU function configuration/Network Slice Subnet To activate an
SliceSub state Configuration NSI in the
net.opera network slice
tionalSta
group, set
te
this
parameter to
Enabled.

4 SliceProfi Slice profile ID 1 Managed Element/gNB DU function configuration/Network Slice Subnet This
le.slicePr Configuration/Slice Profile Configuration parameter is
ofileId configured in
accordance
with the
actual
operator
requirements.

5 SliceProfi Tracking area 512000 Managed Element/gNB DU function configuration/Network Slice Subnet This
le.covera codes Configuration/Slice Profile Configuration parameter is
geAreaTA configured in
List
accordance
with the
actual
operator
requirements.

9 - 74
 Network Slicing Management

6 SliceProfi PLMN ID list 460-01 Managed Element/gNB DU function configuration/Network Slice Subnet This
le.pLMNI Configuration/Slice Profile Configuration parameter is
dList configured in
accordance
with the
actual
operator
requirements.

7 NSSAI.sst Slice service 1 Managed Element/gNB DU function configuration/Network Slice Subnet This
type Configuration/Slice Profile Configuration/NSSAI List Configuration; parameter is
Managed Element/gNB DU function configuration/Cell DU/QoSMap configured in
configuration parameters/MLCP configuration for SA/GBR-based MLCP accordance
configuration for SA/NSSAI List Configuration; Managed Element/gNB with the
DU function configuration/Cell DU/QoSMap configuration actual
parameters/MLCP configuration for SA/NGBR-based MLCP configuration operator
for SA/NSSAI List Configuration; Managed Element/gNB DU function requirements.
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/MLCP configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function configuration/Cell DU/QoSMap
configuration parameters/LCG configuration for SA/LCG configuration
for SA/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/5QI-based
QoS weight factor configuration for SA/5QI-based QoS weight
factor/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/The
configures of SaDelayGuaranteeConfig/NSSAI List Configuration

8 NSSAI.sd Slice 1118481 Managed Element/gNB DU function configuration/Network Slice Subnet This
differentiator Configuration/Slice Profile Configuration/NSSAI List Configuration; parameter is
Managed Element/gNB DU function configuration/Cell DU/QoSMap configured in
configuration parameters/MLCP configuration for SA/GBR-based MLCP accordance
configuration for SA/NSSAI List Configuration; Managed Element/gNB with the
DU function configuration/Cell DU/QoSMap configuration actual
parameters/MLCP configuration for SA/NGBR-based MLCP configuration operator
for SA/NSSAI List Configuration; Managed Element/gNB DU function requirements.
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/MLCP configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function configuration/Cell DU/QoSMap
configuration parameters/LCG configuration for SA/LCG configuration
for SA/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/5QI-based
QoS weight factor configuration for SA/5QI-based QoS weight
factor/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/The
configures of SaDelayGuaranteeConfig/NSSAI List Configuration

Figure 2 NetworkSliceSubnet

10 - 74
 Network Slicing Management

Figure 3 SliceProfile

Figure 4 NSSAI

11 - 74
 Network Slicing Management

4.4.1.4 Feature Deactivation

When Administrative state is Locked or the Operational state is Disabled, the slice is unavailable.

4.4.1.4.1 Feature Deactivation Process

Table 13 Slice ManagementConfiguration Process and Related Parameter

No. Step Related Parameter Verification

1 Modify the NetworkSliceSubnet record in network slice configuration in NetworkSliceSubnet.administrativeStat None

DU e
NetworkSliceSubnet.operationalState

4.4.1.4.2 Feature Deactivation Process Related Parameter and Figure

Table 14 Slice Management Feature Deactivation

No. Parameter ID Parameter Na Configuration Exa Parameter Path

me mple

1 NetworkSliceSubnet.operatio Operational Disabled[Disabled] Managed Element/gNB DU function configuration/Network

nalState state Slice Subnet Configuration

2 NetworkSliceSubnet.adminis Administrative Locked[Locked] Managed Element/gNB DU function configuration/Network

trativeState state Slice Subnet Configuration

Figure 5 Feature Deactivation-NetworkSliceSubnet

12 - 74
 Network Slicing Management

4.4.1.5 Test Method

4.4.1.5.1 Slice Management Test Method

Table 15 Slice Management Test Method

Test Item Slice Management

Sub-Item N/A

Prerequisites The cell is established properly and in service.

test Steps 1、Configure different slice policies and make UEs access the gNodeB.
2、For the detailed configuration, refer to the following guide.
Refer to Admission Congestion Control Section 6；
Refer to QoS Management Section 12；

Expected Result The UE can be connected to the gNodeB properly, and services operate properly.

4.4.1.5.2 RAN Supporting NSSI Lifecycle Management Test Method

Table 16 RAN Supporting NSSI Lifecycle Management Test Method

Test Item RAN Supporting NSSI Lifecycle Management

Sub-item N/A

Prerequisites The gNodeB is configured with multiple slices. The slices status is unlocked.

Test Steps 1、The UE is connected normally, the signaling is normal, and the PDU Session is successfully established.
2、Modify the slice state, and set the Administrative state of the slice to locked[Locked] or the Operational status to
Disabled[Disabled]. For details, see【Figure Configuring the Deactivation NetworkSliceSubnet Parameter】.
3、Observe cell data of corresponding signaling.

13 - 74
 Network Slicing Management

Expected 1. If only one PDU Session is created when the UE attaches, after the slice of this PDU Session is Locked or Disabled,
Result the service is terminated and the UE is released. The signaling UE CONTEXT RELEASE REQUEST carries the cause
message: F1ap_CauseRadioNetwork_Ext_resources_not_available_for_the_slice. For the signaling screenshot, seeFig
ure 8.
2. If multiple PDU Session of different slices are established during UE attaches, some of the slices are Locked or
Disabled., the services of those PDU Session are terminated, services of other slices is normal, and the UE is not
released. The signaling UE CONTEXT MODIFICATION REQUIRED carries the cause cause message:
F1ap_CauseRadioNetwork_Ext_resources_not_available_for_the_slice. For the signaling screenshot, seeFigure 9. The
signaling PDU SESSION RESOURCE NOTIFY carries the cause cause message:
Ngap_CauseRadioNetwork_Root_Resources_not_available_for_the_slice. For the signaling screenshot, seeFigure 10.
For detail, refer to 4.4.1.6.2 RAN Supporting NSSI Lifecycle Management Provisioning Observation

4.4.1.5.3 RAN Supporting Alarm Reporting With Slice information Test Method

Table 17 RAN Supporting Alarm Reporting With Slice information Test Method

Test Item RAN Supporting Alarm Reporting With Slice information

Sub-item N/A

Prerequisites The cell is established properly and in service.

Test You can check the alarm with slice information by triggering cell shutdown or cell out-of-service. Test alarm reporting: Use
Steps different methods to trigger the corresponding alarms. Wait for one minute and then check the alarm information in the
UME alarm management.
1. Test method for triggering the cell shutdown alarm: Change the Admin state of the DU cell to Locked[Locked], that is,
blocking the DU cell. For details. For alarm information observation, seeFigure 11.
2. Test method for triggering the cell out-of-service alarm: Delete the CU cell, that is, do not configure the CU cell. For alarm
information observation, seeFigure 12.

Expected 1. The title of the cell shutdown alarm is Cell Shutdown, and the additional parameters contain the network slice
Result information.
2. The title of the cell out-of-service alarm is Cell out-of-service. Additional parameters are written into the network slice
information.
For detail, refer to 4.4.1.6.3 RAN Supporting Alarm Reporting With Slice information Provisioning Observation

4.4.1.6 Provisioning Observation

4.4.1.6.1 Slice Management Provisioning Observation

Observe the signaling of the INITIAL CONTEXT SETUP, and verify that the corresponding slice bearer is established successfully.

Figure 6 INITIAL CONTEXT SETUP REQUEST

14 - 74
 Network Slicing Management

Figure 7 INITIAL CONTEXT SETUP RESPONSE

4.4.1.6.2 RAN Supporting NSSI Lifecycle Management Provisioning Observation

Note: After base station commissioning, the slice operational status is enabled. The provisioning observation is displayed slice deactivation
status in slice lifecycle management.
Set up a signaling tracing task in the signaling tracing and analysis module of the UME NM, observe the signaling of the F1 and NG interfaces,
and check the cause messages carried in the signaling.

Expected Result 1: Only one PDU Session is created when the UE attaches.
Figure 8 UE CONTEXT RELEASE REQUEST Signaling

15 - 74
 Network Slicing Management

Expected Result 2: Multiple PDU Session of different slices are established during UE attaches
Figure 9 UE CONTEXT MODIFICATION REQUIRED Signaling

Figure 10 PDU SESSION RESOURCE NOTIFY Signaling

16 - 74
 Network Slicing Management

4.4.1.6.3 RAN Supporting Alarm Reporting With Slice information Provisioning Observation

As shown in the Figure 11, the additional parameters in the alarm information will carry the PLMN information and slice information of the
gNodeB. Note: For the 1-111111 and 1-111113 shown in the figure, 111111 and 111113 are in hexadecimal format. The DN information indicates
the location of the cell to be shut down.

Figure 11 Cell Shutdown Alarm

As shown in the Figure 12, the additional parameters in the alarm information will carry the PLMN information and slice information of the
gNodeB. Note: For the 1-111111 and 1-111113 shown in the figure, 111111 and 111113 are in hexadecimal format. The DN information indicates
the location of the out-of-service cell.

Figure 12 Cell Out-of-Service Alarm

17 - 74
 Network Slicing Management

4.4.2 VLAN ID Provisioning Guidance

4.4.2.1 Prerequisites

Table 18 Hardware Requirement

Device Description Remark

5GC/EPC 5GC None

BBU V9200 None

AAU/RRU/Qcell No spectial requirement on RRU None

Table 19 Other Requirement

Other Requirement Description

CN The VLAN need to be supported.

Carrier frequency bands, frequencies, and bandwidths None.

UE None.

Transmission bandwidth None.

FTP server None.

4.4.2.2 Restrictions

Support FR1 only, and FR2 is not supported.

4.4.2.3 Feature Activation

4.4.2.3.1 Feature Activation Process

Table 20 VLAN ID Process and Related Parameter

18 - 74
 Network Slicing Management

No. Step Related Parameter Verification

1 Add slice configuration corresponding to vid in network slice information in CU NetworkSliceInfoUp.sst None
NetworkSliceInfoUp.sd

3 Add vid in slice service configuration SliceServiceConfig.vid None

4.4.2.3.2 Related Parameters and Figures

For an example of the parameters and configurations associated with the virtual LAN number configuration, refer to the following table.

Table 21 VLAN ID Feature Activation

No. Parameter ID Paramete Configuration Parameter Path Configuration Principle

r Name Example

1 NetworkSliceI SST 1 Managed Element/GNBCUUPFunction/Network slice This parameter is

nfoUp.sst information of the simplified version configured as planned.

2 NetworkSliceI SD 1118481 Managed Element/GNBCUUPFunction/Network slice This parameter is

nfoUp.sd information of the simplified version configured as planned.

3 SliceServiceC VLAN ID 111 Managed Element/GNBCUUPFunction/Slice service This parameter is

onfig.vid configuration configured as planned.

Figure 13 Configuring the NetworkSliceInfoUp.sst and NetworkSliceInfoUp.sd Parameter

Figure 14 Configuring the SliceServiceConfig.vid Parameter

19 - 74
 Network Slicing Management

4.4.2.4 Feature Deactivation

When the slice corresponding to the vid is deleted or the cinfiguration where the vid is located is deleted, the vid will be unavailable.

4.4.2.4.1 Feature Deactivation Process

Table 22 VLAN ID Process and Related Parameter

No. Step Related Parame Verificati

ter on

1 Delete the slice corresponding to vid in the network slice information, or delete the vid in the slice NetworkSliceInf None
service configuration. oUp
SliceServiceCon
fig

4.4.2.4.2 Feature Deactivation Process Related Parameter and Figure

Delete the following nodes.

Figure 15 NetworkSliceInfoUp Feature Deactivation

Figure 16 SliceServiceConfig Feature Deactivation

20 - 74
 Network Slicing Management

4.4.2.5 Test Method

Table 23 VLAN ID Test Method

Test Item RAN Supporting Alarm Reporting With Slice information

Sub-item N/A

Prerequisites None.

Test 1. Add SliceServiceConfig configuration on the Network Management;

Steps 2. UE accesses;
3. Perform UDP uplink packet injection service;
4. Capture packets on the NG port of the gNodeB.

Expected 1. The Virtual LAN ID carried in the packet is consistent with theSliceServiceConfig.vid on the Network Management.
Result

4.4.2.6 Provisioning Observation

Asshown in Figure 17, Virtual LAN ID is the VLAN ID in packets.

Figure 17 VLAN ID in packets

5 Slice Awareness

5.1 Principle

The network slice perception function includes the following:

● AMF selection based on slice awareness
● AMF redirection
● Slice-Based Awareness Service

21 - 74
 Network Slicing Management

5.1.1 AMF selection based on slice awareness

Because different AMFs of the core network may support different network slices, and different UEs may subscribe to different network slices.
The RAN needs to sense the network slices supported by the AMFs and UEs so that the RAN can route the UEs to the correct network slices.
In the NG establishment procedure, the RAN can obtain the network slices supported by AMFs. In the UE access procedure, the RAN can sense
the network slice that the UE subscribes to in accordance with the 5G-S-TMSI or NSSAI information carried by the UE.
After successfully sensing the network slice information of the AMFs and the UE, the RAN selects an AMF for the UE.

■ If the UE carries a valid 5G-S-TMSI, the AMF is selected based on the 5G-S-TMSI.

■ If the UE carries a valid RegisteredAMF, AMF is selected based on RegisteredAMF.

■ If the UE carries a valid NSSAI, the AMF is selected based on the NSSAI.

■ If the UE does not carry any 5G-S-TMSI or NSSAI, the default AMF is selected (if the NgAp.defaultFlag parameter for connecting an AMF is

set to "true," the AMF is the default AMF).

The slice information supported by the AMF is obtained from the NG Setup Request message when a connection is established on the NG
interface. The 5G-S-TMSI or NSSAI during UE access is carried in the RRC Setup Complete message, see Figure 18.

Figure 18 Slice Awareness and AMF

5.1.2 AMF Re-allocation

During a Registration procedure in a PLMN, if the network decides that the UE should be served by a different AMF based on Network Slice(s)
aspects, then the AMF that first received the Registration Request shall redirect the Registration request to another AMF via the RAN or via
direct signalling between the initial AMF and the target AMF. The redirection message sent by the AMF via the RAN shall include information for
selection of a new AMF to serve the UE.
For a UE that is already registered, the system shall support a redirection initiated by the network of a UE from its serving AMF to a target
AMF due to Network Slice(s) considerations (e.g. the operator has changed the mapping between the Network Slice instances and their
respective serving AMF(s)). Operator policy determines whether redirection between AMFs is allowed.
AMF redirection can be implemented in two modes:
(1) Indirect Redirection Between AMFs
(2) Direct Redirection Between AMFs

5.1.2.1 Indirect Redirection Between AMFs

Figure 19 Indirect Redirection Between AMFs

22 - 74
 Network Slicing Management

As shown inFigure 19：

1） GNB sends the initial UE message to the source AMF to trigger the UE's access and registration procedure in the AMF.
2） When the AMF finds that it no longer supports the UE slice, it chooses the RAN to perform indirect redirection. The RerouteNASRequest
message sent by the source AMF to gNB will carry:
● Information related to the target AMF (i.e. AMF Set ID ). The gNB matches the new AMF according to the information.
●gNB sends the initial UE message (i.e. NGAP Message ) to the AMF. The gNB can decode the message, obtain the unsaved information, and
construct the initial UE message to the target AMF.
● The slice information (i.e. Allowed NSSAI ) allowed by the AMF may be carried. If this cell is carried, gNB needs to transmit this cell to the
target AMF.
3） GNB selects and rebinds the target AMF, and sends a new initial UE message to the target AMF. This message needs to carry the AMF Set ID
, indicating that this message is a redirected initial UE message.
4） Before other procedures change the NG interface connection, the subsequent NG interface messages of the UE are transmitted between
the gNB and the target AMF.

5.1.2.2 Direct Redirection Between AMFs

Figure 20 Base On InitialContextSetupRequest Direct Redirection Between AMFs

As shown inFigure 20：

1） GNB sends the initial UE message to the source AMF to trigger the UE's access and registration flow in the AMF.
2） When the AMF finds that it does not support the slice of the UE, it selects to perform the direct redirection between AMFs.
3） The target AMF returns an initial context setup message to the gNB, carrying the information of the source AMF (that is, the Old AMF cell).
After receiving the message, the gNB binds the association again.
4） Before other procedures change the NG interface connection, the subsequent NG interface messages of the UE are processed between the
gNB and the target AMF.
Figure 21 Base On DownlinkNASTransport Direct Redirection Between AMFs

23 - 74
 Network Slicing Management

As shown inFigure 21：

1） GNB sends the initial UE message to the source AMF, and triggers the UE's access and registration process in the AMF.
2） When the AMF finds that it does not support the slice of the UE, it selects to perform the direct redirection between AMFs.
3） The target AMF returns a downlink nas message to gNB, carrying the information of the source AMF (i.e. Old AMF cell). Upon receipt of the
message, gNB binds the message with the NG association again.
4） Before other procedures change the NG interface connection, the subsequent NG interface messages of the UE are transmitted between
the gNB and the target AMF.

5.1.3 Slice-Based Awareness Service

Figure 22shows the gNodeB's perception of network slice in the core network.

Figure 22 gNodeB perception of Network Slice

The UE sends the NAS message carrying S-NSSAI to the gNodeB. The gNodeB delivers the NAS message to the core network. The core network
verifies whether to support the network slicing of the UE. If not, the supported network slicing information will be returned. If yes, perform the
following verification:
(1) The core network originates the PDU Session setup request to the gNodeB. The request message PDU SESSION RESOURCE SETUP
REQUEST sent to the gNodeB carries the S-NSSAI configured at the core network side. Each PDU Session corresponds to one S-NSSAI.
(2) After getting the S-NSSAI configured at the core network side, the gNodeB verifies whether it supports this network slice. If yes, it will send
a message PDU SESSION RESOURCE SETUP RESPONSE to the core network, which carries the information of PDU Session establishment
success. If not, it will send a message PDU SESSION RESOURCE SETUP RESPONSE to the core network, which carries the information of PDU
Session establishment failure.
For the detailed description of the related messages and cells when the UPDU Session is created, see 9.2.1.1 PDU SESSION RESOURCE SETUP
REQUEST in 3GPP TS 38.413 V15.4.0.
After sensing the S-NSSAI of PDU Session, gNodeB will get the network slice information and QoS information of each Radio Bearer according
to the Radio Bearer and QoS Flow information in PDU Session, to implement differentiated processing strategies for subscribers in different
slices. For details, seeFigure 23.
Figure 23 Network Slice Awareness of Radio Bearers

24 - 74
 Network Slicing Management

Differentiated processing policies for users in different slices at the gNB side include:
● Admission control based on the number of slice group users
● Admission control based on the number of slice group DRBs
● PRB-based admission control of slice groups
● Slice-level QoS mapping
● Slice-level DSCP mapping
● Slice-level WLAN ID mapping

5.1.3.1 Admission Control Based on the Number of Slice Group Users

After the network slicing is deployed, the gNodeB can perform admission control according to the number of users in RRC _ CONNECTED state
in the user's network slicing group. For details, see the corresponding chapter of 《Admission Control》.

5.1.3.2 Slice Group DRB Admission Control

After network slicing deployment, the gNodeB can perform admission control according to the number of DRBs of the user's network slicing
group. For details, see the corresponding chapter of 《Admission Control》.

5.1.3.3 Slice Group PRB Admission Control

After the network slicing is deployed, the gNodeB can perform admission control according to the PRB of the user's network slicing group. For
details, see the corresponding chapter of 《QoS Management》.

5.1.3.4 Slice-level QoS mapping

After network slicing deployment, gNodeB can customize differentiated QoS mapping according to the user's different network slicing services.
For details, see the corresponding chapter of Qo 《QoS Management》.

5.1.3.5 Slice-level DSCP mapping

After the network slicing deployment of the wireless subnet, for example, the QoS guarantee for different slice-based services of the
transmission subnet may have different DSCP mapping policies.The CUUP at the gNodeB side supports mapping different slices to different
DSCP policies, aas shown in Table 24.
Table 24 Slice Based Mapping DSCP Configuration Policy

NO Parameter Descriptions Related Parameters

1 Differentiated Services Code Point SAPriorityMappingTable.dscp

2 Referenced PLMN ID SAPriorityMappingTable.refPlmnIdListUP

3 Slice Service Type SAPriorityMappingTable.sst

25 - 74
 Network Slicing Management

4 Slice differentiation indication SAPriorityMappingTable.sd

5 5G QoS identifier SAPriorityMappingTable.nr5qi

5.1.3.6 Slice level WLAN ID mapping

After the network slicing deployment of the wireless subnet, for example, the QoS guarantee for different slice-based services of the
transmission subnet may have different WLAN ID mapping policies. The CUUP at the gNodeB side supports mapping different slices to different
WLAN ID policies, as shown in Table 25.
Table 25 Slice Based Mapping WLAN ID Configuration Policy

NO Parameter Descriptions Related Parameters

1 VLAN ID SliceServiceConfig.vid

2 Referenced network slice information of the simplified version SliceServiceConfig.refNetworkSliceInfoUp

5.2 Network Analysis

Note:
The feature activation effect depends on the network environment. Therefore, this document only guides the feature provisioning. For network
gains pertinent contents, refer to ZTE for support.

5.2.1 Benefit Analysis

Network slicing is a brand-new design philosophy of telecommunication networks. It can fully adapt to NFV infrastructure, and flexibly match
service requirements with network resources. In this way, network slicing can meet specific function requirements in different vertical
industries, improve service efficiency, reduce overall cost, and improve customer experience. Isolation between network slices can improve
reliability and security.

5.2.2 Impact Analysis

None.

5.3 Application Scenarios

This feature is applicable to all 5G SA network scenarios.

5.4 Provisioning Guidance

5.4.1 AMF Selection and Re-allocation Provisioning Guidance

5.4.1.1 Prerequisites

Table 26 Hardware Requirement

Device Description Remark

5GC/EPC 5GC None

BBU V9200 None

AAU/RRU/Qcell No spectial requirement on RRU None

Table 27 Other Requirement

26 - 74
 Network Slicing Management

Other Requirement Description

CN CN should support multi-PLMN.

Carrier frequency bands, frequencies, and bandwidths None

UE None

Transmission bandwidth None

FTP server None

5.4.1.2 Restrictions

Support FR1 only, and FR2 is not supported

5.4.1.3 Feature Activation

Table 28 Slice SLA Guarantee Feature Activation

No. Paramete Parameter N Configura Parameter Path Configuration Principle

r ID ame tion Exa
mple

1 NSSAI.sst Slice service 1 Managed Element/gNB DU function configuration/Network Slice This parameter is
type Subnet Configuration/Slice Profile Configuration/NSSAI List configured in
Configuration; Managed Element/gNB DU function accordance with the
configuration/Cell DU/QoSMap configuration parameters/MLCP actual operator
configuration for SA/GBR-based MLCP configuration for requirements.
SA/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/NGBR-based MLCP configuration for
SA/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/MLCP configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/LCG
configuration for SA/LCG configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/5QI-
based QoS weight factor configuration for SA/5QI-based QoS
weight factor/NSSAI List Configuration; Managed Element/gNB
DU function configuration/Cell DU/QoSMap configuration
parameters/The configures of SaDelayGuaranteeConfig/NSSAI
List Configuration

27 - 74
 Network Slicing Management

2 NSSAI.sd Slice 1118481 Managed Element/gNB DU function configuration/Network Slice This parameter is
differentiator Subnet Configuration/Slice Profile Configuration/NSSAI List configured in
Configuration; Managed Element/gNB DU function accordance with the
configuration/Cell DU/QoSMap configuration parameters/MLCP actual operator
configuration for SA/GBR-based MLCP configuration for requirements.
SA/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/NGBR-based MLCP configuration for
SA/NSSAI List Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/MLCP configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/LCG
configuration for SA/LCG configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration parameters/5QI-
based QoS weight factor configuration for SA/5QI-based QoS
weight factor/NSSAI List Configuration; Managed Element/gNB
DU function configuration/Cell DU/QoSMap configuration
parameters/The configures of SaDelayGuaranteeConfig/NSSAI
List Configuration

3 GlobalSw Switch of UE False Managed Element/gNB CU-CP function configuration/Global If this parameter is set
itchInfor context Switch to true, the UE Context
mation.U request Request IE is carried in
EContext
enablement the INITIAL UE
ReqEnabl
MESSAGE message,
e
and the AMF must
trigger an initial
context setup
procedure towards the
gNodeB. If this
parameter is set to
false, the UE Context
Request IE is not
carried in the INITIAL
UE MESSAGE message,
and the AMF
determines whether to
trigger this procedure
for all NAS procedures
in accordance with the
operator’s
configuration when
there are only signaling
connections.

4 NgAp.def Default flag False Managed Element/gNB CU-CP function To use the current
aultFlag configuration/EPNgC/NG AP NGAP as the default
NGAP, set this
parameter to True;
otherwise, set it to
False.

Figure 24 Configuring the SCTP Parameter1

28 - 74
 Network Slicing Management

Figure 25 Configuring the SCTP Parameter2

Figure 26 Configuring the Ngap Parameter1

Figure 27 Configuring the Ngap Parameter2

29 - 74
 Network Slicing Management

Figure 28 Configuring the NetworkSliceSubnet Parameter1

Figure 29 Configuring the NetworkSliceSubnet Parameter2

Figure 30 Configuring the GlobalSwitchInformation Parameter

30 - 74
 Network Slicing Management

5.4.1.4 Feature Deactivation

This feature is a basic feature and cannot be disabled.

5.4.1.5 Test Method

Table 29 AMF Selection and Re-allocation Test Method

Test Item AMF Re-allocation due to Network Slice(s) Support

Sub-Item N/A

Prerequisites The cell is established properly and in service.

Make a UE access the network with slice thai is not configured within the initial AMF.

test Steps The initial AMF redirect the UE context to another AMF support the slice.
There are 3 different way to redirect the UE context:
1) Base on InitialContextSetupRequest.
AMF Configured with: SET AMFREALLOCATIONMODE:AMFREALLOCATIONMODE="NASFROWARDING"
NSSF Configured with: SET TARGETAMFCONFIG:TARGETAMFFLAG=1,CANDIDATEAMFFLAG=1
gNB Configured with: SET UEContextReqEnable=1
2) Base on DownlinkNASTransport.
AMF Configured with: SET AMFREALLOCATIONMODE:AMFREALLOCATIONMODE="NASFROWARDING"
NSSF Configured with: SET TARGETAMFCONFIG:TARGETAMFFLAG=1,CANDIDATEAMFFLAG=1
gNB Configured with: SET UEContextReqEnable=0
3) Base on Reroute Nas Transport.
AMF Configured with: SET AMFREALLOCATIONMODE:AMFREALLOCATIONMODE="VIARAN"

Expected Result UE access the network successfully.

5.4.1.6 Provisioning Observation

Creating an Observation Task

Figure 31 result1

31 - 74
 Network Slicing Management

Figure 32 result2

Figure 33 result3

Figure 34 result4

32 - 74
 Network Slicing Management

5.4.2 Slice Awareness Provisioning Guidance

5.4.2.1 Prerequisites

Table 30 Hardware Requirement

Device Description Remark

5GC/EPC 5GC None

BBU V9200 None

AAU/RRU/Qcell No spectial requirement on RRU None

Table 31 Other Requirement

Other Requirement Description

CN CN should support multi-PLMN.

Carrier frequency bands, frequencies, and bandwidths None

UE None

Transmission bandwidth None

FTP server None

5.4.2.2 Restrictions

Support FR1 only, and FR2 is not supported

5.4.2.3 Feature Activation

5.4.2.3.1 Feature Activation Process

After a base station is commissioned successfully, basic NSSI parameters need to be configured on the base station side for the access of UEs
with slices. For the detailed slice management policy, refer to the related documents in the test method.

Table 32 Slice Awareness Process and Related Parameter

No. Step Related Parameter Verification

33 - 74
 Network Slicing Management

1 Add a record in network slice configuration in DU NetworkSliceSubnet.nssiId None

NetworkSliceSubnet.administrativeState
NetworkSliceSubnet.operationalState

2 Add a record in network slice configuration in DU SliceProfile.coverageAreaTAList None

SliceProfile.pLMNIdList

3 Add a record in network slice configuration in DU NSSAI.sst None

NSSAI.sd

5.4.2.3.2 Related Parameters and Figures

When the UE accesses the network, only the NetworkSliceSubnet node and its subordinate nodes need to be configured.

Table 33 Slice Awareness Activation

No. Paramete Parameter N Configurati Parameter Path Configuration

r ID ame on Exampl Principle
e

1 NSSAI.sst Slice service 1 Managed Element/gNB DU function configuration/Network Slice Subnet This
type Configuration/Slice Profile Configuration/NSSAI List Configuration; parameter is
Managed Element/gNB DU function configuration/Cell DU/QoSMap configured in
configuration parameters/MLCP configuration for SA/GBR-based MLCP accordance
configuration for SA/NSSAI List Configuration; Managed Element/gNB with the
DU function configuration/Cell DU/QoSMap configuration actual
parameters/MLCP configuration for SA/NGBR-based MLCP configuration operator
for SA/NSSAI List Configuration; Managed Element/gNB DU function requirements.
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/MLCP configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function configuration/Cell
DU/QoSMap configuration parameters/LCG configuration for SA/LCG
configuration for SA/NSSAI List Configuration; Managed Element/gNB
DU function configuration/Cell DU/QoSMap configuration
parameters/5QI-based QoS weight factor configuration for SA/5QI-
based QoS weight factor/NSSAI List Configuration; Managed
Element/gNB DU function configuration/Cell DU/QoSMap configuration
parameters/The configures of SaDelayGuaranteeConfig/NSSAI List
Configuration

2 NSSAI.sd Slice 1118481 Managed Element/gNB DU function configuration/Network Slice Subnet This
differentiator Configuration/Slice Profile Configuration/NSSAI List Configuration; parameter is
Managed Element/gNB DU function configuration/Cell DU/QoSMap configured in
configuration parameters/MLCP configuration for SA/GBR-based MLCP accordance
configuration for SA/NSSAI List Configuration; Managed Element/gNB with the
DU function configuration/Cell DU/QoSMap configuration actual
parameters/MLCP configuration for SA/NGBR-based MLCP configuration operator
for SA/NSSAI List Configuration; Managed Element/gNB DU function requirements.
configuration/Cell DU/QoSMap configuration parameters/MLCP
configuration for SA/MLCP configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function configuration/Cell
DU/QoSMap configuration parameters/LCG configuration for SA/LCG
configuration for SA/NSSAI List Configuration; Managed Element/gNB
DU function configuration/Cell DU/QoSMap configuration
parameters/5QI-based QoS weight factor configuration for SA/5QI-
based QoS weight factor/NSSAI List Configuration; Managed
Element/gNB DU function configuration/Cell DU/QoSMap configuration
parameters/The configures of SaDelayGuaranteeConfig/NSSAI List
Configuration

34 - 74
 Network Slicing Management

3 NgAp.def Default flag default Managed Element/gNB CU-CP function configuration/EPNgC/NG AP To use the
aultFlag current NGAP
as the default
NGAP, set this
parameter to
True;
otherwise, set
it to False.

4 Sctp.local Local port 36412 Managed Element/Transport Network/SCTP Set this

Port number parameter as
planned.

5 Sctp.rem Remote port 36412 Managed Element/Transport Network/SCTP Set this

otePort number parameter as
planned.

6 Sctp.rem Remote IP 131.82.47.1 Managed Element/Transport Network/SCTP Null

oteIp address

7 Sctp.radi Radio mode NR[8192] Managed Element/Transport Network/SCTP Set this

oMode parameter as
planned.

8 NgAp.sct Init SCTP MO 2 Managed Element/gNB CU-CP function configuration/EPNgC/NG AP This

pInfo ID parameter
should be set
as planned.
This
parameter
cannot be
modified.

1. NSSAI configuration
Enter the MO editing interface of UME，Click 【ManagedElement->GNBDUFunction->NetworkSliceSubnet->SliceProfile->NSSAI】

Figure 35 NSSAI configuration

2. Sctp configuration
Enter the MO editing interface of UME，Click 【ManagedElement->TransportNetwork->Sctp】

Figure 36 SCTP--1

35 - 74
 Network Slicing Management

Figure 37 SCTP--2

3. NgAp configuration
Enter the MO editing interface of UME，Click 【ManagedElement->GNBCUCPFunction->EPNgC->NgAp】

Figure 38 Ngap

36 - 74
 Network Slicing Management

5.4.2.4 Feature Deactivation

When [Locked] is deactivated or the operation status is Disabled, the slice is unavailable.

5.4.2.4.1 Feature Deactivation Process

Table 34 Slice Awareness Configuration Process and Related Parameter

No. Step Related Parameter Verification

1 Modify the NetworkSliceSubnet record in network slice configuration in NetworkSliceSubnet.administrativeStat None

DU e
NetworkSliceSubnet.operationalState

5.4.2.4.2 Feature Deactivation Process Related Parameter and Figure

Table 35 Slice Awareness Feature Deactivation

No. Parameter ID Parameter Na Configuration Exa Parameter Path

me mple

1 NetworkSliceSubnet.operatio Operational Disabled[Disabled] Managed Element/gNB DU function configuration/Network

nalState state Slice Subnet Configuration

2 NetworkSliceSubnet.adminis Administrative Locked[Locked] Managed Element/gNB DU function configuration/Network

trativeState state Slice Subnet Configuration

Figure 39 Feature Deactivation-NetworkSliceSubnet

5.4.2.5 Test Method

After the RAN-aware network slice information is configured, AMFs can be selected for UEs in the following four scenarios:
Observe signaling messages to check the corresponding scenario.

37 - 74
 Network Slicing Management

Scenario 1: If the UE carries a valid 5G-S-TMSI, select an AMF based on the 5G-S-TMSI.

Table 36 Slice Awareness Test Method 1

Test Item Slice Awareness

Sub-Item select an AMF based on the 5G-S-TMSI

Prerequisites Slice parameters are configured on the gNodeB, and the cell can be connected properly.

test Steps 1. Connect the UE and set the rrcStateFuncCfg parameter to 1 (idle function).
2. Exit the idle state through the ping packet, and view the RRCSetupComplete message.

Expected Result At the BTS side, view the INITIAL UE MESSAGE to view the routing information, and select AMF based on 5G-S-TMSI.

Figure 40 Scenario 1: RRCSetupComplete message

Figure 41 Scenario 1: INITIAL UE MESSAGE message

Scenario 2: If the UE carries a valid RegisteredAMF, select an AMF based on the RegisteredAMF.
Table 37 Slice Awareness Test Method 2

Test Item Slice Awareness

Sub-Item select an AMF based on the RegisteredAMF

Prerequisites Slice parameters are configured on the gNodeB, and the cell can be connected properly.

test Steps 1 Configure two NG associations corresponding to two AMFs. Allocate a number to the UE on one AMF, and set it to the
default association.

2. Configure access without slicing at the UE side, and view the RRCSetupComplete message.

Expected The AMF registered by the terminal is the same as the AMF indicated by the RegisteredAMF field in the MSG5. After the access,
Result the service is normal (you can determine which core network to access through the initial context request message).

Figure 42 Scenario :2: RRCSetupComplete message

38 - 74
 Network Slicing Management

Figure 43 Scenario 2: INITIAL CONTEXT SETUP REQUEST message

Scenario 3: If the UE carries a valid NSSAI, the AMF is selected based on the NSSAI.

Table 38 Slice Awareness Test Method 3

Test Item Slice Awareness

Sub-Item select an AMF based on the NSSAI

Prerequisites Slice parameters are configured on the gNodeB, and the cell can be connected properly.

test Steps 1. Connect the UE

2. View the RRCSetupComplete message

Expected Result After the access, the service is normal

Figure 44 Scenario 3: RRCSetupComplete message

Scenario 4: If the UE does not carry 5G-S-TMSI and NSSAI, select the default AMF.

Table 39 Slice Awareness Test Method 4

39 - 74
 Network Slicing Management

Test Item Slice Awareness

Sub-Item select the default AMF

Prerequisites Slice parameters are configured on the gNodeB, and the cell can be connected properly.

test Steps 1. Configure two NG associations corresponding to two AMFs. Allocate numbers for terminals on one AMF.
2. Access without slice on the UE side
3. View the RRCSetupComplete message

Expected Result The AMF accessed by the UE is the same as the AMF to which a number is allocated.

Figure 45 Scenario 4:RRCSetupComplete message

Scenario 5: Network slicing dscp test method:

Table 40 Slice Awareness Test Method 5

Test Item Slice Awareness

Sub-Item Network slicing dscp test

Prerequisites Configure the dscp information of the gNodeB .

test Steps 1. The UE accesses the network, and performs the ping packet or uplink packet injection service..
2.To capture the packets at the gNodeB uplink egress, input esw_mirror_set 0, 10 and 4 in the HWM process,
then enable packet capturing at gNodeB side by wireshark, and filter the gtp packets.

Expected Result The dscp configured for the gNodeB is consistent with that of the captured packet.

Figure 46 Scenario 5:Dscp packet capture

5.4.2.6 Provisioning Observation

Refer to 5.4.2.5 Test Method.

6 RAN Slice SLA Guarantee

6.1 Principle

SLA guarantee is end-to-end guarantee from the core network to the transmission network and then to the RAN. The RAN SLA includes the
following aspects:

40 - 74
 Network Slicing Management

a. Radio Coverage
b. User capacity and the number of online users
c. Peak rate, average rate, guaranteed rate, and bandwidth
d. End-to-end latency, QoS guarantee, and disaster tolerance mode
e. Security level (isolation mode) and slice type (eMBB/uRLLC/mMTC)
f. Time to recovery, whether existing slices are used, and KPI monitoring and statistics requirements.
Currently, the RAN provides guarantee of slice rate and air-interface bandwidth (PRB), and other SLA indicators will be considered later. Rate
guarantee and PRB guarantee cannot coexist, and PRB guarantee takes precedence. When the PlmnGroupList.sliceGuarRBSwit parameter is
set to enabled, the slice PRB guarantee function is enabled and the rate guarantee function is invalidated.

6.1.1 Slice Rate Guarantee

Slice rate guarantee is implemented in the uplink direction and downlink direction respectively. The guaranteed slice rate and the maximum
slice rate are configured by the following parameters: NetworkSliceInfoDU.guarRateDl, NetworkSliceInfoDU.guarRateUl,
NetworkSliceInfoDU.maxRateDl, and NetworkSliceInfoDU.maxRateUl. The four rates are maintained through the flow control window. The
flow control window length is configured by the NetworkSliceInfoDU.rateWinDura parameter.The guaranteed rate is used to improve the
scheduling priority of the services on a slice. If the guaranteed rate of a slice in the flow control window does not meet the requirement, the
services on the slice will be preferentially scheduled. The maximum rate is used to limit the maximum number of resources allocated for the
services on a slice. If the maximum rate of a slice is reached in the flow control window, the services on the slice will not be scheduled.

6.1.2 Slice Group PRB Guarantee

The protocol specifies that the physical resources (PRBs) of the cell are split in the form of Slice Group. A slice can belong to a Slice Group, and
the slices in the Slice Group share the physical resources. Carrier PRB resources can be isolated through slice groups. In each slice group,
resources can be divided into three types: Dedicated resources, preferential resources, and shared resources. For its structure, see Figure 47
and the resource category description, see Table 41.
Figure 47 Structure of Slice Group Resource Categories

Table 41 Resource Category Description

Resource Category Description

Dedicated Resources This part of resources is only dedicated to the slice group that the UE belongs to, and cannot be shared by other
slice groups. It is indicated by "rRMPolicyDedicatedRatio".

Prioritized Resources The resources are preferentially used by the slice group that the UE belongs to. If the resources are not used, the
resources can be used by other slice groups, and is represented by "rRMPolicyMinRatio - rRMPolicyDedicatedRatio".

Shared Resources This part of resources is shared with other slice groups, which are not guaranteed to be used by the slice groups. It is
represented by "rRMPolicyMaxRatio - rRMPolicyMinRatio".

Figure 47 It can be learnt that a slice group contains the following parameters: rRMPolicyDedicatedRatio, rRMPolicyMinRatio, and
rRMPolicyMaxRatio:

■ "rRMPolicyDedicatedRatio" defines the dedicated resource quota (percentage) that can be used by the slice group. The total "dedicated

ratio of radio resource management policy" between multiple slice groups in the same carrier should be less than or equal to 100%.

41 - 74
 Network Slicing Management

■ "rRMPolicyMinRatio " defines the minimum resource quota (percentage) available to the slice group, including at least one of the

priority resource and dedicated resource. The sum of "minimum proportion of radio resource management policies" between multiple
slice groups in the same carrier should be less than or equal to 100%.
■ "rRMPolicyMaxRatio " defines the maximum resource quota (percentage) that can be used by the slice group. It includes at least one of

the shared resources, priority resources and dedicated resources. In addition, the "Maximum Proportion of Radio Resource Management
Policy" between multiple slice groups in the same carrier can exceed 100%.

Based on the above principles, the service is guaranteed. This function uses (UserGroupRrmPolicy) as the user group radio resource
management policy to indicate the slice group and controls it through the PlmnGroupList.sliceGuarRBSwit switch. Services that need to be
guaranteed do not need to be guaranteed at any time. For services that need to be guaranteed during the day, they need to be guaranteed at
night, or they need to be guaranteed during the day and at night. However, the requirements for guarantee resources are different. In order to
guarantee services reasonably and improve resource utilization, slice groups are divided into two types: Calendar slice groups and non-
calendar slice groups, which are distinguished through the parameter UserGroupRrmPolicy.refNetworkSliceCalendar. The meanings of the two
types and the identification criteria are shown in Table 42.
Table 42 Slice Group Type

Slice Group Type Identification Criteria Description

Non-calendar slice No parameter UserGroupRrmPolicy.refNetworkSlic The dedicated ratio of radio resource management policies,
group eCalendar is configured in (UserGroupRrmPolicy). minimum ratio of radio resource management policies, and
maximum ratio of radio resource management policies
configured in the slice group are enabled at each moment.

Calendar slice group In the user group radio resource management Parameters in the calendar, including Dedicated Ratio of Radio
policy (UserGroupRrmPolicy), the UserGroupRrmPo Resource Management Policy, Minimum Ratio of Radio
licy.refNetworkSliceCalendar parameter is Resource Management Policy, and Maximum Ratio of Radio
configured. Resource Management Policy, based on the month, week, and
time.

The parameters in a slice group are processed in uplink and downlink respectively. For the relationships between slice group types and
protocol parameters, refer to Table 43.
Table 43 Mapping Between Slice Group Protocol Parameters and Implementation Parameters

Parameter Type Non-calendar slice group Calendar slice group Remarks

rRMPolicyDedicatedRatio DL dedicated resource ratio(UserGroupRrm DL dedicated resource ratio(NetworkSliceCalen The calendar

Policy.dlDedicatedRatio) dar.dlDedicatedRatio) slice group
UL dedicated resource ratio(UserGroupRrm UL dedicated resource ratio(NetworkSliceCalen parameters
dar.ulDedicatedRatio)
Policy.ulDedicatedRatio) come from the
network slice
rRMPolicyMinRatio DL minimum resource ratio(UserGroupRrm DL minimum resource ratio(NetworkSliceCalen
calendar (Net
Policy.dlMinRatio) dar.dlMinRatio)
workSliceCale
UL minimum resource ratio(UserGroupRrm UL minimum resource ratio(NetworkSliceCalen
Policy.ulMinRatio) dar.ulMinRatio) ndar)
referenced by
rRMPolicyMaxRatio DL maximum resource ratio(UserGroupRrm DL maximum resource ratio(NetworkSliceCalen the user group
Policy.dlMaxRatio) dar.dlMaxRatio)
radio resource
UL maximum resource ratio(UserGroupRrm UL maximum resource ratio(NetworkSliceCalen
management
Policy.ulMaxRatio) dar.ulMaxRatio)
policy (UserGr
oupRrmPolicy)
configured
parameter Use
rGroupRrmPol
icy.refNetwork
SliceCalendar.

Note that only when NetworkSliceCalendar.repeatPeriod is set to "Weekly" and NetworkSliceCalendar.weeklyDate and
NetworkSliceCalendar.guaranteeTime are valid configuration time or when NetworkSliceCalendar.repeatPeriod is set to "Monthly" and
NetworkSliceCalendar.monthlyDate and NetworkSliceCalendar.guaranteeTime are valid configuration time, the following parameters are

42 - 74
 Network Slicing Management

enabled: "Dedicated ratio of radio resource management policy," "Minimum ratio of radio resource management policy" and "Maximum ratio
of radio resource management policy." In other invalid periods, the "Ratio of dedicated radio resource management policies," "Ratio of
minimum radio resource management policies," and "Ratio of maximum radio resource management policies" of the slices and non-slices are
all disabled. In this case, slice guarantee users are as common users.
Slice group (Note: Unless otherwise specified, each slice group includes non-calendar slice group and calendar slice group) supports three
resource guarantee types: TtiWinCtrlNum, TtiCtrlNum, TtiFixedPos, which depend on the configuration of the parameter
UserGroupRrmPolicy.resourceGuarType. The detailed description is as follows:
TtiWinCtrlNum

■ When the UserGroupRrmPolicy.resourceGuarType parameter is set to 0, the resource guarantee type is TTI and the quantity controlled

by the resource window. It isolates resources by controlling the quantity of PRB resources.
■ The dedicated resources of the slice group are controlled at the TTI level, while the preferred and shared resources are controlled by the

resource window (the window length is configured by the parameter CarrierResourceAllocAdap.prbWinDura).

■ The scheduling priorities of the resources included in "rRMPolicyMinRatio" are divided into absolute slice PRB resource guarantee

priority and slice PRB resource guarantee priority, depending on the configuration of the parameter PlmnGroupList.sliceGuarPriorSwitch.
When PlmnGroupList.sliceGuarPriorSwitch is set to true, the scheduling priority of the slice group within the "rRMPolicyMinRatio" is
absolute priority of slice PRB resource guarantee, and its scheduling priority is higher than the GBR and PBR service types of ordinary users
(non-slice group PRB guarantee users). When PlmnGroupList.sliceGuarPriorSwitch is set to false, the scheduling priority of the slice group
within the rRMPolicyMinRatio" is slice PRB resource guarantee priority, Its scheduling priority is lower than the GBR and PBR service types
of ordinary users, but higher than the MBR and AMBR service types of ordinary users. In addition, PlmnGroupList.sliceGuarPriorSwitch is
configured as false from true, or as true from false. It only activates the new BSR requests of the newly-accessed users, the new bearers of
the accessed users and the new bearers established by the accessed users.
■ The throughput statistics of the resources included in "rRMPolicyMinRatio" are related to the configuration of the parameter

EPFAlg.subSliceGrpPrioSwitch. When the EPFAlg.subSliceGrpPrioSwitch parameter is set to Open, when the scheduling PF or EPF
algorithm calculates the user priority through the historical throughput, it will subtract the scheduling throughput of the resources
included in the "rRMPolicyMinRatio" of the slice group. It is not counted in the historical throughput, but shared resources is counted in
the historical throughput. When the EPFAlg.subSliceGrpPrioSwitch parameter is set to Close, when the scheduling PF or EPF algorithm
calculates the user priority through the historical throughput, the scheduling throughput of the resources included in the
"rRMPolicyMaxRatio" of the slice group will be counted into the historical throughput.

TtiCtrlNum

■ When UserGroupRrmPolicy.resourceGuarType is set to 1, the resource guarantee type is TTI control quantity, which isolates resources

by controlling the quantity of PRBs.

■ The dedicated resources of a slice group are controlled at the TTI level, and there are no preferential resources or shared resources. The

dedicated ratio of radio resource management policies, minimum ratio of radio resource management policies, and maximum ratio of
radio resource management policies must be the same.
■ The scheduling priority included in "rRMPolicyMinRatio" is always slice PRB resource guarantee absolute priority, that is, the parameter

PlmnGroupList.sliceGuarPriorSwitch is always configured as true.

■ The number of users guaranteed by each slice group can be limited by the parameterUserGroupRrmPolicy.ttiGuarSelectedUeNum. In

the current TTI, the number of available users guaranteed by the slice group will be less than or equal to the configured value of parameter
UserGroupRrmPolicy.ttiGuarSelectedUeNum. The number of users guaranteed by other slice groups beyond the configured value of
parameter UserGroupRrmPolicy.ttiGuarSelectedUeNum will be selected in the next TTI based on the scheduling priority.
■ The number of PRBs allocated to specific services such as VONR, retransmission and SR is more flexible. You can configure whether to

limit the number of PRBs by setting the parameter UserGroupRrmPolicy.guarResLimitSwitch.

TtiFixedPos

■ When the UserGroupRrmPolicy.resourceGuarType parameter is set to 2, the resource guarantee type is fixed TTI location, which isolates

resources by controlling the number of PRBs and location.

■ The dedicated resources of a slice group are controlled at the TTI level, and there are no preferential resources or shared resources. The

43 - 74
 Network Slicing Management

dedicated ratio of radio resource management policies, minimum ratio of radio resource management policies, and maximum ratio of
radio resource management policies must be the same.
■ The dedicated resources of the slice group are the number of fixed locations, while the start location is specified by the

UserGroupRrmPolicy.ulDedicatedRbStartIdx\UserGroupRrmPolicy.dlDedicatedRbStartIdx parameter. During the location configuration,

you need to consider multiple BWPs and frequency selection configurations to avoid the problem manually.
■ The scheduling priority included in "rRMPolicyMinRatio" is always slice PRB resource guarantee absolute priority, that is, the parameter

PlmnGroupList.sliceGuarPriorSwitch is always configured as true.

■ The number of users guaranteed by each slice group can be limited by the parameterUserGroupRrmPolicy.ttiGuarSelectedUeNum. In

the current TTI, the number of available users guaranteed by the slice group will be less than or equal to the configured value of parameter
UserGroupRrmPolicy.ttiGuarSelectedUeNum. The number of users guaranteed by other slice groups beyond the configured value of
parameter UserGroupRrmPolicy.ttiGuarSelectedUeNum will be selected in the next TTI based on the scheduling priority.
■ The number of PRBs allocated to specific services such as VONR, retransmission and SR is more flexible. You can configure whether to

limit the number of PRBs by setting the parameter UserGroupRrmPolicy.guarResLimitSwitch.

6.2 Network Analysis

Note:

The feature activation effect depends on the network environment. Therefore, this document only guides the feature provisioning. For network
gains pertinent contents, refer to ZTE for support.

6.2.1 Benefit Analysis

■ This feature can provide SLA guarantee for network slices on the wireless side, and provide possibility for SLA guarantee for end-to-end

slices.
■ Rate guarantee can provide guaranteed rates for slice users and improve user experience.

■ With PRB guarantee, resources can be reserved for slice users to ensure that high-priority slice users have sufficient PRB resources, and

daily reporting can improve the utilization of guaranteed resources.

6.2.2 Impact Analysis

None.

6.3 Application Scenarios

This feature is applicable to all 5G SA network scenarios.

6.4 Provisioning Guidance

6.4.1 Slice SLA Guarantee Provisioning Guidanc

6.4.1.1 Prerequisites

Table 44 Hardware Requirement

Device Description Remark

5GC/EPC 5GC 1

BBU V9200 1

AAU/RRU/Qcell No spectial requirement on RRU 1

Table 45 Other Requirement

Other Requirement Description

44 - 74
 Network Slicing Management

CN Slicing needs to be supported

Carrier frequency bands, frequencies, and bandwidths None

UE Slicing needs to be supported

Transmission bandwidth None

FTP server None

6.4.1.2 Restrictions

Support FR1 only, and FR2 is not supported

6.4.1.3 Feature Activation

Allocate resources to network slices in accordance with the PRB guarantee policy or rate through the PRB resource guarantee function switch.
If there is a specific scenario, you need to configure slice-related parameters in accordance with the specific scenario.
The basic NSSI parameters are configured when the base station is commissioned. After the base station is successfully commissioned, the
slice whitelist parameters SlicePmWhitelist.plmn, SlicePmWhitelist.sst and SlicePmWhitelist.sd are configured by default, and then the
UserGroupRrmPolicy, UserGroupSliceList and NetworkSliceInfoDU are generated.

Table 46 Slice SLA Guarantee Feature Activation

No. Paramete Parameter N Configuration Example Parameter Path

r ID ame

1 Network Slice-level DL 10000 Managed Element/gNB DU function

SliceInfo guaranteed configuration/Cell DU/User-group radio resource
DU.guarR rate management policy/The configures of
ateDl
UserGroupSliceList/NetworkSliceInfoDU List
Configuration

2 Network Slice-level UL 10000 Managed Element/gNB DU function

SliceInfo guaranteed configuration/Cell DU/User-group radio resource
DU.guarR rate management policy/The configures of
ateUl
UserGroupSliceList/NetworkSliceInfoDU List
Configuration

3 Network Maximum 40000 Managed Element/gNB DU function

SliceInfo slice-level DL configuration/Cell DU/User-group radio resource
DU.maxR rate management policy/The configures of
ateDl
UserGroupSliceList/NetworkSliceInfoDU List
Configuration

45 - 74
 Network Slicing Management

4 Network Maximum 40000 Managed Element/gNB DU function

SliceInfo slice-level UL configuration/Cell DU/User-group radio resource
DU.maxR rate management policy/The configures of
ateUl
UserGroupSliceList/NetworkSliceInfoDU List
Configuration

5 Network Slice-level 10 Managed Element/gNB DU function

SliceInfo flow control configuration/Cell DU/User-group radio resource
DU.rateW window management policy/The configures of
inDura
length UserGroupSliceList/NetworkSliceInfoDU List
Configuration

6 UserGrou DL dedicated Non-calendar slice group: 20 Managed Element/gNB DU function

pRrmPoli resource Calendar slice group: 0 configuration/Cell DU/User-group radio resource
cy.dlDedi ratio management policy
catedRati
o

46 - 74
 Network Slicing Management

7 UserGrou DL minimum Non-calendar slice group: 20 Managed Element/gNB DU function

pRrmPoli resource Calendar slice group: 0 configuration/Cell DU/User-group radio resource
cy.dlMinR ratio management policy
atio

8 UserGrou DL maximum Non-calendar slice group: 20 Managed Element/gNB DU function

pRrmPoli resource Calendar slice group: 100 configuration/Cell DU/User-group radio resource
cy.dlMax ratio management policy
Ratio

47 - 74
 Network Slicing Management

9 UserGrou UL dedicated Non-calendar slice group: 20 Managed Element/gNB DU function

pRrmPoli resource Calendar slice group: 0 configuration/Cell DU/User-group radio resource
cy.ulDedi ratio management policy
catedRati
o

10 UserGrou UL minimum Non-calendar slice group: 20 Managed Element/gNB DU function

pRrmPoli resource Calendar slice group: 0 configuration/Cell DU/User-group radio resource
cy.ulMinR ratio management policy
atio

48 - 74
 Network Slicing Management

11 UserGrou UL maximum Non-calendar slice group: 20 Managed Element/gNB DU function

pRrmPoli resource Calendar slice group: 0 configuration/Cell DU/User-group radio resource
cy.ulMax ratio management policy
Ratio

12 PlmnGro Switch of Slice rate guarantee: false Managed Element/gNB DU function

upList.sli guaranteeing Slice group PRB guarantee: true configuration/Cell DU/PLMN group configuration
ceGuarPr the absolute
iorSwitch
priority of
network slice
PRB
resources

49 - 74
 Network Slicing Management

13 EPFAlg.s Subtracting Open Managed Element/gNB DU function

ubSliceGr the traffic of configuration/Cell DU/EPF Algorithm
pPrioSwit prioritized
ch
slice group
resources
based on
EPF

14 PlmnGro Switch of the Slice rate guarantee: false Managed Element/gNB DU function
upList.sli network slice Slice group PRB guarantee: true configuration/Cell DU/PLMN group configuration
ceGuarR PRB
BSwit
guarantee
function

15 NSSAI.sst Slice service 1 Managed Element/gNB DU function

type configuration/Network Slice Subnet
Configuration/Slice Profile Configuration/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/MLCP configuration for SA/GBR-based
MLCP configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/MLCP configuration for SA/NGBR-
based MLCP configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/MLCP configuration for SA/MLCP
configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/LCG configuration for SA/LCG
configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/5QI-based QoS weight factor
configuration for SA/5QI-based QoS weight
factor/NSSAI List Configuration; Managed
Element/gNB DU function configuration/Cell
DU/QoSMap configuration parameters/The
configures of SaDelayGuaranteeConfig/NSSAI List
Configuration

50 - 74
 Network Slicing Management

16 NSSAI.sd Slice 1118481 Managed Element/gNB DU function

differentiator configuration/Network Slice Subnet
Configuration/Slice Profile Configuration/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/MLCP configuration for SA/GBR-based
MLCP configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/MLCP configuration for SA/NGBR-
based MLCP configuration for SA/NSSAI List
Configuration; Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/MLCP configuration for SA/MLCP
configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/LCG configuration for SA/LCG
configuration for SA/NSSAI List Configuration;
Managed Element/gNB DU function
configuration/Cell DU/QoSMap configuration
parameters/5QI-based QoS weight factor
configuration for SA/5QI-based QoS weight
factor/NSSAI List Configuration; Managed
Element/gNB DU function configuration/Cell
DU/QoSMap configuration parameters/The
configures of SaDelayGuaranteeConfig/NSSAI List
Configuration

17 UserGrou PLMN ID 460-01 Managed Element/gNB DU function

pSliceList configuration/Cell DU/User-group radio resource
.plmnId management policy/The configures of
UserGroupSliceList

18 Network Slice service 1 Managed Element/gNB DU function

SliceInfo type configuration/Cell DU/User-group radio resource
DU.sst management policy/The configures of
UserGroupSliceList/NetworkSliceInfoDU List
Configuration

19 Network Slice service 1118481 Managed Element/gNB DU function

SliceInfo type configuration/Cell DU/User-group radio resource
DU.sst management policy/The configures of
UserGroupSliceList/NetworkSliceInfoDU List
Configuration

51 - 74
 Network Slicing Management

20 CarrierRe PRB 50 Managed

sourceAll scheduling Element/NRRadioInfrastructure/NRCarrier/Adaptive
ocAdap.p window carrier resource allocation
rbWinDur
length for
a
network
sharing and
slice groups

52 - 74
 Network Slicing Management

21 UserGrou Resource 0 Managed Element/gNB DU function

pRrmPoli guarantee configuration/Cell DU/User-group radio resource
cy.resour type management policy
ceGuarTy
pe

53 - 74
 Network Slicing Management

22 UserGrou Restriction 0;0;0;0 Managed Element/gNB DU function

pRrmPoli on configuration/Cell DU/User-group radio resource
cy.guarRe guaranteed management policy
sLimitSwi
resources
tch

23 UserGrou Index of DL null Managed Element/gNB DU function

pRrmPoli start RB configuration/Cell DU/User-group radio resource
cy.dlDedi allocated to management policy
catedRbS
user group
tartIdx

54 - 74
 Network Slicing Management

24 UserGrou Index of UL null Managed Element/gNB DU function

pRrmPoli start RB configuration/Cell DU/User-group radio resource
cy.ulDedi allocated to management policy
catedRbS
user group
tartIdx

25 UserGrou Index of the Non-calendar slice group: null Managed Element/gNB DU function
pRrmPoli network slice Calendar slice group: GNBDUFunction=460- configuration/Cell DU/User-group radio resource
cy.refNet calendar 01_511184,NetworkSliceCalendar=1 management policy
workSlice
configuration
Calendar

26 Network Period weekly Managed Element/gNB DU function

SliceCale configuration/Network Slicing Calendar
ndar.repe
atPeriod

55 - 74
 Network Slicing Management

27 Network Monthly date 1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0 Managed Element/gNB DU function

SliceCale configuration/Network Slicing Calendar
ndar.mon
thlyDate

28 Network Weekly date 1;0;0;0;0;0;0 Managed Element/gNB DU function

SliceCale configuration/Network Slicing Calendar
ndar.wee
klyDate

29 Network Guarantee 1;1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0; Managed Element/gNB DU function

SliceCale time 0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0; configuration/Network Slicing Calendar
ndar.guar 0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
anteeTim
e

56 - 74
 Network Slicing Management

30 Network DL dedicated 30 Managed Element/gNB DU function

SliceCale resource configuration/Network Slicing Calendar
ndar.dlDe ratio
dicatedR
atio

31 Network DL minimum 40 Managed Element/gNB DU function

SliceCale resource configuration/Network Slicing Calendar
ndar.dlMi ratio
nRatio

57 - 74
 Network Slicing Management

32 Network DL maximum 70 Managed Element/gNB DU function

SliceCale resource configuration/Network Slicing Calendar
ndar.dlM ratio
axRatio

33 Network UL dedicated 30 Managed Element/gNB DU function

SliceCale resource configuration/Network Slicing Calendar
ndar.ulDe ratio
dicatedR
atio

58 - 74
 Network Slicing Management

34 Network UL minimum 40 Managed Element/gNB DU function

SliceCale resource configuration/Network Slicing Calendar
ndar.ulMi ratio
nRatio

35 Network UL maximum 70 Managed Element/gNB DU function

SliceCale resource configuration/Network Slicing Calendar
ndar.ulM ratio
axRatio

1. Slice rate guarantee configuration

59 - 74
 Network Slicing Management

step1) Enter the MO editing interface of UME，see [](4.4.1 Slice Management Provisioning Guide)
step2) Enter the MO editing interface of UME，Click 【ManagedElement->GNBDUFunction->NRCellDU→PlmnGroupList】

Figure 48 Slice rate guarantee

step3) Enter the MO editing interface of UME，Click【ManagedElement->GNBDUFunction-

>NRCellDU→UserGroupRrmPolicy→UserGroupSliceList→NetworkSliceInfoDU】

Figure 49 Slice rate guarantee

2. Slice group PRB guarantee configuration

2.1 Non-calendar slice group
2.1.1 Tti Window Control Number
step1) Enter the MO editing interface of UME，see [](4.4.1 Slice Management Provisioning Guide)
step2) Enter the MO editing interface of UME，Click 【ManagedElement->GNBDUFunction->NRCellDU→PlmnGroupList】
Figure 50 Slice group PRB guarantee

60 - 74
 Network Slicing Management

step3) Enter the MO editing interface of UME，Click 【ManagedElement->GNBDUFunction->NRCellDU→UserGroupRrmPolicy】

Figure 51 Slice group PRB guarantee

Figure 52 Slice group PRB guarantee

61 - 74
 Network Slicing Management

step4) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→UserGroupRrmPolicy】

Figure 53 resourceGuarType

step5) Enter the MO editing interface of UME, Click 【Managed Element->gNB DU function Configuration->Cell DU → User-group Radio
Resource Management Policy →UserGroupSliceList→NetworkSliceInfoDU】. The NetworkSliceInfoDU Configuration page is displayed.
Configure the slice service type and slice differentiator as required.
Figure 54 slice service type and slice differentiato configuration

62 - 74
 Network Slicing Management

step6) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→CarrierResourceAllocAdap】

（Note: If the "adaptive carrier resource allocation" node does not exist in the current version, it does not need to be configured. The slice
group PRB scheduling window length is configured by the parameter UserGroupRrmPolicy.prbWinDura.）

Figure 55 PRB scheduling window length configuration for slice groups

step7) To change the slice group scheduling priority, set the parameter "PlmnGroupList.sliceGuarPriorSwitch" to "true." To enter the MO
editing interface of UME, click "Managed Element ->gNB DU Function Configuration ->DU Cell Configuration →PlmnGroupList" to open the
"PlmnGroupList" configuration interface, and change sliceGuarPriorSwitch to "true."
English path: [ManagedElement->GNBDUFunction->NRCellDU →PlmnGroupList]

Figure 56 Slice group PRB guarantee

63 - 74
 Network Slicing Management

step8) To exclude the Dedicated and Prioritized resources of the slice group from the scheduling PF or EPF algorithm as the historical
throughput, set the parameter EPFAlg.subSliceGrpPrioSwitch to true. To enter the MO editing interface of UME, click Management NE ->gNB
DU Function Configuration ->DU Cell Configuration →EPFAlg to open the "EPFAlg" interface, and set subSliceGrpPrioSwitch to true.
English path: [ManagedElement->GNBDUFunction->NRCellDU →EPFAlg]

Figure 57 Slice group PRB guarantee

2.1.2 Tti Control Number

step1) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→UserGroupRrmPolicy】.Other
steps are the same as those described in the "TTI Window Control Number" provisioning guide.

Figure 58 resourceGuarType

64 - 74
 Network Slicing Management

2.2 Calendar slice group

2.2.1 Tti Window Control Number

step1) Refer to 2.1.1 to complete the configuration of non-calendar slice group TTI and resource window control quantity.
step2) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→UserGroupRrmPolicy】, open
the "UserGroupRrmPolicy" configuration interface

Figure 59 Resource Assurance Proportion Configuration

step3) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→NetworkSliceCalendar】, open

the "NetworkSliceCalendar" configuration interface,
If this parameter is set to Weekly, set the week date, guaranteed time, and UL/DL resource ratio, seeFigure 60. If this parameter is set to
Monthly, set the month date, guaranteed time, and UL/DL resource ratio, see Figure 61.

65 - 74
 Network Slicing Management

Figure 60 Slice Calendar Configuration ‒ Weekly Date

Figure 61 Slice Calendar Configuration ‒ Month Date

step4) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→NetworkSliceCalendar】, open

the "NetworkSliceCalendar" configuration interface,Configuring the Resource Proportion.

Figure 62 Resource Proportion Configuration

66 - 74
 Network Slicing Management

step5) Enter the MO editing interface of UME，Click 【ManagedElement->NRRadioInfrastructure->NRCarrier→UserGroupRrmPolicy】, open

the "UserGroupRrmPolicy" configuration interface,
Configure the index of the network slice calendar.

Figure 63 Index of the Network Slicing Calendar Configuration

2.2.2 Tti Control Number

step1) Refer to 6.4.1.3 Feature Activation in 2.1.2 to completes the configuration of the number of TTIs of non-calendar slice groups.
step2) Refer to 6.4.1.3 Feature Activation in 2.1.2 completes the configuration of the calendar slice group.

67 - 74
 Network Slicing Management

2.2.3 Tti Fixed Position

step1) Refer to 6.4.1.3 Feature Activation in 2.1.2 to completes the configuration of the number of TTIs of non-calendar slice groups.
step2) Refer to 6.4.1.3 Feature Activation in 2.1.3 completes the configuration of the calendar slice group.

6.4.1.4 Feature Deactivation

After the parameter PlmnGroupList.sliceGuarRBSwit is enabled, the PRB guarantee function of the slice is enabled, and the rate guarantee
function no longer takes effect at this time.

Table 47 Slice SLA Guarantee Feature Deactivation

No. Parameter ID Parameter Name Configuration Parameter Path

Example

1 PlmnGroupList.slice Switch of the network slice PRB true Managed Element/gNB DU function configuration/Cell
GuarRBSwit guarantee function DU/PLMN group configuration

Figure 64 Slice SLA Guarantee Feature Deactivation

6.4.1.5 Test Method

Table 48 Slice SLA Guarantee Test Method

Test Item Slice SLA Guarantee

Sub-Item N/A

Prerequisites The cell is established properly and in service.

test Steps 1. Configure the slice rate feature.

2. Make a UE access the network, establish GBR (GBR: 60 M, MBR: 180 M) and NGBR bearers respectively, and associate them
with configured slices.
3. Uplink and downlink TCP packets are sent at full load.

Expected 1. The KPI can correctly display the number and usage of RBs occupied by each UL/DL slice.
Result

Table 49 Slice PRB Guarantee Feature Test Method

Test Item Slice PRB Guarantee Feature

Sub-Item Slice absolute priority switch from off to on, downlink slice resource allocation (NGBR bearer) test

68 - 74
 Network Slicing Management

Prerequisites UserGroupRrmPolicy.dlMaxRatio=100.
UserGroupRrmPolicy.dlMinRatio=100.
UserGroupRrmPolicy.dlDedicatedRatio=10.
PlmnGroupList.sliceGuarRBSwit=true.
Downlink PBR rate: 5QI4: Extreme traffic, 5QI3: 20 M
Downlink AMBR rate: 5QI4: Extreme traffic, 5QI3: 50 M

test Steps 1. Set up the cell according to the input configuration and configure a slice group. After the UE1 is connected at the near
point, perform the downlink full-traffic service on the NGBR (5QI9) bearer that belongs to the slice group. After the UE2 (non-
slice user) is connected at the near point, perform the downlink full-traffic service on the NGBR bearer (5QI8).
2. Change PlmnGroupList.sliceGuarPriorSwitch=true.
3: After accessing the near point of the new UE3, perform downlink full-traffic service on the 5QI4 (GBR) bearer that belongs to
this slice group. After accessing the near point of the UE4 (non-slice user), perform downlink full-traffic service on the 5QI3
bearer.

Expected 1. Check the downlink traffic of UE2 to ensure the PBR traffic of 20 M; the downlink resource occupied by UE1 is the remaining
Result traffic;
2. Check the downlink traffic of UE1, UE2 and UE4. Note: If a UE in the old slice enters the LCH queue, the slice priority of the
UE will also be increased. At this time, the downlink traffic of UE1 and UE3 is basically equal, and there is no downlink traffic
of UE2 and UE4.
Note: If the maximum continuous section is divided, the UE with a lower priority may have small traffic.

Table 50 Slice PRB Guarantee FeatureTest Method

Test Item Slice PRB Guarantee Feature

Sub-Item Slice absolute priority switch from off to on, uplink slice resource allocation (NGBR bearer) test

Prerequisites UserGroupRrmPolicy.ulMaxRatio=100
UserGroupRrmPolicy.ulMinRatio=100
UserGroupRrmPolicy.ulDedicatedRatio=10
PlmnGroupList.sliceGuarRBSwit=true
Uplink PBR rate: 5QI4: Extreme traffic, 5QI3: 20 M
Uplink AMBR rate: 5QI4: Extreme traffic, 5QI3: 50 M

test Steps 1. Set up the cell according to the input configuration and configure a slice group. After the UE1 is connected at the near
point, perform the uplink full-traffic service on the NGBR (5QI9) bearer that belongs to the slice group. After the UE2 (non-slice
user) is connected at the near point, perform the uplink full-traffic service on the NGBR bearer (5QI8).
2. Change PlmnGroupList.sliceGuarPriorSwitch=true.
3. After accessing the near point of the new UE3, perform uplink full-traffic service on the 5QI4 (GBR) bearer that belongs to
this slice group. After accessing the near point of the UE4 (non-slice user), perform uplink full-traffic service on the 5QI3
bearer.

Expected 1. Check the uplink traffic of UE2 to ensure the PBR traffic of 20 M; the uplink resource occupied by UE1 is the remaining
Result traffic;
2. Check the uplink traffic of UE1, UE2 and UE4. Note: If a UE in the old slice enters the LCH queue, the slice priority of the UE
will also be increased. At this time, the uplink traffic of UE1 and UE3 is basically equal, and there is no uplink traffic of UE2 and
UE4.
Note: If the maximum continuous section is divided, the UE with a lower priority may have small traffic.

Table 51 TTI Control Quantity Test Method

Test Item TTI Control Quantity

Sub-Item TTI Control Quantity

Prerequisites UserGroupRrmPolicy.resourceGuarType=TtiCtrlNum
UserGroupRrmPolicy.ttiGuarSelectedUeNum=2
UserGroupRrmPolicy.guarResLimitSwitch=[0;0;0;0]
PlmnGroupList.sliceGuarRBSwit=1
PlmnGroupList.sliceGuarPriorSwitch=1
UserGroupRrmPolicy.dlDedicatedRatio=1%
UserGroupRrmPolicy.dlMinRatio=1%
UserGroupRrmPolicy.dlMaxRatio=1%
UserGroupRrmPolicy.ulDedicatedRatio=1%
UserGroupRrmPolicy.ulMinRatio=1%
UserGroupRrmPolicy.ulMaxRatio=1%

69 - 74
 Network Slicing Management

test Steps 1. UE1 is associated with slice group 1, and only the uplink and downlink of UE1 are filled with packets.
2. UE2 is not associated with slice group 1. Add UE2 uplink/downlink full packet filling.

Expected Result 1.
670063: UL PRB Utilization rate of a slice in NRCellDu(%)=1%
670064: DL PRB Utilization rate of a slice in NRCellDu(%)=1%
UE1 only schedules 3RB per slot in the uplink and downlink, and the number of uplink and downlink full-scheduling
packets.
2.
All indicators remain unchanged.

Table 52 Calendar-Type Slice Guarantee Test Method

Test Item Calendar slice guarantee test

Sub-Item Calendar slice guarantee test

Prerequisites UserGroupRrmPolicy.resourceGuarType=TtiWinCtrlNum
PlmnGroupList.sliceGuarRBSwit=true
PlmnGroupList.sliceGuarPriorSwitch=true
UserGroupRrmPolicy.ulDedicatedRatio=0
UserGroupRrmPolicy.ulMinRatio=0
UserGroupRrmPolicy.ulMaxRatio=100
UserGroupRrmPolicy.dlDedicatedRatio=0
UserGroupRrmPolicy.dlMinRatio=0
UserGroupRrmPolicy.dlMaxRatio=100
EPFAlg.subSliceGrpPrioSwitch=true
UserGroupRrmPolicy.refNetworkSliceCalendar=GNBDUFunction=460-01_511184,NetworkSliceCalendar=1
NetworkSliceCalendar.repeatPeriod=Weekly;
NetworkSliceCalendar.weeklyDate=1;0;0;0;0;0;0；NetworkSliceCalendar.guaranteeTime=1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;1；//凌晨0:00到0：15、中午11:45到12:15、半夜23:45到0:00；
NetworkSliceCalendar.dlDedicatedRatio=30
NetworkSliceCalendar.dlMinRatio=40
NetworkSliceCalendar.dlMaxRatio=80；
NetworkSliceCalendar.ulDedicatedRatio=30
NetworkSliceCalendar.ulMinRatio=40
NetworkSliceCalendar.ulMaxRatio=80

test Steps 1. Associate the UE1 with the slice group. Between 11:45 and 12:15 on Sunday at noon, perform the uplink/downlink full packet filling service by UE1 a
configuration flexibly according to the test time).

Expected 1.
Result 670063: UL PRB Utilization rate of a slice in NRCellDu(%)=80%
670064: DL PRB Utilization rate of a slice in NRCellDu(%)=80%

6.4.1.6 Provisioning Observation

Creating an Observation Task

Figure 65 result1

70 - 74
 Network Slicing Management

Figure 66 result2

Figure 67 Creating a Real-Time Slicing PRB KPI observation task

71 - 74
 Network Slicing Management

Figure 68 result3

Figure 69 result4

7 Related Counters, KPIs, and Alarms

7.1 Related Counters

Table 53 Counter List

No. Counter ID Counter Name FR1/FR2 FR1 TDD/FR1 FDD

1 C600960000 Average number of RRC connections in a cell slice FR1 FR1 TDD&FR1 FDD

2 C600960001 Number of PDU session setup requests in a cell slice FR1 FR1 TDD&FR1 FDD

3 C600960002 Number of PDU sessions successfully set up in a cell slice FR1 FR1 TDD&FR1 FDD

4 C600960003 Number of QoS flow setup requests in a cell slice FR1 FR1 TDD&FR1 FDD

5 C600960004 Number of QoS flows successfully set up in a cell slice FR1 FR1 TDD&FR1 FDD

72 - 74
 Network Slicing Management

No. Counter ID Counter Name FR1/FR2 FR1 TDD/FR1 FDD

6 C600960005 Number of gNodeB-triggered QoS flow releases in a cell slice FR1 FR1 TDD&FR1 FDD

7 C600960006 Number of gNodeB-triggered normal QoS flow releases in a cell slice FR1 FR1 TDD&FR1 FDD

8 C600960007 Number of initial QoS flow setup requests in the cell slice FR1 FR1 TDD&FR1 FDD

9 C600960008 Number of QoS flows successfully set up in the cell slice FR1 FR1 TDD&FR1 FDD

10 C600960011 Number of QoS flow modify requests in a cell slice FR1 FR1 TDD&FR1 FDD

11 C600960012 Number of QoS flows successfully modify in a cell slice FR1 FR1 TDD&FR1 FDD

12 C600960013 Average number of QoS flows in a cell slice FR1 FR1 TDD&FR1 FDD

13 C600960014 Maximum number of QoS flows in a cell slice FR1 FR1 TDD&FR1 FDD

14 C600960030 Maximum number of RRC connections in a cell slice FR1 FR1 TDD&FR1 FDD

15 C605270000 Cell Slice UL PDCP throughput FR1 FR1 TDD&FR1 FDD

16 C605270001 Volume of successfully sent DL PDCP packets by Cell Slice FR1 FR1 TDD&FR1 FDD

17 C605270002 Cell Slice DL PDCP SDU throughput FR1 FR1 TDD&FR1 FDD

18 C605270003 Cell Slice UL PDCP SDU throughput FR1 FR1 TDD&FR1 FDD

19 C605290000 DL CUUP delay of a cell slice FR1 FR1 TDD&FR1 FDD

20 C605290001 UL CUUP delay of a cell slice FR1 FR1 TDD&FR1 FDD

21 C605290002 Number of sent Cell Slice UL PDCP SDUs FR1 FR1 TDD&FR1 FDD

22 C605290003 Number of received Cell Slice DL PDCP SDUs FR1 FR1 TDD&FR1 FDD

23 C613620000 DL RLC SDU delay FR1&FR2 FR1 TDD&FR1 FDD

24 C613620002 UL RLC SDU delay FR1&FR2 FR1 TDD&FR1 FDD

25 C613630000 Number of sent UL Slice RLC SDUs FR1 FR1 TDD&FR1 FDD

26 C613630001 Number of received DL Slice RLC SDUs FR1 FR1 TDD&FR1 FDD

27 C613630002 Number of DL Slice RLC SDUs with successful HARQ response FR1 FR1 TDD&FR1 FDD

28 C613640000 Slice DL RLC Received volume FR1 FR1 TDD&FR1 FDD

29 C613640001 Slice UL RLC Received volume FR1 FR1 TDD&FR1 FDD

30 C613640003 Slice DL RLC SDU volume sent through Uu FR1 FR1 TDD&FR1 FDD

31 C613640004 Slice DL UE throughput data volume FR1 FR1 TDD&FR1 FDD

32 C613640005 Uplink UE throughput data volume of the slice FR1 FR1 TDD&FR1 FDD

33 C613650000 DL Slice RLC SDU delay FR1 FR1 TDD&FR1 FDD

34 C613650001 DL Slice HARQ Response delay FR1 FR1 TDD&FR1 FDD

35 C613650002 DL Slice IP packet delay FR1 FR1 TDD&FR1 FDD

36 C613650003 UL Slice RLC SDU delay FR1 FR1 TDD&FR1 FDD

37 C613650004 Duration of DL UE throughput transmission in a slice FR1 FR1 TDD&FR1 FDD

38 C613650005 Duration of UL UE throughput transmission in a slice FR1 FR1 TDD&FR1 FDD

39 C616730000 Number of UL PRBs scheduled by a DU cell slice FR1 FR1 TDD&FR1 FDD

40 C616730002 Number of UL PRBs available in a DU cell slice FR1 FR1 TDD&FR1 FDD

41 C616730002 Number of UL PRBs available in a DU cell slice FR1 FR1 TDD&FR1 FDD

42 C616730003 Number of DL PRBs available in a DU cell slice FR1 FR1 TDD&FR1 FDD

43 C616730003 Number of DL PRBs available in a DU cell slice FR1 FR1 TDD&FR1 FDD

73 - 74
 Network Slicing Management

No. Counter ID Counter Name FR1/FR2 FR1 TDD/FR1 FDD

7.2 Related KPIs

Table 54 KPI List

No. KPI ID KPI Name

1 669507 Average delay of downlink RLC SDU packets in a slice

2 669508 Average IP delay of downlink packets in a slice

3 669509 Average delay of uplink RLC SDU packets in a slice

4 669520 Slice DL RLC Average Throughput

5 669521 Slice UL RLC Average Throughput

6 669524 Slice DL RLC Recived Number of Bytes

7 669525 Slice UL RLC Recived Number of Bytes

8 669794 Slice UL Tail packet Bytes

9 669795 Slice DL Tail Packet Bytes

10 670063 UL PRB Utilization rate of a slice in NRCellDu

11 670064 DL PRB Utilization rate of a slice

7.3 Related Alarms

This feature has no related alarm.

8 Abbreviations
For the acronyms, refer to the abbreviations.

9 References
1. 3GPP TS 38.413, “NG Application Protocol (NGAP)”
2. 3GPP TS 38.331, “Radio Resource Control (RRC) protocol specification”

74 - 74