BSI PD CLC/TS 50136-9:2020
$198.66
Alarm systems. Alarm transmission systems and equipment – Requirements for common protocol for alarm transmission using the Internet Protocol (IP)
Published By | Publication Date | Number of Pages |
BSI | 2020 | 58 |
This document specifies a protocol for point-to-point transmission of alarms and faults, as well as communications monitoring, between a Supervised Premises Transceiver and a Receiving Centre Transceiver using the Internet Protocol (IP).
The protocol is intended for use over any network that supports the transmission of IP data. These include Ethernet, xDSL, GPRS, WiFi, UMTS and WIMAX.
The system performance characteristics for alarm transmission are specified in EN 50136-1.
The requirements for the performance of the alarm transmission system, the SPT and the RCT are specified in the relevant parts of the EN 50136 series.
Compliance with this document is voluntary.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
8 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions 3.2 Abbreviations |
9 | 4 Objective 5 Messaging 5.1 General |
10 | 5.2 Message format overview 5.2.1 General |
11 | 5.2.2 Identifiers 5.2.3 Message format |
12 | 5.2.4 Connection handle 5.2.5 Device ID 5.2.5.1 General 5.2.5.2 SPT Device ID |
13 | 5.2.6 Message ID |
14 | 5.2.7 Message length 5.2.8 Sequence numbers 5.2.9 Flags 5.3 Padding and message length 5.3.1 General |
15 | 5.3.2 Message length 5.4 Hashing 5.4.1 General 5.4.2 Invalid hash – transmitter response 5.4.3 Invalid hash – receiver response 5.5 Encryption 5.5.1 General |
16 | 5.5.2 Key exchange 5.6 Timeouts and retries |
17 | 5.7 Version number 5.8 Reverse commands 5.9 Initial values |
18 | 6 Message types 6.1 General 6.2 Path supervision 6.2.1 General 6.2.2 Poll message 6.2.3 Poll response |
19 | 6.3 Event message format 6.3.1 General |
20 | 6.3.2 Event field |
21 | 6.3.3 Time event field 6.3.4 Time message field 6.3.5 Link field – IP Address |
22 | 6.3.6 Link field – Port number 6.3.7 Link field – URL 6.3.8 Link field – Filename 6.3.9 Alarm Text |
23 | 6.3.10 Site Name 6.3.11 Building Name 6.3.12 Location 6.3.13 Room |
24 | 6.3.14 Alarm Trigger 6.3.15 Longitude 6.3.16 Latitude 6.3.17 Altitude |
25 | 6.4 Event response format 6.5 Configuration messages 6.5.1 General |
26 | 6.5.2 Connection handle request 6.5.3 Connection handle response |
27 | 6.5.4 Device ID request 6.5.5 Device ID response |
28 | 6.5.6 Encryption selection request 6.5.7 Encryption selection response |
29 | 6.5.8 6.4.8 Encryption key exchange request |
30 | 6.5.9 Encryption key exchange response 6.5.10 Hash selection request |
31 | 6.5.11 Hash selection response 6.5.12 Path supervision request |
32 | 6.5.13 Path supervision response 6.5.14 Set time command |
33 | 6.5.15 Set time response 6.5.16 Protocol version request |
34 | 6.5.17 Protocol version response 6.5.18 Transparent message |
35 | 6.5.19 Transparent response 6.5.20 DTLS completed request |
36 | 6.5.21 DTLS completed response 6.5.22 RCT IP parameter request |
37 | 6.5.23 RCT IP parameter response |
38 | 7 Commissioning and connection setup 7.1 General 7.2 Commissioning 7.2.1 General 7.2.2 Procedures 7.2.3 Commissioning message sequence |
39 | 7.2.4 Commissioning using Shared Secret 7.2.4.1 General |
40 | 7.2.4.2 Transferring the Shared Secret via out-of-band channel 7.2.5 Commissioning using X.509 Certificates and DTLS |
41 | 7.3 Connection setup |
43 | Annex A (normative)Result codes |
44 | Annex B (normative)Protocol identifiers |
45 | Annex C (normative)Shared secret C.1 Formatting of the shared secret C.2 Checksum for Shared Secret Formatting C.3 Example of Secret Encoding and Formatting |
46 | Annex D (informative)Examples of messaging sequences D.1 Commissioning |
49 | D.2 Connection setup |
53 | Annex E (informative)Examples of application protocols E.1 SIA E.2 Ademco Contact ID |
54 | E.3 Scancom Fast Format E.4 VdS 2465 |
55 | Annex F (informative)Design principles F.1 General F.2 Information security F.3 Use of UDP signalling |