ETSI TS 132 156-2016 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fixed Mobile Convergence (FMC) model repertoire (V13 0 0 3GPP TS 32 156 vers.pdf

1、 ETSI TS 1Universal Mobile TelTelecommFixed Mobile Con(3GPP TS 32.1TECHNICAL SPECIFICATION132 156 V13.0.0 (2016elecommunications System (LTE; munication management; nvergence (FMC) model reper.156 version 13.0.0 Release 1316-02) (UMTS); ertoire 13) ETSI ETSI TS 132 156 V13.0.0 (2016-02)13GPP TS 32.1

2、56 version 13.0.0 Release 13Reference RTS/TSGS-0532156vd00 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 enregistre la Sous-Prfecture de Grasse (0

3、6) 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 present document shall not be modified without

4、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 Secretariat. Users of the p

5、resent 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 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. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks

8、 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 TS 132 156 V13.0.0 (2016-02)23GPP

9、TS 32.156 version 13.0.0 Release 13Intellectual 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 found in ETSI

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

11、nvestigation, 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 Technical Sp

12、ecification (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 delive

13、rables. 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“, “will“, “will not“, “can“ and “cannot“ are to be interp

14、reted 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 132 156 V13.0.0 (2016-02)33GPP TS 32.156 version 13.0.0 Release 13Contents Intelle

15、ctual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Requirements 7g35 Model Elements and Notations 7g35.1 General . 7g35.2 Basic model elements . 7g35.2.1 Attribute

16、 8g35.2.1.1 Description 8g35.2.1.2 Example 9g35.2.1.3 Name style. 9g35.2.2 Association relationship 9g35.2.2.1 Description 9g35.2.2.2 Example 10g35.2.2.3 Name style. 10g35.2.3 Aggregation association relationship 10g35.2.3.1 Description 10g35.2.3.2 Example 11g35.2.3.3 Name style. 11g35.2.4 Composite

17、 aggregation association relationship . 11g35.2.4.1 Description 11g35.2.4.2 Example 11g35.2.4.3 Name style. 11g35.2.5 Generalization relationship . 11g35.2.5.1 Description 11g35.2.5.2 Example 11g35.2.5.3 Name style. 12g35.2.6 Dependency relationship . 12g35.2.6.1 Description 12g35.2.6.2 Example 12g3

18、5.2.6.3 Name style. 12g35.2.7 Comment 12g35.2.7.1 Description 12g35.2.7.2 Example 12g35.2.7.3 Name style. 13g35.2.8 Multiplicity, a.k.a. cardinality in relationships . 13g35.2.8.1 Description 13g35.2.8.2 Example 13g35.2.8.3 Name style. 14g35.2.9 Role . 14g35.2.9.1 Description 14g35.2.9.2 Example 15g

19、35.2.9.3 Name style. 15g35.2.10 Xor constraint . 15g35.2.10.1 Description 15g35.2.10.2 Example 15g3ETSI ETSI TS 132 156 V13.0.0 (2016-02)43GPP TS 32.156 version 13.0.0 Release 135.2.10.3 Name style. 15g35.3 Stereotype . 16g35.3.1 . 16g35.3.1.1 Description 16g35.3.1.2 Example 16g35.3.1.3 Name style.

20、16g35.3.2 . 16g35.3.2.1 Description 16g35.3.2.2 Example 17g35.3.2.3 Name style. 17g35.3.3 . 17g35.3.3.1 Description 17g35.3.3.2 Example 17g35.3.3.3 Name style. 18g35.3.4 18g35.3.4.1 Description 18g35.3.4.2 Example 18g35.3.4.3 Name style. 18g35.3.5 . 19g35.3.5.1 Description 19g35.3.5.2 Example 19g35.

21、3.5.3 Name style. 19g35.3.6 . 19g35.3.6.1 Description 19g35.3.6.2 Example 19g35.3.6.3 Name style. 20g35.4 Others . 21g35.4.1 Association class . 21g35.4.1.1 Description 21g35.4.1.2 Example 21g35.4.1.3 Name style. 21g35.4.2 Abstract class 22g35.4.2.1 Description 22g35.4.2.2 Example 22g35.4.2.3 Name s

22、tyle. 22g35.4.3 Predefined data types 22g35.4.3.1 Description 22g35.4.3.2 Example 23g35.4.3.3 Name style. 23g36 Qualifiers 23g37 UML Diagram Requirements . 24g3Annex A (informative): Examples of using . 25g3A.1 First Example . 25g3A.2 Second Example . 26g3Annex B (normative): Attribute properties .

23、27g3Annex C (normative): Design patterns . 29g3C.1 Intervening Class and Association Class 29g3C.1.1 Concept and Definition 29g3C.1.2 Usage in the non-transport domain . 32g3C.1.3 Usage in the transport domain 32g3C.2 Use of ExternalXyz class 33g3Annex D (informative): Stereotypes for naming purpose

24、s . 34g3Annex E (informative): Change history . 36g3History 37 ETSI ETSI TS 132 156 V13.0.0 (2016-02)53GPP TS 32.156 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to c

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

26、 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 editori

27、al only changes have been incorporated in the document. ETSI ETSI TS 132 156 V13.0.0 (2016-02)63GPP TS 32.156 version 13.0.0 Release 131 Scope The JWG on Model Alignment work has chosen UML to capture behaviour of systems/entities under management. UML provides a rich set of concepts, notations and

28、model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of JWG Model Alignment work. This paper documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism

29、 , for use by JWG Model Alignment work. Collectively, this set of notations and model elements is called the FMC (developed by the Converged Management of Fixed/Mobile Networks project) Model Repertoire. JWG Model Alignment specifications shall employ the UML notation and model elements of this repe

30、rtoire. In the course of the JWG Model Alignment work, JWG Model Alignment group may modify (add, delete, modify) UML notation and model elements of this repertoire when necessary. 2 References 1 OMG “Unified Modelling Language (OMG UML), Infrastructure“, Version 2. 4. 2 OMG “Unified Modelling Langu

31、age (OMG UML), Superstructure“, Version 2. 4. 3 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 4 3GPP TS 23.002: “Network architecture“. 5 3GPP TS 32.107: “ Telecommunication management; Fixed Mobile Convergence (FMC) Federated Net

32、work Information Model (FNIM)“. 6 3GPP TS 28.620: “ Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM)“. 7 ITU-T X.680,“OSI networking and system aspects Abstract Syntax Notation One (ASN.1)“. 8 ITU-T X.501,“Inform

33、ation technology Open Systems Interconnection The Directory: Models“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of this document, the following definitions and abbreviations apply. For definitions and abbreviations not found here, see also Fixed Mobile Convergence (FMC) Federa

34、ted Network Information Model (FNIM) 0, Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model 6.g3Distinguished Name: See 3GPP TS 32.300 3. Naming attribute: It is a class attribute that holds the class instance identifier. See attribute id of Top_ 6. S

35、ee examples of naming attribute in 3GPP TS 32.300 3. Lower Camel Case: It is the practice of writing compound words in which the words are joined without spaces. Initial letter of all except the first word shall be capitalized. Examples: “managedNodeIdentity“ and “minorDetails“ are the LCC for manag

36、ed node identity and minor details respectively. Upper Camel Case: It is the Lower Camel Case except that the first letter is capitalised. Examples: “ManagedNodeIdentity“ and “MinorDetails“ are the UCC for managed node identity and minor details respectively. ETSI ETSI TS 132 156 V13.0.0 (2016-02)73

37、GPP TS 32.156 version 13.0.0 Release 13Well Known Abbreviation: An abbreviation can be used as the modelled element name or as a component of a modelled element name. The abbreviation, when used in such manner, must be documented in the same document where the modelled element is defined. 3.2 Abbrev

38、iations CM Conditional Mandatory CO Conditional OptionalDN Distinguished Name FMC Fixed Mobile Convergence FNIM Federated Network Information Model IOC Information Object Class IRP Integration Reference Point JWG (3GPP/TM Forum) Joint Working Group LCC Lower Camel Case M Mandatory NA Not Applicable

39、NRM Network Resource Model O Optional OMG Object Management Group UCC Upper Camel Case UIM Umbrella Information Model UML Unified Modelling Language (OMG) WKA Well Known Abbreviation 4 Requirements The UML notations and model elements captured in this repertoire shall be used to model behaviours of

40、the systems/entities specified by the JWG Resource Model Alignment work such as the Umbrella Information Model (UIM) of the FNIM 6 discussed in Converged Management of Fixed/Mobile Network project. 5 Model Elements and Notations 5.1 General Note that the graphical notation in this document is only u

41、sed to represent particular model elements. Although the graphical notation is a correct representation of the model element, it may not be a valid representation of a UML class diagram. The examples used in this document are for illustration purposes only and may or may not exist in specifications.

42、 UML properties not described in this document shall not be used in specifications based on this repertoire. 5.2 Basic model elements UML has defined a number of basic model elements. This subclause lists the subset selected for use in specifications based on this repertoire. The semantics of these

43、selected basic model elements are defined in 1. For each basic model element listed, there are three parts. The first part contains its description. The second part contains its graphical notation examples and the third part contains the rule, if any, recommended for labelling or naming it. The grap

44、hical notation has the following characteristics: Subclause 7.2.7 of 2 specifies “A class is often shown with three compartments. The middle compartment holds a list of attributes while the bottom compartment holds a list of operations“ and “Additional compartments may be supplied to show other deta

45、ils“. This repertoire only allows the use of the name (top) ETSI ETSI TS 132 156 V13.0.0 (2016-02)83GPP TS 32.156 version 13.0.0 Release 13compartment and attribute (middle) compartment. The operation (bottom) compartment may be present but is always empty, as shown in the figure below. Classes may

46、or may not have attributes. The graphical notation of a class may show an empty attribute (middle) compartment even if the class has attributes, as shown in figure below. The visibility symbol shall not appear along with the class attribute, as shown below. The use of the decoration, i.e. the symbol

47、 in the name (top) compartment, is optional. 5.2.1 Attribute 5.2.1.1 Description It is a typed element representing a property of a class. See 10.2.5 Property of 1. An element that is typed implies that the element can only refer to a constrained set of values. See 10.1.4 Type of 1 for more informat

48、ion on type. See 5.3.4 and 5.4.3 for predefined data types and user-defined data types that can apply type information to an element. The following table captures the properties of this modelled element. Table 5.2.1.1-1: Attribute properties Property name Description Legal values documentation Conta

49、ins a textual description of the attribute. Should refer (to enable traceability) to the specific requirement. Any isOrdered For a multi-valued multiplicity; this specifies if the values of this attribute instance are sequentially ordered. See subclause 7.3.44 and its Table 7.1 of 2. True, False (default) isUnique For a multi-valued multiplicity, this specifies if the values of this attribute instance are unique (i.e., no duplicate attribute values). See subclause 7.3.44 and its Table 7.1 of 2. True (default), Fal