The present document is the result of the Multi-SDO JWG on Model Alignment which 3GPP TSG SA WG5 (SA5) has developed jointly with TMF and NGMN, and which does not fully follow the 3GPP templates and drafting rules.
Therefore 3GPP SA5 has desired to keep the present document as similar as possible to the original in ([9]), for comparison with the corresponding TMF version.
Thus 3GPP SA5 has done only the strictly necessary changes from the 3GPP drafting rules perspective in order to publish the present document as a 3GPP Technical Report. One of these type of changes is due to the fact that it is not allowed to use "shall" in an informative TR. However, in order to preserve the original intention of "must" and "shall" in the original JWG document and distinguish it from other places where "should" has been used (in case it is decided in the future to transform the TR into a TS), the use of "shall" is marked in italics font as "shall".
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 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 <<stereotype>>, 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 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 necessary.
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, etc.) 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 in the same Release as the present document.
TS 32.300: "3rd Generation Partnership Projects; Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
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) Federated Network Information Model (FNIM) [5], Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model [6].
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 as the Umbrella Information Model (UIM) [6] of the FNIM discussed in Converged Management of Fixed/Mobile Network project.