Content for TS 32.156 Word version: 18.6.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Requirements
...
...
1 Scope p. 7
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 <<stereotype>> to model network management systems and their managed nodes. This set of notations and model elements is called the FMC (developed by the Converged Management of Fixed/Mobile Networks project) Model Repertoire; see also TS 32.107 and TS 28.620.
2 References p. 7
[1]
OMG "Unified Modelling Language (OMG UML), Infrastructure": Version 2. 4.
[2]
OMG "Unified Modelling Language (OMG UML), Superstructure": Version 2. 4.
[3]
TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
[4] Void
[5] Void
[6]
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]
TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)".
[10]
TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)".
[11]
TS 32.111-2: " Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
[12]
TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)".
[13]
TS 32.404: "Telecommunication management; Performance Management (PM); Performance measurements - Definitions and template".
[14] Void
[15]
TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[16]
TS 28.532: "Management and orchestration; Generic management services".
[17]
TS 28.531: "Management and orchestration; Provisioning".
[18]
TR 21.905: "Vocabulary for 3GPP Specifications".
[19]
TS 32.102: "Telecommunication management; Architecture".
[20]
TS 28.533: "Management and orchestration; Architecture framework".
[21]
RFC 20: "ASCII format for Network Interchange"
[22]
RFC 7950: "The YANG 1.1 Data Modeling Language"
[23]
TS 29.501: "Principles and Guidelines for Services Definition; Stage 3"
3 Definitions and abbreviations p. 8
3.1 Definitions p. 8
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Naming attribute:
It is a class attribute that holds the class instance identifier. See attribute id of Top_ in TS 28.620. See examples of naming attribute in TS 32.300.
Lower Camel Case:
The practice of writing compound words in which the words are joined without spaces and that the initial letter of all except the first word is capitalized.
EXAMPLES:
Upper Camel Case:
'managedNodeIdentity' and 'minorDetails' are the LCC for "managed node identity" and "minor details" respectively.
The practice of writing compound words in which the words are joined without spaces and that the initial letters of all words are capitalised.
EXAMPLES:
Well Known Abbreviation:
'ManagedNodeIdentity' and 'MinorDetails' are the UCC for "managed node identity" and "minor details" respectively.
An abbreviation that can be used as the modelled element name or as a component of a modelled element name.
Manager:
IRP Manager or MnS consumer
Agent:
IRP Agent or MnS producer
Data type:
Constraint on an attribute value.
Simple type:
Data type constraining an attribute value to a scalar.
Complex type:
Data type of a structured and/or multi-valued attribute.
Attribute:
Information element of an object composed of an attribute name and an attribute value.
Attribute name:
Name of an attribute.
Attribute value:
Value of an attribute that is defined by a simple type or a complex type.
Attribute field:
Attribute contained in an attribute that can contain attribute fields.
Attribute field name:
Name of an attribute field.
Attribute field value:
Value of an attribute field defined by a simple type or a complex type.
Simple attribute:
Attribute whose value is a simple type.
Complex attribute:
Attribute whose value is a complex type.
Structured attribute:
A kind of a complex attribute whose value contains one or more attribute fields.
Multi-valued attribute:
A kind of a complex attribute with multiplicity > 1.
Attribute element:
A single value of a multi-valued attribute.
Attribute field element:
A single value of a multi-valued attribute field.
Data node:
An object, an attribute, an attribute field, an attribute element, or an attribute field element.
Attribute data node:
An attribute, an attribute field, an attribute element, or an attribute field element.
Configuration data node:
A leaf data node, whose value is configurable, or a data node that contains at least one child data node, that is configurable.
State data node:
A read-only leaf data node, that represents a particular aspect of the system status, and whose value is set automatically by the management system, or a data node that contains only read-only child data nodes, that represent particular aspects of the system status, and whose values are set automatically by the management system.
Data node tree:
The collection of data nodes and their relationships.
3.2 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 21.905, TS 28.620, TS 28.532 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, TS 28.532 and TS 28.620.
CM
Conditional Mandatory
CO
Conditional Optional
LCC
Lower Camel Case
NA
Not Applicable
OMG
Object Management Group
UCC
Upper Camel Case
WKA
Well Known Abbreviation
4 Requirements p. 10
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 TS 28.620.
A model described using this UML repertoire
- provides the basis of identifying information in request messages.
- describes the structure of information on the MnS Producer.
- provides constraints on the possibilities to update information on the MnS Producer. After each change the information shall conform to the structure and constraints of the model (otherwise the request for changes shall be rejected).
