oSIST prEN 50090-4-4:2024

Home and Building Electronic Systems (HBES) - Part 4-4: HBES IoT Point API

This document lays down the requirements for the HBES Point API extension to the EN 50090 series, allowing vendor independent communication between smart home and building devices on IPv6 networks.

Systèmes électroniques pour les foyers domestiques et les bâtiments (HBES) - Partie 4-4: API de Point IdO HBES

Le présent document définit les exigences relatives à l'extension de l'API de Point HBES à la série EN 50090 pour permettre une communication indépendante du fournisseur entre des dispositifs de maison intelligente et de bâtiment sur des réseaux IPv6.

Stanovanjski in stavbni elektronski sistemi (HBES) - 4-4. del: HBES IoT Point API

General Information

• Status: Not Published
• Public Enquiry End Date: 30-Dec-2024
• ICS: 35.240.67 - IT applications in building and construction industry
• ICS: 97.120 - Automatic controls for household use
• Technical Committee: ELI - Electrical and communication installations
• Current Stage: 4020 - Public enquire (PE) (Adopted Project)
• Start Date: 07-Nov-2024
• Due Date: 27-Mar-2025
• Ref Project: prEN 50090-4-4 - Home and Building Electronic Systems (HBES) - Part 4-4: HBES IoT Point API

Standards Content (Sample)

SLOVENSKI STANDARD
01-december-2024
Stanovanjski in stavbni elektronski sistemi (HBES) - 4-4. del: HBES IoT Point API
Home and Building Electronic Systems (HBES) - Part 4-4: HBES IoT Point API
Systèmes électroniques pour les foyers domestiques et les bâtiments (HBES) - Partie 4-
4: API de Point IdO HBES
Ta slovenski standard je istoveten z: prEN 50090-4-4
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
97.120 Avtomatske krmilne naprave Automatic controls for
za dom household use
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD DRAFT
NORME EUROPÉENNE
EUROPÄISCHE NORM
November 2024
ICS 35.240.67; 97.120 -
English Version
Home and Building Electronic Systems (HBES) - Part 4-4: HBES
IoT Point API
Systèmes électroniques pour les foyers domestiques et les To be completed
bâtiments (HBES) - Partie 4-4: API de Point IdO HBES
This draft European Standard is submitted to CENELEC members for enquiry.
Deadline for CENELEC: 2025-01-24.

It has been drawn up by CLC/TC 205.

If this draft becomes a European Standard, 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.

This draft European Standard was established by CENELEC in three official versions (English, French, German).
A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to
the CEN-CENELEC Management Centre has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to
provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without notice and
shall not be referred to as a European Standard.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Project: 76630 Ref. No. prEN 50090-4-4 E

Contents Page
European foreword . 3
1 Scope. 4
2 Normative references . 4
3 Terms, definitions and abbreviations . 5
3.1 Terms and definitions . 5
3.2 Abbreviations . 10
4 HBES IoT Point API . 12
4.1 Introduction . 12
4.2 System Entities . 13
4.3 Device Model . 14
4.4 Conventions used in this document . 16
5 Point API Standard . 16
5.1 Application Protocol . 16
5.2 Overview . 16
5.3 System Design . 19
5.4 Device Bootstrapping and Configuration . 22
5.5 Resource Model . 26
5.6 Runtime Interworking . 76
6 Security . 101
6.1 Introduction . 101
6.2 Device Identity Enrollment . 102
6.3 Device Identity Certificates . 106
6.4 Certificate Validation . 108
6.5 Device Access Control . 109
6.6 OSCORE Application Layer Security . 116
7 Software Update . 137
7.1 Introduction . 137
7.2 Software Update Client Resource (swu) . 138
7.3 Software Update Modes . 143
8 Profiles . 152
8.1 HBES IoT Point API Device . 152
8.2 CBOR Encoding . 157
9 Examples . 159
9.1 DEVICE POINT LIST EXAMPLES . 159
9.2 DEVICE CONFIGURATION EXAMPLE . 162
9.3 DATA ENCRYPTION/DECRYPTION EXAMPLE . 170
10 HBES IoT Router . 174
10.1 Introduction . 174
10.2 Conformance . 174
10.3 Number Format . 174
10.4 Uniform Resource Identifiers . 174
10.5 Uniform Resource Name . 174
10.6 HBES IoT Router Specification . 175
10.7 Runtime Interworking . 184
10.8 Profiles . 187
10.9 Security . 189
10.10 Examples . 189
Bibliography . 192

European foreword
This document (prEN 50090-4-4:2024) has been prepared by CLC/TC 205 “Home and Building
Electronic Systems (HBES)”.
This document is currently submitted to the Enquiry.
The following dates are proposed:
• latest date by which the existence of this (doa) dav + 6 months
document has to be announced at national
level
• latest date by which this document has to be (dop) dav + 12 months
implemented at national level by publication of
an identical national standard or by
endorsement
• latest date by which the national standards (dow) dav + 36 months
conflicting with this document have to be (to be confirmed or
withdrawn modified when voting)

1 Scope
This document lays down the requirements for the HBES Point API extension to the EN 50090 series,
allowing vendor independent communication between smart home and building devices on IPv6
networks.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this 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:2011, Home and Building Electronic Systems (HBES) — Part 1 Standardization structure
EN 50090-3-3, Home and Building Electronic Systems (HBES) — Part 3-3: Aspects of application —
HBES Interworking model and common HBES data types
EN 50090-4-1, Home and Building Electronic Systems (HBES) — Part 4-1: Media independent layers
— Application layer for HBES Class 1
EN 50090-4-2, Home and 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, Home and Building Electronic Systems (HBES) — Part 7-1: System management —
Management procedures
EN ISO 22510, Open data communication in building automation, controls and building management
— Home and building electronic systems — KNXnet/IP communication (ISO 22510)
RFC 7252, The Constrained Application Protocol (CoAP)
RFC 8949, Concise Binary Object Representation (CBOR)
RFC 6838, Media Type Specifications and Registration Procedures
RFC 6690, Constrained RESTful Environments (CoRE) Link Fomat
RFC 1035, Domain names – Implementation and specification
RFC 8323, CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
RFC 4291, IP Version 6 Addressing Architecture
RFC 6763, DNS-Based Service Discovery
RFC 8766, Discovery Proxy for Multicast DNS-Based Service Discovery
RFC 6762, Muticast DNS
RFC 3596, DNS Extensions to Support IP Version 6
RFC 8613, Object Security for Constrained RESTful Environments (OSCORE)
RFC 7959, Block-Wise Transfers in the Constrained Application Protocol (CoAP)
RFC 9175, Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing
RFC 8516, “Too Many Requests” Response Code for the Constrained Application Protocol
RFC 3306, Unicast-Prefix-based IPv6 Multicast Addresses
RFC 3307, Allocation Guidelines for IPv6 Multicast Addresses
RFC 6282, Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks
RFC 9148, EST-coaps: Enrollment over Secure Transport with the Secure Constrained Applicatoin
Protocol
RFC 8995, Bootstrapping Remote Secure Key Infrastructure (BRSKI)
RFC 5967, The application/pkcs10 Media Type
RFC 5273, Certificate Management over CMS (CMC): Transport Protocols
RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL)
Profile
RFC 2818, HTTP Over TLS
RFC 7251, AES-CCM Elliptic Curve Cryptography (ECC) Cipher Suites for TLS
RFC 8392, CBOR Web Token (CWT)
RFC 3986, Uniform Resource Identifier (URI): Generic Syntax
RFC 8747, Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
RFC 8152, CBOR Object Signing and Encryption (COSE)
RFC 3339, Date and Time on the Internet: Timestamps
RFC 6335, Internet Assigned Numbers Authority (IANA) Procedures for the Managmenet of the Service
Name and Transport Protocol Port Number Registry
RFC 4492, Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)
RFC 5869, HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in EN 50090-1:2011 and the
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
3.1.1
Actuator
Point performing an actuation in HBES IoT (executed by a specific procedure, with an expected result)
that changes an Installation state during Runtime
3.1.2
Advanced Message Queuing Protocol
open standard application layer protocol for message-oriented middleware with defining features such
as message orientation, queuing, routing (in
...