ISO 15075-2003 Transport information and control systems - In-vehicle navigation systems - Communications message set requirements《运输信息和控制系统 车载导航系统 通信信息集要求》.pdf

《ISO 15075-2003 Transport information and control systems - In-vehicle navigation systems - Communications message set requirements《运输信息和控制系统 车载导航系统 通信信息集要求》.pdf》由会员分享，可在线阅读，更多相关《ISO 15075-2003 Transport information and control systems - In-vehicle navigation systems - Communications message set requirements《运输信息和控制系统 车载导航系统 通信信息集要求》.pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO 15075:2003(E) ISO 2003INTERNATIONAL STANDARD ISO 15075 First edition 2003-12-01Transport information and control systems In-vehicle navigation systems Communications message set requirements Systmes de commande et dinformation des transports Systmes de navigation dans les vhicu

2、les Exigences relatives lensemble des messages des communications ISO 15075:2003(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed

3、 to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the s

4、oftware 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 i

5、t is found, please inform the Central Secretariat at the address given below. ISO 2003 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 permi

6、ssion in writing from either ISO at the address below or ISOs 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 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2003 All rights reser

7、vedISO 15075:2003(E) ISO 2003 All rights reserved iiiForeword 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. E

8、ach 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 Internati

9、onal 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 Standa

10、rds 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. Attention is drawn to the possibility that some of the elements of this document may be the subject

11、 of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 15075 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems. INTERNATIONAL STANDARD ISO 15075:2003(E) ISO 2003 All rights reserved 1Transport information and control system

12、s In-vehicle navigation systems Communications message set requirements 1 Scope This International Standard specifies message content and format utilized by in-vehicle navigation systems. Its emphasis is on messages that are required to generate or enhance routing instructions. There is a particular

13、 focus on messages that would not necessarily be included in a more general traffic management message list. Although this International Standard emphasizes requirements for Locally Determined Route Guidance (LDRG) systems that utilize on-vehicle map databases, it also includes messages that would b

14、e utilized primarily by Centrally Determined Route Guidance (CDRG) systems and certain value-added messages. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 2.1 Locally Determined Route Guidance System LDRG system which provides a driver with ste

15、p-by-step driving instructions that are determined by an on-vehicle system NOTE The system typically consists of a display screen, a computer, routing and guidance software, a navigable map database, and positioning equipment to track the vehicles location as it proceeds along its path. 2.2 Centrall

16、y Determined Route Guidance System CDRG system which provides a driver with step-by-step driving instructions that are similar to those offered by a LDRG NOTE With a centrally determined system, the routing instructions are determined at an off-vehicle location and transmitted to the vehicle. 2.3 me

17、ssage data element which is formatted for transmission and broadcast by means of electromagnetic field propagation ISO 15075:2003(E) 2 ISO 2003 All rights reserved2.4 standard location references standardized method for referencing geographic locations including points, links between points and geog

18、raphic areas 1)2.5 traffic message centre TMC centre that transmits (receives) messages to (from) the vehicle by any communication means other than short range, vehicle-to-roadside communications (beacons) NOTE The bulk of these messages are expected to be traffic related. 2.6 roadside beacon RS sho

19、rt-range vehicle-to-roadside communication device with the inherent location feature that if the vehicle is receiving the signal, then the vehicle has to be positioned in a specific, localized area 3 Message set: Contents and format The messages in this International Standard are divided into three

20、categories, as follows. Messages that are required by route guidance systems to determine their recommended routes on-board the vehicle (LOCALLY DETERMINED). These address a wide range of information such as traffic conditions, tolls, road construction and availability of parking. Messages that are

21、required by route guidance systems for which routes are determined off-board the vehicle (CENTRALLY DETERMINED). These primarily focus on requesting and transmitting routing information. VALUE-ADDED messages that could be displayed by an in-vehicle navigation system, routed through a system, or util

22、ized by a system in providing guidance. These include messages for communicating information regarding items such as emergencies, toll and fee payments, and ridesharing. Tables 1, 2 and 3 consist of message contents and formats for locally determined route guidance systems, centrally determined rout

23、e guidance systems, and value-added messages. The structure of the tables is as follows. Item number: The alphanumeric number assigned to a message by ISO/TC 204. This signifies the messages relative position in the list and its classification: L = LDRG; C = CDRG; V = value added Message: A brief de

24、scription of the message. Data flow: IN means flow into the vehicle (navigation system) from the infrastructure (communication device); OUT means flow to the infrastructure (communication device) from the vehicle (navigation system). See Figure 1. 1) ITS standards for location referencing are being

25、developed within both CEN/TC 278, SWG 7.3, and ISO/TC 204, SWG 3.3. Oak Ridge National Laboratories in the US are working on a standard location message protocol. Japan utilizes a standard referencing system devised by the Japan Kokudo-Chiri-In. The field size estimates for location references in th

26、is International Standard are based on preliminary drafts from these efforts. ISO 15075:2003(E) ISO 2003 All rights reserved 3Data fields comprising the message: Description of the specific data fields required for the message. Note that this International Standard uses the same data fields in a mod

27、ular way to create different messages. Field type: A = alphanumeric; F = floating point; I = integer; V = variable Required field size: Specified in bits. Field format: F = fixed length; V = variable length Key 1 communication device 2 in-vehicle application 3 navigation system aIn bOut Figure 1 ISO

28、 15075:2003(E) 4 ISO 2003 All rights reservedTable 1 Messages used by locally determined route guidance systems Item No. Message Data flow Data fields comprising the message Field type Required field size Field format Message code general use by TMC or roadside (RS) beacon l 16 F Sequence number l 6

29、 F Message time stamp (1 s resolution) l 17 F Data format code congestion levels, link travel times, travel time deltas, or time/speed factors (ratios). l 3 F Number (L) of 5 min time segments per link (L u 6)(1st = current; 2nd = predicted 5 min later; etc.) l 3 F Standard location reference for a

30、geographic area (1) l 64 F Number (N) of links being reported in the message repeated group: N times l 8 F standard location reference for the link (1) l 64 F cause code type (2 bits: 00 = not specified) l 2 F cause code (optional) repeated group: L times l 6 F 1L Dynamic link times from traffic mes

31、sage centre (TMC) IN Travel information for 5 min interval l V V Message code (for use by RS beacons) l 16 F Sequence number l 6 F Message time stamp (1 s resolution) l 17 F Beacon pair identification (40) controller number l 8 F first beacon (location) ID number l 16 F second beacons ID (for inform

32、ation supplied in pairs) l 16 F Data format code congestion levels, link travel times, travel time deltas, or time/speed factors (ratios) l 3 F Number (L) of 5 min time segments per link (L u 6) l 3 F Number (N) of links being reported in the messagerepeated group: N times l 8 F standard location re

33、ference for the link (1) l 64 F cause code type (2 bits: 00 = not specified) l 2 F cause code (optional) repeated group: L times l 6 F 2L Dynamic link times from roadside beacons (RS) (Applicable to beacons only) IN from RS Travel information for 5 min interval l V V Message code (from vehicle to TM

34、C or RS beacon) l 16 F 3L Request for temporary vehicle ID OUT Transaction number (random) chosen by vehicle l 16 F ISO 15075:2003(E) ISO 2003 All rights reserved 5Table 1 (continued) Item No. Message Data flow Data fields comprising the message Field type Required field size Field format Message co

35、de (from TMC or RS beacon to vehicle) l 16 F Transaction number sent by the vehicle l 16 F Temporary vehicle ID assigned by TMC or RS beacon (40) flag indicating ID was assigned by TMC (0) or RS beacon (1) l 1 F asssigned vehicle ID l 39 F 4L Assignment of temporary vehicle ID IN NOTE Japan uses the

36、 transaction number as the first 16 bits and then adds 23 bits as a beacon assigned ID. Message code (general use to TMC or RS beacon) l 16 F Assigned vehicle ID l 40 F Link database version l 4 F Number (N) of links being reported in the message repeated group: N times l 8 F standard location refer

37、ence for the link (1) l 64 F cause code type (2 bits: 00 = not specified) l 2 F cause code optional: “time-out” while on link, ignition off while on link, traffic patterns (TBD codes) l 5 F travel time (in s) l 12 F waiting (stopped) time (in s); FFF means no data are available l 12 F 5L Vehicle pro

38、be reports (database link travel times) OUT end-of-link travel time stamp (1 s resolution) l 17 F Message code (general use to TMC or RS beacon) l 16 F Assigned vehicle ID l 40 F Vehicle measured travelling time (from previous location (beacon) (40) beacon number (site Identification) for previously

39、 passed beacon (24) beacon controller number l 8 F beacon (location) ID number l 16 F 6L Vehicle probe reports (beacon-to- beacon travel times) OUT vehicle determined elapsed travel time (in s) between beacon l 16 F ISO 15075:2003(E) 6 ISO 2003 All rights reservedTable 1 (continued) Item No. Message

40、 Data flow Data fields comprising the message Field type Required field size Field format Message code l 16 F Number (N) of exception rules reported in this messagerepeated group: N times l 5 F exception rule code (1, 2, 3 or 4) l 2 F IF 1 (roadway type): roadway type code l 4 F threshold value l 6

41、F IF 2 (zone): zone code ID l 11 F threshold value l 6 F IF 3 (links): Number (n) of links in the message repeated group: n times l 6 F standard location reference for the link (1) l 64 F threshold values l 6 F IF 4 (global): 7L Probe exception reporting rules (may vary by roadway type, zones, links

42、, etc.) IN thresholds for the whole system l 6 F Message code l 16 F 8L Request for origin, destination and route IN Assigned vehicle ID l 40 F Message code l 16 F Assigned vehicle ID l 49 F Origin standard location reference (1) l 64 F Destination standard location reference (1) l 64 F Number (N) o

43、f en route links being reported (00 = No route reported) repeated group: N times l 16 F standard location references for the links (1) l N*64 F 9L Reporting origin, destination and route IN NOTE This message can be used to report origin- destination pair and (optional) planned route for either local

44、ly or centrally determined systems. Message code l 16 F Assigned vehicle ID l 40 F Origin standard location reference (1) l 64 F Destination standard location reference (1) l 64 F 10L Report of trip completion OUT Travel time (1 min resolution) l 16 F ISO 15075:2003(E) ISO 2003 All rights reserved 7

45、Table 1 (continued) Item No. Message Data flow Data fields comprising the message Field type Required field size Field format Message code l 16 F 11L Request for vehicles current position IN Assigned vehicle ID l 40 F Message code l 16 F Assigned vehicle ID l 40 F 12L Reporting current vehicle posit

46、ion OUT standard location reference for current vehicle position (1) l 64 F Message code l 16 F Beacon pair identification (site identification) (40) controller number l 8 F first beacons (location) ID number l 16 F second beacons ID (supplied in pairs) l 16 F Beacon location standard location refer

47、ence (1) l 64 F 13L Position report from RS beacon (standard location reference) (Applicable to beacons only) IN from RS offset from reference point (1 m resolution) l 16 F Message code l 16 F Beacon pair Identification (site Identification) (40) controller number l 8 F first beacons (location) ID n

48、umber l 16 F second beacons ID (supplied in pairs) l 16 F Beacon number (site Identification) (1 or 24) V beacon controller number l 8 extension number (0 = end of repetition) l 1 F beacon (location) ID number l 15 F Beacon location map version l 16 F standard location reference for the beacon (1) l

49、 64 F road type l 2 F link number l 12 F road name number of characters for display: o l 8 F number of characters for phonetic output: p l 8 F road name for display l 8*o V road name for phonetic output l 8*p V point name: number of characters for display: q l 8 F number of characters for phonetic output: r l 8 F point name for display A 8*q V 14L Position repor