Digital Data Communications for Measurement and Control - Fieldbus for Use in Industrial Control Systems - Part 5: Application Layer Service Definition CORRIGENDUM 1
|Publication Date:||1 July 2004|
|ICS Code (IT applications in industry):||35.240.50|
|ICS Code (Industrial automation systems):||25.040|
|ICS Code (Open systems interconnection (OSI)):||35.100|
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
This part of IEC 61158 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". Each type has its own separate clause in the document.
Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this standard to provide access to the FAL to control certain aspects of its operation.