Alarmbridge Service - How It Works

The iotcomms.io Alarmbridge Service provides cloud-based alarm and emergency communication across various protocols and device types. It enables seamless integration between alarm devices and alarm receiving centers (ARCs) by converting and mapping events across analog protocols, such as TT92, TTNew, BS8521:1 and IP-based protocols, such as SCAIP, NOW-IP, and SIA DC09.

The Alarmbridge Service is available as a SaaS offer, in the cloud or in a hybrid cloud deployment model. The hybrid cloud deployment option lets you run the service within your own data center using the Hybrid Enabler Service to meet highest privacy standards while the iotcomms.io team manages and monitors the service for best operational efficiency.

Key functions:

1. Alarm Event Receiving

   • Event Decoding

     \listPseudoHeader-0

     • The Event Receiver is configured to handle incoming alarm events, whether transmitted using analog or IP-based protocols.

     • The service decodes these events for further processing.

   • Protocol Conversion or API Callback

     • Once an alarm event is received and decoded, it is either routed through the automatic protocol conversion function for seamless interoperability.

     • Alternatively, it is sent as an API callback event to be processed by your application, enabling flexible integration with external systems.

2. Protocol Conversion

   • Seamless Interoperability

     \listPseudoHeader-0

     • The Alarmbridge Service bridges the gap between analog and IP-based alarm systems by converting alarm events from one protocol to another.

     • This ensures compatibility between legacy devices and modern ARC platforms, enabling a unified alarm handling process.

   • Analog to IP Conversion

     • Incoming analog alarm events, such as those using BS8521 or TT92 protocols, are decoded and converted into modern IP-based protocols like SCAIP or NOW-IP.

     • This function facilitates the transition to IP-based systems while maintaining support for existing analog devices.

   • IP to Analog Conversion

     • IP-based alarm events, such as those using SCAIP or NOW-IP, are converted to analog protocols for compatibility with legacy ARC platforms.

     • This allows modern devices to seamlessly connect with older ARC platforms, extending their usability without requiring infrastructure upgrades.

3. Alarm Event Sending

   • Alarm Event Triggers

     \listPseudoHeader-0

     • Alarm events to be sent can originate either from the automatic protocol conversion function or via an API call from your application.

     • These triggers initiate the Event Sender functionality, ensuring reliable alarm transmission.

   • Event Sender Function

     • The Event Sender processes the outgoing alarm event and formats it according to the target protocol, such as SCAIP, NOW-IP or BS-8521:1.

     • It ensures compatibility with the receiving platform, enabling seamless communication.

   • Reliable Delivery with Re-Transmissions

     • The Event Sender includes built-in alarm event re-transmission capabilities to guarantee that the alarm event is always successfully delivered to its destination.

4. Alarm Event Rewriting

   • Configurable Rewriting Rules

     \listPseudoHeader-0

     • The Alarmbridge Service can re-write alarm events based on custom configurations.

     • These rules allow you to modify event parameters to meet the specific requirements of the receiving system, ensuring seamless interoperability.

   • Facilitating System Interoperability

     • By re-writing alarm events, Alarmbridge can adapt event formats, content, or protocol-specific attributes to bridge differences between devices and ARC platforms.

     • This function ensures compatibility between otherwise incompatible systems, simplifying integration processes.

5. Three-Phase Alarm Event Receiving

   • The Alarmbridge Service supports all three phases of handling an incoming alarm event:

     • Alarm Event Decoding

       In the first phase, the alarm event from the device is received and decoded, converted and sent to the alarm receiving center.

     • Voice Communication Phase

       Following the alarm event, a two-way audio channel is established between the alarm device and the ARC operator, enabling real-time communication for assessment and guidance. In-call commands may be sent to control volume, toggle speak/listen etc.

     • Cleardown and Disconnect Phase

       Once the alarm session is concluded, the cleardown phase ensures protocol specific termination of the session.

6. VoIP and Video Communication Integration

   • The Alarmbridge Service securely integrates VoIP and video enabled alarm devices in the alarm communication flow. It allows devices deployed on Internet to access the alarm receiving center using SIP/TLS and SRTP event if the alarm receiving center have such capabilities.**

     **

     • VoIP Calling

       The Alarmbridge Service enables two-way VoIP communication between the alarm device and the ARC.

     • Video Communication

       The Alarmbridge Service can handle SIP video calls to and from the ARC and integrates with standard camera equipment to give the alarm operator visibility into the alarm situation.

7. Heartbeat Monitoring and Connectivity Assurance

   • Heartbeat Monitoring Function

     The Alarmbridge Service's heartbeat monitoring function tracks device connectivity. Devices send periodic "heartbeat" signals to confirm their active status, and if a signal is missing within the configured timeframe, an alarm event is issued, alerting the ARC to a potential connectivity issue.

8. Flexible Integration Options

   • API and Callback Integration

     The Alarmbridge Service integrates with external applications using APIs and callbacks, providing real-time connectivity updates and alarm event notifications.

   • Stand-Alone Protocol Converter

     For simpler implementations, Alarmbridge can operate as a stand-alone protocol converter, managing protocol-specific event conversions without additional external integrations.