BS EN 50090-4-1-2004 Home and building electronic systems (HBES) - Media independent layers - Application layer for HBES Class 1《家用和建筑物电子系统(HBES) 介质独立层 1类HBES应用层》.pdf

1、BRITISH STANDARD BS EN 50090-4-1:2004 Home and Building Electronic Systems (HBES) Part 4-1: Media independent layers Application layer for HBES Class 1 The European Standard EN 50090-4-1:2004 has the status of a British Standard ICS 35.100.70; 97.120 BS EN 50090-4-1:2004 This British Standard was pu

2、blished under the authority of the Standards Policy and Strategy Committee on 1 April 2004 BSI 1 April 2004 ISBN 0 580 43605 5 National foreword This British Standard is the official English language version of EN 50090-4-1:2004. The UK participation in its preparation was entrusted to Technical Com

3、mittee IST/6, Data communications, which has the responsibility to: A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international or European publications referred to in this document may be fou

4、nd in the BSI Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online. This publication does not purport to include all the necessary provisions of a contract. Users are resp

5、onsible for its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep

6、the UK interests informed; monitor related international and European developments and promulgate them in the UK. Summary of pages This document comprises a front cover, an inside front cover, the EN title page, pages 2 to 80, an inside back cover and a back cover. The BSI copyright notice displayed

7、 in this document indicates when the document was last issued. Amendments issued since publication Amd. No. Date CommentsEUROPEAN STANDARD EN 50090-4-1 NORME EUROPENNE EUROPISCHE NORM February 2004 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electro

8、technique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2004 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 50090-4-1:2004 E ICS 35.100.70; 97.120 Supersedes R205-007:

9、1996English version Home and Building Electronic Systems (HBES) Part 4-1: Media independent layers Application layer for HBES Class 1 Systmes lectroniques pour les foyers domestiques et les btiments (HBES) Partie 4-1: Couches indpendantes des media Couche application pour HBES Classe 1 Elektrische S

10、ystemtechnik fr Heim und Gebude (ESHG) Teil 4-1: Medienunabhngige Schicht Anwendungsschicht fr ESHG Klasse 1 This European Standard was approved by CENELEC on 2003-12-02. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this Euro

11、pean 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 Central Secretariat or to any CENELEC member. This European Standard exists in one official version (Englis

12、h). 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 Secretariat has the same status as the official version. CENELEC members are the national electrotechnical committees of Austria, Belgium, Cyprus, Cz

13、ech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EN 50090-4-1:2004 2 Contents Foreword4 Introduction5 1 S

14、cope .5 2 Normative references .5 3 Terms, definitions and abbreviations .5 3.1 Terms and definitions.5 3.2 Abbreviations .6 4 Services of the application layer 6 4.1 Communication modes 6 4.2 Service primitives of the application layer7 5 Application layer Protocol Data Unit (APDU) .8 6 Application

15、 layer services.11 6.1 Application layer services on multicast communication mode.11 6.2 Application layer services on broadcast communication mode .17 6.3 Application layer services on point-to-point connection-less communication mode36 6.4 Application layer services on point-to-point connection-or

16、iented communication mode .51 6.5 Router-specific application layer services on point-to-point connection-oriented communication mode.79 7 Parameters of application layer80 7.1 Association table80 7.2 Verify flag .80 Figure 1 Interaction of the application layer for services that are not remote conf

17、irmed .7 Figure 2 Interaction of the application layer for services that are remote confirmed .8 Figure 3 APDU (example) 8 Figure 4 Mapping the ASAP to the TSAP (example) .11 Figure 5 Mapping a TSAP to an ASAP 11 Figure 6 Handling requests and responses11 Figure 7 Message flow for the A_Group_Value_

18、Read service 12 Figure 8 A_GroupValue_Read-PDU (example) .12 Figure 9 A_GroupValue_Response-PDU (example), length of ASAP data is more than 6 bit 13 Figure 10 A_GroupValue_Response-PDU (example) length of ASAP data is 6 bit or less.13 Figure 11 Message flow for the A_Group_Value_Write service 15 Fig

19、ure 12 A_GroupValue_Write-PDU (example), length of ASAP data is more than 6 bit16 Figure 13 A_GroupValue_Write-PDU (example), length of ASAP data is 6 bit or less .16 Figure 14 A_IndividualAddress_Write-PDU (example)17 Figure 15 A_IndividualAddress_Read-PDU (example)19 Figure 16 A_IndividualAddress_

20、Response-PDU (example) 19 Figure 17 Message flow for the A_IndividualAddressSerialNumber_Read service.21 Figure 18 A_IndividualAddressSerialNumber_Read-PDU (example)22 Figure 19 A_IndividualAddressSerialNumber_Response-PDU (example)22 Figure 20 A_IndividualAddressSerialNumber_Write-PDU (example)24 F

21、igure 21 A_ServiceInformation_Indication_Write-PDU (example).26 3 EN 50090-4-1:2004 Figure 22 A_DomainAddress_Write-PDU27 Figure 23 A_DomainAddress_Read-PDU (example).29 Figure 24 A_DomainAddress_Response-PDU (example).29 Figure 25 A_DomainAddressSelective_Read-PDU (example)31 Figure 26 A_NetworkPar

22、ameter_Read-PDU (example) 32 Figure 27 A_NetworkParameter_Response-PDU (example).33 Figure 28 A_NetworkParameter_Write-PDU (example) 35 Figure 29 A_PropertyValue_Read-PDU (example) .37 Figure 30 A_PropertyValue_Response-PDU (example)37 Figure 31 A_PropertyValue_Write-PDU (example)40 Figure 32 A_Prop

23、ertyDescription_Read-PDU (example).43 Figure 33 A_PropertyDescription_Response-PDU (example).43 Figure 34 A_DeviceDescriptor_Read-PDU (example).46 Figure 35 A_DeviceDescriptor_Response-PDU (example) .47 Figure 36 Message flow for A_Link_Read Service 48 Figure 37 A_Link_Read-PDU (example)49 Figure 38

24、 A_Link_Response-PDU .49 Figure 39 Message flow for A_Link_Write Service 50 Figure 40 A_Link_Write-PDU .50 Figure 41 A_ADC_Read-PDU (example).52 Figure 42 A_ADC_Response-PDU (example) .52 Figure 43 A_Memory_Read-PDU (example) .54 Figure 44 A_Memory_Response-PDU (example)55 Figure 45 A_Memory_Write-P

25、DU (example)57 Figure 46 A_MemoryBit_Write-PDU 60 Figure 47 A_UserMemory_Read-PDU (example)63 Figure 48 A_UserMemory_Response-PDU .63 Figure 49 A_UserMemory_Write-PDU .66 Figure 50 A_UserMemoryBit_Write-PDU (example)69 Figure 51 A_UserManufacturerInfo_Read-PDU (example) .72 Figure 52 A_UserManufactu

26、rerInfo_Response-PDU.72 Figure 53 A_Restart-PDU (example) .74 Figure 54 A_Authorize_Request-PDU (example) 75 Figure 55 A_Authorize_Response-PDU (example) .76 Figure 56 A_Key_Write-PDU (example) 78 Figure 57 A_Key_Response-PDU (example) 78 Table 1 APCI overview.9 Table 2 Function table for A_MemoryBi

27、t_Write-Services 59 Table 3 Function table for A_UserMemoryBit_Write-Services.68 Table 4 Association table of keys to access levels 77 EN 50090-4-1:2004 4 Foreword This European Standard was prepared by the Technical Committee CENELEC TC 205, Home and Building Electronic Systems (HBES) with the help

28、 of CENELEC co-operation partner Konnex Association (formerly EHBESA). The text of the draft was submitted to the Unique Acceptance Procedure and was approved by CENELEC as EN 50090-4-1 on 2003-12-02. This European Standard supersedes R205-007:1996. CENELEC takes no position concerning the evidence,

29、 validity and scope of patent rights. Konnex Association as Cooperating Partner to CENELEC confirms that to the extent that the standard contains patents and like rights, the Konnex Associations members are willing to negotiate licenses thereof with applicants throughout the world on fair, reasonabl

30、e and non-discriminatory terms and conditions. Konnex Association Tel.: + 32 2 775 85 90 Neerveldstraat, 105 Fax.: + 32 2 675 50 28 Twin House e-mail: infokonnex.org B - 1200 Brussels www.konnex.org Attention is drawn to the possibility that some of the elements of this standard may be the subject o

31、f 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 implemented at national level by publication of an identical national standard or by endorseme

32、nt (dop) 2004-12-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2006-12-01 EN 50090-4-1 is part of the EN 50090 series of European Standards, which will comprise the following parts: Part 1: Standardization structure Part 2: System overview Part 3:

33、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 requirements 5 EN 50090-4-1:2004 Introduction This document specifies the services and protocol

34、 of the application layer for usage in Home and Building Electronic Systems. Some services are targeted to field level communication between devices. Other services are exclusively reserved for management purposes. Some services can be used for both management and run-time communication. 1 Scope Thi

35、s part of the EN 50090 specifies the services and protocol of the application layer for usage in Home and Building Electronic Systems. It provides the services and the interface to the user process as defined in EN 50090-3-2. This procedure is based on the services and the protocol is provided by th

36、e Transport Layer, Network Layer and Data Link Layer as specified in EN 50090-4-2. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the

37、 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 Electronic Systems (HBES) Part 3-2: Aspects of application User process for HBES Class 1 EN 50090-4-2:2004 Home and

38、Building Electronic Systems (HBES) Part 4-2 Media independent layers Transport layer, network layer and general parts of data link layer for HBES Class 1 EN 50090-7-1:2004 Home and Building Electronic Systems (HBES) Part 7-1: System management Management procedures EN 50173-1:2002 Information techno

39、logy - Generic cabling systems 3 Terms, definitions and abbreviations 3.1 Terms and definitions For the purposes of this part the terms and definitions given in EN 50090-1 and the following apply. 3.1.1 application (in the sense of network application) a system with its associated transmission metho

40、d which is supported by telecommunications cabling EN 50173-1:2002, definition 3.1.2 3.1.2 user application software functionality, the control algorithm that runs in one single device 1)At draft stage. EN 50090-4-1:2004 6 3.2 Abbreviations AL Application Layer AD-converter Analog-to-Digital-convert

41、er APDU Application layer Protocol Data Unit APCI Application layer Protocol Control Information ASAP Application layer Service Access Point Acon Application layer confirmation con confirmation CPU Central Processing Unit HBES Class 1 refers to simple control and command HBES Class 2 refers to Class

42、 1 plus simple voice and stable picture transmission HBES Class 3 refers to Class 2 plus complex video transfers ind indication Lcon Local confirmation PDU Protocol Data Unit Rcon Remote confirmation req request res response TL Transport Layer TPDU Transport layer Protocol Data Unit TSAP Transport l

43、ayer Service Access Point USERMSG User Message 4 Services of the application layer 4.1 Communication modes The application layer shall provide a large variety of application services to the application process. Application processes in different devices interoperate by using services of application

44、layer over communication modes. According to transport layer, the following different types of communication modes shall exist: a) point-to-multipoint, connection-less (multicast); b) point-to-domain, connection-less (broadcast); c) point-to-all-points, connection-less (system broadcast); d) point-t

45、o-point, connection-less; e) point-to-point, connection-oriented. The application layer services that are offered shall depend on the communication mode. An application layer service shall not be applied on a communication mode for which it is not specified. Some services may be used on the point-to

46、-point connection-oriented, as well as the point-to-point connection-less communication mode, although application layer services shall always be mapped to transport layer services depending on the type of the communication mode. 7 EN 50090-4-1:2004 4.2 Service primitives of the application layer Ea

47、ch specified application layer service shall be invoked by the transport layer primitives request (req), indication (ind) and confirmation (con). For a remote confirmed service, the remote device shall use the same transport layer primitives to respond to the service. The transport layer confirmatio

48、n primitive shall only be a confirmation from the transport layer instance and shall include all data from the request plus the state which indicates whether the service was sent successfully or not. The application layer shall map the transport layer confirmation primitive to a local application la

49、yer confirmation (Lcon). Application Layer Local User of AL Remote/Response User of AL T_Service.req (WRITE_PDU) T_Service.ind (WRITE_PDU) T_Service.con (WRITE_PDU) Application Process A_Service.Lcon A_Service.req A_Service.ind Transport LayerFigure 1 Interaction of the application layer for services that are not rem