DIN EN 61158-5-11-2008 Industrial communication networks - Fieldbus specifications - Part 5-11 Application layer service definition - Type 11 elements (IEC 61158-5-11 2007) English.pdf

1、September 2008DEUTSCHE NORM DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik im DIN und VDEPreisgruppe 33DIN Deutsches Institut fr Normung e.V. Jede Art der Vervielfltigung, auch auszugsweise, nur mit Genehmigung des DIN Deutsches Institut fr Normung e.V., Berlin, gestattet.ICS

2、35.100.70; 35.160; 35.240.50!$O NOTE This is part of the abstract ORPC model. 3.6.45 dedicated AR AR used directly by the FAL User NOTE On Dedicated ARs, only the FAL Header and the user data are transferred. 3.6.46 default DL-address value 126 as an initial value for DL-address, which has to be cha

3、nged (e.g. by assignment of an DL-address via the fieldbus) before operation with a DP-master (class 1) 3.6.47 device physical hardware connected to the link NOTE A device may contain more than one node. 3.6.48 device profile a collection of device dependent information and functionality providing c

4、onsistency between similar devices of the same device type 3.6.49 diagnosis information all data available at the server for maintenance purposes 3.6.50 diagnosis information collection system diagnosis information that is assembled at the client side 3.6.51 dynamic AR AR that requires the use of th

5、e AR establishment procedures to place it into an established state 3.6.52 end node producing or consuming node 3.6.53 endpoint one of the communicating entities involved in a connection 3.6.54 engineering abstract term that characterizes the client application or device responsible for configuring

6、an automation system via interconnecting data items 3.6.55 error discrepancy between a computed, observed or measured value or condition and the specified or theoretically correct value or condition B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 611

7、58-5-11:2008 15 3.6.56 error class general grouping for related error definitions and corresponding error codes 3.6.57 error code identification of a specific type of error within an error class 3.6.58 event an instance of a change of conditions 3.6.59 FAL subnet subnetworks composed of one or more

8、data link segments, identified by a subset of the network address NOTE FAL subnets are permitted to contain bridges but not routers. 3.6.60 FIFO variable a Variable Object class, composed of a set of homogeneously typed elements, where the first written element is the first element that can be read

9、NOTE On the fieldbus only one, complete element can be transferred as a result of one service invocation. 3.6.61 frame denigrated synonym for DLPDU 3.6.62 group a) a general term for a collection of objects. Specific uses: b) when describing an address, an address that identifies more than one entit

10、y 3.6.63 interface (a) shared boundary between two functional units, defined by functional characteristics, signal characteristics, or other characteristics as appropriate (b) collection of FAL class attributes and services that represents a specific view on the FAL class 3.6.64 interface definition

11、 language syntax and semantics of describing service parameters in a formal way NOTE This description is the input for the ORPC model, especially for the ORPC wire protocol. 3.6.65 interface pointer key attribute that unambiguously addresses an object interface instance 3.6.66 invocation act of usin

12、g a service or other resource of an application process NOTE Each invocation represents a separate thread of control that may be described by its context. Once the service completes, or use of the resource is released, the invocation ceases to exist. For service invocations, a service that has been

13、initiated but not yet completed is referred to as an outstanding service invocation. B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 61158-5-11:2008 16 3.6.67 I/O data object designated to be transferred cyclically for the purpose of processing 3.6.6

14、8 identifier related diagnosis information dedicated to modules for maintenance purpose 3.6.69 index address of an object within an application process 3.6.70 instance the actual physical occurrence of an object within a class that identifies one of many objects within the same object class EXAMPLE

15、California is an instance of the object class state. NOTE The terms object, instance, and object instance are used to refer to a specific instance. 3.6.71 instance attributes attribute that is unique to an object instance and not shared by the object class 3.6.72 instantiated object that has been cr

16、eated in a device 3.6.73 logical device a certain FAL class that abstracts a software component or a firmware component as an autonomous self-contained facility of an automation device 3.6.74 manufacturer ID identification of each product manufacturer by a unique number 3.6.75 management information

17、 network-accessible information that supports managing the operation of the fieldbus system, including the application layer NOTE Managing includes functions such as controlling, monitoring, and diagnosing. 3.6.76 master parameter set the configuration and parameterization data of all DP-slaves that

18、 are assigned to the corresponding DP-master and the bus parameters 3.6.77 member piece of an attribute that is structured as an element of an array 3.6.78 message router object within a node that distributes messaging requests to appropriate application objects B55EB1B3E14C22109E918E8EA43EDB30F09CC

19、7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 61158-5-11:2008 17 3.6.79 method a synonym for an operational service which is provided by the server ASE and invoked by a client 3.6.80 module a) hardware or logical component of a physical device b) addressable unit inside the DP-slave 3

20、.6.81 multipoint connection connection from one node to many NOTE Multipoint connections allow messages from a single producer to be received by many consumer nodes. 3.6.82 network a set of nodes connected by some type of communication medium, including any intervening repeaters, bridges, routers an

21、d lower-layer gateways 3.6.83 object abstract representation of a particular component within a device, usually a collection of related data (in the form of variables) and methods (procedures) for operating on that data that have clearly defined interface and behaviour 3.6.84 object remote procedure

22、 call model for object oriented or component based remote method invocation 3.6.85 object specific service service unique to the object class which defines it 3.6.86 originator client responsible for establishing a connection path to the target 3.6.87 peer role of an AR endpoint in which it is capab

23、le of acting as both client and server 3.6.88 physical device an automation or other network device a certain FAL class that abstracts the hardware facilities of an automation device 3.6.89 point-to-point connection connection that exists between exactly two application objects 3.6.90 pre-defined AR

24、 endpoint AR endpoint that is defined locally within a device without use of the create service NOTE Pre-defined ARs that are not pre-established are established before being used B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 61158-5-11:2008 18 3.6

25、.91 pre-established AR endpoint AR endpoint that is placed in an established state during configuration of the AEs that control its endpoints 3.6.92 process data object(s) which are already pre-processed and transferred acyclically for the purpose of information or further processing 3.6.93 produce

26、act of sending data to be received by a consumer 3.6.94 producer node that is responsible for sending data 3.6.95 property a general term for descriptive information about an object 3.6.96 provider source of a data connection 3.6.97 providerID an unambiguous identifier within the scope of the ACCO a

27、ssigned by the provider to recognize the internal data of a configured interconnection source 3.6.98 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 of the identity or the number of subscribers and i

28、t may publish its APDUs using a dedicated AR. 3.6.99 publishing manager role of an AR endpoint in which it issues one or more confirmed service request APDUs to a publisher to request the publisher to publish a specified object. Two types of publishing managers are defined by this standard, pull pub

29、lishing managers and push publishing managers, each of which is defined separately 3.6.100 pull publisher type of publisher that publishes an object in response to a request received from its pull publishing manager 3.6.101 pull publishing manager type of publishing manager that requests that a spec

30、ified object be published in a corresponding response APDU 3.6.102 push publisher type of publisher that publishes an object in an unconfirmed service request APDU B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 61158-5-11:2008 19 3.6.103 push publis

31、hing manager type of publishing manager that requests that a specified object be published using an unconfirmed service 3.6.104 pull subscriber type of subscriber that recognizes received confirmed service response APDUs as published object data 3.6.105 push subscriber type of subscriber that recogn

32、izes received unconfirmed service request APDUs as published object data 3.6.106 quality code aware attribute of the RT-Auto class that indicates that an RT-Auto object uses a status code for its data items 3.6.107 quality code additional status information of a data item 3.6.108 quality code unawar

33、e opposite of quality code aware 3.6.109 real configuration input and output data structure of the DP-slave, including definition of data consistency 3.6.110 resource a processing or information capability of a subsystem 3.6.111 route endpoint object container containing Variable Objects of a variab

34、le class 3.6.112 RT-auto an FAL class that abstracts the automation function as a process-related component of an automation device 3.6.113 runtime object model objects that exist in a device together with their interfaces and methods that are accessible 3.6.114 serial number a unique 32-bit integer

35、 value assigned by each manufacturer to every device having Type 2 communication capabilities NOTE The Manufacturer ID and serial number jointly form a unique identifier for each device. B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 61158-5-11:2008

36、 20 3.6.115 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 3.6.116 service operation or function than an object and/or object class performs upon request from anothe

37、r object and/or object class 3.6.117 slot address of a module within a DP-slave 3.6.118 subscriber role of an AREP in which it receives APDUs produced by a publisher 3.6.119 sync function at the DP-slaves for simultaneous data transfer between the output data object and the process 3.6.120 target en

38、d-node to which a connection is established 3.6.121 unconnected message manager (UCMM) component within a node that transmits and receives unconnected explicit messages and sends them directly to the Message Router object 3.6.122 unconnected service messaging service which does not rely on the set u

39、p of a connection between devices before allowing information exchanges 3.7 Abbreviations and symbols ACCO Active connection control object AE Application entity AL Application layer ALME Application layer management entity ALP Application layer protocol APO Application object AP Application process

40、 APDU Application protocol data unit API Application process identifier AR Application relationship AREP Application relationship endpoint ASCII American Standard Code for Information Interchange ASE Application service element B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN

41、 EN 61158-5-11:2008-09 EN 61158-5-11:2008 21 CID Connection ID CIM Computer integrated manufacturing CIP Control and information protocol CM Common memory CM_API Actual packet interval CM_RPI Requested packet interval Cnf Confirmation COR Connection originator CR Communication relationship CREP Comm

42、unication relationship endpoint DL- (as a prefix) data-link- DLC Data-link connection DLCEP Data-link connection endpoint DLL Data-link layer DLM Data-link-management DLSAP Data-link service access point DLSDU DL-service-data-unit DNS Domain name service DP Decentralised peripherals FAL Fieldbus app

43、lication layer FIFO First-in First-out HMI Human-machine interface ID Identifier IDL Interface definition language IEC International Electrotechnical Commission Ind Indication IP Internet protocol ISO International Organization for Standardization LDev Logical device LME Layer management entity O2T

44、Originator to target (connection characteristics) OT Originator to target (connection characteristics) ORPC Object remote procedure call OSI Open Systems Interconnect PDev Physical device PDU Protocol data unit PL Physical layer QoS Quality of service QC Quality code REP Route endpoint Req Request R

45、sp Response B55EB1B3E14C22109E918E8EA43EDB30F09CC7B7EF8DD9NormCD - Stand 2009-03 DIN EN 61158-5-11:2008-09 EN 61158-5-11:2008 22 RT Runtime SAP Service access point SCL Security level SDU Service data unit SEM State event matrix SMIB System management information base SMK System management kernel STD State transition diagram, used to describe object behaviour S-VFD Simple virtual field device T2O Target to originator (connection characteristics) TO Target to originator (connection characteristics) VAO V