|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Fixed Mobile Convergence (FMC) model repertoire
(3GPP TS 32.156 version 13.2.0 Release 13)
---------------------- Page: 1 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 1 ETSI TS 132 156 V13.2.0 (2019-05)
Reference
RTS/TSGS-0532156vd20
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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
If you find errors in the present document, please send your comment to one of the following services:
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 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 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 2 ETSI TS 132 156 V13.2.0 (2019-05)
Intellectual 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-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 (https://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, essential to the present document.
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. 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 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 deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 3 ETSI TS 132 156 V13.2.0 (2019-05)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Requirements . 8
5 Model Elements and Notations . 8
5.1 General . 8
5.2 Basic model elements . 8
5.2.1 Attribute . 8
5.2.1.1 Description . 8
5.2.1.2 Example . 9
5.2.1.3 Name style. 9
5.2.2 Association relationship . 10
5.2.2.1 Description . 10
5.2.2.2 Example . 10
5.2.2.3 Name style. 11
5.2.3 Aggregation association relationship . 11
5.2.3.1 Description . 11
5.2.3.2 Example . 11
5.2.3.3 Name style. 11
5.2.4 Composite aggregation association relationship . 11
5.2.4.1 Description . 11
5.2.4.2 Example . 11
5.2.4.3 Name style. 12
5.2.5 Generalization relationship . 12
5.2.5.1 Description . 12
5.2.5.2 Example . 12
5.2.5.3 Name style. 12
5.2.6 Dependency relationship . 12
5.2.6.1 Description . 12
5.2.6.2 Example . 12
5.2.6.3 Name style. 12
5.2.7 Comment . 13
5.2.7.1 Description . 13
5.2.7.2 Example . 13
5.2.7.3 Name style. 13
5.2.8 Multiplicity, a.k.a. cardinality in relationships . 13
5.2.8.1 Description . 13
5.2.8.2 Example . 13
5.2.8.3 Name style. 14
5.2.9 Role . 14
5.2.9.1 Description . 14
5.2.9.2 Example . 15
5.2.9.3 Name style. 15
5.2.10 Xor constraint . 15
5.2.10.1 Description . 15
5.2.10.2 Example . 15
5.2.10.3 Name style. 16
5.3 Stereotype . 16
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 4 ETSI TS 132 156 V13.2.0 (2019-05)
5.3.1 <> . 16
5.3.1.1 Description . 16
5.3.1.2 Example . 16
5.3.1.3 Name style. 17
5.3.2 <> . 17
5.3.2.1 Description . 17
5.3.2.2 Example . 17
5.3.2.3 Name style. 17
5.3.3 <> . 17
5.3.3.1 Description . 17
5.3.3.2 Example . 18
5.3.3.3 Name style. 18
5.3.4 <> . 18
5.3.4.1 Description . 18
5.3.4.2 Example . 19
5.3.4.3 Name style. 19
5.3.5 <> . 19
5.3.5.1 Description . 19
5.3.5.2 Example . 20
5.3.5.3 Name style. 20
5.3.6 <> . 20
5.3.6.1 Description . 20
5.3.6.2 Example . 20
5.3.6.3 Name style. 21
5.4 Others . 21
5.4.1 Association class . 21
5.4.1.1 Description . 21
5.4.1.2 Example . 22
5.4.1.3 Name style. 22
5.4.2 Abstract class . 22
5.4.2.1 Description . 22
5.4.2.2 Example . 22
5.4.2.3 Name style. 22
5.4.3 Predefined data types . 22
5.4.3.1 Description . 22
5.4.3.2 Example . 23
5.4.3.3 Name style. 23
6 Qualifiers . 24
7 UML Diagram Requirements . . 25
Annex A (informative): Examples of using <> . 26
A.1 First Example . 26
A.2 Second Example . 27
Annex B (normative): Attribute properties . 28
Annex C (normative): Design patterns . 29
C.1 Intervening Class and Association Class . 29
C.1.1 Concept and Definition . 29
C.1.2 Usage in the non-transport domain . 32
C.1.3 Usage in the transport domain . 32
C.2 Use of “ExternalXyz” class . 33
Annex D (informative): Void . 34
Annex E (informative): Change history . 35
History . 36
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 5 ETSI TS 132 156 V13.2.0 (2019-05)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 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 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
---------------------- Page: 6 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 6 ETSI TS 132 156 V13.2.0 (2019-05)
1 Scope
UML provides a rich set of concepts, notations and model elements to model distributive systems. This paper
documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML
extension mechanism <> to model network management systems and their managed nodes. This set of
notations and model elements is called the FMC Model Repertoire; see also 3GPP TS 32.107 [5] and 3GPP TS 28.620
[6].
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] 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,"OSI networking and system aspects – Abstract Syntax Notation One (ASN.1)".
[8] Void
[9] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [X] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [9].Naming 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 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 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 element name. The abbreviation, when used in such manner, must be documented in the same document
where the modelled element is defined.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [9], 3GPP TS 28.620 [6] and the
following apply. An abbreviation defined in the present document takes precedence over the definition of the same
abbreviation, if any, in 3GPP TR 21.905 [9], and 3GPP TS 28.620 [6].
CM Conditional Mandatory
CO Conditional Optional
IRP Integration Reference Point
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 7 ETSI TS 132 156 V13.2.0 (2019-05)
LCC Lower Camel Case
M Mandatory
NA Not Applicable
O Optional
UCC Upper Camel Case
WKA Well Known Abbreviation
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 8 ETSI TS 132 156 V13.2.0 (2019-05)
4 Requirements
The UML notations and model elements captured in this repertoire shall be used to model behaviours of the
systems/entities such as the Umbrella Information Model (UIM) of the FNIM in 3GPP TS 28.620 [6].
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 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 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 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 graphical 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 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 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 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].
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 32.156 version 13.2.0 Release 13 9 ETSI TS 132 156 V13.2.0 (2019-05)
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 information 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 Contains a textual description of the attribute. Any
Should refer (to enable traceability) to the specific requirement.
isOrdered For a multi-valued multiplicity; this specifies if the values of this True, False (default)
attribute instance are sequentially ordered. See subclause 7.3.44 and
its Table 7.1 of [2].
isUnique For a multi-valued multiplicity, this specifies if the values of this
...