DIN EN 61158-5-4-2008 工业通讯网络.现场总线规范.第5-4部分:应用层设备定义.4型元件.仅为CD-ROM

标准号：DIN EN 61158-5-4-2008
中文标准名称：工业通讯网络.现场总线规范.第5-4部分:应用层设备定义.4型元件.仅为CD-ROM
英文标准名称：Industrial communication networks - Fieldbus specifications - Part 5-4: Application layer service definition - Type 4 elements (IEC 61158-5-4:2007); English version EN 61158-5-4:2008, only on CD-ROM
标准类型：N18;P76
发布日期：1999/12/31 12:00:00
实施日期：2008/9/1 12:00:00
中国标准分类号：N18;P76
国际标准分类号：35.100.70;35.160
引用标准：IEC 60559;IEC 61158-3-4;IEC 61158-4-4;IEC 61158-6-4;ISO/IEC 7498-1;ISO/IEC 7498-3;ISO/IEC 8822;ISO/IEC 8824;ISO/IEC 9545;ISO/IEC 10646-1;ISO/IEC 10731
适用范围：1.1 OverviewThis standard provides common elements for basic time-critical and non-time-critical messagingcommunications between application programs in an automation environment and material specificto Type 4 fieldbus. 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 ofcertainty. Failure to complete specified actions within the time window risks failure of theapplications 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 Type 4fieldbus application layer in terms ofa) an abstract model for defining application resources (objects) capable of being manipulated byusers via the use of the FAL service,b) the primitive actions and events of the service;c) the parameters associated with each primitive action and event, and the form which they take;andd) the interrelationship between these actions and events, and their valid sequences.The purpose of this standard is to define the services provided to1) the FAL user at the boundary between the user and the application layer of the fieldbusreference model, and2) Systems Management at the boundary between the application layer and Systems Managementof the fieldbus reference model.This standard specifies the structure and services of the Type 4 fieldbus application layer, inconformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI application layerstructure (ISO/IEC 9545).FAL services and protocols are provided by FAL application-entities (AE) contained within theapplication processes. The FAL AE is composed of a set of object-oriented application serviceelements (ASEs) and a layer management entity (LME) that manages the AE. The ASEs providecommunication 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 themanagement of the instances of FAL classes.Although these services specify, from the perspective of applications, how request and responsesare issued and delivered, they do not include a specification of what the requesting and respondingapplications are to do with them. That is, the behavioral aspects of the applications are notspecified; only a definition of what requests and responses they can send/receive is specified. Thispermits greater flexibility to the FAL users in standardizing such object behavior. In addition to theseservices, some supporting services are also defined in this standard to provide access to the FAL tocontrol certain aspects of its operation.1.2 SpecificationsThe principal objective of this standard is to specify the characteristics of conceptual applicationlayer services suitable for time-critical communications, and thus supplement the OSI BasicReference Model in guiding the development of application layer protocols for time-criticalcommunications.A secondary objective is to provide migration paths from previously-existing industrialcommunications protocols. It is this latter objective which gives rise to the diversity of servicesstandardized as the various Types of IEC 61158, and the corresponding protocols standardized insubparts of IEC 61158-6.This specification may be used as the basis for formal application programming interfaces.Nevertheless, it is not a formal programming interface, and any such interface will need to addressimplementation issues not covered by this specification, includinga) the sizes and octet ordering of various multi-octet service parameters, andb) the correlation of paired request and confirm, or indication and response, primitives.