BS ISO/IEC 14543-3-10:2020
$167.15
Information technology. Home electronic system (HES) architecture – Amplitude modulated wireless short-packet (AMWSP) protocol optimized for energy harvesting. Architecture and lower layer protocols
Published By | Publication Date | Number of Pages |
BSI | 2020 | 38 |
This part of ISO/IEC 14543 specifies a wireless protocol for low-powered devices such as energy harvesting devices in a home environment. This wireless protocol is specifically designed to keep the energy consumption of such sensors and switches extremely low.
The design is characterized by
-
keeping the communications very short, infrequent and mostly unidirectional, and
-
using communication frequencies that provide a good range even at low transmit power and avoid collisions from disturbers.
This allows the use of small and low-cost energy harvesting devices that can compete with similar battery-powered devices. The messages sent by energy harvesting devices are received and processed mainly by line-powered devices such as relay switch actuators, repeaters or gateways. Together these form part of a home automation system, which, when conforming to ISO/IEC 14543 (all parts), is defined as a home electronic system.
This document specifies OSI Layers 1 to 3 of the amplitude modulated wireless short-packet (AMWSP) protocols.
The AMWSP protocol system consists of two and optionally three types of components that are specified in this document. These are the transmitter, the receiver and optionally the repeater. Repeaters are needed when the transmitter and the receiver are located in such a way that no good direct communication between them can be established.
Protection against malicious attacks is handled in the upper layers and thus not treated in this document.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
4 | CONTENTS |
6 | FOREWORD |
8 | INTRODUCTION |
10 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions |
15 | 3.2 Abbreviated terms 4 Conformance 5 Architecture 5.1 Generic protocol description 5.1.1 Overview |
16 | 5.1.2 Physical layer 5.1.3 Data link layer 5.1.4 Network layer Tables Table 1 – AMWSP protocol stack structure (OSI) |
17 | 5.1.5 Transport layer 5.1.6 Session layer 5.1.7 Presentation layer 5.1.8 Application layer 5.2 Data unit description Figures Figure 1 – Structure of a subtelegram |
18 | 6 Layer 1 – Physical layer 6.1 Overview 6.2 General description |
19 | Figure 2 – Illustration of an ASK envelope and various physical parameters |
20 | 6.3 Requirements for the 315 MHz AMWSP protocol |
21 | Table 2 – Transmitter requirements for the 315 MHz AMWSP protocol |
22 | Table 3 – Receiver requirements for the 315 MHz AMWSP protocol Table 4 – Minimum required link budget for the 315 MHz AMWSP protocol |
23 | 6.4 Requirements for the 868,3 MHz AMWSP protocol Table 5 – Maximum RX power for the 315 MHz AMWSP protocol Table 6 – Transmitter requirements for the 868,3 MHz AMWSP protocol |
24 | Table 7 – Receiver requirements for the 868,3 MHz AMWSP protocol Table 8 – Minimum required link budget for the 868,3 MHz AMWSP protocol |
25 | 6.5 Frame structure Figure 3 – Complete frame structure for the 868,3 MHz AMWSP protocol Table 9 – Maximum RX power for the 868,3 MHz AMWSP protocol |
26 | Figure 4 – Encoded subframe Table 10 – Frame definition for the 315 MHz AMWSP protocol Table 11 – Frame definition for the 868,3 MHz AMWSP protocol |
27 | 7 Layer 2 – Data link layer 7.1 Overview 7.2 Subtelegram timing Figure 5 – TX maturity time divided into four 10 ms time ranges Table 12 – Maturity time parameters |
28 | 7.3 Data integrity 7.3.1 General Table 13 – Allocation of time slots to the different subtelegrams |
29 | 7.3.2 4 bit summation hash function algorithm 7.3.3 8 bit summation hash function algorithm 7.3.4 8 bit cyclic redundancy check (CRC) hash function algorithm Table 14 – Identification of the hash function used in the telegram |
30 | 7.4 Listen before talk 8 Layer 3 – Network layer 8.1 Overview 8.2 Switch telegram |
31 | 8.3 Repeater 8.3.1 General 8.3.2 Time response for collision avoidance Figure 6 – Conversion of a switch telegram to a normal telegram Table 15 – Conversion of the telegram type and STATUS fieldsfrom a switch telegram to a telegram |
32 | 8.3.3 Bits of a repeater level in the STATUS byte 8.4 Addressing 8.4.1 General Table 16 – STATUS byte with repeater level bits Table 17 – Repeating bits in STATUS byte |
33 | 8.4.2 Encapsulation Figure 7 – Example of an encapsulation |
34 | Annex A (informative)Examples of how to evaluate the hash values Figure A.1 – Example of a C code program of the 4 bit long summation hash value Figure A.2 – Example of a C code program of the 8 bit long summation hash value |
35 | Figure A.3 – Efficient C code program for the evaluationof an 8 bit long CRC type hash value |
36 | Bibliography |