1、BRITISH STANDARDBS EN 61158-4-8:2008Industrial communication networks Fieldbus specifications Part 4-8: Data-link layer protocol specification Type 8 elementsICS 25.040.40; 35.100.20g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g
2、36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61158-4-8:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 May 2008 BSI 2008ISBN 978 0 580 61579 5National forewordThis British Standard is the UK i
3、mplementation of EN 61158-4-8:2008. It is identical with IEC 61158-4-8:2007. Together with all of the other sections of BS EN 61158-4, it supersedes BS EN 61158-4:2004 which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee AMT/7, Industrial communications Pr
4、ocess measurement and control, including Fieldbus. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance
5、 with a British Standard cannot confer immunity from legal obligations. Amendments/corrigenda issued since publicationDate CommentsEUROPEAN STANDARD EN 61158-4-8 NORME EUROPENNE EUROPISCHE NORM February 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisati
6、on Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 61158-4-8:2008 E ICS 35.100.20; 25.040.40 Partial
7、ly supersedes EN 61158-4:2004English version Industrial communication networks - Fieldbus specifications - Part 4-8: Data-link layer protocol specification - Type 8 elements (IEC 61158-4-8:2007) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 4-8: Spcification des pro
8、tocoles des couches de liaison de donnes - Elments de type 8 (CEI 61158-4-8:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 4-8: Protokollspezifikation des Data Link Layer (Sicherungsschicht) - Typ 8-Elemente (IEC 61158-4-8:2007) This European Standard was approved by CENELEC on 2008-02-01
9、. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtaine
10、d on application to the Central Secretariat or to any CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central
11、 Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malt
12、a, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Foreword The text of document 65C/474/FDIS, future edition 1 of IEC 61158-4-8, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control
13、and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-4-8 on 2008-02-01. This and the other parts of the EN 61158-4 series supersede EN 61158-4:2004. With respect to EN 61158-4:2004 the following changes were made: deletion of Type 6 fieldbus, and the
14、 placeholder for a Type 5 fieldbus data-link layer, for lack of market relevance; addition of new fieldbus types; partition into multiple parts numbered 4-1, 4-2, , 4-19. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identica
15、l national standard or by endorsement (dop) 2008-11-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2011-02-01 NOTE Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the commitment
16、to limited release of intellectual-property-rights made by the holders of those rights permits a particular data-link layer protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the EN 61784 series. Use of the various protocol ty
17、pes in other combinations may require permission from their respective intellectual-property-right holders. IEC and CENELEC draw attention to the fact that it is claimed that compliance with this standard may involve the use of patents as follows, where the xx notation indicates the holder of the pa
18、tent right: Type 8 and possibly other types: DE 41 00 629 C1 PxC Steuer- und Datenbertragungsanlage IEC and CENELEC take no position concerning the evidence, validity and scope of these patent rights. The holders of these patent rights have assured IEC that they are willing to negotiate licences und
19、er reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holders of these patent rights are registered with IEC. Information may be obtained from: PxC: Phoenix Contact GmbH b) for use in the testing and procurement of equip
20、ment; c) as part of an agreement for the admittance of systems into the open systems environment; d) as a refinement to the understanding of time-critical communications within OSI. This standard is concerned, in particular, with the communication and interworking of sensors, effectors and other aut
21、omation devices. By using this standard together with other standards positioned within the OSI or fieldbus reference models, otherwise incompatible systems may work together in any combination. BS EN 61158-4-8:2008 8 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 4-8: Data-link laye
22、r protocol specification Type 8 elements 1 Scope 1.1 General The data-link layer provides basic time-critical messaging communications between devices in an automation environment. This protocol provides a highly-optimized means of interchanging fixed-length input/output data and variable-length seg
23、mented messages between a single master device and a set of slave devices interconnected in a loop (ring) topology. The exchange of input/output data is totally synchronous by configuration, and is unaffected by the messaging traffic. Devices are addressed implicitly by their position on the loop. T
24、he determination of the number, identity and characteristics of each device can be configured, or can be detected automatically at start-up. 1.2 Specifications This standard specifies a) procedures for the timely transfer of data and control information from one data-link user entity to a peer user
25、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 standard, and their representation as physical interface data units. 1.3 Procedures The p
26、rocedures 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
27、and a Ph-service provider in the same system through the exchange of Ph-service primitives. 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 or fieldbus reference
28、models, and which require the ability to interconnect in an open systems interconnection environment. Profiles provide a simple multi-attribute means of summarizing an implementations capabilities, and thus its applicability to various time-critical communications needs. BS EN 61158-4-8:2008 9 1.5 C
29、onformance This standard also specifies conformance requirements for systems implementing these procedures. This standard does not contain tests to demonstrate compliance with such requirements. 2 Normative references The following referenced documents are indispensable for the application of this s
30、tandard. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 61158-2 (Ed.4.0), Industrial communication networks Fieldbus specifications Part 2: Physical layer specification and service de
31、finition IEC 61158-3-8, Digital data communications for measurement and control Fieldbus for use in industrial control systems Part 3-8: Data link service definition Type 8 elements ISO/IEC 7498-1, Information technology Open Systems Interconnection Basic Reference Model: The Basic Model ISO/IEC 749
32、8-3, Information technology Open Systems Interconnection Basic Reference Model: Naming and addressing ISO/IEC 10731, Information technology Open Systems Interconnection Basic Reference Model Conventions for the definition of OSI services 3 Terms, definitions, symbols and abbreviations For the purpos
33、es of this standard, the following terms, definitions, symbols and abbreviations apply. 3.1 Reference model terms and definitions This standard is based in part on the concepts developed in ISO/IEC 7498-1 and ISO/IEC 7498-3, and makes use of the following terms defined therein. 3.1.1 DL-address 7498
34、-33.1.2 DL-address-mapping 7498-13.1.3 DL-connection 7498-13.1.4 DL-connection-end-point 7498-13.1.5 DL-connection-end-point-identifier 7498-13.1.6 DL-data-source 7498-13.1.7 DL-name 7498-33.1.8 DL-protocol 7498-13.1.9 DL-protocol-connection-identifier 7498-13.1.10 DL-protocol-control-information 74
35、98-13.1.11 DL-protocol-data-unit 7498-1BS EN 61158-4-8:2008 10 3.1.12 DL-service-connection-identifier 7498-13.1.13 DL-service-data-unit 7498-13.1.14 DL-user-data 7498-13.1.15 layer-management 7498-13.1.16 (N)-entity DL-entity Ph-entity 7498-13.1.17 (N)-interface-data-unit DL-service-data-unit (N=2)
36、 Ph-interface-data-unit (N=1) 7498-13.1.18 (N)-layer DL-layer (N=2) Ph-layer (N=1) 7498-13.1.19 (N)-service DL-service (N=2) Ph-service (N=1) 7498-13.1.20 (N)-service-access-point DL-service-access-point (N=2) Ph-service-access-point (N=1) 7498-13.1.21 (N)-service-access-point-address DL-service-acc
37、ess-point-address (N=2) Ph-service-access-point-address (N=1) 7498-13.1.22 Ph-interface-control-information 7498-13.1.23 Ph-interface-data 7498-13.1.24 primitive name 7498-33.1.25 reset 7498-13.1.26 systems-management 7498-13.2 Service convention terms and definitions This standard also makes use of
38、 the following terms defined in ISO/IEC 10731 as they apply to the data-link layer: 3.2.1 confirm (primitive); requestor.deliver (primitive) 3.2.2 DL-service-primitive; primitive 3.2.3 DL-service-provider 3.2.4 DL-service-user 3.2.5 indication (primitive) acceptor.deliver (primitive) BS EN 61158-4-8
39、:2008 11 3.2.6 request (primitive); requestor.submit (primitive) 3.2.7 response (primitive); acceptor.submit (primitive) 3.3 Common terms and definitions NOTE This subclause contains the common terms and definitions used by Type 8. 3.3.1 link, local link single DL-subnetwork in which any of the conn
40、ected DLEs may communicate directly, without any intervening DL-relaying, whenever all of those DLEs that are participating in an instance of communication are simultaneously attentive to the DL-subnetwork during the period(s) of attempted communication 3.3.2 DLSAP distinctive point at which DL-serv
41、ices are provided by a single DL-entity to a single higher-layer entity. NOTE This definition, derived from ISO/IEC 7498-1, is repeated here to facilitate understanding of the critical distinction between DLSAPs and their DL-addresses. (See Figure 1.) PhSA P PhSA P DL-entity DLS-user-entity DLS-user
42、-entity DLSA P DLSA P DLSA P DLSA P- addresses group DL- address DLSA P- address Ph-layer DL-layer DLS-use rs DLSA P- address NOTE 1 DLSAPs and PhSAPs are depicted as ovals spanning the boundary between two adjacent layers. NOTE 2 DL-addresses are depicted as designating small gaps (points of access
43、) in the DLL portion of a DLSAP. NOTE 3 A single DL-entity may have multiple DLSAP-addresses and group DL-addresses associated with a single DLSAP. Figure 1 Relationships of DLSAPs, DLSAP-addresses and group DL-addresses 3.3.3 DL(SAP)-address either an individual DLSAP-address, designating a single
44、DLSAP of a single DLS-user, or a group DL-address potentially designating multiple DLSAPs, each of a single DLS-user BS EN 61158-4-8:2008 12 NOTE This terminology is chosen because ISO/IEC 7498-3 does not permit the use of the term DLSAP-address to designate more than a single DLSAP at a single DLS-
45、user. 3.3.4 extended link DL-subnetwork, consisting of the maximal set of links interconnected by DL-relays, sharing a single DL-name (DL-address) space, in which any of the connected DL-entities may communicate, one with another, either directly or with the assistance of one or more of those interv
46、ening DL-relay entities NOTE An extended link may be composed of just a single link. 3.3.5 frame denigrated synonym for DLPDU 3.3.6 receiving DLS-user DL-service user that acts as a recipient of DL-user-data NOTE A DL-service user can be concurrently both a sending and receiving DLS-user. 3.3.7 send
47、ing DLS-user DL-service user that acts as a source of DL-user-data 3.4 Additional Type 8 definitions 3.4.1 bus coupler PhL entity which includes or excludes Ph-segments into or from the network 3.4.2 device slave or master 3.4.3 device code two octets which characterize the properties of a slave 3.4
48、.4 DLPDU cycle transaction initiated from the master in which user data or identification/status information is sent to all slaves and within the same cycle - received from all slaves 3.4.5 IN data data received by the master and sent by the slaves 3.4.6 master DL-entity controlling the data transfe
49、r on the network and initiating the media access of the slaves by starting the DLPDU cycle 3.4.7 OUT data data sent by the master and received by the slaves 3.4.8 parameter channel acyclic transmission path using a client/server communication model BS EN 61158-4-8:2008 13 3.4.9 process data channel conveyance path allowing a very efficient, high-speed and cyclic transmission of process-relevant data, between slaves and master 3.4.10 rec
