En 30 segundos
This 3Blue1Brown video adapts Nicky Case’s contact-tracing illustration to explain the privacy goals of DP-3T. A simplified Alice-and-Bob example follows Bluetooth broadcasts, a positive report and matching on a recipient’s phone.
- 1Follow the chainContact tracing can alert recent contacts after a positive result.
- 2Changing identifiersPhones exchange pseudorandom Bluetooth identifiers rather than GPS histories in this example.
- 3Match on the phoneThe receiving phone checks published reports against identifiers it recorded.
Conclusiones
- People may transmit an infection before symptoms appear.
- Changing Bluetooth identifiers can support proximity notifications without collecting GPS histories in the illustrated design.
- Phones check exposure matches locally against information published after a positive report.
- Open source enables inspection, but real implementations still have privacy and measurement limitations.
Lee el texto editado por capítulos
Why tracing matters
The 2020 explainer distinguishes people who are not infected, those who are infectious without symptoms, and those with symptoms. Even if symptomatic people isolate after testing, earlier contacts can continue a chain of transmission.
The 2020 explainer distinguishes people who are not infected, those who are infectious without symptoms, and those with symptoms. Even if symptomatic people isolate after testing, earlier contacts can continue a chain of transmission.
Contact tracing attempts to get ahead of that chain by notifying recent contacts of a person who tests positive. Interviews take time; uploading location histories could raise substantial privacy concerns.
A decentralized alternative
The video adapts an illustration by Nicky Case to explain a decentralized alternative, DP-3T. Its aim is to notify potentially exposed people while reducing the personal information shared with a central service.
The video adapts an illustration by Nicky Case to explain a decentralized alternative, DP-3T. Its aim is to notify potentially exposed people while reducing the personal information shared with a central service.
The narrator points to open source code as a way for others to inspect a proposed implementation. Openness enables scrutiny, but it does not by itself prove that every deployed app is free of privacy or security flaws.
Broadcast and exchange
In the simplified example, Alice’s phone broadcasts changing pseudorandom identifiers over Bluetooth. These identifiers do not contain her name or GPS location; nearby compatible phones can record them.
In the simplified example, Alice’s phone broadcasts changing pseudorandom identifiers over Bluetooth. These identifiers do not contain her name or GPS location; nearby compatible phones can record them.
If Alice and Bob stay near one another, their phones exchange and retain identifiers for a limited period. Matching is designed to happen on individual phones rather than sending everyone’s contact graph to a central authority.
A positive report and local matching
Alice later tests positive. In the illustration, she chooses to upload information needed to identify her recent broadcasts, using a one-time code from a health provider to authorize the report.
Alice later tests positive. In the illustration, she chooses to upload information needed to identify her recent broadcasts, using a one-time code from a health provider to authorize the report.
Bob’s phone periodically checks published information from positive reports against the identifiers it recorded. A match can trigger an alert, allowing Bob to take the public-health steps recommended at the time.
The example is a conceptual explanation, not a guarantee that a contact occurred or that transmission was prevented. Bluetooth proximity estimates can be imperfect, and privacy depends on the implementation and threat model; the [DP-3T project](https://github.com/DP-3T/documents) documents both design and limitations.
Más de este canal
40:44EN
51:55EN
0:55EN
33:51EN
2:25EN
1:02EN