mSafety lets your business customize a lone worker safety service.
Handles dust and sand. Resistant to corrosive effects of sea water. Withstands vibrations and drops. Extreme temperatures and solar radiation are no match for mSafety either.
The advanced LTE release 13 CAT-M1 chipset, as well as the power-efficient multicore microcontroller, give mSafety devices a fantastic battery life.
mSafety uses LTE Cat-M1, a low-power wide-area cellular technology, which eliminates dependency on a smartphone and provides a reliable connection with a global roaming profile.
Why LTE Cat-M1? Find out why Sony chose this cellular technology in our white paper.
Thanks to BLE, mSafety devices can connect automatically to external devices and sensors as soon as they are switched on—and start sending data immediately.
All the data you collect with mSafety is easy to integrate into your existing systems. REST APIs ensure data transmits directly from your devices to your endpoint.
Group devices in fleets—as large as hundreds or as small as one. Device and fleet management is possible in the mSafety web interface and with the REST APIs.
mSafety gives you the freedom to update the smartwatch application without involving device users. Deploy applications, decide update patterns, and remotely update applications in run time—for individual devices or entire fleets.
Configure parameters like sample periods, upload intervals, and pairing of external devices. You can even configure an application without a FOTA update using Shadow: a feature that enables targeted adaptations for certain user groups or even for individual users.
mSafety devices are managed by Sony's backend architecture from the moment they are manufactured. All device data is routed directly to the customer endpoint once configured.
mSafety’s data management and scaling framework for IoT devices is built on the AWS IoT Core platform. No manual input from users or service providers is needed to transmit data.
The application data can be end-to-end encrypted from the wearable to the customer’s endpoint. It is never visible during transfer nor in the mSafety backend.
Communication between devices and the mSafety backend is secured using TLS 1.2 with mutual authentication, involving both the server and the client. Each wearable is provisioned with a unique TLS client private key and an X.509 client certificate.
For a detailed explanation of mSafety's security model, please turn to our white paper.
In this white paper, we’ve summarized the most important considerations for a business looking to enter the connected wearables market.
