ETSI TR 128 820-2014 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) Federated Network Operation Model (FNOM) Umbr_1.pdf

1、 ETSI TR 128 820 V12.0.0 (2014-10) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Operation Model (FNOM) Umbrella Operation Model (UOM) (3GPP TR 28.820 version 12.0.0 Release 12) TECHNICAL REPORT ETSI ETSI TR 128

2、 820 V12.0.0 (2014-10)13GPP TR 28.820 version 12.0.0 Release 12Reference DTR/TSGS-0528820vc00 Keywords LTE,UMTS 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 enregi

3、stre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org 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

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

5、at. 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send yo

6、ur comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp 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. Th

7、e 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. European Telecommunications Standards Institute 2014. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are T

8、rade Marks of 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. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 128 820 V12.0.0 (2014

9、-10)23GPP TR 28.820 version 12.0.0 Release 12Intellectual 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 ETSI members and non-members, and can be fou

10、nd 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Poli

11、cy, 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. Foreword This Tech

12、nical Report (TR) 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 deliv

13、erables. 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“, “may not“, “need“, “need not“, “will“, “will not“, “can“ and “cann

14、ot“ 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 TR 128 820 V12.0.0 (2014-10)33GPP TR 28.820 version 12.0.0 Releas

15、e 12Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 Umbrella Operation Model (UOM) . 8g34.1 Introduction 8g34.2 Interfac

16、e/Signal diagram 8g34.3 Operations 9g34.3.1 Create Operations Group 9g34.3.1.1 Operation createEntity . 9g34.3.1.1.1 Definition. 9g34.3.1.1.2 Input parameters 9g34.3.1.1.3 Output parameters . 10g34.3.2 Delete Operations Group 11g34.3.2.1 Operation deleteEntitiesWithSc 11g34.3.2.1.1 Definition. 11g34

17、.3.2.1.2 Input parameters 11g34.3.2.1.3 Output parameters . 11g34.3.2.2 Operation deleteEntities 12g34.3.2.2.1 Definition. 12g34.3.2.2.2 Input parameters 12g34.3.2.2.3 Output parameters . 12g34.3.3 Get Operations Group . 13g34.3.3.1 Operation getEntityIdsWithSc . 13g34.3.3.1.1 Definition. 13g34.3.3.

18、1.2 Input parameters 13g34.3.3.1.3 Output parameters . 13g34.3.3.2 Operation getEntitiesWithSc . 14g34.3.3.2.1 Definition. 14g34.3.3.2.2 Input parameters 14g34.3.3.2.3 Output parameters . 14g34.3.3.3 Operation getEntities . 15g34.3.3.3.1 Definition. 15g34.3.3.3.2 Input parameters 15g34.3.3.3.3 Outpu

19、t parameters . 15g34.3.4 Set Operations Group 16g34.3.4.1 Operation setEntitiesWithScAtomic . 16g34.3.4.1.1 Definition. 16g34.3.4.1.2 Input parameters 16g34.3.4.1.3 Output parameters . 16g34.3.4.2 Operation setEntitiesWithSc . 17g34.3.4.2.1 Definition. 17g34.3.4.2.2 Input parameters 17g34.3.4.2.3 Ou

20、tput parameters . 18g34.3.4.3 Operation setEntities . 19g34.3.4.3.1 Definition. 19g3ETSI ETSI TR 128 820 V12.0.0 (2014-10)43GPP TR 28.820 version 12.0.0 Release 124.3.4.3.2 Input parameters 19g34.3.4.3.3 Output parameters . 19g34.4 Notifications . 20g34.4.1 Notification notify 20g34.4.1.1 Definition

21、 20g34.4.1.2 Input parameters 20g34.4.1.3 Output parameters . 20g3Annex A: Interface/Signal diagrams 21g3Annex B: Notification Notify attributes . 22g3Annex C: Change history 24g3History 25g3ETSI ETSI TR 128 820 V12.0.0 (2014-10)53GPP TR 28.820 version 12.0.0 Release 12Foreword This Technical Report

22、 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 i

23、dentifying 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 ch

24、anges 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. ETSI ETSI TR 128 820 V12.0.0 (2014-10)63GPP TR 28.820 version 12.0.0 Release 121 Scope The present document is the result o

25、f the Multi-SDO JWG on Model Alignment which 3GPP TSG SA WG5 (SA5) has developed jointly with TMF and NGMN, and which does not fully follow the 3GPP templates and drafting rules. Therefore 3GPP SA5 has desired to keep the present document as similar as possible to the original, for comparison with t

26、he corresponding TMF version. Thus 3GPP SA5 has done only the strictly necessary changes from the 3GPP drafting rules perspective in order to publish the present document as a 3GPP Technical Report. As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Inform

27、ation Models in the context of FMC basic use cases were developed 3GPP TR 32.833 1, TM Forum TR 166 2. These use cases led to the recognition that it would be necessary to define common operation model elements applicable for wire-line and wireless networks. The present document defines these common

28、 model elements. To be noted: - The Umbrella Operation Model (UOM) described in the present document provides the set of interfaces/operations etc. that have been agreed for convergence to strengthen consistency of representation and semantics of network management operations in the fixed and mobile

29、 environments. - The UOM is necessary but not sufficient for implementation. - The UOM cannot be used directly for implementation. Implementation classes must be derived from those in the UOM by Inheritance or some other appropriate mechanism. - Classes derived from those in the UOM (e.g. for the fi

30、xed environment) may use different names from those used in the UOM. 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, vers

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

32、that document in the same Release as the present document. 1 3GPP TR 32.833: “Telecommunication management; Study on management of converged networks“. 2 TM Forum TR 166: “Information Model Federation Concepts and Principles“. http:/collab.tmforum.org/sf/go/doc13634?nav=1. 3 Fixed Mobile Convergence

33、 (FMC) Federated Network Information Model (FNIM). 4 Fixed Mobile Convergence (FMC) Model Repertoire. ETSI ETSI TR 128 820 V12.0.0 (2014-10)73GPP TR 28.820 version 12.0.0 Release 123 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and defini

34、tions given in Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) 3 apply. 3.2 Symbols For the purposes of the present document, the symbols given in Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) 3 apply. 3.3 Abbreviations For the purposes of the pr

35、esent document, the abbreviations given in Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) 3 and the following apply: FFS For Further Study FMC Fixed Mobile Convergence FNIM Federated Network Information Model FNOM Federated Network Operation Model M Mandatory ME Managed El

36、ement NM Network ManagementNW Network O OptionalOMG Object Management Group SC Selection Criteria SDO Standards Developing Organization UOM Umbrella Operation Model XML Extensible Markup Language XPath XML Path Language ETSI ETSI TR 128 820 V12.0.0 (2014-10)83GPP TR 28.820 version 12.0.0 Release 124

37、 Umbrella Operation Model (UOM) 4.1 Introduction This clause introduces a number of classes and their relations that form the UOM. These classes are defined as the OMG UML defined classifier called interface. The definitions of these classes are implementation neutral in that they only capture the s

38、emantics of the operations. They do not: a) Include syntax or representation of the operation model elements. b) Relate to the information model elements. Various SDOs and organizations are expected to use this interface definition for their definitions of domain/technology-specific “interface“ clas

39、ses. This procedure will maximize the probability of the domain/technology specific concrete “interface“ classes (from various SDOs) being semantically consistent, a necessary characteristic for FMC NM purposes. The set of “interface“ is basic in that their definitions and usage are necessary for th

40、e harmonization of various domain/technology-specific “interface“ classes, forming the so-called FNOM. 4.2 Interface/Signal diagram These Interfaces are abstract. Other Interfaces are for further study. The UML diagrams in figure 4.2-1 do not show operation parameters. See annex A for the UML diagra

41、ms that do. Figure 4.2-1: Interface/Signal diagram ETSI ETSI TR 128 820 V12.0.0 (2014-10)93GPP TR 28.820 version 12.0.0 Release 124.3 Operations 4.3.1 Create Operations Group 4.3.1.1 Operation createEntity 4.3.1.1.1 Definition The client requests the server to create an identifiable entity. It is po

42、ssible to provide an identifier of an existing entity of the same class to be used as the template for the new entity to be created. The operation properties are: Property name Legal values isAtomic True preconditions None postconditions Entity has been created as requested. bulkTransferPattern NONE

43、 emitsEvents False emittedEvents - isOneWay False operationExceptions All mandatory pre-defined Exceptions (see Table 9 of 4). Optional pre-defined Exceptions: CapacityExceeded ObjectExisting supportQualifier M 4.3.1.1.2 Input parameters Parameter Name Documentation and Allowed Values Properties ent

44、ityId This parameter provides the identifier of the entity to be created by the Server. If no identifier is provided, the Server provides a unique identifier. allowedValues: FFS type: DN isOrdered: False isUnique: True defaultValue: No value multiplicity: 1 isBulkPotential: False supportQualifier: M

45、 referenceEntity This parameter provides the identifier of an existing entity that is of the same class as the entity to be created. Attribute values associated with the referenced entity become the default values for those not specified by the attributeList parameter. This parameter may contain no

46、information. allowedValues: Distinguished Name of an existing entity of the same class known by the server. type: DN isOrdered: False isUnique: True defaultValue: No value multiplicity: 1 isBulkPotential: False supportQualifier: O attributeList This parameter provides the entity attribute names and

47、values to be populated to the new entity. These values override the values of the referenceEntity (if the referenceEntity parameter contains information) and the default values property of the entity definition. allowedValues: For the attribute names, only the subject entity class defined attributes

48、. For the attribute values, see the subject entity class attribute allowedValues property. type: AttributeValuePair isOrdered: False isUnique: True defaultValue: No value multiplicity: * isBulkPotential: False supportQualifier: O ETSI ETSI TR 128 820 V12.0.0 (2014-10)103GPP TR 28.820 version 12.0.0

49、Release 124.3.1.1.3 Output parameters None. ETSI ETSI TR 128 820 V12.0.0 (2014-10)113GPP TR 28.820 version 12.0.0 Release 124.3.2 Delete Operations Group 4.3.2.1 Operation deleteEntitiesWithSc 4.3.2.1.1 Definition The client requests the server to delete entities identified by selection criteria. The operation properties are: Property name Legal values isAtomic False preconditions None postconditions Selected entities do not exist. bulkTransferPattern NONE emitsEvents False emittedEvents - isOneWay False operationExceptions All mandatory pre-defined Ex