EN 50090-5-3:2016

SLOVENSKI STANDARD
01-marec-2016
1DGRPHãþD
SIST EN 50090-5-3:2007
Stanovanjski in stavbni elektronski sistemi (HBES) - 5-3. del: Mediji in nivoji,
odvisni od medijev - Radijska frekvenca za HBES razreda 1
Home and Building Electronic Systems (HBES) - Part 5-3: Media and media dependent
layers - Radio Frequency for HBES Class 1
Elektrische Systemtechnik für Heim und Gebäude (ESHG) - Teil 5-3: Medien und
medienabhängige Schichten - Signalübertragung über Funk für ESHG Klasse 1
Systèmes électroniques pour les foyers domestiques et les bâtiments (HBES) - Partie 5-
3: Médias et couches dépendantes des médias - Radio Fréquence pour HBES Classe 1
Ta slovenski standard je istoveten z: EN 50090-5-3:2016
ICS:
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 EN 50090-5-3

NORME EUROPÉENNE
EUROPÄISCHE NORM
January 2016
ICS 97.120 Supersedes EN 50090-5-3:2006
English Version
Home and Building Electronic Systems (HBES) - Part 5-3: Media
and media dependent layers - Radio Frequency for HBES Class
Systèmes électroniques pour les foyers domestiques et les Elektrische Systemtechnik für Heim und Gebäude (ESHG) -
bâtiments (HBES) - Partie 5-3: Médias et couches Teil 5-3: Medien und medienabhängige Schichten -
dépendantes des médias - Radio Fréquence pour HBES Signalübertragung über Funk für ESHG Klasse 1
Classe 1
This European Standard was approved by CENELEC on 2015-11-02. 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-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC 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 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2016 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 50090-5-3:2016 E
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms, definitions and abbreviations . 5
3.1 Terms and definitions . 5
3.2 Abbreviations . 6
4 General . 6
5 HBES RF Physical Layer . 7
5.1 Physical Layer for HBES RF Ready . 7
5.1.1 Signalling for HBES RF Ready . 7
5.1.2 Telegram structure for RF Ready . 8
5.1.3 Medium access RF Ready . 8
5.2 Physical Layer for HBES RF Multi . 9
5.2.1 General requirements (HBES RF Multi). 9
5.2.2 Physical Layer type RF Multi . 11
5.2.3 Telegram structure for HBES RF Multi systems . 13
6 HBES RF Data Link Layer . 13
6.1 HBES RF Data Link Layer for all HBES RF devices . 13
6.1.1 Differences to existing (bidirectional) HBES EN 50090 protocol . 13
6.1.2 Data Link Layer Frame . 15
6.1.3 Use of the HBES Ctrl Field . 18
6.1.4 Data Link Layer protocol . 18
6.1.5 Data Link Layer services . 19
6.2 HBES RF Data Link Layer for HBES RF Ready . 21
6.2.1 Data Link Layer protocol . 21
6.2.2 The Layer-2 of an RF Retransmitter . 21
6.3 HBES RF Data Link Layer specific to HBES RF Multi systems . 22
6.3.1 Medium access RF Multi . 22
6.3.2 Frame format . 24
6.3.3 RF Multi-channel usage . 24
6.3.4 Fast Acknowledgment . 30
6.3.5 Data Link Layer protocol . 35
6.3.6 Runtime with an RF Repeater and Fast Ack requested . 38
6.3.7 InterFrame delays for RF Repeaters . 38
6.3.8 Repetition counter . 39
6.3.9 Media Coupler . 39
6.4 Semi-directional devices and bidirectional mode . 39
7 Compatibility between HBES Ready and HBES RF Multi. 40
7.1 Communication between HBES RF 1.1 and HBES RF1 Multi devices . 40
7.2 Communication between HBES RF Ready and HBES RF Multi devices . 41
7.3 Communication between HBES RF Multi and HBES RF Multi devices . 41
Bibliography . 42

European foreword
This document (EN 50090-5-3:2016) has been prepared by CLC/TC 205 "Home and Building Electronic
Systems (HBES)".
The following dates are fixed:
(dop) 2016-11-02
• latest date by which this document has
to be implemented at national level by
publication of an identical national
standard or by endorsement
(dow) 2018-11-02
• latest date by which the national
standards conflicting with this
document have to be withdrawn
This document supersedes EN 50090-5-3:2006.

EN 50090-5-3:2006:
- the difference between this version and the previous version of Part 5-3 is that the previous
version contained only a description of the HBES RF Ready solution, where the current version
was extended with the upward compatible HBES RF Multi solution.

Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent
rights.
Introduction
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 Association's members are willing to negotiate licenses thereof
with applicants throughout the world on fair, reasonable and non-discriminatory terms and conditions.

KNX Association
De Kleetlaan 5, Bus 11
B-1831 Brussels-Diegem
Tel:    +32 (0)2 775 86 44
Mob:   +32 (0) 476 21 56 58
Fax:   +32 (0)2 675 50 28
e-mail: info@knx.org
www.knx.org
Attention is drawn to the possibility that some of the elements of this document 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.
CEN and CENELEC maintain online lists of patents relevant to their standards. Users are encouraged to
consult the lists for the most up to date information concerning patents
(ftp://ftp.cencenelec.eu/EN/IPR/Patents/IPRdeclaration.pdf).

1 Scope
This European Standard defines the mandatory and optional requirements for the medium specific
Physical and Data Link Layer of HBES Radio Frequency.
Data Link Layer interfaces and general definitions that are medium independent are given in
EN 50090-4-1.
This European standard defines the requirements for HBES RF Ready and HBES RF Multi devices.
HBES RF Ready is a single RF channel system. HBES RF Multi is an RF multichannel evolution of HBES
RF Ready system with 2 additional RF channels for fast reaction time products and 2 RF channels for
slow reaction time products.
HBES RF Multi, specified below provides the following features:
- more reliability in Frame transmissions in presence of interferers.
- more efficiency when more HBES RF products are installed at the same location.
- mixing of permanent and non-permanent receiving products.
- mixing of fast and slow reaction time devices.
- Listen Before Talk.
Fast RF channels are mainly intended to be used with human controlled applications like for example
lights, shutters… Slow RF channels are mainly intended to be used with non-permanent receivers for
automatic applications like sensors (smoke, temperature, wind, etc.), heating control, etc.
Compatibility issues with products in compliance with the former HBES RF specification (HBES RF 1.1)
and the new versions are considered in Clause 7 at the end of this document.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. 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-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
ETSI EN 300 220 (all parts), Electromagnetic compatibility and Radio spectrum Matters (ERM); Short
Range Devices (SRD); Radio equipment to be used in the 25 MHz to 1 000 MHz frequency range with
power levels ranging up to 500 mW
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.
3.1.1
RF channel hopping
action to change the RF channel during or after transmitting a frame
3.1.2
budget link
budget link of a device is the difference expressed in dB between the max radiated power and the
radiated sensitivity. The higher the budget link, the better the radio range is
3.2 Abbreviations
AFA Adaptive Frequency Agility
BER Bit Error Rate
D.C. Duty Cycle
DLL Data Link Layer
EOA End of Ack
ERP Effective Radiated Power
F1 F1 RF channel with a preamble of 15 ms in the transmitted Frame
F1r F1 RF channel with a preamble of 4,8 ms in the transmitted Frame
F1sh F1 RF channel with a preamble of 1ms in the transmitted Frame
FSK Frequency Shift Keying
F One of F1, F2 or F3 RF channels
x
GFSK Gaussian Frequency Shift Keying
LBT Listen Before Talk
NPRM Non-Permanent Reception Mode
PhL Physical Layer
PRM Permanent Reception Mode
Rx Receiver
RSSI Received Signal Strength Indication
SN HBES Serial Number
S One of S1 or S2 RF channels
x
TRx Transceiver
Tx Transmitter
4 General
As described in the scope, this European standard defines the RF Physical Layer requirements for:
- HBES RF Ready;
- HBES RF Multi.
For HBES certification in Europe, the products shall be in compliance with at least one of the following
clauses.
Table 1 — Guide for compliance
System Physical Layer Data Link Layer
HBES RF Ready 5.1 6.1 and 6.2
HBES RF Multi 5.2 6.1 and 6.3
5 HBES RF Physical Layer
5.1 Physical Layer for HBES RF Ready
5.1.1 Signalling for HBES RF Ready
Table 2 — General requirements for Physical Layer Type HBES RF Ready
Characteristic Value or applicable standard
Tx centre frequency f = 868,300 MHz
c
Bandwidth 600 kHz
a
Max. Tx frequency tolerance ± 25 ppm
Tx duty cycle max 1 %
Tx modulation type FSK
FSK deviation f = ± 48 kHz to ± 80 kHz
DEV
typically 60 kHz
Tx chip rate 32 768 chips per second
Maximum Tx chip rate tolerance ± 1,5 %
Maximum Tx jitter per transition ± 5 µs
Tx ERP Typical : 0 dBm
Min : -3 dBm
Max: +14dBm
b
Rx blocking performance according to ETSI EN 300 220-1, category 2 receivers
Rx centre frequency f = 868,300 MHz
c
a, b
Rx frequency tolerance ± 25 ppm HBES Tx to HBES Rx
a, b
± 60 ppm Metering Tx to HBES Rx
b
Minimal Rx chip rate tolerance ±2,0 %
b
Rx radiated sensitivity typical: -95 dBm
b
minimal: -80 dBm
c
Minimal operating temperature 0°C to 45°C
range
a
This frequency tolerance includes tolerances due to temperature variations within the operating
temperature range and tolerances due to crystal aging.
b -4
At Bit Error Rate (BER) 10 in optimum antenna direction.
c
HBES Physical Layer parameters shall be met for the entire product temperature range declared
by the manufacturer. (e.g. : -10°C to 70°C for outdoor usage).
A link budget of 100 dB is recommended.
5.1.2 Telegram structure for RF Ready
Table 3 — HBES Ready systems Telegrams definition
Characteristics Value Notes
Data encoding Manchester chip "0" means f (= f - f )
LO C DEV
chip "1" means f (= f + f )
HI C DEV
bit "0" is coded as f to f transition, chip sequence "10"
HI LO
bit "1" is coded as f to f transition, chip sequence "01"
LO HI
Preheader consists of Preamble, see below
Manchester violation,
Sync word
Preamble 79x chip sequence "01" learning sequence for Rx, number of preamble chips is
sent by Tx not checked by Rx (~4.8 ms)
Manchester chip sequence "000111" necessary for capture effect
violation
Sync word chip sequence useful for synchronization on chip rate
"011010010110"
Postamble 2 chips to 8 chips software reasons, mandatory for all Tx, number of
postamble not checked by Rx.
Capture effect optional Preheader allows it; Rx may use it
5.1.3 Medium access RF Ready
5.1.3.1 Definition and use
Medium access control shall serve for prevention of collisions on the RF medium. For two reasons
medium access cannot be completely controlled on RF.
1) Unidirectional senders access the medium at non-predictable times.
2) Non HBES RF devices access the medium at non-predictable times.
Bidirectional devices shall be able to sense whether the medium is free before they transmit. The inter-
Frame time shall be the time interval during which a bidirectional device shall wait for a free medium
(regardless of whether it is addressed by a preceding Frame or not). If no preamble is detected during
this interFrame time the device may start sending.
If a Frame is received while the Physical Layer gets a request to send, the interFrame time shall start
after the Frame reception is completed, this is after the last CRC is received. The same shall apply for
sending: if the Physical Layer gets a send request while it is sending, the interFrame time shall start when
the last CRC is transmitted.
NOTE RF supports no collision avoidance; therefore the transmission priorities are not coded in the Frame.
5.1.3.2 Medium Access Time
Table 4 – Medium access times
Type of frame InterFrame time Random time Total medium access Time
[Tint] [Trd] [Tma]
REPEATED Ready frame 5 ms 0 ms ≤ Trd < 10 ms 5 ms ≤ Tma < 15 ms
Ready frame 15 ms 0 ms ≤ Trd < 15 ms 15 ms ≤ Tma < 30 ms
Bidirectional devices
Ready frame 150 ms 0 ms ≤ Trd < 10 ms 150 ms ≤ Tma < 160 ms
Unidirectional devices
The assumed typical ‘blind time’ for devices is 1 ms.
The step for the random time shall be 1 ms.
5.2 Physical Layer for HBES RF Multi
5.2.1 General requirements (HBES RF Multi)
The RF channels used in the HBES RF Multi shall be composed of the following 3 + 2 RF channels.
Table 5 – RF channels of the HBES RF Multi Physical Layer
signalling speed preamble length
RF channel name Abbreviation encoding
kbps ms
Primary fast RF channel F1 16,384 Manchester 15
Second fast RF channel F2 16,384 Manchester 15
Third fast RF channel F3 16,384 Manchester 15
Primary slow RF channel S1 8,192 Manchester 500
Second slow RF channel S2 8,192 Manchester 500

The RF channels shall be divided in two categories.
1) The first category shall contain RF channels for “fast” RF Telegrams. The fast Telegrams shall
be composed of a short 15 ms wake-up at 16,384 kbps signalling speed.
2) The second category contains RF channels for “slow” RF Telegrams. The slow Telegrams are
composed of a long 500 ms wake-up at 8,192 kbps signalling speed.
The two categories of RF channels define explicitly two application domains.
EXAMPLE 1 Non-permanent receivers: smoke sensors, heating control.
EXAMPLE 2 Permanent receivers: all devices concerning human interaction
The first three Fast RF channels are primarily used in application for fast permanent and non-permanent
receivers and the last two RF channels are primarily used for slow non-permanent Rx devices. The
receiver reception capability determines the preamble length.
Devices from both categories can coexist independently without link or with links done by specific mains
powered products receiving all the 5 RF channels.
Fast Telegrams are Telegrams transmitted on any of the Fast RF channels; slow Telegrams are
Telegrams transmitted on a Slow RF channel.
Typically NPRM devices using slow Telegrams can only receive RF Telegrams with long wake-up. This
enables the NPRM devices to stay in low power mode most of the time and to become periodically active
for the reception of a long preamble. It is suggested that battery powered devices use mainly the RF
channels S1 and S2 with the lower data rate.
PRM devices supporting the Fast RF channels shall be in permanent scanning and receiving mode.
NPRM devices supporting the Fast RF channels shall scan each RF channel every 15 ms (1 ms for
hopping, 1 ms for scanning one RF channel). If a preamble is detected, it shall listen to the Frame, if not it
shall jump to next RF channel.
A receiver on only one RF channel without scanning any other is not permitted.
In the first three Fast RF channels, the first RF channel is the one used by RF HBES Ready devices and
the two other Fast RF channels are escape RF channels used in case of a busy RF channel.
In the two Slow RF channels, the first one is S1 for slow products and the other Slow RF channels is an
escape RF channel used in case of a busy RF channel.
Devices will mainly use F1, F2, F3 or S1, S2: 5 RF channels will only in very seldomly be supported in
applications.
5.2.2 Physical Layer type RF Multi
5.2.2.1 HBES RF1 channel definitions for RF channels F1, F2 and F3
Table 6 – RF channel definitions for RF1 channels F1, F2 and F3
Parameter Value Comment
b
Tx centre frequency Channel F1 868,300 MHz HBES Tx to HBES Rx
Tx : ± 25 ppm
Channel F2 868,950 MHz
Rx : ± 25 ppm
a
Channel F3 869,850 MHz
c
Metering Tx to HBES RF Multi
Tx : ± 60 ppm
Rx : ± 60 ppm
TX radiated power Typical: 0 dBm
Min: -3 dBm
Max: +14 dBm
Deviation Typical : 60 kHz
± 48 kHz to ± 80 kHz
Max allowed bandwidth 500 kHz For F1 and F2
a
300 kHz For F3
Tx max duty cycle 1 % for F1 For F3 only, Duty Cycle is 100 % up to a
maximum radiated power of 5 mW and
0,1 % for F2
restricted to 1 % from 5 mW to 25 mW
100 % for F3
Tx chip rate 32 768 chips per second
Maximum Tx chip rate
±1,5 %
tolerance
Maximum Tx jitter per
±5 µs
transition
d
Sensitivity max -95 dBm typical Radiated test
-4
-80 dBm min BER : 10
Minimal Rx chip rate
± 2 %
tolerance
Preamble length 247x chip sequence “01” ~15 ms, number of preamble chips is not
checked by Rx
Receiver blocking Minimum category 2 Category 2 according ETSI EN 300 220 (all
performance parts)
e
Minimal operating range 0°C to 45°C
a
RF channel F3 is optional. It might not be implemented by hardware.
b
This frequency tolerance includes tolerances due to temperature variations within the operating temperature
range and tolerances due to crystal aging.
c
Frequency error correction may be needed in the case of Tx metering to HBES Rx specific products. Metering
only applies to RF channel F1.
d -4
At Bit Error Rate (BER) 10 in optimum antenna direction.
e
HBES Physical Layer parameters shall be met on the entire product temperature range declared by the
manufacturer. (e.g. : -10°C to +70°C for outdoor usage).

5.2.2.2 HBES RF1 channel definitions for RF channels S1 and S2
Table 7 — RF channel definitions for RF1 Multi channels S1 and S2
Parameter Value Comment
a
Tx centre frequency Channel S1 869,850 MHz
Tx: ±25 ppm
Rx: ±25 ppm
Channel S2 869,525 MHz
Tx radiated power Typical: 0 dBm
Min: -3 dBm
Max: +14 dBm
Deviation The usage of frequency error correction may
±20 kHz to ±65 kHz
be needed to guarantee good receiver
performances.
Max allowed bandwidth 300 kHz For S1
250 kHz For S2
Tx max duty cycle 100 % for S1 For S1 only, Duty Cycle is 100 % up to a
maximum radiated power of 5 mW and
10 % for S2
restricted to 1 % from 5 mW to 25 mW
Tx chip rate 16 384 chips per second
Maximum Tx chip rate
Tx: ±1,5 %
tolerance
Maximum Tx jitter per
±5 µs
transition
b
Sensitivity max -95 dBm typical Radiated test
-4
-80 dBm min BER = 10
Minimal Rx chip rate
± 2 %
tolerance
Preamble length 4111 chip sequence “01” ~500 ms, number of preamble chips is not
checked by Rx
Receiver blocking Minimum category 2 Category 2 according ETSI EN 300 220 (all
performance parts)
c
Minimal operating 0°C to 45°C
range
a
This frequency tolerance includes tolerances due to temperature variations within the operating temperature

range and tolerances due to crystal aging.
b -4
At Bit Error Rate (BER) 10 in optimum antenna direction.
c
HBES Physical Layer parameters shall be met on the entire product temperature range declared by the

manufacturer. (e.g. : -10°C to +70°C for outdoor usage).

5.2.3 Telegram structure for HBES RF Multi systems
Table 8 – HBES RF Multi Telegrams definition
Characteristics Value Notes
Data encoding Manchester chip “0” means f (= f – f )
LO C DEV
chip “1” means f (= f + f )
HI C DEV
bit “0” is coded as f to f transition, chip sequence “10”
HI LO
bit “1” is coded as f to f transition, chip sequence “01”
LO HI
Preheader consists of Preamble, see below
Manchester violation,
Sync word
Preamble See above Depends on which RF channel is used.
Manchester chip sequence “000111” necessary for capture effect
violation
Sync word chip sequence useful for synchronization on chip rate
“011010010110”
Postamble 2 chips to 8 chips software reasons, mandatory for all Tx, number of
postamble not checked by Rx.
(Only applicable if no Fast Ack is used, refer to 6.3.4.3.)
Capture effect optional Preheader allows it; Rx may use it

6 HBES RF Data Link Layer
6.1 HBES RF Data Link Layer for all HBES RF devices
6.1.1 Differences to existing (bidirectional) HBES EN 50090 protocol
6.1.1.1 Extended Group Address
The Extended Group Address (8 octets) in a HBES RF Frame shall be the combination of the standard
HBES Group Address (2 octets) with the HBES Serial Number or the RF Domain Address of the sender
of the Frame (6 octets). Every group addressed HBES RF Frame shall contain an Extended Group
Address.
Any received Frame shall be taken in account by the receiver only if the Extended Group Address of the
sender is known by the receiver.
NOTE According to the RF Frame, these 8 octets are not transmitted consecutively.
The HBES RF Frame shall contain the HBES Serial Number - or the RF Domain Address of the sender
according Table 9. The sender shall indicate the used value (HBES Serial Number or RF Domain
Address) with the value of the field Address Extension Type (AET) as also indicated in Table 9.
Table 9 — Use of HBES Serial Number or RF Domain Address
HBES Serial Number or
RF Domain Address
communication mode
point-to-system, connectionless (system broadcast) yes no
point-to-domain, connectionless (broadcast) no yes
a a
point-to-multipoint, connectionless (multicast) yes yes
point-to-point, connectionless no yes
point-to-point, connection-oriented no yes
Address Extension Type (=AddrExtensionType) (AET) 0 1
a
It may depend on the used configuration mode whether the HBES RF device uses the HBES
serial number or RF Domain Address.
In any Frame in system broadcast communication mode the Destination Address shall be 0000h and the
Address Type shall be “group”.
6.1.1.2 Predefined Extended Group Addresses for transmit-only devices
Transmit only devices shall use Extended Group Addresses. As transmit-only devices only have sending
Datapoints (only one Group Address per Datapoint), all addresses can and shall be factory set.
• For Group Addresses
For all unidirectional sensors, Datapoint 1 shall have Group Address = 0001h, Datapoint 2 shall
have Group Address = 0002h, Datapoint N will have Group Address = N, with as result on the
bus Extended Group Address (HBES Serial Number of sensor, 0001h), (HBES Serial Number
of sensor, 0002h) and (HBES Serial Number of sensor, N). These Group Addresses shall be
unique for each sender.
• For Individual Addresses
All devices shall have the default Individual Address (05FFh).
6.1.1.3 Pre-defined Extended Group Addresses for bidirectional devices
The consequence from the above is that if groups consist of one sender and n receivers, form a 1-to-n
relationship. If several senders control a group of actuators, each of these actuators shall listen to the
sending addresses of all senders.
6.1.1.4 RF Domain Address
The RF Domain Address shall be a 6 octet number. It shall be guaranteed during the Configuration
procedures that the RF Domain Address is a unique number.
The sender shall include the RF Domain Address in the RF Frame according Table 9. This shall be
indicated by the value 1 of the field AddrExtensionType in the second block of the RF Frame.
HBES Serial Number
of the sender
RF Domain Address
of the sender
The receiver shall discard the RF Frame if the field AddrExtensionType does not match with the used
communication mode as given in Table 9.
In any Frame in broadcast communication mode the Destination Address shall be 0000h and the Address
Type shall be “group”.
6.1.1.5 RF Broadcast and RF System Broadcast
Broadcasts can be broadcasts within an installation or system broadcasts. Whether a broadcast is a
system broadcast shall be indicated by the AddrExtensionType field in the second block of the RF Frame.
- 0: system broadcast (shall not be restricted to the RF installation = domain; the Frame shall
contain the HBES Serial Number of the sender).
- 1: broadcast (shall be restricted to the installation = domain; the Frame shall contain the
Domain Address).
6.1.2 Data Link Layer Frame
6.1.2.1 General
This subclause specifies the Frame format of the HBES-RF system.
6.1.2.2 Structure
The Frame format builds on the FT3 Data Link Layer (IEC 870-5). The Frame consists of a preamble
(Physical Layer), several data blocks, each followed by 2 octets CRC, and a postamble (Physical Layer).
The first data block has a fixed length of 10 data octets. The following blocks contain 16 data octets,
except the last block, which may contain less than 16 octets (the remainder).
10 2 octets 16 2 2
octets octets octets octets
preamble data block 1 CRC data block 2 CRC … CRC postamble
Figure 1 — Overview of the Data Link Layer Frame
6.1.2.3 Bit and octet order
Data shall be transmitted most significant bit (msb) first.
For data fields consisting of multiple octets (e.g. HBES Serial Number/Domain Address and Device
Addresses) the most significant octet (MSB) shall be transmitted first.
6.1.2.4 First block
octet 1 octet 2 octet 3 octet 4 octet 5 to octet 10 octet 11 and octet 12
Length C Esc RF-info SN/DoA CRC
7 6 5 4 3 2 1 0
44h FFh 0
Figure 2 — Structure of the first block
reserved
received signal
strength
battery state
unidir
• Length
Description: According to IEC870-5: total number of user octets counted from the C-field (excluding the
CRCs). FFh value is reserved for future use.” See EN 50090-4-2.

• C ()
Description: According to IEC870-5. HBES only uses SEND/NO REPLY (C = 44h)

• Esc ()
Description: This field shall have the fixed value FFh.

• RF-info – bit 7
Description: This bit is reserved for HBES system and shall be set to 0.

• RF-info – bit 6
Description: This bit shall be set to 0 by the sender.

• RF-info – bits 5 and 4
Description: These bits shall be set to 00b by the sender.

• RF-info – bits 3 and 2
Description: This field shall contain the received signal strength indication.
This field shall be filled in by the Retransmitter with the lowest received signal strength;
other senders shall always fill in the value 00h for this field.
The Retransmitter shall not change the value if it cannot measure the signal strength.
Encoding: 00b: void (no measurement)
01b: weak
10b: medium
11b: strong
• RF-info – bit 1
Description: This field shall contain the battery state of the sender of the Frame.
Encoding: 0: battery is weak
1: battery is ok
• RF-info – bit 0: Unidir
Description: Unidir
Encoding: 0: Frame sent by bidirectional device
1: Frame sent by unidirectional device

• SN/DoA()
Description: HBES Serial Number or Domain Address of the sender.
The field AddrExtensionType in the LPCI in the second block shall indicate whether this
field contains the HBES Serial Number or the Domain Address.

• CRC
Description: CRC according to IEC870-5-1
Encoding: For information: The CRC according to FT3 of IEC 870-5-1 uses
16 13 12 11 10 8 6 5 2 0
2 +2 +2 +2 +2 +2 +2 +2 +2 +2
as a generator polynomial. It starts with zero and treats the data msb first. The CRC result
is complemented. The MSB of the 16-Bit CRC is transmitted first.
EXAMPLE 3 The sequence 01 02 03 04 05 06 07 08 has the CRC FCBCh.

6.1.2.5 Second block for Standard Telegrams
octet 1 octet 2 octet 3 octet 4 octet 5 octet 6 octet 7
HBES Ctrl Source Address Destination Address LPCI
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

octet 8 octets 9 to octet n octet n+1 and n+2
data CRC
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

Figure 3 — Structure of the second block for Standard Telegrams
• ffff field
Description: The Frame format field is described in 6.1.3.

• Extended Frame Format (EFF)
Description: The Extended Frame Format field shall specify the format of the Frame.
Encoding: 0000b = Standard Frame
Other values are reserved (see EN 50090-4-2).

• Source Address (SA)
Description: The Source Address shall contain the Individual Address of the device that initiates the transmission
of the Frame.
Encoding: See EN 50090-4-2, Clause “Individual Address”.

• Destination Address (DA)
Description: This shall be the Destination Address of the Frame and shall be an Individual Address or a Group
Address.
Encoding: See EN 50090-4-2 for the format of the Individual Address and the Group Address.

• Address Type (AT)
Description: This field shall specify whether the Destination Address is an Individual Address, a Group Address
or the broadcast address.
Encoding: For the Standard Frame, the encoding shall be as follows:
0: Individual Address
1: Group Address
• Repetition counter (RC)
Description Specifies the maximum number of repetitions allowed for one Frame.

• Data Link Layer Frame Number (LFN)
Description Sequence counter to discriminate successive Frames.

• Address Extension Type (AET)
Description: For the Standard Frame, the AET shall be used as follows:
Encoding: 0: The field SN/DoA in the first block shall be interpreted as the HBES Serial Number of the sender.
1: The field SN/DoA in the first block shall be interpreted as the RF Domain Address.

f
f
f
f
EFF
EFF
EFF
EFF
APCI
APCI
APCI/Data
APCI/Data
APCI/Data
APCI/Data
APCI/Data
APCI/Data
AT
RC
RC
RC
LFN
LFN
LFN
AET
TPCI
TPCI
Seq number
Seq number
Seq number
Seq number
APCI
APCI
• TPCI
Description: The TPCI field shall contain the Transport Layer service indication.
Encoding: See EN 50090-4-2.
00b: unnumbered data
01b: numbered data
10b: unnumbered control
11b: numbered control
• Sequence Number
Description: This field shall contain the Sequence Number of the Frame.

• APCI
Description: The APCI field shall contain the Application Layer service indication.
Encoding: See EN 50090-4-1.
• Data
Description: Up to 8 data octets in this block (16 octets max block length), subsequent data octets in following
blocks (each block 16 octets, except the last block, which may contain less than 16 data octets.)
6.1.3 Use of the HBES Ctrl Field
6.1.3.1 Overview
Table 10 — HBES CTRL field values
HBES Ctrl
bit
Frame Type
7 6 5 4 3 2 1 0
0 0 0 0 e e e e Asynchronous Data Frames L_Data
0 0 0 1 e e e e Fast_ACK
0 0 1 0 r r r r Reserved
0 0 1 1 r r r r Reserved
0 1 0 0 e e e e Reserved
0 1 0 1 0 0 0 0 Reserved
0 1 0 1 r r r r Reserved range rrrr ≠0000
0 1 1 0 0 0 0 0 Reserved
0 1 1 0 r r r r Reserved range rrrr ≠0000
0 1 1 1 0 0 0 0 Reserved
0 1 1 1 r r r r Reserved range rrrr ≠0000
1 0 0 0 e e e e RF Multi asynchronous Data Frames L_Data
1 0 0 1 e e e e RF Multi asynchronous Data Frames L_Data with
Fast_ACK requested
1 0 1 0 0 0 0 0 RF Multi Repeater Acknowledge Frame
1 0 1 0 r r r r Reserved range rrrr ≠ 0000
1 0 1 1 r r r r Reserved
1 1 r r r r r r Reserved
1 1 1 1 1 1 1 1 Escape value for future HBES Ctrl Extensions (2 Octet
HBES Ctrl FFxx)
eeee = EFF field, see EN 50090-4-2
r = reserved. Reserved bits are reserved for the HBES system.
Reserved or unknown coding of HBES Ctrl shall not be used by the
transmitter and shall be ignored by the receiver.

6.1.4 Data Link Layer protocol
6.1.4.1 AddrExtensionType
The AddrExtensionType bit shall be a parameter of the Data Link Layer instance.
In transmission direction the sending Data Link Layer instance shall evaluate the AddrExtensionType and
set the correct data in the field SN/DoA in block 1 of the transmitted Frame: either the devices’ own HBES
Serial Number or the Domain Address,
In reception direction the receiving Data Link Layer instance shall use this bit for a correct interpretation of
the field SN/DoA in block 1 of the received Frame as either HBES Serial Number or Domain Address.
This Data Link Layer parameter shall be set by the Application Layer and shall be passed through the
communication stack by the other layers as input to the Data Link Layer.
6.1.4.2 Duplication prevention
6.1.4.2.1 General
Please refer to EN 50090-4-2 for medium independent requirements for error and exception handling.
In the presence of Retransmitters in the system, Frame duplications can occur in the receivers if both the
original sender and repetitions sent by the Retransmitters are received. Therefore a mechanism is
foreseen in Layer-2 to prevent the evaluation of duplicated Telegrams in receivers.
6.1.4.2.2 Transmitters
The Data Link Layer of each transmitter shall insert a Link layer Frame Number (LFN) into the LPCI of
each sent Frame (see 6.1.2.5). The LFN shall be a 3 bit counter that shall be incremented for each
transmitted Frame. After 8 Frames the counter shall wrap around and shall start off again from zero.
In order to increase the probability to have no Frame lost, the Frame with the same LFN can be resent.
6.1.4.2.3 Receivers
The receiver shall discard subsequent Telegrams that contain the identical LFN from the same sender. In
case the LFN differs, the newly received LFN shall be stored.
Every receiver shall have a table to store the HBES Serial Number and the LFN of previously received
Telegrams (no matter from where they are sent). The table length shall be less or equal to 7, because the
LFN counts from 0 to 7. This avoids unintentional discarding of Telegrams, even if Telegrams from only
one device are received.
This mechanism ensures that repeated Telegrams originating from the same sender up to within the
following 8 Telegrams are discarded.
6.1.5 Data Link Layer services
6.1.5.1 L_Data service and protocol
In addition to the general Data Link Layer protocol requirements specified in EN 50090-4-2, for the
L_Data-service, the following shall apply.
The L_Data service on HBES RF shall either be an unconfirmed or a confirmed Telegram service. If the
local Data Link User prepares an LSDU for one or more remote Data Link Layer users, it shall apply the
L_Data.req service to pass the LSDU to the local Data Link Layer. The local Data Link Layer shall accept
the service request and shall try to send the LSDU to the remote Data Link Layer Users. The Destination
Address may be an Individual Address, a Group Address or the Broadcast Address. The Local Data Link
Layer shall pass an L_Data.con primitive to the Local Data Link Layer User that shall indicate a correct or
erroneous data transfer.
The Local Data Link Layer shall accept the L_Data.req service request. The fields SN/DoA, AT and AET
shall be filled in as follows.
If the service parameter address_type denotes an Individual Address then
- the SN/DoA field in the Frame shall be filled with the RF Domain Address;
- the Address Extension Type (AET) shall be set to 1; this shall indicate that the SN/DoA
field shall be interpreted as the RF Domain Address
- the Address Type field shall be set to 0; this shall denote that the Destination Address shall
be interpreted as an Individual Address.
If the address_type denotes a Group Address then
a) if the Destination Address value equals the broadcast address 0000h then
1) the SN/DoA field in the Frame shall be filled with the RF Domain Address;
2) the Address Extension Type (AET) shall be set to 1; this shall indicate that the SN/DoA field
shall be interpreted as the RF Domain Address
3) the Address Type field shall be set to 1; this shall denote that the Destination Address shall
be interpreted as a Group Address.
b) if the Destination Address value does not equal the broadcast address 0000h but is a normal
Group Address, then
4) the SN/DoA field in the Frame shall be filled with the HBES Serial Number of the sender or
the RF Domain Address (depending on the way the HBES device was configured);
5) the Address Extension Type (AET) shall be set to 0 (this shall indicate that the SN/DoA field
shall be interpreted as the HBES Serial Number of the sender) or 1 (this shall indicate that
the SN/DoA field shall be interpreted as the RF Domain Address);
6) the Address Type field shall be s
...