ETSI TS 128 510-2018 LTE Telecommunication management Configuration Management (CM) for mobile networks that include virtualized network functions Requirements (V15 0 0 3GPP TS 28 .pdf

《ETSI TS 128 510-2018 LTE Telecommunication management Configuration Management (CM) for mobile networks that include virtualized network functions Requirements (V15 0 0 3GPP TS 28 .pdf》由会员分享，可在线阅读，更多相关《ETSI TS 128 510-2018 LTE Telecommunication management Configuration Management (CM) for mobile networks that include virtualized network functions Requirements (V15 0 0 3GPP TS 28 .pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 128 510 V15.0.0 (2018-07) LTE; Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Requirements (3GPP TS 28.510 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 128 510 V15.0.0 (2018-07)13GPP TS 28.510 ve

2、rsion 15.0.0 Release 15Reference RTS/TSGS-0528510vf00 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/

3、88 Important 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

4、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 doc

5、ument 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

6、of the 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

7、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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its M

8、embers. 3GPPTM and LTETMare 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. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 128 510 V15.0.0 (201

9、8-07)23GPP TS 28.510 version 15.0.0 Release 15Intellectual 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-me

10、mbers, 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/). Pursua

11、nt 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 docum

12、ent. 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 traden

13、ame. 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 doc

14、ument 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 http:/weba

15、pp.etsi.org/key/queryform.asp. 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 provi

16、sions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 128 510 V15.0.0 (2018-07)33GPP TS 28.510 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Sco

17、pe 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Background and concepts . 6g34.1 Configuration management in the context of NFV 6g35 Business level requirements . 6g35.1 Requirements 6g35.2 Actor roles 7g35.3 Telecommunications resources 7g35.4

18、High-level use cases . 7g35.4.1 Create Managed Object for Network Element in the context of NFV 7g35.4.2 Delete MOI(s) for Network Element in the context of NFV 7g35.4.3 Update the configuration parameters corresponding to the subject VNF instance (application part) after a VNF instance is scaled .

19、8g35.4.4 Retrieve virtualized NE information by NM 8g36 Specification level requirements 8g36.1 Requirements 8g36.1.1 Requirements for Itf-N 8g36.1.2 Requirements for Os-Ma-nfvo 9g36.1.3 Requirements for Ve-Vnfm-em 9g36.1.4 Requirements for Ve-Vnfm-vnf 9g36.2 Actor roles 9g36.3 Telecommunication res

20、ources 9g36.4 Use cases 9g36.4.1 MOI creation related use cases . 9g36.4.1.1 Introduction . 9g36.4.1.2 Create MOI(s) after a VNF is instantiated (Triggered by NM) . 10g36.4.1.3 Create MOI(s) after a VNF is instantiated (Triggered by EM) . 11g36.4.1.4 Create MOI(s) for a specified VNF instance (Trigg

21、ered by NM) . 11g36.4.1.5 Associate MOI(s) with a VNF instance (Triggered by NM) . 12g36.4.1.6 Bulk MOIs creation . 13g36.4.2 Configure VNF instance with Managed Object attributes 15g36.4.3 Delete the MOI(s) corresponding to a VNF instance (application part) . 16g36.4.4 Update the MOI(s) correspondi

22、ng to the subject VNF instance (application part) after a VNF instance is scaled (Triggered by NM) . 16g36.4.5 Update the MOI(s) corresponding to the subject VNF instance (application part) after a VNF instance is scaled (Triggered by EM) . 17g36.4.6 Void 17g36.4.7 Void 17g36.4.8 Void 17g36.4.9 Enab

23、le/disable the auto-scaling of the VNF instance(s) corresponding to an NE 17g36.4.10 VNF instance information synchronization 18g3Annex A (informative): Change history . 19g3History 20 ETSI ETSI TS 128 510 V15.0.0 (2018-07)43GPP TS 28.510 version 15.0.0 Release 15Foreword This Technical Specificatio

24、n 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 an

25、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 c

26、hanges 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 Specific

27、ation Group Services and System Aspects, Telecommunication Management; as identified below: TS 28.510: Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Requirements. TS 28.511: Telecommunication management; Configuration Mana

28、gement (CM) for mobile networks that include virtualized network functions; Procedures. TS 28.512: Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Stage 2. TS 28.513: Telecommunication management; Configuration Management (C

29、M) for mobile networks that include virtualized network functions; Stage 3. ETSI ETSI TS 128 510 V15.0.0 (2018-07)53GPP TS 28.510 version 15.0.0 Release 151 Scope The present document (together with the relevant requirements described in 1, 2, 3 and 4) specifies the requirements applicable to Config

30、uration Management (CM) of 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,

31、 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 docume

32、nt in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 4 3GPP TS 28.5

33、00: “Telecommunication management; Management concept, architecture and requirements for mobile networks that include virtualized network functions“. 5 ETSI GS NFV-IFA 008 (V2.1.1): “Network Function Virtualisation (NFV); Management and Orchestration; Ve-Vnfm reference point - Interface and Informat

34、ion Model Specification“. 6 ETSI GS NFV-IFA 010 (V2.1.1): “Network Functions Virtualisation (NFV); Management and Orchestration; Functional requirements specification“. 7 ETSI GS NFV-IFA 013 (V2.1.1): “Network Function Virtualisation (NFV); Management and Orchestration; Os-Ma-nfvo reference point -

35、Interface and Information Model Specification“. 8 3GPP TS 28.525: “Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Requirements“. 9 3GPP TS 32.612: “Telecommunication management; Configuration Management (CM); Bulk CM Integrat

36、ion Reference Point (IRP): Information Service (IS)“ 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 in 3GPP TS 28.500 4 and the following apply. A term defined in the present document takes precedence

37、over the definition of the same term, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 4. VNF application specific parameters: parameters for realizing the network element function. NOTE: VNF application specific parameters are defined by 3GPP. Examples can be network element name, network element a

38、ddress, etc. VNF non-application specific parameters: parameters for instantiating/scaling/terminating a VNF instance. NOTE: VNF non-application specific parameters are defined by ETSI NFV ISG and are related to the VNF deployment on virtualized infrastructure. An example can be VM parameters. ETSI

39、ETSI TS 128 510 V15.0.0 (2018-07)63GPP TS 28.510 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and in 3GPP TS 28.500 4 and the following apply. An abbreviation defined in the present document takes precedence over the

40、 definition of the same abbreviation, if any, in 3GPP TR 21.905 1 or in 3GPP TS 28.500 4. MO Managed Object MOI Managed Object Instance 4 Background and concepts 4.1 Configuration management in the context of NFV 3GPP Configuration Management (CM) has system modification functions and system monitor

41、ing functions (as described in 3). The decoupling of software and hardware in NFV gives rise to the need to model the VNF application specific parameters (i.e. 3GPP service related) by 3GPP whilst modelling the VNF non-application specific parameters (i.e. non-3GPP service related) in ETSI GS NFV-IF

42、A 008 5. For Configuration Management, NM and EM manage NEs and NRs and the related configuration parameters (e.g. identification, port, neighbour relation) which are modelled as the MO(s) and MO attributes. The MO attributes, which are defined by 3GPP, typically are VNF application specific paramet

43、ers. 5 Business level requirements 5.1 Requirements REQ-NFV_CM-CON-1 EM shall be able to perform necessary virtualized network function configuration due to the VNF lifecycle management from VNFM: - Add the VNF as managed node after VNF instantiation. - Remove the VNF from managed nodes after VNF te

44、rmination. - Configure the VNF after some VNF LCM operations (i.e. instantiation). - Re-configure the VNF after some VNF LCM operations (e.g. scaling, update/upgrade, etc.). REQ-NFV_CM-CON-2 3GPP management system shall have a capability to create MO(s) corresponding to a VNF instance. REQ-NFV_CM-CO

45、N-3 3GPP management system shall have a capability to configure the MO(s) corresponding to a VNF instance. REQ-NFV_CM-CON-4 Void REQ-NFV_CM-CON-5 Void REQ-NFV_CM-CON-6 Void REQ-NFV_CM-CON-7 Void REQ-NFV_CM-CON-8 3GPP management system shall have a capability to delete MOI(s) related to a VNF instanc

46、e. REQ-NFV_CM-CON-9 NM shall have a capability retrieving views of virtualized NEs from various management systems (e.g. EM, NFVO). REQ-NFV_CM-CON-10 3GPP management system shall have a capability to manage bulk creation of MOIs representing NEs whose software components are designed to run on NFVI.

47、 ETSI ETSI TS 128 510 V15.0.0 (2018-07)73GPP TS 28.510 version 15.0.0 Release 155.2 Actor roles See detailed actors and roles for each use case in clause 5.4. 5.3 Telecommunications resources See detailed telecommunication resources for each use case in clause 5.4. 5.4 High-level use cases 5.4.1 Cre

48、ate Managed Object for Network Element in the context of NFV Use Case Stage Evolution / Specification Related use Goal To create Managed Object (MO) for a new NE that includes virtualized network functions. Actors and Roles 3GPP management system (EM, NM) creates MO for NE. NFV MANO system instantia

49、tes VNF instance and configures VNF non-application specific parameters for VNF instance. Telecom resources NFV MANO system (NFVO, VNFM), 3GPP management system (EM, NM) Assumptions NFV MANO system has already instantiated a VNF instance using the related VNF Package. Pre conditions N/A Begins when Operator has decided to create MO for a new NE. Step 1 (M) 3GPP management system adds the VNF instance as a NE MO. 3GPP management system can configure the VNF instance with application specific parameters during the creation process o