Abstract: A embodiment may involve receiving a contact tracing request for a first user identifier that corresponds to a first portable device identifier of a first portable device. The second example embodiment may also involve requesting and receiving, from a first computing device associated with the first user identifier, device adjacency data, wherein the device adjacency data contains a plurality of contact entries, wherein one of the contact entries identifies a second portable device identifier of a second portable device that was wirelessly detected by the first portable device and a timestamp of when the wireless detection of the second portable device occurred. The second example embodiment may involve determining, from the mappings, a second user identifier that corresponds to the second portable device identifier. The second example embodiment may further involve transmitting, to a second computing device associated with the second user identifier, a contact tracing notification.

Abstract: A embodiment may involve receiving a contact tracing request for a first user identifier that corresponds to a first portable device identifier of a first portable device. The second example embodiment may also involve requesting and receiving, from a first computing device associated with the first user identifier, device adjacency data, wherein the device adjacency data contains a plurality of contact entries, wherein one of the contact entries identifies a second portable device identifier of a second portable device that was wirelessly detected by the first portable device and a timestamp of when the wireless detection of the second portable device occurred. The second example embodiment may involve determining, from the mappings, a second user identifier that corresponds to the second portable device identifier. The second example embodiment may further involve transmitting, to a second computing device associated with the second user identifier, a contact tracing notification.

Abstract: A embodiment may involve receiving a contact tracing request for a first user identifier that corresponds to a first portable device identifier of a first portable device. The second example embodiment may also involve requesting and receiving, from a first computing device associated with the first user identifier, device adjacency data, wherein the device adjacency data contains a plurality of contact entries, wherein one of the contact entries identifies a second portable device identifier of a second portable device that was wirelessly detected by the first portable device and a timestamp of when the wireless detection of the second portable device occurred. The second example embodiment may involve determining, from the mappings, a second user identifier that corresponds to the second portable device identifier. The second example embodiment may further involve transmitting, to a second computing device associated with the second user identifier, a contact tracing notification.

Abstract: A embodiment may involve receiving a contact tracing request for a first user identifier that corresponds to a first portable device identifier of a first portable device. The second example embodiment may also involve requesting and receiving, from a first computing device associated with the first user identifier, device adjacency data, wherein the device adjacency data contains a plurality of contact entries, wherein one of the contact entries identifies a second portable device identifier of a second portable device that was wirelessly detected by the first portable device and a timestamp of when the wireless detection of the second portable device occurred. The second example embodiment may involve determining, from the mappings, a second user identifier that corresponds to the second portable device identifier. The second example embodiment may further involve transmitting, to a second computing device associated with the second user identifier, a contact tracing notification.

Abstract: A embodiment may involve receiving a contact tracing request for a first user identifier that corresponds to a first portable device identifier of a first portable device. The second example embodiment may also involve requesting and receiving, from a first computing device associated with the first user identifier, device adjacency data, wherein the device adjacency data contains a plurality of contact entries, wherein one of the contact entries identifies a second portable device identifier of a second portable device that was wirelessly detected by the first portable device and a timestamp of when the wireless detection of the second portable device occurred. The second example embodiment may involve determining, from the mappings, a second user identifier that corresponds to the second portable device identifier. The second example embodiment may further involve transmitting, to a second computing device associated with the second user identifier, a contact tracing notification.

Abstract: A embodiment may involve receiving a contact tracing request for a first user identifier that corresponds to a first portable device identifier of a first portable device. The second example embodiment may also involve requesting and receiving, from a first computing device associated with the first user identifier, device adjacency data, wherein the device adjacency data contains a plurality of contact entries, wherein one of the contact entries identifies a second portable device identifier of a second portable device that was wirelessly detected by the first portable device and a timestamp of when the wireless detection of the second portable device occurred. The second example embodiment may involve determining, from the mappings, a second user identifier that corresponds to the second portable device identifier. The second example embodiment may further involve transmitting, to a second computing device associated with the second user identifier, a contact tracing notification.