Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 28.800  Word version:  15.0.0

Top   Top   Up   Prev   None
0…   5…   6…

 

6  Potential requirements on management and orchestration architecture

REQ-NWA -CON-01
The 3GPP management system shall support the management requirements of network slice as defined in TR 28.801 section 6.
REQ-NWA -CON-02
The management and orchestration architecture of next generation network and services shall support the management functions as defined in clause 4.9 of TR 28.801 for network slice management.
REQ-NWA -CON-03
The 3GPP management system shall have a functionality to provide various categories of network management FM and PM data to other network management functions which act as consumers of the data.
REQ-NWA -CON-04
The 3GPP management system shall support the management of networks containing non-5G system and 5G system.
REQ-NWA -CON-05
The 3GPP management system shall, based on operator policy, expose suitable APIs externally to another operator's management system that supports requirements expressed in clause 6.10.2 of TS 22.261.
REQ-NWA -CON-06
The 3GPP management system shall, based on operator policy, expose suitable APIs externally to the communication services provider that supports requirements expressed in clause 6.10.2 of TS 22.261.
REQ-NWA -CON-07
The 3GPP management system shall support interaction of management data with ETSI NFV.
REQ-NWA -CON-08
The 3GPP management system shall be able to coordinate with other 3GPP management systems to host communication services across multiple CSPs.
Up

7  Potential management and orchestration architecture options

7.1  Management functions of next generation networks and services

7.1.1  General

The following management functions are to be considered for supporting the management of the next generation networks and services:
  • Network slice related management functions:
    • Communication service management function:
      • Feasibility check for communication service and preparation of network slice requirements
      • Exposure of communication service related data, management functions and capabilities subject to the agreement of the network operator
      • Lifecycle management (LCM) for communication service
      • Fault management (FM) for communication service
      • Performance management (PM) for communication service
      • Configuration management (CM) for communication service
    • Network slice management functions:
      • Network resource discovery function
      • Feasibility check for the network slice and determine the network slice subnet related requirements
      • Providing network slice capability information
      • Providing control of appropriate management functionalities and management data
      • Network Slice self- optimization, self-configuration and self-healing.
      • Network slice related policy management
      • Lifecycle management (LCM) for Network slice
      • Fault management (FM) for Network slice
      • Performance management (PM) for Network slice
      • Configuration management (CM) for Network slice
    • Network slice subnet management functions:
      • Network resource discovery function
      • Feasibility check for the network slice subnet and determine the network slice subnet related requirements
      • Network slice subnet related policy management
      • Providing network slice subnet capability information
      • Lifecycle management (LCM) for Network slice Subnet
      • Fault management (FM) for Network slice Subnet
      • Performance management (PM) for Network slice Subnet
      • Configuration management (CM) for Network slice Subnet
      • Network slice subnet self- optimization, self-configuration and self-healing
  • 5G Network function related management functions:
    • Fault Management (FM) for 5G Network function
    • Performance Management (PM) for 5G Network function
    • Configuration Management (CM) for 5G Network function
    • Trace Management for 5G Network function
    • MDT for 5G Network function
    • SON (self-configuration/self-healing/ANR/MRO/ES/SWM) for 5G Network function
    • EntryPoint management function (EPM) for 5G Network function
There are four groups of objects which are necessary to be managed in the context of 5G network management:
  • 5G services
  • 5G slice instances
  • 5G network functions
  • Resources including virtual resources or non-virtual resources which support the 5G network
Up

7.1.2  Principles to be considered for 5G management architectureWord‑p. 15

The following principles should be taken into account for the 5G management architecture:
  1. The architecture should investigate the relation and interaction between slicing management functions (NSMF/NSSMF) and MANO.
  2. The architecture should consider the relation between slicing management functions (NSMF/NSSMF) and OSS/NM/EM.
  3. Separate the view from the functional aspects and deployment aspects.
  4. The architecture should show the interface with the Transport network manager.

7.2  Management interfaces of next generation networks and services

7.2.1  Management interfaces

7.2.1.1  Fault Management interfaces

The list of necessary fault management interfaces will be addressed in the normative phase.

7.2.1.2  Performance Management interfaces

The list of necessary performance management interfaces will be addressed in the normative phase.

7.2.1.3  Configuration Management interfaces

The list of necessary configuration management interfaces will be addressed in the normative phase.

7.2.1.4  Trace Management interfaces

The list of necessary Trace management interfaces will be addressed in the normative phase.

7.2.1.5  MDT interfacesWord‑p. 16

The list of necessary MDT interfaces will be addressed in the normative phase.

7.2.1.6  SON interfaces

The list of necessary SON interfaces will be addressed in the normative phase.

7.2.1.7  EntryPoint management interfaces

The list of necessary EntryPoint management interfaces will be addressed in the normative phase.

7.2.1.8  Notification Log management interfaces

The list of necessary notification log management interfaces will be addressed in the normative phase.

7.2.1.9  Notification management interfaces

The list of necessary notification management interfaces will be addressed in the normative phase.

7.2.1.10  Network provisioning interfaces

The list of necessary network provisioning interfaces will be addressed in the normative phase.

7.3  Potential Management architecture

7.3.1  Service based management architecture

There are the following management layers related to the 5G management:
  • Service management layer
  • Network management layer
  • NF management layer
The following diagram is an example of positioning of management functions to each layer.
[not reproduced yet]
Figure 7.3.1-1: Example of layering architecture and management functions
Up

7.3.2  Integrated management and orchestration architectureWord‑p. 17

This clause provides an example of potential integrated network and network slicing management and orchestration architecture for 5G.
The Network and Network Slice Management Function (NNSMF) is responsible for the management of network and network slice. NNSMF also provides the standardized interface_1 to the Service Manager who is using the network and network slice.
Sets of network functions and Network Slice Subnet Management Function (SNMF) are responsible for the management of sets of network functions and network slice subnet. SNMF also provides the standardized interface_2 to NNSMF.
NF Management Function (NFMF) is responsible for the management of network function. NFMF also provides standardized interface_3 to SNMF.
[not reproduced yet]
Figure 7.3.2-1: An example of potential integrated management architecture
Up

7.3.3  Management Architecture for Multiple Operators communication

7.3.3.1  Solution options for FM and PM for services hosted across multiple operators

7.3.3.1.1  Introduction
An operator (Operator-A) hosts a 5G communication service for a CSP by realizing it over multiple other operators' networks.
7.3.3.1.2  Option 1: FM and PM data collection and reporting by single operatorWord‑p. 18
The first option of FM and PM data collection and reporting of the service initiated by Operator-A consists of the following steps:
  1. Operator-A agrees with other Operators to collect and report, at the agreed limit of exposure, the FM and PM data of the service to a data repository (Y).
  2. In accordance with the said agreement, other Operators start monitoring the service and report FM and PM data to the repository (Y).
  3. Operator-A sends a notification to the communication service provider on the availability of FM and PM data at the repository (Y).
  4. The communication service provider can fetch available FM and PM data.
Up
7.3.3.1.3  Option 2: FM and PM data collection and reporting by multiple operators individually
The second option of FM and PM data collection and reporting of the service is initiated by the operator-A, with individual reports by the other operators, consists of the following steps:
  1. Operator-A agrees with other Operators to collect and report the FM and PM data of the service to the repository (Xop) that may be specific to each operator.
  2. All operators agree with the communication service provider the agreed limit of exposure of the FM and PM data of the service.
  3. In accordance with the said agreement, all Operators start monitoring the service and FM and PM data are reported directly to their respective repository (Xop).
  4. Each operator sends a notification to the CSP of the availability of FM and PM data at the repository (Xop).
  5. The CSP provider can fetch available FM and PM data.
Up

7.3.3.2  Potential architecture to support 5G communication services across multiple operators

A 5G communication service that is hosted across multiple operators may require the exposure of interfaces by a network owning operator to a 3rd party: either the communication services provider (item 5.8) or to another operator (item 5.7). Over this interface any of the following managed entities may be managed by the 3rd party with the agreed upon level of exposure:
  • A communication service,
  • An NSI or a part of an NSI.
The operator owning the network agrees previously with the 3rd party to the appropriate type of interface exposure, which may provide, amongst others, the ability to
  • request life cycle management of a communication service, an NSI or part of an NSI including specifying various parameters for the request such as the appropriate SLA, penalties for SLA violation
  • issue requests for collecting monitoring data for any of existing managed entities
  • request re-configuration of an existing managed entity
The operator can report the success or failure of a request to the 3rd party over the exposed interface.
Up

7.3.3.3  Potential scenarios for the management of communication services across multiple CSPsWord‑p. 19

7.3.3.3.1  Introduction
A communication service customer requests a communication service to a communication service provider (CSP). Based on the services offered by multiple other CSPs, the CSP may host and manage the communication service over multiple CSPs. The following scenarios are possible
7.3.3.3.2  Option 1: A communication service composed of multiple communication services
  • The CSP decomposes a communication service to multiple communication services and determines to host these multiple communication services in other CSP networks.
  • The CSP sends a request to host a part of the communication service to other multiple CSPs with the required parameters. The parameters include but are not limited to the service identifier the network requirements of the composed communication service, suitable APIs (e.g., PM/FM exposure), etc.
  • After receiving the request, each of the other CSPs creates the service. During the creation of the composed communication service.
  • The CSP may receive the acknowledgement from each of the multiple other CSPs after a successful deployment of the service, the acknowledgement may include the appropriate information to identify the partial communication service.
  • The CSP can provide the end-to-end management of the communication service to the customer.
Up
7.3.3.3.3  Option 2: A communication service hosted on of multiple network slice instances
  • The CSP creates a communication service and decomposes the communication service with multiple network slice instances and determines to host the multiple network slice instances in multiple other network providers'.
  • The CSP sends a request to host a network slice instance to each of multiple other network providers with the required parameters. The parameters include but are not limited to respective identifiers the network requirements of the composed network slice instance, suitable APIs (e.g., PM/FM exposure), etc.
  • After receiving the request, each of multiple other network providers create the network slice instance as specified in TR 28.801.
  • The CSP may receive the acknowledgement from each of the multiple other network providers after a successful deployment of the network slice instance, the acknowledgement may include the appropriate information to identify the instantiated NSI.
  • The CSP can provide the end-to-end management of the communication service to the customer.
Up

7.3.4  Network slice management functions

This clause describes an example of network slice management functions.
The CSMF consumes, via standardized interface (A), the network slice management service provided by NSMF.
The NSMF consumes, via standardized interface (B), the network slice subnet management service provided by NSSMF.
The NSSMF consumes, via standard interfaces (Cs), the FCAPS management services provided by the Network Functions.
NSSMF and NSMF may include (comprise) a range of sub-functionalities offering management services.
The NSSMF and NSMF consume via MANO defined interfaces, the ETSI NFV defined NS management services provided by ETSI defined NFVO;
[not reproduced yet]
Figure 7.3.4-1: Network slice management functions (an example)
Up

7.4  Potential management data interaction with NFV-MANOWord‑p. 20

7.4.1  General

When the network slice being built on the virtualisation environment and the network slice resource management is supported by the NFV-MANO, data interaction between management functions supporting network slicing and NFV-MANO is used.

7.4.2  Management architecture relation between slicing management functions and NFV-MANO

7.4.2.1  Option A: NSSMF Interacts Management Data with NFV-MANO

Assuming NSSIs are assumed to fully or partially build on the virtualization environment managed by NFV-MANO as shown in Figure 7.4.2.1-1. The management data interaction between NSSMF and NFV-MANO may contain network service lifecycle management data, virtual resource performance management data, and virtual resource fault management data.
[not reproduced yet]
Figure 7.4.2.1-1: NSSMF interactions with NFVO of NFV-MANO management system
Up
In case that NSSMF interacts with NFV-MANO, the management data interactions are given as following:
  • NSSMF may request on-boarding of NSD to NFVO serving a network slice subnet;
  • NSSMF may request NS lifecycle management from NFVO serving a network slice subnet;
  • NSSMF may request NFVO to create a network service supporting a network slice subnet instance.
NSSMF may request connectivity service to TN management system.

8  ConclusionsWord‑p. 21

The management and orchestration architecture of next generation networks and services has considered the following scenarios:
  • Management of the networks containing non-5G NE and 5G NE
  • Management and orchestration for network slicing
  • FM and PM data collection and reporting for single and multiple operators
  • Management and orchestration for management of 5G-RAN and 5GC
  • Management of communication services
  • Exposure of management interfaces to another operator
  • Exposure of management interfaces to communication services provider
  • Management and orchestration of networks with non-3GPP parts
The following potential management solutions are studied:
  • Service based management architecture
  • Architecture relation between slicing management and NFV-MANO
  • Management architecture for multiple operators communication
The potential management interfaces, management architecture related requirements and principles to be considered for 5G management architecture are also studied.
Up

9  RecommendationsWord‑p. 22

It is recommended to start normative work on the management architecture for the 5G network in Rel-15.
It is recommended to consider a management architecture to support
  • network management
  • network slicing management
  • 5G Core and RAN management
  • management across multiple operators' scenario
  • interaction with non-3GPP management system e.g. NFV-MANO
It is recommended to continue the details on service based management architecture, management services, and position of management services in different management layers in Rel-15.
Up

$  Change HistoryWord‑p. 23


Up   Top