Remote health monitoring technology from Sony's mSafety™

System description
Cloud solution
Wearable
SDK
Device mgmt
Connectivity
Security
API

System description

A customizable wearable device and a secure cloud backend

The mSafety platform consists of two main components: a wearable device and a cloud backend.
mSafety customers develop their own unique application to be embedded in the wearable, and connected to their backend application, through the mSafety cloud backend.

IoT solution from Sony

mSafety cloud backend

The mSafety cloud backend provides the fundamental structures needed for mSafety wearables to interact with customer’s cloud backend servers in a secure and scalable manner as well as wearable on-boarding and software updates.

mSafety platform web app

The mSafety platform web app is the front-end application that enables customers to perform user management, device management and to manage software-over-the-air updates. In addition, documentation and downloads of software and development tools are provided.

Wearable device

The wearable is directly connected to the Internet without the need for pairing with a mobile phone. It features in-device sensors with algorithms to monitor i.a. activity, heart rate, heart rate variability, VO2Max, as well as GNSS/GPS for location tracking. In addition, it can be connected to external sensors via Bluetooth Low Energy. A global roaming profile and data subscription plan means the wearable remains continuously connected in all environments.

The unobtrusive device works out of the box - once switched on, the wearable connects automatically with the service provider’s back-end and starts sending data.

Size: 53,2 x 45,0 x 12,75 mm
Weight: ca 30g
eUICC: LTE Cat-M connectivity, ready-to-use with global roaming profile (embedded Universal Integrated Circuit Card)
Sensors: Accelerometer, GPS, Gyro, Heart Rate
Screen: 1.4 inch 160x160 pixel Monochrome OLED with touch + 3 HW keys
Water resistance: IP68
Notifications: Vibrator, buzzer

The mSafety watch features low power consumption in a variety of modes thanks to an advanced LTE release 13 CAT-M1 chipset, and power-efficient multicore microcontroller. These features allow for an extended battery life.

Note about medical certification

Although the mSafety wearable is suitable for a variety of different use cases, including medical, it is important to note that the wearable is not a medically certified device. Should medical certification of the customer application be necessary, this is the responsibility of the customer.

Software Development Kit (SDK)

Create your own unique applications

mSafety customers develop their own unique mHealth & safety applications to be embedded in the wearable.

The mSafety platform offers a Software Development Kit (SDK) upon which you can build your innovative, value-adding services for lots of use cases – from monitoring the elderly in their own homes, to tracking kite-surfers or solitary workers in high-risk occupations.

Customers control their own app design and every aspect of the operating system, i.a. what data is collected, how often it’s collected or what is shown on the wearable display.

The mSafety business model maximises versatility and customer choice and controls your cost of ownership. You are charged for the service, not for having the app or for the number of users.

Device fleet management with end-to-end-encryption

The mSafety cloud backend provides easy fleet management. This includes for example: Adding and removing devices, remote device configuration and Firmware updates Over-The-Air (FOTA).

Find more info about FOTA, the easy way to manage and update your fleet of wearables here.

When the device is powered up for the first time, the data subscription plan is activated and an on-boarding process with the mSafety backend is executed. Partners can access the device management functions through the mSafety portal. This portal also provides user management functions, documentation and downloads.

Connectivity

LTE Cat-M

For a continuous and reliable connection, the device comes with a global roaming profile using cellular connectivity technology, LTE Cat-M1. LTE Cat-M is designed for use cases requiring low-power IoT communication – such as in safety and eHealth wearables.

For basic orientation, see the GSMA Mobile IoT Deployment Map. Please ask your local service provider for more accurate, up-to-date information on deployment in your area. Feel free to talk to us about developing a go-to-market plan.

See the GSMA Mobile IoT Deployment Map

Security - A root-of-trust platform

The mSafety solution has been designed, developed and manufactured with extremely high requirements on privacy and security. This includes:

Secure boot and update of mSafety wearable base software and partner application software. Wearable devices are tied to a specific partner by provisioning of partner specific keys and information.

The interface between the wearable and the mSafety Cloud backend is secured through TLS 1.2 with Server & Client (wearable) mutual authentication. Partner unique TLS client private key and X.509 Client Certificate is provisioned into the wearable.
The platform supports end-to-end encryption of application data from partner’s wearable application to partner’s backend application so that application data is not visible in the mSafety Cloud backend.

External sensor APIs

In the following you will find a list of wearable sensor algorithms, available through APIs. This list will be extended over time.

Activity recognition. Recognizes “still”, “walk” or “run”
Step counter
Energy Expenditure, i.e. “calories burned” in kcal per minute
VO2Max in ml/kg/min

Sleep detection – differs between light and deep sleep
Gesture recognition – recognizes user’s arm up, typically to turn on device screen
Heart Rate
Heart Rate Variability – an indication of the level of stress
Location

The technology behind mSafety