BS EN 61158-5-21:2012

INTRODUCTION
1 Scope
2 Normative references
3 Terms, definitions, symbols, abbreviations and
  conventions
4 Concepts
5 Data type ASE
6 Communication model specification
Bibliography
Annex ZA (normative) - Normative references to
         international publications with their
         corresponding European publications

Describes the common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment as well as material specific to the Type 21 protocol.

1.1 Overview The Fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be considered a window between corresponding application programs. This standard provides the common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment as well as material specific to the Type 21 protocol. The term “time-critical” is used to represent the presence of a time-window within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant, and possibly human life. This standard defines, in an abstract way, the externally visible service provided by the FAL in terms of: an abstract model for defining application resources (objects) capable of being manipulated by users via the FAL service; the primitive actions and events of the service; the parameters associated with each primitive action and event, and the form that they take; the interrelationship between these actions and events, and their valid sequences. The purpose of this standard is to define the services provided to: the FAL-user at the boundary between the user and the application layer of the fieldbus Reference Model; systems management at the boundary between the application layer and systems management of the fieldbus Reference Model. This standard describes the structure and services of the IEC FAL, 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 (AEs) contained in 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 management of the instances of FAL classes. Although these services specify how requests and responses are issued and delivered from the perspective of applications, they do not include a specification of what the requesting and responding applications are to do with them. That is, these services only define what requests and responses applications can send or receive, not the functions of the applications themselves. 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. 1.2 Specifications The principal objective of this standard is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for time-critical communications. A secondary objective is to provide migration paths from previously existing industrial communications protocols. This latter objective gives rise to the diversity of services standardized as the various types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6. This standard may be used as the basis for formal application programming interfaces. Nevertheless, it is not a formal programming interface, and any such interface must address implementation issues not covered by this standard, including: sizes and octet ordering of various multi-octet service parameters; correlation of paired primitives for request and confirmation, or indication and response. 1.3 Conformance This standard does not specify individual implementations or products, nor does it constrain the implementations of application layer entities in industrial automation systems. There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through the implementation of conforming application layer protocols that fulfill any given type of application layer services as defined in this standard.