Industrial communication networks – Fieldbus specifications – Part 4-3: Data-link layer protocol specification – Type 3 elements
|Publication Date:||1 April 2019|
|ICS Code (Networking):||35.110|
|ICS Code (Data link layer):||35.100.20|
|ICS Code (Industrial process measurement and control):||25.040.40|
The data-link layer provides basic time-critical messaging communications between devices in an automation environment.
This protocol provides communication opportunities to a pre-selected "master" subset of datalink entities in a cyclic asynchronous manner, sequentially to each of those data-link entities. Other data-link entities communicate only as permitted and delegated by those master data-link entities.
For a given master, its communications with other data-link entities can be cyclic, or acyclic with prioritized access, or a combination of the two.
This protocol provides a means of sharing the available communication resources in a fair manner. There are provisions for time synchronization and for isochronous operation.
This document specifies
a) procedures for the timely transfer of data and control information from one data-link user entity to a peer user entity, and among the data-link entities forming the distributed data-link service provider;
b) the structure of the fieldbus DLPDUs used for the transfer of data and control information by the protocol of this document, and their representation as physical interface data units.
The procedures are defined in terms of
a) the interactions between peer DL-entities (DLEs) through the exchange of fieldbus DLPDUs;
b) the interactions between a DL-service (DLS) provider and a DLS-user in the same system through the exchange of DLS primitives;
c) the interactions between a DLS-provider and a Ph-service provider in the same system through the exchange of Ph-service primitives.
These procedures are applicable to instances of communication between systems which support time-critical communications services within the data-link layer of the OSI or fieldbus reference models, and which require the ability to interconnect in an open systems interconnection environment.
Profiles provide a simple multi-attribute means of summarizing an implementation's capabilities, and thus its applicability to various time-critical communications needs.
This document also specifies conformance requirements for systems implementing these procedures. This document does not contain tests to demonstrate compliance with such requirements.