Skip to content

Overview

The SDK for mobile devices was designed to allow developers to integrate with EVVA Access components from the Xesar mechatronical System into their own mobile applications.

The typical use case for this is when you want to use your own mobile application for some form of access.

Understand the system

Section titled “Understand the system”

It is important to understand that the Mobile SDK is only a small part of the system that is required to make such an integration work. The following diagram pictures a distribution overview and highlights the Mobile SDK in red.

Distribution view.

You will also need:

  • a working Xesar Software installation
  • with it’s provisioned EVVA Access Components
  • as well as a Middleware that will be the handler between your own mobile application, the working Xesar Installation and your own backend, which may for example be an ERP or a booking system.

Understand the Mobile SDK

Section titled “Understand the Mobile SDK”

Mobile Disengage with EVVA components (Xesar system) works over Bluetooth Low Energy and uses

  1. the continuous BLE Advertisement of EVVA components
  2. the GATT standard based Mobile Identification Medium Service to provide authentication and authorization capabilities equivalent to the standard Identification Medium in a Xesar.

Functionality covered by the SDK

Section titled “Functionality covered by the SDK”

Maintenance (on the roadmap, not available yet)

Section titled “Maintenance (on the roadmap, not available yet)”
  • Bridge for communication BLE to MQTT for Maintenance/Provisioning of components
  • Bridge for communication from RFID to MQTT to allow updates for RFID media

Responsibilities of the SDK

Section titled “Responsibilities of the SDK”

The implementation in the SDK handles the BLE communication and the full disengage sequence flow with the EVVA Component. This includes the required cryptographical operations.

The responsibility will be gradually be extended with support for features around provisioning and the handling of an Identification Medium). Therefore, the SDK already includes basic support for RFID as well as an MQTT client.

Responsibilities of your mobile application

Section titled “Responsibilities of your mobile application”
  1. push notifications
  2. security for the application bootstrap and data storage (e.g. 2FA, keystore)
  3. communication with your own Middleware and/or backend.

Supported Mobile Platforms

Section titled “Supported Mobile Platforms”
  • iOS (>=15)
  • Android (>= Android 10 & >= API Level 29)

Supported forms of application development

Section titled “Supported forms of application development”