semi合集-English.pdf - 第1727页

SEMI E41-95 © SEM I 1995 10 10.2 Par ameter Dictionar y Table 4 Parameter Dict ionary Parameter Name Definition Form: Possible Values ErrorCo de Contains the code f or the spec ific err o r f ound. Enum erated: EXReco ve…

SEMI E41-95 © SEMI 19959

EXType Identifies the type of exception condition. Y RO Enumerated:

AlarmError

EXMessage Text message describing the abnormal

situation monitored.

YROText

EXEnabled Indicates that reporting to the decision

authority on the exception condition is

enabled.

Y RW Boolean:

TRUE – Enabled

FALSE - Disabled

EXRecActList List of possible recovery actions. N RO List of:

Text

EXStateList All concurrent sub-states of the exception

condition according to the state model in

Figure 3.

Y RO List of:

Text

EXRecoveryAction Recovery action which may be requested to

resolve the abnormal situation.

NROText

EXState A unique sub-state of the exception

condition according to the state model in

Figure 3.

YROText:

EXSTATE/CLEARED

EXSTATE/SET/NOTPOSTED

EXSTATE/SET/POSTED

EXSTATE/NOTRECOVERING

EXSTATE/RECOVERING

EXSTATE/ABORTINGRECOVERY

10 Messaging Services Detai l

This section defines the messaging services required to implement the exception management concepts. The

messages were introduced in Section 8.1. These services are independent of the messaging protocol used. They may

be mapped to SECS-II (SEMI-E5) or to other comparable protocols.

These messaging services define the messages to be used, the nature of the parameters contained within the

messages, and data type of the parameters. Not defined here is the internal structure of the actual messages as

transferred, including order of the parameters and how various data structures and data types are represented.

The service message notation used in the tables below is described in Conventions, Section 5.3.

10.1 Service List — The messages shown in Table 3 are exchanged between service-provider and service-user for

the purpose of accomplishing exception management tasks.

Table 3 Service List

Message Name Type Description

EXPost N Notification by the exception agent that the abnormal situation related to the exception

condition has been detected or significant information has changed while the situation exists.

EXCleared N Notification by the exception agent that the abnormal situation related to the exception

condition is no longer apparent or relevant.

EXRecover R Decision authority request that a particular recovery action be performed.

EXRecoveryComplete N Notification by the exception agent that a recovery action has completed.

EXRecoveryAbort R Decision authority request that a recovery action be terminated immediately.

SEMI E41-95 © SEMI 1995 10

10.2 Parameter Dictionary

Table 4 Parameter Dictionary

Parameter Name Definition Form: Possible Values

ErrorCode Contains the code for the specific error found. Enumerated:

EXRecover:

Parameters improperly specified

Insufficient parameters specified

Recovery action currently invalid

Busy with another recovery

Currently unable to perform the recovery

EXRecoveryAbort:

Parameters improperly specified

Insufficient parameters specified

No active recovery action

EXRecoveryComplete:

FailedRecovery aborted

ErrorText Text in support of the error code. Text

EXAck Indicates whether the request was successful or the activity

completed normally.

Boolean:

TRUE – Successful

FALSE – Unsuccessful

EXID Persistent exception condition identifier. Text:

Unique with respect to the exception agent.

EXMessage Message describing the situation related to an exception

condition.

Text

EXRecovery Identifies a recovery action associated with an exception

condition.

Text

EXRecoveryStatus Reports the acceptance or rejection of a requested recovery

action and whether completion was normal.

Structure composed of:

EXAck

(List of) Status

EXType Identifies the type of exception condition. Enumerated:

Alarm

Error

Status Reports any errors found. Structure composed of:

ErrorCode

ErrorText

Timestamp Event date and time. Text

yyyymmddhhmmsscc

10.3 Service Detail — Tables 5 through 9 define the parameters for each service. Parameters have additional detail

which is defined in the parameter dictionary, Table 4.

10.3.1 EXPost — Detection of abnormal situations by the exception agent is communicated using the EXPost

service, as described in Section 8.1. This notification is also used to communicate any significant changes in

exception condition information while its state is SET.

Table 5 EXPost Service Detail

Parameter Req/Ind Comment

Timestamp M

EXID M Identifies the exception condition which has detected the abnormal situation.

EXType M

EXMessage M

(List of) EXRecovery C List of possible recovery actions. Not available for alarms.

10.3.2 EXCleared — Notification that an abnormal situation is no longer apparent or relevant, as is described in

Section 8.1, is communicated using the EXCleared service.

Table 6 EXCleared Service Detail

Parameter Req/Ind Comment

Timestamp M

EXID M Identifies the exception condition which has detected the abnormal situation.

EXType M

EXMessage M

10.3.3 EXRecover — Recovery action requests, described in Section 8.1, are communicated using the EXRecover

service. The recovery action services are not available for alarms.

Table 7 EXRecover Service Detail

Parameter Req/Ind Rsp/Cnf Comment

EXID M - Identifies the exception condition on which to perform the recovery action.

EXRecovery M - The particular recovery action being requested.

EXRecoveryStatus - M

10.3.4 EXRecoveryComplete — Notification of recovery action completion by the exception agent is

communicated using the EXRecoveryComplete service. Recovery action completion, which is described in Section

8.1, is not directly linked to clearing the exception condition state, and successful completion indicates only that the

operation performed completed normally.

Table 8 EXRecoveryComplete Service Detail

Parameter Req/Ind Comment

Timestamp M

EXID M Identifies the exception condition on which the recovery action was performed.

EXRecoveryStatus M

10.3.5 EXRecoveryAbort — Recovery action abort, described in Section 8.1 is communicated using the

EXRecoveryAbort service.

Table 9 EXRecoveryAbort Service Detail

Parameter Req/Ind Rsp/Cnf Comment

EXID M - Identifies the exception condition on which the recovery action is being performed.

EXRecoveryStatus - M

10.4 Fundamental Requirements — Exception management defines the standard services available to achieve

exception condition-based exception handling and error recovery in equipment.

All exception agent implementations shall support the fundamental requirements. This standard provides for two

aspects of fundamental requirements: exception reporting and interactive exception handling. It is possible to

support only exception reporting in systems which do not require interactive exception handling. Interactive

exception handling requires that exception reporting be supported.

10.4.1 Exception Reporting — The fundamental requirements of the exception agent for exception reporting are

based on maintaining the decision authority updated on the exception conditions it is interested in. These are listed

below.

• Detect and report the occurrence of significant abnormal situations by setting the related exception condition,

and posting it if reporting is enabled.