semi合集-English.pdf - 第3478页

SEMI E134-0305 © SEMI 2004, 2005 31 11.1.3 EventRequest — Identifies an event generated by a speci fic so urce that the consumer is requesting to be reported when the DCP is activated. The equ ipment shall report only th…

100%1 / 7923
SEMI E134-0305 © SEMI 2004, 2005 30
consumer with sufficient privilege (see Section 10) using the DataCollectionManager’s ActivatePlan and
GetPlanDefinition operations, respectively. Built-in DCPs cannot be deleted by any consumer.
11.1.2.2 DataCollectionPlan Attribute Definition Table
Table 41 DataCollectionPlan Attribute Definition
Attribute Name Definition Form
name Consumer-defined (or supplier-defined, in the
case of built-in DCPs) human-readable name
for the DCP.
Text.
id Consumer-defined (or supplier-defined, in the
case of built-in DCPs) unique identifier for the
DCP.
Text, unique across all DCP definitions on the
equipment, formatted according to the ISO
11578:1996 definition of UUID.
description Consumer-defined (or supplier-defined, in the
case of built-in DCPs) description of the
purpose of the DCP.
Text.
intervalInMinutes The preferred number of minutes for which the
equipment shall buffer all data described by the
plan.
Positive integer 0. See Section 11.1.2.3 for
further explanation.
isPersistent Whether or not the DCP, once activated, shall
remain activated across equipment shutdowns.
Boolean. See behavior defined in Section
12.1.5.
11.1.2.3 intervalInMinutes
11.1.2.3.1 If the value of this field is zero, events and exceptions contained in the plan shall be reported to the
consumer when they occur, and trace reports contained in the plan shall be reported according to their individual
buffer settings (see the description of the TraceRequest type in Section 11.1.5).
11.1.2.3.2 If the value of this field is greater than zero, upon activation of the DCP, any exceptions, events, or traces
defined in the plan that occur during this time span shall be buffered on the equipment in the order that they occur.
Buffered data shall be reported at the end of the interval, or when the equipment’s buffering capacity for the
currently active DCPs is reached, whichever is sooner. After each interval expires, the equipment shall begin
buffering new data for the next interval, again sending the results when the interval expires (or buffering capacity is
reached). Each result sent shall contain only the data collected during that interval. The equipment shall continue
this buffering/sending cycle as long as the DCP is active.
11.1.2.3.3 All data sent is formatted using the DataCollectionReport format described in Section 14.1.1.1.
11.1.2.4 DataCollectionPlan Association Definition Table
Table 42 DataCollectionPlan Association Definition
Association Role Name Definition Comments
eventRequests A set of events that the consumer is requesting to
be reported for this plan.
List of structured data, of type EventRequest,
described in Section 11.1.3.
exceptionRequests A set of exceptions that the consumer is
requesting to be reported for this plan.
List of structured data of type ExceptionRequest,
described in Section 11.1.4.
traceRequests A set of trace data collection activities that the
consumer is requesting to be reported for this
plan.
List of structured data of type TraceRequest,
described in Section 11.1.5.
SEMI E134-0305 © SEMI 2004, 2005 31
11.1.3 EventRequest — Identifies an event generated by a specific source that the consumer is requesting to be
reported when the DCP is activated. The equipment shall report only those events matching both the source and id
attributes specified in the EventRequst. The format for sending an event report is described in Section 14.1. The
equipment shall support multiple DCPs requesting the same event, with different sets of requested parameters. It
shall be an error to request the same event more than once in the same DCP (see Section 9.1.2.2.7).
11.1.3.1 EventRequest Attribute Definition Table
Table 43 EventRequest Attribute Definition
Attribute Name Definition Form
sourceId The source of the event. Text, formatted according to the convention used to identify an
event source. See limitations, Section 3.1.1.
eventId The identifier for the event. Text, formatted according to the convention used to identify a
specific event. See limitations, Section 3.1.1.
11.1.3.2 EventRequest Association Definition Table
Table 44 EventRequest Association Definition
Association Role Name Definition Comments
parameterRequests A set of parameters that the
consumer is requesting to be
reported when the requested event is
detected
Ordered list of structured data, of type ParameterRequest,
described in Section 11.1.5.6 . The order of the
ParameterRequests appearing in an EventRequest determines
the order in which those Parameter values will be reported in
the corresponding EventReport (see Section 14.1.3).
11.1.4 ExceptionRequest — Identifies an exception or class of exceptions that the consumer is requesting to be
reported when the DCP is activated. The format for sending an exception report is described in Section 14.1. The
equipment shall support multiple DCPs requesting the same exception criteria. It shall be an error to request the
same exception criteria more than once in the same DCP (see Section 9.1.2.2.8).
11.1.4.1 ExceptionRequest Attribute Definition Table
Table 45 ExceptionRequest Attribute Definition
Attribute Name Definition Form
sourceId The source of the exception. Text, formatted according to the convention used to identify an
exception source. See limitations, Section 3.1.1.
exceptionId The identifier of the exception. Text, formatted according to the convention used to uniquely
identify an exception. See limitations, Section 3.1.1.
severity The severity of the exception. Text, formatted according to the convention used to identify the
severity of an exception. Acceptable values, if any, are
supplier-defined.
11.1.4.2 sourceId — If this is the only non-empty attribute, then all exceptions from this source will be reported,
regardless of id or severity.
11.1.4.3 exceptionId — If this is the only non-empty attribute, then all exceptions with this id will be reported,
regardless of source or severity.
11.1.4.4 severity — If this is the only non-empty attribute, then all exceptions with this severity will be reported,
regardless of the source or id of the exception. Note that equipment suppliers are not required to define severity
classifications for exceptions. If severity classifications are not supported by the equipment supplier, any
ExceptionRequest containing a non-empty severity attribute shall be rejected as invalid (see Section 9.1.2.2.8). If
the equipment supplier does define severity classifications for exceptions, the ability to request exceptions based on
severity in a DCP shall be supported.
SEMI E134-0305 © SEMI 2004, 2005 32
11.1.4.5 If more than one of the above attributes is non-empty, then whether or not an exception will be reported
will be determined by applying Boolean AND logic to the non-empty attributes. At least one attribute must be non-
empty.
11.1.4.6 It is not possible to customize the parameters to be sent when exceptions occur. Equipment suppliers
define what parameters, if any, are sent with exceptions.
11.1.4.7 ExceptionRequests may refer to exceptions whose state the equipment tracks (for example, the “alarm set”
and “alarm clear” states for E30 alarms). If an ExceptionRequest in a DCP refers to such an exception, the
equipment shall send an ExceptionReport (see Section 14.1.4) each time there is a change in the exception’s state.
Different data may be reported for each different exception state. If an Exception does not have any associated state,
it is not necessary to report any description of the state of the exception (see Section 14.1.4.1.2).
11.1.5 TraceRequest — This class identifies a set of parameters whose values are to be periodically collected and
reported to the consumer using the format defined in Section 14.1 . The class is used to describe at what rate the set
of requested parameters should be collected, if/how collected trace data should be buffered on the tool and when the
results should be sent to the consumer, and when the trace should start and stop.
11.1.5.1 TraceRequest Attribute Definition Table
Table 46 TraceRequest Attribute Definition
Attribute Name Definition Form
id Unique identifier for this trace request. Integer, unique across all trace requests belonging to this
DCP.
intervalInSeconds The period of time in seconds between
each collection.
Real number. Numbers less than 1.0 specify sub-second
intervals. See Section 9.1.2.2.12 for possible errors.
collectionCount The total number of collection results that
should be obtained before terminating the
trace.
Positive integer 0. See Section 11.1.5.2 for further
explanation.
groupSize The preferred number of collection results
to obtain before sending to the consumer.
Integer 0. See Section 11.1.5.3 for further explanation.
isCyclical Whether or not the trace should re-trigger
after its stop trigger has occurred.
Boolean. True indicates that the trace is cyclical. See
Section 11.1.5.4 for further explanation.
11.1.5.2 collectionCount
11.1.5.2.1 A value of 0 for this attribute indicates that the trace shall continue indefinitely, until a stop trigger is
detected, or until the DCP is deactivated. If > 0, the trace shall continue until a stop trigger (see Section 11.1.5.7) is
detected or until the total number of collection results obtained is equal to collectionCount, whichever occurs first.
For example, the consumer may wish to provide both a stop trigger and a non-zero collectionCount in order to limit
the total number of collection results to report regardless of whether or not the stop trigger occurs, or in case an error
condition on the equipment prevents the stop trigger from firing.
11.1.5.3 groupSize
11.1.5.3.1 Depending on the buffering capacity of the equipment, the DCP may send a TraceReport before
‘groupSize’ results have been obtained. A TraceReport must not include more than ‘groupSize’ collection results
(excluding groupSize = 0). See Section 12.3.13 for a description of the effect of this setting on DCP behavior.
11.1.5.4 isCyclical
11.1.5.4.1 At least one start and one stop trigger must be supplied for a trace request to be cyclical. If this attribute
has the value ‘true’, the trace shall be restarted if any one of the start triggers is detected after termination. If this
attribute has the value ‘false’, the trace will not restart unless the DCP is deactivated and then re-activated. See
Section 9.1.2.2.13 for possible errors.