IEC 61158-5-10:2023
工業(yè)通信網(wǎng)絡(luò)–現(xiàn)場總線規(guī)范–第 5-10 部分：應(yīng)用層服務(wù)定義 –類型 10 元素

Industrial communication networks – Fieldbus specifications – Part 5-10: Application layer service definition – Type 10 elements

預(yù)覽 IEC 61158-5-10:2023前三頁

標準號

IEC 61158-5-10:2023

發(fā)布

2023年

總頁數(shù)

766頁

發(fā)布單位

國際電工委員會

當(dāng)前最新

IEC 61158-5-10:2023

 

 

引用標準

IEC 61131-3:2013 IEC 61158-1:2023 IEC 61158-2:2023 IEC 61158-6-10:2023 IEC 61784-3-3 IEC 61800-7-203:2015 IEC 62439-2:2021 IEEE Std 802.1AB-2016 IEEE Std 802.1AS-2020 IEEE Std 802.1CB-2017 IEEE Std 802.1Q-2018 IEEE Std 802.3-2018 ISO 8601-1:2019 ISO/IEC 10646 ISO/IEC 10731 ISO/IEC 646:1991 ISO/IEC 7498-1 ISO/IEC 8822 ISO/IEC 8824-1 ISO/IEC 9545 ISO/IEC 9834-8

適用范圍

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'. This part of IEC 61158 provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 10 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 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 document defines in an abstract way the externally visible service provided by the Type 10 fieldbus application layer in terms of: an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service, the primitive actions and events of the service; the parameters associated with each primitive action and event, and the form which they take; and the interrelationship between these actions and events, and their valid sequences. The purpose of this document 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, and Systems Management at the boundary between the application layer and Systems Management of the fieldbus reference model. This document specifies the structure and services of the Type 10 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) 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. 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 document to provide access to the FAL to control certain aspects of its operation. The principal objective of this document 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. It is this latter objective which 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 document can 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 address implementation issues not covered by this specification, including a) the sizes and octet ordering of various multi-octet service parameters, and b) the correlation of paired request and confirm, or indication and response, primitives. This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. There is no conformance of equipment to this application layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfil the Type 10 application layer services as defined in this document.

IEC 61158-5-10:2023相似標準

誰引用了IEC 61158-5-10:2023 更多引用