IEC 61158-5-2003 pdf – Digital data communications for measurement and control – Fieldbus for use in industrial control systems – Part 5: Application layer service definition

IEC 61158-5-2003 pdf – Digital data communications for measurement and control – Fieldbus for use in industrial control systems – Part 5: Application layer service definition.
1 Scope The fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs.” The FAL is an Application Layer Communication Standard designed to support the conveyance of time-critical and non-time-critical application requests and responses among devices in an automation environment. The term “time-critical” is used to represent the presence of an application time-window, within which one or more specified actions are required to be completed with some defined level of certainty. This standard specifies the structure and services of the IEC fieldbus Application Layer. It is specified in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. This part of IEC 61 1 58 specifies interactions between remote applications in terms of – an abstract model for defining application resources (objects) capable of being manipulated by users via the use of FAL Services, – the primitives (interactions between the FAL and the FAL user) associated with each FAL Service; – the parameters associated with each primitive; – the interrelationship between and the valid sequences of the primitives for each service. Several models of communications are specified in this document. Each model is specifed as a communciation “type”.
IEC 61 1 31 , Programmable controllers IEC 61 1 31 -1 :1 992, Part 1: Programmable controllers — General information IEC 61 1 31 -3:1 993, Part 3: Programmable controllers — Programming languages IEC 61 1 58, Digital data communications for measurement and control – Fieldbus for use in industrial control systems IEC 61 1 58-3:2003, Digital data communications for measurement and control – Fieldbus for use in industrial control systems — Part 3: Data Link Layer service definition IEC 61 1 58-4:2003, Digital data communications for measurement and control – Fieldbus for use in industrial control systems — Part 4: Data Link Layer Protocol Specification IEC 61 1 58-6:2003, Digital data communications for measurement and control – Fieldbus for use in industrial control systems — Part 6: Application Layer Protocol Specification ISO/IEC 646:1 991 , Information technology – ISO 7–bit coded character set for information interchange ISO/IEC 7498, Information technology – Open Systems Interconnection – Basic Reference Model ISO/IEC 7498-1 :1 994, Information technology – Open Systems Interconnection – Basic Reference Model — Part 1: The Basic Model ISO/IEC 7498-3:1 997, Information technology – Open Systems Interconnection – Basic Reference Model — Part 3: Naming and addressing ISO/IEC 8822:1 994, Information technology – Open Systems Interconnection – Presentation service definition ISO/IEC 8824:1 990, Information technology – Open Systems Interconnection – Specification of Abstract Syntax Notation One (ASN.1) ISO/IEC 8859-1 :1 998, Information technology – 8-bit single-byte coded graphic character sets – Part 1: Latin alphabet No. 1 ISO/IEC 9545:1 994, Information technology – Open Systems Interconnection – Application Layer structure ISO/IEC 1 0646-1 :1 993, Information technology – Universal Multiple-Octet Coded Character Set (UCS) – Architecture and Basic Multilingual Plane
3.2 ISO/IEC 8822 terms For the purposes of this document, the following terms as defined in ISO/IEC 8822 apply: a) abstract syntax b) presentation context 3.3 ISO/IEC 9545 terms For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply: a) application-association b) application-context c) application context name d) application-entity-invocation e) application-entity-type f) application-process-invocation g) application-process-type h) application-service-element i) application control service element 3.4 ISO/IEC 8824 terms For the purposes of this document, the following terms as defined in ISO/IEC 8824 apply: a) object identifier b) type 3.5 Fieldbus Data Link Layer terms For the purposes of this document, the following terms as defined in IEC 61 1 58-3 and IEC 61 1 58-4 apply. a) DL-Time b) DL-Scheduling-policy c) DLCEP d) DLC e) DL-connection-oriented mode f) DLPDU g) DLSDU h) DLSAP i) fixed tag j) generic tag k) link l) MAC ID m) network address