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

1、 ETSI TS 132 156 V15.0.0 (2018-06) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire (3GPP TS 32.156 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 156 V15.0.0 (2018-06)13GPP TS 32.156 version 15

2、.0.0 Release 15Reference RTS/TSGS-0532156vf00 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 (06) N 7803/88

3、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 wri

4、tten 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 docume

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

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

7、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 Memb

8、ers. 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 132 156 V15.0.0 (2018-0

9、6)23GPP TS 32.156 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-membe

10、rs, 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/). Pursuant

11、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 document

12、. 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 tradename

13、. 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 docume

14、nt 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:/webapp.

15、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 provisio

16、ns). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 156 V15.0.0 (2018-06)33GPP TS 32.156 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References

17、7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Requirements 9g35 Model Elements and Notations 9g35.1 General . 9g35.2 Basic model elements . 9g35.2.1 Attribute 10g35.2.1.1 Description 10g35.2.1.2 Example 10g35.2.1.3 Name style. 11g35.2.2 Association relationship

18、11g35.2.2.1 Description 11g35.2.2.2 Example 11g35.2.2.3 Name style. 12g35.2.3 Aggregation association relationship 12g35.2.3.1 Description 12g35.2.3.2 Example 12g35.2.3.3 Name style. 12g35.2.4 Composite aggregation association relationship . 12g35.2.4.1 Description 12g35.2.4.2 Example 12g35.2.4.3 Na

19、me style. 13g35.2.5 Generalization relationship . 13g35.2.5.1 Description 13g35.2.5.2 Example 13g35.2.5.3 Name style. 13g35.2.6 Dependency relationship . 13g35.2.6.1 Description 13g35.2.6.2 Example 13g35.2.6.3 Name style. 14g35.2.7 Comment 14g35.2.7.1 Description 14g35.2.7.2 Example 14g35.2.7.3 Name

20、 style. 14g35.2.8 Multiplicity, a.k.a. cardinality in relationships . 14g35.2.8.1 Description 14g35.2.8.2 Example 14g35.2.8.3 Name style. 15g35.2.9 Role . 15g35.2.9.1 Description 15g35.2.9.2 Example 16g35.2.9.3 Name style. 16g35.2.10 Xor constraint . 16g35.2.10.1 Description 16g35.2.10.2 Example 16g

21、35.2.10.3 Name style. 17g35.3 Stereotype . 17g3ETSI ETSI TS 132 156 V15.0.0 (2018-06)43GPP TS 32.156 version 15.0.0 Release 155.3.0 Description 17g35.3.1 . 17g35.3.1.1 Description 17g35.3.1.2 Example 17g35.3.1.3 Name style. 18g35.3.2 . 18g35.3.2.1 Description 18g35.3.2.2 Example 18g35.3.2.3 Name sty

22、le. 18g35.3.3 . 18g35.3.3.1 Description 18g35.3.3.2 Example 19g35.3.3.3 Name style. 19g35.3.4 19g35.3.4.1 Description 19g35.3.4.2 Example 20g35.3.4.3 Name style. 20g35.3.5 . 20g35.3.5.1 Description 20g35.3.5.2 Example 21g35.3.5.3 Name style. 21g35.3.6 . 21g35.3.6.1 Description 21g35.3.6.2 Example 21

23、g35.3.6.3 Name style. 22g35.4 Others . 22g35.4.1 Association class . 22g35.4.1.1 Description 22g35.4.1.2 Example 23g35.4.1.3 Name style. 23g35.4.2 Abstract class 23g35.4.2.1 Description 23g35.4.2.2 Example 23g35.4.2.3 Name style. 23g35.4.3 Predefined data types 23g35.4.3.1 Description 23g35.4.3.2 Ex

24、ample 24g35.4.3.3 Name style. 24g36 Qualifiers 25g37 UML Diagram Requirements . 26g3Annex A (informative): Examples of using . 27g3A.1 First Example . 27g3A.2 Second Example . 28g3Annex B (normative): Attribute properties . 29g3Annex C (normative): Design patterns . 30g3C.1 Intervening Class and Ass

25、ociation Class 30g3C.1.1 Concept and Definition 30g3C.1.2 Usage in the non-transport domain . 33g3C.1.3 Usage in the transport domain 33g3C.2 Use of “ExternalXyz” class 34g3Annex D (informative): Void . 35g3Annex E (normative): stereotype definition 36g3E.1 Description 36g3ETSI ETSI TS 132 156 V15.0

26、.0 (2018-06)53GPP TS 32.156 version 15.0.0 Release 15E.2 Example 36g3E.3 Name style. 36g3Annex F (normative): Application of and . 37g3Annex G(informative): Change history . 39g3History 40g3ETSI ETSI TS 132 156 V15.0.0 (2018-06)63GPP TS 32.156 version 15.0.0 Release 15Foreword This Technical Specifi

27、cation 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 wit

28、h 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

29、all 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. ETSI ETSI TS 132 156 V15.0.0 (2018-06)73GPP TS 32.156 version 15.0.0 Release 151 Scope The JWG on Model Alignment wor

30、k has chosen UML to capture behaviour of systems/entities under management. UML provides a rich set of concepts, notations and 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 document

31、s the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism , 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 Netwo

32、rks project) Model Repertoire. JWG Model Alignment specifications shall employ the UML notation and model elements of this repertoire. 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 nec

33、essary. 2 References 1 OMG “Unified Modelling Language (OMG UML), Infrastructure“, Version 2. 4. 2 OMG “Unified Modelling Language (OMG UML), Superstructure“, Version 2. 4. 3 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 4 Void 5

34、3GPP TS 32.107: “ Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network 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,“OS

35、I networking and system aspects Abstract Syntax Notation One (ASN.1)“. 8 Void 9 3GPP TS 32.602 “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)“. 10 3GPP TS 32.612: “Telecommunication management; Configuration Manageme

36、nt (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 11 3GPP TS 32.111-2: “ Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 12 3GPP TS 32.302: “Telecommunication management; Configuration Management

37、 (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 13 3GPP TS 32.404: “Telecommunication management; Performance Management (PM); Performance measurements - Definitions and template“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of this document, th

38、e following definitions and abbreviations apply. For definitions and abbreviations not found here, see also Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) 5, Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model 6.g3Distinguis

39、hed Name: See 3GPP TS 32.300 3. ETSI ETSI TS 132 156 V15.0.0 (2018-06)83GPP TS 32.156 version 15.0.0 Release 15Naming attribute: It is a class attribute that holds the class instance identifier. See attribute id of Top_ 6. See examples of naming attribute in 3GPP TS 32.300 3. Lower Camel Case: It is

40、 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 “managed node identity” and “minor details” respectively. Upper Camel Case: It is the

41、 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. Well Known Abbreviation: An abbreviation can be used as the modelled element name or as a component of a modelled el

42、ement name. The abbreviation, when used in such manner, must be documented in the same document where the modelled element is defined. 3.2 Abbreviations CM Conditional Mandatory CO Conditional OptionalDN Distinguished Name FMC Fixed Mobile Convergence FNIM Federated Network Information Model IOC Inf

43、ormation Object Class IRP Integration Reference Point JWG (3GPP/TM Forum) Joint Working Group LCC Lower Camel Case M Mandatory NA Not Applicable NRM Network Resource Model O Optional OMG Object Management Group UCC Upper Camel Case UIM Umbrella Information Model UML Unified Modelling Language (OMG)

44、WKA Well Known Abbreviation ETSI ETSI TS 132 156 V15.0.0 (2018-06)93GPP TS 32.156 version 15.0.0 Release 154 Requirements The UML notations and model elements captured in this repertoire shall be used to model behaviours of the systems/entities specified by the JWG Resource Model Alignment work such

45、 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 used to represent particular model elements. Although the graphical notation

46、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. UML properties not described in this document shall not be used in specific

47、ations 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 selected basic model elements are defined in 1. For each basic model element

48、 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 graphical notation has the following characteristics: Subclause 7.2.7 of 2 speci

49、fies “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 details“. This repertoire only allows the use of the name (top) compartment and attribute (middle) compartment. The operation (bottom) compartment may be present but is always empty, as shown in the figure below. Classes may or may not have attributes. The graphical notation of a class may show an empty a