5 Specification level requirements

28.5573GPPManagement and orchestrationManagement of Non-Public Networks (NPN)Release 17Stage 1 and stage 2TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 Use cases

5.1.0 Generic use cases

5.1.0.1 Collecting UE related data

In some NPN scenarios, the NPN-SC may need to deploy a new vertical service or supervise NPN service SLA based on the UE related data (e.g. UE measurement, etc). In this situation, the 3GPP management system may collect UE related data and provide them to authorized NPN-SC. To obtain the UE related data, the NPN-SC may consume the corresponding capability exposed by the NPN-SP.

5.1.1 Use cases related to SNPN management

5.1.1.1 Create a SNPN

This use case describes a scenario where an NPN-SP decides to provision an NPN for use by an NPN-SC in the form of SNPN. It is either an MNO or an enterprise can be playing a role of NPN-SP, and it is an enterprise (the different or same if the enterprise is also NPN-SP) be playing a role of NPN-SC. This SNPN consists of network resources decoupled from PLMN resources, including:

– RAN NE(s)

– 5GC network functions

– Transport network

In this scenario, the NPN-SC sends to the NPN-SP a request for the provision of an NPN. This request contains the NPN related SLS requirements. To fulfil the SLS of requested NPN, the NPN-SP decides to create a new SNPN.

The NPN-SP maps SLS of requested NPN into 3GPP 5G system related requirements. These requirements allow the NPN operator to decide on the constituent network resources and the topology of the 3GPP 5G network to be created for the SNPN, as follows:

– For the AN and CN related parts, the NPN operator takes all the actions needed to set up and configure required network resources, including RAN NE(s) and 5GC network functions. For more details, refer to TS 28.531 [8], clauses 5.1.17 "Creation of 3GPP NF" and 5.1.18 "Configuration of a 3GPP NF instance". Some of these actions can require setting up a new 3GPP sub-network. For more details, refer to TS 28.531 [8], clause 5.1.19 "Creation of a 3GPP sub-network".

– For the TN related part, the NPN operator takes all the actions needed to set up the required connectivity along the RAN and CN, configuring the underlying transport network. When taking these actions, information on SNPN topology (e.g. external connection points of AN and CN) and performance (e.g. latency, bandwidth) should be considered.

If the requested NPN requires connectivity to external PLMN resources (e.g. to allow UEs registered into the SNPN to access public network services), the NPN-SP derives the requirements for such a connectivity. These requirements allow the NPN operator to configure the transport network connecting the SNPN and the PLMN accordingly.

NOTE 1: To allow UEs to access public network services from the SNPN, the UEs also have to be registered in the PLMN UDM.

NOTE 2: For the derivation of connectivity requirements between SNPN and the PLMN, the NPN-SP makes use of two sources of information:

1) the SLS of requested NPN, received from the NPN-SC; and

2) connectivity information of the created 3GPP 5G network, received from the NPN operator.

In this use case, depending on different situations, the NPN operator role can be played by:

– the mobile network operator only. In such MNO Managed Mode case, the mobile network operator takes the entire responsibility of operating the SNPN and managing SNPN-PLMN connectivity, if required; or

– the mobile network operator and the enterprise. In such MNO-Vertical Mode case, the mobile network operator can expose some management capabilities to the enterprise, according to business agreement between the two parties. SNPN-PLMN connectivity, if required, is always managed by the mobile network operator; or

– the vertical only. In such Vertical Managed Mode case, the enterprise takes the entire responsibility of operating the SNPN. The SNPN-PLMN connectivity, if required, is always managed by the mobile network operator who takes the entire responsibility of operating the PLMN.

In this use case depending on the different NID assignment models as described in clause 4.4, the NPN operator role can configure the NID to related AN nodes and 5GC NFs. The management of NID is described in clause 4.4 in the present document.

5.1.2 PNI-NPN provisioning by network slice (NSaaS) of PLMN

A mobile network operator (playing the role of NPN-SP) decides to provision a PNI-NPN for use by an enterprise (playing the role of NPN-SC) in the form of a network slice of a PLMN. This network slice may include PLMN network functions / network function services for non-public use. Depending on NPN-SC, the slice can span one or more network domains, e.g.:

– Network slice corresponding to a RAN-only network slice subnet.

– Network slice corresponding to CN-only network slice subnet.

– Network slice corresponding to a network slice subnet composed of RAN slice subnet + Transport network slice subnet + CN slice subnet.

In this scenario, the NPN-SC provides the NPN related SLA requirements to the NPN-SP. These requirements specify NPN related SLS (i.e. NPN desired performance and required functionality) together with other business related information (i.e. NPN lifetime, NPN slice charging / accounting, etc.). To fulfil the SLS of requested NPN, the NPN-SP decides to use network slicing.

The NPN-SP maps SLS of requested PNI-NPN into ServiceProfile attributes. For details on these attributes, see TS 28.541 [7]. Based on these attributes, the NPN-SP determines to reuse an existing network slice or create a new network slice for the PNI-NPN. If an existing network slice can be reused, the operator may reconfigure the existing network slice.

In this use case, the NPN operator role is played by:

– The mobile network operator only. In such MNO Managed Mode case, the mobile network operator takes the entire responsibility of operating the network slice of the PLMN.

– The mobile network operator and the enterprise. In such MNO-Vertical Managed Mode, according to business agreement between both parties, the mobile network operator can expose some management capabilities to the enterprise.

NOTE: The scope of the NPN operator in this use case does not include the management of enterprise owned 5G network resources (i.e. on-premise physical equipment and on-premise NFVI).

5.2 Requirements

5.2.1 Generic requirements for management of NPN

REQ-NPN-FUN-01 The 3GPP management system shall have the capability to monitor the performance measurements and KPIs associated with an NPN.

REQ-NPN-FUN-02 The 3GPP management system shall have the capability to provide the performance measurements and KPIs associated with an NPN to authorized entity, either NPN-SC (when NPN-SP and NPN-OP are both played by the same actor) or NPN-SP (when NPN-SP and NPN-OP are played by different actors).

REQ-NPN-FUN-03 The 3GPP management system shall have the capability to receive SLA requirements from authorized NPN-SC and then translating the SLA requirements into service and network resources related requirements.

REQ-NPN-FUN-04 The 3GPP management system shall have the capability to evaluate SLS assurance related to an NPN.

REQ-NPN-FUN-05 The 3GPP management system shall have the capability to restrict the exposure of management capabilities and corresponding managed resources to NPN-SC.

REQ-NPN-FUN-06 The 3GPP management system shall have the capability to support management capabilities exposure, which includes management capabilities of network provisioning, fault supervision and performance assurance to the authorized NPN-SC.

REQ-NPN-FUN-07 The 3GPP management system shall have the capability to provision both physical and virtual NPNs.

REQ-NPN-FUN-08 The 3GPP management system shall have the capability to provision different NPNs intended to different NPN-SCs.

REQ-NPN-FUN-09 The 3GPP management system shall have the capability to provision an NPN which serves different NPN-SCs.

REQ-NPN-FUN-10 The 3GPP management system shall offer the NPN-SC the ability to manage its own NPN(s) and its private slice(s) in the PLMN in a combined manner.

5.2.2 Requirements for management of SNPN

REQ-SNPN-FUN-01 The 3GPP management system shall have the capability to support standalone operation of an SNPN.

REQ-SNPN-FUN-02 The 3GPP management system shall have the capability to support management of dedicated NPN identifier (i.e. combination of a PLMN ID and a Network Identifier (NID) which is used to identify an SNPN.

REQ-SNPN-FUN-03 The 3GPP management system shall have the capability to configure NID which consists of an assignment mode and an NID value.

REQ-SNPN-FUN-04 The 3GPP management system shall have the capability to configure an NR cell for the support of SNPN, by configuring a gNB (gNB-DU in NG-RAN split deployment scenarios) with a list of served NIDs per PLMN Identity.

REQ-SNPN-FUN-05 The 3GPP management system shall have the capability to interwork with one or more non-3GPP management systems to support the operation of a SNPN which includes 3GPP and non-3GPP segments.

5.2.3 Requirements for management of PNI-NPN

REQ-PNIN-FUN-01 The 3GPP management system shall have the capability to collect NPN UE related data which may include MDT data and trace data.

REQ-PNIN-FUN-02 The 3GPP management system shall have the capability to provide NPN UE related data to authorized NPN-SC according to pre-defined agreements.

REQ-PNIN-FUN-03 The 3GPP management system should have the capability to support assignment and maintenance of CAG ID which identifies the CAG cells.

REQ-PNIN-FUN-04 The 3GPP management system shall have the capability to configure a NR cell to support PNI-NPN, by configuring a gNB (gNB-DU in NG-RAN split deployment scenarios) with a list of serving CAGs per PLMN Identity.

REQ-PNIN-FUN-05 The 3GPP management system should have the capability to manage the list of UEs that are allowed on the corresponding CAG.

REQ-PNIN-FUN-06 The 3GPP management system should have the capability to configure access policy of CAG cells.

NOTE: The access policy of CAG cells includes such as allowed days/time slots for NPN UEs that are allowed on the corresponding CAG cells.

REQ-PNIN-FUN-07 The 3GPP management system shall have the capability to provision a PNI-NPN by means of dedicated DNN, or by one (or more) network slice instance(s). For the latter, the network slice instance is made available for the NPN-SC by means of Network Slice as a Service (NSaaS) model (see clause 4.1.6 from TS 28.530 [2]).