Skip to content

BLE Mobile Disengage Sequence

The implementation that transmits the mobile identification medium uses a design with a replay protection mechanism that has a patent pending. See EP3739554A1.

InterfaceAnnotations
BLE AdvertisementSee documentation of the EVVA component manufacturer specific advertisement.
Mobile Identification Medium ServiceSee GATT service description
Mobile Access Data In Disengage FlowSee specification of data in flow
Sequence diagram of disengage with mobile identification medium.
Step DescriptionCharacteristicOperationAnnotations
1Discover an EVVA component via BLE Advertisement of EVVA Components and connectN.A.N.A.
  • Component unique identifier (6 bytes) is contained in advertisement
  • Battery indication is contained in the advertisement
2Read mobile groupsMobileGroupsRead

If the component does not return any mobile group, the connection SHOULD be closed.

3Subscription of the access statusAccessStatusSubscribe

Will be notified on change

4Read challengeChallengeRead
  • Challenge is valid for the transaction within the current connection
  • Challenge mechanism enables Over-The-Air Replay-Attack Prevention
5Read the matching access rights from the persistent memory on the mobile phoneN.A.N.A.
  • Access Rights are pre-encrypted by the backend and cannot be read or manipulated on the mobile device.
  • Matching can be achieved using the component unique identifier (6 bytes). This requires meta-data that is handled/added by the backend.
6Transmit the access rights packaged and encrypted (AEAD) using the current challenge (see Step 4). See Mobile Access Data In Disengage Flow for specifications.MobileAccessDataWriteWithoutResponse
7Receive access status notification from the component (see Step 2) and close connection.AccessStatusNotifyStatus values are specified in Mobile Identification Medium Service

Specification Mobile