Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 28.820  Word version:  12.0.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 6

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, 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.
As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed TR 32.833, TM Forum TR 166 [2]. These use cases led to the recognition that it would be necessary to define common operation model elements applicable for wire-line and wireless networks. The present document defines these common model elements.
To be noted:
  • The Umbrella Operation Model (UOM) described in the present document provides the set of interfaces/operations etc. that have been agreed for convergence to strengthen consistency of representation and semantics of network management operations in the fixed and mobile environments.
  • The UOM is necessary but not sufficient for implementation.
  • The UOM cannot be used directly for implementation. Implementation classes must be derived from those in the UOM by Inheritance or some other appropriate mechanism.
  • Classes derived from those in the UOM (e.g. for the fixed environment) may use different names from those used in the UOM.
Up

2  Referencesp. 6

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.
[1]
TR 32.833: "Telecommunication management; Study on management of converged networks".
[2]
TM Forum TR 166: "Information Model Federation Concepts and Principles". http://collab.tmforum.org/sf/go/doc13634?nav=1.
[3]
Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM):
[4]
Fixed Mobile Convergence (FMC) Model Repertoire:
Up

3  Definitions, symbols and abbreviationsp. 6

3.1  Definitionsp. 6

For the purposes of the present document, the terms and definitions given in Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) [3] apply.

3.2  Symbolsp. 6

For the purposes of the present document, the symbols given in Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) [3] apply.

3.3  Abbreviationsp. 7

For the purposes of the present document, the abbreviations given in Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) [3] and the following apply:
FFS
For Further Study
FMC
Fixed Mobile Convergence
FNIM
Federated Network Information Model
FNOM
Federated Network Operation Model
M
Mandatory
ME
Managed Element
NM
Network Management
NW
Network
O
Optional
OMG
Object Management Group
SC
Selection Criteria
SDO
Standards Developing Organization
UOM
Umbrella Operation Model
XML
Extensible Markup Language
XPath
XML Path Language

Up   Top   ToC