C.2 Use of “ExternalXyz” class
32.1563GPPFixed Mobile Convergence (FMC) model repertoireRelease 17Telecommunication managementTS
This subclause will be completed for the next release.
Annex D (informative):
Void
Annex E (normative): <<SupportIOC>> stereotype definition
E.1 Description
It is the descriptor for a set of management capabilities.
The <<SupportIOC>> is an extension of UML class. See Annex [F] for the differences between <<InformationObjectClass>> and <<SupportIOC>>.
See more on UML class in 10.2.1 of [1].
E.2 Example
This sample shows an AlarmList <<SupportIOC>>.
<<SupportIOC>> notation
E.3 Name style
For <<SupportIOC>> name, use the same style as <<InformationObjectClass>> (see subclause 5.3.2).
Annex F (normative):
Application of <<InformationObjectClass>> and <SupportIOC>>
The <<InformationObjectClass>> and <<SupportIOC>> are stereotypes. These two stereotypes serve similar purpose in that each is a named set of network resource properties. However, their applications, in the context of supporting network management over Itf-N or through the use of management services,, can be different. This Annex highlights their similarities and differences of such application.
|
<<InformationObjectClass>> |
<<SupportIOC>> |
|
|
Can it be an abstract class? |
Yes |
Yes |
|
Can it be a concrete class? |
Yes |
Yes |
|
Can it inherit from <<InformationObjectClass>>? |
Yes |
No, except for <<InformationObjectClass>> Top. |
|
Can it inherit from <<SupportIOC>>? |
No |
Yes |
|
Can it be name-contained by <<InformationObjectClass>>? |
Yes |
Yes |
|
Can it be name-contained by <<SupportIOC>>? |
No |
Yes |
|
Can an instance have a DN? |
<<InformationObjectClass>> must be a class of a naming-tree meaning all its instances must have a DN. |
<<SupportIOC>> may be used by specification author for a class within a naming-tree. If so, it means that all its instances will have a DN. |
|
Can either 1) IRPManager use operations of Basic CM IRP [9] and Bulk CM IRP [10] or 2) MnS consumer use the Provisioning operations [17] and [16] to access the information in an instance? |
Either 1) IRPManager can use the Basic CM IRP and Bulk CM IRP operations or 2) MnS consumer can use the provisioning operations to access information of all <<InformationObjectClass>> defined in all NRM [15], in accordance to the qualifier values of the <<InformationObjectClass>>. |
Either 1) IRPManager can use the Basic CM IRP and Bulk CM IRP operations to access information of instances of <<SupportIOC>> defined in their respective Interface IRP (i.e. Basic CM IRP or Bulk CM IRP), in accordance to the qualifier values of the <<SupportIOC>> or 2) MnS consumer can use the provisioning operations to access information of instances of <<SupportIOC>> specified in [16] and [17] in accordance to the qualifier values of the <<SupportIOC>>. Neither 1) IRPManager can use the Basic CM IRP and Bulk CM IRP operations to access information of instances of <<SupportIOC>> not defined in their respective Interface IRP (i.e. Basic CM IRP or Bulk CM IRP) nor 2) MnS consumer can use the Provisioning operations to access information of instances of <<SupportIOC>> not defined in [16] and [17] |
|
Can either 1) IRPManager use operations of Interface IRP, except Basic CM IRP [9] and Bulk CM IRP [10] (e.g. Alarm IRP [11]), or 2) MnS consumer use non Provisioning operations (e.g. fault supervision operations [14] and [16] to access the information? |
No |
Either 1) IRPManager can use the Interface IRP operations to access information of <<SupportIOC>> defined in their respective Interface IRP, in accordance to qualifier values of the <<SupportIOC>> or 2) . MnS consumer can use the Provisioning operations to access information of instances of <<SupportIOC>> specified in [16] and [17] in accordance to the qualifier values of the <<SupportIOC>>. Neither 1) IRPManager can not use the Interface IRP operations to access information of <<SupportIOC>> not defined in their respective Interface IRP, nor 2) MnS consumer can not use the Provisioning operations to access information of instances of <<SupportIOC>> not defined in [16] and [17]. |
|
Can either IRPManager or MnS consumer receive information via Notification [12] whose objectClass and objectInstance parameters carry the instance DN? |
Yes. The types of notification emitted are shown by the Notification Table associated with the class definition. |
Yes if <<SupportIOC>> is a class of a naming-tree. The types of notification emitted are shown by the Notification Table associated with the class definition. No if <<SupportIOC>> is not a class of a naming-tree. |
|
Measurement [13] |
Measurements can be associated with <<InformationObjectClass>> instances. |
Measurements can be associated with <<SupportIOC>> instances if <<SupportIOC>> class is used in a naming-tree. |
Annex G(informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2012-12 |
New version after approval |
2.0.0 |
11.0.0 |
||||
|
2013-01 |
Fixed layout problems |
11.0.0 |
11.0.1 |
||||
|
2013-03 |
Fixed title of the spec by removing a semi colon |
11.0.1 |
11.0.2 |
||||
|
2013-06 |
SA#60 |
SP-130304 |
001 |
– |
Model Repertoire introduce CR S5vTMFa354 |
11.0.2 |
11.1.0 |
|
2014-09 |
SA#65 |
SP-140597 |
002 |
– |
Introduce the agreed result of MSDO JWG Model Alignment work |
11.1.0 |
11.2.0 |
|
2014-10 |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.2.0 |
12.0.0 |
|
2016-01 |
– |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-12 |
SA#74 |
SP-160855 |
0003 |
– |
B |
Add missing Annex |
14.0.0 |
|
2017-04 |
Editorial fixes (MCC) |
14.0.1 |
|||||
|
2018-06 |
SA#80 |
SP-180422 |
0007 |
– |
A |
Clarify the use of datatype |
14.1.0 |
|
2018-06 |
SA#80 |
SP-180423 |
0015 |
1 |
A |
Clarification and removal of text |
14.1.0 |
|
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2018-12 |
SA#82 |
SP-181042 |
0016 |
1 |
F |
Add producer – consumer interaction to Annex B |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181042 |
0017 |
1 |
F |
Add producer – consumer interaction to Annex F |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181042 |
0018 |
1 |
F |
Update example of the generalization relationship |
15.1.0 |
|
2018-12 |
SA#82 |
SP-181044 |
0019 |
2 |
D |
Inconsistent definition of composition |
16.0.0 |
|
2018-12 |
SA#82 |
SP-181044 |
0020 |
– |
C |
Make the use of roles optional |
16.0.0 |
|
2018-12 |
SA#82 |
SP-181044 |
0021 |
– |
C |
Make the use of the visibility symbol optional |
16.0.0 |
|
2019-03 |
SA#83 |
SP-190132 |
0023 |
1 |
A |
Removal of reference to a temporary joint working group |
16.1.0 |
|
2019-06 |
SA#84 |
SP-190377 |
0028 |
1 |
A |
Correct style for Definition |
16.2.0 |
|
2019-12 |
SA#86 |
SP-191159 |
0035 |
– |
F |
Add passedById and other updates |
16.3.0 |
|
2019-12 |
SA#86 |
SP-191172 |
0036 |
4 |
F |
Update attribute properties table in clause 5.2.1.1 |
16.3.0 |
|
2020-03 |
SA#87E |
SP-200172 |
0037 |
– |
F |
Correct reference to NOTE in attribute properties table in clause 5.2.1.1 |
16.4.0 |
|
2022-03 |
SA#95e |
SP-220179 |
0039 |
1 |
F |
Specifying multivalue attributes |
16.5.0 |
|
2022-03 |
SA#95e |
SP-220186 |
0040 |
– |
F |
Clarify definition of AllowedValues |
17.0.0 |
|
2022-06 |
SA#96 |
SP-220510 |
0042 |
1 |
A |
Clarification of property defaultValue |
17.1.0 |
|
2022-12 |
SA#98e |
SP-221170 |
0047 |
– |
A |
Correct the wrong example for Generalization relationship notation |
17.2.0 |
|
2022-12 |
SA#98e |
SP-221168 |
0048 |
2 |
F |
Clarify definitions of attribute properties |
17.2.0 |