This use case highlights potential management options/scenarios for possible network deployments, specifically at the early stages of introducing 5G network elements along with existing non-5G generation 3GPP network(s).
Operator wants to manage a network containing both non-5G NE(s) and 5G NE(s).
There are following scenarios for operator to manage the 5G NE functions:
Operator enhances the existing management and orchestration function to manage both 5G NE(s) and non-5G NE(s). For example, operator may enhance the fault management function to retrieve the faults information from both non-5G NE and 5G NE; or
Operator creates new management functions to manage both 5G NE and non-5G NE. For example, operator may create new management function to manage the next generation network feature massive Internet of Things.
The 5G network provides multiple communication services to the communication service customers. The 5G network may be composed of virtualized network elements and non-virtualized network elements provided by different vendors.
The management of the 5G networks and services includes network services management, network management and network elements management. The network elements management includes the NF management and resource management.
There are different types of network management functions, for example, the 5G network slicing management functions are NSSMF, NSMF and CSMF, the LTE nodes management functions are NM, EM, and the NFV-MANO management functions are NFVO, VNFM, VIM.
For different management purposes, some of the network management functions request access to network management data, i.e. FM data and PM data, such as:
NF related FM and PM data;
Network related FM and PM data;
Communication service related FM and PM data.
Different network management functions may request same data. For example, as data consumers, EM, NM and NSSMF may all need the alarm data or performance measurement data of some specific NFs although they focus on different aspects of network management.
The request comes to a logical function whose responsibility is collection and re-distribution of the FM and PM data of NFs. Then, the multiple network management functions get the FM and PM data from the logical data collection and reporting function. For example, the PM data of NFs is collected somewhere (data repository = X) and the logical data collection and reporting function notifies subscripted consumers of availability and location of recently arrived data in X. The consumers can then fetch the PM data at their leisure.
A communication service provider provides a communication service to communication service customer. The communication services provider requests operator A to host the service. The operator A decides to use multiple other operators' networks to host the service.
The service has been instantiated and is in operation.
For different management purposes (as described in the clause 5.3), some of the network management functions request access to network management data, i.e. FM and PM data. To gather the FM/PM data for the communications service Operator A then agrees with all participating operators on how the PM/FM data is collected. All operators provide the PM/FM data in accordance with the said agreement.
Operator A indicates the availability of FM/PM data to the communication services customer. The communication services provider can then fetch the PM/FM data at their convenience for the customer.
The customer sends communication service related requirements to service management function.
The service management function translates the communication service related requirements to network related requirements. The information indicating whether to use network slice may be included in the network related requirement.
In case of using network slice, the management function for handling network slice creates a new network slice instance or reuses an existing network slice instance to satisfy the network related requirements as described in clause 5.2. Otherwise, the management function for handling network without slicing utilizes network without slicing to satisfy the network related requirements.
3GPP TR 28.801 specifies the requirements and use cases for multi-operator slices. To support those use cases an operator's management system exposes suitable APIs to another operator for slice management in accordance with clause 6.10 of TS 22.261. All exposure is based on the operator's policy.
The operator wants to manage the 5G network. The 5G network may comprise non-3GPP parts (e.g. transport network, data center network) together with the 3GPP part (i.e. 5G-RAN and 5GC), thus the properly coordination between 3GPP management system and corresponding non-3GPP part management systems may be needed.
A communication service customer requests a communication service to CSP A. CSP A decides to host the communication service across multiple CSPs to satisfy network related requirements. Non-management pre-requisites, such as trust relationships between CSPs, legal and business related, to create a communication service are assumed to exist.
The CSP A decides to host a communication service across multiple CSPs (CSP A and CSP B) to satisfy the requirements based on pre-existing agreements between CSP A and CSP B. The end-to-end management of the communication service hosted by multiple CSPs may reside with the CSP A. CSP A can request agreed upon management data to CSP B on the part of the communication service hosted in CSP B.