1、March 2013 Translation by DIN-Sprachendienst.English price group 36No part of this translation may be reproduced without prior permission ofDIN Deutsches Institut fr Normung e. V., Berlin. Beuth Verlag GmbH, 10772 Berlin, Germany,has the exclusive right of sale for German Standards (DIN-Normen).ICS
2、35.240.99; 97.120!$3“1962916www.din.deDDIN EN 13321-2Open Data Communication in Building Automation, Controls andBuilding Management Home and Building Electronic Systems Part 2: KNXnet/IP Communication;English version EN 13321-2:2012,English translation of DIN EN 13321-2:2013-03Offene Datenkommunika
3、tion fr die Gebudeautomation und Gebudemanagement Elektrische Systemtechnik fr Heim und Gebude Teil 2: KNXnet/IP-Kommunikation;Englische Fassung EN 13321-2:2012,Englische bersetzung von DIN EN 13321-2:2013-03Rseau ouvert de communication de donnes pour lautomatisation, la rgulation et lagestion tech
4、nique du btiment Systmes lectroniques pour la maison et le btiment Partie 2: Communication KNXnet/IP;Version anglaise EN 13321-2:2012,Traduction anglaise de DIN EN 13321-2:2013-03SupersedesDIN EN 13321-2:2007-01www.beuth.deIn case of doubt, the German-language original shall be considered authoritat
5、ive.Document comprises 172 pages 02.13 DIN EN 13321-2:2013-03 2 A comma is used as the decimal marker. National foreword This document (EN 13321-2:2012) has been prepared by Technical Committee CEN/TC 247 “Building Automation, Controls and Building Management” (Secretariat: SNV, Switzerland). The re
6、sponsible German body involved in its preparation was the Normenausschuss Heiz- und Raum-lufttechnik (Heating and Ventilation Technology Standards Committee), Working Committee NA 041-03-68 AA Gebudeautomation und -kommunikation (SpA CEN/TC 247/WG 4). Amendments This standard differs from DIN EN 133
7、21-2:2007-01 as follows: a) the standard has been editorially revised. Previous editions DIN V EN V 13321-2: 2000-05 DIN EN 13321-2: 2007-01 EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 13321-2 December 2012 ICS 35.240.99; 97.120 Supersedes EN 13321-2:2006English Version Open Data Communicat
8、ion in Building Automation, Controls and Building Management - Home and Building Electronic Systems -Part 2: KNXnet/IP Communication Rseau ouvert de communication de donnes pour lautomatisation, la rgulation et la gestion technique du btiment - Systmes lectroniques pour la maison et le btiment - Par
9、tie 2: Communication KNXnet/IP Offene Datenkommunikation fr die Gebudeautomation und Gebudemanagement - Elektrische Systemtechnik fr Heim und Gebude - Teil 2: KNXnet/IP-Kommunikation This European Standard was approved by CEN on 30 September 2012. CEN members are bound to comply with the CEN/CENELEC
10、 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 t
11、o 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 offici
12、al 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, N
13、orway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2012 CEN All rights of exploitation i
14、n any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 13321-2:2012: EEN 13321-2:2012 (E) 2 Contents Page Foreword 4Introduction .51 Scope 72 Normative references 83 Terms and definitions .84 Symbols and abbreviations . 105 Requirements 115.1 Clause 1: Overview . 115.1.
15、1 KNXnet/IP Document Clauses . 115.1.2 Mandatory and optional implementation of IP protocols . 135.1.3 Security considerations . 155.2 Clause 2: Core . 175.2.1 Scope . 175.2.2 KNXnet/IP frames 175.2.3 Host protocol independence . 195.2.4 Discovery and self description 205.2.5 Communication Channels
16、. 215.2.6 General implementation guidelines 245.2.7 Data Packet structures . 285.2.8 IP Networks . 425.2.9 Certification . 475.3 Clause 3: Device Management Specification . 485.3.1 Scope . 485.3.2 KNXnet/IP Device Management . 485.3.3 Implementation rules and guidelines . 605.3.4 Data packet structu
17、res . 625.3.5 Certification . 655.4 Clause 4: Tunnelling . 665.4.1 Scope . 665.4.2 Tunnelling of KNX telegrams . 665.4.3 Configuration and Management 705.4.4 Frame structures. 705.4.5 Certification . 725.5 Clause 5: Routing . 735.5.1 Scope . 735.5.2 KNXnet/IP Routing of KNX telegrams . 735.5.3 Imple
18、mentation rules and guidelines . 805.5.4 Configuration and Management 835.5.5 Data packet structures . 835.5.6 Certification . 855.6 Clause 6: Remote Diagnosis and Configuration . 865.6.1 Scope . 865.6.2 Remote Diagnosis of KNXnet/IP devices . 875.6.3 Configuration and Management 875.6.4 Data packet
19、 structures . 885.6.5 Certification . 93Annex A (normative) List of codes . 94Annex B (informative) Binary examples of KNXnet/IP IP frames 103Annex C (normative) KNXnet/IP Parameter Object . 122DIN EN 13321-2:2013-03 EN 13321-2:2012 (E) 3 Annex D (normative) Common External Messaging Interface (cEMI
20、) . 125Annex E (normative) Coupler Resources . 158Bibliography 170DIN EN 13321-2:2013-03 EN 13321-2:2012 (E) 4 Foreword This document (EN 13321-2:2012) has been prepared by Technical Committee CEN/TC 247 “Building Automation, Controls and Building Management”, the secretariat of which is held by SNV
21、. 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 June 2013, and conflicting national standards shall be withdrawn at the latest by June 2013. Attention is drawn to the possibility that some of th
22、e 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 13321-2:2006. Whereas ENV 13321-2:2000 described the transmission of EIB packets over Ethernet including the fr
23、ame encoding, this document describes the transmission of HBES packets using the Internet Protocol. Details of the HBES packet frames are covered in part 1 of EN 13321, removing the need to explicitly describe the HBES frames in this document. This document is Part 2 of the EN 13321 series of Europe
24、an Standards under the general title Open data communication in building automation, controls and building management Home and building electronic systems, which consists of the following parts: Part 1: Product and system requirements; Part 2: KNXnet/IP communication. According to the CEN/CENELEC In
25、ternal Regulations, the national standards organisations 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,
26、 Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. DIN EN 13321-2:2013-03 EN 13321-2:2012 (E) 5 Introduction This European Standard is intended for the design of new bui
27、ldings and the retrofit of existing buildings in terms of acceptable indoor environment, practical energy conservation and efficiency. This standard defines the integration of KNX protocol implementations within the Internet Protocol (IP) named KNXnet/IP.It defines a standard protocol, which is impl
28、emented within KNX devices, Engineering Tool Software (ETS) and other implementations to support KNX data exchange over IP networks. In fact, KNXnet/IP provides a general framework, which accommodates several specialised “Service Protocols” in a modular and extendible fashion. The KNXnet/IP standard
29、 consists of the following clauses: Clause 1, Overview Clause 2, Core Specification Clause 3, Device Management Clause 4, Tunnelling Clause 5, Routing Clause 6, Remote Diagnosis and Configuration Additional clauses may be added to the KNXnet/IP standard in the future at which time Clause 1 “Overview
30、” as well as Annex A will need to be updated. KNXnet/IP supports different software implementations on top of the protocol. More specifically, these software implementations can be Building Management, Facility Management, Energy Management, or simply Data Base and SCADA (Supervision, Control and Da
31、ta Acquisition) packages. Most of these packages need to be configured for the specific user application. In order to simplify this process and cut costs for engineering, KNXnet/IP provides simple engineering interfaces, namely a description “language” for the underlying KNX system. This may be done
32、 off-line, e.g. generated as an ETS export file, or on-line by a mechanism that self-describes the underlying KNX system (reading data from the system itself). In conjunction with the EIB/KNX-to-BACnet mapping described in EN ISO 16484-5, EIB/KNX installations can very easily be integrated into BACn
33、et system environments. KNXnet/IP supports: on-the-fly change-over between Operational modes (configuration, operation); event driven mechanisms; connections with a delay time greater than tEIB_transfer_timeout(e.g. network connection via satellite). Clause 1, Overview Clause 1 “Overview” provides a
34、 general overview of KNXnet/IP and covers security considerations. Clause 2, Core specification DIN EN 13321-2:2013-03 EN 13321-2:2012 (E) 6 Clause 2 “Core Specification” defines a standard protocol which is implemented within KNXnet/IP devices and Engineering Tool Software to support KNX data excha
35、nge over IP networks. This specific implementation of the protocol over the Internet Protocol (IP) is called KNXnet/IP. This standard addresses: definition of data packets sent over the IP host protocol network for KNXnet/IP communication; discovery and self-description of KNXnet/IP servers; configu
36、ration and establishment of a communication channel between a KNXnet/IP client and a KNXnet/IP server. Clause 3, Device Management Clause 3 “Device Management” defines services for remote configuration and remote management of KNXnet/IP servers. Clause 4, Tunnelling Clause 4 “Tunnelling” defines ser
37、vices for point-to-point exchange of KNX telegrams over an IP network between a KNXnet/IP device acting as a server and a KNXnet/IP Client. This point-to-point exchange may be established by a super ordinate system for building automation or management functions or by an Engineering Tool Software. I
38、t supports all ETS functions for download, test, and analysis of KNX devices on KNX networks connected via KNXnet/IP servers. This includes changes of single KNX device object properties. Tunnelling assumes that a data transmission round-trip between a KNXnet/IP Tunnelling client and KNXnet/IP serve
39、rs takes less than tKNX_transfer_timeouts. Clause 5, Routing Clause 5 “Routing” defines services for a point-to-multipoint exchange of KNX telegrams over an IP network between KNXnet/IP routers and/or KNX/IP devices. Clause 6, Remote Diagnosis and Configuration Clause 6 “Remote Diagnosis and Configu
40、ration” defines services for a point-to-point exchange of KNX telegrams over an IP network between KNXnet/IP routers and/or KNX/IP devices. The services provide means for diagnosing communication settings and for changing these remotely. DIN EN 13321-2:2013-03 EN 13321-2:2012 (E) 7 1 Scope This Euro
41、pean Standard defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX transmission speed)
42、 backbone in KNX installations. Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand building control communication beyond the local KNX control bus, providing: remote configuration; remote operation (including control and annunciation); fast inte
43、rface from LAN to KNX and vice versa; WAN connection between KNX systems (where an installed KNX system is at least one line). A KNXnet/IP system contains at least these elements: one EIB line with up to 64 (255) EIB devices; OR one KNX segment (KNX-TP1, KNX-TP0, KNX-RF, KNX-PL110, KNX-PL132); a KNX
44、-to-IP network connection device (called KNXnet/IP server); and typically additional software for remote functions residing on e.g. a workstation (may be data base application, BACnet Building Management System, browser, etc.). Figure 1 shows a typical scenario where a KNXnet/IP client (e.g. running
45、 ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP servers at a time. For subnetwork, routing server-to-server communication is possible. DIN EN 13321-2:2013-03 EN 13321-2:2012 (E) 8 Figure 1 Device types and conf
46、iguration examples 2 Normative references Not applicable. 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 subnet portion of a network that shares a common address component known as the “subnet address“ Note 1 to entry: Different network prot
47、ocols specify the subnet address in different ways. 3.2 Engineering Tool Software ETS software used to configure KNX devices 3.3 Host Protocol Address Information HPAI structure holding the IP host protocol address information used to address a KNXnet/IP endpoint on another KNXnet/IP device 3.4 communication channel logical connection between a KNXnet/IP client and a KNXnet/IP server (or, in case of routing, between two or more KNXnet/IP servers) Note 1 to entry: A communication channel consists of one or more connections on the definition of the host protocol used for KNXnet/IP. DIN EN
