|
TECHNICAL REPORT
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Fixed Mobile Convergence (FMC)
Federated Network Operation Model (FNOM)
Umbrella Operation Model (UOM)
(3GPP TR 28.820 version 12.0.0 Release 12)
---------------------- Page: 1 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 1 ETSI TR 128 820 V12.0.0 (2014-10)
Reference
DTR/TSGS-0528820vc00
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:
http://www.etsi.org
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 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 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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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.
© European Telecommunications Standards Institute 2014.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 2 ETSI TR 128 820 V12.0.0 (2014-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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 (http://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.
Foreword
This Technical Report (TR) 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", "may not", "need", "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 TR 28.820 version 12.0.0 Release 12 3 ETSI TR 128 820 V12.0.0 (2014-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Umbrella Operation Model (UOM) . 8
4.1 Introduction . 8
4.2 Interface/Signal diagram . 8
4.3 Operations . 9
4.3.1 Create Operations Group . 9
4.3.1.1 Operation createEntity . 9
4.3.1.1.1 Definition. 9
4.3.1.1.2 Input parameters . 9
4.3.1.1.3 Output parameters . 10
4.3.2 Delete Operations Group . 11
4.3.2.1 Operation deleteEntitiesWithSc . 11
4.3.2.1.1 Definition. 11
4.3.2.1.2 Input parameters . 11
4.3.2.1.3 Output parameters . 11
4.3.2.2 Operation deleteEntities . 12
4.3.2.2.1 Definition. 12
4.3.2.2.2 Input parameters . 12
4.3.2.2.3 Output parameters . 12
4.3.3 Get Operations Group . 13
4.3.3.1 Operation getEntityIdsWithSc . 13
4.3.3.1.1 Definition. 13
4.3.3.1.2 Input parameters . 13
4.3.3.1.3 Output parameters . 13
4.3.3.2 Operation getEntitiesWithSc . 14
4.3.3.2.1 Definition. 14
4.3.3.2.2 Input parameters . 14
4.3.3.2.3 Output parameters . 14
4.3.3.3 Operation getEntities . 15
4.3.3.3.1 Definition. 15
4.3.3.3.2 Input parameters . 15
4.3.3.3.3 Output parameters . 15
4.3.4 Set Operations Group. 16
4.3.4.1 Operation setEntitiesWithScAtomic . 16
4.3.4.1.1 Definition. 16
4.3.4.1.2 Input parameters . 16
4.3.4.1.3 Output parameters . 16
4.3.4.2 Operation setEntitiesWithSc . 17
4.3.4.2.1 Definition. 17
4.3.4.2.2 Input parameters . 17
4.3.4.2.3 Output parameters . 18
4.3.4.3 Operation setEntities . 19
4.3.4.3.1 Definition. 19
ETSI
---------------------- Page: 4 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 4 ETSI TR 128 820 V12.0.0 (2014-10)
4.3.4.3.2 Input parameters . 19
4.3.4.3.3 Output parameters . 19
4.4 Notifications . 20
4.4.1 Notification notify . 20
4.4.1.1 Definition . 20
4.4.1.2 Input parameters . 20
4.4.1.3 Output parameters . 20
Annex A: Interface/Signal diagrams . 21
Annex B: Notification Notify attributes . 22
Annex C: Change history . 24
History . 25
ETSI
---------------------- Page: 5 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 5 ETSI TR 128 820 V12.0.0 (2014-10)
Foreword
rd
This Technical Report 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 TR 28.820 version 12.0.0 Release 12 6 ETSI TR 128 820 V12.0.0 (2014-10)
1 Scope
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 3GPP TR 32.833 [1], 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.
2 References
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] 3GPP 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.
ETSI
---------------------- Page: 7 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 7 ETSI TR 128 820 V12.0.0 (2014-10)
3 Definitions, symbols and abbreviations
3.1 Definitions
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 Symbols
For the purposes of the present document, the symbols given in Fixed Mobile Convergence (FMC) Federated Network
Information Model (FNIM) [3] apply.
3.3 Abbreviations
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
ETSI
---------------------- Page: 8 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 8 ETSI TR 128 820 V12.0.0 (2014-10)
4 Umbrella Operation Model (UOM)
4.1 Introduction
This clause introduces a number of classes and their relations that form the UOM. These classes are defined as the
OMG UML defined classifier called interface.
The definitions of these classes are implementation neutral in that they only capture the semantics of the operations.
They do not:
a) Include syntax or representation of the operation model elements.
b) Relate to the information model elements.
Various SDOs and organizations are expected to use this interface definition for their definitions of domain/technology-
specific "interface" classes. This procedure will maximize the probability of the domain/technology specific concrete
"interface" classes (from various SDOs) being semantically consistent, a necessary characteristic for FMC NM
purposes.
The set of "interface" is basic in that their definitions and usage are necessary for the harmonization of various
domain/technology-specific "interface" classes, forming the so-called FNOM.
4.2 Interface/Signal diagram
These Interfaces are abstract. Other Interfaces are for further study.
The UML diagrams in figure 4.2-1 do not show operation parameters. See annex A for the UML diagrams that do.
Figure 4.2-1: Interface/Signal diagram
ETSI
---------------------- Page: 9 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 9 ETSI TR 128 820 V12.0.0 (2014-10)
4.3 Operations
4.3.1 Create Operations Group
4.3.1.1 Operation createEntity
4.3.1.1.1 Definition
The client requests the server to create an identifiable entity.
It is possible to provide an identifier of an existing entity of the same class to be used as the template for the new entity
to be created.
The operation properties are:
Property name Legal values
isAtomic True
preconditions
None
postconditions
Entity has been created as requested.
bulkTransferPattern
NONE
emitsEvents
False
emittedEvents
--
isOneWay
False
All mandatory pre-defined Exceptions (see Table 9 of [4]).
operationExceptions
Optional pre-defined Exceptions:
CapacityExceeded
ObjectExisting
supportQualifier
M
4.3.1.1.2 Input parameters
Parameter Name Documentation and Allowed Values Properties
entityId
This parameter provides the identifier of the entity to be created by the type: DN
Server. isOrdered: False
If no identifier is provided, the Server provides a unique identifier. isUnique: True
allowedValues: FFS defaultValue: No
value
multiplicity: 1
isBulkPotential:
False
supportQualifier: M
referenceEntity
This parameter provides the identifier of an existing entity that is of the same type: DN
class as the entity to be created. isOrdered: False
Attribute values associated with the referenced entity become the default isUnique: True
values for those not specified by the attributeList parameter. defaultValue: No
value
This parameter may contain no information.
multiplicity: 1
allowedValues: Distinguished Name of an existing entity of the same class
isBulkPotential:
known by the server.
False
supportQualifier: O
attributeList
This parameter provides the entity attribute names and values to be type:
populated to the new entity. AttributeValuePair
These values override the values of the referenceEntity (if the isOrdered: False
isUnique: True
referenceEntity parameter contains information) and the default values
defaultValue: No
property of the entity definition.
value
allowedValues: For the attribute names, only the subject entity class defined
multiplicity: *
attributes. For the attribute values, see the subject entity class attribute
isBulkPotential:
allowedValues property.
False
supportQualifier: O
ETSI
---------------------- Page: 10 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 10 ETSI TR 128 820 V12.0.0 (2014-10)
4.3.1.1.3 Output parameters
None.
ETSI
---------------------- Page: 11 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 11 ETSI TR 128 820 V12.0.0 (2014-10)
4.3.2 Delete Operations Group
4.3.2.1 Operation deleteEntitiesWithSc
4.3.2.1.1 Definition
The client requests the server to delete entities identified by selection criteria.
The operation properties are:
Property name Legal values
isAtomic
False
preconditions
None
postconditions
Selected entities do not exist.
bulkTransferPattern
NONE
emitsEvents False
emittedEvents --
isOneWay False
All mandatory pre-defined Exceptions (see Table 9 of [4]).
operationExceptions
Optional pre-defined Exceptions:
None
supportQualifier
M
4.3.2.1.2 Input parameters
Parameter Name Documentation and Allowed Values Properties
selectionCriteria
This parameter provides the criteria whose evaluation would yield zero or type: External
more entity identifier(s). isOrdered: False
The grammar for selectionCriteria is not defined in the UOM and may be isUnique: True
dependent on the technology used (e.g. in case of XML use XPath). defaultValue: No
allowedValues: N/A value
multiplicity: 1
isBulkPotential:
False
supportQualifier: M
4.3.2.1.3 Output parameters
Parameter Name Documentation Properties
states
This parameter provides information about the status of the operation. type: OperationStatusBestEffort
allowedValues: See property::type. isOrdered: False
isUnique: True
defaultValue: No value
multiplicity: 1
isBulkPotential: False
supportQualifier: M
ETSI
---------------------- Page: 12 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 12 ETSI TR 128 820 V12.0.0 (2014-10)
4.3.2.2 Operation deleteEntities
4.3.2.2.1 Definition
The client requests the server to delete entities identified by explicit object identifiers.
The operation properties are:
Property name Legal values
isAtomic
False
preconditions
None
postconditions
Identified entities do not exist.
bulkTransferPattern
NONE
emitsEvents False
emittedEvents --
isOneWay False
All mandatory pre-defined Exceptions (see Table 9 of [4]).
operationExceptions
Optional pre-defined Exceptions:
None
supportQualifier
M
4.3.2.2.2 Input parameters
Parameter Documentation Properties
Name
entityIdList This parameter provides the identifiers of the entities to be deleted by the type: DN
Server. isOrdered: False
allowedValues: See property::type. isUnique: True
defaultValue: No
value
multiplicity: 1.*
isBulkPotential: False
supportQualifier: M
4.3.2.2.3 Output parameters
Parameter Name Documentation Properties
status
This parameter provides information about the status of the operation. type: OperationStatusBestEffort
allowedValues: See property::type. isOrdered: False
isUnique: True
defaultValue: No value
multiplicity: 1
isBulkPotential: False
supportQualifier: M
ETSI
---------------------- Page: 13 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 13 ETSI TR 128 820 V12.0.0 (2014-10)
4.3.3 Get Operations Group
4.3.3.1 Operation getEntityIdsWithSc
4.3.3.1.1 Definition
The client requests the server to return the identifiers of the entities identified by selection criteria.
The operation properties are:
Property name Legal values
isAtomic False
preconditions
None
postconditions
No change in the entities.
bulkTransferPattern
NONE
emitsEvents
False
emittedEvents
--
isOneWay
False
All mandatory pre-defined Exceptions (see Table 9 of [4]).
operationExceptions
Optional pre-defined Exceptions:
AccessDenied
FilterNotSupported
supportQualifier M
4.3.3.1.2 Input parameters
Parameter Name Documentation and Allowed Values Properties
selectionCriteria
It This parameter provides the criteria whose evaluation would yield zero or more entity type: External
identifier(s). isOrdered: False
The grammar for selectionCriteria is not defined in the UOM and may be dependent on the isUnique: True
technology used (e.g. in case of XML use XPath). defaultValue: No
allowedValues: N/A value
multiplicity: 1
isBulkPotential:
False
supportQualifier: M
4.3.3.1.3 Output parameters
Parameter Name Documentation Properties
entityIdList This parameter returns a list of entity identifiers. type: DN
allowedValues: See property::type. isOrdered: False
isUnique: True
defaultValue: No value
multiplicity: *
isBulkPotential: False
supportQualifier: M
status This parameter returns information about the status of the operation. type: OperationStatusBestEffort
allowedValues: See property::type. isOrdered: False
isUnique: True
defaultValue: No value
multiplicity: 1
isBulkPotential: False
supportQualifier: M
ETSI
---------------------- Page: 14 ----------------------
3GPP TR 28.820 version 12.0.0 Release 12 14 ETSI TR 128 820 V12.0.0 (2014-10)
4.3.3.2 Operation getEntitiesWithSc
4.3.3.2.1 Definition
The client requests the server to return information (list of attribute values) of the entities identified by selection criteria.
The operation properties are:
Property name Legal values
isAtomic
False
preconditions
None
postconditions
No change in the entities.
bulkTransferPattern
ITERATOR
emitsEvents
False
emittedEvents
--
isOneWay False
All mandatory pre-defined Exceptions (see Table 9 of [4]).
operationExceptions
Optional pre-defined Exceptions:
AccessDenied
FilterNotSupported
supportQualifier M
4.3.3.2.2 Input parameters
Parameter Name Documentation Properties
selectionCriteria This parameter provides the criteria whose evaluation would yield zero or more entity type: External
identifier(s). For the identified entities the attribute values are to be returned. isOrdered: False
The grammar for selectionCriteria is not defined in the UOM and may be dependent on the isUnique: True
technology used (e.g. in case of XML use XPath). defaultValue: No
allowedValues: N/A value
multiplicity: 1
isBulkPotential:
False
supportQualifier: M
attributeNameList
This parameter provides the names of attributes whose values are requested by the client. type: String
If no attribute name is provided, all available attributes have to be returned. isOrdered: False
isUnique: True
allowedValues: See property::type. defaultValue: No
value
multiplicity: *
isBulkPotential:
False
supportQualifier: M
4.3.3.2.3 Output parameters
Parameter Name Documentation Properties
entityInstanceList
This parameter returns the list of entities together with their requested type: Top_
attributes. isOrdered: False
...