1 / 19

Location GE webinar 6 th June 2013

Location GE webinar 6 th June 2013. Who are we?. A leading partner in Galileo Lead the system design & security team End-to-end system integration Prime contractor for the ground segment A key partner for the space segment Satellite integration Subsystems: power, thermal, structure

daquan-neal
Download Presentation

Location GE webinar 6 th June 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Location GE webinar6th June 2013

  2. Who are we? • A leading partner in Galileo • Lead the system design & security team • End-to-end system integration • Prime contractor for the ground segment • A key partner for the space segment • Satellite integration • Subsystems: power, thermal, structure • Critical equipments: signal, security, control • Thales Alenia Space is the prime contractor of EGNOS • Commissioned in 2005 and operational (2006) • Superior performances with full availability • Certification achieved • 15 years experience/heritage in LBS Europe #1 in Satellite systems World #1 in commercial payloads European #1 for Space Defense European #1 for European Navigation systems Outstanding assets in Science & Exploration Advanced technologies for Earth Observation • High & very high resolution optical & radar instruments • LEO platforms • World leader in meteorology and oceanography Key player in orbital Infrastructures & Transportation

  3. Location GE • GNSS assistance to terminals • Location retrieval of terminals • OMA Terminal Location (RestFul) • Location methods • AGNSS • WiFi • Cell-ID • Qop manager (R3) • Selection of best location method • Selection of best position retrieved, fallbacks

  4. Location GE – SLC • Main features • Client application interface via Terminal Location 1.0 • Mobile terminal interface via OMA SUPL 2.0 • LCS service provider / service control and authorisation • Authorisation based on privacy policy per LCS service • Location method selection and triggering • Client application interface (Terminal Location) • RESTful, resource-oriented API • Compliant to OMA-TS-REST_NetAPI_TerminalLocation V1.0 • In the scope of FIWARE, a subset of the normalized services is selected: • Location Query: one-shot localisation (R1) • Periodic subscription: tracking (R2) • Area subscription: geo-fencing (R2)

  5. Location GE SPC • Assistance GNSS • Improved TTFF • Improved GNSS chipset sensitivity • Integration of SBAS in fix calculation • Integrity • Differential corrections • WiFi • Localisation based on access points in reach • Optional triangulation based received power • Hotspot database to be provided by operator/sub • CID • Basic association of GSM identifiers with internal cell position/radius • Database to be provided by operator

  6. Testing • Fleet management tool (R2.2) • Simulates a fleet of terminals following routes • Facilitates the demonstration of one-shot and subscriptions scenarios in a controlled environment (simulation) • Dedicated API for terminal management • Dedicated API for scenario management • API documented in Location GE test plan • Android app • Implements a SUPLv2 agent in an Android phone • Facilitates the demonstration of one-shot localisation (R2.3) with real terminals • Will facilitate the demonstration of subscriptions (R3) with real terminals

  7. Terminal Location API

  8. REST Location Resources

  9. Location Query Parameters

  10. Location Query Scenario (1) http://{serverRoot}/location/{apiVersion}/queries/location

  11. Location Query Scenario (2) • Outline of flow • An application requests the location of terminals by using GET with the resource URL and providing: • Authentication attributes • Terminal destination address (MSISDN) • QOP (age, accuracy, delay) • SLC triggers the request to SUPL terminal, specifying selected location method to use for that session • Upon terminal response, SLC returns location to requestor

  12. Location Query Examples Request Response

  13. Area Notification Subscription Params

  14. Area Notification Subscription Params

  15. Area Notification Subscription Scenario (1) http://{server root}/location/{apiVersion}/subscriptions/area/circle/{subscriptionId}

  16. Area Notification Subscription Scenario (2) • Outline of flow: • An application creates a new notification subscription for the requesting client by using POST and receives the resulting resource URL containing subscriptionId • SLC triggers SUPL session with target terminal for SUPL V2 Area Event Trigger request • When the terminal crosses in or out the specified area (circle), the REST service on the server notifies the application of current location information using POST to the application supplied notifyURL • Optionally, an application deletes a subscription for periodic location notification and stops notifications for a particular client by using DELETE to resource URL containing subscriptionId

  17. Area Notification Subscription Examples Request

  18. Area Notification Subscription Examples Subscription notification

  19. Thank youContacts: Rémi Challamel, Tanguy Bourgault

More Related