A modern telecare solution that is built around digital interfaces instead of analogue signals increases flexibility, reliability and functionality. It also offers the opportunity to connect several sensors to the telecare unit. A key factor for the digital migration is standards compliance where SCAIP, Social Care Alarm Internet Protocol, is a key building block. But still many alarm devices and alarm receiving platforms lack compliance with the SCAIP standard.
Lack of compliance with the SCAIP standard
When telecare devices started to be used in the 1960’s, analogue protocols and the fixed network was the only and obvious choice. Since then, the telecommunication network has continuously evolved and both mobile networks and fiber networks have more and more taken over the role of communication.
In many markets, the analogue care devices are still dominant causing problems such as call failures, reliability issues and lack of functionality and security. Digitalization of the telecare market provides devices and systems that are always connected allowing sensors and care devices to continuously share information with a receiving platform, which leads to improved monitoring of devices.
A key factor for the migration is standards compliance, where the SCAIP/CENELEC TS 50134-9 standard is a key building block. But adding SCAIP support it is both complex and costly, and can slow down time to market.
One of the challenges today is that many devices, such as smart assistants, iot and care devices, do not comply to the SCAIP standard and neither do many Alarm Receiving and Contact Centres.
Become SCAIP compliant with iotcomms.io Alarmbridge
SCAIP is an SIP-based protocol used for sending and receiving alarms and notifications over IP networks.
With our serverless Alarmbridge we make it easy to allow device manufacturers and receiving platforms to comply to the SCAIP standard through integration with a cloud service.
Alarmbridge supports a wide range of device manufacturers and can connect to alarm receiving platforms through a variety of protocols. The service will allow heartbeat functions to be sent on pre-set intervals.
For device manufacturers & Alarm Receiving Platforms
Alarmbridge converts SIP/SCAIP-signaling to standard HTTP messaging and connects SCAIP capable devices with Alarm Receiving Centres.
If you are a device manufacturer not supporting SCAIP, you can easily integrate to our platform via a REST API and we will translate and send the SCAIP message to the SCAIP compliant receiving platform.
If your receiving platform is not supporting SCAIP, we will receive the SCAIP message from the device and deliver it to you through a REST API making you SCAIP compliant.
EXAMPLE USE CASE
SCAIP messaging with VoIP communication
This example shows a scenario were a SCAIP compliant device is connected to iotcomms.io Alarmbridge, sending alarms and heartbeats that is passed on to an Alarm Receiving Centre as a REST callback.
The alarm event may trigger a voice call to be established with the device. iotcomms.io allows high level API functions to establish voice calls between the device, an ordinary phone system or by using the WebRTC gateway capabilities with a web browser.
Become SCAIP compliant using the provided high level functionality in Alarmbridge.
Reduce the amount of API callbacks between the platforms using the heartbeat service – trigger alarm events only in case heartbeat requests are not received in expected time.
Establish voice call between the device and an ordinary phone system or by using the WebRTC gateway capabilities with a web browser application.
Get access to the full voice and video capabilities provided by the iotcomms.io platform, such as SIP trunks to receive and place voice calls, and Mediaservice capabilities for interactive voice services.
Save time by not having to dig into protocol specific event flows for social care alarm integration.
All incoming alarm events are authenticated against provisioned devices.
Receive service alarm events in case of unforeseen service related issues such as access from unprovsioned devices or failure to deliver alarm events.
Supported Telecare devices
iotcomms.io supports Telecare devices from a range of vendors.
Support for equipment from other vendors can be added upon request.
Serverless functions built upon AWS public cloud for unlimited scale, reach & global deployment – extend to new markets quick and easy
cPaaS that you can trust for
mission-critical installations – our platform delivers superior availability, reliability & performance
Built upon microservices with strongest possible security in mind – 24/7 support and redundant environment keeps you fully secure