EN 13321-2-2012 en Open Data Communication in Building Automation Controls and Building Management - Home and Building Electronic Systems - Part 2 KNXnet IP Communication《开放数据通信在楼宇.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationOpen Data Communication in Building Automation, Controls and Building Management Home and Building Electronic SystemsPart 2: KNXnet/IP CommunicationBS EN 13321-2:2012National for

2、ewordThis British Standard is the UK implementation of EN 13321-2:2012. It supersedes BS EN 13321-2:2006 which is withdrawn.The UK participation in its preparation was entrusted to Technical Committee RHE/16, Performance requirements for control systems.A list of organizations represented on this co

3、mmittee 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. The British Standards Institution 2013.Published by BSI Standards Limited 2013 ISBN 978 0 580 77057 9 ICS 35

4、.240.99; 97.120Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 January 2013.Amendments issued since publicationDate Text affectedBRITISH STANDARDBS EN 13321-2

5、:2012EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 13321-2 December 2012 ICS 35.240.99; 97.120 Supersedes EN 13321-2:2006English Version Open Data Communication in Building Automation, Controls and Building Management - Home and Building Electronic Systems -Part 2: KNXnet/IP Communication Rse

6、au ouvert de communication de donnes pour lautomatisation, la rgulation et la gestion technique du btiment - Systmes lectroniques pour la maison et le btiment - Partie 2: Communication KNXnet/IP Offene Datenkommunikation fr die Gebudeautomation und Gebudemanagement - Elektrische Systemtechnik fr Hei

7、m 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 Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alt

8、eration. 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 ma

9、de 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, Esto

10、nia, 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 STAN

11、DARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 13321-2:2012: EBS EN 13321-2:2012EN 13321-2:2012 (E

12、) 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.1 KNXnet/IP Document Clauses . 115.1.2 Mandatory and optional implementation of IP protocols . 135.1.3 Security consid

13、erations . 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 . 215.2.6 General implementation guidelines 245.2.7 Data Packet structures . 285.2.8 IP Networks . 425.2.9 Certificati

14、on . 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 structures . 625.3.5 Certification . 655.4 Clause 4: Tunnelling . 665.4.1 Scope . 665.4.2 Tunnelling of KNX telegrams . 665.4

15、.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 Implementation rules and guidelines . 805.5.4 Configuration and Management 835.5.5 Data packet structures . 835.5.6 Certifi

16、cation . 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 structures . 885.6.5 Certification . 93Annex A (normative) List of codes . 94Annex B (informative) Binary examples of

17、 KNXnet/IP IP frames 103Annex C (normative) KNXnet/IP Parameter Object . 122BS EN 13321-2:2012EN 13321-2:2012 (E) 3 Annex D (normative) Common External Messaging Interface (cEMI) . 125Annex E (normative) Coupler Resources . 158Bibliography 170BS EN 13321-2:2012EN 13321-2:2012 (E) 4 Foreword This doc

18、ument (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. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endo

19、rsement, 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 the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifyin

20、g 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 frame encoding, this document describes the transmission of HBES packets using the Internet Protocol. Details of the HBES packet f

21、rames 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 European Standards under the general title Open data communication in building automation, controls and building management Home and b

22、uilding electronic systems, which consists of the following parts: Part 1: Product and system requirements; Part 2: KNXnet/IP communication. According to the CEN/CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standar

23、d: 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

24、, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 13321-2:2012EN 13321-2:2012 (E) 5 Introduction This European Standard is intended for the design of new buildings and the retrofit of existing buildings in terms of acceptable indoor environment, practical energy conservation and efficiency

25、. This standard defines the integration of KNX protocol implementations within the Internet Protocol (IP) named KNXnet/IP.It defines a standard protocol, which is implemented within KNX devices, Engineering Tool Software (ETS) and other implementations to support KNX data exchange over IP networks.

26、In fact, KNXnet/IP provides a general framework, which accommodates several specialised “Service Protocols” in a modular and extendible fashion. The KNXnet/IP standard consists of the following clauses: Clause 1, Overview Clause 2, Core Specification Clause 3, Device Management Clause 4, Tunnelling

27、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” as well as Annex A will need to be updated. KNXnet/IP supports different software implementations on top of the protocol. More spec

28、ifically, these software implementations can be Building Management, Facility Management, Energy Management, or simply Data Base and SCADA (Supervision, Control and Data Acquisition) packages. Most of these packages need to be configured for the specific user application. In order to simplify this p

29、rocess and cut costs for engineering, KNXnet/IP provides simple engineering interfaces, namely a description “language” for the underlying KNX system. This may be done off-line, e.g. generated as an ETS export file, or on-line by a mechanism that self-describes the underlying KNX system (reading dat

30、a 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 BACnet system environments. KNXnet/IP supports: on-the-fly change-over between Operational modes (configuration, operation); event driven

31、 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 general overview of KNXnet/IP and covers security considerations. Clause 2, Core specification BS EN 13321-2:2012EN 13321-2:2012 (E)

32、 6 Clause 2 “Core Specification” defines a standard protocol which is implemented within KNXnet/IP devices and Engineering Tool Software to support KNX data exchange over IP networks. This specific implementation of the protocol over the Internet Protocol (IP) is called KNXnet/IP. This standard addr

33、esses: definition of data packets sent over the IP host protocol network for KNXnet/IP communication; discovery and self-description of KNXnet/IP servers; configuration and establishment of a communication channel between a KNXnet/IP client and a KNXnet/IP server. Clause 3, Device Management Clause

34、3 “Device Management” defines services for remote configuration and remote management of KNXnet/IP servers. Clause 4, Tunnelling Clause 4 “Tunnelling” defines services 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

35、. 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. It supports all ETS functions for download, test, and analysis of KNX devices on KNX networks connected via KNXnet/IP servers. This include

36、s changes of single KNX device object properties. Tunnelling assumes that a data transmission round-trip between a KNXnet/IP Tunnelling client and KNXnet/IP servers takes less than tKNX_transfer_timeouts. Clause 5, Routing Clause 5 “Routing” defines services for a point-to-multipoint exchange of KNX

37、 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 Configuration” defines services for a point-to-point exchange of KNX telegrams over an IP network between KNXnet/IP routers and/or KNX/IP devices

38、. The services provide means for diagnosing communication settings and for changing these remotely. BS EN 13321-2:2012EN 13321-2:2012 (E) 7 1 Scope This European Standard defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes

39、 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) backbone in KNX installations. Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand build

40、ing control communication beyond the local KNX control bus, providing: remote configuration; remote operation (including control and annunciation); fast interface 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 syst

41、em 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-to-IP network connection device (called KNXnet/IP server); and typically additional software for remote functions residing on e.g. a workstati

42、on (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 ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP serve

43、rs at a time. For subnetwork, routing server-to-server communication is possible. BS EN 13321-2:2012EN 13321-2:2012 (E) 8 Figure 1 Device types and configuration examples 2 Normative references Not applicable. 3 Terms and definitions For the purposes of this document, the following terms and definit

44、ions 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 protocols specify the subnet address in different ways. 3.2 Engineering Tool Software ETS software used to configure KNX devices 3.3 Host Protocol Addre

45、ss 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 server

46、s) Note 1 to entry: A communication channel consists of one or more connections on the definition of the host protocol used for KNXnet/IP. BS EN 13321-2:2012EN 13321-2:2012 (E) 9 3.5 KNX node device implementing a KNX protocol stack and fulfilling the requirements for certification according to the

47、KNX standard 3.6 KNXnet/IP server KNX device with physical access to a KNX network implementing the KNXnet/IP server protocol to communicate with KNXnet/IP clients or other KNXnet/IP servers (in case of routing) on an IP network channel Note 1 to entry: A KNXnet/IP server is by design always also a

48、KNX node. 3.7 KNXnet/IP client application using the KNXnet/IP client protocol to get access to a KNX subnetwork over an IP network channel 3.8 KNXnet/IP device implementation of KNXnet/IP services on a KNX node (KNXnet/IP server) or any other hardware (KNXnet/IP client) 3.9 KNXnet/IP router special

49、 type of KNXnet/IP device that routes KNX protocol packets between KNX sub-networks 3.10 Time To Live TTL maximum number of IP routers a multicast UDP/IP datagram may be routed through Note 1 to entry: Each IP router the datagram passes decrements the TTL by one; the local host adapter also does this. When the TTL has reach