Difference between revisions of "Almbus/IP"
(→Technical) |
|||
| (10 intermediate revisions by the same user not shown) | |||
| Line 33: | Line 33: | ||
<tr> | <tr> | ||
| − | <td style="width: 130px;vertical-align: top;">''' | + | <td style="width: 130px;vertical-align: top;">'''Transport''' |
</td> | </td> | ||
<td>UDP/IPv4, UDP/IPv6 | <td>UDP/IPv4, UDP/IPv6 | ||
| Line 41: | Line 41: | ||
</td> | </td> | ||
<td><span style="font-family:monospace;">x-azh-almbusip</span> | <td><span style="font-family:monospace;">x-azh-almbusip</span> | ||
| + | </td></tr> | ||
| + | <tr> | ||
| + | <td style="width: 130px;vertical-align: top;">'''Initial Release''' | ||
| + | </td> | ||
| + | <td>0.0.1 (2014) | ||
</td></tr> | </td></tr> | ||
<tr> | <tr> | ||
| Line 61: | Line 66: | ||
</table> | </table> | ||
| − | '''ALMBUS''' is a alarm signaling protocol used to publish, store and recall alarm situations on various building infrastructure devices. The suffix IP indices that this version transmits all data via a IP Networks, for example Ethernet (IEEE 802.3). ALMBUS can be used to invoke a alarm status on software devices from hardware alarms (like fire alarm system) or vice-versa. | + | '''ALMBUS''' (abbreviation of ''alarm bus'') is a open, royalty free alarm signaling protocol used to publish, store and recall alarm situations on various building infrastructure devices. The suffix IP indices that this version transmits all data via a IP Networks, for example Ethernet (IEEE 802.3). ALMBUS can be used to invoke a alarm status on software devices from hardware alarms (like fire alarm system) or vice-versa. |
== Overview == | == Overview == | ||
| Line 72: | Line 77: | ||
To prevent false alarms, ALMBUS/IP incorporates several mechanisms to ignore malformed, unsolicited messages from other protocols or services, that may wrongly use the assigned broadcast address and port in the same network. | To prevent false alarms, ALMBUS/IP incorporates several mechanisms to ignore malformed, unsolicited messages from other protocols or services, that may wrongly use the assigned broadcast address and port in the same network. | ||
| + | |||
| + | ALMBUS protocol revisions starting at 1.0.0 feature back- and forward compatibility to newer versions, however only the latest version is published, as this is the most future stable implementation. | ||
ALMBUS supports | ALMBUS supports | ||
| Line 80: | Line 87: | ||
* Global perfect forward secrecy | * Global perfect forward secrecy | ||
* Single device muting | * Single device muting | ||
| + | |||
| + | By default, all Extensible Services / Server compatible products include ALMBUS. The ALMBUS reference implementation is currently present in 40+ Programming languages free to use and implement. | ||
| + | |||
| + | In theory, every ALMBUS enabled device that runs compatible implementation automatically joins the alarm group of the current broadcast domain. To connect indepenedent broadcast domains (for example different VLANS or router subnets) to the same ALMBUS group, the firewalls must be configured to pass UDP Multicast traffic in the assigned ranges or use a ALMBUS gateway solution. | ||
=== Message Types === | === Message Types === | ||
| Line 110: | Line 121: | ||
== License == | == License == | ||
| − | Considering the importance of life safety, The ALMBUS specification is royalty-free and associated documentation is available to the public. | + | Considering the importance of life safety, The ALMBUS specification is royalty-free and associated documentation is available to the public. Implementations that comply to the ALMBUS specification (without alterations on the base) can display the icon to indicate ALMBUS compatibility. |
| − | |||
== See also == | == See also == | ||
Latest revision as of 04:13, 23 February 2023
| almbus/ip | |
|---|---|
|
| |
| Developer | Netroda Technologies |
| Type | Alarm Signaling Protocol |
| Transport | UDP/IPv4, UDP/IPv6 |
| Identifier | x-azh-almbusip |
| Initial Release | 0.0.1 (2014) |
| Revision | 1.2.0 (2021) |
| Platform | Extensible Services / Server |
| Extended from | Inter-Networking Electronics Protocol |
ALMBUS (abbreviation of alarm bus) is a open, royalty free alarm signaling protocol used to publish, store and recall alarm situations on various building infrastructure devices. The suffix IP indices that this version transmits all data via a IP Networks, for example Ethernet (IEEE 802.3). ALMBUS can be used to invoke a alarm status on software devices from hardware alarms (like fire alarm system) or vice-versa.
Overview
ALMBUS devices are connected together using a ring network (almbus-lo) or, when used as IP protocol, any possible network topology. Every enabled device has the ability to raise alarms, receive alarms and forward/repeat alarms for requesting devices. Each Device can be assigned a unique device identification, alarm groups, restrictions and / or limitations.
The actions taken once upon a device received or raises a alarm are different. for example, The Digital Signage system SignMatic displays a alarm-specific information message on all displays, and refuses to accept any user request to display something else unless all alarms are cleared.
Technical
Devices that are ALMBUS-Enabled (usually part of the ES-Platform) are enabled to issue alarms. the IP version uses UDP Muticast groups to publish and receive alarms, the system can be configured to use perfect forward secrecy to minimize alarm hijacking, however it is strongly discouraged to use ALMBUS on publically accessible networks.
To prevent false alarms, ALMBUS/IP incorporates several mechanisms to ignore malformed, unsolicited messages from other protocols or services, that may wrongly use the assigned broadcast address and port in the same network.
ALMBUS protocol revisions starting at 1.0.0 feature back- and forward compatibility to newer versions, however only the latest version is published, as this is the most future stable implementation.
ALMBUS supports
- Message payload encryption
- Alarm groups
- Alarm identities
- Specific/Custom alarms
- Global perfect forward secrecy
- Single device muting
By default, all Extensible Services / Server compatible products include ALMBUS. The ALMBUS reference implementation is currently present in 40+ Programming languages free to use and implement.
In theory, every ALMBUS enabled device that runs compatible implementation automatically joins the alarm group of the current broadcast domain. To connect indepenedent broadcast domains (for example different VLANS or router subnets) to the same ALMBUS group, the firewalls must be configured to pass UDP Multicast traffic in the assigned ranges or use a ALMBUS gateway solution.
Message Types
| Alarm Type | Description |
|---|---|
| Danger | Indicates a dangerous situation occuring in the current context, for example mass shootings, terrorism attacks etc. |
| Fire | Requests immediate evacuation of the assigned area, as the building or structure is on fire |
| Evacuate | Requests immediate evacuation of the assigned areas |
| Havary | Raised when building infrastructure has severe malfunctions, like leaking pipes causing flooding or overheating of a structure due to failure on climatic systems |
| Catastrophy | Used for scenarios where a natual catastrophy is awaited or happening, for example tsunamis, hurricanes or thunderstorms |
| Clear | Indicates that a alarm has been revoked. |
| Information | Generous, non-dangerous announcements |
License
Considering the importance of life safety, The ALMBUS specification is royalty-free and associated documentation is available to the public. Implementations that comply to the ALMBUS specification (without alterations on the base) can display the icon to indicate ALMBUS compatibility.
