semi合集-English.pdf - 第1578页

SEMI E36.1-0704 © SEMI 2004 15 NOTICE: SEMI makes no warranties or represen tations as to the suitability o f the standards set forth herein for any particular application. The determination of the suitability of the sta…

100%1 / 7923
SEMI E36.1-0704 © SEMI 2004 14
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#oemPartNumber">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Component"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#partName">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Component"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#oemName">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Component"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#errorNumber">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#ErrorCode"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#mediaUrl">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Media"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#caption">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Media"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#mediaCategory">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Media"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#companyURL">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Company"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#companyName">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Company"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#businessUnit">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Publisher"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.semi.org/e36/schema#businessUnitURL">
<rdfs:domain rdf:resource="http://www.semi.org/e36/schema#Publisher"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
</rdf:RDF>
SEMI E36.1-0704 © SEMI 2004 15
NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for any
particular application. The determination of the suitability of the standard is solely the responsibility of the user.
Users are cautioned to refer to manufacturer' s instructions, product labels, product data sheets, and other relevant
literature, respecting any materials or equipment mentioned herein. These standards are subject to change without
notice.
By publication of this standard, Semiconductor Equipment and Materials International (SEMI) takes no position
respecting the validity of any patent rights or copyrights asserted in connection with any items mentioned in this
standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and
the risk of infringement of such rights are entirely their own responsibility.
Copyright by SEMI® (Semiconductor Equipment and Materials
International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o
f
the contents in whole or in part is forbidden without express written
consent of SEMI.
SEMI E37-0303 © SEM 1995, 2003 1
SEMI E37-0303
HIGH-SPEED SECS MESSAGE SERVICES (HSMS) GENERIC
SERVICES
NOTICE: The designation of SEMI E37 was updated during the 0303 publishing cycle to reflect the reapproval of
SEMI E37.2.
1 Purpose
HSMS provides a means for independent manufacturers
to produce implementations which can be connected
and interoperate without requiring specific knowledge
of one another.
HSMS is intended as an alternative to SEMI E4 (SECS-
I) for applications where higher speed communication
is needed or when a simple point-to-point topology is
insufficient. SEMI E4 (SECS-I) can still be used in
applications where these and other attributes of HSMS
are not required.
HSMS is also intended as an alternative to SEMI E13
(SECS Message Services) for applications where
TCP/IP is preferred over OSI.
It is intended that HSMS be supplemented by
subsidiary standards which further specify details of its
use or impose restrictions on its use in particular
application domains.
2 Scope
High-Speed SECS Message Services (HSMS) defines a
communication interface suitable for the exchange of
messages between computers in a semiconductor
factory.
3 Referenced Documents
3.1 SEMI Standards
SEMI E4 — SEMI Equipment Communication
Standard 1 — Message Transport (SECS-I)
SEMI E5 — SEMI Equipment Communication
Standard 2 — Message Content (SECS-II)
3.2 IETF Documents
1
IETF RFC 791 — Internet Protocol
IETF RFC 792 — Internet Control Message Protocol
IETF RFC 793 — Transmission Control Protocol
IETF RFC 1120 — Requirements for Internet Hosts -
Communication Layers
1 The IETF documents can be obtained from The Network
Information Center, Network Solutions, 14700 Park Meadow Drive,
Suite 200, Chantilly, VA 22021 USA
IETF RFC 1340 — Assigned Numbers. Note: This
RFC supersedes RFC 820.
3.3 POSIX Document
2
IEEE POSIX P1003.12 — Protocol Independent
Interfaces (PII)
4 Terminology
API — Application Program Interface. In the case of
TCP/IP, a set of programming conventions used by an
application program to prepare for or invoke TCP/IP
capabilities.
communication failure — a failure in the
communication link resulting from a transition to the
NOT CONNECTED state from the SELECTED state.
(See Section 9.)
confirmed service (HSMS) — an HSMS service
requested by sending a message from the initiator to the
responding entity which requires that completion of the
service be indicated by a response message from the
responding entity to the initiator.
connection — a logical linkage established on a TCP/IP
LAN between two entities for the purposes of
exchanging messages.
control message — an HSMS message used for the
management of HSMS sessions between two entities.
data message — an HSMS message used for
communication of application-specific data within an
HSMS session. A Data Message can be a Primary
Message or a Reply Message.
entity — an application program associated with an
endpoint of a TCP/IP connection.
header — a 10-byte data element preceding every
HSMS message.
initiator (HSMS) — the entity requesting an HSMS
service. The initiator requests the service by sending an
appropriate HSMS message.
2 POSIX documents can be obtained from Institute of Electrical and
Electronic Engineers (IEEE), 345 East 47th Street, New York, NY
10017 USA