SIST EN 14908-1:2014
(Main)Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 1: Protocol Stack
Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 1: Protocol Stack
EN 14908-1 applies to a communication protocol for networked control systems in commercial Building Automation, Controls and Building Management. The protocol provides peer-to-peer communication for networked control and is suitable for implementing both peer-to-peer and master-slave control strategies. This specification describes services in layers 2 to 7. In the layer 2 (data link layer) specification, it also describes the MAC sub-layer interface to the physical layer. The physical layer provides a choice of transmission media. The interface described in this specification supports multiple transmission media at the physical layer. In the layer 7 specification, it includes a description of the types of messages used by applications to exchange application and network management data.
Firmenneutrale Datenkommunikation für die Gebäudeautomation und Gebäudemanagement - Gebäudedatennetzprotokoll - Teil 1: Datenprotokollschichtenmodell
Réseau ouvert de communication de donées pour l'automatisation, la régulation et la gestion technique du bâtiment - Protocole de bâtiment du réseau - Partie 1 : Spécifications du protocole
La présente Norme européenne s'applique à un protocole de communication pour les systèmes de contrôlecommande
en réseau pour l'automatisation, la régulation et la gestion technique des bâtiments commerciaux.
Le protocole permet les communications de poste à poste pour le contrôle-commande en réseau et est
utilisable pour mettre en oeuvre les deux stratégies poste à poste et maître-esclave. Ces spécifications
décrivent les services afférents aux couches 2 à 7. Dans les spécifications de la couche 2 (DLL, Data Link
Layer), la sous-couche MAC (Media Access Control), interface avec la couche physique, est aussi décrite. La
couche physique procure un choix de supports de communication. L'interface décrite dans ces spécifications
permet de prendre en charge plusieurs supports de communication de la couche physique. Dans les
spécifications de la couche 7, se trouve une description des types de messages utilisés par les applications
pour échanger des données de gestion de l'application et du réseau de communication.
Odprta izmenjava podatkov v avtomatizaciji stavb in izvršnih elementov ter pri upravljanju stavb - Protokol regulacijske mreže - 1. del: Protokolarni sklad
Standard EN 14908-1 velja za komunikacijski protokol za mrežne krmilne sisteme v komercialni avtomatizaciji stavb in izvršnih elementov ter pri upravljanju stavb. Protokol zagotavlja komunikacijo vsak-z-vsakim za mrežno krmiljenje in je primeren za uporabo pri uvajanju nadzornih strategij na osnovi razmerja vsak-z-vsakim in nadrejeni-podrejeni. Ta specifikacija opisuje storitve v slojih 2 do 7. V specifikaciji sloja 2 (podatkovno-povezovalni sloj) je opisana tudi povezava med podslojem MAC in fizičnim slojem. Fizični sloj ponuja izbiro različnih prenosnih medijev. Povezava, opisana v tej specifikaciji, podpira več prenosnih medijev na fizičnem sloju. V specifikaciji sloja 7 so opisane vrste sporočil, ki jih uporabljajo aplikacije za izmenjevanje podatkov o aplikacijah in upravljanju omrežja.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Odprta izmenjava podatkov v avtomatizaciji stavb in izvršnih elementov ter pri upravljanju stavb - Protokol regulacijske mreže - 1. del: Protokolarni skladFirmenneutrale Datenkommunikation für die Gebäudeautomation und Gebäudemanagement - Gebäudedatennetzprotokoll - Teil 1: DatenprotokollschichtenmodellRéseau ouvert de communication de donées pour l'automatisation, la régulation et la gestion technique du bâtiment - Protocole de bâtiment du réseau - Partie 1 : Spécifications du protocoleOpen Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 1: Protocol Stack97.120Avtomatske krmilne naprave za domAutomatic controls for household use35.240.99IT applications in other fieldsICS:Ta slovenski standard je istoveten z:EN 14908-1:2014SIST EN 14908-1:2014en,fr,de01-julij-2014SIST EN 14908-1:2014SLOVENSKI
STANDARDSIST EN 14908-1:20061DGRPHãþD
SIST EN 14908-1:2014
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 14908-1
April 2014 ICS 35.240.99; 91.140.01; 97.120 Supersedes EN 14908-1:2005English Version
Open Data Communication in Building Automation, Controls and Building Management - Control Network Protocol - Part 1: Protocol Stack
Réseau ouvert de communication de données pour l'automatisation, la régulation et la gestion technique du bâtiment - Protocole de contrôle du réseau - Partie 1: Niveaux du protocole
Offene Datenkommunikation für die Gebäudeautomation und Gebäudemanagement - Gebäude-Netzwerk-Protokoll -Teil 1: Datenprotokollschichtenmodell This European Standard was approved by CEN on 12 April 2013.
CEN 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 obtained on application to the CEN-CENELEC Management Centre or to any CEN 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 CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2014 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 14908-1:2014 ESIST EN 14908-1:2014
EN 14908-1:2014 (E) 2
Contents Foreword .5 Introduction .6 1 Scope.7 2 Normative references .7 3 Terms and definitions .7 4 Symbols and abbreviations .9 4.1 Symbols and graphical representations .9 4.2 Abbreviations . 10 5 Overview of protocol layering . 11 6 MAC sublayer . 13 6.1 General . 13 6.2 Service provided . 13 6.3 Interface to the link layer . 13 6.4 Interface to the physical layer . 14 6.5 MPDU format . 15 6.6 Predictive p-persistent CSMA — overview description . 15 6.7 Idle channel detection . 16 6.8 Randomising . 17 6.9 Backlog estimation . 17 6.10 Optional priority . 18 6.11 Optional collision detection . 19 6.12 Beta1, Beta2 and Preamble Timings . 20 7 Link layer . 22 7.1 Assumptions . 22 7.2 Service provided . 22 7.3 CRC. 22 7.4 Transmit algorithm . 23 7.5 Receive Algorithm . 23 8 Network layer . 23 8.1 Assumptions . 23 8.2 Service provided . 25 8.3 Service interface . 25 8.4 Internal structuring of the network layer . 26 8.5 NPDU format . 26 8.6 Address recognition . 27 8.7 Routers . 27 8.8 Routing algorithm . 28 8.9 Learning algorithm — subnets . 28 9 Transaction control sublayer . 28 9.1 Assumptions . 28 9.2 Service provided . 29 9.3 Service interface . 29 9.4 State variables . 30 SIST EN 14908-1:2014
EN 14908-1:2014 (E) 3
9.5 Transaction control algorithm . 30 10 Transport layer . 31 10.1 Assumptions . 31 10.2 Service provided . 31 10.3 Service interface . 31 10.4 TPDU types and formats . 32 10.5 Protocol diagram . 33 10.6 Transport protocol state variables . 34 10.7 Send algorithm . 34 10.8 Receive algorithm . 34 10.9 Receive transaction record pool size and configuration engineering . 34 11 Session layer . 37 11.1 Assumptions . 37 11.2 Service Provided . 37 11.3 Service interface . 38 11.4 Internal structure of the session layer . 38 11.5 SPDU types and formats . 39 11.6 Protocol timing diagrams . 40 11.7 Request-response state variables . 43 11.8 Request-response protocol — client part . 43 11.9 Request-response protocol — server part . 43 11.10 Request-response protocol timers . 44 11.11 Authentication protocol. 44 11.12 Encryption algorithm . 44 11.13 Retries and the role of the checksum function . 44 11.14 Random Number Generation . 45 11.15 Using Authentication . 45 12 Presentation/application layer . 45 12.1 Assumptions . 45 12.2 Service provided . 45 12.3 Service interface . 46 12.4 APDU types and formats . 47 12.5 Protocol diagrams . 48 12.6 Application protocol state variables . 50 12.7 Request - response messaging in offline state . 50 12.8 Network variables . 51 12.9 Error notification to the application program . 52 13 Network management & diagnostics . 53 13.1 Assumptions . 53 13.2 Services provided . 53 13.3 Network management and diagnostics application structure . 53 13.4 Node states . 53 13.5 Using the network management services . 54 13.6 Using router network management commands . 58 13.7 NMPDU formats and types . 59 13.8 DPDU types and formats . 80 Annex A (normative)
Reference implementation . 85 A.1 General . 85 A.2 Predictive CSMA algorithm . 85 Annex B (normative)
Additional Data Structures . 380 B.1 General . 380 SIST EN 14908-1:2014
EN 14908-1:2014 (E) 4
B.2 Read-only structures . 381 B.3 Domain table . 386 B.4 Address table . 386 B.5 Network variable tables - informative . 391 B.6 Self-Identification structures . 393 B.7 Configuration structure . 400 B.8 Statistics relative structure . 402 Annex C (informative)
Behavioral characteristics . 404 C.1 Channel capacity and throughput . 404 C.2 Network metrics . 405 C.3 Transaction metrics . 406 C.4 Boundary conditions — power-up . 407 C.5 Boundary conditions — high load . 407 Annex D (normative)
PDU summary . 408 Annex E (normative)
Naming and addressing. 410 E.1 Address types and formats . 410 E.2 Domains . 410 E.3 Subnets and nodes . 411 E.4 Groups. 411 E.5 Unique_Node_ID and node address assignment . 412 E.6 NPDU addressing . 413 Bibliography . 415
SIST EN 14908-1:2014
EN 14908-1:2014 (E) 5
Foreword This document (EN 14908-1:2014) has been prepared by Technical Committee CEN/TC 247 “Building Automation, Controls and Building Management”, the secretariat of which is held by SNV. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by October 2014 and conflicting national standards shall be withdrawn at the latest by October 2014. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. This document supersedes EN 14908-1:2005. This European Standard is part of a series of standards for open data transmission in building automation, control and in building management systems. The content of this European Standard covers the data communications used for management, automation/control and field functions. The following is a list of technical changes since the previous edition: — EN 14908-5 has been added to the normative references; — the normative Annex A has been re-worked for a better understanding. The reference implementation of the standard shows in detail which part is normative and hardware independent, which one is normative but hardware dependent and which one is not normative because it is hardware dependent. This information supports the development of a protocol stack and the understanding of the specified communication services. EN 14908-1 is part of a series of European Standards under the general title Control Network Protocol (CNP), which comprises the following parts: Part 1: Protocol stack; Part 2: Twisted pair communication; Part 3: Power line channel specification; Part 4: IP communication; Part 5: Implementation; Part 6: Application elements. According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 14908-1:2014
EN 14908-1:2014 (E) 6
Introduction This European Standard has been prepared to provide mechanisms through which various vendors of building automation, control, and building management systems may exchange information in a standardised way. It defines communication capabilities. This European Standard will be used by all involved in design, manufacture, engineering, installation and commissioning activities. SIST EN 14908-1:2014
EN 14908-1:2014 (E) 7
1 Scope This European Standard applies to a communication protocol for networked control systems in commercial Building Automation, Controls and Building Management. The protocol provides peer-to-peer communication for networked control and is suitable for implementing both peer-to-peer and master-slave control strategies. This specification describes services in layers 2 to 7. In the layer 2 (data link layer) specification, it also describes the MAC sub-layer interface to the physical layer. The physical layer provides a choice of transmission media. The interface described in this specification supports multiple transmission media at the physical layer. In the layer 7 specification, it includes a description of the types of messages used by applications to exchange application and network management data. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 14908-5, Open Data Communication in Building Automation, Controls and Building Management Implementation Guideline - Control Network Protocol - Part 5: Implementation 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. For the purposes of this European Standard, the following subclause introduces the basic terminology employed throughout this European Standard. Most of it is commonly used and the terms have the same meaning in both the general and the standard context. However, for some terms, there are subtle differences. For example, in general, bridges do selective forwarding based on the layer 2 destination address. There are no layer 2 addresses in this standard protocol, so bridges forward all packets, as long as the domain address in the packet matches a domain of which the bridge is a member. Routers, in general, perform network address modification so that two protocols with the same transport layer but different network layers can be connected to form a single logical network. Routers of this standard may perform network address modification, but typically, they only examine the network address fields and selectively forward packets based on the network layer address fields. 3.1 channel physical unit of bandwidth linking one or more communication nodes. Note 1 to entry: Refer to Annex E for further explanation of the relationship between a channel and a subnet. 3.2 physical repeater device that reconditions the incoming physical layer signal on one channel and retransmits it onto another channel 3.3 store-and-forward repeater device that stores and then reproduces data packets onto a second channel SIST EN 14908-1:2014
EN 14908-1:2014 (E) 8
3.4 bridge device that connects two channels (x and y); forwards all packets from x to y and vice versa, as long as the packets originate on one of the domain(s) that the bridge belongs to 3.5 configuration non-volatile information used by the device to customise its operation. There is configuration data for the correct operation of the protocol in each device, and optionally, for application operation. The network configuration data stored in each device has a checksum associated with the data. Examples of network configuration data are node addresses, communication media parameters such as priority settings, etc. Application configuration information is application specific 3.6 domain virtual network that is the network unit of management and administration. Group and subnet (see below) addresses are assigned by the administrator responsible for the domain, and they have meaning only in the context of that domain 3.7 flexible domain used in conjunction with Unique_Node_ID and broadcast addressing. A node responds to a Unique_Node_ID-addressed message if the address matches, regardless of the domain on which the message was sent. To respond so that the sender receives it, the response shall be sent on the domain in which it was received. Furthermore, this domain shall be remembered for the duration of the transaction so that duplicate detection of any retries is possible. This transitory domain entry at a node is called the flexible domain. How many flexible domain entries a node supports depends on the implementation. However, a minimum of 1 is required 3.8 subnet set of nodes accessible through the same link layer protocol; a routing abstraction for a channel; in this standard subnets are limited to a maximum of 127 nodes 3.9 node abstraction for a physical node that represents the highest degree of address resolvability on a network. A node is identified (addressed) within a subnet by its (logical) node identifier. A physical node may belong to more than one subnet; when it does, it is assigned one (logical) node number for each subnet to which it belongs. A physical node may belong to at most two subnets; these subnets shall be in different domains. A node may also be identified (absolutely) within a network by its Unique_Node_ID 3.10 group uniquely identifiable set of nodes within a domain. Within this set, individual members are identified by their member number. Groups facilitate one-to-many communication and are intended to support functional addressing 3.11 router device that routes data packets to their respective destinations by selectively forwarding from subnet to subnet; a router always connects two (sets of) subnets; routers may modify network layer address fields. Routers may be set to one of four modes:
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.