Information technology — Open Systems Interconnection — Systems Management: Usage metering function for accounting purposes — Amendment 1: Implementation conformance statement proformas

Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Gestion-systèmes: Fonction de comptage d'utilisation aux fins de comptabilité — Amendement 1: Formulaires de déclaration de conformité d'implémentation

General Information

Status
Published
Publication Date
19-Dec-1998
Current Stage
6060 - International Standard published
Start Date
20-Dec-1998
Completion Date
20-Dec-1998
Ref Project

RELATIONS

Buy Standard

Standard
ISO/IEC 10164-10:1995/Amd 1:1998 - Information technology — Open Systems Interconnection — Systems Management: Usage metering function for accounting purposes — Amendment 1: Implementation conformance statement proformas Released:12/20/1998
English language
46 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 10164-10:1995/Amd 1:1998 - Formulaires de déclaration de conformité d'implémentation
French language
46 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO/IEC
STANDARD 10164-10
First edition
1995-12-15
AMENDMENT 1
1998-12-15
Information technology — Open Systems
Interconnection — Systems Management:
Usage metering function for accounting
purposes
AMENDMENT 1: Implementation conformance
statement proformas
Technologies de l'information — Interconnexion de systèmes ouverts
(OSI) — Gestion-systèmes: Fonction de comptage d'utilisation aux fins de
comptabilité
AMENDEMENT 1: Proformes de déclaration de conformité de mise en
œuvre
Reference number
B C
ISO/IEC 10164-10:1995/Amd.1:1998(E)
---------------------- Page: 1 ----------------------
ISO/IEC 10164-10:1995/Amd.1:1998(E)
© ISO/IEC 1998

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or

mechanical, including photocopying and microfilm, without permission in writing from the publisher.

ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland
---------------------- Page: 2 ----------------------
 ISO/IEC 10164-10:1995/Amd.1:1998(E)
ISO/IEC
Contents
0AGE

1) Subclause 2.1 ................................................................................................................................................. 1

2) Subclause 2.2 ................................................................................................................................................. 1

3) New subclause 3.7.......................................................................................................................................... 1

4) Clause 4.......................................................................................................................................................... 2

5) New Annexes B to D...................................................................................................................................... 3

Annex B – MCS proforma ........................................................................................................................................ 3

Annex C – MICS proforma ....................................................................................................................................... 9

Annex D – MOCS proforma ..................................................................................................................................... 24

Annex F – MRCS proforma for name binding.......................................................................................................... 46

iii
---------------------- Page: 3 ----------------------
ISO/IEC 10164-10:1995/Amd.1:1998(E) ISO/IEC
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form

the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the

development of International Standards through technical committees established by the respective organization to deal

with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest.

Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the

work.

In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. Draft

International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication

as an International Standard requires approval by at least 75 % of the national bodies casting a vote.

Amendment 1 to ISO/IEC 10164-10:1995 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information

technology, Subcommittee SC 33, Distributed application services, in collaboration with ITU-T. The identical text is

published as ITU-T Rec. X.742/Amd.1.
---------------------- Page: 4 ----------------------
)3/�)%#�����������������!MD�����������%�
).4%2.!4)/.!,��34!.$!2$
)3/�)%#�����������������!MD�����������%�
)45�4�2EC��8������������!MD���������%�
)45�4��2%#/--%.$!4)/.
).&/2-!4)/.��4%#(./,/’9�� ��/0%.��3934%-3��).4%2#/..%#4)/.��
3934%-3��-!.!’%-%.4���53!’%��-%4%2).’��&5.#4)/.
&/2��!##/5.4).’��0520/3%3
!-%.$-%.4���
)MPLEMENTATION�CONFORMANCE�STATEMENT�PROFORMAS
�� 3UBCLAUSE����
2EPLACE�THE�EXISTING�REFERENCE�8�����BY�

– ITU-T Recommendation X.724 (1996) | ISO/IEC 10165-6:1997, )NFORMATION�TECHNOLOGY� �/PEN�3YSTEMS

)NTERCONNECTION� �3TRUCTURE�OF�MANAGEMENT�INFORMATION��2EQUIREMENTS�AND�GUIDELINES�FOR�IMPLEMENTATION

CONFORMANCE�STATEMENT�PROFORMAS�ASSOCIATED�WITH�/3)�MANAGEMENT.
�� 3UBCLAUSE����
!DD�THE�FOLLOWING�REFERENCES�

– ITU-T Recommendation X.290 (1995), /3)�CONFORMANCE�TESTING�METHODOLOGY�AND�FRAMEWORK�FOR

PROTOCOL�2ECOMMENDATIONS�FOR�)45�4�APPLICATIONS� �’ENERAL�CONCEPTS.

ISO/IEC 9646-1:1994, )NFORMATION�TECHNOLOGY� �/PEN�3YSTEMS�)NTERCONNECTION� �#ONFORMANCE�TESTING

METHODOLOGY�AND�FRAMEWORK� �0ART����’ENERAL�CONCEPTS.

– ITU-T Recommendation X.291 (1995), /3)�CONFORMANCE�TESTING�METHODOLOGY�AND�FRAMEWORK�FOR

PROTOCOL�2ECOMMENDATIONS�FOR�)45�4�APPLICATIONS� �!BSTRACT�TEST�SUITE�SPECIFICATION.

ISO/IEC 9646-2:1994, )NFORMATION�TECHNOLOGY� �/PEN�3YSTEMS�)NTERCONNECTION� �#ONFORMANCE�TESTING

METHODOLOGY�AND�FRAMEWORK� �0ART����!BSTRACT�4EST�3UITE�SPECIFICATION.

– ITU-T Recommendation X.296 (1995), /3)�CONFORMANCE�TESTING�METHODOLOGY�AND�FRAMEWORK�FOR

PROTOCOL�2ECOMMENDATIONS�FOR�)45�4�APPLICATIONS )MPLEMENTATION�CONFORMANCE�STATEMENTS.

ISO/IEC 9646-7:1995, )NFORMATION�TECHNOLOGY� �/PEN�3YSTEMS�)NTERCONNECTION� �#ONFORMANCE�TESTING

METHODOLOGY�AND�FRAMEWORK 0ART��� )MPLEMENTATION�#ONFORMANCE�3TATEMENTS.
�� .EW�SUBCLAUSE����
!DD�A�NEW�SUBCLAUSE�����AND�RENUMBER�THE�EXISTING�SUBCLAUSE�����TO�����
��� /3)�#ONFORMANCE�TESTING�DEFINITIONS

This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.290 |

ISO/IEC 9646-1:
a) PICS proform;
b) protocol implementation conformance statement;
c) system conformance statement.
)45�4�2EC��8������������!MD���������%� 1
---------------------- Page: 5 ----------------------
)3/�)%#�����������������!MD�����������%�
�� #LAUSE��
)NSERT�THE�FOLLOWING�ABBREVIATIONS�BY�ALPHABETICAL�ORDER�
ICS Implementation Conformance Statement
MCS Management Conformance Summary
MICS Management Information Conformance Statement
MIDS Management Information Definition Statement
MOCS Managed Object Conformance Statement
MRCS Managed Relationship Conformance Statement
PICS Protocol Implementation Conformance Statement
2 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 6 ----------------------
)3/�)%#�����������������!MD�����������%�
�� .EW�!NNEXES�"��#��$�AND�&
!DD�THE�FOLLOWING�ANNEXES�
!NNEX��"
-#3�PROFORMA

(This annex forms an integral part of this Recommendation | International Standard)

"�� )NTRODUCTION
"���� 0URPOSE�AND�STRUCTURE

The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and

provides information on whether the implementation claims conformance to any of the listed set of documents that

specify conformance requirements to OSI management.

The MCS proforma is a document, in the form of a questionnaire that when completed by the supplier of an

implementation becomes the MCS.
"���� )NSTRUCTIONS�FOR�COMPLETING�THE�-#3�PROFORMA�TO�PRODUCE�AN�-#3

The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is

provided in the text which precedes each table.
"���� 3YMBOLS��ABBREVIATIONS�AND�TERMS

For all annexes of this Recommendation | International Standard, the following common notations, defined in CCITT

Rec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7 are used for the Status column:

m Mandatory;
o Optional;
c Conditional;
x Prohibited;
– Not applicable or out of scope.

NOTE 1 – 'c', 'm', and 'o' are prefixed by a 'c:' when nested under a conditional or optional item of the same table;

NOTE 2 – 'o' may be suffixed by '.N' (where N is a unique number) for mutually exclusive or selectable options among a set of

status values. Support of at least one of the choices (from the items with the same values of N) is required.

For all annexes of this Recommendation | International Standard, the following common notations, defined in CCITT

Rec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7 are used for the Support column:

Y Implemented;
N Not implemented;
– No answer required;
Ig The item is ignored (i.e. processed syntactically but not semantically).
"���� 4ABLE�FORMAT

Some of the tables in this Recommendation | International Standard have been split because the information is too wide

to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the

corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts

should have the following layout:
Index First block of columns Second block of columns Etc.
_______________
#OPYRIGHT�RELEASE�FOR�-#3�PROFORMA

Users of this Recommendation | International Standard may freely reproduce the MCS proforma in this annex so that it can be

used for its intended purpose, and may further publish the completed MCS. Instructions for completing the MCS proforma are

specified in ITU-T Rec. X.724 | ISO/IEC 10165-6.
)45�4�2EC��8������������!MD���������%� 3
---------------------- Page: 7 ----------------------
)3/�)%#�����������������!MD�����������%�

In this Recommendation | International Standard the constituent parts of the table appear consecutively, starting with the

first block of columns.

When a table with subrows is too wide to fit on a page, the continuation tables(s) have been constructed with index

numbers identical to the index numbers in the corresponding rows of the first table, and with subindex numbers

corresponding to the subrows within each indexed row. For example, if Table X.1 has 2 rows and the continuation of

Table X.1 has 2 subrows for each row, the tables are presented as follows:
4ABLE�8��� �4ITLE
Support
Index A B C D E F G
1a b –
2a b –
4ABLE�8����CONTINUED�
Index Subindex H I J K L
1 1.1 h i j
1.2 h i j
2 2.1 h i j
2.2 h i j

A complete table reconstructed from the constituent parts should have the following layout:

Support
Index A B C D E F G Subindex H I J K L
1 a b – 1.1 h i j
1.2 h i j
2 a b – 2.1 h i j
2.2 h i j

References made to cells within tables shall be interpreted as references within reconstructed tables. In the example,

above, the reference X.1/1d corresponds with the blank cell in the column G for row with Index 1, and X.1/1.2b

corresponds to the blank cell in column L for row with Subindex 1.2
"�� )DENTIFICATION�OF�THE�IMPLEMENTATION
"���� $ATE�OF�STATEMENT

The supplier of the implementation shall enter the date of this statement in the box below. Use the

format DD-MM-YYYY.
Date of statement
4 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 8 ----------------------
)3/�)%#�����������������!MD�����������%�
"���� )DENTIFICATION�OF�THE�IMPLEMENTATION

The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the

system(s) in which it may reside, in the box below.
"���� #ONTACT

The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the

content of the MCS, in the box below.

"�� )DENTIFICATION�OF�THE�2ECOMMENDATION�\�)NTERNATIONAL�3TANDARD�IN�WHICH�THE�MANAGEMENT

INFORMATION�IS�DEFINED

The supplier of the implementation shall enter the title, reference number and date of the publication of the

Recommendation | International Standard which specifies the management information to which conformance is

claimed, in the box below.
Recommendation | International Standard to which conformance is claimed
"���� 4ECHNICAL�CORRIGENDA�IMPLEMENTED

The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify

the identified Recommendation | International Standard, in the box below.
"���� !MENDMENTS�IMPLEMENTED

The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the

identified Recommendation | International Standard, in the box below.
"�� -ANAGEMENT�CONFORMANCE�SUMMARY

The supplier of implementation shall state the capabilities and features supported and provide summary of conformance

claims to Recommendations | International Standards using the tables in this annex.

)45�4�2EC��8������������!MD���������%� 5
---------------------- Page: 9 ----------------------
)3/�)%#�����������������!MD�����������%�

The supplier of the implementation shall specify the roles that are supported, in Table B.1.

4ABLE�"��� �2OLES
Index Roles supported Status Support Additional information
1 Manager role support o.1
2 Agent role support o.1

The supplier of the implementation shall specify support for management information in the manager role, in Table B.2.

4ABLE�"��� �-ANAGER�ROLE�MINIMUM�CONFORMANCE�REQUIREMENT
Index Item Status Support Additional information
1 Operations on managed objects c1
2 Object creation notification from at least one c1
usage metering managed object
3 Object deletion notification from at least one c1
usage metering managed object
4 Attribute value change notification from at least c1
one usage metering managed object
5 State change notification from at least usage c1
metering managed object
6 Resume metering action to usage metering control c1
object managed object
7 Start metering action to usage metering control c1
object managed object
8 Suspend metering action to usage metering c1
control object managed object
9 Metering resumed notification from usage c1
metering control object managed object
10 Metering started notification from usage metering c1
control object managed object
11 Metering suspended notification from usage c1
metering control object managed object
12 Usage report notification from usage metering c1
data object managed object
c1: if B.1/1a then o.2 else –

The supplier of the implementation shall specify support for management information in the agent role, in Table B.3.

4ABLE�"��� �!GENT�ROLE�MINIMUM�CONFORMANCE�REQUIREMENT
Index Item Status Support Additional information
1 Usage metering control object object class c2
2 Usage metering data object object class c2
3 Usage metering record object class c2
c2: if B.1/2a then o.3 else –
4ABLE�"��� �,OGGING�OF�EVENT�RECORDS
Index Item Status Support Additional information
1 Does the implementation support logging of event c3
records in agent role?
c3: if B.1/2a then o.3 else –
6 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 10 ----------------------
)3/�)%#�����������������!MD�����������%�

NOTE – Conformance to this Recommendation | International Standard does not require conformance to CCITT Rec. X.735 |

ISO/IEC 10164-6.

The supplier of the implementation shall provide information on claims of conformance to any of the Recommendation |

International Standards summarized in Tables B.5 to B.8. For each Recommendation | International Standard that the

supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,

or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and

Additional information columns.

In Tables B.6 to B.8, the Status column is used to indicate whether the supplier of the implementation is required to

complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables

or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used

by the supplier of the implementation to indicate completion of the referenced tables or referenced items.

4ABLE�"��� �0)#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the PICS PICS of PICS
proforma proforma
1 CCITT Rec. X.730 | Annex E SM application context o
ISO/IEC 10164-1 all tables
4ABLE�"��� �-/#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the MOCS MOCS of MOCS
proforma proforma
1 CCITT Rec. X.730 | Annex C objectCreation and –c4
ISO/IEC 10164-1 objectDeletion records
2 CCITT Rec. X.730 | Annex C attribute –c5
ISO/IEC 10164-1 valueChange record
3 CCITT Rec. X.731 | Annex C stateChangeRecord – c5
ISO/IEC 10164-2 all tables
4 ITU-T Rec. X.742 | Annex D.4 usageMetering –c6
ISO/IEC 10164-10 ControlObject
5 ITU-T Rec. X.742 | Annex D.5 usageMetering –c7
ISO/IEC 10164-10 DataObject
6 ITU-T Rec. X.742 | Annex D.6 usageMeteringRecord – c8
ISO/IEC 10164-10
c4: if (B.3/1a or B.3/2a) and B.4/1a then m else –
c5: if B.3/1a and B.4/1a then m else –
c6: if B.3/1a then m else –
c7: if B.3/2a then m else –
c8: if (B.3/1a or B.3/3a) and B.4/1a then m else –
)45�4�2EC��8������������!MD���������%� 7
---------------------- Page: 11 ----------------------
)3/�)%#�����������������!MD�����������%�
4ABLE�"��� �-2#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the MRCS MRCS of MRCS
proforma proforma
1 ITU-T Rec. X.742 | Annex F usageMeter –c9
ISO/IEC 10164-10 all tables
Control-system
2 CCITT Rec. X.735 | Annex D logRecord-log – c10
ISO/IEC 10164-6
Item D.1/1
c9: if B.3/1a then o else –
c10: if B.3/3a then o else –
4ABLE�"��� �-)#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the MRCS MICS of MICS
proforma proforma
1 ITU-T Rec. X.742 | Tables C.1 management operations – c11
ISO/IEC 10164-10 and C.4
2 ITU-T Rec. X.742 | Table C.5 attributeValueChange, – c12
ISO/IEC 10164-10 objectCreation,
objectDeletion
meteringResumed,
meteringStarted,
meteringSuspended,
and usageReport
notifications
4 ITU-T Rec. X.742 | Table C.6 resumeMetering, – c13
ISO/IEC 10164-10 startMetering and
suspendMetering actions
c11: if B.2/1a then m else –

c12: if B.2/2a or B.2/3a or B.2/4a or B.2/5a or B.2/9a or B.2/10a or B.2/11a or B.2/12a then m else –

c13: if B.2/6a or B.2/7a or B.2/8a then m else –
8 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 12 ----------------------
)3/�)%#�����������������!MD�����������%�
!NNEX��#
-)#3�PROFORMA

(This annex forms an integral part of this Recommendation | International Standard)

#�� )NTRODUCTION

The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims

conformance, in the manager role, to management information specified in this Recommendation | International

Standard, to provide conformance information in a standard form.
#�� )NSTRUCTIONS�FOR�COMPLETING�THE�-)#3�PROFORMA�TO�PRODUCE�A�-)#3

The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T

Rec. X.724 | ISO/IEC 10165-6. In addition to the general guidance given in ITU-T Rec. X.724 | ISO/IEC 10165-6, the

Additional information column shall be used to identify the object classes for which the management operations are

supported. The supplier of the implementation shall state which items are supported in tables below and if necessary,

provide additional information.
#�� 3YMBOLS��ABBREVIATIONS�AND�TERMS
The following abbreviations are used throughout the MICS proforma:
smi2AttributeId {joint-iso-itu-t ms(9) smi(3) part2(2) attribute(7)
smi2Notification {joint-iso-itu-t ms(9) smi(3) part2(2) notification(10)
smi2Package {joint-iso-itu-t ms(9) smi(3) part2(2) package(4)
umf-act {joint-iso-itu-t ms(9) function(2) part10(10) action(9)
umf-att {joint-iso-itu-t ms(9) function(2) part10(10) attribute(7)
umf-mo {joint-iso-itu-t ms(9) function(2) part10(10) managedObjectClass(3)
umf-not {joint-iso-itu-t ms(9) function(2) part10(10) notification(10)
umf-par {joint-iso-itu-t ms(9) function(2) part10(10) parameter(5)
umf-pkg {joint-iso-itu-t ms(9) function(2) part10(10) package(4)
The notations used for the Status and Support columns are specified in B.1.3.
#�� 3TATEMENT�OF�CONFORMANCE�TO�THE�MANAGEMENT�INFORMATION
#���� !TTRIBUTES

The specifier of a manager role implementation that claims to support management operations on the attributes specified

in this Recommendation | International Standard shall import a copy of the following tables and complete them.

_______________
#OPYRIGHT�RELEASE�FOR�-)#3�PROFORMA

Users of this Recommendation | International Standard may freely reproduce the MICS proforma in this annex so that it can be

used for its intended purpose, and may further publish the completed MICS. Instructions for completing the MICS proforma are

specified in ITU-T Rec. X.724 | ISO/IEC 10165-6.
)45�4�2EC��8������������!MD���������%� 9
---------------------- Page: 13 ----------------------
)3/�)%#�����������������!MD�����������%�
4ABLE�#��� �!TTRIBUTE�SUPPORT
Set by create Get Replace

Index Attribute template label Value of object Constraints Status Support Status Support Status

Support
identifier for attribute and values
1 accountableObjectReference {umf-att 1} d – o.1 –
2 accountableObjectsReference {umf-att 2} c1 o.1 –
List
3 additionalInformation {smi2AttributeID 6} – o.1 –
4 additionalText {smi2AttributeID 7} – o.1 –
5 allomorphs {smi2AttributeID 50} – o.1 –
6 auditInfo {umf-att 4} – o.1 –
7 controlObjectId {umf-att 5} – o.1 –
8 controlStatus {smi2AttributeID 34} – o.1 –
9 correlatedNotifications {smi2AttributeID 12} – o.1 –
10 dataErrors {umf-att 8} – o.1 –
11 dataObjectId {umf-att 6} – o.1 –
12 dataObjectsReferenceList {umf-att 7} c1 o.1 –
13 eventTime {smi2AttributeID 13} – o.1 –
14 eventType {smi2AttributeID 14} – o.1 –
15 loggingTime {smi2AttributeID 59} – o.1 –
16 logRecordId {smi2AttributeID 3} – o.1 –
17 managedObjectClass {smi2AttributeID 60} – o.1 –
18 managedObjectInstance {smi2AttributeID 61} – o.1 –
19 nameBinding {smi2AttributeID 63} – o.1 –
20 notificationIdentifier {smi2AttributeID 16} – o.1 –
21 objectClass {smi2AttributeID 65} – o.1 –
22 operationalState {smi2AttributeID 35} – o.1 –
23 packages {smi2AttributeID 66} – o.1 –
24 proceduralStatus {smi2AttributeID 36} – o.1 –
25 providerId {umf-att 10} – o.1 –
26 reportingTriggers {umf-att 11} c1 o.1 o.1
27 usageInfo {umf-att 12} – o.1 –
c1: if C.2/1a then o.1 else –
10 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 14 ----------------------
)3/�)%#�����������������!MD�����������%�
4ABLE�#����CONCLUDED�
Add Remove Set to default
Index Status Support Status Support Status Support Additional information
1 –––
2 –––
3 –––
4 –––
5 –––
6 –––
7 –––
8 –––
9 –––
10 –––
11 –––
12 –––
13 –––
14 –––
15 –––
16 –––
17 –––
18 –––
19 –––
20 –––
21 –––
22 –––
23 –––
24 –––
25 o.1 o.1 –
26 –––
#�� #REATE�AND�DELETE�MANAGEMENT�OPERATIONS

The specifier of a manager role implementation that claims to support the create or delete management operations on the

managed objects specified in this Recommendation | International Standard shall import a copy of the following tables

and complete them.
#���� 5SAGE�METERING�CONTROL�OBJECT�MANAGED�OBJECT�CLASS
4ABLE�#��� �#REATE�AND�DELETE�SUPPORT
Index Operation Constraints and values Status Support Additional information
1 Create support usageMeteringControlObject o.4
1.1 Create with reference object – c:o
2 Delete support – o.4
)45�4�2EC��8������������!MD���������%� 11
---------------------- Page: 15 ----------------------
)3/�)%#�����������������!MD�����������%�
#���� 5SAGE�METERING�DATA�OBJECT�MANAGED�OBJECT�CLASS
4ABLE�#��� �#REATE�AND�DELETE�SUPPORT
Index Operation Constraints and values Status Support Additional information
1 Create support usageMeteringDataObject o.4
1.1 Create with reference object – c:o
2 Delete support – o.4
#���� 5SAGE�METERING�RECORD�MANAGED�OBJECT�CLASSES
4ABLE�#��� �#REATE�AND�DELETE�SUPPORT
Index Operation Constraints and values Status Support Additional information
1 Create support – x
1.1 Create with reference object – –
2 Delete support usageMeteringRecord o.4
#�� .OTIFICATIONS

The specifier of a manager role implementation that claims to support notifications specified in this Recommendation |

International Standard shall import a copy of Table C.5 and complete it.
4ABLE�#��� �.OTIFICATION�SUPPORT
Support

Index Notification type Value of object Constraints Status Confirmed Non- Additional

template label identifier and values confirmed information
for notification type
1 attributeValueChange {smi2Notification 1} c2
2 meteringResumed {umf-not 2} c3
3 meteringStarted {umf-not 3} c4
4 meteringSuspended {umf-not 4} c5
5 objectCreation {smi2Notification 6} c6
6 objectDeletion {smi2Notification 7} c7
7 stateChange {smi2Notification 14} c8
7 usageReport {umf-not 1} c9
c2: if B.2/4a then o.1 else –
c3: if B.2/9a then o.1 else –
c4: if B.2/10a then o.1 else –
c5: if B.2/11a then o.1 else –
c6: if B.2/2a then o.1 else –
c7: if B.2/3a then o.1 else –
c8: if B.2/5a then o.1 else –
c9: if B.2/512a then o.1 else –
12 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 16 ----------------------
)3/�)%#�����������������!MD�����������%�
4ABLE�#����CONTINUED�

Index Subindex Notification field Value of object identifier Constraints Status Support Additional

name label of attribute type and values information
associated with field
1 1.1 additionalInformation {smi2AttributeID 6} o
1.1.1 – c:m
identifier
1.1.2 significance – c:m
1.1.3 information – c:m
1.2 additionalText {smi2AttributeID 7} o
1.3 attributeIdentifierList {smi2AttributeID 8} o
1.3.1 globalForm – c:o.1
1.3.2 localForm – c:o.1
1.4 attributeValueChangeDefinition {smi2AttributeID 10} m
1.4.1 attributeID –m
1.4.1.1 globalForm – c:o.2
1.4.1.2 localForm – c:o.2
1.4.2 oldAttributeValue – o
1.4.3 newAttributeValue – m
1.5 correlatedNotifications {smi2AttributeID 12} o
1.5.1 correlatedNotifications – c:m
1.5.2 sourceObjectInst – c:o
1.5.2.1 distinguishedName – c:o.3
1.5.2.1.1 AttributeType – c:m
1.5.2.1.2 AttributeValue – c:m
1.5.2.2 nonSpecificForm – c:o.3
1.5.2.3 localDistinguishedName – c:o.3
1.5.2.3.1 AttributeType – c:m
1.5.2.3.2 AttributeValue – c:m
1.6 notificationIdentifier {smi2AttributeID 16} o
1.7 sourceIndicator {smi2AttributeID 26} o
2 2.1 actionResponse {umf-att 3} c:m
2.1.1 success – c:o
2.1.1.1 distinguishedName – c:o.4
2.1.1.1.1 AttributeType – c:m
2.1.1.1.2 AttributeValue – c:m
2.1.1.2 nonSpecificForm – c:o.4
2.1.1.3 localDistinguishedName – c:o.4
2.1.1.3.1 AttributeType – c:m
2.1.1.3.2 AttributeValue – c:m
2.1.2 failed – c:o
2.1.2.1 distinguishedName – c:o.5
2.1.2.1.1 AttributeType – c:m
2.1.2.1.2 AttributeValue – c:m
)45�4�2EC��8������������!MD���������%� 13
---------------------- Page: 17 ----------------------
)3/�)%#�����������������!MD�����������%�
4ABLE�#����CONTINUED�

Index Subindex Notification field Value of object identifier Constraints Status Support Additional

name label of attribute type and values information
associated with field
2.1.2.2 nonSpecificForm – c:o.5
2.1.2.3 localDistinguishedName – c:o.5
2.1.2.3.1 AttributeType – c:m
2.1.2.3.2 AttributeValue – c:m
2.1.3 indeterminate – c:o
2.1.3.1 distinguishedName – c:o.6
2.1.3.1.1 AttributeType – c:m
2.1.3.1.2 AttributeValue – c:m
2.1.3.2 nonSpecificForm – c:o.6
2.1.3.3 localDistinguishedName – c:o.6
2.1.3.3.1 AttributeType – c:m
2.1.3.3.2 AttributeValue – c:m
2.2 dataObjectsReferenceList {umf-att 7} c:m
2.2.1 distinguishedName – c:o.7
2.2.1.1 AttributeType – c:m
2.2.1.2 AttributeValue – c:m
2.2.2 nonSpecificForm – c:o.7
2.2.3 localDistinguishedName – c:o.7
2.2.3.1 AttributeType – c:m
2.2.3.2 AttributeValue – c:m
2.3 reportingTriggers {umf-att 11} c:o
2.3.1 periodic – c:o.8
2.3.1.1 days – c:o.9
2.3.1.2 hours – c:o.9
2.3.1.3 minutes – c:o.9
2.3.1.4 seconds – c:o.9
2.3.1.5 milliSeconds – c:o.9
2.3.1.6 microSeconds – c:o.9
2.3.1.7 nanoSeconds – c:o.9
2.3.1.8 picoSeconds – c:o.9
2.3.2 induced – c:o.8
2.3.3 event – c:o.8
2.3.4 stimulus – c:o.8
3 3.1 actionResponse {umf-att 3} c:m
3.1.1 success – c:o
3.1.1.1 distinguishedName – c:o.10
3.1.1.1.1 AttributeType – c:m
3.1.1.1.2 AttributeValue – c:m
14 )45�4�2EC��8������������!MD���������%�
---------------------- Page: 18 ----------------------
)3/�)%#�����������������!MD�����������%�
4ABLE�#����CONTINUED�

Index Subindex Notification field Value of object identifier Constraints Status Support Additional

name label of attribute type and values information
associated with field
3.1.1.2 nonSpecificForm – c:o.10
3.1.1.3 localDistinguishedName – c:o.10
3.1.1.3.1 AttributeType – c:m
3.1.1.3.2 AttributeValue – c:m
3.1.2 failed – c:o
3.1.2.1 distinguishedName – c:o.11
3.1.2.1.1 AttributeType – c:m
3.1.2.1.2 AttributeValue – c:m
3.1.2.2 nonSpecificForm – c:o.11
3.1.2.3 localDistinguishedName – c:o.11
3.1.2.3.1 AttributeType – c:m
3.1.2.3.2 AttributeValue – c:m
3.1.3 indeterminate – c:o
3.1.3.1 distinguishedName – c:o.12
3.1.3.1.1 AttributeType – c:m
3.1.3.1.2 AttributeValue – c:m
3.1.3.2 nonSpecificForm – c:o.12
3.1.3.3 localDistinguishedName – c:o.12
3.1.3.3.1 AttributeType – c:m
3.1.3.3.2 AttributeValue – c:m
3.2 dataObjectsReferenceList {umf-att 7} c:m
3.2.1 distinguishedName – c:o.13
3.2.1.1 AttributeType – c:m
3.2.1.2 AttributeValue – c:m
3.2.2 nonSpecificForm – c:o.13
3.2.3 localDistinguishedName – c:o.13
3.2.3.1 AttributeType – c:m
3.2.3.2 AttributeValue – c:m
3.3 reportingTriggers {umf-att 11} c:o
3.3.1 periodic – c:o.14
3.3.1.1 days – c:o.15
3.3.1.2 hours – c:o.15
3.3.1.3 minutes – c:o.15
3.3.1.4 seconds – c:o.15
3.3.1.5 milliSeconds – c:o.15
3.3.1.6 microSeconds – c:o.15
3.3.1.7 nanoSeconds – c:o.15
3.3.1.8 picoSeconds – c:o.15
)45�4�2EC��8������������
...

NORME ISO/CEI
INTERNATIONALE 10164-10
Première édition
1995-12-15
AMENDEMENT 1
1998-12-15
Technologies de l'information —
Interconnexion de systèmes ouverts
(OSI) — Gestion-systèmes: Fonction de
comptage d'utilisation aux fins de
comptabilité
AMENDEMENT 1: Formulaires de déclaration
de conformité d'implémentation
Information technology — Open Systems Interconnection — Systems
Management: Usage metering function for accounting purposes
AMENDMENT 1: Implementation conformance statement proformas
Numéro de référence
ISO/CEI 10164-10:1995/Amd.1:1998(F)
---------------------- Page: 1 ----------------------
ISO/CEI 10164-10:1995/Amd.1:1998(F)
PDF – Exonération de responsabilité

Le présent fichier PDF peut contenir des polices de caractères intégrées. Conformément aux conditions de licence d'Adobe, ce fichier peut

être imprimé ou visualisé, mais ne doit pas être modifié à moins que l'ordinateur employé à cet effet ne bénéficie d'une licence autorisant

l'utilisation de ces polices et que celles-ci y soient installées. Lors du téléchargement de ce fichier, les parties concernées acceptent de fait la

responsabilité de ne pas enfreindre les conditions de licence d'Adobe. Le Secrétariat central de l'ISO décline toute responsabilité en la

matière.
Adobe est une marque déposée d'Adobe Systems Incorporated.

Les détails relatifs aux produits logiciels utilisés pour la création du présent fichier PDF sont disponibles dans la rubrique General Info du

fichier; les paramètres de création PDF ont été optimisés pour l'impression. Toutes les mesures ont été prises pour garantir l'exploitation de

ce fichier par les comités membres de l'ISO. Dans le cas peu probable où surviendrait un problème d'utilisation, veuillez en informer le

Secrétariat central à l'adresse donnée ci-dessous.
© ISO/CEI 1998

Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publication ne peut être reproduite ni utilisée sous quelque

forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l'accord écrit de l’ISO à

l’adresse ci-après ou du comité membre de l’ISO dans le pays du demandeur.
ISO copyright office
Case postale 56 � CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax. + 41 22 734 10 79
E-mail copyright@iso.ch
Web www.iso.ch
Version française parue en 2000
ImpriméenSuisse
ii © ISO/CEI 1998 – Tous droits réservés
---------------------- Page: 2 ----------------------
© ISO/CEI ISO/CEI 10164-10:1995/Amd.1:1998(F)
Sommaire
0AGE

1) Paragraphe 2.1................................................................................................................................................ 1

2) Paragraphe 2.2................................................................................................................................................ 1

3) Nouveau paragraphe 3.7................................................................................................................................. 2

4) Article 4.......................................................................................................................................................... 2

5) Nouvelles Annexes B, C, D et F .................................................................................................................... 3

Annexe B – Formulaire MCS.................................................................................................................................... 3

Annexe C – Formulaire MICS .................................................................................................................................. 9

Annexe D – Formulaire MOCS................................................................................................................................. 24

Annexe F – Formulaire MRCS pour les corrélations de noms.................................................................................. 46

iii
---------------------- Page: 3 ----------------------
ISO/CEI 10164-10:1995/Amd.1:1998(F) © ISO/CEI
Avant-propos

L'ISO (Organisation internationale de normalisation) et la CEI (Commission électrotechnique internationale)

forment le système spécialisé de la normalisation mondiale. Les organismes nationaux membres de l'ISO ou de la

CEI participent au développement de Normes internationales par l'intermédiaire des comités techniques créés par

l'organisation concernée afin de s'occuper des domaines particuliers de l'activité technique. Les comités

techniques de l'ISO et de la CEI collaborent dans des domaines d'intérêt commun. D'autres organisations

internationales, gouvernementales et non gouvernementales, en liaison avec l'ISO et la CEI participent également

aux travaux.

Dans le domaine des technologies de l'information, l'ISO et la CEI ont créé un comité technique mixte,

l'ISO/CEI JTC 1. Les projets de Normes internationales adoptés par le comité technique mixte sont soumis aux

organismes nationaux pour vote. Leur publication comme Normes internationales requiert l'approbation de 75 % au

moins des organismes nationaux votants.

L'Amendement 1 à l'ISO/CEI 10164-10:1995 a été élaboré par le comité technique mixte ISO/CEI JTC 1,

Technologies de l'information, sous-comité SC 33, Services d'applications distribuées, en collaboration avec

l'UIT-T. Le texte identique est publié en tant que Rec. UIT-T X.742/Amd.1.
---------------------- Page: 4 ----------------------
)3/�#%)�����������������!MD�����������&�
./2-%��).4%2.!4)/.!,%
)3/#%)!MD&
2EC5)448!MD&
2%#/--!.$!4)/.��5)4�4
TECHNOLOGIES DE L'INFORMATION – INTERCONNEXION
DE SYSTÈMES OUVERTS (OSI) – GESTION-SYSTÈMES:
FONCTION DE COMPTAGE D'UTILISATION
AUX FINS DE COMPTABILITÉ
!-%.$%-%.4���
&ORMULAIRES�DE�D'CLARATION�DE�CONFORMIT'�D�IMPL'MENTATION
�� 0ARAGRAPHE����
2EMPLACER�LA�R'F'RENCE�EXISTANTE���LA�2ECOMMANDATION�8�����PAR�

– Recommandation UIT-T X.724 (1996) | ISO/CEI 10165-6:1997, 4ECHNOLOGIES� DE� L�INFORMATION�

)NTERCONNEXION�DES�SYST¤MES�OUVERTS� �3TRUCTURE�DE�L�INFORMATION�DE�GESTION��SP'CIFICATIONS�ET�DIRECTIVES

POUR� L�'TABLISSEMENT� DES� FORMULAIRES� DE� D'CLARATION� DE� CONFORMIT'� D�IMPL'MENTATIONS� ASSOCI'S� �� LA

GESTION�/3).
�� 0ARAGRAPHE����
!JOUTER�LES�R'F'RENCES�SUIVANTES�

– Recommandation UIT-T X.290 (1995), #ADRE� G'N'RAL� ET� M'THODOLOGIE� DES� TESTS� DE� CONFORMIT'

D�INTERCONNEXION�DES�SYST¤MES�OUVERTS�POUR�LES�2ECOMMANDATIONS�SUR�LES�PROTOCOLES�POUR�LES�APPLICATIONS

DE�L�5)4�4� �#ONCEPTS�G'N'RAUX.

ISO/CEI 9646-1:1994, 4ECHNOLOGIES�DE�L�INFORMATION� �)NTERCONNEXION�DE�SYST¤MES�OUVERTS��/3)�� �#ADRE

G'N'RAL�ET�M'THODOLOGIE�DES�TESTS�DE�CONFORMIT'� �0ARTIE����#ONCEPTS�G'N'RAUX.

– Recommandation UIT-T X.291 (1995), #ADRE� G'N'RAL� ET� M'THODOLOGIE� DES� TESTS� DE� CONFORMIT'

D�INTERCONNEXION�DES�SYST¤MES�OUVERTS�POUR�LES�2ECOMMANDATIONS�SUR�LES�PROTOCOLES�POUR�LES�APPLICATIONS

DE�L�5)4�4� �3P'CIFICATION�DE�SUITE�DE�TESTS�ABSTRAITE.

ISO/CEI 9646-2:1994, 4ECHNOLOGIES�DE�L�INFORMATION� �)NTERCONNEXION�DE�SYST¤MES�OUVERTS��/3)�� �#ADRE

G'N'RAL�ET�M'THODOLOGIE�DES�TESTS�DE�CONFORMIT'� �0ARTIE����3P'CIFICATION�DES�SUITES�DE�TESTS�ABSTRAITE.

– Recommandation UIT-T X.296 (1995), #ADRE�G'N'RAL�ET�M'THODOLOGIE�DES�TESTS�DE�CONFORMIT'�/3)�POUR

LES�2ECOMMANDATIONS�SUR�LES�PROTOCOLES�POUR�LES�APPLICATIONS�DE�L�5)4�4� �$'CLARATIONS�DE�CONFORMIT'

D�INSTANCE.

ISO/CEI 9646-7:1995, 4ECHNOLOGIES� DE� L�INFORMATION� � )NTERCONNEXION� DE� SYST¤MES� OUVERTS� �/3)��

%SSAIS�DE�CONFORMIT'� �-'THODOLOGIE�G'N'RALE�ET�PROC'DURES� �0ARTIE����$'CLARATIONS�DE�CONFORMIT'�DES

MISES�EN� UVRE.
2EC��5)4�4�8������������!MD���������&� 1
---------------------- Page: 5 ----------------------
)3/�#%)�����������������!MD�����������&�
�� .OUVEAU�PARAGRAPHE����

!JOUTER�UN�NOUVEAU�PARAGRAPHE�����ET�RENUM'ROTER�LE�PARAGRAPHE�����EXISTANT�EN�����

��� $'FINITIONS�DES�TESTS�DE�CONFORMIT'�/3)

La présente Recommandation | Norme internationale utilise les termes suivants définis dans la Rec. UIT-T X.290 |

ISO/CEI 9646-1:
a) formulaire PICS;
b) déclaration de conformité d'implémentation de protocole;
c) déclaration de conformité de système.
�� !RTICLE��
)NS'RER�LES�ABR'VIATIONS�SUIVANTES�PAR�ORDRE�ALPHAB'TIQUE�

ICS Déclaration de conformité d'implémentation (IMPLEMENTATION�CONFORMANCE�STATEMENT)

MCS Récapitulatif de conformité de gestion (MANAGEMENT�CONFORMANCE�SUMMARY)

MICS Déclaration de conformité d'information de gestion (MANAGEMENT� INFORMATION� CONFORMANCE

STATEMENT)

MIDS Déclaration de définition d'information de gestion (MANAGEMENT�INFORMATION�DEFINITION�STATEMENT)

MOCS Déclaration de conformité d'objet géré (MANAGED�OBJECT�CONFORMANCE�STATEMENT)

MRCS Déclaration de conformité de relation gérée (MANAGED�RELATIONSHIP�CONFORMANCE�STATEMENT)

PICS Déclaration de conformité d'implémentation de protocole (PROTOCOL�IMPLEMENTATION�CONFORMANCE

STATEMENT)
2 2EC��5)4�4�8������������!MD���������&�
---------------------- Page: 6 ----------------------
)3/�#%)�����������������!MD�����������&�
�� .OUVELLES�!NNEXES�"��#��$�ET�&
!JOUTER�LES�ANNEXES�SUIVANTES�
!NNEXE��"
&ORMULAIRE�-#3

(Cette annexe fait partie intégrante de la présente Recommandation | Norme internationale)

"�� )NTRODUCTION
"���� 0URPOSE�AND�STRUCTURE

The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and

provides information on whether the implementation claims conformance to any of the listed set of documents that

specify conformance requirements to OSI management.

The MCS proforma is a document, in the form of a questionnaire that when completed by the supplier of an

implementation becomes the MCS.
"���� )NSTRUCTIONS�FOR�COMPLETING�THE�-#3�PROFORMA�TO�PRODUCE�AN�-#3

The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is

provided in the text which precedes each table.
"���� 3YMBOLS��ABBREVIATIONS�AND�TERMS

For all annexes of this Recommendation | International Standard, the following common notations, defined in CCITT

Rec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7 are used for the Status column:

m Mandatory;
o Optional;
c Conditional;
x Prohibited;
– Not applicable or out of scope.

NOTE 1 – 'c', 'm', and 'o' are prefixed by a 'c:' when nested under a conditional or optional item of the same table;

NOTE 2 – 'o' may be suffixed by '.N' (where N is a unique number) for mutually exclusive or selectable options among a set of

status values. Support of at least one of the choices (from the items with the same values of N) is required.

For all annexes of this Recommendation | International Standard, the following common notations, defined in CCITT

Rec. X.291 | ISO/IEC 9646-2 and ITU-T Rec. X.296 | ISO/IEC 9646-7 are used for the Support column:

Y Implemented;
N Not implemented;
– No answer required;
Ig The item is ignored (i.e. processed syntactically but not semantically).
"���� 4ABLE�FORMAT

Some of the tables in this Recommendation | International Standard have been split because the information is too wide

to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the

corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts

should have the following layout:
Index First block of columns Second block of columns Etc.
_______________
$ROITS�DE�REPRODUCTION�DU�FORMULAIRE�-#3

Les utilisateurs de la présente Recommandation | Norme internationale sont autorisés à reproduire le formulaire MCS de la

présente annexe pour utiliser celui-ci conformément à son objet. Ils sont également autorisés à publier le formulaire une fois

celui-ci complété. Les instructions pour remplir le formulaire MCS sont spécifiées dans la Rec. UIT-T X.724 | ISO/CEI 10165-6.

2EC��5)4�4�8������������!MD���������&� 3
---------------------- Page: 7 ----------------------
)3/�#%)�����������������!MD�����������&�

In this Recommendation | International Standard the constituent parts of the table appear consecutively, starting with the

first block of columns.

When a table with subrows is too wide to fit on a page, the continuation tables(s) have been constructed with index

numbers identical to the index numbers in the corresponding rows of the first table, and with subindex numbers

corresponding to the subrows within each indexed row. For example, if Table X.1 has 2 rows and the continuation of

Table X.1 has 2 subrows for each row, the tables are presented as follows:
4ABLE�8��� �4ITLE
Support
Index A B C D E F G
1a b –
2a b –
4ABLE�8����CONTINUED�
Index Subindex H I J K L
1 1.1 h i j
1.2 h i j
2 2.1 h i j
2.2 h i j

A complete table reconstructed from the constituent parts should have the following layout:

Support
Index A B C D E F G Subindex H I J K L
1 a b – 1.1 h i j
1.2 h i j
2 a b – 2.1 h i j
2.2 h i j

References made to cells within tables shall be interpreted as references within reconstructed tables. In the example,

above, the reference X.1/1d corresponds with the blank cell in the column G for row with Index 1, and X.1/1.2b

corresponds to the blank cell in column L for row with Subindex 1.2
"�� )DENTIFICATION�OF�THE�IMPLEMENTATION
"���� $ATE�OF�STATEMENT

The supplier of the implementation shall enter the date of this statement in the box below. Use the

format DD-MM-YYYY.
Date of statement
4 2EC��5)4�4�8������������!MD���������&�
---------------------- Page: 8 ----------------------
)3/�#%)�����������������!MD�����������&�
"���� )DENTIFICATION�OF�THE�IMPLEMENTATION

The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the

system(s) in which it may reside, in the box below.
"���� #ONTACT

The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the

content of the MCS, in the box below.

"�� )DENTIFICATION�OF�THE�2ECOMMENDATION�\�)NTERNATIONAL�3TANDARD�IN�WHICH�THE�MANAGEMENT

INFORMATION�IS�DEFINED

The supplier of the implementation shall enter the title, reference number and date of the publication of the

Recommendation | International Standard which specifies the management information to which conformance is

claimed, in the box below.
Recommendation | International Standard to which conformance is claimed
"���� 4ECHNICAL�CORRIGENDA�IMPLEMENTED

The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify

the identified Recommendation | International Standard, in the box below.
"���� !MENDMENTS�IMPLEMENTED

The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the

identified Recommendation | International Standard, in the box below.
"�� -ANAGEMENT�CONFORMANCE�SUMMARY

The supplier of implementation shall state the capabilities and features supported and provide summary of conformance

claims to Recommendations | International Standards using the tables in this annex.

2EC��5)4�4�8������������!MD���������&� 5
---------------------- Page: 9 ----------------------
)3/�#%)�����������������!MD�����������&�

The supplier of the implementation shall specify the roles that are supported, in Table B.1.

4ABLE�"��� �2OLES
Index Roles supported Status Support Additional information
1 Manager role support o.1
2 Agent role support o.1

The supplier of the implementation shall specify support for management information in the manager role, in Table B.2.

4ABLE�"��� �-ANAGER�ROLE�MINIMUM�CONFORMANCE�REQUIREMENT
Index Item Status Support Additional information
1 Operations on managed objects c1
2 Object creation notification from at least one c1
usage metering managed object
3 Object deletion notification from at least one c1
usage metering managed object
4 Attribute value change notification from at least c1
one usage metering managed object
5 State change notification from at least usage c1
metering managed object
6 Resume metering action to usage metering control c1
object managed object
7 Start metering action to usage metering control c1
object managed object
8 Suspend metering action to usage metering c1
control object managed object
9 Metering resumed notification from usage c1
metering control object managed object
10 Metering started notification from usage metering c1
control object managed object
11 Metering suspended notification from usage c1
metering control object managed object
12 Usage report notification from usage metering c1
data object managed object
c1: if B.1/1a then o.2 else –

The supplier of the implementation shall specify support for management information in the agent role, in Table B.3.

4ABLE�"��� �!GENT�ROLE�MINIMUM�CONFORMANCE�REQUIREMENT
Index Item Status Support Additional information
1 Usage metering control object object class c2
2 Usage metering data object object class c2
3 Usage metering record object class c2
c2: if B.1/2a then o.3 else –
4ABLE�"��� �,OGGING�OF�EVENT�RECORDS
Index Item Status Support Additional information
1 Does the implementation support logging of event c3
records in agent role?
c3: if B.1/2a then o.3 else –
6 2EC��5)4�4�8������������!MD���������&�
---------------------- Page: 10 ----------------------
)3/�#%)�����������������!MD�����������&�

NOTE – Conformance to this Recommendation | International Standard does not require conformance to CCITT Rec. X.735 |

ISO/IEC 10164-6.

The supplier of the implementation shall provide information on claims of conformance to any of the Recommendation |

International Standards summarized in Tables B.5 to B.8. For each Recommendation | International Standard that the

supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,

or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and

Additional information columns.

In Tables B.6 to B.8, the Status column is used to indicate whether the supplier of the implementation is required to

complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables

or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used

by the supplier of the implementation to indicate completion of the referenced tables or referenced items.

4ABLE�"��� �0)#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the PICS PICS of PICS
proforma proforma
1 CCITT Rec. X.730 | Annex E SM application context o
ISO/IEC 10164-1 all tables
4ABLE�"��� �-/#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the MOCS MOCS of MOCS
proforma proforma
1 CCITT Rec. X.730 | Annex C objectCreation and –c4
ISO/IEC 10164-1 objectDeletion records
2 CCITT Rec. X.730 | Annex C attribute –c5
ISO/IEC 10164-1 valueChange record
3 CCITT Rec. X.731 | Annex C stateChangeRecord – c5
ISO/IEC 10164-2 all tables
4 ITU-T Rec. X.742 | Annex D.4 usageMetering –c6
ISO/IEC 10164-10 ControlObject
5 ITU-T Rec. X.742 | Annex D.5 usageMetering –c7
ISO/IEC 10164-10 DataObject
6 ITU-T Rec. X.742 | Annex D.6 usageMeteringRecord – c8
ISO/IEC 10164-10
c4: if (B.3/1a or B.3/2a) and B.4/1a then m else –
c5: if B.3/1a and B.4/1a then m else –
c6: if B.3/1a then m else –
c7: if B.3/2a then m else –
c8: if (B.3/1a or B.3/3a) and B.4/1a then m else –
2EC��5)4�4�8������������!MD���������&� 7
---------------------- Page: 11 ----------------------
)3/�#%)�����������������!MD�����������&�
4ABLE�"��� �-2#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the MRCS MRCS of MRCS
proforma proforma
1 ITU-T Rec. X.742 | Annex F usageMeter –c9
ISO/IEC 10164-10 all tables
Control-system
2 CCITT Rec. X.735 | Annex D logRecord-log – c10
ISO/IEC 10164-6
Item D.1/1
c9: if B.3/1a then o else –
c10: if B.3/3a then o else –
4ABLE�"��� �-)#3�SUPPORT�SUMMARY

Index Identification of the Table Description Constraints Status Support Table Additional

document that numbers of and values numbers information
includes the MRCS MICS of MICS
proforma proforma
1 ITU-T Rec. X.742 | Tables C.1 management operations – c11
ISO/IEC 10164-10 and C.4
2 ITU-T Rec. X.742 | Table C.5 attributeValueChange, – c12
ISO/IEC 10164-10 objectCreation,
objectDeletion
meteringResumed,
meteringStarted,
meteringSuspended,
and usageReport
notifications
4 ITU-T Rec. X.742 | Table C.6 resumeMetering, – c13
ISO/IEC 10164-10 startMetering and
suspendMetering actions
c11: if B.2/1a then m else –

c12: if B.2/2a or B.2/3a or B.2/4a or B.2/5a or B.2/9a or B.2/10a or B.2/11a or B.2/12a then m else –

c13: if B.2/6a or B.2/7a or B.2/8a then m else –
8 2EC��5)4�4�8������������!MD���������&�
---------------------- Page: 12 ----------------------
)3/�#%)�����������������!MD�����������&�
!NNEXE��#
&ORMULAIRE�-)#3

(Cette annexe fait partie intégrante de la présente Recommandation | Norme internationale)

#�� )NTRODUCTION

The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims

conformance, in the manager role, to management information specified in this Recommendation | International

Standard, to provide conformance information in a standard form.
#�� )NSTRUCTIONS�FOR�COMPLETING�THE�-)#3�PROFORMA�TO�PRODUCE�A�-)#3

The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T

Rec. X.724 | ISO/IEC 10165-6. In addition to the general guidance given in ITU-T Rec. X.724 | ISO/IEC 10165-6, the

Additional information column shall be used to identify the object classes for which the management operations are

supported. The supplier of the implementation shall state which items are supported in tables below and if necessary,

provide additional information.
#�� 3YMBOLS��ABBREVIATIONS�AND�TERMS
The following abbreviations are used throughout the MICS proforma:
smi2AttributeId {joint-iso-itu-t ms(9) smi(3) part2(2) attribute(7)
smi2Notification {joint-iso-itu-t ms(9) smi(3) part2(2) notification(10)
smi2Package {joint-iso-itu-t ms(9) smi(3) part2(2) package(4)
umf-act {joint-iso-itu-t ms(9) function(2) part10(10) action(9)
umf-att {joint-iso-itu-t ms(9) function(2) part10(10) attribute(7)
umf-mo {joint-iso-itu-t ms(9) function(2) part10(10) managedObjectClass(3)
umf-not {joint-iso-itu-t ms(9) function(2) part10(10) notification(10)
umf-par {joint-iso-itu-t ms(9) function(2) part10(10) parameter(5)
umf-pkg {joint-iso-itu-t ms(9) function(2) part10(10) package(4)
The notations used for the Status and Support columns are specified in B.1.3.
#�� 3TATEMENT�OF�CONFORMANCE�TO�THE�MANAGEMENT�INFORMATION
#���� !TTRIBUTES

The specifier of a manager role implementation that claims to support management operations on the attributes specified

in this Recommendation | International Standard shall import a copy of the following tables and complete them.

_______________
$ROITS�DE�REPRODUCTION�DU�FORMULAIRE�-)#3

Les utilisateurs de la présente Recommandation | Norme internationale sont autorisés à reproduire le formulaire MICS de la

présente annexe pour utiliser celui-ci conformément à son objet. Ils sont également autorisés à publier le formulaire une fois

celui-ci complété. Les instructions pour remplir le formulaire MICS sont spécifiées dans la Rec. UIT-T X.724 | ISO/CEI 10165-6.

2EC��5)4�4�8������������!MD���������&� 9
---------------------- Page: 13 ----------------------
)3/�#%)�����������������!MD�����������&�
4ABLE�#��� �!TTRIBUTE�SUPPORT
Set by create Get Replace

Index Attribute template label Value of object Constraints Status Support Status Support Status

Support
identifier for attribute and values
1 accountableObjectReference {umf-att 1} d – o.1 –
2 accountableObjectsReference {umf-att 2} c1 o.1 –
List
3 additionalInformation {smi2AttributeID 6} – o.1 –
4 additionalText {smi2AttributeID 7} – o.1 –
5 allomorphs {smi2AttributeID 50} – o.1 –
6 auditInfo {umf-att 4} – o.1 –
7 controlObjectId {umf-att 5} – o.1 –
8 controlStatus {smi2AttributeID 34} – o.1 –
9 correlatedNotifications {smi2AttributeID 12} – o.1 –
10 dataErrors {umf-att 8} – o.1 –
11 dataObjectId {umf-att 6} – o.1 –
12 dataObjectsReferenceList {umf-att 7} c1 o.1 –
13 eventTime {smi2AttributeID 13} – o.1 –
14 eventType {smi2AttributeID 14} – o.1 –
15 loggingTime {smi2AttributeID 59} – o.1 –
16 logRecordId {smi2AttributeID 3} – o.1 –
17 managedObjectClass {smi2AttributeID 60} – o.1 –
18 managedObjectInstance {smi2AttributeID 61} – o.1 –
19 nameBinding {smi2AttributeID 63} – o.1 –
20 notificationIdentifier {smi2AttributeID 16} – o.1 –
21 objectClass {smi2AttributeID 65} – o.1 –
22 operationalState {smi2AttributeID 35} – o.1 –
23 packages {smi2AttributeID 66} – o.1 –
24 proceduralStatus {smi2AttributeID 36} – o.1 –
25 providerId {umf-att 10} – o.1 –
26 reportingTriggers {umf-att 11} c1 o.1 o.1
27 usageInfo {umf-att 12} – o.1 –
c1: if C.2/1a then o.1 else –
10 2EC��5)4�4�8������������!MD���������&�
---------------------- Page: 14 ----------------------
)3/�#%)�����������������!MD�����������&�
4ABLE�#����CONCLUDED�
Add Remove Set to default
Index Status Support Status Support Status Support Additional information
1 –––
2 –––
3 –––
4 –––
5 –––
6 –––
7 –––
8 –––
9 –––
10 –––
11 –––
12 –––
13 –––
14 –––
15 –––
16 –––
17 –––
18 –––
19 –––
20 –––
21 –––
22 –––
23 –––
24 –––
25 o.1 o.1 –
26 –––
#�� #REATE�AND�DELETE�MANAGEMENT�OPERATIONS

The specifier of a manager role implementation that claims to support the create or delete management operations on the

managed objects specified in this Recommendation | International Standard shall import a copy of the following tables

and complete them.
#���� 5SAGE�METERING�CONTROL�OBJECT�MANAGED�OBJECT�CLASS
4ABLE�#��� �#REATE�AND�DELETE�SUPPORT
Index Operation Constraints and values Status Support Additional information
1 Create support usageMeteringControlObject o.4
1.1 Create with reference object – c:o
2 Delete support – o.4
2EC��5)4�4�8������������!MD���������&� 11
---------------------- Page: 15 ----------------------
)3/�#%)�����������������!MD�����������&�
#���� 5SAGE�METERING�DATA�OBJECT�MANAGED�OBJECT�CLASS
4ABLE�#��� �#REATE�AND�DELETE�SUPPORT
Index Operation Constraints and values Status Support Additional information
1 Create support usageMeteringDataObject o.4
1.1 Create with reference object – c:o
2 Delete support – o.4
#���� 5SAGE�METERING�RECORD�MANAGED�OBJECT�CLASSES
4ABLE�#��� �#REATE�AND�DELETE�SUPPORT
Index Operation Constraints and values Status Support Additional information
1 Create support – x
1.1 Create with reference object – –
2 Delete support usageMeteringRecord o.4
#�� .OTIFICATIONS

The specifier of a manager role implementation that claims to support notifications specified in this Recommendation |

International Standard shall import a copy of Table C.5 and complete it.
4ABLE�#��� �.OTIFICATION�SUPPORT
Support

Index Notification type Value of object Constraints Status Confirmed Non- Additional

template label identifier and values confirmed information
for notification type
1 attributeValueChange {smi2Notification 1} c2
2 meteringResumed {umf-not 2} c3
3 meteringStarted {umf-not 3} c4
4 meteringSuspended {umf-not 4} c5
5 objectCreation {smi2Notification 6} c6
6 objectDeletion {smi2Notification 7} c7
7 stateChange {smi2Notification 14} c8
7 usageReport {umf-not 1} c9
c2: if B.2/4a then o.1 else –
c3: if B.2/9a then o.1 else –
c4: if B.2/10a then o.1 else –
c5: if B.2/11a then o.1 else –
c6: if B.2/2a then o.1 else –
c7: if B.2/3a then o.1 else –
c8: if B.2/5a then o.1 else –
c9: if B.2/512a then o.1 else –
12 2EC��5)4�4�8������������!MD���������&�
---------------------- Page: 16 ----------------------
)3/�#%)�����������������!MD�����������&�
4ABLE�#����CONTINUED�

Index Subindex Notification field Value of object identifier Constraints Status Support Additional

name label of attribute type and values information
associated with field
1 1.1 additionalInformation {smi2AttributeID 6} o
1.1.1 – c:m
identifier
1.1.2 significance – c:m
1.1.3 information – c:m
1.2 additionalText {smi2AttributeID 7} o
1.3 attributeIdentifierList {smi2AttributeID 8} o
1.3.1 globalForm – c:o.1
1.3.2 localForm – c:o.1
1.4 attributeValueChangeDefinition {smi2AttributeID 10} m
1.4.1 attributeID –m
1.4.1.1 globalForm – c:o.2
1.4.1.2 localForm – c:o.2
1.4.2 oldAttributeValue – o
1.4.3 newAttributeValue – m
1.5 correlatedNotifications {smi2AttributeID 12} o
1.5.1 correlatedNotifications – c:m
1.5.2 sourceObjectInst – c:o
1.5.2.1 distinguishedName – c:o.3
1.5.2.1.1 AttributeType – c:m
1.5.2.1.2 AttributeValue – c:m
1.5.2.2 nonSpecificForm – c:o.3
1.5.2.3 localDistinguishedName – c:o.3
1.5.2.3.1 AttributeType – c:m
1.5.2.3.2 AttributeValue – c:m
1.6 notificationIdentifier {smi2AttributeID 16} o
1.7 sourceIndicator {smi2AttributeID 26} o
2 2.1 actionResponse {umf-att 3} c:m
2.1.1 success – c:o
2.1.1.1 distinguishedName – c:o.4
2.1.1.1.1 AttributeType – c:m
2.1.1.1.2 AttributeValue – c:m
2.1.1.2 nonSpecificForm – c:o.4
2.1.1.3 localDistinguishedName – c:o.4
2.1.1.3.1 AttributeType – c:m
2.1.1.3.2 AttributeValue – c:m
2.1.2 failed – c:o
2.1.2.1 distinguishedName – c:o.5
2.1.2.1.1 AttributeType – c:m
2.1.2.1.2 AttributeValue – c:m
2EC��5)4�4�8������������!MD���������&� 13
---------------------- Page: 17 ----------------------
)3/�#%)�����������������!MD�����������&�
4ABLE�#����CONTINUED�

Index Subindex Notification field Value of object identifier Constraints Status Support Additional

name label of attribute type and values information
associated with field
2.1.2.2 nonSpecificForm – c:o.5
2.1.2.3 localDistinguishedName – c:o.5
2.1.2.3.1 AttributeType – c:m
2.1.2.3.2 AttributeValue – c:m
2.1.3 indeterminate – c:o
2.1.3.1 distinguishedName – c:o.6
2.1.3.1.1 AttributeType – c:m
2.1.3.1.2 Attribut
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.