semi合集-English.pdf - 第3482页

SEMI E134-0305 © SEMI 2004, 2005 35 12 Data Collection Plan State Models 12.1 DataCollectionPlan State Model Da ta Co l le c tio n Pl a n Acti ve In acti ve 2 8 4 7 H 1 H De let ed 17 6 10 12 13 Hi ber na ti ng 14 15 16 …

100%1 / 7923
SEMI E134-0305 © SEMI 2004, 2005 34
11.1.8 ExceptionTrigger — Identifies an exception that can be generated by a specific source, and whose
occurrence can trigger the starting or stopping of a trace. For stateful exceptions, the trigger can be activated by a
transition to any of the defined states for that exception. See Section 9.1.2.2.11 for possible errors.
11.1.8.1 ExceptionTrigger Attribute Definition Table
Table 49 ExceptionTrigger 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 for the exception. Text, formatted according to the convention used to identify a specific
exception. See limitations, Section 3.1.1.
exceptionState For stateful exceptions, the
exception state which activates
the trigger.
Text, equal to a valid state for the exception. For exceptions
corresponding to E30 alarms, valid values are:
“urn:semi-org:E30:alarmSet”
“urn:semi-org:E30:alarmClear”
If no state is provided, the trigger shall activate when the equipment
detects an occurrence of the exception.
11.1.9 ParameterRequest — This class provides the source and name of a specific parameter that the equipment is
to report to the consumer as part of the DCP’s event or trace reports. Multiple trace reports or event reports across
multiple DCPs may refer to the same parameter.
11.1.9.1 ParameterRequest Attribute Definition Table
Table 50 ParameterRequest Attribute Definition
Attribute Name Definition Form
sourceId Unique identifier for the source
of the parameter.
Text, must be a valid parameter source, formatted according to the
convention used for identifying a source. See limitations, Section 3.1.1 .
parameterName Name of the parameter. Text, must be a valid parameter name for the specified source, formatted
according to the convention used for identifying a parameter. See
limitations, Section 3.1.1 .
SEMI E134-0305 © SEMI 2004, 2005 35
12 Data Collection Plan State Models
12.1 DataCollectionPlan State Model
DataCollectionPlan
ActiveInactive
2
8
4
7
H 1
H Deleted
17
6
10
12
13
Hibernating
1415
16
11
3
5
9
Figure 20
DataCollectionPlan State Model
12.1.1 The purpose of the DataCollectionPlan state model is to define the consumer’s view of the behavior of a
DCP, which includes the consumer’s interactions with the equipment necessary to define, activate, de-activate, and
delete DCPs. Each DCP on the equipment shall execute independently, as described in these state models. The
equipment supplier is not required to provide a direct, literal implementation of these state models. They are
documented here to provide a precise definition of the required behavior for DCPs on the equipment. The
transitions described in these state machines are not to be made available for event data collection.
12.1.1.1 Implementation mappings of this specification may identify additional conditions other than those defined
in this document under which DCP activity should be terminated (that is, cause a transition from the “Active” to the
“Inactive” state). All such conditions, and the details of required equipment behavior under those conditions, shall
be fully specified in any implementation mapping for which this is a consideration.
12.1.2 DataCollectionPlan — The superstate for all DCP states. The equipment has validated the DCP and stored it
in non-volatile memory. The DCP may now be activated and de-activated.
12.1.3 Inactive — The equipment is not sending or buffering any event, exception, or trace reports requested in the
DCP to any consumer. A transition to Active is required for the data defined in this DCP to be reported to a
consumer.
12.1.4 Active — The equipment is sending and/or buffering all event, exception, and trace reports requested in the
DCP to all consumers that have successfully activated the DCP. This state contains substates that are described in
Section.12.2 .
12.1.5 Hibernating — The equipment has paused the sending and buffering of all event, exception, and trace
reports requested in the DCP, because the equipment is entering a state in which it will not be possible to
communicate data to any consumers. The DCP has its ‘isPersistent’ attribute equal to ‘true’.
12.1.6 Deleted — The DCP is no longer stored in non-volatile memory, and can no longer be legally referenced by
any consumer.
SEMI E134-0305 © SEMI 2004, 2005 36
12.1.7 DataCollectionPlan Transition Table
Table 51 DataCollectionPlan Transition Definition
Num Previous State Trigger New State Actions
1 (no state) A consumer invokes the DefinePlan
operation of the DataCollection-
Manager interface. The equipment has
validated its contents.
Inactive The equipment shall store the DCP in non-
volatile memory. The DCP can now be
activated.
2 Inactive A consumer invokes the ActivatePlan
operation of the DataCollection-
Manager interface using the identifier of
this DCP. The consumer has sufficient
privilege for this operation.
Active The equipment shall store the id of the
requesting consumer and the time of the
request. If the DCP is persistent, the
equipment shall store this information in
non-volatile memory. The equipment
shall begin sending and/or buffering all
exception, event, and trace reports
according to the DCP definition, to the
requesting consumer.
3 Inactive A consumer invokes the ActivatePlan
operation of the DataCollection-
Manager interface using the identifier of
this DCP. The equipment has
determined that the DCP is invalid.
Inactive The equipment shall not activate the DCP.
The equipment shall identify all errors in
the DCP, and return this information using
the InvalidPlan error, defined in Section
9.1.2.2.6.
4 Active A consumer invokes the ActivatePlan
operation of the DataCollection-
Manager interface using the identifier of
this DCP. The consumer has sufficient
privilege. The DCP was previously
activated by at least one other consumer.
Active If the requesting consumer had already
previously requested activation of this
DCP, the equipment shall not activate the
DCP again for that consumer (see Section
9.1.2.5.3). Otherwise, the equipment shall
store the id of the requesting consumer and
the time of the request. If the DCP is
persistent, the equipment shall store this
information in non-volatile memory. The
equipment shall begin sending data from
this DCP to the requesting consumer
beginning with the next available
DataCollectionReport (see Section
9.1.2.5).
5 Active A consumer invokes the DeactivatePlan
operation of the DataCollectionManager
interface using the identifier of this
DCP. The consumer has sufficient
privilege. More than one consumer is
currently receiving data from this DCP.
Active The equipment shall stop sending data
from this DCP to the requesting consumer.
The equipment shall delete the activation
information stored (either in volatile, or
non-volatile storage) when the requesting
consumer originally activated the DCP.
The equipment shall continue to
buffer/send data from this DCP to the
remaining consumers.
6 Active A consumer with insufficient privilege
invokes the DeactivatePlan operation of
the DataCollectionManager interface
using the identifier of this DCP.
Active The equipment shall respond to the
consumer with an error stating that the
DCP will not be deactivated because the
consumer does not have sufficient
privilege. See Section 9.1.2.7.
7 Active A consumer invokes the DeletePlan
operation of the DataCollection-
Manager interface using the identifier of
this DCP. At least one consumer is
receiving data from this DCP.
Active The equipment shall respond to the
consumer with an error stating that the
DCP will not be deleted because the DCP
is active (see Section 9.1.2.8).