5 Architecture reference model

28.5333GPPArchitecture frameworkManagement and orchestrationRelease 17TS

5.1 General concepts

5.1.1 Management service producers, consumers and exposure

The management services for a mobile network with or without network slicing may be produced by any entity. For example, it can be a Network Functions (NF), or network management functions. The entity may provide (produce) such management services as, for example, the performance management services, configuration management services and fault supervision services.

The management services can be consumed by another entity, which may in turn produce (expose) the service to other entities. Figure 5.1.1-1 shows an example of the management service X which is initially produced by the entity A which is an NF , then consumed by another entity B which is a network management function. Then entity B in turn exposes it to the entity C.

Figure 5.1.1-1. Example of producers and consumers of the management service

Figure 5.1.1-2 shows another example of the management service X which is produced by the entity A which is a NF, then entity B processes the information and produce management service Y and exposes it to the entity C.

Figure 5.1.1-2. Example of producers and consumers of management services

5.1.2 Interactions between management service producer and management service consumer

The interactions between the management service producer and management service consumer follows one of the three following paradigms:

– "Request-response": A management service producer is requested by a management service consumer to invoke an operation, which either performs an action or provides information or both. The management service producer provides response based on the request by management service consumer.

Figure 5.1.2.1: Request-response communication paradigm

– "Subscribe-notify": A management service consumer requests a management service producer to establish a subscription to receive network events via notifications, under the filter constraint specified in this operation.

Subscriptions can be created also by other means than by using such operation.

Figure 5.1.2.2: Subscribe-notify communication paradigm

NOTE: Example of a common aspect applicable to all management services is the use of notifications. For a management service to use notifications the management service consumer needs a subscription to notifications it is interested in. The management service consumer requests the creation of a subscription by sending a subscribe operation to the management service producer. To cancel a subscription the consumer sends an unsubscribe operation to the producer.

– "Connect-streaming": A management producer is provided with the address the management service consumer. The management service producer requests to establish a connection with the management service consumer for management data streaming. The management service producer sends the management data, when they are ready, by streaming to the management service consumer over the established connection.

Figure 5.1.2.3: Connect-streaming communication paradigm

– "Request-response with access control" in explicit authentication and authorization mode: An authentication service producer is requested by a management service consumer for authentication, the authentication service producer authenticates the management service consumer according to information in the request, authentication policies and other information associated to the identity of the management service consumer. After being successfully authenticated, the management service consumer may send request to an authorization service producer to get access token for permissions. After getting access token from an authorization service producer, the management service consumer sends request to corresponding management service producers to access management services. The management service producer provides response to the consumer after verifying the access token. Figure 5.1.1.2-4 depicted typical Request-response communication paradigm with access control explicit authentication and authorization mode

Figure 5.1.1.2-4: Request-response communication paradigm with access control (explicit authentication and authorization)

– "Request-response with access control" in implicit authentication and authorization mode: management service consumer initiates a management session towards management service producer. Management service producer accesses authentication service producer to authenticate the management service consumer according to information in the request, groups and other information associated to the identity of the management service consumer. After successfully being authenticated, the management service consumer sends request to management service producer to access management services, management service producer enforces access control using local policies applicable for the current authentication context

NOTE: If Authentication Service Producer is unavailable, MnS Producer may opt to perform local authentication.

Figure 5.1.1.2-5: Request-response communication paradigm with access control (implicit authentication and authorization)

5.2 Management interactions with NFV MANO

3GPP management system shall be capable to consume NFV MANO interface (e.g. Os-Ma-nfvo, Ve-Vnfm-em and Ve-Vnfm-vnf reference points).

Producer of management services can consume management interfaces provided by NFV MANO for following purposes:

– Network service LCM.

– VNF LCM, PM, FM, CM on resources supporting VNF.

5.3 Management service deployment based on ZSM framework

ZSM framework reference architecture is described in ETSI GS ZSM 002 [29]. The ZSM framework reference architecture defines a set of architectural building blocks that collectively enable construction of more complex management services and management functions using a consistent set of composition and interoperation patterns. So it is important to show the 3GPP Management Service deployment based on ZSM Framework.Figure 5.3-1 shows an example of 3GPP Management Service deployment based on ZSM framework reference architecture. In this example:

– 3GPP Cross Management Domain (A bundle of Cross Domain MnFs) provides a set of MnS(s) for Cross Domain Network (including Network Slice) and consumes MnSs provided by the RAN Management Domain and the CN Management Domain. 3GPP Cross Management Domain can implement close loop (s) within the domain. 3GPP Cross Management Domain is a part of E2E Service Management Domain in ETSI ZSM Framework.

– RAN Management Domain (A bundle of RAN MnFs) provides a set of MnS(s) for the RAN SubNetwork and NF. RAN Management Domain can implement close loop(s) within the domain. RAN Management Domain is a Management Domain in ETSI ZSM Framework.

– CN Management Domain (A bundle of CN MnFs) provides a set of MnS(s) for the CN SubNetwork and NF. CN Management Domain can implement close loop(s) within the domain. CN Management Domain is a Management Domain in ETSI ZSM Framework.

– A 3GPP Management Framework Consumer (e.g. vertical OT system, BSS) can consume MnS(s) provided by the 3GPP Cross Management Domain, RAN Management Domain,CN Management Domain. 3GPP Management Framework Consumer is a ZSM framework consumer in ETSI ZSM Framework.

Figure 5.3-1: An example of Management Service deployment framework.

The closed control loop SLS assurance (COSLA) is an example of the closed loop in ZSM framework. COSLA can be deployed at domain level or cross domain level. A domain COSLA provides domain specific assurance, e.g. closed control loop assurance in a RAN management domain, CN management domain. A cross domain COSLA can provide a part of end-to-end SLS assurance service, e.g. to assure the service experience in 3GPP cross management domain.

5.4 Management interactions with NWDAF

3GPP management system interacts with NWDAF in a coordinated way. 3GPP management system takes the responsibility of management from the network-wide view, addresses the slow control loop with broad management scope. NWDAF is a 5GC NF as specified in TS 23.288 [30].