SAE J 2539-2002 Comparison of GATS Messages to SAE ATIS Standards《GATS信息和SAE ATIS标准的对比》.pdf

《SAE J 2539-2002 Comparison of GATS Messages to SAE ATIS Standards《GATS信息和SAE ATIS标准的对比》.pdf》由会员分享，可在线阅读，更多相关《SAE J 2539-2002 Comparison of GATS Messages to SAE ATIS Standards《GATS信息和SAE ATIS标准的对比》.pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirelyvoluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefro

2、m, is the sole responsibility of the user.”SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.TO PLACE A DOCUMENT ORDER: +1 (724) 776-4970 FAX: +1 (724) 776-0790SAE WEB ADDRESS http:

3、/www.sae.orgCopyright 2002 Society of Automotive Engineers, Inc.All rights reserved. Printed in U.S.A.SURFACEVEHICLE400 Commonwealth Drive, Warrendale, PA 15096-0001INFORMATIONREPORTJ2539ISSUEDFEB2002Issued 2002-02Comparison of GATS Messages to SAE ATIS StandardsForewordThis SAE Information Report p

4、rovides a function by function comparison of the GATS implementation ofseveral ITS functions (covered in the U.S. by SAE Standards J2313, J2353, J2354, J2369, and J2374) and notesareas where harmonization opportunities exist. The purpose of this document is to serve the SAE ATISCommittee in its deli

5、berations regarding world ATIS harmonization.It is recommended that the reader also review the related PDF files of prENV ISO 14821 (Aug 5th, 1999) whichcontains the overview of the GATS messages. The full set of documents, containing about 6 inches of printedpaper, can be found on the SAE web site.

6、 SAE will not be repeating GATS material directly in this informationreport as it is copyrighted by CEN and the original authors. This document will be published as an SAE Information Report after committee acceptance. TABLE OF CONTENTS1. Scope . 22. References . 22.1 Applicable Publications 22.2 Re

7、lated Publications . 43. Definition 44. Overview 75. Taxonomy Comparisons. 85.1 The Big Picture. 85.2 MAYDAY (SAE J2313) . 105.3 Interactive Traffic Information Services (SAE J2354) . 105.4 Broadcast Traffic Information Services (SAE J2369) . 115.5 Navigation Services (SAE J2354) 125.6 Floating Car

8、Data Collection (So Called “Vehicle Probes”) 125.7 Information Services (SAE J2354 and J2369) 125.8 Parking Services (SAE J2354) . 125.9 Transit Services (SAE J2354, J2369, and NTCIP PI Std) 135.10 Weather Services (SAE J2354 and J2369) 13SAE J2539 Issued FEB2002-2-6. Detailed Comparisons 136.1 Some

9、 Common Concepts. 136.1.1 Languages 136.1.2 Basic Elements . 146.1.3 Tagging Formats.146.1.4 Location Referencing Formats (SAE J2374 and LRMS) 156.2 MAYDAY (SAE J2313) . 166.3 Interactive Traffic Information Services (SAE J2354) . 166.4 Broadcast Traffic Information Services (SAE J2369) 196.5 Naviga

10、tion Services (SAE J2354) .206.6 Floating Car Data Collection (So Called “Vehicle Probes”) 226.7 Information Services (SAE J2354 and J2369) 226.8 Parking Services (SAE J2354) . 236.9 Transit Services (SAE J2354, J2369 and NTCIP PI Std) . 246.10 Weather Services (SAE J2354 and J2369) 257. Recommended

11、 Changes to US ATIS . 258 Summary Recommendations . 27Figure 1 ATIS Interactive Traffic Messages 17Figure 2 ATIS Navigation Services Messages 20Figure 3 ATIS Messages for Preference Settings . 21Figure 4 ATIS Directory Messages . 23Figure 5 ATIS Messages for Parking Services . 24Figure 6 ATIS Messag

12、es for Parking Services . 24Table 1 EDIFACT Message Types from the early 1990s 171. ScopeThis SAE Information Report provides a comparative summary between the various messages foundin the SAE ATIS standards work (notably SAE J2313, J2353, J2354, J2369 and J2374) and that found in theGATS standard (

13、Global Automotive Telematics Standard). GATS is a message set meant to be deployed onmobile phone systems based on the GSM (Global System for Mobile Communication) phone system which isbeing deployed in European markets and which the SAE may need to harmonize with as part of the WorldStandards activ

14、ities of TC204. This document provides an overview of the various types of supportedmessages and how they compare with US terms and messages. Some selected features of the GATS workare recommended for assimilation into the next revision of ATIS standards. No attempt at determining a U.S.policy in th

15、is regard is provided. This document seeks to provide the reader familiar with SAE ATIS with a highlevel overview of technical knowledge of the GATS approach in similar areas. 2. References2.1 Applicable PublicationsThe following publications form a part of this specification to the extent specified

16、herein. Unless otherwise indicated, the latest version of SAE publications shall apply.2.1.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1746ISP-Vehicle Location Referencing StandardSAE J2313On-Board Land Vehicle Mayday Reporting Interface, Rev. 1.0, Se

17、ptember 1999SAE J2353Draft Standard: Data Dictionary for Advanced Traveler Information Systems (ATIS), Rev.1.0.0, October 1999SAE J2354Draft Standard: Message Sets for Advanced Traveler Information Systems (ATIS), Rev.1.0.0, September 1999SAE J2539 Issued FEB2002-3-SAE J2369Standards for ATIS Messag

18、e Sets Delivered Over Reduced Bandwidth MediaSAE J2374Information Report based on Location Reference Message Specification, Rev. B (MDI),May22, 1997SAE J2540Messages for Handling String and Look-up Tables in ATIS Standards2.1.2 ASN PUBLICATIONAvailable from ASN.1Abstract Syntax Notation 12.1.3 GATS

19、PUBLICATIONSAvailable from the GATS forum or from CEN TC278.GATS Message Set; Main Part Main2034.pdf 05.08.99GATS Message Set; Annex 1 - Numbering and ADP Message Header A1_2034.pdf 05.08.99GATS Message Set; Annex 2 - Basic Information Elements A2_2033.pdf 05.08.99GATS Message Set; Annex 3.1 - Servi

20、ce-Independent Protocols A31_2033.pdf 05.08.99GATS Message Set; Annex 3.2 - ADP for Service-Independent Messages A32_2033.pdf 05.08.99GATS Message Set; Annex 4.1.1 - Specification of Internal Services Configuration and Master DataUpdate A4112033.pdf 05.08.99GATS Message Set; Annex 4.1.2 - Specificat

21、ion of Key Management and Security A4122033.pdf05.08.99GATS Message Set; Annex 4.1.3 - ADP for CAS Functionality - Configuration and Key Management -A4132033.pdf 05.08.99GATS Message Set; Annex 4.2.1 - Specification of Diagnostic Services A4212033.pdf 05.08.99GATS Message Set; Annex 4.2.2 - ADP for

22、Diagnostic Services A4222033.pdf 05.08.99GATSMessageSet;Annex5.1.1-Specification Emergency Service and Break-down AssistanceA5112033.pdf 05.08.99GATS Message Set; Annex 5.1.2 - ADP Emergency and Breakdown Services A5122033.pdf 05.08.99GATS Message Set; Annex 5.2.1 - Specification Interactive Traffic

23、 Information Services A5212034.pdf05.08.99GATS Message Set; Annex 5.2.2 - Specification of Broadcast Traffic Information Services A5222033.pdf05.08.99GATS Message Set; Annex 5.2.3 - ADP Traffic Information Services A5232034.pdf 05.08.99GATS Message Set; Annex 5.3.1 - Specification Navigation Service

24、s A5312033.pdf 05.08.99GATS Message Set; Annex 5.3.2 - ADP Navigation Services A5322033.pdf 05.08.99GATS Message Set; Annex 5.4.1 - Specification Floating Car Data A5412034.pdf 05.08.99GATS Message Set; Annex 5.4.2 - ADP Floating Car Data A5422034.pdf 05.08.99GATS Message Set; Annex 5.5.1 - Specific

25、ation Operator Services A5512033.pdf 05.08.99GATS Message Set; Annex 5.5.2 - ADP for Operator Services A5522033.pdf 05.08.99GATS Message Set; Annex 5.6.1 - Specification General Information Services A5612034.pdf 05.08.99GATS Message Set; Annex 5.6.2 - ADP for General Information Services A5622034.pd

26、f 05.08.99GATS Message Set; Annex 6.1 - Minimum Onboard Positioning Performance Requirements for TrafficTelematics Terminal Devices A61_2033.pdf 05.08.99GATS Message Set; Annex 6.2 - Preparation of Extended Location Block A62_2033.pdf 05.08.99GATS Message Set; Annex 7.1 GSM specific Parameter A71_20

27、33.pdf 05.08.992.1.4 FHWA PUBLICATIONSAvailable from Lee Simmons, FHWA, HVH-1 Room 3400, 400 7th Street SW,Washington, D.C. 20590.National ITS Architecture, Federal Highway Administration, U.S. Department of Transportation, Version2.0, September 1998SAE J2539 Issued FEB2002-4-2.1.5 ITE PUBLICATIONSA

28、vailable from ITE, 525 School Street SW, Suite 410, Washington, DC 20024.Message Sets for External Traffic Management Center Communication (MS/ETMC2), TM 2.01, Rev. 2.0,September 19982.1.6 CEN PUBLICATIONSAvailable from CENTraffic and Traveler Information (TTI) TTI Messages via Traffic Message Codin

29、g- Part I: Coding protocolfor Radio Data Systems Traffic Message Channel (RDS-TMS) using ALERT-C2.1.7 ISO P UBLICATIONAvailable from ANSI, 25 West 43rd Street, New York, NY 10036-8002.ISO 9735Electronic data interchange for administration, commerce and transport (EDIFACT)Application level syntax rul

30、es (Amended and reprinted 1990)Amendment 1:1992 to ISO 9735:19882.1.8 NTCIP S TANDARDSAvailable from the Institute of Transportation Engineers (ITE), 1099 14th Street, NW,Suite 300 West | Washington, DC 20005-3438 USA, Telephone: +1 202-289-0222 | Fax: +1 202-289-7722.NTCIP 1403Standard on Passenger

31、 Information (PI) Objects2.2 Related PublicationsThe following publications are provided for information purposes only and are not arequired part of this document.2.2.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1761Information Report, ITS Terms and De

32、finitions, 1995SAE J2369-1Draft of Host Adaptation Annexes, June 19993. Definitions3.1 ADPApplication Data Protocol, i.e., a message set for a telematics service.3.2 AMPSAnalog Mobile Phone Systems, an analog modulation system (e.g., the native modulation used is notformed of digital data packets) w

33、hich was first deployed in the US market.3.3 ASN.1Abstract Syntax Notation One, a set of formatting and expression rules suitable for defining messageswhich the US has agreed to publish its standards in and which are also used by TC204. The messages anddata elements found in both SAE J documents and

34、 GATS documents are now published in ASN.1 formatting. 3.4 ATISAdvanced Traveler Information Systems. The name of the committee within the SAE which is chargedwith the “last mile” message formats which are presented to consumers of ITS information. 3.5 BIFBAPBearer Independent Format and Bearer Appl

35、ication Protocol, terminology used to indicate a twostep process of first developing the messages (the BIF) then tailoring those messages to a specific applicationand media which will bear it. Although this terminology is most used among European practitioners andamong some ENTERPRISE States, it con

36、ceptually was the format followed in developing US ATIS. In thisprocess, SAE J2354 was developed without regard to media restrictions. Other efforts such as SAE J2369were expressly developed for the restricted bandwidth limits found in mobile media such as sub carriers.GATS on the other hand was dev

37、eloped from the beginning to be hosted on GSM phone technology and istoday attempting to use same formats and messages on other media.3.6 Broadcast ServicesIn the GSM sense a packet which is sent to all users in a coverage area (rather thanaddressed to a specific end terminal device in a point to po

38、int fashion). SAE J2539 Issued FEB2002-5-3.7 EDIFACTElectronic Data Interchange For Administration, Commerce and Transport Early European work inITS was formatting in accordance with the EDIFACT Syntax (ISO 9735), but it is now being replaced with theuse of ASN.1 formatting. 3.8 GATSGlobal Automotiv

39、e Telematics Standard. A mobile phone system based on the GSM (Global Systemfor Mobile Communication) phone system deployed in Germany and other areas of Europe. The GATSsystem provides a message set which offers many of the same services in US ITS-ATIS. GATS is beingadvanced by the CEN TC278 proces

40、s as a standard.3.9 GSMGlobal System for Mobile Communication a digital phone systems deployed in Europe and whichprovides a short datagram message service upon which GATS is built. 3.10 ILOCIntersection Location, An Intersection Location (ILOC) exists where two or more intersecting roads withdiffer

41、ent road attributes meet, and on a road at the point of a road attribute change, i.e., a road number or roadname change.3.11 Interactive ServicesIn GSM this refers to services which the user interfaces with menu and other displayplaced on the GSM phone to request specific information. GATS provide a

42、 number of specifications regardingsuch “end application” whereas the SAE work is limit to only the message sets, leaving the actual applicationup to the implementers.3.12 Information Service Provider (ISP)In the context of the ITS, a public or private entity which may beresponsible for gathering, f

43、using, analyzing, and/or reporting transportation related information to users,including vehicles and non-mobile users. In the sense of GATS the ISP is closely aligned (if not the sameentity as) the controller of the gateway which interacts with the end using GATS terminals. 3.13 LRMSLocation Refere

44、ncing Message SetA body of work outlining a number of “profiles” used in thedescription of affected areas, typically roadway segments. The preferred methodology for use in ATIS is theISP Vehicle profile (SAE J1746) which provides a mean to send Lat-Long values between the ISP and thevehicle. A highl

45、y compressed form of this is the GRID profile which is suitable for limited bandwidthapplications. Indexing values, which typically require prior agreement between users, are called Geometryprofiles in this body of work. A standard (SAE J1746) is now being developed in this area to use indexes.3.14

46、MLOCManeuver Location, Defined by the ERTICO Committee on Location Referencing Report as “Eachmaneuver involves three ILOCS: the starting ILOC of the maneuver, the intermediate ILOC that contains theroad in question, and the ending ILOC of the maneuver. The relationship describing an affected maneuv

47、er iscalled a Maneuver Location (MLOC).”3.15 NANational ITS Architecture, the body of the US FHWA sponsored work outlining the US overall architecturefor the ITS systems. This large effort, from which the SAE and other participating SDOs have developedmessage interface standards, has been widely dup

48、licated under local government sponsorship in other partsof the world.3.16 NTCIPNational Transportation Communications for ITS Protocol, NTCIP is the U.S. body of work concernedwith roadside devices and many of the actual equipment systems used in the roadway side of ITS. Some ofthese devices, for e

49、xample a roadside changeable message sign, can contain the same information found inGATS and ATIS roadway advisory messages. 3.17 PSAPPublic Safety Answering Point, U.S. nomenclature for the entity which answers, determines theresponse for, and often dispatches aid when an emergency number (911 in the U.S.) is called. The U.S.market almost exclusively used one number for this function (most of the rest of the world uses three numbers)and it is operated by public agencies for the public good. Vehicle based systems at this time ar