requirements_and_architecture_for_emergency_calling----Page:17
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
|
Routing core requirements Both civic and geo coordinates conversion from civic to geo may introduce errors need to check validity of civic addresses thus, need to map both point-in-polygon and hierarchical strings Delegation service boundaries follow arcane political maps mapping updates must be done at local level Scaling global directory Caching can’t go to root directory for each call must work even if routing machinery is temporarily unavailable Reliable WAN-scale automated replication |