semi合集-English.pdf - 第2447页

SEMI E87-0705 © SEMI 1999, 2005 16 about the carrier. When the carrierID is provided by the Bi nd or the Carrier Notification service, the carrier object shall be instantiated in the ID NOT READ su bstate. When the carri…

100%1 / 7923
SEMI E87-0705 © SEMI 1999, 2005 15
10.7.2 Carrier State Model Diagram
CARRIER
1
21
CARRIER SLOT MAP STATUS
SLOT MAP NOT
READ
WAITING FOR
HOST
SLOT MAP
VERIFICATION
OK
SLOT MAP
VERIFICATION
FAIL
12
13
14
15 16
C
CARRIER ID STATUS
ID NOT READ
WAITING FOR
HOST
ID
V
ERIFICATION
OK
ID
V
ERIFICATION
FAILED
3
4
5
6
7
9
2
8
C
11
10
NOT
ACCESSED
IN
A
CCESS
CARRIER
COMPLETE
18
19
17
CARRIER
STOPPED
20
CARRIER ACCESSING STATUS
Figure 3
Carrier State Model Diagram
10.7.3 Carrier State Definitions
10.7.3.1 CARRIER — The CARRIER state has three ANDed (orthogonal) states: CARRIER ID STATUS,
CARRIER SLOT MAP STATUS and CARRIER ACCESSING STATUS.
10.7.3.2 CARRIER ACCESSING STATUS — This is a substate of CARRIER and indicates the current accessing
status of the carrier. It has four substates, NOT ACCESSED, IN ACCESS, CARRIER COMPLETE, and CARRIER
STOPPED. The initial default entry substate is NOT ACCESSED.
10.7.3.2.1 NOT ACCESSED — This is a substate of CARRIER ACCESSING STATUS and is active when access
by the equipment to the carrier has not been started. The carrier can be moved out.
10.7.3.2.2 IN ACCESS — This is a substate of CARRIER ACCESSING STATUS and is active when access by the
equipment to the carrier has been started but has not been finished, and the carrier should not be moved out.
10.7.3.2.3 CARRIER COMPLETE — This is a substate of CARRIER ACCESSING STATUS and is active when
the access by the equipment to the carrier has been finished, and the carrier should be moved out. This is a final
state.
10.7.3.2.4 CARRIER STOPPED — This is a substate of CARRIER ACCESSING STATUS and is active when the
access by the equipment to the carrier has been stopped abnormally, and the carrier should be moved out. This is a
final state.
10.7.3.3 CARRIER ID STATUS — This is a substate of CARRIER and indicates the current status of the carrier
with respect to its identifier. It has four substates, ID NOT READ, WAITING FOR HOST, ID VERIFICATION
FAILED, ID VERIFICATION OK. The initial substate is conditional based on information the equipment has
SEMI E87-0705 © SEMI 1999, 2005 16
about the carrier. When the carrierID is provided by the Bind or the Carrier Notification service, the carrier object
shall be instantiated in the ID NOT READ substate. When the carrierID is provided by the carrier ID reader, the
carrier shall be instantiated in the WAITING FOR HOST substate. When the Carrier is instantiated by the
ProceedWithCarrier service, the carrier shall be instantiated in the ID VERIFICATION OK substate. Finally when
the carrier is instantiated by the CancelCarrier service, the carrier will be instantiated in the ID VERIFICATION
FAILED substate.
10.7.3.3.1 ID NOT READ — This is a substate of CARRIER ID STATUS. This state is active whenever the
CarrierID has not been read by the equipment.
10.7.3.3.2 ID VERIFICATION FAILED — This is a substate of CARRIER ID STATUS and is active when the
carrierID has failed verification by the host following the CancelCarrier service. This is a final state.
10.7.3.3.3 ID VERIFICATION OK — This is a substate of CARRIER ID STATUS and is active as soon as the
CarrierID has been accepted. The ID is determined to be accepted by either successful verification by the equipment
or the host, or by bypassing ID read because a carrier ID reader is not available and the BypassReadID variable is
set to true. This is a final state.
10.7.3.3.4 WAITING FOR HOST — This is a substate of CARRIER ID STATUS and is active during the period of
time when the carrierID has been read by the equipment successfully or unsuccessfully and has not yet been verified
by the host.
10.7.3.4 CARRIER SLOT MAP STATUS — This is a substate of CARRIER and indicates the current status of the
carrier with respect to its slot map. It has four substates, SLOT MAP NOT READ, WAITING FOR HOST, SLOT
MAP VERIFICATION FAILED, SLOT MAP VERIFICATION OK. The initial default entry sub-state is SLOT
MAP NOT READ.
10.7.3.4.1 SLOT MAP NOT READ — This is a substate of CARRIER SLOT MAP STATUS and is the default
entry state. It is active when the Carrier is first loaded at the equipment until the Slot Map has been read successfully
by the equipment at the Substrate Port.
10.7.3.4.2 SLOT MAP VERIFICATION FAIL — This is a substate of CARRIER SLOT MAP STATUS and is
active when the Slot Map has been read by the equipment and has failed verification by the host. This is a final
state.
10.7.3.4.3 SLOT MAP VERIFICATION OK — This is a substate of CARRIER SLOT MAP STATUS and is active
as soon as the slot map has been verified. This is a final state.
10.7.3.4.4 WAITING FOR HOST — This is a substate of CARRIER SLOT MAP STATUS and is active when the
equipment is waiting for input from the host.
10.7.4 Carrier State Transition Table
10.7.4.1 Table 7 indicates the triggers and the expected behavior of the instantiated carrier object.
Table 7 Carrier State Transition Definition
# Previous State Trigger New State Actions Comment
1 (no state) A carrier is instantiated. CARRIER None. No event is required for this
transition
2 (no state) Normal: A Bind or Carrier
Notification service is received.
ID NOT READ None. Data required to be available for
this event report:
CarrierID
CarrierIDStatus
SEMI E87-0705 © SEMI 1999, 2005 17
# Previous State Trigger New State Actions Comment
3 (no state) Normal: A carrierID not
currently existing at the
equipment is successfully read.
Abnormal: A carrierID is read
successfully but an equipment
based verification failed.
WAITING FOR
HOST
None. Data required to be available for
this event report:
CarrierID
PortID
CarrierIDStatus
Normally, this transition will
happen after a successful ID read
if a bind service has not been
issued (host based verification) or
abnormally if a bind service is
followed by a successful ID read
and an unsuccessful equipment
based verification.
4 (no state) ID Read fail or
UnknownCarrierID Events:
ProceedWithCarrier service is
received.
ID
VERIFICATION
OK
A carrier is
instantiated
having the
carrierID
provided by the
Proceed
WithCarrier
service.
Data required to be available for
this event report:
CarrierID
CarrierIDStatus
This transition can happen only if
a bind service has not been
received.
5 (no state) ID Read fail or
UnknownCarrierID Events: A
CancelCarrier service is
received.
ID
VERIFICATION
FAIL
A carrier is
instantiated
having the
carrierID
provided by the
Cancel Carrier
service.
Data required to be available for
this event report:
CarrierID
CarrierIDStatus
This transition can happen only if
a bind service has not been
received.
6 ID NOT
READ
Carrier ID is read successfully
and the equipment has verified
the carrierID successfully.
ID
VERIFICATION
OK
None. Data required to be available for
this event report:
PortID
CarrierID
CarrierIDStatus
7 ID NOT
READ
Carrier ID is read
unsuccessfully.
WAITING FOR
HOST
None. Data required to be available for
this event report:
PortID
CarrierID
CarrierIDStatus
8 WAITING
FOR HOST
A ProceedWithCarrier service
is received.
ID
VERIFICATION
OK
None. Data required to be available for
this event report:
PortID
CarrierID
CarrierIDStatus
9 WAITING
FOR HOST
A Cancel Carrier Service is
received.
ID
VERIFICATION
FAIL
None. Data required to be available for
this event report:
PortID
CarrierID
CarrierIDStatus
10 ID NOT
READ
BypassReadID variable is set to
FALSE, and a carrier is
received when the id reader is
not in service or not installed.
WAITING FOR
HOST
Wait for
ProceedWith-
Carrier.
Data required to be available for
this event report:
PortID
CarrierID
CarrierIDStatus