Adding real-time communication into business-critical integrated solutions and new smart devices is difficult with many of the cloud services on the market today. While current conventional communications platforms do not meet the diverse set of requirements for business- or safety-critical solutions, iotcomms.io is built specifically for such use-cases. But why is iotcomms.io suitable for solutions of critical nature? Below are four important client requirements covered in our whitepaper Towards an embedded cPaaS market.

Towards an embedded cPaaS market

Device support

Some embedded communications applications need to work over a wide range of devices – including mobile phones, PCs, mobile radios, desk-phones and even legacy pagers. Sectors such as hospitals evolve operational systems only slowly – and may have an “if it isn’t broken, don’t fix it” mindset.

Characteristics of a Communications Platform for business-critical solutions: Protocols

Support for industry-specific protocols

Some applications will be based on event “triggers”, such as alarms or industrial controls.
  • In many instances the underlying systems may be legacy installations that will not be replaced as part of the transformation project (perhaps a fire alarm, or building management system).

  • In other cases, there may be specific standard applied – for example the Social Care Alarm Internet Protocol, SCAIP for telecare monitoring in Europe.
Characteristics of a Communications Platform for business-critical solutions: Customised interaction flows

Customised interaction flows

The normal metaphor and user-interaction model of a “phone call” or an SMS message, with a ring-tone or busy signals, may not be applicable. The platform needs to be able to support one-way voice (eg for audio announcements), one-way video / one-way audio (for example, for a video doorbell), perhaps push-to-talk, listen-only, group-calling or various other options.

Characteristics of a Communications Platform for business-critical solutions: Support for application-specific triggers

Support for application-specific triggers

Many embedded communications functions will have unique triggers for initiation of a call, session or message. Unlike standardised “click to call” or green-button “dial” interfaces, there could be a wide variety of events involved, from IoT sensors, to camera feeds. There may be a need for customised gateways, integrations and test regimes.

The text above is an extract from the whitepaper “Towards an embedded cPaaS market” written by industry analyst Dean Bubley, where he lists 14 important requirements for systems-embedded cPaaS clients. Download it below!

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn
Get your copy!
Towards an embedded cPaaS market

Towards an embedded cPaaS market

Explore the cPaaS market and learn the differences between a conventional communications platform and an embedded systems cPaaS, such as iotcomms.io.
Read it and understand more about what characterize a communications platform geared towards complex use-cases and business-critical applications.