ETSI TS 128 620-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Um.pdf

《ETSI TS 128 620-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Um.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 128 620-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Um.pdf（27页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 128 620 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM) (3GPP TS 28.620 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI

2、ETSI TS 128 620 V14.0.0 (2017-04)13GPP TS 28.620 version 14.0.0 Release 14Reference RTS/TSGS-0528620ve00 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 lucr

3、atif enregistre la Sous-Prfecture de Grasse (06) N 7803/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 p

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

5、 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors i

6、n the present document, please send your comment to one 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 a

7、s 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. European Telecommunications Standards Institute 2017. All rights reserved. DECT

8、TM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade 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 A

9、ssociation. ETSI ETSI TS 128 620 V14.0.0 (2017-04)23GPP TS 28.620 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 fo

10、r 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 (http

11、s:/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, essen

12、tial 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 interpre

13、ted 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“,

14、 “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 ETSI TS 128 620 V14.0.0 (2017-04)3

15、3GPP TS 28.620 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 UIM Partition operational . 7g34.1 Introduction 7g34.2 C

16、lass diagram . 7g34.3 Class definitions . 8g34.3.1 Domain_ . 8g34.3.1.1 Definition 8g34.3.1.2 Attributes . 9g34.3.2 ManagedElement_ 9g34.3.2.1 Definition 9g34.3.2.2 Attributes . 9g34.3.3 Function_ . 9g34.3.3.1 Definition 9g34.3.3.2 Attributes . 9g34.3.4 ManagementSystem_ 10g34.3.4.1 Definition 10g34

17、.3.4.2 Attributes . 10g34.3.5 TopologicalLink_ 10g34.3.5.1 Definition 10g34.3.5.2 Attributes . 10g34.3.6 TerminationPointEncapsulation_ . 10g34.3.6.1 Definition 10g34.3.6.2 Attributes . 11g34.3.6.3 Attribute constraints 11g34.3.7 LayerTermination_ 11g34.3.7.1 Definition 11g34.3.7.2 Attributes . 12g3

18、4.3.7.3 Attribute constraints 12g34.3.8 Top_ . 12g34.3.8.1 Definition 12g34.3.8.2 Attributes . 12g35 UIM Partition inventory 12g36 UIM Class attribute definitions . 13g36.1 Attribute properties. 13g3Annex A (informative): Extract from 3GPP TS 32.622 Generic network resources IRP: NRM 17g3Annex B (in

19、formative): Extract from MTOSI documents . 18g3Annex C (informative): Rationale and Usage of TPE/LT . 23g3Annex D (informative): Change history . 25g3History 26g3ETSI ETSI TS 128 620 V14.0.0 (2017-04)43GPP TS 28.620 version 14.0.0 Release 14Foreword This Technical Specification has been produced by

20、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 identifying change of r

21、elease 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.

22、e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 128 620 V14.0.0 (2017-04)53GPP TS 28.620 version 14.0.0 Release 141 Scope As a result of the analysis of the requirements for the ha

23、rmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed 6, 14. These use cases led to the recognition that it would be necessary to define common model elements applicable for wire-line and wireless networks. This document defines these common mod

24、el elements. To be noted: - The Umbrella Information Model (UIM) described in this document provides the set of classes etc. that have been agreed for convergence to strengthen consistency of representation in the fixed and mobile environments. For full management of an FNIM solution many other clas

25、ses will be required in addition to those in the UIM. - The UIM is necessary but not sufficient for implementation. - The UIM cannot be used directly for implementation. Implementation classes must be derived from those in the UIM by Inheritance or some other appropriate mechanism. - Classes derived

26、 from those in the UIM (e.g. for the fixed environment) must use different names from those used in the UIM. - Where an implementation class is essentially identical to the abstract class defined in UIM the name of the implementation class should be the same as that of the UIM minus the underscore,

27、e.g. the UIM class “Function_” would become “Function”. 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, e

28、tc.) 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

29、 in the same Release as the present document. 1 ATM Forum, Technical Committee, Network Management, M4 Network View CMIP MIB Specification, “CMIP Specification for the M4 Interface“, Sep, 1995. 2 3GPP TS 32.xyz series on NRM. 3 3GPP TS 32.300 “Telecommunication management; Configuration Management;

30、Name convention for Managed Objects“. 4 3GPP S5-102610 “S5vTMFa033 E NSN Proposed enhancement of Generic NRM IOCs v3“. 5 3GPP TS 32.622 “Generic network resources IRP: NRM“. 6 3GPP TR 32.833 “Study on Management of Converged Networks“ (3GPP SA5). 7 TM Forum GB922,“Information Framework (SID) Suite,

31、Release 9.5“http:/www.tmforum.org/DocumentsInformation/GB922InformationFramework/45189/article.html. 8 TM Forum MTOSI 2.1:(http:/www.tmforum.org/MTOSIRelease21/11998/home.html). 9 TM Forum “SD1-44_ConnectionlessTechnologyManagement.pdf“(part of 0) (Especially Appendix III Mapping MEF MTNMETH). ETSI

32、ETSI TS 128 620 V14.0.0 (2017-04)63GPP TS 28.620 version 14.0.0 Release 1410 TM Forum “SD1-7_DSLOverview.pdf“ (part of 0). 11 TM Forum “SD1-18_layers.pdf“ (part of 0) (Especially “4.2.7 ATM and SDH capable STM-4“). 12 TM Forum “Connectionless, Connection Oriented Convergence and TP Modelling“ (http:

33、/tmforum.org/FeatureDescription/ConnectionlessConnection/41718/article.html). 13 TM Forum TR 146 “Lifecycle Compatibility Release 1.0“ (http:/www.tmforum.org/TechnicalReports/TR146LifecycleCompatibility/36664/article.html). 14 TM Forum TR 166 “Information Model Federation Concepts and Principles“ (h

34、ttp:/collab.tmforum.org/sf/go/doc13634?nav=1). 15 Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM). 16 TM Forum MTOSI “SD1-25_objectNaming.pdf“ (part of 0). 17 ITU-T X.200 (07/1994) “Information technology Open Systems Interconnection Basic Reference Model: The basic model“.

35、 3 Definitions and abbreviations 3.1 Definitions For the purposes of this document, the following definitions, symbols and abbreviations apply. For definitions, symbols and abbreviations not found here. See also Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) 0.3.2 Symbols

36、3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 x and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 x. AS Application Server (3GPP) BBF Broadban

37、d ForumCIM Common Information Model (DMTF) CP Connection Point DM Domain Manager DN Distinguished Name DTMF Distributed Management Task Force EM Element Manager FNIM Federated Network Information Model FMC Fixed Mobile Convergence HLR Home Location Register (3GPP) IOC Information Managed Object IRP

38、Integration Reference Point (3GPP) LR Layer Rate LT Layer Termination ME Managed ElementMTNM Multi Technology Network Management (TM Forum) MTOSI Multi Technology Operations System Interface (TM Forum) NE Network Element NM Network Management NRM Network Resource Model (3GPP) NW Network SDO Standard

39、s Development Organization SID Shared Information b) Relate to the protocol used to create/delete/read/write/modify the NM information. Various SDOs and organizations are expected to use the UIM classes for definition of Domain/Technology-specific model classes. This procedure will maximize the prob

40、ability of the domain/technology specific concrete classes (from various SDOs) being semantically consistent, a necessary characteristic for FMC NM purposes. Currently, 3GPP SA5 defines its abstract classes in its Generic NRM IRP 0 and defines concrete classes in other NRM IRPs such as EUTRAN NRM IR

41、P. 3GPP/SA5 have agreement and will consider changes in classes in its Generic NRM IRP such that they are harmonized (if not identical) to those (to-be-defined) as UIM classes. Classes from other IRPs that are relevant for consideration in the UIM are likely to be reflected in some way in the Generi

42、c NRM IRP for use in the UIM. 4.2 Class diagram The criteria for choosing these classes is their relevance to (e.g. can be used by) Domain/Technology-specific model classes (e.g. 3GPP/SA5 network resource model 0, BBF ATM network management model Error! Reference source not found., TMF MTNM, DMTF CI

43、M)” Note that this set of classes is basic in that their definitions and usage are necessary for the harmonization of various Domain/Technology-specific model classes, forming the so-called FNIM. These classes are abstract. Other classes are for further study. - Domain_ (similar to SubNetwork of 3GP

44、P 0 and MultiLayerSubNetwork of SID/MTOSI 0) - Function_ (similar to ManagedFunction of 3GPP 0 and LogicalResource of SID/MTOSI 0) - LayerTermination_ (similar to a single layer in the layerParameterList_T structure of SID/MTOSI 7) - ManagedElement_ (similar to ManagedElement of 3GPP 0 and SID/MTOSI

45、 0) - ManagementSystem_ (similar to ManagementNode of 3GPP 0 and OperationsSystem of SID/MTOSI 7) - TerminationPointEncapsulation_ (similar to TerminationPoint of SID/MTOSI 0) - Top_ (similar to Top 0 of 3GPP and RootEntity of SID/MTOSI 0) - TopologicalLink_ (similar to Link 0 of 3GPP and Topologica

46、lLink of SID/MTOSI 0) ETSI ETSI TS 128 620 V14.0.0 (2017-04)83GPP TS 28.620 version 14.0.0 Release 14Figure 1: Class diagram Note: The above class diagram shows the naming and as well as inheritance relations. Figure 2: Inheritance class diagram 4.3 Class definitions 4.3.1 Domain_ 4.3.1.1 Definition

47、 This class groups managed entities: - Such that the group represents a topological structure which describes the potential for connectivity; - Subject to common administration; - With common characteristics. ETSI ETSI TS 128 620 V14.0.0 (2017-04)93GPP TS 28.620 version 14.0.0 Release 14A domain is

48、a partition of instances of managed entities. 4.3.1.2 Attributes Attribute Name Support Qualifier isReadable isWritable isInvariant isNotifyable dnPrefix M M - - M T F F T userLabel M M M - M T T F T userDefinedNetworkType M M M - M T T F T 4.3.2 ManagedElement_ 4.3.2.1 Definition This (and its cont

49、ained Function_(s) represents telecommunications resources (e.g. equipment) within the telecommunications network. This group performs Managed Element (ME) functions, e.g., provides support and/or service to the subscriber. This can also provide access to a grouping of equipments for management purposes. An ME communicates with a manager (directly or indirectly) for the purpose of being monitored and/or controlled. MEs may or may not additionally perform element managemen