User's Manual
Table Of Contents
- 1 General description
- 2 Functional overview
- 2.1 Product description
- 2.2 Functional modes
- 2.3 Reporting interval
- 2.3.1 Energy considerations
- 2.3.2 Standard reporting interval
- 2.3.3 Illumination-controlled reporting interval
- 2.3.4 Temperature-controlled reporting interval
- 2.3.5 Humidity-controlled reporting interval
- 2.3.6 Acceleration-controlled reporting interval
- 2.3.7 Magnet contact sensor-controlled reporting interval
- 2.3.8 Arbitration between reporting intervals
- 3 Sensor functionality
- 4 Product interface
- 5 Radio communication
- 6 Security
- 7 Commissioning
- 8 NFC interface
- 9 NFC registers
- 9.1 NFC memory areas
- 9.2 Device identification NDEF
- 9.3 User information NDEF
- 9.4 NFC HEADER
- 9.5 CONFIGURATION
- 9.5.1 Using the NFC configuration functionality
- 9.5.2 CONFIGURATION area structure
- 9.5.3 NFC_PIN_CODE
- 9.5.4 PRODUCT_ID
- 9.5.5 USER_KEY
- 9.5.6 SECURITY_KEY_MODE
- 9.5.7 SECURITY_MODE
- 9.5.8 EEP
- 9.5.9 SIGNAL
- 9.5.10 LED_MODE
- 9.5.11 FUNCTIONAL_MODE
- 9.5.12 STANDARD_TX_INTERVAL
- 9.5.13 THRESHOLD_CFG1
- 9.5.14 THRESHOLD_CFG2
- 9.5.15 LIGHT_SENSOR_CFG
- 9.5.16 ACC_SENSOR_CFG
- 9.5.17 SOLAR_THRESHOLD
- 9.5.18 SOLAR_TX_INTERVAL
- 9.5.19 LIGHT_THRESHOLD
- 9.5.20 LIGHT_TX_INTERVAL
- 9.5.21 ACCELERATION_THRESHOLD
- 9.5.22 ACCELERATION_TX_INTERVAL
- 9.5.23 TEMPERATURE_THRESHOLD
- 9.5.24 TEMPERATURE_TX_INTERVAL
- 9.5.25 HUMIDITY_THRESHOLD
- 9.5.26 HUMIDITY_TX_INTERVAL
- 9.5.27 MAGNET_CONTACT_TX_INTERVAL
- 9.5.28 ILLUMINATION_TEST_RESULT
- 9.6 USER DATA
- 10 Mechanical interface
- 11 Installation recommendations
- 12 Regulatory notes
- 13 Product history
USER MANUAL
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS
© 2020 EnOcean | www.enocean.com F-710-017, V1.0 STM 550 / EMSI User Manual | v1.4 | November 2020 | Page 35/97
6 Security
STM 550 implements the security handling functions as specified in the EnOcean security
specification: https://www.enocean-alliance.org/sec/
6.1 Basic concepts
Security for radio transmission addresses two main issues:
◼ Unauthorized interception (reception and correct interpretation) of transmitted data
In doing so, a third (unauthorized) party is able to understand the content of a re-
ceived content.
◼ Unauthorized transmission of radio telegrams
In doing so, a third (unauthorized) party is able to transmit a radio telegram that is
treated by a receiver as valid request.
Somewhat loosely speaking, the goal of security has to be preventing an unauthorized person
(often referred to as an Attacker) both from learning about the current state of a system and
from actively changing it.
These goals can be achieved via techniques such as telegram encryption, telegram authori-
zation and dynamic security key modification. All three techniques will be reviewed in the
subsequent chapters for reference.
6.1.1 Telegram encryption
The goal of telegram encryption is to prevent unauthorized receivers from correctly inter-
preting the content of a telegram.
In order to do so, the original (plain text) data is encrypted with a key thus transforming it
into encrypted, unreadable data. Only when the correct key is known it is possible to trans-
form – decrypt - the encrypted data into readable data again. Figure 22 below shows the
concept.
Figure 22 – Telegram encryption
Decryption
Decryption Key
Unencrypted Data
(Plain Text)
Encryption
Unencrypted Data
(Plain Text)
Encrypted Data
Encryption Key
Encrypted Data