semi合集-English.pdf - 第3371页

SEMI E132-0305 © SEMI 2004, 2005 24 # Current State Trigger Ne w State Actions Comments 2 AUTHENTICATING Client or equipment failed to authent icate, an error occurred during the process, or the client has no correspondi…

100%1 / 7923
SEMI E132-0305 © SEMI 2004, 2005 23
14.3.2 Session States
14.3.2.1 ACTIVE — Parent state, covers entire lifecycle of an authenticated session. Session is active beginning
with a successful request to establish a new session, and is active until the session is closed.
14.3.2.2 AUTHENTICATING — This state is where the client and the equipment carry out the authentication
process and establish new authenticated sessions. Privileges are granted to the session once the client is
authenticated and the session successfully established. See Section 10 for the authentication message flow, and
Section 13.2.6 for session establishment.
14.3.2.3 ESTABLISHED — This state is the parent of all those sub-states that relate to service invocation and
communications subsequent to successful authentication and session establishment. It has two simultaneous sub-
states, COMMUNICATING and MONITORING, both of which are active whenever the session is
ESTABLISHED.
14.3.2.4 COMMUNICATING (ESTABLISHED Sub-State) — This is the ESTABLISHED sub-state where all session
communications are handled.
14.3.2.5 MONITORING (ESTABLISHED Sub-State) — This state provides a watchdog mechanism to monitor status
of the established session.
14.3.2.6 READY (COMMUNICATING Sub-State) — Initial state upon session established and COMMUNICATING
state becomes active. Both the client and the equipment have been successfully authenticated without errors. The
equipment is awaiting service requests in this state and can report relevant events to authenticated clients. Except
for the services defined in this specification, the services allowed or events reported are dependent on the
specifications that defined them.
14.3.2.7 SESSION MONITOR (MONITORING Sub-State) — Initial state upon entry to ESTABLISHED state and
when MONITORING becomes active. The equipment shall periodically check the active status of the session by
sending ping messages to the client. See Section 15.1.1for details of the SessionPing message. A ping message is
sent upon first entry to the state. When resuming persistent sessions during equipment startup, the ping message
tells client of each persistent session that the equipment is now online. The interval at which the next ping message
is sent, and the number of attempts to be made before closing a session shall be configurable, and must include a
way to disable periodic pings (such as by using a delay interval of zero). If the client does not respond after the
configured number of pings, the equipment shall terminate the session automatically. The default number of ping
attempts shall be set to 3.
14.3.2.8 CLOSING — Session is being terminated either at request of client, security admin, or equipment initiated
due to errors. Session context are cleared including established session identifier. A SessionClosed (section 15.1.3)
notification is sent to client (if possible) on transition to this state.
14.3.2.9 FROZEN — A persistent session is put on hold as the equipment is powered down or in a state where it is
not able to communicate. A SessionFrozen (section 15.1.2) notificatication is sent to client (if possible) on
transition to this state. When resuming a persistent session, behavior is governed by re-entry to the ESTABLISHED
state and its sub-states.
14.3.3 Session State Transitions
Table 34 Session State Transitions Table
# Current State Trigger New State Actions Comments
1 (no state) Client request to start
an authenticated
session
AUTHENTICATING Equipment and client
begins authentication and
session establishment
message flow (see Sections
10 and 14.3.2.2).
SEMI E132-0305 © SEMI 2004, 2005 24
# Current State Trigger New State Actions Comments
2 AUTHENTICATING Client or equipment
failed to authenticate,
an error occurred
during the process, or
the client has no
corresponding
ACLEntry.
(no state) Error reported and
connection is terminated.
3 AUTHENTICATING Request to establish
new session received
but max session limit
would be exceeded, or
request is for a new
admin session and
there is already an
active admin session.
(no state) Error reported and
connection is terminated.
4 AUTHENTICATING Client and equipment
successfully
authenticated with no
errors and the request
to establish new
session was successful.
ESTABLISHED Equipment enters the
COMMUNICATING and
MONITORING sub-states
for the session. Active
session count is
incremented if non-admin
session.
5 ESTABLISHED Entry to
COMMUNICATING,
client authenticated and
a session is established
or resumed.
READY Equipment is waiting for
service requests for this
session.
COMMUNICATING
and MONITORING
are concurrent sub-
states of
ESTABLISHED.
6 READY Equipment receives a
client request for
service.
READY Equipment verifies session
id and permission for the
client to execute requested
service based on granted
privileges.
7 ESTABLISHED Entry to
MONITORING, client
authenticated and a
session is established
or resumed.
SESSION MONITOR Equipment sends a ping
message to client to
indicate session is
established. When
resuming persistent
sessions during startup,
indicates equipment is
now online.
Concurrent with
COMMUNICATING
state.
8 SESSION MONITOR Ping delay timer
reached
SESSION MONITOR Equipment sends ping
message to client. If ping
is not replied within
configurable timeout, or
after the configured
number of retries, the
session will be closed by
equipment.
See Section 14.3.2.7.
9 ESTABLISHED Client or
SecurityAdmin request
to terminate session,
equipment is shutting
down, or
communication errors
have been detected by
the equipment.
CLOSING Equipment properly closes
session and clears any
state information.
SessionClosed notification
is sent to client (if
possible).
See Sections 14.3.2.3
and 13.1.4 for
discussion of
equipment response to
communication errors.
SEMI E132-0305 © SEMI 2004, 2005 25
# Current State Trigger New State Actions Comments
10 ESTABLISHED Equipment is shutting
down or is in
emergency down, and
session is persistent
FROZEN SessionFrozen notification
is sent to client (if
possible).
Applies to sessions that
are persistent only, see
PersistSession
(Section 13.2.3).
11 FROZEN Equipment has
completed startup or
has otherwise entered a
state where it is able to
resume authenticated
session
communications.
ESTABLISHED Session context including
client endpoint, client id,
session id etc is restored
from non-volatile memory.
MONITORING and
COMMUNICATING sub-
states will be entered, see
transition 7 for
notifications to client on
online status.
In attempting to
resume a frozen
session, the client may
not actually be
reachable by the
equipment. In such
cases, the session will
eventually be closed
according to the
SessionPing messages
sent from the
SessionMonitor sub-
state (see transitions 8
and 9).
12 CLOSING Session terminated (no state) Session is deleted and
active session count
decremented if non-admin
session.
15 Client Interface
15.1 This section specifies the interface that the equipment shall use to communicate security related information
and requests/events to authenticated clients with established sessions.
Figure 17
Session Client Interface
Table 35 Session Client Operations
Operation Description Type Requestor/
Sender
Responder/
Receiver
SessionPing Used by equipment to check if client is still active. RR Equipment Client
SessionFrozen Notification to client that current session will be frozen. FF Equipment Client
SessionClosed Used by equipment to close an active session. RR Equipment Client
15.1.1 SessionPing — Upon receiving this request, the client shall reply with its id. The client id returned must be
the same one used by the client during the authentication phase. See the Session Monitoring state defined in Section
14.3.2.7, regarding behavior of established authenticated sessions in the event of ping timeouts.
Table 36 SessionPing Parameter Definitions
Parameter Description Kind Form
clientId Id of the client responding to the ping message. OUT Text, equal to the client Id
used in authentication phase.
«interface»
SessionClient
SessionFrozen()
SessionPing()
SessionClosed()