covid19/cwa-documentation
covid19/cwa-documentation
1
0
Fork 0
mirror of https://github.com/corona-warn-app/cwa-documentation synced 2024-11-26 11:14:27 +01:00
Code Releases Activity

Updated grammer

Browse Source
This commit is contained in:
emmetsap 2020-11-13 15:30:11 +00:00
parent 8de0c07a09
commit ff7418e720
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
solution_architecture.md
View File

@ -272,19 +272,19 @@ If the back end calls from the mobile applications cannot be spread as evenly as
A definite prerequisite for compatibility is that the identifiers of the mobile devices can be matched, i.e. the GAEN framework by Apple and Google is being used. A definite prerequisite for compatibility is that the identifiers of the mobile devices can be matched, i.e. the GAEN framework by Apple and Google is being used.
Most European countries are developing similar contact tracing apps, these app may use the common frameworks by Google and Apple, enabling transmission and detection of GAEN format diagnosis keys between devices running different contact tracing applications. Most European countries are developing similar contact tracing apps, these app may use the common frameworks by Google and Apple, enabling transmission and detection of GAEN format diagnosis keys between devices running different contact tracing applications.
Each country has its own separate database of users, in order to coordinate exposure information between countries a common service is required. Each country has its own separate database which contain the keys from infected individuals. In order to coordinate exposure information between countries a common service is required to enable interoperability.
The European Federation Gateway Service (EFGS) handles sharing diagnosis keys between different country's backend servers. The [European Federation Gateway Service (EFGS)](https://github.com/eu-federation-gateway-service/efgs-federation-gateway) enables interoperability of diagnosis keys between the connected country backend servers.
![Figure 15: High-level EFGS overview](images/solution_architecture/EFGS_overview.jpg "Figure 15: High-level EFGS overview") ![Figure 15: High-level EFGS overview](images/solution_architecture/EFGS_overview.jpg "Figure 15: High-level EFGS overview")
The Federation Gateway Service facilitates backend-to-backend integration, countries can onboard incrementally, while the national backends retain flexibility and control over data distribution to their users. The Federation Gateway Service facilitates backend-to-backend integration, countries can onboard incrementally, while the national backends retain flexibility and control over data distribution to their users.
For example if a German user is visiting France then all uploaded keys are of relevance to the French database, likewise if a French user is visiting Germany that users keys are of relevance to the German database. For example, if a German citizen visits France and then becomes infected, the keys of the German citizen are then relevant for the citizens of France. In this case the German citizen keys would be shared with the EFGS to enable the French backend to obtain the keys. Similarly, if a French user is visiting Germany that users keys are of relevance to the German database.
![Figure 16: Autonomous National Backend](images/solution_architecture/EFGS_Autonomous_Backend.jpg "Figure 16: Autonomous National Backend") ![Figure 16: Autonomous National Backend](images/solution_architecture/EFGS_Autonomous_Backend.jpg "Figure 16: Autonomous National Backend")
In the example above user A from country A travels to country B and tests positive, only the relevant users in Country B will receive the alert. In the example above, user A from country A travels to country B and tests positive, only the relevant users (those which came within proximity of the infected user A) in Country B will receive the alert.
Devices only communicate with their country's backend, the EFGS is only sent keys by a country's backend. Devices only communicate with their country's backend. That country's backend is then responsible to send relevant keys to the EFGS.
All countries provide all keys to the EFGS, the EFGS only transmits relevant keys to each country's backend, notifications and alerts are handled by each individual country's backend. All connected countries provide keys to the EFGS. The EFGS then makes available relevant keys to each additional connected country's backend. Notifications and alerts are handled by each individual country's backend.
The EFGS stores information of all currently infected citizens along with a list of countries they visited. The EFGS stores information of all currently infected citizens along with a list of countries they visited.
In order for the EFGS to function correctly all users must specify their visited countries correctly (either manually or automatically). In order for the EFGS to function correctly all users must specify their visited countries correctly (either manually or automatically).