Eddystone-URL attachments

Question

according to the image below, is it fair to say that Eddystone-URL beacons cannot be associated with attachments((with google beacon platform, even if deprecated)) because it does not have an ID identifier in the frame? the UUID acts only at the GAP level of the protocol stack enter image description here

Answer 1

The old Google Beacon Platform (for which Google announced a shut down date of April 1, 2021) included a registration endpoint which would allow you to register the beacon with their servers. One of the benefits of this server registration was to allow you to attach data on the server-side, so that when the beacons were detected by Google Play Services, the attachments would be downloaded and made available through the API.

This did work with Eddystone-URL, because the identifier payload used to register the beacon was simply a sequence of bytes. In the case of Eddystone-URL, you would register the bytes of the compressed URL (using Google's Eddystone-URL compression scheme). The registered bytes were Base64 encoded, so it didn't matter that they were binary data. You simply set the type to EDDYSTONE which covered both the typical EDDYSTONE-UID and less commonly registered EDDYSTONE-URL.

See here for more info on the way the AdvertiseId was registered.