GB/T 47014.3-2026Industrial communication networks - Fieldbus specifications - Type 2 elements: EtherNet/IP, ControlNet and DeviceNet specifications - Part 3: Applicatoin layer service definition (English PDF)

1.1 Overview

The Fieldbus Application Layer (FAL) provides user programs with a method to access the fieldbus communication environment. In this respect, the FAL can...

It is considered as a "window between corresponding applications".

This document provides basic time constraints and...

Non-time-strict message communication common elements. The term "time-strict" is used to indicate the existence of a time window, within which...

Within the specified time window, one or more prescribed actions must be completed with a defined level of determinism. Failure to complete the prescribed actions within the specified time window will result in...

The application requesting this action risks failure, which could endanger equipment, factories, or even personal safety.

This document defines the Type 2 Fieldbus application layer externally visible services in an abstract form as follows.

a) An abstract model used to define application resources (objects) that users can manipulate using FAL services;

b) The actions and events of the service primitive;

c) The parameters associated with each primitive action and event, and the format they use;

d) The interrelationships between these actions and events and their effective sequence.

This document aims to define the services to be provided to.

a) FAL users located at the boundary between the user in the fieldbus reference model and the application layer;

b) System management, which is located at the intersection of the application layer and system management in the fieldbus reference model.

This document specifies the structure and services of the Type 2 fieldbus application layer, consistent with the OSI Basic Reference Model GB/T 9387.1 (IDT).

It conforms to ISO/IEC 7498-1 and OSI application layer architecture GB/T 17176 (IDT ISO/IEC 9545).

FAL services and protocols are provided by FAL application entities (AEs) included in the application process. FALAEs consist of a set of object-oriented applications.

It consists of a Service Element (ASE) and a Layer Management Entity (LME) that manages the AE. The ASE provides communication services to operate a set of related elements.

Application Process Object (APO) classes. One of them, FALASE, is the management ASE, which provides a set of common methods for managing FAL class instances.

Serve.

From an application perspective, although these services specify how requests and responses are sent and transmitted, they do not specify how requests are sent.

Applications and responses handle this type of service. That is, the specific behavior of the application is not specified; only that it can send/receive.

Which requests and responses. This provides FAL users with greater flexibility to standardize the behavior of such objects. In addition to these services, this document also...

Several support services are defined to provide access to the FAL and to control certain aspects of its operation.

1.2 Standards

The main purpose of this document is to define the characteristics of conceptual application-layer services applicable to time-strict communication, thereby serving as a basis for the OSI basic parameters.

This supplements the model to guide the development of application layer protocols for time-critical communication.

A secondary objective of this document is to provide a path for migrating from existing industrial communication networks. This objective leads to a diversification of services.

These services are standardized into different types of IEC 61158, and the corresponding protocols are standardized into sub-parts of IEC 61158-6.

This document can be used as a basis for formal application programming interfaces (APIs), but it is not a formal programming interface itself; all such interfaces require...