1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationHome and Building ElectronicSystems (HBES) Part 3-3: Aspects of application HBES Interworkingmodel and common HBES data typesBS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCH
2、ANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSINational forewordThis British Standard is the UK implementation of EN 50090-3-3:2009.The UK participation in its preparation was entrusted to Technical CommitteeIST/6, Data communications.A list of organizations represented on this co
3、mmittee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions of acontract. Users are responsible for its correct application. BSI 2010ISBN 978 0 580 64399 6ICS 97.120Compliance with a British Standard cannot confer immunity fromlegal ob
4、ligations.This British Standard was published under the authority of the StandardsPolicy and Strategy Committee on 31 January 2010Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDBS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53,
5、 Uncontrolled Copy, (c) BSIEUROPEAN STANDARD EN 50090-3-3 NORME EUROPENNE EUROPISCHE NORM May 2009 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: Avenue Marnix 17, B
6、 - 1000 Brussels 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 50090-3-3:2009 E ICS 97.120 English version Home and Building Electronic Systems (HBES) - Part 3-3: Aspects of application - HBES Interworking model and common
7、HBES data types Systmes lectroniques pour les foyers domestiques et les btiments (HBES) - Partie 3-3: Aspects de lapplication - Modle dinter-fonctionnement des HBES et types de donnes communes Elektrische Systemtechnik fr Heim und Gebude (ESHG) - Teil 3-3: Anwendungsaspekte - ESHG-Interworking-Model
8、l und bliche ESHG-Datenformate This European Standard was approved by CENELEC on 2008-12-01. 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-
9、date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member. This European Standard exists in two official versions (English, French). A version in any other language made by translation under the res
10、ponsibility of a CENELEC member into its own language and notified to the Central 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, Germa
11、ny, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. BS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53,
12、Uncontrolled Copy, (c) BSIEN 50090-3-3:2009 - 2 - Foreword This European Standard was prepared by the Technical Committee CENELEC TC 205, Home and Building Electronic Systems (HBES), joined by the co-operating partner KNX Association. The text of the draft was submitted to the Unique Acceptance Proc
13、edure and was approved by CENELEC as EN 50090-3-3 on 2008-12-01. CENELEC takes no position concerning the evidence, validity and scope of patent rights. KNX Association as Cooperating Partner to CENELEC confirms that to the extent that the standard contains patents and like rights, the KNX Associati
14、ons members are willing to negotiate licenses thereof with applicants throughout the world on fair, reasonable and non-discriminatory terms and conditions. KNX Association Tel.: + 32 2 775 85 90 De Kleetlaan 5, bus 11 Fax.: + 32 2 675 50 28 B - 1831 Diegem e-mail: infoknx.org www.knx.org Attention i
15、s drawn to the possibility that some of the elements of this standard may be the subject of patent rights other than those identified above. CENELEC shall not be held responsible for identifying any or all such patent rights. The following dates were fixed: latest date by which the EN has to be impl
16、emented at national level by publication of an identical national standard or by endorsement (dop) 2009-12-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2011-12-01 EN 50090-3-3 is part of the EN 50090 series of European Standards, which will compri
17、se the following parts: Part 1: Standardization structure Part 2: System overview Part 3: Aspects of application Part 4: Media independent layers Part 5: Media and media dependent layers Part 6: Interfaces Part 7: System management Part 8: Conformity assessment of products Part 9: Installation requi
18、rements _BS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSI- 3 - EN 50090-3-3:2009 Contents Introduction 5 1 Scope 6 2 Normative references . 6 3 Terms, definitions and abbreviations 7 3.1 Terms and definitions . 7 3.2 Abbreviation
19、s 7 4 HBES Interworking model 7 4.1 Principles of HBES Interworking 11 4.2 Busload 12 4.3 Datapoint Type error handling 13 4.4 Interpretability of data and data integrity 15 5 General Functional Block Design and Implementation Rules 15 5.1 Introduction . 15 5.2 Describe the Application Domain . 15 5
20、.3 Describe the Application 15 5.4 Describe the Functional Block 19 5.5 Describing the Datapoint Types . 29 Annex A (informative) Common HBES data types 38 Figures Figure 1 The HBES Interworking Model An Application Domain can contain one or more Applications . 7 Figure 2 The HBES Interworking Model
21、 An Application Model may contain one or more Functional Blocks . 8 Figure 3 Standard representation for Functional Blocks 8 Figure 4 Datapoints indicated in Functional Blocks 9 Figure 5 Functional Blocks grouped in devices and linked 9 Figure 6 Functional Block with 5 Datapoints 10 Figure 7 The inf
22、ormation contained in a Datapoint Type definition 10 Figure 8 Example of an Interworking specification . 11 Figure 9 Functional Block diagram (Example) . 20 Figure 10 Table listing separate datapoints of a functional block 21 Figure 11 Specification form for Inputs and Outputs 22 Figure 12 Specifica
23、tion form for Parameters and Diagnostic Data 29 Figure 13 Example of multi-state datapoint 32 Figure 14 Datapoint Type specification form 34 Figure A.1 Structure of Datapoint Types 38 Figure A.2 December 12, 2006 encoded according DPT_Date in an A_GroupValue_Write-frame (example on TP1) 39 BS EN 500
24、90-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSIEN 50090-3-3:2009 - 4 - Tables Table 1 Use of heart-beat . 12 Table 2 Authorisation level names . 27 Table 3 Datatypes notation styles 35 Table A.1 Compatibility rules 67 BS EN 50090-3-3:200
25、9Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSI- 5 - EN 50090-3-3:2009 Introduction Interworking between devices signifies that these products send and receive datagrams and are able to properly understand and react on them. This ability is provid
26、ed without additional equipment (like translators or gateways). NOTE Media couplers are needed if different media are used in an installation. The market requires Interworking for a multi-vendor approach, this is, products from different manufacturers can interwork in a certain application segment o
27、r domain as well as across different applications (cross discipline Interworking). Such an Interworking is only possible if a set of requirements is complied with as defined in an Interworking model. For this, Functional Blocks need to be defined, which in turn specify Datapoints and the communicati
28、on mechanisms to be used. Such a set of requirements is referred to as “Application Interworking Specifications“ (AIS). AIS allow Interworking independent of the implementation by a manufacturer. Besides the advantages for the user (multi-vendor offer) Interworking also allows a broad OEM market and
29、 easy market access for niche-products providers. Furthermore Interworking allows the establishment of a common market infrastructure (i.e. common configuration tool, training, etc.) BS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) B
30、SIEN 50090-3-3:2009 - 6 - 1 Scope This European Standard gives general guidelines and recommendations to ensure interworking between HBES devices made by different manufacturers. It also contains design guidelines for the design of Functional Blocks and new datapoint types, the building blocks of HB
31、ES interworking. In this way, the standard can be used as a basis to design application specifications relative to an Application Domain. If designed and supported by a large group of manufacturers, such application specifications will ensure to end customers a high degree of interoperability betwee
32、n products based on the HBES Communication System of different manufacturers. This European Standard is used as a product family standard. It is not intended to be used as a stand-alone standard. 2 Normative references The following referenced documents are indispensable for the application of this
33、document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 50090-1 1)Home and Building Electronic Systems (HBES) Part 1: Standardization structure EN 50090-3-2:2004 Home and Building Ele
34、ctronic Systems (HBES) Part 3-2: Aspects of application User process for HBES Class 1 EN 50090-4-1:2004 Home and Building Electronic Systems (HBES) Part 4-1: Media independent layers Application Layer for HBES Class 1 EN 50090-4-2: 2004 Home and Building Electronic Systems (HBES) Part 4-2: Media ind
35、ependent layers Transport layer, network layer and general parts of data link layer for HBES Class 1 1)Under consideration. BS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSI- 7 - EN 50090-3-3:2009 3 Terms, definitions and abbrevia
36、tions 3.1 Terms and definitions For the purposes of this document, the definitions given in EN 50090-1 apply. 3.2 Abbreviations AIS Application Interworking Specifications COV Change of Value DMA Direct Memory Access DP Data Point DPT Datapoint type DPT ID Datapoint type identifier FB Functional Blo
37、ck GO Group Object IO Interface Object lsb least significant bit M Mandatory msb most significant bit MSB Most Significant Byte NA Not Applicable O Optional PDT Property Data Type PID Property Identifier OEM Original Equipment Manufacturer 4 HBES Interworking model HBES Interworking can be applied i
38、n many application domains. Each Application Domain can encompass one or more Applications. Application Application Domain Figure 1 - The HBES Interworking Model An Application Domain can contain one or more Applications The Application Modelling or the process of analysing, deciding on the solution
39、 and specifying the model for such an Application needs to be agreed upon amongst manufacturers in Application Specification Groups. BS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSIEN 50090-3-3:2009 - 8 - Applications shall not b
40、e defined in terms of products, but analysed and split up into Functional Blocks, which communicate with one another. The term Distributed Application indicates this approach: the total functionality of an Application is spread over a number of Functional Blocks implemented in various devices in the
41、 network. A Functional Block transports its data over the bus via one or more Datapoints (these are Inputs, Outputs, Parameters and Diagnostic Data). A Functional Block thus describes the standard specification of the chosen solution for one given task of an application. These Datapoints and their d
42、escribed functionality are implemented by the product developer. The following picture shows the Interworking model as defined so far. Functional BlockApplication ModelApplication DomainFigure 2 - The HBES Interworking Model An Application Model may contain one or more Functional Blocks The Function
43、al Blocks shall be described as objects; this is a set of Datapoints and a well-defined behaviour. The standard graphical representation for a Functional Block shall be the following: Input(s) Functional Block name Output(s) Name Input I1 DPT I1 I1 O1 DPT O1 Name Output O1 Name Input I2 DPT I2 I2 Pa
44、rameter(s) Diagnostic Data Name Parameter P1 DPT P1 P1 DD1 DPT DD1 Figure 3 - Standard representation for Functional Blocks BS EN 50090-3-3:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 08/04/2010 02:53, Uncontrolled Copy, (c) BSI- 9 - EN 50090-3-3:2009 The Datapoints that are typically
45、 Inputs shall be put on the left, the Outputs on the right, the Parameters on the left below the Inputs and the Diagnostic Data on the right below the Outputs. For each Datapoint, a name shall be given, an indication of its Datapoint Type and an abbreviation. Name Input I1 DPT I1 - I1 Name of the Da
46、tapoint Indication of the Datapoint type to be used. Abbreviation for the Datapoint Figure 4 - Datapoints indicated in Functional Blocks A manufacturer may group one or more of these Functional Blocks, of the same or of different Applications, to build a device. Input(s) Functional BlockBOutput(s)cc
47、c DPT I1- I1 O1DPT O1- O1I2DPT I2- I2Parameter(s)P1DPT P1- P1Functional BlockAOutput(s)O1DPT O1- O1Parameter(s)P1DPT P1- P1P2DPT P2- P2Input(s) Functional BlockCOutput(s)I1DPT I1- O1DPT O1- O1O2DPT O2- O2Parameter(s)P1DPT P1- P1P2DPT P2- P2Device 1Device 2Figure 5 - Functional Blocks grouped in devi
48、ces and linked For every Functional Block its behaviour shall be specified. This fixes its handling of its Datapoints and physical inputs and outputs (e.g. a state machine of a dimming actuator). A Datapoint is any interface over which data in the Functional Block can be set or received and/or trans
49、mitted (for its run-time operation). Every Functional Block may have one or more such Datapoints. From the communication point of view, 4 classes of Datapoints can be distinguished (for more information see 5.3.3): NOTE These classes of Datapoints are defined in EN 50090-4-2, EN 50090-4-1 and EN 50090-3-2: Group Object Datapoint Interface Object Property Datapoint Polling Va
