If you have difficulty in submitting comments on draft standards you can use a commenting template and email it to admin.start@bsigroup.com. The commenting template can be found here.
Standards Development
1.1 General
This document specifies DL protocol elements to transfer data between a Type 12 MainDevice and a Type 12 segment consisting of a network in between. The network can be according to the IEEE 802.1 specification or a set of CPF 12 segments connected with elements defined in this specification.
The data-link layer provides basic time-critical messaging communications between devices in an automation environment.
This protocol provides communication opportunities to all participating data-link entities
a) in a synchronously-starting cyclic manner, and
b) in a cyclic or acyclic asynchronous manner, as requested each cycle by each of those data- link entities.
Thus, this protocol can be characterized as one which provides cyclic and acyclic access asynchronously but with a synchronous restart of each cycle.
1.2 Specifications
This document specifies
a) procedures for the transfer of data and control information from one data-link user entity to one or more user entities;
b) the structure of the DLPDUs used for the transfer of data and control information by the protocol of this standard, and their representation as physical interface data units.
1.3 Procedures The procedures are defined in terms of
a) the interactions between DL entities (DLEs) through the exchange of 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 the MAC services of ISO/IEC 8802-3.
1.4 Applicability
These procedures are applicable to instances of communication between systems which support time-critical communications services within the data-link layer of the OSI reference model, 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.
1.5 Conformance
This standard also specifies conformance requirements for systems implementing these procedures. This part of this standard does not contain tests to demonstrate compliance with such requirements.
NEW WORK ITEM PROPOSAL
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment on proposal
Required form fields are indicated by an asterisk (*) character.