{"id":344459,"date":"2024-10-20T00:11:36","date_gmt":"2024-10-20T00:11:36","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-clc-ts-50136-92020\/"},"modified":"2024-10-25T23:34:07","modified_gmt":"2024-10-25T23:34:07","slug":"bsi-pd-clc-ts-50136-92020","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-clc-ts-50136-92020\/","title":{"rendered":"BSI PD CLC\/TS 50136-9:2020"},"content":{"rendered":"
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).<\/p>\n
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.<\/p>\n
The system performance characteristics for alarm transmission are specified in EN 50136-1.<\/p>\n
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.<\/p>\n
Compliance with this document is voluntary.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 3.1 Terms and definitions 3.2 Abbreviations <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 4 Objective 5 Messaging 5.1 General <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 5.2 Message format overview 5.2.1 General <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 5.2.2 Identifiers 5.2.3 Message format <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 5.2.4 Connection handle 5.2.5 Device ID 5.2.5.1 General 5.2.5.2 SPT Device ID <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 5.2.6 Message ID <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 5.2.7 Message length 5.2.8 Sequence numbers 5.2.9 Flags 5.3 Padding and message length 5.3.1 General <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 5.3.2 Message length 5.4 Hashing 5.4.1 General 5.4.2 Invalid hash \u2013 transmitter response 5.4.3 Invalid hash – receiver response 5.5 Encryption 5.5.1 General <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 5.5.2 Key exchange 5.6 Timeouts and retries <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.7 Version number 5.8 Reverse commands 5.9 Initial values <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 6 Message types 6.1 General 6.2 Path supervision 6.2.1 General 6.2.2 Poll message 6.2.3 Poll response <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 6.3 Event message format 6.3.1 General <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 6.3.2 Event field <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 6.3.3 Time event field 6.3.4 Time message field 6.3.5 Link field \u2013 IP Address <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6.3.6 Link field \u2013 Port number 6.3.7 Link field \u2013 URL 6.3.8 Link field – Filename 6.3.9 Alarm Text <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 6.3.10 Site Name 6.3.11 Building Name 6.3.12 Location 6.3.13 Room <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 6.3.14 Alarm Trigger 6.3.15 Longitude 6.3.16 Latitude 6.3.17 Altitude <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 6.4 Event response format 6.5 Configuration messages 6.5.1 General <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 6.5.2 Connection handle request 6.5.3 Connection handle response <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 6.5.4 Device ID request 6.5.5 Device ID response <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 6.5.6 Encryption selection request 6.5.7 Encryption selection response <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 6.5.8 6.4.8 Encryption key exchange request <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 6.5.9 Encryption key exchange response 6.5.10 Hash selection request <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 6.5.11 Hash selection response 6.5.12 Path supervision request <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 6.5.13 Path supervision response 6.5.14 Set time command <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 6.5.15 Set time response 6.5.16 Protocol version request <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 6.5.17 Protocol version response 6.5.18 Transparent message <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 6.5.19 Transparent response 6.5.20 DTLS completed request <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 6.5.21 DTLS completed response 6.5.22 RCT IP parameter request <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 6.5.23 RCT IP parameter response <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 7.2.4 Commissioning using Shared Secret 7.2.4.1 General <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 7.2.4.2 Transferring the Shared Secret via out-of-band channel 7.2.5 Commissioning using X.509 Certificates and DTLS <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 7.3 Connection setup <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Annex A (normative)Result codes <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Annex B (normative)Protocol identifiers <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Annex D (informative)Examples of messaging sequences D.1 Commissioning <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | D.2 Connection setup <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Annex E (informative)Examples of application protocols E.1 SIA E.2 Ademco Contact ID <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | E.3 Scancom Fast Format E.4 VdS 2465 <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Annex F (informative)Design principles F.1 General F.2 Information security F.3 Use of UDP signalling <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Alarm systems. Alarm transmission systems and equipment – Requirements for common protocol for alarm transmission using the Internet Protocol (IP)<\/b><\/p>\n |