Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate Exposure Notification Service payload according A/G #4

Open
sciabarracom opened this issue May 18, 2020 · 0 comments
Open

Comments

@sciabarracom
Copy link
Contributor

sciabarracom commented May 18, 2020

Imgur

The Exposure Notification Service payload has four sections:

  1. Flags Section — Bluetooth Low Energy general discoverable mode (bit 1) shall be set to 1.
  2. Complete 16-bit Service UUID Section — The UUID is 0xFD6F, and shall precede the Service Data section.
  3. Service Data 16-bit UUID Section — This section shall have two different sections in its payload:
    a. A 16 byte Rolling Proximity Identifier.
    b. A 4 byte Associated Encrypted Metadata that contains the following (LSB first):
    i. Byte 0 — Versioning.
    • Bits 7:6 — Major version (01).
    • Bits 5:4 — Minor version (00).
    • Bits 3:0 — Reserved for future use.
    ii. Byte 1 — Transmit power level.
    • This is the measured radiated transmit power of Bluetooth Advertisement packets, and is used to
    improve distance approximation. The range of this field shall be -127 to +127 dBm.
    iii. Byte 2 — Reserved for future use.
    iv. Byte 3 — Reserved for future use.
@sciabarracom sciabarracom changed the title Generate Generate Exposure Notification Service payload according A/G May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant