Difference between revisions of "GAEN Due Diligence: Verifying The Google/Apple Covid Exposure Notification API (Q4774)"
Jump to navigation
Jump to search
(Created claim: quote (P203): The lack of GAEN API transparency around this raises obvious concerns and reduces the value of health authorities and other app implementers making their client code publicly available) |
(Created claim: date (P100): 16 June 2020) |
||||||||||||||
| Property / date | |||||||||||||||
| + | 16 June 2020
| ||||||||||||||
| Property / date: 16 June 2020 / rank | |||||||||||||||
| + | Normal rank | ||||||||||||||
Revision as of 21:23, 19 June 2020
scholarly article published on June 2020
| Language | Label | Description | Also known as |
|---|---|---|---|
| English |
GAEN Due Diligence: Verifying The Google/Apple Covid Exposure Notification API
|
scholarly article published on June 2020
|
Statements
It can seen that the GAEN API RSSI values seem to correspond to beacons from only one channel. Bluetooth advertises beacons on three radio channels so as to improve tolerance of interference. Each channel may have different radio propagation characteristics, and be subject to different levels of interference from other transmitters.
0 references
The lack of GAEN API transparency around this raises obvious concerns and reduces the value of health authorities and other app implementers making their client code publicly available
0 references
16 June 2020
0 references