Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

2.5.4 Get an Address Location

Office

This use case, illustrated in the following diagram, describes the Location Information Web Service interface that is used by protocol clients to retrieve a civic address location. Locations are associated with network identifiers that allow varying degrees of detail. If the client network identifiers are updated, a new request is invoked to the Location Information Server. This section follows the behavior described in product behavior note.<16>

MS-OCSPROT_pict7896040c-fffb-44c6-8b9f-a909de761945.png

Figure 9: Steps for getting an address location

References

Preconditions

  • The protocol client obtains the FQDN of the protocol server.

Steps

  1. The protocol client sends an HTTPS-SOAP GetLocations request to the protocol server, as described in [MS-E911WS]. The request includes network identifiers as an input for locations.

  2. The protocol server returns an HTTPS-SOAP GetLocations response, as described in [MS-E911WS].The locations description includes a list of civic addresses. If the list includes more than one address, then the protocol client selects one address, based on the user’s input.

Post-conditions

  • The protocol client caches its location and uses it in services that depend on location, such as an emergency call.

Show:
© 2015 Microsoft