Navigation data delivery structures and protocols

ISO 24099:2011 defines the data structures and protocol(s) used in intelligent transport system (ITS) applications for the delivery and update of map-related data from Service Centre (SC) to users [(In-vehicle Systems (IVS)]. ISO 24099:2011 also specifies the message generation protocols in the Service Centre and the message receiving protocols in the In‑vehicle Systems. The map centre specified in ISO 24099:2011 represents the supplier of map data and the Service Centre provides data and services to user devices. The term protocol as used in ISO 24099:2011 is a temporal sequence of map-related data interactions between system components that implement map-related data delivery and update. The delivery and update of map-related data rely on existing communication technology. The protocols associated with communication technology, and the other application control protocols and non-map-related data, for example images to display independent of the map database such as HTML images, are outside the scope of ISO 24099:2011. Definitions of security mechanisms and business transaction mechanisms are also outside the scope of ISO 24099:2011.

Structures et protocoles pour la diffusion de données dans les systèmes de navigation

General Information

Status
Published
Publication Date
05-Jan-2011
Current Stage
9093 - International Standard confirmed
Start Date
22-Feb-2023
Completion Date
22-Feb-2023
Ref Project

Buy Standard

Standard
ISO 24099:2011 - Navigation data delivery structures and protocols
English language
52 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO
STANDARD 24099
First edition
2011-01-15
Navigation data delivery structures and
protocols
Structures et protocoles pour la diffusion de données dans les systèmes
de navigation
Reference number
©
ISO 2011
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2011 – All rights reserved

Contents Page
Foreword .v
Introduction.vi
1 Scope.1
2 Conformance .2
3 Terms and definitions .2
4 UML Expressions for diagrams .4
5 Abbreviated terms.4
6 Requirements.5
6.1 User-related requirements.5
6.2 Data requirements.5
6.3 Protocol requirements .6
6.4 Communication requirements .6
6.5 Update strategies .6
6.6 Others .7
7 Reference architecture and framework concept.7
7.1 Reference architecture.7
7.2 Framework concept.9
7.2.1 Varieties of updates .9
7.2.2 Case of update by geographic area.9
7.2.3 Case of incremental update .11
7.2.4 Descriptions of the exchange process of updating data .12
7.2.5 Methods for specifying update data by users or centre .14
7.2.6 Rules for specifying the objects to be replaced or deleted (Rules for identifiers).14
7.2.7 Version control .15
8 Protocols .15
8.1 Introduction.15
8.2 Protocol for an In-vehicle-System-Triggered system delivering map data or POI data .16
8.3 Protocol for an In-vehicle-System-Triggered system delivering status data.17
8.4 Protocol for a Service-Centre-Triggered system delivering map data, POI data or status
data .18
8.5 Protocol for a Service-Centre-Triggered system delivering emergency data.19
8.6 Definitions of messages used in the protocols .20
9 Data structures .21
9.1 Introduction.21
9.2 Class: Update target_identifier .21
9.3 Class: Area_ID .22
9.4 Class: Content_ID.22
9.5 Class: Version.22
9.6 Class: Area_version.23
9.7 Class: Content_version .23
9.8 Class: Operation.23
9.9 Class: Request_to_send_data .24
9.10 Class: With_or_without_data .24
9.11 Class: Data_size .24
9.12 Class: Kind_of_content .25
9.13 Class: Emergency_data_identifier.25
9.14 Class: Main_data .25
Annex A (normative) Abstract test suite. 26
Annex B (informative) Description of UML expression elements . 27
Annex C (informative) Use cases. 29
Annex D (informative) Examples of protocols for each update . 35
Annex E (informative) Example of a data update operation . 50
Bibliography. 52

iv © ISO 2011 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
ISO 24099 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
Introduction
This International Standard was developed in relation to growing market demand for dynamic update services
for map-related data in navigation systems. Map-related data includes not only feature geometry and
attributes but also point of interest (POI) data such as hotels, restaurants, and dynamic content such as traffic,
weather, movie schedules, parking availability, etc. Currently, most map data updates are provided on
physical media whose map data content begins aging rapidly once it is delivered to the user. In the future, it is
anticipated that the transmission of these data will most often, but not exclusively, be via wireless means. The
advantage of wireless data delivery is that it simplifies the distribution logistics thereby accelerating the ability
of a consumer to receive fresher data. This International Standard facilitates the potential for on-demand
updates of on-board map databases. Further, the updates do not necessarily require the replacement of an
entire map database. Rather, the updates can be limited to a portion of a dataset or a specific list of attributes
or POI changes can also be provided.
The services described above have begun to be deployed in a non-interoperable manner by various car
manufacturers and information system providers. This International Standard is intended to promote the
successful widespread adoption of such services through user access to an interoperable network of servers
offering more content choices than is available through a single provider.
This International Standard defines the data structures and protocol needed to enable interoperability between
multiple content providers and consumers of map-related data content in a wireless environment. As far as
possible the data structures are compatible with the ISO geographic data file (GDF) data model. Different
software profiles can be developed to support various system configurations: systems which store all data in
the vehicle (on-board), systems which store all data in a central server (off-board), and systems which use
both on-board and off-board data storage (hybrid).
Furthermore, this International Standard is designed to utilize the communications protocols such as those
under development in TC 204/WG 16. This International Standard recognizes the possible need for security
mechanisms in the provision of this data.
The International Organization for Standardization (ISO) draws attention to the fact that it is claimed that
compliance with this document may involve the use of a patent concerning procedures, methods and/or
formats given in this document.
ISO takes no position concerning the evidence, validity and scope of this patent right.
The holder of this patent right has assured ISO that he/she is willing to negotiate licences under reasonable
and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the
statement of the holder of this patent right is registered with ISO. Information may be obtained from:
INCREMENT P CORPORATION (iPC) 1-7-1 Shimomeguro, Meguro-ku, Tokyo 153-8665, Japan
Hitachi, Ltd. 6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo 100-8280, Japan
NAVTEQ 425 W Randolph St, Chicago IL 60606, USA
Nissan Motor Co., Ltd. 17-1, Ginza 6-chome, Chuo-ku, Tokyo 104-8023, Japan
Toyota Motor Corporation 1 Toyota-Cho, Toyota City, Aichi Prefecture 471-8571, Japan
Xanavi Informatics Corporation 6-35, Hironodai 2-chome, Zama-shi, Kanagawa-ken 228-0012, Japan
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights other than those identified above. ISO shall not be held responsible for identifying any or all such patent
rights.
vi © ISO 2011 – All rights reserved

ISO
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.