semi合集-English.pdf - 第3489页

SEMI E134-0305 © SEMI 2004, 2005 42 12.3.5 Enabled — Th e DCP is performing trace data collection (se e su bstate descriptions) as requested in a specific trace request provided with the DC P. Either the occ u rrence of …

100%1 / 7923
SEMI E134-0305 © SEMI 2004, 2005 41
Num Previous State Trigger New State Actions
26 WaitingForException An exception matching
the criteria specified in
an exception request has
occurred.
WaitingForException The DCP creates an ExceptionReport
for the exception (see Section 14.1.4).
If the DCP is not buffered, a new
DataCollectionReport (see Section
14.1) is created containing the
ExceptionReport and made available
for sending. If the DCP is buffered,
the ExceptionReport is added to the
DCP buffer in the order in which the
exception was detected.
27 (no state) DCP is activated. TraceRequestMonitor-i The DCP begins monitoring any trace
requests. See Section 12.3 for further
explanation.
12.3 Trace Request State Model
Figure 22
TraceRequest State Model
12.3.1 The purpose of the trace request state model is to define a consumer’s view of DCP trace behavior while in
the Active state of the DataCollectionPlan state model. Each trace request within each active DCP 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
for DCP trace activity on the equipment. The transitions described in this state model are not to be made available
for event data collection.
12.3.2 TraceRequestMonitor-i — This is the top level state for describing the behavior of a single trace request
within a single DCP in the Active state. Each trace request within each active DCP executes this state model
independently.
12.3.3 Tracing — This is the top level state for trace activity for a single trace request.
12.3.4 Disabled — The DCP is not performing trace data collection. The DCP is waiting for the occurrence of a
start trigger defined for this trace request.
35
TraceRequestMonitor-i
H
28
Tracing
29
H
Disabled
3130
Enabled
H
WaitingForInterval33
34
H
36
H
TraceRequestBuffering
37
H
NotBufferingTraceResults
38
BufferingTraceResults
39
H
NotSendingTraceResults
41
40
SendingTraceResults
42
H
32
SEMI E134-0305 © SEMI 2004, 2005 42
12.3.5 Enabled — The DCP is performing trace data collection (see substate descriptions) as requested in a specific
trace request provided with the DCP. Either the occurrence of a start trigger defined for the trace request was
detected, or there was no defined start trigger and the DCP began tracing immediately after activation. If the DCP
entered this state due to the detection of a start trigger, it shall record the specific trigger that was detected and the
time at which it was detected for inclusion in a trace report (see Section 14.1.5).
12.3.6 Waiting forInterval — The DCP is waiting for a time period equal to the TraceRequest attribute
‘intervalInSeconds’ (see Section 11.1.5) to expire before collecting the data associated with the trace request.
12.3.7 TraceRequestBuffering — This is the top level state for trace request buffering activity. Buffered trace
requests store the results of each trace interval as a CollectedData entry within a single TraceReport (see Section
14.1.5). Each CollectedData entry appears within the TraceReport in the order the collection results were obtained.
12.3.7.1 When a stop trigger is detected, or the total number of results collected since the trace was enabled is equal
to ‘collectionCount’, or the number of results collected since the last send is equal to ‘groupSize’, or the DCP’s trace
buffering capacity has been reached, the DCP creates a single DataCollectionReport and makes it available for
sending. The DataCollectionReport contains a single TraceReport that contains two or more CollectedData entries,
in the order in which the results were obtained (see Section 14.1.5).
12.3.8 NotBufferingTraceResults — The trace request is not buffering collected results into a single TraceReport,
because ‘groupSize’ is 1. Each collected result is added to a new TraceReport and either made available for
sending with a DataCollectionReport, or added to the DCP buffer in the order the TraceReport was completed.
12.3.9 BufferingTraceResults — The trace request is buffering collected results into a single TraceReport because
‘groupSize’ is > 1. Each new result is appended to the TraceReport as CollectedData (see Section 14.1.5.2).
12.3.10 NotSendingTraceResults — The DCP is waiting for this trace request to produce a DataCollectionReport
containing a buffered TraceReport for sending.
12.3.11 SendingTraceResults — A DataCollectionReport containing a buffered TraceReport has been made
available for sending. The DCP sends the DataCollectionReport to the DCP consumer.
12.3.12 TraceRequest Transition Table
Table 53 TraceRequest Transition Definition
Num Previous State Trigger New State Actions
28 (no state) DCP is activated. Tracing The DCP begins monitoring trace
activity for this trace request
29 (no state) DCP is activated. Disabled If there are any start triggers defined
for this trace request, the DCP stays in
the Disabled state until the occurrence
of one of the start triggers before
enabling the trace. See Section 12.3.4
for further explanation.
30 Disabled DCP is activated, or is
returning from the
Hibernating to the Active
state. There are no start
triggers defined for the trace
request.
Enabled The DCP initiates trace activity for this
trace request.
31 Enabled The stop trigger for this
request is detected. The trace
request is cyclical.
Disabled The equipment shall record the specific
trigger that was detected and the time at
which it was detected for inclusion in
the corresponding trace report (see
Section 14.1.5). The DCP sends any
buffered trace results to the consumer
in a single DataCollectionReport
message, and begins waiting for the
occurrence of a requested start trigger.
SEMI E134-0305 © SEMI 2004, 2005 43
Num Previous State Trigger New State Actions
32 Disabled A start trigger was detected. Enabled The DCP initiates trace activity for this
trace request. The DCP shall record the
specific trigger that was detected and
the time at which it was detected for
inclusion in the first TraceReport
generated (see Section 14.1.5).
33 (no state) The trace request is enabled WaitingForInterval The DCP collects and records the
requested trace data and buffers or
sends a new TraceReport. See Section
12.3.13 for further explanation. The
DCP continues waiting for the next
‘intervalInSeconds’ period to expire.
34 WaitingForInterval The period specified by
‘intervalInSeconds’ for this
trace request expires.
WaitingForInterval The DCP collects and records the
requested trace data in a corresponding
TraceReport. See Section 12.3.13 for
further explanation. The DCP
continues waiting for the next
‘intervalInSeconds’ period to expire.
35 Enabled The trace request is not
cyclical (‘isCyclical’ is false),
and the stop trigger for this
request was detected, or the
total number of requested
collected results was
obtained.
(no state) The trace terminates, and cannot be re-
enabled without deactivating and re-
activating the DCP.
36 (no state) The DCP is activated. TraceRequest-
Buffering
The DCP begins performing any trace
buffering required for this trace request.
37 (no state) The DCP is activated. NotBufferingTrace-
Results
The DCP determines whether this trace
request should be buffered. If this trace
request is not buffered, the trace
request remains in this state until the
trace terminates. See Section 12.3.8 for
further explanation.
38 NotBufferingTrace-
Results
The trace request’s
‘groupSize’ is > 1.
BufferingTrace-
Results
The DCP begins buffering collected
trace results. See Section 12.3.9 for
further explanation.
39 (no state) The DCP is activated. NotSendingTrace-
Results
The DCP waits for a buffered trace
report to become available for sending.
40 NotSendingTrace-
Results
A buffered trace report is
available for sending.
SendingTrace-Results The DCP sends the corresponding
DataCollectionReport to the consumer.
41 SendingTrace-Results A buffered trace report has
been sent to the consumer.
NotSending-
TraceResults
The DCP waits for a buffered trace
report to become available for sending.
42 TraceRequest-
Buffering
The trace request is not
cyclical (‘isCyclical’ is false),
and the stop trigger for this
request was detected, or the
total number of requested
collected results was
obtained.
(no state) The DCP performs no more activities
related to this trace request.
12.3.13 Reporting Trace Results — Trace results are reported as CollectedData within a TraceReport (see Section
14.1.5). In addition to the collected data values, the DCP shall record the time at which the data collection was
initiated (the time at which the TraceRequest’s ‘intervalInSeconds’ period expired).
12.3.13.1 If the DCP is buffered (‘intervalInMinutes’ attribute is > 0), and the TraceRequest is not buffered
(groupSize is 1), the DCP shall create a new TraceReport containing a single CollectedData entry with the