1、 ETSI TS 128 526 V14.0.0 (2017-05) LTE; Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Procedures (3GPP TS 28.526 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 128 526 V14.0.0 (2017-05)13GPP TS 28.526 versio
2、n 14.0.0 Release 14Reference DTS/TSGS-0528526ve00 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 I
3、mportant notice The present document can be downloaded from: http:/www.etsi.org/standards-search 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 writ
4、ten 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 documen
5、t 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of t
6、he following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx 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 t
7、he PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of
8、ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks 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 Trade Marks registered and owned by the GSM Assoc
9、iation. ETSI ETSI TS 128 526 V14.0.0 (2017-05)23GPP TS 28.526 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ET
10、SI 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:/i
11、pr.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
12、 to the present document. 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
13、as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “wi
14、ll“, “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 ETSI TS 128 526 V14.0.0 (2017-05)33GPP
15、 TS 28.526 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Lifecycle Management procedures 7g34.1 Intro
16、duction 7g34.2 VNF Instance procedures . 7g34.2.1 VNF Identifier creation . 7g34.2.2 VNF instantiation 7g34.2.2.1 VNF instantiation by EM request 7g34.2.2.2 VNF instantiation as part of NS update initiated through Os-Ma-nfvo. 8g34.2.2.3 Provide IP address of the managing EM in VNF instantiation . 9g
17、34.2.2.4 Query VNF instance information through Ve-Vnfm-em 11g34.2.3 VNF scaling 12g34.2.3.1 Scale VNF instance initiated by EM . 12g34.2.3.2. Scale VNF instance to a level initiated by EM 12g34.2.3.3 VNF scaling as part of NS scaling initiated through Os-Ma-nfvo 13g34.2.4 VNF instance termination .
18、 14g34.2.4.1 VNF termination by EM request . 14g34.2.4.2 VNF termination by removing VNF instance from NS 14g34.2.5 Notifications about VNF lifecycle changes 15g34.2.6 Autoscaling enabling/disabling . 16g34.2.6.1 Autoscaling enabling/disabling initiated through Ve-Vnfm-em . 16g34.2.6.2 Autoscaling e
19、nabling/disabling through Os-Ma-nfvo . 16g34.2.7 Subscribing to VNF lifecycle change notifications through Ve-Vnfm-em . 16g34.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 . 1
20、7g34.3 VNF Package procedures . 17g34.3.1 VNF package on-boarding 17g34.3.2 VNF Package enabling . 18g34.3.3 VNF Package disabling 18g34.3.4 VNF Package deleting 19g34.3.5 Abort VNF package deletion 19g34.3.6 VNF Package querying . 19g34.3.7 Fetch VNF Package 20g34.3.8 Notify operation on VNF Packag
21、e management interface 20g34.3.9 Subscribe operation on VNF Package management interface 21g34.3.10 Fetch on-boarded VNF Package artifacts . 21g34.4 NS Instance procedures 22g34.4.1 NS Instance instantiation 22g34.4.2 NS Instance termination 23g34.4.3 NS Instance querying 23g34.4.3.1 Query NS instan
22、ce information through Os-Ma-nfvo . 23g34.4.4 NS Instance scaling . 24g34.4.5 NS Instance updating 25g34.4.5.1 NS update to associate an NS instance to a different NSD version. 25g34.4.5.2 Modifying VNF instance information through Os-Ma-nfvo . 25g3ETSI ETSI TS 128 526 V14.0.0 (2017-05)43GPP TS 28.5
23、26 version 14.0.0 Release 144.4.5.3 Modifying VNF instance configuration through Os-Ma-nfvo 26g34.4.6 Subscription regarding NS Instance lifecycle changes . 27g34.4.7 Create NS Instance identifier 27g34.4.8 Delete NS Instance identifier 28g34.4.9 Procedure for the Notify operation for notifications
24、to NM . 28g34.5 NS Descriptor (NSD) procedures . 29g34.5.1 NSD on-boarding 29g34.5.2 NSD enabling 29g34.5.3 NSD disabling . 30g34.5.4 NSD querying . 30g34.5.5 NSD deletion 31g34.5.6 NSD updating . 31g34.5.7 Subscribe to NSD change notifications 32g34.5.8 Notify operation for NSD management changes 3
25、2g34.6 PNFD procedures . 33g34.6.1 PNFD on-boarding 33g34.6.2 PNFD updating . 34g34.6.3 PNFD deletion 34g34.6.4 PNFD querying . 34g3Annex A (informative): Change history . 36g3History 37g3ETSI ETSI TS 128 526 V14.0.0 (2017-05)53GPP TS 28.526 version 14.0.0 Release 14Foreword This Technical Specifica
26、tion has been produced by the 3rdGeneration 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
27、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 al
28、l 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 present document is part of a TS-family covering the 3rdGeneration Partnership Project Technical Speci
29、fication 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 Manage
30、ment (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) fo
31、r mobile networks that include virtualized network functions; Stage 3. ETSI ETSI TS 128 526 V14.0.0 (2017-05)63GPP TS 28.526 version 14.0.0 Release 141 Scope The present document specifies the Life Cycle Management (LCM) procedures for mobile networks that include virtualized network functions, whic
32、h can be part of EPC or IMS. 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
33、 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
34、 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
35、 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 V2.1.1 (2016-10) “Network Function Virtualization (NFV); Manag
36、ement 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 manageme
37、nt (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,
38、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. ETSI ETSI TS 128 526 V14.0.0 (2017-05)73GPP TS 28.526 versi
39、on 14.0.0 Release 143.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.
40、905 1 or in 3GPP TS 28.500 2. 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
41、 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 informati
42、on 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
43、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). Figure 4.2.1-1 Procedures of VNF identifier creation 4.2.2 VNF instantiation 4.2.2.1 VNF instantiation by EM request
44、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 Cre
45、ateVnfRequest to VNFM with vnfDescriptorId, vnfInstanceName, and vnfInstanceDescription to create the VNF identifier (see clause 7.2.2 4). EM VNFM 3. Notify 1. CreatesVnfIdentifierRequest 2. CreateVnfIdentifierResponse ETSI ETSI TS 128 526 V14.0.0 (2017-05)83GPP TS 28.526 version 14.0.0 Release 142.
46、 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
47、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”, lifeycleOperationOccurr
48、enceId, affectedVnfc, affectedVl, and affectedVirtualStorage to indicate the start of VNF instantiation (see clause 9.5.1 4). 6. VNFM send a Notify (see clause 7.5.3 4), carrying VnfLifecycleChangeNotification information element to EM with attributes vnfInstanceId, status = “result”, operation = “i
49、nstantiation”, 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). g28g68g1005g856g3g18g396g286g258g410g286g115g374g296g90g286g395g437g286g400g410g3g1006g856g3g18g396g286g258g410g286g115g374g296g90g286g400g393g381g374g400g286g3g115g69g38g68g1007g856g3g47g374g400g410g258g374g410g349g258g410g286g115g374g296g90g286g395g437g286g400g410g3g1010g856g3g69g381g410g349g296g455g1
