semi合集-English.pdf - 第2109页
SEMI E54.14-0305 © SEMI 2005 3 5.1.2 AREP — Applicat ion Reference Endpoint 5.1.3 ASE — Application Service El ement 5.1.4 CDM — Comm on Device Model 5.1.5 DCE — Distri buted Computing Environment 5.1.6 DCP — Discovery a…

SEMI E54.14-0305 © SEMI 2005 2
4 Referenced Standards
4.1 SEMI Standards
SEMI E39 — Object Services Standard: Concepts, Behavior, and Services
SEMI E54.1 — Standard for Sensor/Actuator Network Common Device Model
SEMI E54.3 — Specification for Sensor/Actuator Network Specific Device Model for Mass Flow Device
SEMI E54.10 — Specification for Sensor/Actuator Network Specific Device Model for an In-Situ Particle Monitor
Device
SEMI E54.11 — Specific Device Model for Endpoint Devices
4.2 IEC Standards
1
IEC 61158-5 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems – Application Layer service definition (reference standard for the model in use)
IEC 61158-6 — Digital data communication for measurement and control – Fieldbus for use in industrial control
systems – Application Layer protocol specification (reference standard for the model in use)
4.3 IEEE Standards
2
IEEE 802.3 — Telecommunications and information exchange between systems — Local and metropolitan area
networks — Part 3:Carrier sense multiple access with collision detection (CSMA/CD) access method and physical
layer specifications
IEEE 802.1D — Telecommunications and information exchange between systems — Local and metropolitan area
networks — Common specifications — Media Access Control (MAC) Bridges
IEEE 802.1Q — Telecommunications and information exchange between systems — Local and metropolitan area
networks — Common specifications —Virtual Bridged Local Area Networks
4.4 ISO Standards
3
ISO 7498 Information Technology — Open Systems Interconnection — Basic Reference Model
4.5 PROFINET Standards
4
PROFINET IO — Application Layer protocol specification
PROFINET IO — Application Layer service definition
PROFIBUS Profile Guidelines — Part 1: Identification & Maintenance Functions
PROFINET — Discovery and Configuration Protocol
PROFINET — Installation Guideline
GSD Specification for PROFINET
NOTICE: Unless otherwise indicated, all documents cited shall be the latest published versions.
5 Terminology
5.1 Abbreviations and Acronyms
5.1.1 APDU — Application Protocol Data Unit
1 International Electrotechnical Commission 3, rue de Varembé, Case Postale 131, CH-1211 Geneva 20, Switzerland. Telephone:
41.22.919.02.11; Fax: 41.22.919.03.00, Website: www.iec.ch
2 IEEE , The Institute of Electrical and Electronics Engineers, Inc., 3 Park Avenue, New York, NY 10016-5997, USA, Website: www.ieee.org
3 International Organization for Standardization, ISO Central Secretariat, 1, rue de Varembé, Case postale 56, CH-1211 Geneva 20, Switzerland.
Telephone: 41.22.749.01.11; Fax: 41.22.733.34.30, Website: www.iso.ch
4 Profibus International, Haid-und-Neu-Str. 7,76131 Karlsruhe, Germany, Telephone: 49 721 9658 590; Fax: 49 721 9658 589, Website:
www.profibus.com

SEMI E54.14-0305 © SEMI 2005 3
5.1.2 AREP — Application Reference Endpoint
5.1.3 ASE — Application Service Element
5.1.4 CDM — Common Device Model
5.1.5 DCE — Distributed Computing Environment
5.1.6 DCP — Discovery and Configuration Protocol
5.1.7 DHCP — Dynamic Host Configuration Protocol
5.1.8 DM — Device Manager
5.1.9 GSD — Generic station description
5.1.10 IM — Identification and Maintenance
5.1.11 IO — Input Output
5.1.12 IP — Internet Protocol
5.1.13 NCS — Network Communication Standard
5.1.14 OSI — Basic Reference Model for Open Systems Interconnection (ISO 7498)
5.1.15 PDU — Protocol Data Unit
5.1.16 PHY — Physical Layer
5.1.17 RPC — Remote Procedure Call
5.1.18 SAC — Sensor, actor, controller (object)
5.1.19 SAN — Sensor/actor network
5.1.20 SAP — Service Access Point
5.1.21 SDM — Specific Device Model
5.1.22 UDP — User Datagram Protocol
5.2 Terminology Defined in Sensor/Actuator Network Common Device Model (SEMI E54.1)
5.2.1 attribute
5.2.2 behavior
5.2.3 byte
5.2.4
common device model
5.2.5 device
5.2.6 Device Manager (DM) Object
5.2.7 device model
5.2.8 instance
5.2.9 network communication standard
5.2.10 object
5.2.11 Sensor, Actuator and Controller (SAC) Object
5.2.12 service
5.2.13 specific device model
5.2.14 state diagram

SEMI E54.14-0305 © SEMI 2005 4
5.3 Terminology Mapping
5.3.1 As this standard defines the mapping of CDM
data structure and behavior over a network it makes
use of many of the terms in SEMI E54.1. Table 1
provides a mapping of fundamental terminology of
the CDM document into this document which uses the
terminology of PROFINET IO.
5.4 PROFINET Specific Definitions
5.4.1 Context Management — network-accessible
information (communication objects) that supports
managing the operation of the system, including the
application layer.
NOTE 1: Managing includes functions such as controlling,
monitoring, and diagnosing.
5.4.2 Device Data Base — an electronic file that provides a clear and comprehensive description of the
characteristics of a device type in a precisely defined format. Also called a GSD File.
5.4.3 Device Profile — a Device Data Base Sheet, which specifies the characteristic features of a device, and a
GSD File.
5.4.4 channel — single physical or logical link of an input or output application object of a server to the process.
5.4.5 channel related diagnosis — information concerning a specific element of an input or output application
object, provided for maintenance purposes.
5.4.6 diagnosis data object — object(s) which contains diagnosis information referenced by
device/slot/subslot/diagnosis identifier.
5.4.7 GSD File — see Device Data Base.
5.4.8 Index — address of a record data object.
5.4.9 IO Controller — a device that manages its assigned IO Devices and handles user data exchange; usually a
programmable controller.
5.4.10 IO data object — object designated to be transferred cyclically for the purpose of processing and referenced
by device/slot/Subslot.
5.4.11 IO Device — a device that is configured and managed by IO Controllers and IO Supervisors; an IO Device
initiates no unsolicited communications.
5.4.12 IO Supervisor — a device that interacts as a configuration or diagnostic tool; usually a programming device.
5.4.13 module — hardware or logical component of a physical device.
5.4.14 provider — node or source sending data to one or many consumers.
5.4.15 record data object — object(s) which are already pre-processed and transferred acyclically for the purpose
of information or further processing and referenced by device/slot/subslot/index.
5.4.16 resource — processing or information capability.
5.4.17 server — a) role of an AREP in which it returns a confirmed service response APDU to the client that
initiated the request — b) object which provides services to another (client) object.
5.4.18 service — operation or function that an object and/or object class performs upon request from another object
and/or object class.
5.4.19 Service Access Point — an addressable location in a device for the directing of service requests.
5.4.20 slot — address of a structural unit within an IO device.
Table 1 Mapping of CDM to NCS Terminology
CDM Term NCS Equivalent
Device IO Device
Object =(with ASE as class specification)
Instance =
Attribute =
Behavior =
Service =
State Diagram Protocol Machine, State Machine
Byte =, Unsigned8
Nibble Specific field coding
Character String Visible String