ISO 17438-4:2019 pdf download – Intelligent transport systems – Indoor navigation for personal and vehicle ITS station
1 Scope
This document defines detailed use cases, requirements and message specifications for supporting indoor navigation functionality between a personal/vehicle (P/V) ITS station and a central ITS station.
This document defines:
a) Clusters of use cases based on processing flows for indoor navigation between a P/V ITS station and a central ITS station;
b) Detailed use cases derived from the clusters of use cases for indoor navigation;
c) Message specifications to support some of the detailed use cases. The message specifications include mandatory, conditional and optional elements.
This document is only applicable to the core flow for the navigational functionality in indoor space. The following issues which are adjunctive but essential for commercial navigation services are beyond the scope of this document:
-Authorized and authenticated access of users and services, including security;
-Payment;
-Preparation of indoor data which are necessary for indoor navigation;
– Detailed data formats for indoor navigation data, including indoor maps and indoor positioning references (these form a part of ISO 17438-21) and ISO 17438-32);
-How to transfer and share data required for indoor navigation between a roadside ITS station and a central ITS station, i.e. low-level communication protocols;
-Other issues dependent on implementation of an instance of indoor navigation, e.g. indoor-outdoor seamless navigation.
This document uses the XML and Data eXchange Message (DXM) format defined in ISO 13184-2 to encode defined messages.
Because of the existence of indoor spaces, to provide navigation functionality, indoor navigation requires access to more data:
-Indoor positioning reference
Unlike GNSS, many indoor positioning technologies require additional data to support positioning. For example, indoor positioning using WiFi or WLAN infrastructure, which is most frequently mentioned, requires information related to access point devices installed in target indoor spaces or a radio-signal fingerprint map constructed in the target indoor spaces. Other indoor positioning technologies, such as Bluetooth Low Energy (BLE) beacons or Radio-Frequency Identification (RFID) tags, are similar. Geomagnetic indoor positioning also requires a fingerprint map on the strength of the geomagnetic fields in the indoor spaces. Detailed composition of indoor positioning reference data is dependent on indoor positioning technologies.
– Indoor map
Various types of indoor maps, including indoor networks, cells, POIs and background maps, are required for planning routes in indoor spaces and for guidance. Therefore, fundamental functionalities to support indoor navigation need to include the following:
-Identification of indoor spaces to be involved in navigation;
Search and retrieval, or access, of/to indoor maps and indoor positioning reference.
Indoor navigation can be implemented in client-based forms or server-based forms according to various aspects such as accessibility to indoor maps or indoor positioning references to each indoor space. In this document, specific use cases for client-based indoor navigation and server-based indoor navigation including the basic functionalities mentioned above are defined in Clause Z. In Clause 8, message definitions for some use cases defined in Clause Z are shown. An example scenario of an indoor navigation using defined use cases and messages is given in Annex C.