Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Include Blue Tooth signal strength information in ID emission #43

Closed
SchwertAs opened this issue May 14, 2020 · 2 comments
Closed

Include Blue Tooth signal strength information in ID emission #43

SchwertAs opened this issue May 14, 2020 · 2 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation wontfix This will not be worked on

Comments

@SchwertAs
Copy link

SchwertAs commented May 14, 2020

This concerns a missing feature. Due to very different signal strength ability varying between different Smartphont types and even differnt Smartphones of equal type, it might be neccessary to send a reference value of the own blue tooth signal strenght together with the personal token to get valuable distance measures by strength of blue tooth signal.

Where to find the issue

The issue should be added distibuted to the concerning user stories

Describe the issue

A blue tooth receiver is only able to detect the received signal strength it is getting. To figure out the distance of an emitter the source signal strength must be known. There might be some less reliable methods by detecting singnal strength of the sender by time curve analysis whilst approach of the sender - but more reliable is a direct information of the emitters sending strength. This should be sent within the exchange of IDs to the approached smartphone. The signal strenght information should only be used for the distance detection and must not be saved to the contact list.

Suggested change

add this to concerning user stories

@SchwertAs SchwertAs added bug Something isn't working documentation Improvements or additions to documentation labels May 14, 2020
@LukasMasuch LukasMasuch added the wontfix This will not be worked on label May 14, 2020
@LukasMasuch
Copy link
Member

Hey @SchwertAs, thanks for your suggestion. This issue concerns the Exposure Notification API from Apple/Google and cannot be implemented from our developers for the Corona-Warn-App. The Exposure Notification API already has certain device metadata encrypted in the broadcasted identifier (e.g. transmit power level). You can find more information about technical details within the Bluetooth Specification.

@tklingbeil
Copy link
Member

tklingbeil commented May 14, 2020

If you have a look at the Bluetooth specification, you'll see that the Associated Encrypted Metadata (AEM) contains the "transmit (Tx) power for better distance approximation".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working documentation Improvements or additions to documentation wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants