IEC 61158-6-21:2010 pdf – Industrial communication networks – Fieldbus specifications – Part 6-21: Application layer protocol specification -Type 21 elements.
NOTE A device may conlain nor, than on. node
3.2.25
device profile
a collection of device-dependent information and functionality providing consistency between similar devices of the same device type
3.2.26
diagnostic Information
all data available at the server for maintenance purposes
3.2.27
end node
producing or consuming node
3.2.28
endpoint
one ci the communicating entities Involved In a connection
3.2.29
error
discrepancy between a computed, observed, or measured value or condition and the specified or theoretically correct value or condition
3.2.30
error class
general grouping for related error definitions and correspondin9 error codes
3.2.31
error code
identification of a specific type of error within an error class
3.2.32
event
Instance of a change of conditions
3.2.33
FIFO variable
variable object class composed of a set of homogeneously typed elements, where the first written element Is the first element that can be read
NOTE in a fiel&u5 system. only one complete element can be translerred as a result 01 one service invocation
3.2.34
frame
simplified synonym for data link protocol data unit (DLPOU)
3.2.35
group
a) (General): a general term for a collection of objects
b) (Addressing): when describing an address, an address that identifies more than one entity
3.2.36
invocation
act of using a service or otfler resource of an application process
NOTE Each Invocation represents a separate thread ol control that ‘nay be described by Its contest Onc, the service completes. or use ot Ihe resource is released. the invocallon ceases ID exist.
3.2.48
physical device automation or other network device
32.49
point-to-point connection
connection that exists between exactly Iwo application objects
3.2.50
pre-established AR endpoint
AR endpoint placed In an established state during configuration of the AEs that control its endpoints
3.2.51
process data
object(s) that are already pre.processed and transferred cyclically for the purpose of Information or further processing
3.2.52
produce
act of sending data to be received by a consumer
3.2.53
producer
node that is responsible for sending data
3.2.54
properly
general term for descriptive information about an object
3.2.55
provider
source of a data connection
3.2.56
publisher
role of an AR endpoint that transmits APDUs onto the fieldbus for consumption by one or more subscribers
NOTE A publisher may not be aware ot the idenhity or number oh subscribera
3.2.57
publishing manager
role of an AR endpoint in which it issues one or more confirmed service request application protocol data units (APDLJ5) to a publisher to request that a specified oblect be published Two types of publishing managers are defined by this standard, pull publishing managers and push publishing managers, each of which is defined separately.
3.2.58
push publisher
type of publisher that publishes an object in an unconfirmed service request APDU
3.2.59
push publishing manager
type of publishing manager that requests that a specified object be published using an unconfirmed service
3.2.60
push subscriber
type of subscriber that recognizes received unconfirmed service request APDUs as published object data
3261
sending
service user that sends a confirmed primitive or an unconfirmed primitive, or a service provider that sends a confirmed APDU or an unconfirmed APDU
3.2.62
server
a) role of an application relationship endpoint 4AREP) in which It returns a confirmed service response APDU to the client that initiated the request
b) object that provides services to anot her (client) object
3.2.63
service
operation or function than an object and/or object class perlorms upon request from another obiect andor object class
3.2.64
station
host of one AP. identified by a unique data link connection endpoint (DLCEP).address
3.2.65
subscriber
role of an AREP in which it receives APDUs produced by a publisher
3.2.66
receiving
service user that receives a confirmed primitive or an unconfirmed primitive, or a service provider that receives a confirmed APDU or an unconfirmed APDU
3.2.67
resource
processing or information capability of a subsystem.