CLC/TS 50134-9:2018
(Main)Alarm systems - Social alarm systems - Part 9: IP Communications Protocol
Alarm systems - Social alarm systems - Part 9: IP Communications Protocol
This Technical Specification specifies a protocol for point-to-point transmission of alarms, faults, control signals and communications monitoring, between a Local Unit and Controller and an Alarm Receiving Centre using the Internet protocol (IP). The protocol is intended for use over any network that supports the transmission of IP data with sufficient quality of service to support VoIP or a separate voice channel. The Alarm Protocol is defined as an XML scheme including the alarm types, codes and necessary additional information. The alarm protocol is an application layer protocol using another Internet Protocol as a transport protocol to handle addressing and transport functions. The transport protocol initially defined in this Technical Specification is SIP (Session Initiation Protocol). The system performance characteristics for alarm transmission are specified in EN 50134-5. The performance characteristics of the Local Unit and Controller are expected to comply with the requirements of its associated alarm system standard and to apply for the transmission of social alarms. The protocols described in this standard are based on the SS 91100:2014 SCAIP standard [7] and defined to enable backwards compatibility with existing products based on the SCAIP standard.
Alarmanlagen - Personen-Hilferufanlagen - Teil 9: IP-Übertragungsprotokoll
Systèmes d'alarme - Systèmes d'alarme sociale - Partie 9: Protocole de communication IP
Alarmni sistemi - Socialni alarmni sistemi - 9. del: Komunikacijski protokoli IP
Ta tehnična specifikacija opredeljuje protokol za prenos alarmov, napak, krmilnih signalov in komunikacij od točke do točke med lokalno enoto in krmilnikom ter sprejemnim centrom za alarme prek internetnega protokola (IP). Protokol je namenjen za uporabo v vseh omrežjih, ki podpirajo prenos podatkov IP z ustrezno kakovostjo storitve za podporo protokola VoIP, ali prek ločenega glasovnega kanala.
Alarmni protokol je opredeljen kot shema XML, vključno z vrstami alarmov, kodami in potrebnimi dodatnimi informacijami.
Protokol alarma je protokol aplikacijske ravni, ki uporablja drug internetni protokol kot transportni protokol za obdelavo naslovov in izvajanje transportnih funkcij. Transportni protokol, prvotno opredeljen v tej tehnični specifikaciji, je SIP (protokol za začetek seje).
Lastnosti delovanja sistema za prenos alarma so navedene v standardu EN 50134-5. Pričakuje se, da bodo lastnosti delovanja lokalne enote in krmilnika izpolnjevale zahteve standarda za povezani alarmni sistem ter se uporabljale za prenos socialnih alarmov.
Protokoli, opisani v tem standardu, temeljijo na standardu SS 91100:2014 SCAIP [7] in so opredeljeni tako, da omogočajo povratno združljivost z obstoječimi izdelki na podlagi standarda SCAIP.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2018
Alarmni sistemi - Socialni alarmni sistemi - 9. del: Komunikacijski protokoli IP
Alarm systems - Social alarm systems - Part 9: IP Communications Protocol
Systèmes d'alarme - Systèmes d'alarme sociale - Partie 9: Protocole de communication
IP
Ta slovenski standard je istoveten z: CLC/TS 50134-9:2018
ICS:
13.320 Alarmni in opozorilni sistemi Alarm and warning systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
TECHNICAL SPECIFICATION CLC/TS 50134-9
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
September 2018
ICS 13.320; 35.240.99
English Version
Alarm systems - Social alarm systems - Part 9: IP
Communications Protocol
Systèmes d'alarme - Systèmes d'alarme sociale - Partie 9: Alarmanlagen - Personen-Hilferufanlagen - Teil 9: IP
Protocole de communication IP Übertragungsprotokoll
This Technical Specification was approved by CENELEC on 2018-05-28.
CENELEC members are required to announce the existence of this TS in the same way as for an EN and to make the TS available promptly
at national level in an appropriate form. It is permissible to keep conflicting national standards in force.
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, Serbia, 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: Rue de la Science 23, B-1040 Brussels
© 2018 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. CLC/TS 50134-9:2018 E
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms, definitions and abbreviations . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 8
4 Social Alarm transmission network architecture . 9
4.1 General . 9
4.2 Alarm and status messages . 10
4.2.1 General . 10
4.2.2 Authentication . 10
4.2.3 Encryption . 10
4.3 Voice / multimedia over IP implementation . 10
4.4 Separate voice network . 10
5 Use Case 1: Event without voice- or multimedia communication . 11
5.1 General . 11
5.2 Event not treated by alarm receiver . 11
5.3 Event information update . 12
5.4 Aborting message session . 12
5.5 Heartbeat . 12
6 Use case 2: Event with voice or multimedia communication . 12
6.1 LUC initiated voice / multimedia channel . 12
6.2 ARC initiated voice / multimedia channel . 13
6.3 Voice session initiation decision . 14
7 Message format description . 14
7.1 General . 14
7.2 Interoperability Considerations with Version Numbering . 15
7.2.1 General . 15
7.2.2 Interoperability between LUC and ARC versions with the same major version number . 15
7.2.3 Interoperability between LUC and ARC with Different Major Version Numbers . 15
7.2.4 Interoperability with SCAIP . 15
7.3 Message Request. 15
7.4 Message Response . 19
8 DTMF code . 21
9 Sessions . 22
9.1 Message . 22
9.2 Voice or multimedia . 23
Annex A (normative) Codes for device types . 24
Annex B (normative) Codes for device components . 27
Annex C (normative) Status codes . 28
Annex D (normative) Location codes . 32
Annex E (normative) Info codes . 34
Annex F (informative) XML schema . 35
Annex G (informative) Rationale and roadmap . 40
Bibliography . 41
European foreword
This document (CLC/TS 50134-9:2018) has been prepared by CLC/TC 79 “Alarm systems”.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
EN 50134 consists of the following parts, under the general title Alarm systems — Social alarm systems:
— Part 1: System requirements;
— Part 2: Trigger devices;
Part 3: Local unit and controller;
—
— Part 5: Interconnections and communications;
Part 7: Application guidelines;
—
— Part 9: IP Communications Protocol [the present Technical Specification].
Annexes which are designated “informative” are given for information only.
Introduction
As telecommunication operators continue to migrate towards Next Generation Networks they are increasingly
converging voice traffic onto their IP infrastructures which may have an adverse impact on the reliability of in-
call, tone based protocols.
The impact differs per country but is rapidly increasing across Europe. In addition, cellular technology is
increasingly used next to broadband, cable and fibre solutions.
This Technical Specification defines the IP communications protocol for social alarms, optimized for stand-
alone usage. The majority of current social alarms usage is stand-alone within the home and not related to
other alarm systems. The combination of social alarms with other types of alarm systems is pending for a
future version of this standard.
1 Scope
This Technical Specification specifies a protocol for point-to-point transmission of alarms, faults, control
signals and communications monitoring, between a Local Unit and Controller and an Alarm Receiving Centre
using the Internet protocol (IP). The protocol is intended for use over any network that supports the
transmission of IP data with sufficient quality of service to support VoIP or a separate voice channel.
The Alarm Protocol is defined as an XML scheme including the alarm types, codes and necessary additional
information.
The alarm protocol is an application layer protocol using another Internet Protocol as a transport protocol to
handle addressing and transport functions. The transport protocol initially defined in this Technical
Specification is SIP (Session Initiation Protocol).
The system performance characteristics for alarm transmission are specified in EN 50134-5. The performance
characteristics of the Local Unit and Controller are expected to comply with the requirements of its associated
alarm system standard and to apply for the transmission of social alarms.
The protocols described in this standard are based on the SS 91100:2014 SCAIP standard [7] and defined to
enable backwards compatibility with existing products based on the SCAIP standard.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
EN 50134–1, Alarm systems — Social alarm systems — Part 1: System requirements
ISO 8601, Data elements and interchange formats — Information interchange — Representation of dates and
times
ITU X509, Information technology — Open Systems Interconnection — The Directory: Public-key and attribute
certificate frameworks
RFC 2119, Key words for use in RFCs to Indicate Requirement Levels
RFC 2617, HTTP Authentication: Basic and Digest Access Authentication
[HTTP-AUTH]
RFC 3261, SIP: Session Initiation Protocol
[SIP]
RFC 3264, An Offer/Answer Model with the Session Description Protocol (SDP)
[SDP]
RFC 3428, Session Initiation Protocol (SIP) Extension for Instant Messaging
[SIP-IM]
RFC 3550, RTP: A Transport Protocol for Real-Time Applications
[RTP]
RFC 3711, The Secure Real-time Transport Protocol (SRTP)
[SRTP]
RFC 4568, Session Description Protocol (SDP) - Security Descriptions for Media Streams
[SDP-SEC]
RFC 4733, RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
[RTP-DTMF]
RFC 5245, Interactive Connectivity Establishment (ICE): A Protocol for Network Address
[ICE]
Translator (NAT) Traversal for Offer/Answer Protocols
RFC 5389, Session Traversal Utilities for NAT (STUN)
[STUN]
RFC 5764, Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the
[SRTP-DTLS]
Secure Real-time Transport Protocol (SRTP)
RFC 5766, Traversal Using Relays around NAT (TURN): Relay Extensions to Session
[TURN]
Traversal Utilities for NAT (STUN)
RFC 5768, Indicating Support for Interactive Connectivity Establishment (ICE) in the Session
[SIP-ICE]
Initiation Protocol (SIP)
RFC 5870, A Uniform Resource Identifier for Geographic Locations ('geo' URI)
RFC 6314, NAT Traversal Practices for Client-Server SIP
[SIP-NAT]
G.711 (11/88), Pulse code modulation (PCM) of voice frequencies
G.729 (06/12), Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction
(CS-ACELP)
3 Terms, definition
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.