SAE J 2366-7-2002 ITS Data BusApplication Message Layer.pdf

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-0001RECOMMENDEDPRACTICEJ2366-7ISSUEDAPR2002Issued 2002-04ITS Data BusApplication Message LayerTABLE OF CONTENTS1. Scope . 52. References 52

4、.1 Applicable Publications 52.1.1 SAE Publications 52.2 Related Publications . 52.2.1 SAE Publications 52.2.2 ISO Publications . 63. Definitions. 63.1 AHdr (Application Header) 63.2 ALP (Application Layer Primitives) . 63.3 AMI-C (Automotive Multimedia Interface Collaboration) 63.4 APDU (Application

5、 Protocol Data Unit) 63.5 Audio Arbiter. 63.6 Audio Bus . 63.7 Audio Bus Capability 63.8 Audio Bus Device . 63.9 Byte 63.10 CEA (Consumer Electronics Association) 63.11 Clear. 63.12 ID 63.13 ITS 63.14 Logical Node 63.15 MC (Message Code) 63.16 Mute . 73.17 Octet . 73.18 OEM (Original Equipment Manuf

6、acturer) . 73.19 OSI . 73.20 Output Level. 73.21 Physical Node 73.22 PMODE (Power Mode Line). 73.23 Primitives 73.24 Receiver . 7SAE J2366-7 Issued APR2002-2-3.25 SAPID (Service Access Point Identifier) .73.26 Set 73.27 Transmitter74. Protocol Overview .84.1 Basic Concepts.84.1.1 SAPID for Message I

7、nterpretation84.1.2 SAPID for Service Announcement84.1.3 Physical Nodes and Logical Nodes 94.1.4 Physical Node IDs and Logical Node IDs .94.1.5 Logical Node Status 94.2 Application Layer Primitives 104.2.1 Send Application Message .104.2.2 Receive Application Message. 104.2.3 Change Status Request 1

8、14.2.4 Get Status Information114.3 Application Common Header Elements 114.3.1 Control 124.3.2 SAPID . 134.3.3 Address.134.3.4 Sequence 144.3.5 MsgLen (MSB) 144.4 Application Message Layer SAPIDs .144.4.1 Application SAPIDs. 144.4.2 Standard APDU Encoding Rules 144.4.3 Encapsulated Protocols 205. Sta

9、ndard Messages Supported by All Logical Nodes . 225.1 APLNewStatus and APLReqStatus 225.2 APLReqLogicalNodeInfo and APLDevInfo .235.3 APLReqMaxMsgLen and APLMaxMsgLen 245.4 APLPing and APLPingReply . 245.5 APLDiag and APLDiagReply 245.6 APLResults . 246. Audio Arbitration .246.1 Introduction . 246.2

10、 Audio Bus Messages SAPID 256.3 Responsibilities. 256.3.1 Audio Arbiter . 256.3.2 Transmitter 256.3.3 Receiver 256.4 Audio Arbitration Sequences 256.4.1 Audio Arbiter Identification 256.4.2 Transmitter Activation . 266.5 Audio Bus Messages 286.5.1 ABCapabilityReq and ABCapabilityReply. 286.5.2 ABTra

11、nsmitRequest 306.5.3 ABSetTransmitParms . 306.5.4 ABAudioStart 306.5.5 ABAudioDone . 306.5.6 ABDeviceDisconnect 306.5.7 ABMute .30SAE J2366-7 Issued APR2002-3-7. Example Message Construction . 31Appendix A ITS Data Bus Application Message Layer Lexicon. 33A.1 Scope33A.2 IDB Application Message Layer

12、 PDU Elements . 33A.2.1 ClassMap 33A.2.2 Action 33A.2.3 Modifier .35A.2.4 Object . 37A.2.5 Feature .39A.2.6 UnitType and UnitType Lists . 41A.2.6.1 PositionList . 45A.2.6.2 HeadingList . 47A.2.6.3 ResultList 47A.2.6.4 AudioList . 48A.2.6.5 StatusCodeList . 49A.2.6.6 TransmissionStateList 49A.2.6.7 F

13、uelTypesList . 50A.2.6.8 WarningList . 50A.2.6.9 EntPlayerStatusList 51A.2.6.10 Languages 51A.2.6.11 DisplayStatusList 51A.2.6.12 Encapsulated Protocols 51A.3 Explanations and Rationale 52A.3.1 PositionList . 52A.3.2 HeadingList . 52A.3.3 ResultList 52A.3.3.1 RAcknowledge 52A.3.3.2 RAlreadyInUse 52A

14、.3.3.3 RCRCError . 52A.3.3.4 RDecodeError . 52A.3.3.5 RDeviceNotPresent 52A.3.3.6 RDeviceNotReady 52A.3.3.7 RDeviceReady 52A.3.3.8 RFailure 52A.3.3.9 RInProcess . 52A.3.3.10 RInvalidAction. 52A.3.3.11 RInvalidFeature 53A.3.3.12 RInvalidLength 53A.3.3.13 RInvalidMessage 53A.3.3.14 RInvalidModifier 53

15、A.3.3.15 RInvalidObject 53A.3.3.16 RInvalidUnitType 53A.3.3.17 RInvalidValue 53A.3.3.18 RNoMedia .53A.3.3.19 RNotSupported . 53A.3.3.20 ROutOfRange . 53A.3.3.21 RSecurityError 53A.3.3.22 RSuccess 53A.3.3.23 RTooFrequent . 53A.3.3.24 RUnknown 53SAE J2366-7 Issued APR2002-4-A.3.4 AudioList . 53A.3.5 S

16、tatusCodeList . 53A.3.6 TransmissionStateList 53A.3.7 FuelTypesList . 53A.3.8 WarningList . 53A.3.9 EntMediaInfo. 53A.3.10 EntPlayerStatusList 54A.3.11 EntTrackInfo . 54A.3.12 Language 55A.3.13 DisplayStatusList 55A.3.14 Encapsulated Protocols 55A.4 Notes 55List of FiguresFigure 1 Application Messag

17、e Layer Message Format. 12Figure 2 APDU Format . 15Figure 3 Standard MC Packet Format 16Figure 4 StatusCode Format. 19Figure 5 Encapsulated Protocol Example . 21Figure 6 Transmitter Activation Sequence 27Figure 7 Transmit Request Rejected Sequence . 28Figure 8 Set Trip Origin Message . 31Figure 9 Re

18、quest Current Vehicle Speed Message 31Figure 10 Vehicle Speed Response Message 31Figure 11 Request Periodic Speed Report Message 32Figure 12 Periodic Speed Report Message 32Figure 13 Update Rate Too High Response Message . 32List of TablesTable 1 SAPID Size . 13Table 2 SAPID Categories and Document

19、Cross-Reference 14Table 3 ClassMap Element of MC . 16Table 4 Valid Action Elements. 17Table 5 Valid Modifier Elements 17Table 6 Valid Object Elements 18Table 7 Valid Feature Codes .18Table 8 Valid UnitType and Corresponding Value Elements .18Table 9 Supported Encapsulated Protocols 21Table 10 Applic

20、ation Messages Supported by All Logical Nodes 22Table 11 Audio Bus Common Application Messages 28Table 12 Audio Bus Use Categories 30Table A1 ClassMap 33Table A2 Action 33Table A3 Modifier .35Table A4 Object . 37Table A5 Feature .39Table A6 UnitType and UnitType Lists . 41Table A7 PositionList Names

21、 and Values 45Table A8 HeadingList Names and Values . 47Table A9 ResultList Names and Values. 47Table A10 AudioList Names and Values 48SAE J2366-7 Issued APR2002-5-Table A11 StatusCode List Names and Values .49Table A12 Transmission StateList Names and Values 49Table A13 FuelTypesList Names and Valu

22、es 50Table A14 WarningList Names and Values . 50Table A15 EntPlayerStatusList Format 51Table A16 Language Names and Values 51Table A17 DisplayStatusList Names and Values. 51Table A18 Supported Encapsulated Protocols 51Table A19 EntMediaInfo Format 53Table A20 EntTrackInfo Format .541. ScopeNOTE SAE

23、J2366-7LXITS Data Bus Application Message Layer Lexicon is now combined (as anappendix) with SAE J2366-7 to provide for a quicker revision process in the future.This SAE Surface Vehicle Recommended Practice defines an Application Message Layer, which may be usedas part of a complete protocol stack w

24、ith the other protocol layers in the SAE J2366 family.The Application Message Layer provides application message support for devices that are interconnected viaa bus or network. Design of the messages and headers has stressed flexibility, expandability, economy (interms of octets on the bus), and re

25、usability.The Application Message Layer is independent of the underlying network used, and may be used on anynetwork. Sections of this document make specific reference to the use of SAE J2366-7 with other layers of theSAE J2366 family of protocols, and may not apply when SAE J2366-7 is used with oth

26、er networks.In addition, this document defines an audio arbitration scheme that may be used with the SAE J2366-1L LowImpedance Stereo Audio (LISA) bus, or any other comparable analog audio bus.2. References2.1 Applicable PublicationsThe following publications form a part of this specification to the

27、 extent specifiedherein. Unless otherwise indicated, the latest issue of SAE publications shall apply.2.1.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1760Data Security Services (Under Development at time of this documents publication)SAE J2366-2ITS Da

28、ta Bus Protocol Link LayerSAE J2590PMODE for In-Vehicle Networks2.2 Related PublicationsThe following publications are provided for information purposes only and are not arequired part of this specification.2.2.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.S

29、AE J2355ITS Data Bus Architecture Reference Model Information ReportSAE J2366-1ITS Data Bus Protocol Physical LayerSAE J2366-1LLow Impedance Stereo Audio (LISA) busSAE J2366-4ITS Data Bus Protocol Thin Transport LayerSAE J2366-7 Issued APR2002-6-2.2.2 ISO P UBLICATIONSAvailable from ANSI, 25 West 43

30、rd Street, New York, NY 10036-8002.ISO/IEC 8824:1998 (ITU-T X.680) Information Technology Abstract Syntax Notation One (ASN.1):Specification of Basic NotationISO 7498:1990, Information Processing Systems Open System Interconnect Basic Reference Model3. Definitions3.1 AHdr (Application Header)This el

31、ement identifies the contents of Application Messages and identifies howthe data are to be interpreted.3.2 ALP (Application Layer Primitives)These are generally function call parameters and are “out-of-band”signals between an application and the Application Message Layer.3.3 AMI-C (Automotive Multim

32、edia Interface Collaboration)http:/www.ami-c.org3.4 APDU (Application Protocol Data Unit)This packet of data contains the specific application messages.One or more specific messages may be contained within a single APDU.3.5 Audio ArbiterThe function that determines whether and at what levels devices

33、 may access the analogAudio Bus. The Audio Arbiter function may be present on any node on the network, and does not have to beassociated with a Transmitter or Receiver, nor does it require direct connection to the Audio Bus.3.6 Audio BusAn audio bus that allows Transmitters and Receivers to share on

34、e or more audio channels. TheAudio Bus is assumed to support individual output gain settings for Transmitters and audio mixing of multipleTransmitter outputs. The Audio Bus is assumed to be capable of accommodating up to a maximum of 16connected Receivers, and a maximum of 16 connected Transmitters.

35、 When used with the SAE J2366 seriesof protocols, the total number of physical connections is limited to 16.3.7 Audio Bus CapabilityA device that is a Transmitter and/or a Receiver is considered to have Audio BusCapability.3.8 Audio Bus DeviceA device that uses or controls access to the Audio Bus ch

36、annels. A single physicaldevice may host one or more of the following device functions: Audio Arbiter, Transmitter, Receiver. Therecan be a maximum of 16 Audio Bus Devices on the network.3.9 ByteIn this document, bytes and octets are synonymous. See the definition for octet for more information.3.10

37、 CEA (Consumer Electronics Association)http:/www.ce.org3.11 ClearThe word “clear” is used in referring to one or more bits to indicate that they each have a value of 0B.3.12 IDIdentifier3.13 ITS Intelligent Transportation Systems3.14 Logical NodeThis is used to indicate an application running on a P

38、hysical Node or on another device that isdirectly attached to the Physical Node, and for which the Physical Node is acting as a ”proxy” on the network.A Logical Node has a Logical ID within that Physical Node. Logical Node ID 0H refers to the Physical Nodeitself.3.15 MC (Message Code)Each MC represe

39、nts a single Application Layer message. Multiple MCs may bechained together in a single APDU.SAE J2366-7 Issued APR2002-7-3.16 MuteThis action, when requested of a Transmitter, causes it to apply silence to the Audio Bus. This may, insome cases, be equivalent to an Output Level of zero. This action,

40、 when requested of a Receiver, causes it tosilence the Receiver output.3.17 OctetAn octet is a unit of data transmission that consists of eight bits. On most commonly usedmicroprocessors, such an eight-bit quantity is commonly referred to as a “byte.” The bits within an octet maybe subdivided and/or

41、 grouped, to provide specific meanings.3.18 OEM (Original Equipment Manufacturer)In this document it refers to the manufacturer of a vehicle.3.19 OSIOfficially known as the “ISO Reference Model of Open System Interconnection.” It refers to a model, orway of thinking about communication protocols as

42、being divided into (usually) seven distinct layers.3.20 Output LevelWhen sent to a Transmitter, defines the output level that the Transmitter is to present to theAudio Bus. This parameter takes a value of 0-255, which represents a range of 0-100%.3.21 Physical NodeA Physical Node is a device that ma

43、kes a single physical connection to the network. EachPhysical Node has at least one Physical Node ID. Each Physical Node ID may have associated with it up to 15additional “virtual” node IDs, called Logical Node IDs.3.22 PMODE (Power Mode Line)This is a signal defined in SAE J2590 that indicates the

44、power mode of thenetwork. There are three basic power modes: KEY ON, KEY OFF, and KEY PULSE. Of these modes, KEYON and KEY OFF are the only ones generally pertinent to an application.3.23 PrimitivesThese are parameters necessary for the operation of a protocol but are generally not part of thedata s

45、tream between layers of a protocol stack. These parameters are passed through various methodsincluding function call variables, private messages, and global variables.3.24 ReceiverAn Audio Bus device that “sinks” audio from one or more channels of the Audio Bus. Such devicesmight include: Amplifier,

46、 Voice Recognition System. There can be at most 16 connected Receivers on theAudio Bus.3.25 SAPID (Service Access Point Identifier)There are two primary uses / definitions of SAPID.In the body of an APLNewStatus message, the SAPID value is used to specify a group of messages,representing a service b

47、eing provided, which are supported by a Logical Node.In the AHdr, the SAPID value specifies the interpretation to be placed upon the message. The valuerepresented by this element identifies which “interpreter” should be used to decode an APDU.This release of the SAE J2366-7 protocol supports a large

48、 number of SAPIDs. SAPIDs in the range 0 to32767 are interpreted according to the rules laid out in this document. The SAPID value may be used todifferentiate (for example) between “unlock vehicle doors” and “unlock CD changer door.” Although the APDUitself may contain the same message octets for bo

49、th messages, one SAPID will specify that the message is avehicle related message while the other SAPID will specify that the message is a CD changer relatedmessage. SAPID values above 32767 are intended for use by encapsulated protocols. The SAPID specifieswhat protocol material is contained in the APDU, allowing it to be interpreted correctly.3.26 SetThe word “set” is used in referring to one or more bits to indicate that they each have a value of 1B.3.27 TransmitterAn Audio Bus device that produces audio onto one or more channe