|
TECHNICAL SPECIFICATION
LTE;
Telecommunication management;
Life Cycle Management (LCM) for mobile networks that include
virtualized network functions;
Procedures
(3GPP TS 28.526 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 1 ETSI TS 128 526 V15.1.0 (2019-04)
Reference
RTS/TSGS-0528526vf10
Keywords
LTE
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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 2019.
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 a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 2 ETSI TS 128 526 V15.1.0 (2019-04)
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.526 version 15.1.0 Release 15 3 ETSI TS 128 526 V15.1.0 (2019-04)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Lifecycle Management procedures . 7
4.1 Introduction . 7
4.2 VNF Instance procedures . 7
4.2.1 VNF Identifier creation . 7
4.2.2 VNF in sta ntiatio n . 7
4.2.2.1 VNF instantiation by EM request. 7
4.2.2.2 VNF instantiation as part of NS update initiated through Os-Ma-nfvo. 8
4.2.2.3 Provide IP address of the managing EM in VNF instantiation . 9
4.2.2.4 Query VNF instance information through Ve-Vnfm-em . 11
4.2.3 VNF scaling . 12
4.2.3.1 Scale VNF instance initiated by EM . 12
4.2.3.2. Scale VNF instance to a level initiated by EM. 12
4.2.3.3 VNF scaling as part of NS scaling initiated through Os-Ma-nfvo . 13
4.2.4 VNF instance termination . 14
4.2.4.1 VNF termination by EM request . 14
4.2.4.2 VNF termination by removing VNF instance from NS . 14
4.2.5 Notifications about VNF lifecycle changes . 15
4.2.6 Autoscaling enabling/disabling . 16
4.2.6.1 Autoscaling enabling/disabling initiated through Ve-Vnfm-em . 16
4.2.6.2 Autoscaling enabling/disabling through Os-Ma-nfvo . 16
4.2.7 Subscribing to VNF lifecycle change notifications through Ve-Vnfm-em . 16
4.2.8 3GPP network function software update when application software is part of VNF Package and
synchronization of VNF instance information is performed through Os-Ma-nfvo . 17
4.3 VNF Package procedures . 17
4.3.1 VNF package on-boarding . 17
4.3.2 VNF Package enabling . 18
4.3.3 VNF Package disabling . 18
4.3.4 VNF Package deleting . 18
4.3.5 Abort VNF package deletion . 19
4.3.6 VNF Package querying . 19
4.3.7 Fetch VNF Package . 20
4.3.8 Notify operation on VNF Package management interface . 20
4.3.9 Subscribe operation on VNF Package management interface . 20
4.3.10 Fetch on-boarded VNF Package artifacts . 21
4.4 NS Instance procedures . 21
4.4.1 NS Instance instantiation . 21
4.4.2 NS Instance termination . 22
4.4.3 NS Instance querying . 23
4.4.3.1 Query NS instance information through Os-Ma-nfvo . 23
4.4.4 NS Instance scaling . 23
4.4.5 NS Instance updating . 24
4.4.5.1 NS update to associate an NS instance to a different NSD version. 24
4.4.5.2 Modifying VNF instance information through Os-Ma-nfvo . 25
4.4.5.3 Modifying VNF instance configuration through Os-Ma-nfvo . 26
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 4 ETSI TS 128 526 V15.1.0 (2019-04)
4.4.5.4 NS update to add a PNF to the NS instance . 26
4.4.5.5 NS update to modify a PNF in the NS instance . 27
4.4.5.6 NS update to remove a PNF from the NS instance . 28
4.4.5.7 NS update to associate an VNF instance with a VNF profile . 29
4.4.5.8 NS update to associate an PNF with a PNF profile . 29
4.4.6 Subscription regarding NS Instance lifecycle changes . 30
4.4.7 Create NS Instance identifier . 30
4.4.8 Delete NS Instance identifier . 31
4.4.9 Procedure for the Notify operation for notifications to NM . 31
4.5 NS Descriptor (NSD) procedures . 32
4.5.1 NSD on-boarding . 32
4.5.2 NSD enabling. 32
4.5.3 NSD disabling . 33
4.5.4 NSD querying . 33
4.5.5 NSD deletion . 34
4.5.6 NSD updating . 34
4.5.7 Subscribe to NSD change notifications . 35
4.5.8 Notify operation for NSD management changes . 35
4.6 PNFD procedures . 36
4.6.1 PNFD on-boarding . 36
4.6.2 PNFD updating . 37
4.6.3 PNFD deletion . 37
4.6.4 PNFD querying . 37
Annex A (informative): Change history . 39
History . 40
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 5 ETSI TS 128 526 V15.1.0 (2019-04)
Foreword
rd
This Technical Specification has been produced by the 3 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
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project Technical Specification
Group Services and System Aspects, Telecommunication Management; as identified below:
TS 28.525: Telecommunication management; Life Cycle Management (LCM) for mobile networks that include
virtualized network functions; Requirements.
TS 28.526: Telecommunication management; Life Cycle Management (LCM) for mobile networks that
include virtualized network functions; Procedures.
TS 28.527: Telecommunication management; Life Cycle Management (LCM) for mobile networks that include
virtualized network functions; Stage 2.
TS 28.528: Telecommunication management; Life Cycle Management (LCM) for mobile networks that include
virtualized network functions; Stage 3.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 6 ETSI TS 128 526 V15.1.0 (2019-04)
1 Scope
The present document specifies the Life Cycle Management (LCM) procedures for mobile networks that include
virtualized network functions.
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 28.500: "Management concept, architecture and requirements for mobile networks that
include virtualized network functions".
[3] 3GPP TS 28.525: "Life Cycle Management (LCM) for mobile networks that include virtualized
network functions; Requirements".
[4] ETSI GS NFV-IFA008 V2.1.1 (2016-10) "Network Function Virtualization (NFV); Management
and Orchestration; Ve-Vnfm Reference Point - Interface and Information Model Specification".
[5] ETSI GS NFV-IFA013 V3.1.2 (2018-08) "Network Function Virtualization (NFV); Management
and Orchestration; Os-Ma-nfvo Reference Point - Interface and Information Model Specification".
[6] 3GPP TS 32.508: "Telecommunication management; Procedure flows for multi-vendor plug-and-
play eNode B connection to the network".
[7] 3GPP TS 32.532: "Telecommunication management; Software management (SwM); Integration
Reference Point (IRP); Information Service (IS)".
[8] ETSI GS NFV-IFA011 V2.1.1 (2016-10) "Network Function Virtualization (NFV); Management
and Orchestration; VNF Packaging Specification".
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], 3GPP TS 28.500 [2]
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 in 3GPP TS 28.500 [2].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], 3GPP TS 28.500 [2] 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] or in 3GPP TS 28.500 [2].
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 7 ETSI TS 128 526 V15.1.0 (2019-04)
4 Lifecycle Management procedures
4.1 Introduction
The procedures listed in clause 4, as some of all the possibilities, are not exhaustive.
4.2 VNF Instance procedures
4.2.1 VNF Identifier creation
Figure 4.2.1-1 depicts the procedure of VNF instance identifier creation initiated through Ve-Vnfm-em reference point
(see clause 7.2.2 of GS NFV-IFA008 [4])
1. EM sends to VNFM a CreateVnfIdentifierRequest with parameter vnfdId, vnfInstanceName and
vnfInstanceDescription to create a VNF instance identifier (vnfInstanceId) and an associated
instance of an NsInfo information element (see clause 7.2.2.2 of GS NFV-IFA008 [4]).
2. VNFM sends to EM a CreateVnfIdentifierResponse with parameter vnfInstanceId identifying the instance
identifier of the VNF has been created (see clause 7.2.2.3 of GS NFV-IFA008 [4]).
3. VNFM sends to EM a Notify (see clause 7.3.3 of GS NFV-IFA008 [4]) carrying
VnfIdentifierCreationNotification information element with attribute vnfInstanceId to
indicate the VNF instance identifier creation (see clause 9.5.7 of GS NFV-IFA008 [4]).
VNFM
EM
1. CreatesVnfIdentifierRequest
2. CreateVnfIdentifierResponse
3. Notify
Figure 4.2.1-1 Procedures of VNF identifier creation
4.2.2 VNF instantiation
4.2.2.1 VNF instantiation by EM request
Figure 4.2.2.1-1 depicts a procedure of VNF instantiation by EM request. It is assumed that EM has subscribed to
receive the VNF lifecycle change notification from VNFM. As a result of this procedure, the new VNF instance is not
associated to any NS (see NOTE in clause 7.2.3.4 in [4]).
1. EM sends CreateVnfRequest to VNFM with vnfDescriptorId, vnfInstanceName, and
vnfInstanceDescription to create the VNF identifier (see clause 7.2.2 [4]).
2. VNFM sends CreateVnfResponse to EM with vnfInstanceId to indicate the creation of a new instance of a
VNF information element (see clause 7.2.2.3 [4]).
3. EM sends InstantiateVnfRequest to VNFM with input parameters, listed in clause 7.2.3.2 [4] to instantiate a
VNF (see clause 7.2.3 [4]).
4. VNFM sends InstantiateVnfResponse with lifecycleOperationOccurrenceId to EM (see clause 7.2.3.3
[4]).
5. VNFM send a Notify (see clause 7.5.3 [4]), carrying VnfLifecycleChangeNotification information
element to EM with attributes vnfInstanceId, status = “start”, operation = “instantiation”,
lifeycleOperationOccurrenceId, affectedVnfc, affectedVl, and
affectedVirtualStorage to indicate the start of VNF instantiation (see clause 9.5.1 [4]).
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 8 ETSI TS 128 526 V15.1.0 (2019-04)
6. VNFM send a Notify (see clause 7.5.3 [4]), carrying VnfLifecycleChangeNotification information
element to EM with attributes vnfInstanceId, status = “result”, operation = “instantiation”,
lifeycleOperationOccurrenceId, affectedVnfc, affectedVl, and
affectedVirtualStorage to indicate the result of VNF instantiation, when the VNF instantiation
operation is completed (see clause 9.5.1 [4]).
EM VNFM
1. CreateVnfRequest
2. CreateVnfResponse
3. InstantiateVnfRequest
4. InstantiateVnfResponse
5. Notify
6. Notify
Figure 4.2.2.1-1: VNF instantiation procedure
4.2.2.2 VNF instantiation as part of NS update initiated through Os-Ma-nfvo
Figure 4.2.2.2-1 depicts the procedure of instantiating a VNF instance as part of an NS update through the Os-Ma-nfvo
reference point (see clause 7.3.5 [5]).
1. NM sends to NFVO an UpdateNsRequest with parameters nsInstanceId, updateType =
"InstantiateVnf", instantiateVnfData, and updateTime to instantiate the VNF instance (see clause
7.3.5.2 [5]). The instantiateVnfData contains the parameters that are needed for VNF instantiation,
including vnfdId, flavourId, and can include in addition the parameters instantiationLevelId,
vnfInstanceName, etc (see clause 8.3.4.12 [5]).
2. NFVO sends to NM an UpdateNsResponse with parameter lifecycleOperationOccurrenceId
providing the identifier of the NS lifecycle operation occurrence (see clause 7.3.5.3 [5]).
3. NFVO sends to NM a Notify (see clause 7.4.3 [5]), carrying NsLifecycleChangeNotification
information element with attributes nsInstanceId, lifecycleOperationOccurrenceId,
operation = "UpdateNs", and notificationType = "start" to indicate the start of the NS update that
includes the VNF instantiation (see clause 8.3.2.2 [5]).
4. NFVO sends to NM a Notify (see clause 7.4.3 [5]), carrying NsLifecycleChangeNotification
information element with attributes nsInstanceId, lifecycleOperationOccurrenceId,
operation = "UpdateNs", notificationType = "result" to indicate the end result of the NS update that
includes the VNF instantiation, and affectedVnf providing information about the added VNF instance. The
affectedVnf includes parameters vnfInstanceId, vnfdId, vnfProfileId, vnfName and
changeType = "instantiated" (see clauses 8.3.2.2 and 8.3.2.3 [5]).
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 9 ETSI TS 128 526 V15.1.0 (2019-04)
NFVO
NM
1. UpdateNsRequest
2. UpdateNsResponse
3. Notify
4. Notify
Figure 4.2.2.2-1: VNF instantiation as part of NS update initiated through Os-Ma-nfvo
4.2.2.3 Provide IP address of the managing EM in VNF instantiation
Figure 4.2.2.3-1 depicts a procedure of providing the IP address of the managing EM to the VNF in instantiation. As a
result of this procedure, the new VNF instance is not associated to any NS (see NOTE in clause 7.2.3.4 in [4]). The
figure uses UML notation to show multiple options available.
1. EM sends CreateVnfIdentifierRequest with parameters vnfdId, and optionally vnfInstanceName and
vnfInstanceDescription to VNFM (see clause 7.2.2 [4]).
2. VNFM creates a new VnfInfo object
3. VNFM sends CreateVnfIdentifierResponse with the new VNF identifier to EM (see clause 7.2.2 [4]).
If the Multi-vendor Plug and Play connection to the network method is not used and managing EM IP address is
provided as VNF configuration data, the steps 4.1.1 through 4.1.4 are executed.
4.1.1. EM sends ModifyVnfConfigurationRequest with parameters vnfInstanceId,
vnfConfigurationData, extVirtualLink and vnfcConfigurationData to VNFM (see clause
7.6.2 [4]). The managing EM IP address value used in parameter vnfConfigurationData.
4.1.2. VNFM sets the vnfConfigurationData in the vnfInfo object.
4.1.3. VNFM sends ModifyVnfConfigurationResponse to EM (see clause 7.6.2 [4]).
4.1.4. EM sends InstantiateVnfRequest with parameters vnfInstanceId, flavourId,
instantiationLevelId, extVirtualLink, extManagedVirtualLink,
localizationLanguage and additionalParam to VNFM (see clause 7.2.3 [4]).
Note: The extVirtualLink may be known to the EM (e.g. provided by another entity).
If the Multi-vendor Plug and Play connection to the network method is not used and managing EM IP address is
provided as additional parameter for instantiation, the steps 4.2.1 through 4.2.3 are executed.
4.2.1. EM sends InstantiateVnfRequest with parameters vnfInstanceId, flavourId,
instantiationLevelId, extVirtualLink, extManagedVirtualLink,
localizationLanguage and additionalParam to VNFM (see clause 7.2.3 [4]). The managing EM IP
address value used in parameter additionalParam.
4.2.2. VNFM maps the managing EM IP address value received in parameter additionalParam of
InstantiateVnfRequest to vnfConfigurationData (see Note 1).
NOTE 1: the specific mechanism for this mapping (e.g. vendor specific LCM script or specific VNFM) is out of
scope of 3GPP
4.2.3. VNFM sets the vnfConfigurationData in the vnfInfo object.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 28.526 version 15.1.0 Release 15 10 ETSI TS 128 526 V15.1.0 (2019-04)
If the Multi-vendor Plug and Play connection to the network method is used to provide the managing EM IP address
to VNF, step 4.3.1 is executed.
4.3.1. EM sends InstantiateVnfRequest with parameters vnfInstanceId, flavourId,
instantiationLevelId, extVirtualLink, extManagedVirtualLink,
localizationLanguage and additionalParam to VNFM (see clause 7.2.3 [4]).
5. VNFM initiates the VNF instantiation process.
6. VNFM sends InstantiateVnfResponse with the
...