semi合集-English.pdf - 第1832页

SEMI E42-0704 © SEMI 1995, 2004 101 Table 14.13 RMEComplete Ser vice Parameter Req/Ind Rsp/Conf Description REOpID C - Operation ID, us ed where multipl e completion messages m ay occur, corresponding to the value in the…

100%1 / 7923
SEMI E42-0704 © SEMI 1995, 2004 100
Table 14.9 RMESelect Service
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RESelect M - Recipe specifiers with (optionally) one or more associated parameter
names/values per recipe.
REOpID C C(=) Operation ID, used where multiple confirmations may occur. May be
null or omitted where the service initiator does not request a new
service, until all confirmations for the outstanding service have been
received.
LinkID - M LinkID is set to zero if, and only if, no further completion messages
will be required.
REStatus - M Indicates the results of the operation.
14.10 RMEDeselect — The service user may deselect a recipe to prevent its re-execution.
Parameters for RMEDeselect are listed in Table 14.10.
Table 14.10 RMEDeselect Service
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RERcpID M - Identifier of the recipe.
REStatus - M Information concerning the results of the operation.
14.11 RMEGetDescriptor — The service user may request the descriptors of one or more recipes.
Parameters for RMEGetDescriptor are listed in Table 14.11.
Table 14.11 RMEGetDescriptor
Parameter Req/Ind Rsp/Conf Description
RESpec M - Specifier of the recipe executor.
(List of) RERcpID M - Identifier of the recipe.
(List of) REDesc - M Requested recipe descriptor(s) in the same order as requested.
REStatus - M Information concerning the results of the operation.
14.12 RMEChange — The service provider informs an originating namespace that a permitted change has
occurred.
Parameters for RMEChange are listed in Table 14.12.
Table 14.12 RMEChange Service
Parameter Req/Ind Rsp/Conf Description
REOpID C - Operation ID, used where multiple completion messages may occur,
corresponding to the value in the original request. May be null or
omitted where the service initiator does not request a new service
using REOpID, until the confirmation for the outstanding service has
been received.
RERcpID M - Identifier of the recipe of interest. Equivalent to specifier of
corresponding managed recipe.
REChangeStatus M - State of the changed recipe.
(List of) AttrSettings C - Attributes of particular interest to the result. Varies with action.
REStatus M - Information concerning the results of the operation.
14.13 RMEComplete — The service provider notifies the service user that an action requested by the service user
has completed.
Parameters for RMEComplete are listed in Table 14.13.
SEMI E42-0704 © SEMI 1995, 2004 101
Table 14.13 RMEComplete Service
Parameter Req/Ind Rsp/Conf Description
REOpID C - Operation ID, used where multiple completion messages may occur,
corresponding to the value in the original request. May be null or
omitted where the service initiator does not request a new service
using REOpID, until the confirmation for the outstanding service has
been received.
RERcpID M - Identifier of the recipe of interest. Equivalent to specifier of
corresponding managed recipe.
REChangeStatus M - State of the changed recipe.
(List of) AttrSettings C - Attributes of particular interest to the result. Varies with action.
REStatus M - Information concerning the results of the operation.
15 Recipe Management Compliance
This section gives a centralized reference location for compliance for RMS objects. It provides references to other
sections of the standard where detailed requirements are located. This section also defines standard terminology and
documentation related to RMS compliance that can be used by agent suppliers and device manufacturers to describe
compliance with this standard.
Each object defined by RMS has both fundamental requirements and additional capabilities. Fundamental
requirements shall be met by all instances of an RMS-compliant object as specified in cited sections. Additional
capabilities consist of those features that are optional. However, for RMS compliance, where features providing the
same or similar capabilities are implemented, they shall be implemented according to RMS specifications.
Except where one or more subsections are specifically excluded, section references include all subsections of the
referenced section.
The following table format is used in this section to specify fundamental and additional (optional) capabilities.
Fundamental capabilities have a "Y" in the column labeled "Fund." Otherwise, the capability is optional.
Capability Reference Fundamental
Name of capability Sections in SEMI E42 Y or N
15.1 Areas of Compliance — There are seven areas of RMS compliance, as follows:
a. Managed Recipe
b. Recipe Namespace Management
c. Distributed Recipe Namespace Management
e. Distributed Recipe Namespace Recorder
d. Distributed Recipe Namespace Segment
f. Execution Recipe
g. Recipe Executor
15.2 Managed Recipe — This section defines RMS compliance for the managed recipe.
A managed recipe has attributes, a body, and is capable of supporting at least one agent-specific dataset. An RMS-
compliant managed recipe reflects its compliance (a) through its attributes and (b) through its structure when it is
transferred.
In some cases, a capability is represented by a single attribute. In other case, support of an additional capability
requires several attributes that are required as a set.
SEMI E42-0704 © SEMI 1995, 2004 102
Table 15.1 describes the requirements for compliance to the managed recipe.
Table 15.1 Section References for Managed Recipe Capabilities
Capability Reference Fundamental
Recipe identifier (class, name, version) 3.2.3 Y
/PROCESS/ recipe class 3.2.3.2 Y
Mandatory and required generic attributes 3.2.5, 3.4.1, 3.4.2 Y
Mandatory and required agent-specific dataset attributes 3.4.2.2 Y
Recipe State Model 8.3, Table 8.1 Y
/PROCESS/ recipe subclass(es) 3.2.3.2 N
Non-process recipe class(es) 3.2.3.2 N
Multi-part recipe (ExtRef, LinkList) 3.2.3.1, 3.4.2.1 N
Variable parameters (Parameters, LinkParam) 3.2.4.2, 3.4.2.1 N
Approval level (ApprovalLevel) 3.4.2.1, 3.4.2.1 N
Certification Certified 3.4.2.1 N
Source Form recipe body 3.2.2.1.1 N
*
Object Form recipe body 3.2.2.1.2 N
*
* At least one of the two forms is required.
15.3 Managed Recipe Compliance Table — Table 15.2 provides a statement of compliance for the managed recipe.
Table 15.2 Recipe Namespace Management Compliance Table
Manual Recipe Compliance Table
Fundamental RMS Requirements Implemented RMS Compliant
Recipe identifier (class, name, version) ❒ Yes ❒ No
/PROCESS/ recipe class ❒ Yes ❒ No
Mandatory and required generic attributes ❒ Yes ❒ No
Mandatory and required agent-specific dataset
attributes
❒ Yes ❒ No
Recipe State Model ❒ Yes ❒ No
❒ Yes
1
❒ No
Additional Capabilities Implemented RMS Compliant
2
/PROCESS/ recipe subclass(es) ❒ Yes ❒ No ❒ Yes ❒ No
Non-process recipe class(es) ❒ Yes ❒ No ❒ Yes ❒ No
Multi-part recipe (ExtRef, LinkList) ❒ Yes ❒ No ❒ Yes ❒ No
Variable parameters (Parameters, LinkParam) ❒ Yes ❒ No ❒ Yes ❒ No
Approval level (ApprovalLevel) ❒ Yes ❒ No ❒ Yes ❒ No
Agent-specific dataset mandatory and required
attributes
❒ Yes ❒ No ❒ Yes ❒ No
Certification Certified ❒ Yes ❒ No ❒ Yes ❒ No
Source Form recipe body ❒ Yes ❒ No ❒ Yes ❒ No
Object Form recipe body ❒ Yes ❒ No ❒ Yes ❒ No
1
Do not mark YES unless all fundamental RMS requirements are implemented.
2
Additional capabilities may not be marked RMS compliant unless all fundamental RMS requirements are implemented.
15.4 Recipe Namespace Management — Recipe Namespace Management requires compliance to specifications for
the managed recipe, the recipe namespace, and the recipe namespace manager.
15.4.1 Recipe Namespace — This section defines RMS compliance for the recipe namespace object. A recipe
namespace exhibits RMS compliance through its attributes and access to managed recipes.