GB/T 17143.5-1997 Information technology Open Systems Interconnection System management Part 5: Event reporting management function
Some standard content:
GB/T17143.5-1997
This standard is equivalent to ISO/IEC10164-5:1993 "Information Technology Open Systems Interconnection System Management: Incident Report Management Function" and ISO/IEC10164-5:1993/Cor.1:1994 "Information Technology Open Systems Interconnection System Management: Incident Report Management Function Technical Modification 1".
According to ISO/IEC10164-5:1993/Cor.1:1994, this standard adds 3.7 clauses. 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 Appendices A, B and C of this standard are informative appendices. This standard was proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the Standardization Institute of the Ministry of Electronics Industry. Drafting unit of this standard: Standardization Institute of the Ministry of Electronics Industry. The main drafters of this standard are Zheng Hongren, Zhou Xiaohua and Shi Meilin. 535
GB/T 17143. 5--1997
ISO/IEC Foreword
ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) are worldwide specialized standardization organizations. National member bodies (which are all members of ISO or IEC) participate in the formulation of international standards for specific technical scopes through various technical committees established by international organizations. The technical committees of ISO and IEC cooperate in areas of common interest. Other official and non-official international organizations in contact with ISO and IEC can also participate in the formulation of international standards. For information technology, ISO and IEC have established a joint technical committee, namely ISO/IEC JTC 1. The draft international standards proposed by the joint technical committee are circulated to national member bodies for voting. At least 75% of the national member bodies participating in the voting must vote in favor of the publication of an international standard.
ISO/IEC10164-5 was developed by the ISO/IECJTC1 "Information Technology" Joint Technical Committee in cooperation with CCITT. The equivalent text is CCITT X.734.
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 representing 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 Tracking function
—Part 9: Objects and attributes of access control—Part 10: Accounting and metering function
Part 11: Workload monitoring function
—Part 12: Test management function
Part 13: Summarization function
—Part 14: Classification of credibility and diagnostic tests 536
GB/T17143.5—1997
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/T16645
GB/T17142
GB/T 17175
Information technology
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
Public management information protocol
System management overview
Management information structure
National Standard of the People's Republic of China
Information technology Open Systems Interconnection
System management
Part 5: Event report management function
Information technology-Open Systems Interconnection-Systems Menagement-Part 5: Event report management function1Scope
GB/T17143.5—1997
idtIS0/1EC10164-5: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 the event reporting management function, which consists of a service and two functional units. This function belongs to 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 event reporting management function; establish a model that links the services provided by this function to user requirements; - define the services provided by this function, - specify the protocols necessary to provide the services; - define the relationship between the service and SMI operations and notifications; define the relationship with other system management functions; - specify consistency requirements.
This standard
does not define the characteristics of any implementation intended to provide the event reporting management function, nor does it specify the manner in which management is accomplished by users of the event reporting management function; it does not define any characteristics of the interactions that lead to the use of the event reporting management function, nor does it specify the services necessary to establish, normally release, and abnormally release management contacts, nor does it specify the authorization required for the use of the event reporting management function or any related activities; nor does it define managed objects related to the management of specific protocol machines. 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 are valid. All standards are subject to revision, and parties using this standard should explore the possibility of using the latest versions of the following standards. GB9387-88 Basic reference model for open systems interconnection of information processing systems (idtISO7498:1984, eqvCCITTX200: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, eqvCCITTX.700:1992)GB/T15129-—941
Service specifications for open systems interconnection of information processing systems (idtISO/TR8509:1987, eqvCCITTX. 210:1988)
Approved by the National Technical Supervision Bureau on December 15, 1997 538
Implemented on August 1, 1998
GB/T 17143.51997
GB/T16263-1966 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): GB/T 16644—1996
Information technology Open Systems Interconnection Common Management Information Service Definition (idtISO/IEC9595：1991,eqvCCITT X.710:1991)
GB/T 17142—1997
Information technology Open Systems Interconnection System Management Overview (idtISO/IEC10040：1992) GB/T 17143.1---19971
Information technology Open Systems Interconnection System Management Part 1: Object Management Function (idtISO/IEC 10164-1:1993)
GB/T 17143.2---1997
Information technology Open Systems Interconnection
System management Part 2: State management functions (idtISO/IEC 10164-2:1993)
GB/T 17175.2—1997
Information technology Open Systems Interconnection
ISO/IEC 10165-2:1992)
GB/T 17176—1997
Management information structure Part 2: Management information definition (idtInformation technology Open Systems Interconnection Application layer structure (idtISO/IEC9545:1994)GB/T 17178. 1--1997
Information technology Open systems interconnection
Conformance test methods and frameworks
Part 1: Basic concepts
(idtISO/IEC9646-1:1994)
3 Definitions
This standard adopts the following definitions.
3.1 Basic reference model definition
This standard adopts the following terms defined in GB9387: a) open system;
b) system management.
3.2 Service agreement definition
This standard adopts the following terms defined in GB/T15129: Primitive
3.3 Management framework definition
This standard adopts the following terms defined in GB/T9387.4: a) management information;
b) managed object;
c) system management application entity.
3.4 System Management Overview Definition
This standard adopts the following terms defined in GB/T17142: a) Agent role;
b) Subordinate consistency;
c) General consistency;
d) Management support object;
e) Manager role;
f) Notification,
g) System management functional unit;
h) System management operation.
3.5 Public management information service definition
This standard adopts the following terms defined in GB/T16644: a) Attribute;
b) Public management information service;
c) Public management information service element.
3.6OSI--Conformance Test Definitions
GB/T 17143.5-—1997
This standard adopts the following terms defined in GB/T17178.1: System Conformance Statement.
3.7 Supplementary Definitions
This standard adopts the following definitions.
3.7.1Discriminator
A management support object that allows the system to select management operations and event reporting related to other managed objects. 3.7.2Discriminator Input Object A conceptual object whose attributes are either parameters of an operation or parameters of a notification. The discriminator input object is defined to perform discrimination and its instance exists only during the duration of discrimination. The discriminator input object can be used for discrimination if and only if its attributes have object identification. At this time, the attributes that do not match the rules defined for it can be checked. 3.7.3 Event forwarding discriminator event forwarding discriminator A discriminator that acts on potential event reports. 3.7.4 Event report management function The event report management function includes functions for managing the definition of supported object classes, which allows managers to control the sending of event reports from managed objects independently of the definition of managed objects.
3.7.5 Potential event report potential event report A class of discriminator input objects defined for the purpose of event forwarding discrimination. A potential event report consists of all the information that needs to be passed in the event report. This information is derived from the information contained in the notification and the information generated when the notification is processed locally (if any). Abbreviations
5 Conventions
Abstract Syntax Notation 1
Public Management Information Service
Public Management Information Service Elements
Event Forwarding Discriminator
Event Reporting Function
Identifier
Management Application Protocol Data Unit
Protocol Data Unit
System Management Application Entity
System Management Functional Unit
Management Information Structure
This standard defines services for the event reporting management function following the descriptive conventions defined in GB/T 15129. 6 Requirements
The requirements to be met are:
a) A flexible definition of event reporting control services that allows the system to select which event reports are sent to a specific management system; b) Specification of the destination to which the event reports are to be sent (e.g., management system flags); c) Specification of a mechanism for controlling the forwarding of event reports (e.g., pausing or resuming forwarding); 540
GB/T 17143. 51997
d) The ability of an external management system to modify the conditions for reporting events; e) The ability to specify a backup unit to which event reports can be sent when the original unit is unavailable. 7 Event Report Management Functional Model
7.1 General
The above functional requirements related to system behavior can be simplified to basic requirements for system behavior. It has the ability to specify the conditions that potential event reports sent by a specific managed object should meet in order to be sent to a specified destination. 7.2 Event Report Management Model
The event report management model describes the conceptual components that provide for the reporting of remote events and the local processing of potential events. This model also describes control messages, event report messages and retrieval messages. Conceptually, the event pre-processing function receives local notifications and forms potential event reports. Conceptually, these potential event reports are distributed to all event forwarding discriminators contained in the local open system. For the purpose of discrimination, potential event reports are only seen by the event forwarding discriminator as discriminator input objects and are not visible outside the local system. The event forwarding discriminator is used to decide which event reports are to be sent to a specific destination within a specified time. It can also be used to specify the mode of forwarding events (confirmed or unconfirmed). Each event forwarding discriminator can contain scheduling capabilities to determine the time period during which event reports are selected for forwarding. Each event forwarding discriminator contains a discriminator construct that specifies the characteristics that potential event reports must meet in order to be forwarded. The event reports that have been selected are forwarded to the destination as quickly as possible. The event forwarding discriminator itself is a managed object and can therefore issue notifications. These notifications are processed as potential event reports by all event forwarding discriminators, including the discriminator that generated the notification. Figure 1 is a graphical representation of the components involved in generating, processing and reporting events. Managed Objects
Event Preprocessing
Potential Event Reports
Response!
Figure 1 Event Report Management Model
7.2.1 Event Report Management Function
Event Report
Event Report Management allows an open system to establish and control the identification and forwarding of event reports to other open systems. Event reports are triggered by notifications, which are caused by events such as threshold violations or configuration status changes. The event forwarding management function provides the ability to identify the destination to which selected event reports are sent. Event Report Management provides methods by which identification and forwarding can be started, stopped, suspended or resumed, and by which the properties of the event forwarding discriminator can be read and modified. The event report management function provides the ability to establish a long-term event reporting relationship between two open systems. When the event forwarding discriminator is in the unlocked state, the reporting open system forwards the event report to the specified destination, its given operation state is allowed, and any schedule is not "off duty".
Event report management includes:
-Start event forwarding;
-End event forwarding,
--Pause event forwarding;
-Resume event forwarding;
Modify event forwarding conditions;
Retrieve event forwarding conditions.
8 Class Definition
8.1 Managed Object
GB/T 17143. 5-1997
This standard provides the class definition of managed objects, attributes and packages related to discriminators and event forwarding discriminators. 8.1.1 Discriminators
The basic superclass is the discriminator object class. Discriminators may be specialized into subclasses to define classes of management support objects that allow control of various system management functions. A discriminator provides the specification of conditions that must be satisfied before allowing management actions or notifications associated with a discriminator input object to be processed. Some conditions are common to all discriminator subclasses, others are unique to a particular discriminator subclass.
The conditions specified by a discriminator are:
The identification of a dispatch packet that determines when discriminator processing occurs; The criteria for discrimination;
The administrative and operational state of the discriminator;
The conditions specified for a particular discriminator object subclass. 8.1.1.1 Management of discriminators
A discriminator is a managed object that allows a management system to control the management actions that can be accepted by the managed system and the event reports that can be forwarded. Thus, a discriminator can be created, deleted, read, and modified. In addition, the activity of a discriminator can be suspended and resumed by manipulating its administrative state.
When a discriminator is created, the discriminator will generate an object creation notification, which will be processed by the newly created discriminator. Each discriminator has an operational state and an administrative state. The operational states defined for a discriminator are those defined in ISO/IEC 17143.2. The administrative state attributes defined for a discriminator are a subset of those defined in ISO/IEC 17143.2. Changes in operational state shall be reported using a state change notification. This notification will be processed by the affected discriminator as appropriate, either before it enters the disabled state, or after it enters the enabled state.
The operational states defined for a discriminator are enabled and disabled. For a discriminator, the enabled state is the state in which the discriminator can process discriminator input objects (unless administratively prohibited from doing so, or if any schedule is "off duty"); in the disabled state, the discriminator does not process any discriminator input objects. bzxz.net
The administrative states defined for a discriminator are "locked" and "unlocked". A discriminator's administrative state changes as a result of intervention by the management system or local administrative activity. The precise semantics of these states are defined as part of the class definition of a discriminator subclass. A management system may lock or unlock a discriminator. Whenever a discriminator's administrative state changes, the discriminator shall generate a notification. When the state changes from unlocked to locked, and the discriminator is in the permitted state, the discriminator shall not change state until the state change notification indicating the state change has been processed by the discriminator. When the discriminator state changes from locked to unlocked, the discriminator shall generate a notification indicating the state change immediately upon entering the unlocked state. The state change from unlocked to locked is considered to occur instantaneously and does not interrupt the processing of current potential event reports.
When a discriminator is deleted, the discriminator shall generate an object deletion notification and process it before being deleted. If the discriminator is in the unlocked and permitted states, it shall process the discriminator input object indicating the object deletion before it is deleted. In addition to manipulating the state of a discriminator, an administrator may change the times when a discriminator is available, as well as change the conditions under which tests of discriminator input objects may evaluate to TRUE. These changes are restricted to occur in a manner that does not affect discriminator input objects currently being processed. An availability condition shall occur when an administrator may change the times when a discriminator is available. The discriminator availability condition attribute values are a subset of those defined in ISO 17143.1. If a discriminator is available, and a scheduling attribute change causes the current time to fall outside the "available" time range, the availability condition becomes "off duty". This notification will be processed by the affected event forwarding discriminators before entering the off duty condition. No state change notification is generated for this attribute. Changes to attribute values other than changes to the administrative state, operational state, and availability state (if any) will be reported using attribute value change notifications.
In the absence of a manageable event forwarding discriminator available, a mechanism may be used to configure an open system for forwarding events (see Annex B). Such a mechanism is outside the scope of this standard. 8.1.1.2 Normal operation of a discriminator
A discriminator consists of a discriminator construct, which is a filtering mechanism that acts on the attributes of the discriminator input object. A discriminator construct is a collection of one or more assertions about the presence or value of an attribute. If a discriminator construct contains more than one assertion, the assertions are grouped together using logical operators.
A discriminator construct may specify tests for equality and inequality of attributes, tests for the presence of an attribute, and the negation of any of these conditions. Multiple conditions may be combined using AND or OR operators. When an attribute value assertion appears in a discriminator construct and the attribute is not present in the discriminator input object being tested, the result of the test for the attribute value assertion shall evaluate to FALSE. An empty discriminator construct evaluates to TRUE for any set of the discriminator input object's attributes. For a discriminator, if the discriminator construct evaluates to TRUE, the discriminator is unlocked and allowed, and the availability status (if any) is not "off duty", then the discriminator input object passes through the discriminator and will be processed further (the processing to be performed depends on the precise semantics of the discriminator subclass). If a discriminator is in the locked or disabled state, or the availability status (if any) is "off duty", then discriminator input objects are not processed by that discriminator. If a discriminator is set up so that an administrator cannot change the times when it is available, then the discriminator is considered to be always available.
8.1.1.3 Discriminator attributes
The following mandatory attributes are defined for the discriminator object class.8.1.1.3.1 Discriminator identifier
This attribute is used to uniquely identify an instance of a discriminator.8.1.1.3.2 Discriminator construction
This attribute specifies tests for information processed by the discriminator.8.1.1.3.3 Administrative status
This attribute indicates the administrative status of the discriminator. Administrative status. The following administrative status are defined: a) Unlocked: The management system allows the discriminator to process information; b) Locked: The management system prohibits the discriminator from processing information. 8.1.1.3.4 Operational status
This attribute represents the operational capability of the discriminator to perform its functions. The following operational status are defined: a) Allowed: The discriminator is operational; b) Prohibited: The discriminator is inoperable. 8.1.1.4 Discriminator notification
The following mandatory notifications are defined for the discriminator object class: a) State change,
b) Attribute value change;
c) Object creation;
d) Object deletion.
8.1.1.5 Scheduling package
GB/T 17143.5--1997
To accommodate various levels of complexity in the scheduling event reporting activity cycle, scheduling-related conditional scheduling packages are defined for event forwarding discriminators to provide discriminators with the ability to automatically switch between their reporting-on and reporting-off conditions. If no scheduling package is present in a discriminator, it is always in the reporting-on condition. 8.1.1.5.1 AvailabilityStatus Package
This conditional package shall be present if any other scheduling-related package is instantiated. This package contains the following attributes: AvailabilityStatus (AvailabilityStatus) Status) This attribute reflects the availability status of the managed object. When the resource becomes unavailable according to a predetermined schedule, its value shall be "off duty". This attribute is read-only. The value at creation time is determined by the specified scheduling parameters and the resource status. In this package, the value that needs to be set for this attribute is "off duty".
No state change notification is generated for this attribute. 8.1.1.5.2 Duration Package
The duration package provides the ability to automatically control the time when managed objects start and stop activities through the use of start time and stop time attributes.
a) Start time
This attribute defines a date and time when a managed object is unlocked and allowed to become active. If a start time attribute value is not specified in the create request, it defaults to the creation time of the managed object, making it active immediately. Changes to the start time attribute result in an attribute value change notification. b) Stoptime
This attribute defines a date and time when a managed object stops being active. If the stop time attribute value is not specified in the create request, its default value is "continuous operation". A null value is used for the stop time to indicate continuous operation. Changes to the stop time attribute result in a property value change notification. 8.1.1.5.3DaySchedulingPackage
TheDaySchedulingCondition Package provides the ability to schedule a discriminator on a 24h period. The Scheduling Attributes and their associated default values are defined as follows:Intervals of day
This attribute defines the table of time intervals (times of the day when the intervals start and the intervals end) during which the discriminator should present the "on duty" condition. Outside of these time intervals, the discriminator presents the "off duty" condition. If not specified in the create request, the default value for this component is a single interval covering the entire 24h period of a day.
8.1.1.5.4WeekSchedulingPackage
TheWeekSchedulingCondition Package provides the ability to schedule a discriminator on a weekly period. The Scheduling Attributes and their associated default values are defined as follows:Weekmask
This structured attribute defines a set of mask components, corresponding to selected days of the week, each of which specifies a set of time intervals on a 24h clock. The Weekmask attribute defaults to the "always on" scheduling criteria when the discriminator is created. The components of each mask are defined as follows:
a) Days of week
This component defines the days of the week on which the discriminator's scheduling mechanism should allow the discriminator to have intervals in which discriminator processing can occur. If this component is not present at creation time, it defaults to all seven days of the week. b) Intervals of dayThis component defines a list of time intervals (times of day when the interval starts and the interval ends) at which the discriminator will present an "on duty" condition if the current day is selected to match daysOfWeek. Outside of these time intervals, the discriminator presents an "off duty" condition. If not specified in the creation request, this component defaults to a single interval covering the full 24h period of a day. 544
8.1.1.5.5 External Scheduler Scheduling Package
GB/T 17143.5—1997
The External Scheduler Scheduling Condition Package provides the ability to schedule event reports based on a scheduling plan defined in an External Scheduler Managed Object. The "on-duty" and "off-duty" conditions of the discriminator will change according to the scheduling characteristics specified by the Scheduler Managed Object. The scheduling attributes are defined as follows:
Scheduler name
This attribute specifies the name of the Scheduler Managed Object associated with the discriminator. The relationship means that the "on-duty" and "off-duty" conditions of the discriminator should be scheduled by the external scheduler. This attribute is a read-only attribute. 8.1.2 Event Forwarding Discriminator
The Event Forwarding Discriminator allows potential event reports associated with a managed object to meet specified conditions before the event report is forwarded to a specific destination. The Event Forwarding Discriminator is a subclass of the Discriminator Object class. 8.1.2.1 Event Forwarding Discriminator Attributes
In addition to the attributes inherent to the discriminator, the event forwarding discriminator has the following attributes: Destination
The destination attribute identifies the destination to which the discriminator forwards event reports. The destination may be a single application entity title or multiple application entity titles.
8.1.2.2 Backup Destination Packet
This packet has two attributes that specify the backup destination and the current destination. This packet appears when a backup is required for a destination. 8.1.2.2.1 Backup Destination Table
The backup destination table attribute is an ordered list of application entity titles. The application entities identified in the backup destination table are AE (Application Entity) titles that are designated as event destinations in the event that the destination specified by the destination attribute fails. AE failure detection and switching backup strategies are local matters. Application entities that appear first in the table take precedence over those that follow. This attribute is not used when the destination attribute has multiple application entity titles. 8.1.2.2.2 CurrentDestination
The CurrentDestination attribute is defined as a single application entity header. The CurrentDestination attribute identifies the application entity to which the discriminator is currently forwarding events. This attribute is read-only and its value is assigned as a result of a system operation using the Destination or BackupDestination table attributes. 8.1.2.3 Mode Package
If the mode of reporting events is specified by the management system, this package has one attribute and is present when required: ConfirmedMode
This attribute has two values: Confirmed and Unconfirmed. Its value is set only at object creation time. If the attribute is not specified in the request, the mode used to send the event report is a local matter. All potential event reports forwarded by an event forwarding discriminator set to Confirmed mode are sent as Confirmed Event Reports; if the mode is set to Unconfirmed, they are sent as Unconfirmed Reports. 8.1.2.4 Event Forwarding Discriminator Characteristics
In addition to the characteristics inherent to the discriminator object class, the event forwarding discriminator exhibits the following characteristics. Tests for the following attributes of a potential event report may be specified by the discriminator construct in the event forwarding discriminator: managed object class; managed object instance; event type: - event type specific attributes, e.g., for error related events these attributes are: - severity: - backed up status; - probable cause. To perform these tests, the discriminator must understand the abstract syntax used. If the discriminator construct for the potential event report evaluates to TRUE, and the event forwarding discriminator is in the unlocked and enabled state and the availability status is not "off duty", then the event report is sent to the specified destination. 8.2 Generic definitions introduced
The following generic definitions used in this standard are defined in ISO 17143.2 and ISO 17143.1: Administrative state;
Operational state;
-Availability status
-State change notification;
Object creation notification;
Object deletion notification
Attribute value change notification.
9 Service definitions
This standard does not define any services. The services defined in other functions are described below. 9.1 Introduction
The information and management control requirements required between systems may change over time and as the management or communication environment changes. It is therefore necessary to provide a mechanism for implementing OSI management services.
It is assumed that systems should have the ability to modify the operation of event forwarding discriminators in other systems. In particular, the required operations applicable to each instance of an event forwarding discriminator are:
Create a discriminator;
Delete a discriminator;
Modify the attributes of a discriminator;
-Suspend the activity of a discriminator;
-Resume the activity of a discriminator.
These operations provide a means for the system to start/end/suspend/resume event reporting for a particular managed object. It is also considered necessary for the system to be able to modify and read any of the attributes of a particular event forwarding discriminator. The operational state attribute, the current destination attribute, the confirmation mode attribute and the availability status attribute are all read-only, they cannot be changed by administration. 9.2 Initiating event report forwarding
The PT-CREATE service defined in IEC 6143.1 is used to allow an open system to request another open system to create an event forwarding discriminator, thereby requesting the imposition of new or additional event forwarding controls. When an event forwarding discriminator is created, it generates an object creation notification indicating its administrative state, operational state, and availability status and confirmation mode (if any). Whether this notification results in the transmission of an event report depends on the administrative and operational state, availability status, and the discriminator construct that handles the potential event report.
The semantics of the discriminator attributes are defined in clause 8. The attributes and defaults for the create operation are defined as follows. Discriminator construct. This attribute specifies the test conditions used by the event forwarding discriminator when testing potential event reports. If no value is specified for this parameter in the incoming request, an empty discriminator construct shall be defined, i.e., the discriminator construct evaluates to TRUE for all potential event reports. Annex B shows an example of the value notation for a discriminator construct. Discriminator identifier: If this value is not provided, the management system shall assign a value and send it back in the response. Destination: This attribute identifies the destination to which event reports that have passed the test conditions will be sent. If no destination is specified in the request, the discriminator created uses the requester's AE (Application Entity) title as the default destination. Administrative state: This attribute specifies the administrative state when the discriminator was created. The administrative state of the discriminator is GB/T17143.2. A discriminator may be created in either the unlocked or locked state. If no administrative state is specified, the unlocked state is assumed. Operational State: This attribute specifies the operational state of the discriminator. The operational states of the discriminator are those defined in ISO/IEC 17143.2. A discriminator may be in the enabled or disabled state. The operational state shall not be specified as part of the create request, but shall be returned in the response, 546
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.