|
TECHNICAL SPECIFICATION
5G;
Management and orchestration;
Architecture framework
(3GPP TS 28.533 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 1 ETSI TS 128 533 V15.0.0 (2018-10)
Reference
DTS/TSGS-0528533vf00
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 2 ETSI TS 128 533 V15.0.0 (2018-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 3 ETSI TS 128 533 V15.0.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Management framework. 7
4.1 Management services . 7
4.2 Management service components . 7
4.2.1 Introduction. 7
4.2.2 Management service component type A . 7
4.2.3 Management information . 7
4.2.3.1 Management service component type B . 7
4.2.3.2 Management service component type C . 7
4.3 Combination of management service components . 7
4.4 Management capability exposure governance . 8
4.5 Management Function (MF) Concept . 9
4.6 Management data analytics ca pability . 11
5 Architecture reference model . 11
5.1 General concepts . 11
5.1.1 Management service providers, consumers and exposure . 11
5.1.2 Interactions between management service producer and management service consumer . 12
5.2 Management interactions with NFV MANO . 13
Annex A (informative): Example of deployment model with utilization of management
services . 14
A.1 Utilization of Management services in network and subnet layers . 14
A.2 Utilization of management services in network function management. . 14
A.3 Utilization of management services by Exposure Governance Management Function (EGMF) . 15
A.4 Utilization of interface to NFV-MANO by the producer of management services . 16
A.5 Management Data Analytics Service (MDAS) . 17
A.6 Utilization of management services in functional management architecture . 17
A.7 Utilization of management data analytics services . 18
A.8 An example of deployment scenario for network and network slice . 19
Annex B (normative): Solutions for management of 5G network and network slicing . 21
Annex C (informative): Example of mapping Management Services (MnS) to pre-Rel-15
management framework . 22
Annex D (informative): Change history . 23
History . 24
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 4 ETSI TS 128 533 V15.0.0 (2018-10)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The management of the 3GPP network is provided by management services. The service based architecture and
interfaces support various management services of vastly different requirements on network configuration, network
performance, and network fault supervision. The 3GPP network management architecture evolves supporting operators'
design and management of their service oriented networks.
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 5 ETSI TS 128 533 V15.0.0 (2018-10)
1 Scope
The present document defines the network management and orchestration architecture for 3GPP networks including
network slicing. The use cases and requirements are specified in TS 28.530 [3].
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[3] 3GPP TS 28.530: "Management and orchestration of networks and network slicing; Concepts, use
cases and requirements".
[4] 3GPP TS 28.541: "Management and orchestration of 5G networks; Network Resource Model
(NRM); Stage 2 and stage 3".
[5] 3GPP TS 28.552: "Management and orchestration of 5G networks; Performance measurements
and assurance data".
[6] 3GPP TS 28.554: "Management and orchestration of 5G networks; 5G End to end Key
Performance Indicators (KPI)".
[7] 3GPP TS 32.425: "Telecommunication management; Performance Management (PM);
Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)".
[8] 3GPP TS 28.531: "Management and orchestration of 5G networks; Provisioning; Stage 1".
[9] 3GPP TS 28.xxx: "Management and orchestration; Management services".
[10] 3GPP TS 28.500: "Telecommunication management; Management concept, architecture and
requirements for mobile networks that include virtualized network functions"
[11] 3GPP TS 28.510; "Telecommunication management; Configuration Management (CM) for mobile
networks that include virtualized network functions; Requirements".
[12] 3GPP TS 28.511; "Telecommunication management; Configuration Management (CM) for mobile
networks that include virtualized network functions; Procedures".
[13] 3GPP TS 28.512; "Telecommunication management; Configuration Management (CM) for mobile
networks that include virtualized network functions; Stage 2".
[14] 3GPP TS 28.513: "Telecommunication management; Configuration Management (CM) for mobile
networks that include virtualized network functions; Stage 3".
[15] 3GPP TS 28.515; "Telecommunication management; Fault Management (FM) for mobile
networks that include virtualized network functions; Requirements".[16] 3GPP TS 28.516:
"Telecommunication management; Fault Management (FM) for mobile networks that include
virtualized network functions; Procedures".
[17] 3GPP TS 28.517: "Telecommunication management; Fault Management (FM) for mobile
networks that include virtualized network functions; Stage 2".
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 6 ETSI TS 128 533 V15.0.0 (2018-10)
[18] 3GPP TS 28.518: "Telecommunication management; Fault Management (FM) for mobile
networks that include virtualized network functions; Stage 3".
[19] 3GPP TS 28.520: "Telecommunication management; Performance Management (PM) for mobile
networks that include virtualized network functions; Requirements".
[20] 3GPP TS 28.521: "Telecommunication management; Performance Management (PM) for mobile
networks that include virtualized network functions; Procedures".
[21] 3GPP TS 28.522: "Telecommunication management; Performance Management (PM) for mobile
networks that include virtualized network functions; Stage 2".
[22] 3GPP TS 28.523: "Telecommunication management; Performance Management (PM) for mobile
networks that include virtualized network functions; Stage 3".
[23] 3GPP TS 28.525: "Telecommunication management; Life Cycle Management (LCM) for mobile
networks that include virtualized network functions; Requirements".
[24] 3GPP TS 28.526: "Telecommunication management; Life Cycle Management (LCM) for mobile
networks that include virtualized network functions; Procedures".
[25] 3GPP TS 28.527: "Telecommunication management; Life Cycle Management (LCM) for mobile
networks that include virtualized network functions; Stage 2".
[26] 3GPP TS 28.528: "Telecommunication management; Life Cycle Management (LCM) for mobile
networks that include virtualized network functions; Stage 3".
[27] ETSI GS NFV 003: "Network Functions Virtualisation (NFV); Terminology for Main Concepts in
NFV V1.3.1 (2018-01)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1] or NFV-MANO [27].
Exposure governance management function: Management Function entity with the role of management service
exposure governance.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], in NFV-MANO [27] and the
following apply. An abbreviation defined in the present document takes precedence over the definition of the same
abbreviation, if any, in 3GPP TR 21.905 [1].
CM Configuration Management
LCM Lifecycle Management
MDAS Management Data Analytics Service
MF Management Function
MnS Management Service
NFV-MANO Network Functions Virtualisation Management and Orchestration
PM Performance Management
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 7 ETSI TS 128 533 V15.0.0 (2018-10)
4 Management framework
4.1 Management services
A management service offers management capabilities. These management capabilities are accessed by management
service consumers via standardized service interface composed of individually specified management service
components.
Figure 4.1.1: Management Service
4.2 Management service components
4.2.1 Introduction
A management service combines elements of management service component type A, B and C. The management
service components are combined to allow a management service consumer to interact with a management service
producer via a specified service interface.
4.2.2 Management service component type A
Management service component type A is a group of management operations and/or notifications agnostic of managed
entities.
4.2.3 Management information
4.2.3.1 Management service component type B
Management service component type B is the management information represented by information model of managed
entities.
The following are examples of Management service component type B:
1) Network resource models of 3GPP defined entities for mobile networks such as those found in [4]
4.2.3.2 Management service component type C
Management service component type C is performance information of the managed entity and fault information of the
managed entity.
The following are examples of Management service component type C:
1. Alarm information as defined in TS 28.xxx [9].
2. Performance data as defined in TS 28.552 [5], TS 28.554 [6] and TS 32.425 [7].
4.3 Combination of management service components
A management service may contain the combination of the following:
1) management service component type A and management service component type B
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 8 ETSI TS 128 533 V15.0.0 (2018-10)
2) management service component type A, management service component type B and management service
component type C.
The instances of management services carry information about specified management service components in the
metadata attributes. Figure 4.3.1.illustrates examples of management service instances with various management
service components of type A, type B and type C:
Figure 4.3.1: Example of Management Service and component type A, B and C
4.4 Management capability exposure governance
As precondition for Management Service exposure governance offer, producer of management capability exposure
governance should have access to:
An association between information about specified management service components and instances of management
services.NOTE: The detail creation of an association is left for implementation and out of scope of 3GPP
standardization.
Management capability exposure governance provides exposure governance on basic elements of management function
service based interface:
1) Management service component type A
2) Management service component type B
3) Management service component type C
As described in Figure 4.4.1 left hand part, when there is a Management Service A exposure without exposure
rd
governance, Management Service A Consumer (e.g. 3 party) can access all management capability offered by
Management Service A Producer.
As described in Figure 4.4.1 right hand part, when Management Service A is exposed with applied exposure
governance it becomes Management Service A. Management Service A Consumer can access Management Service A'
after following steps:
- Management Service A, exposed by Management Service A' Producer, is consumed by Management Service A'
Consumer;
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 9 ETSI TS 128 533 V15.0.0 (2018-10)
- Management Service B, exposed by Management Service B Producer, is consumed by Management Service B
Consumer (e.g. operator) who is authorized to access offered management capabilities exposure governance(s);
- Management Service B Consumer (e.g. operator) request a specified exposure governance on Management
Service A;
- Management Service A Producer produces Management Service A' based on applied exposure governance on
Management Service A.
NOTE: The Management Service A Consumer, the Management Service A' Producer and Management Service B'
Producer can be represented as a single Management Function e.g. a single MF).
Figure 4.4.1: Management capability exposure governance applied on exposed Management Service
A
4.5 Management Function (MF) Concept
A Management Function (MF) is a management entity whose externally-observable behaviour and interfaces are
specified by 3GPP.
In the service-based management architecture MF plays the role of either Management Service producer or
Management Service consumer. A Management Service produced by MF may have multiple consumers. The MF may
consume multiple Management Services from one or multiple Management Service producers. An example of MF
playing both roles (Management Service producer and consumer) illustrated in the figure 4.5.1 below.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 10 ETSI TS 128 533 V15.0.0 (2018-10)
Figure 4.5.1: Example of Management Function and Management Services
Management Functions may interact by consuming Management Services produced by other Management Functions.
The figure 4.6.2 below illustrates multiple scenarios:
- MF1 produces Management Service MnS-a;
- MF2 consumes Management Service MnS-a produced by MF1 and produces Management Services MnS-b and
MnS-c;
- MF3 produces Management Service MnS-c;
- MF4 consumes Management Service MnS-b produced by the MF2;
- MF5 consumes Management Services MnS-c produced by the MF2 and MF3, and in turn produces the same
Management Service MnS-c. The behaviour of MF5 may be seen as aggregation of Management Services MnS-
c.
Figure 4.5.2: An example of interactions between Management Functions
NOTE: The concrete MF is left for implementation and out of scope of 3GPP standardization.
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 11 ETSI TS 128 533 V15.0.0 (2018-10)
4.6 Management data analytics capability
Mobile networks have the capability to support a wide variety of services and requirements. This, along with increasing
flexibility of the network may present management and operational challenges and complexities. The management
system can therefore benefit from management data analytics services for improving networks performance and
efficiency to accommodate and support the diversity of services and requirements. The management data analytics
utilize the network management data collected from the network (including e.g. service, slicing and/or network
functions related data) and make the corresponding analytics based on the collected information. For example, the
information provided by PM data analytics services can be used to optimize network performance, and the information
provided by FM data analytics services can be used to predict and prevent failures of the network. MDAS can be
deployed at different levels, for example, at a domain level (e.g., RAN, CN, NSSI) and/or in a centralized manner (e.g.,
at a PLMN level).
Figure: 4.6.1: Service based architecture for management data analytics
5 Architecture reference model
5.1 General concepts
5.1.1 Management service providers, 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 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 B in turn exposes it to
the entity C.
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 12 ETSI TS 128 533 V15.0.0 (2018-10)
Entity C
The network management
service X is consumed
The network management
service X is produced (exposed)
Entity B
The network management
service X is consumed
The network management
service X is produced
Entity A
Figure 5.1-1. Example of producers and consumers of the management service
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 two
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.
Management Management
service consumer service producer
request
response
Figure 5.1.1.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.
ETSI
---------------------- Page: 13 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 13 ETSI TS 128 533 V15.0.0 (2018-10)
Management Management
service consumer service producer
Subscription request
Subscription Response (positive)
The condition
is met
Notification
The condition
is met
Notification
Figure 5.1.1.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.
5.2 Management interactions with NFV MANO
3GPP management system shall be capable to consume to 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:
- NS LCM.
- LCM VNF, PM, FM, CM on resources supporting VNF.
ETSI
---------------------- Page: 14 ----------------------
3GPP TS 28.533 version 15.0.0 Release 15 14 ETSI TS 128 533 V15.0.0 (2018-10)
Annex A (informative):
Example of deployment model with utilization of
management services
A.1 Utilization of Management services in network and
subnet layers
To deploy a management and orchestration system for the mobile network including network slice(s), the management
system can follow the network and network slice management model, subnetwork and network slice subnet
management model, and network function management model. As an example, management models are shown in
Figure A.1.1, management services in each management model.
Figure A.1.1: Example management layers in layered management model
A.2 Utilization of management services in network
function ma
...