1. ® Sponsored by In Location Alliance Coordination: architecture and use cases 95th OGC Technical Committee Andreas Wachter, ILA/Qualcomm George Percivall OGC 02 June 2015 Copyright © 2015 Open Geospatial Consortium

2. OGC ® OGC – InLocation Alliance (ILA) ILA and OGC Coordination based on an MoU –Potential joint activities to serve shared objectives of ILA and OGC –Discuss value of technology to end users and general market –ILA and OGC member experts from relevant working groups For OGC: L. Granholm, G. Conti, A. Trakas, G. Percivall ILA/OGC Indoor Workshop, Nov. 2014 – Actions –OGC Review of ILA architecture – public document –OGC Review ILA Use Cases - OGC members only –ILA Review of OGC Paper on creating City/Venue Models Copyright © 2015 Open Geospatial Consortium

3. Release 1.0

4.  The ILA System Architecture (SA) specifies the main components and interface requirements of a technology-independent system architecture for indoor location.  The SA has been designed to support a wide range of venues: from the very small (e.g. stand-alone business) to the very large (e.g. corporate campus) to the very distributed (e.g. worldwide retail chain).  The SA is based on open interfaces in order to support multi-vendor environments for indoor location.  While the SA in itself is generic and technology agnostic, the focus of the first public release of the SA is on Wi-Fi and BT.

6.  Mobile Device ◦An electronic device (nomadic or mobile) whose location within a venue is of interest to a location client residing on the Mobile Device or in the network.  Location Server ◦A network server that provides a Mobile Device’s location to a location client and/or provides assistance data to the Mobile Device. A Location Server generally supports both position calculation as well as assistance data provision.  Access/Location Network ◦Any network that can be used for location but with current focus on Wi- Fi and BT.  Access Location Network Database ◦A network data base that stores and provides an Access/Location Network almanac to the Location Server. The Location Server may use this information to calculate the Mobile Device’s position and/or to provide assistance data to the Mobile Device.

7.  Map Database ◦A network data base that stores and provides map data used for location and/or presentation.  LBS Application Server ◦A network server that provides location related content and services to a requesting entity and that is able to request and receive the position of a Mobile Device whose position is the subject of the location related content.  Privacy Policy Database ◦A network data base that records and provides to the Location Server the privacy policies affecting a Mobile Device.

8.  The ILA SA Interfaces are intended to be open interfaces enabling interoperability in a multi- vendor environment.  The ILA SA White Paper provides a high level definition of the information that ILA Network Elements exchange across these interfaces.  The ILA does not define the ILA SA Interfaces itself but is working with external Standards Developing Organizations to develop these interfaces (e.g. OMA for Interface 3 and 5, IEEE and BT SIG for Interface 2).

10.  The ILA SA White Paper provides high level end- to-end system level definitions using message flow diagrams for typical use cases.  Example: Location Aware Content

11.  The ILA will continue to drive the architecture for indoor location based on market requirements and lessons learned from actual deployments.  The ILA will continue to work with external SDOs to create open interface specifications supporting and enabling the ILA architecture.

12. OGC ® OGC Review of ILA Architecture ILA invites OGC member comments on the ILA System Architecture Specifications Release 1.0. –Posted to pending as OGC 15-017 –https://portal.opengeospatial.org/files/?artifact_id=62850https://portal.opengeospatial.org/files/?artifact_id=62850 Of particular interest: comments that relate OGC standards to the ILA architecture –For example, please comment on which OGC standards are relevant to the numbered interfaces in the ILA Architecture –In Figure 1 and the associated text it is appropriate to interpret “Map Database” to be a source of any geospatial content, e.g., maps, features, coverages. Please send comments to George Percivall before 22 May 2015 so they can be discussed in Boulder. –Comments from Carl Reed in the following pages Copyright © 2015 Open Geospatial Consortium

13. OGC ® Initial OGC comments on ILA Architecture (Reed 1/2) Section 6.5 – Map –“well-known coordinate system” should be “well-known coordinate reference system” –“map information can be used for...” section can be enhanced, e.g., least, indoor navigation should be added Section 7.2 and 8.1 – Interface 2 –Many of the IETF RFCs dealing with mobile location would be relevant here. These include: HELD, LoST, PIDF-LO, and location enabled SIP Section 7.3 and 8.2 – Interface 3 –SWE, SensorThings, above IETF RFCs Section 7.4 and 8.3 – Interface 4 –OLS. SWE. InDoorGML, IETF URI mapping RFCs. –Given the data fusion requirements, GML and GML application schemas –Moving Features. Copyright © 2015 Open Geospatial Consortium

14. OGC ® Initial OGC comments on ILA Architecture (C. Reed 1/3) Section 8.3 – Interface 6 – proprietary data –“ Some or all of the data (i.e., AD, crowdsourced data, etc.) may be proprietary i.e., use proprietary format and encoding”. –Not clear why handling of proprietary data motivates the use of proprietary data formats and encodings Section 8.3 – Interface 6 – concepts and names –“Maps, e.g. access point locations, heat maps, etc. will utilize standardized map formats.” –Don’t use “map” unless talking about a picture of data; mostly are referring to geospatial content or location enabled content; much better stating that standard content/data models are required. –For example, the Location Object model and encoding as used by the IETF (which happens to be a GML encoding). By using vendor and encoding pattern neutral models, then any number of encodings (XML, JSON, JAVA, etc) can be used. Copyright © 2015 Open Geospatial Consortium

15. OGC ® Initial OGC comments on ILA Architecture (C. Reed 2/3) Section 8.3 – Interface 6 – Topology –“Maps that are used for route determination require as a minimum the relationships between nodes and paths, or shall contain geometric descriptions of spaces related to nodes.” –Navigation and routing require topology along with properties (e.g. speed limits) at nodes and along edges that bound or provide rules for the actual routing algorithm. –Recommend using terms consistent with existing international standards (OGC, ISO, IETF) Section 7.5 – Interface 5 –OLS, Open GeoSMS?, WPS, 3dPS? Section 7.6 – Interface 6 –WMS, InDoorGML, CityGML, Simple Features, GML, SLD Section 7.7 – Interface 7 –InDoorGML, CityGML, Simple Features, GML Copyright © 2015 Open Geospatial Consortium

16. OGC ® OGC review of ILA Use Cases (document is OGC member-only information) ILA invites OGC comments on “ILA Use Case and Eco System Analysis” –Posted to pending as OGC 15-036 –https://portal.opengeospatial.org/files/?artifact_id=63274&version=1 Please send your comments to George Percivall, (gpercivall@opengeospatial.org) before 26 June 2015. The ILA Use Case document must be treated as OGC Member information. Copyright © 2015 Open Geospatial Consortium

17. OGC ® Action – Comment on ILA documents ILA System Architecture Specifications Release 1.0. –Posted to pending as OGC 15-017 –https://portal.opengeospatial.org/files/?artifact_id=62850https://portal.opengeospatial.org/files/?artifact_id=62850 ILA Use Case and Eco System Analysis –Posted to pending as OGC 15-036 –https://portal.opengeospatial.org/files/?artifact_id=63274https://portal.opengeospatial.org/files/?artifact_id=63274 Please send your comments before 26 June 2015 –to George Percivall, (gpercivall@opengeospatial.org) Copyright © 2015 Open Geospatial Consortium