semi合集-English.pdf - 第3485页

SEMI E134-0305 © SEMI 2004, 2005 38 Num Previous State Trigger New State Actions 15 Hibernating The equipmen t ha s entered a sta te in which it is possible to begin communicating data to consumers (for example, as part …

100%1 / 7923
SEMI E134-0305 © SEMI 2004, 2005 37
Num Previous State Trigger New State Actions
8 Active A consumer invokes the DeactivatePlan
operation of the DataCollection-
Manager interface using the identifier of
this DCP. The consumer has sufficient
privilege, and there are no other
consumers.receiving data from this
DCP.
Inactive 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 stops sending and
buffering the exception, event, and trace
reports requested in the DCP to the
requesting consumer, discarding any data
buffered at the time of the deactivation.
9 Active A consumer invokes the DeactivatePlan
operation of the DataCollectionManager
interface using the identifier of this
DCP. The consumer has sufficient
privilege and is requesting that the DCP
be terminated (see Section 9.1.2.7.5).
Inactive The equipment shall stop sending and
buffering all data for this DCP to all
consumers that are currently receiving its
data. The equipment shall notify each
consumer of the reason for the de-
activation using the DCPDeactivated class
defined in Section 9.1.2.7.6. The
equipment shall delete the activation
information stored (either in volatile, or
non-volatile storage) when each consumer
originally activated the DCP.
10 Active The equipment is going to enter a state
in which it will not be possible to
communicate data to any consumers
(e.g., equipment shutdown or
emergency power off). The DCP is not
persistent.
Inactive The equipment shall deactivate the DCP
and notify each consumer receiving data
from this DCP (if possible), as described
in Section 15.1.6.2. The equipment stops
sending and buffering the exception, event,
and trace reports requested in the DCP to
the consumer. The equipment shall
discard all data that has been buffered up
to this point. If possible, the equipment
shall delete the activation information
stored when each consumer originally
activated the DCP.
11 Active The equipment determines that
p
erformance conditions require that data
collection activity be terminated (see
Section 13.1.4).
Inactive The equipment terminates all active DCPs,
and notifies each consumer using the
DCPDeactivation notification defined in
Section 15.1.6.2. The equipment shall
delete the activation information stored
(either in volatile, or non-volatile storage)
when each consumer originally activated
the DCP
12 Inactive A consumer with insufficient privilege
invokes the ActivatePlan operation of
the DataCollectionManager interface
using the identifier of this DCP.
Inactive The equipment responds to the consumer
with an error stating that the DCP will not
be activated because the consumer doesn’t
have sufficient privilege (see Section
9.1.2.7).
13 Inactive A consumer with insufficient privilege
invokes the DeletePlan operation of the
DataCollectionManager interface using
the identifier of this DCP.
Inactive The equipment responds to the consumer
with an error stating that the DCP will not
be deleted because the consumer doesn’t
have sufficient privilege (see Section
9.1.2.8).
14 Active The equipment is going to enter a state
in which it will not be possible to
communicate data to any consumers (for
example, as part of an orderly shutdown
or emergency power off). The DCP is
persistent.
Hibernating The equipment shall notify the consumers
(if possible) that the DCP is going into a
Hibernating state, as described in Section
15.1.6.3. The equipment stops reporting
and buffering the exception, event, and
trace reports defined in the DCP to the
consumers. The equipment shall discard
all data that has been buffered up to this
point.
SEMI E134-0305 © SEMI 2004, 2005 38
Num Previous State Trigger New State Actions
15 Hibernating The equipment has entered a state in
which it is possible to begin
communicating data to consumers (for
example, as part of startup or power on).
Active The equipment shall resume sending
and/or buffering all exception, event, and
trace reports, according to the DCP
definition, and sending these reports to the
consumers that had previously activated
the DCP. If the DCP contains
TraceRequests, all such traces shall be re-
started in the Tracing-Disabled state (see
Section 12.3).
16 Hibernating The equipment, prior to re-activating a
DCP in the Hibernating state, has
determined that the DCP is invalid.
Inactive The equipment shall send the
DCPDeactivation notification (see Section
15.1.6.2) to all consumers that had
previously activated the DCP, and
terminate the DCP.
17 Inactive A consumer invokes the DeletePlan
operation of the DataCollection-
Manager interface using the identifier of
this DCP.
Deleted The equipment deletes the DCP from non-
volatile storage.
12.2 DataCollectionPlan-Active State Model
Figure 21
DataCollectionPlan-Active State Model Diagram
12.2.1 The purpose of the DataCollectionPlan-Active State Model is to define a consumer’s view of DCP behavior
in the Active state of the DataCollectionPlan State Model. Each DCP’s Active state on the equipment shall execute
independently, as described in this state model. The equipment supplier is not required to provide a direct, literal
implementation of this state model. It is documented here to provide a precise definition of the required behavior
Active
H
25
H
27
24
18
NotBuffering
19
Buffering
H
DCPBuffering
20
NotSending
H
21
Sending
22
MonitoringEventRequests
H
23
WaitingForEvent
MonitoringExceptionRequests
WaitingForException
26
MonitoringTraceRequests
TraceRequestMonitor-i
SEMI E134-0305 © SEMI 2004, 2005 39
for DCPs in the Active state on the equipment. The transitions described in this state model are not to be made
available for event data collection.
12.2.2 While in the Active state, if the equipment experiences internal communication or operational failures that
prevent the collection of event, exception, or trace data requested by the DCP, the equipment shall not de-activate
the DCP. If the values of any requested parameters can’t be obtained or refreshed as a result of such communication
failures, the equipment shall use the “NoValue” class (see Section 14.2.1.4) as the reported ParameterValue for all
such affected parameters. The equipment is not required to take any other actions to notify consumers of such
failures.
12.2.2.1 Consumers should be aware that such failures may temporarily prevent the equipment from reporting
requested events or exceptions altogether, and/or result in reporting “NoValue” (see Section 14.2.1.4) for requested
parameters affected by the failure. In the event that the equipment recovers from such failures and any affected
DCPs are still active, the equipment shall resume reporting all event, exception, and trace data whose reporting had
been affected by the failure.
12.2.3 DCPBuffering — This is the top level state for describing the event, exception, and trace buffering behavior
of the DCP
12.2.4 NotBuffering — The DCP is immediately sending DataCollectionReports for each requested event and
exception as they are detected. TraceReports may be individually buffered, according to the ‘groupSize’ setting of
the DCP’s TraceRequests (see Section 11.1.5), but are also sent in the DataCollectionReport format (see Section
14.1 ). This state is only active if the DataCollectionPlan attribute ‘intervalInMinutes’ attribute is set to 0.
12.2.5 Buffering — The DCP is storing all events, exceptions, and trace data in an internal buffer in the order in
which they occur. Buffered data is sent in a single DataCollectionReport (see Section 14.1) when
‘intervalInMinutes’ expires, or when the equipment’s DCP buffering capacity has been reached, whichever occurs
first. The equipment continues buffering new data for the next interval, sending a single DataCollectionReport
when ‘intervalInMinutes’ expires. Each DataCollectionReport sent at the end of each interval contains only the data
collected during that interval. The equipment continues this buffering/sending cycle as long as the DCP is active.
This state is only active if the DataCollectionPlan attribute ‘intervalInMinutes’ attribute is > 0.
12.2.6 NotSending — The DCP is waiting for a DataCollectionReport to become ready for sending to the consumer
who activated the plan.
12.2.7 Sending — The DCP is sending a DataCollectionReport to the consumer that activated this DCP (see Section
14.1).
12.2.8 MonitoringEventRequests — The DCP is actively tracking and reporting any event requests provided with
the DCP. This is the top level state for the WaitingForEvent state.
12.2.9 WaitingForEvent — The DCP is waiting for the occurrence of any of the requested events defined in the
DCP.
12.2.10 MonitoringExceptionRequests — The DCP is actively tracking and reporting any exception requests
provided with the DCP. This is the top level state for the WaitingForException state.
12.2.11 WaitingForException — The DCP is waiting for the occurrence of any of the requested exceptions
specified in the DCP.
12.2.12 MonitoringTraceRequests — The DCP is actively tracking and reporting the results from any trace requests
provided with the DCP. This is the top level state for the TraceRequestMonitor-i states.
12.2.13 TraceRequestMonitor-i — For each trace request provided with the DCP, there is an independently-
executing TraceRequestMonitor-i (i = 0 up to the number of trace requests included in the DCP) that defines the
DCP reporting behavior for trace requests. This state contains substates that are described in Section 12.3.