Content for  TR 21.917  Word version:  17.0.1

Summary based on the input provided by Huawei in SP-220569. SA5 service based management architecture supporting management of 5G SA and NSA scenarios have two options for the management of both legacy nodes and 5G nodes. Description Following content is specified in TS 28.530. The management of 5G SA and NSA could be classified to the following two management options with using interface IRP, NRM IRP and MnS. Option#A (interface IRP and NRM IRP are used for management of legacy nodes)

Option#B (MnS is used for management of legacy nodes)

Summary based on the input provided by Nokia, Nokia Shanghai Bell in SP-220578. This WID extends the 5G Network Resource Model to support several new features of 5G Core (5GC) and NG Radio Access Network (NG-RAN), together with enhancements of the stage 3 Solution Set (SS):

• Support of NG RAN and 5GC features. The 5G NRM is extended to support new or existing features or functionalities of NG RAN and 5GC, e.g. 5G Core SMF, 5G Core managed NFs Profile, the UDM function, Edge Application Server Discovery Function (EASDF) , local NEF selection, Network Slice Admission Control Function (NSACF) in 5GC (including adding Max number of PDU sessions and serving area information), networkSliceSubnetType for NetworkSliceSubnet, configuration of AMF, DDNMF, N33, N5, N70 and N71 interfaces, NRM definition enhancement for the NWDAF, and transport related information model to support end to end network slice management, refer to TS 28.541. Requirement for NR NRM to suport the RAN sharing scenario is added in TS 28.540.
• To support monitoring the progress of the file download in a downloading job, a "ProgressMonitor" DatatType is added, refer to TS 28.622 and TS 28.623.
• YANG solution set is enhanced to support containment mapping, add code begin/end markers and increase prefix length in TS 32.160.
• Stage 3 codes, including YAML and YANG solution sets, are uploaded to 3GPP Forge for validation and then published. Please refer the below link for the SA5 Forge repository: https://forge.3gpp.org/rep/sa5/MnS

Summary based on the input provided by Ericsson in SP-220585. This Work Item enables charging for roaming local breakout scenario. It also supports some scenarios involving non-roaming MVNO (with its own CHF). To support charging for roaming local breakout the following has been introduced from the SMF in the visited MNO:

• Collection of charging information for the purpose of wholesale charging towards the home MNO
• Collection of charging information and conveying it to the home MNO network for the purpose of retail charging

The N40 reference point is defined for the interactions between V-SMF and V-CHF, the N47 reference point is defined for the interactions between V-SMF and H-CHF, specified in TS 32.255. Wherever the V-SMF will use only N40, or both N40 and N47, depends on agreement and SMF configuration. Both reference points use the NchfConvergedCharging service, specified in TS 32.290 and TS 32.291, however online charging is only possible on the N47 when both N40 and N47 is used for the same chargeable data connectivity session.

Summary based on the input provided by Nokia in SP-220631. In network management files are used for storing and transferring different kinds of data (performance measurements, trace data, etc.). Files are transferred between Network Functions and Management Functions or between Management Functions, depending on the use case. Two different types of file transfer are addressed:

• File retrieval from a MnS producer by a MnS consumer
• File download from a MnS consumer to a MnS producer

Fully standardized and interoperable solutions are provided. The solutions follow a model driven approach, where only Network Resource Model (NRM) fragments are standardized and the existing Create, Read, Update and Delete (CRUD) operations are used. Stage 1 requirements and use cases are specified in TS 28.537. Stage 2 definitions of the NRM fragments are specified in TS 28.622. Stage 3 definitions of the NRM fragments are specified in TS 28.623. For File retrieval the File retrieval NRM fragment is defined. Files are represented by "File" objects that are contained in "Files" collections. MnS consumers can retrieve the files using a normal Read operation. Notifications are emitted upon creation of new "File" objects to inform subscribed MnS consumers about the availability of new files for retrieval. For File download the File download NRM fragment is defined. It contains the definition of the "FileDownloadJob". The MnS consumer creates these objects on the MnS producer to request the MnS producer to download a file from the MnS consumer or some file server. The download job features a "ProgressMonitor" allowing to monitor the progress of the file download. After completion of the file download the job object is deleted.

Summary based on the input provided by Nokia in SP-220841. This work item enhances existing and specifies new methods for controlling management data production, collection, coordination, and discovery. Management data includes data from RAN network functions, core network functions and UEs. In this work item, requirements for producing, reporting, storing and discovery of management data are specified in TS 28.537. Besides the existing data collection jobs, where the management data is requested from specific target managed object instances based on the managed object tree (as defined in the SA5 Network Resource Models), this WI introduces a method to request management data based on one or multiple selection criteria namely area of interest (list of cells, list of tracking areas or geographical area), domain (RAN or Core), traffic type (user plane or control plane) or slice type (e.g. eMBB, URLLC), see TS 28.622, TS 28.623. The introduced data collection job allows to request for Trace data, MDT (Minimization of Drive Test) data, RLF (Radio Link Failure) reports, RCEF (RRC Connection Establishment Failure) reports, PM (performance measurements), KPI (end-to-end key performance indicators) or a combination of these. Furthermore, the management production can be requested for a certain time window. In the context of management data discovery, the supported management data which can be provided by a network function has been enhanced to include trace metrics besides performance metrics. In this context the metric identifier for trace metrics, covering Immediate MDT, Logged MDT, Logged MBSFN MDT, Trace, RLF reports and RCEF reports, has been introduced in TS 32.422. The methods of file-based reporting of performance metrics are enhanced to allow implicit notification subscriptions for notifyFileReady notifications indicating the availability of new performance metric reports, see TS 28.622, TS 28.623.

Summary based on the input provided by Huawei in SP-220572. As per the 5G LAN-type service requirements specified in TS 22.261 and the 5G LAN-type Services specified in the TS 23.501 and TS 23.502, the 5G Virtual Network (VN) group consists of a set of UEs using private communication for 5G LAN-type services. The WID 5GLAN_CH specifies the charging principle, charging requirements, service operations and charging information for 5G VN group service charging, including:

• 5G VN group management charging: NEF and CEF support the group management (e.g. creation, modification and deletion) charging in TS 32.254.
• 5G VN group communication charging: SMF supports the charging information collection and reporting per PDU session in TS 32.255.

The corresponding Open API and ASN.1 for 5G LAN VN group service charging are specified in the TS 32.291 and TS 32.298.