This standard defines object management functions consisting of services, function lists and class definitions. GB/T 17143.1-1997 Information technology Open Systems Interconnection System management Part 1: Object management functions GB/T17143.1-1997 Standard download decompression password: www.bzxz.net

GB/T17143.1—1997
This standard is equivalent to ISO/IEC10164-1:1993 "Information technology Open Systems Interconnection System Management Part 1: Object
Management functions".
GB/T17143, under the general title of "Information Technology Open Systems Interconnection System Management", currently includes the following 8 parts: Part 1 (i.e. GB/T17143.1): Object management function Part 2 (i.e. GB/T17143.2): State management function Part 3 (i.e. GB/T17143.3): Attributes representing relationships Part 4 (i.e. GB/T17143.4): Alarm reporting function Part 5 (i.e. GB/T17143.5): Event report management function Part 6 (i.e. GB/T17143.6): Log control function Part 7 (i.e. GB/T17143.7): Security alarm reporting function Part 8 (i.e. GB/T17143.8): Security audit tracking function This standard is proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the Standardization Research Institute of the Ministry of Electronics Industry. The drafting unit of this standard: the Standardization Research Institute of the Ministry of Electronics Industry. The main drafters of this standard: Zheng Hongren, Zhou Xiaohua, Zhao Xiaofan. 458
GB/T 17143. 1—-1997
ISO/IEC Foreword
ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) are specialized organizations for standardization worldwide. National member bodies (which are members of ISO or IEC) participate in the development of international standards for specific technical ranges through technical committees established by international organizations. ISO and IEC technical committees cooperate in areas of common interest. Other official and non-official international organizations in contact with ISO and IEC may also participate in the development of international standards. For information technology, ISO and IEC have established a joint technical committee, ISO/IECJTC1. Draft international standards proposed by the joint technical committee are circulated to national member bodies for voting. To publish an international standard, at least 75% of the national member bodies participating in the voting must vote in favor.
ISO/IEC10164-1 was developed by the ISO/IECJTC1\Information Technology" Joint Technical Committee in cooperation with CCITT. The equivalent text is CCITT X.730.
ISO/IEC10164, under the general title of "Information Technology Open Systems Interconnection System Management", currently includes the following 14 parts: Part 1: Object management function
~Part 2: State management function
Part 3: Attributes of representation relationships
Part 4: Alarm reporting function
Part 5: Incident report management function
Part 6: Log control function
Part 7: Security alarm reporting function
-Part 8: Security audit trail function||tt| |Part 9: Objects and attributes of access control Part 10: Accounting and metering functions
Part 11: Workload monitoring functions
Part 12: Test management functions
Part 13: Summarization functions
Part 14: Credibility and diagnostic test classification 59
GB/T17143.11997
GB/T17143 is a standard consisting of multiple parts formulated in accordance with GB9387 and GB/T9387.4. GB/T17143 is related to the following standards:
GB/T 16644
GB/T 17142
GB/T 17175
GB/T 16645
Information technology
Information technology
Information technology
Information technology
Open systems interconnection
Open systems interconnection
Open systems interconnection
Open systems interconnection
Public management information service definition
System management overview
Management information structure
Public management information protocol
National standard of the People's Republic of China
Open systems interconnectionSystems management
Information technology #
Part 1: Object management functions
Information technology-Open Systems InterconnectionSystems Management--Part 1:Object management function1Scope
GB/T17143.1—1997
idt IS0/IEC 10164-1: 1993
This standard defines a system management function for application processes to interact in a centralized or decentralized management environment for system management as defined in GB/T9387.4. This standard defines an object management function consisting of a service function unit and a class definition. This standard is located in the application layer of GB9387 and is defined according to the model provided by GB/T17176. The role of the system management function is described by GB/T17142.
This standard
Establish user requirements for the object management function, establish a model that links the services and class definitions provided by this function to user requirements; - define the services provided by this function; define the generic notification types and parameters compiled according to GB/T17175.4; specify the protocols necessary to provide services; define the relationship between services and management operations and notifications; - specify the requirements that other standards that use these generic definitions should comply with; define the relationship with other system management functions; specify consistency requirements.
This standard
Does not define the characteristics of any implementation intended to provide object management functions; - does not specify the way in which management is accomplished by users of the object management function; - does not define any characteristics of the interaction that leads to the use of the object management function; - does not specify the services necessary to establish, normally release, and abnormally release management connections; - does not exclude the definition of further notification types; - does not define managed objects.
2 Referenced standards
The provisions contained in the following standards constitute the provisions of this standard through reference in this standard. At the time of publication of this standard, the versions shown were valid. All standards are subject to revision and parties using this standard should investigate the possibility of using the most recent versions of the following standards. GB9387-88 Basic reference model for open systems interconnection of information processing systems (idtISO7498:1984, eqvCCITTX.200:1988)
GB/T9387.4—1996 Basic reference model for open systems interconnection of information processing systems Part 4: Management framework (idtISO/IEC 7498-4:1989, eqvCCITT X.700:1992)Approved by the State Administration of Technical Supervision on December 15, 1997 and implemented on August 1, 1998
GB/T 15129—94
GB/T 17143. 1-1997
Service conventions for open systems interconnection of information processing systems (idtISO/TR8509:1987, eqvCCITTX. 210:1988)
GB/T 16263-19961
Information technology Open Systems Interconnection Abstract Syntax Notation One (ASN.1) Basic Encoding Rules Specification (idt ISO/IEC 8825:1990,eqv CCITT X.209:1988)Information technology Open Systems Interconnection Common Management Information Service Definition (idtISO/IEC9595：GB/T 16644--1996
1991,eqv CCITT X. 710:1991)
Information technology Open Systems Interconnection System Management Overview (idtISO/IEC10040：1992)GB/T 17142-1997
GB/T 17143.4—1997
Information technology Open Systems Interconnection System Management Part 4: Alarm Reporting Function (idtISO/IEC 10164-4:1992)
GB/T 17143. 5--1997
System management Part 5: Event reporting management function (idt Information technology Open Systems Interconnection
ISO/IEC 10164-5:1993)
GB/T 17143.6-1997
Information technology Open Systems Interconnection
IEC 10164-6:1993)
GB/T 17175.1—1997
Information technology Open Systems Interconnection
ISO/IEC 10165-1:1993)
Information technology Open Systems Interconnection
GB/T 17175. 2—1997
ISO/IEC 10165-2:1992)
System management Part 6: Log control function (idtISO/Management information structure Part 1: Management information model (idtManagement information structure Part 2: Management information definition (idtGB/T 17175.4—1997
Information technology Open Systems Interconnection
Management information structure
Part 4: Guide to the definition of managed objects (idtISO/IEC10165-4:1992)GB/T 17176--19971
Information technology Open systems interconnection Application layer architecture (idtISO/IEC9545:1994) Information technology Open systems interconnection
GB/T 17178.1—1997
Conformance test methods and framework Part 1: Basic concepts (idt ISO/IEC 9646-1:1994)
3 Definitions
This standard adopts the following definitions.
3.1 Basic reference model definitions
This standard adopts the following terms defined in GB9387: a) open system,
b) system management;
c) layer management,
d) OSI environment.
3.2 Management framework definitions
This standard adopts the following terms defined in GB/T9387.4: managed object.
3.3 CMIS Definitions
This standard adopts the following terms defined in GB/T16644: Attribute.
3.4 ​​System Management Overview Definitions
This standard adopts the following terms defined in GB/T17142: a) Agent,
b) Agent role;
c) Dependent consistency;
d) General consistency;
e) Class definition;
f) Managed object class;
g) Manager;
b) Manager role;
i) Notification;
i) System management functional unit;
k) System management function;
1) System management application protocol;
m) (System management) operation.
3.5 Management Information Model Definition
GB/T 17143.1-1997
This standard adopts the following terms defined in GB/T17175.1: managed object boundary.
3.6 Service Agreement Definition
This standard adopts the following terms defined in GB/T15129: a) confirmation (primitive);
b) confirmed service;
c) indication (primitive);
d) non-confirmed service;
e) request (primitive);
f) response (primitive);
g) service user;
h) service provider.
3.7 OSI Conformance Test Definition
This standard adopts the following terms defined in GB/T17178.1: system conformance statement.
4 Abbreviations
5 Conventions
Abstract Syntax Notation I
Common Management Information Service
Management Application Protocol Data Unit
Open Systems Interconnection
System Management Application Protocol Machine
Management Information Structure
This standard defines services for object management functions following the descriptive conventions defined in GB/T 15129. In clause 9, the definition of each service includes a table listing the service parameters. For a given service primitive, the presence of each parameter is described by one of the following values: M
The parameter is mandatory;
The parameter value is equal to the value of the parameter in the left column;
GB/T 17143. 1—1997
The use of this parameter is an option for the service user; This parameter is not present in the interaction described by this primitive; The parameter is conditional;
The parameter is subject to mandatory constraints of GB/T 16644.
Note: Parameters marked with "P" in the service tables of this standard are directly mapped to the corresponding parameters of the CMIS service primitives without changing the semantics or syntax of the parameters. The remaining parameters are used to construct the MAPDU. 6 Requirements
The management information service (MIS) user requires the following capabilities: create and delete managed objects;
- inspect and modify the attribute values ​​of managed objects; and be aware of configuration changes of managed objects.
7 Model
7.1 Introduction
Each resource subject to system management is represented by a managed object. These are described in ISO/IEC 17175.1. Managed objects can be created and deleted, and the attribute values ​​of managed objects can be changed, using one or more of the following three different methods:
Through configuration procedures in the local system environment outside the scope of OSI; Through (N) layer operations and/or layer management described in the (N) layer standards in open systems; Through OSI system management services.
The services described by object management are:
Reporting the creation and deletion of managed objects;
Reporting changes in the values ​​of managed object attributes.
The traversal services described by object management are:
Creation and deletion of managed objects;
Performing actions on managed objects;
Attribute changes;
Attribute reads;
Event reporting.
7.2 Traversal Services
Different parts of a system management function define operations or notifications independently of mapping them to the underlying communication services. This allows other system management functions or managed objects to use this standard beyond the scope of the underlying communication services. When a system management function defines specific system management services, these services should map directly to CMIS services. To achieve this, a standard requiring system management must describe in detail the mapping between operations and notifications that apply to traversing the boundaries of a managed object and the underlying communication services. This standard is used to document such mappings. Currently, only the mapping to CMIS is defined by this standard using the penetration service. Except where this standard describes specific services, management operations and notifications that apply across the boundaries of managed objects should be mapped to the penetration services of this standard, as shown in Table 1.
Management operations are described in GB/T17175.1. 464
Default replacement
8 Generic definition
Structure of management information (SMI)
GB/T 17143.1—1997
Table 1 Mapping of penetration service
PT-CREATE
PT-DELETE
PT-ACTION
PT-SET
PT-SET
PT-SET
PT-GET
PT-EVENT-REPORT
Prague (PT)
The generic notifications, parameters and semantics set defined by this standard give details of the following general parameters of the M-EVENT-REPORT service defined in GB/T 16644:
Event type;
Event information;
Event response.
All notifications are potential items in the system management log. This standard defines three managed object classes for this purpose. GB/T17175.2 defines a generic event log record object class from which all items are derived, additional information specified by the event information, and event response parameters. 8.1Event Type
This parameter defines the type of event. This standard defines the following three event types:Object Creation: Indicates that a managed object instance has been created. Where a managed object class is required to report the creation of a managed object instance, the managed object class shall enter the object creation notification type. The creation of a managed object in an open system can be the result of a PTCREATE service or the result of a local operation in the open system;Object Deletion: Indicates that a managed object instance has been deleted. Where a managed object class is required to report the deletion of a managed object instance, the managed object class shall enter the object deletion notification type. The deletion of a managed object in an open system can be the result of a PTDELETE service or the result of a local operation in the open system;Attribute Value Change: Indicates that the attribute value of a managed object has been changed. This notification type is used to report one or more of the following, either by internal operation of the resource or via management operation: a) adding one or more new members to one or more valued set attributes; b) removing one or more members from one or more valued set attributes; c) replacing the value of one or more attributes;
d) changing the value of one or more attributes to their default values. This notification type MUST NOT be used to convey attribute value changes that have specific notification types defined. It is the responsibility of the managed object class definer to fully and in detail describe the requirements that a managed object class has for generating one or more of the above notification types. For attribute value change notifications, this includes identifying which attributes, and which changes in the values ​​of those attributes, are significant enough to warrant notification.
8.2 Event Information
The following parameters constitute the event information specific to notification. 8.2.1 Object Creation Notification Parameters
The following parameters are defined for object creation notifications. 8.2.1.1 Source indicator
GB/T 17143. 11997
When this parameter is present, it indicates the source of the operation that caused this notification type to be generated. It can have one of the following values: Resource operation: the notification is generated in response to a creation caused by an internal operation of the resource; Management operation: the notification is generated in response to a creation caused by an SMI management operation that acts on a managed object by crossing the external boundary of the managed object;
-Unknown: the source of the operation cannot be determined.
8.2.1.2 Attribute table
When this parameter is present, it contains an attribute table and the attribute values ​​at the time of the creation of the managed object. The managed object class definition can specify which attributes are to be included in the table. If the attribute table is not specified by the managed object class definition and the parameter is present in the notification, all attributes of the created managed object shall be included in the table.
8.2.1.3 Other Information
The following parameters defined in ISO/IEC 17143.4 may also be used: Additional Information;
Additional Text;
-Related Notification;
Notification Identifier.
8.2.2 Object Deletion Notification Parameters
The following parameters are defined for Object Deletion Notification. 8.2.2.1 Source Indicator
When this parameter is present, it indicates the source of the operation that caused this type of notification to be generated. It may have one of the following values: Resource Operation: the notification was generated in response to a deletion caused by an operation internal to the resource; Management Operation: the notification was generated in response to a deletion caused by an SMI management operation acting on a managed object across the external boundary of the managed object;
-Unknown: the source of the operation cannot be determined.
8.2.2.2 Attribute List
When this parameter is present, it contains an attribute list and the attribute values ​​of the managed object just before it is deleted. The managed object class definition may specify which attributes are to be included in the table. If the attribute table is not specified by the managed object class definition and the parameter is present in the notification, all attributes of the managed object shall be included in the table. 8.2.2.3 Other information
The following parameters defined in ISO/IEC 17143.4 may also be used: Additional information;
Additional text;
Related notification;
Notification identifier.
8.2.3 Attribute value change notification parameters
The following parameters are defined for attribute value change notifications. 8.2.3.1 Source indicator
When this parameter is present, it indicates the source of the operation that caused this notification type to be generated. It may have one of the following values: Resource operation: the notification is generated in response to an attribute value change caused by an operation internal to the resource; Management operation: the notification is generated in response to an attribute value change caused by an SMI management operation acting on the managed object across the external boundaries of the managed object;
Unknown: the source of the operation cannot be determined.
8.2.3.2 Attribute Identifier Table
GB/T 17143. 1—1997
When this parameter appears, it identifies the attribute set whose value change is reported. 8.2.3.3 Attribute Value Change Definition
This parameter set consists of a sequence of the following three parameters: attribute identifier, old attribute value, and new attribute value. Each sequence describes a single attribute value change. At least one new attribute value shall appear in this table. 8.2.3.3.1 Attribute Identifier
This parameter identifies the attribute whose value change is reported. 8.2.3.3.2 Old Attribute Value
When this parameter appears, it identifies the original value of the attribute. 8.2.3.3.3 New Attribute Value
This parameter identifies the current value of the attribute.
8.2.3.4 Other Information
The following parameters defined in GB/T 17143.4 may also be used: Additional Information;
Additional Text;
-Related Notifications;
Notification Identifier.
8.3 Event Responses
This standard does not specify the information used in the parameters of an Event Response. 8.4 Managed Objects
8.4.1 Object Creation Record
An Object Creation Record is a Managed Object class that is derived from the Event Log Record object class defined in GB/T 17143.6. The Object Creation Record object class represents the information stored in the log generated by an Object Creation Notification. 8.4.2 Object Deletion Record
An Object Deletion Record is a Managed Object class that is derived from the Event Log Record object class defined in GB/T 17143.6. The Object Delete Record object class represents the information stored in the log generated by an object delete notification. 8.4.3 Attribute Value Change Record
An Attribute Value Change Record is a managed object class that is derived from the Event Log Record object class defined in GB/T 17143.6. The Attribute Value Change Record object class represents the information stored in the log generated by an Attribute Value Change Notification. 8.5 Conformance
The managed object class definition supports the functionality defined in this standard by referencing the notification samples defined in GB/T 17175.2 in conjunction with the notification type specifications defined in this standard. The reference mechanism is defined in GB/T 17143.4. For each introduced notification, the managed object class definition shall specify in the action clause which optional and conditional parameters are to be used, as well as any further restrictions on their use and their values. It is allowed to declare that the use of parameters is reserved as optional. 9 Service Definition
9.1 Introduction
This standard provides nine services, six of which are penetration services. They are identified as follows, together with the parameters they carry. 9.2 Object Creation Report Service
This service allows a MIS user, in the role of an agent, to report the creation of a managed object. It can be defined as either a confirmed or unconfirmed service.
The Object Creation Report Service uses the parameters defined in Chapter 8 of this standard, as well as the general MFVENT-REPORT service parameters defined in GB/T 16644.
GB/T 17143. 11997
Table 2 lists the parameters of the Object Creation Report Service. The event time, related notification and notification identifier parameters can be assigned by the notifying object or the managed system. Table 2 Object creation report parameters
Parameter name
Call identifier
Managed object class
Managed object instance
Event type
Event time
Event information
Source indicatorwwW.bzxz.Net
Attribute table
Notification identifier
Related notifications
Additional text
Additional information
Current time
Event response
9.3 Object Deletion Report Service
Req/Ind
Rsp/Canf
This service allows a MIS user to report the deletion of a managed object in the role of an agent. It can be defined as a confirmed or unconfirmed service.
The Object Deletion Report Service uses the parameters defined in Chapter 8 of this standard and the J General M
EVENT-REPORT service parameters defined in GB/T16644.
Table 3 lists the parameters of the Object Deletion Report Service. The event time, related notification and notification identifier parameters can be assigned by the object that issues the notification or the managed system. Table 3 Object deletion report parameters
Parameter name
Call identifier
Managed object class
Managed object instance
Event type
Event time
Event information
Source indicator
Attribute table
Req/Ind
Rsp/Conf
Notification identifier
Related notification
Additional text
Additional information
Current time
Event response
Parameter name
9.4 Attribute value change report service
GB/T 17143. 1—1997
Table 3 (end)
Req/Ind
Rsp/Conf
This service allows a MIS user to report changes in the attribute values ​​of a managed object in the role of an agent. It can be defined as a confirmed or unconfirmed service.
The attribute value change report service uses the parameters defined in Chapter 8 of this standard and the general M-EVENT-REPORT service parameters defined in GB/T16644.
Table 4 lists the parameters of the attribute value change report service. The event time, related notification and notification identifier parameters can be assigned by the object issuing the notification or the managed system. Table 4 Attribute Value Change Report Parameters
Parameter Name
Call Identifier
Managed Object Class
Managed Object Instance
Event Type
Event Time
Event Information
Source Indicator
Attribute Identifier Table
Attribute Value Change Definition
Attribute Identifier
Old Attribute Value
New Attribute Value
Notification Identifier
Related Notification
Additional Text
Additional Information
Current Time
Event Response
Req/Ind
Rsp/Conf
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.