AMI-C SPEC 3001-0-0
`
`Vehicle
`Interface
`Specification
`– Release 1
`
`Release 1, 2001
`
`AHM, Exh. 1026, p. 1
`
`

`

`
`
`
`
`
`
`
`
`
`
`Vehicle Interface Specification
`– Release 1
`
`
`Legal Disclaimer and Copyright Information
`
`
`
`All Automotive Multimedia Interface Collaboration, Inc. (AMI-C) specifications are
`copyrighted and are subject to the following terms and limitations:
`
`AMI-C specifications are for information and evaluation purposes only. Certain elements
`of AMI-C specifications may be subject to third-party intellectual property rights including,
`without limitation, patent rights (such a third party may or may not be a member of AMI-
`C). By releasing an AMI-C specification, AMI-C grants no license, expressed or implied,
`by estoppel or otherwise under AMI-C’s or any third party’s intellectual property rights,
`which may be embodied in such AMI-C specifications.
`
`AMI-C is not responsible and shall not be held responsible in any manner for identifying
`or failing to identify any or all such third-party intellectual property rights. In light of the
`above, AMI-C specifications may not be used for the design, development, production or
`commercialization of products, unless proper licenses are taken from the owners of
`intellectual property rights that pertain to each AMI-C specification and the information
`contained therein.
`
`The AMI-C specifications and the information contained therein are provided on an “as
`is” basis. AMI-C disclaims all warranties, expressed or implied, including but not limited
`to any warranty that the use of the information therein will not infringe the intellectual
`property rights of a third party or any warranties of merchantability or fitness for a
`particular purpose.
`
`In no event is AMI-C liable for any loss of profits, loss of business, loss of use of data,
`interruption of business, or for direct, indirect, special or exemplary, incidental, punitive,
`or consequential damages of any kind in connection with an AMI-C specification or the
`information contained therein or the use thereof by anyone.
`
`All brand and product names may be trademarks that are the sole property of their
`respective owners. All rights reserved.
`
` Copyright AMI-C 2000.
`
` 
`
`AHM, Exh. 1026, p. 2
`
`

`

`AMI-C SPEC 3001.0.0
`
`
`
`Revision Log
`
`[Notice: Refer to the public document section of www.ami-c.org for most current baseline and revision.]
`
`Baseline Date
`
`01/01/01
`
`Baseline No:
`
`Document No.
`
`AMI-C SPEC 3001
`Document Title:
`
`Vehicle Interface Specification – Release 1
`
`
` 0
`
`
`
`
`Revision Date
`
`
`Affected Sections
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Revision No.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`AHM, Exh. 1026, p. 3
`
`

`

`AMI-C SPEC 3001.0.0
`
`Request for Change Form
`
`
`
`[Notice: Use this form to identify any errors or deficiencies or to make general change recommendations.]
`
`Revision No.
`
` 0
`
`
`
`Baseline No.
`
`Document No.
`
`AMI-C SPEC 3001
`Document Title:
`
`Vehicle Interface Specification – Release 1
`
`
` 0
`
`
`
`
`REQUESTOR INFORMATION
`
`
`
`
`Mail to:
`Don Ingersoll
`AMI-C Vice President
`280 Enterprise Drive, Bloomfield Hills,
`
`Michigan, USA 48302-0312
`
`Fax to:
`Don Ingersoll
`AMI-C Vice President
`c/o Results Systems Corp.
`(248) 244-8504
`
`
`Name:
`
`Organization:
`
`E-mail:
`
`Phone:
`
`Description of Change:
`
`
`
`
`Rational for Change:
`
`
`
`
`Proposed Revision:
`
`
`
`
`Affected Sections:
`
`
`
`
`
`E-mail to:
`
`Don Ingersoll
`AMI-C Vice President
`secretary@ami-c.org
`
`
`
`AHM, Exh. 1026, p. 4
`
`

`

`AMI-C SPEC 3001.0.0
`
`
`
`Table of Contents
`
`THE DEVELOPMENT OF ANY SIGNIFICANT SYSTEM DESIGN OR
`COMPREHENSIVE SET OF
`
`SPECIFICATIONS MUST START WITH A DESCRIPTION OF THE SYSTEMS
`FUNCTIONAL
`
`INTENT AND BE SUPPLEMENTED WITH EXAMPLES OF APPLICATIONS
`SHOWING HOW THE
`
`SYSTEM WOULD BE USED. THESE DESCRIPTIONS PROVIDE DIRECTION
`TO THE DESIGN
`
`ENGINEERS WHO ARE CHARGED WITH THE SYSTEM DESIGN
`SPECIFICATIONS. FURTHER
`
`THESE DESCRIPTIONS PROVIDE A METHOD TO CAPTURE A
`CONSENSUS AMONG MANY
`
`COMPETING CORPORATE OBJECTIVES.
`
`THIS DOCUMENT CAPTURES THE FUNCTIONAL INTENT OF THE AMI-C
`SYSTEM
`
`SPECIFICATIONS. THE ARCHITECTURE AND COMPONENT INTERFACE
`SPECIFICATIONS
`
`COMPRISING THE INITIAL AMI-C RELEASE 1 DOCUMENT SET, ARE
`BASED UPON THIS
`
`FUNCTIONAL SPECIFICATION AND THE USE CASES DOCUMENT
`(NUMBER OF DOCUMENT
`
`HERE). THESE DOCUMENTS COMBINED, MAKE A COMPLETE SET OF
`SPECIFICATIONS TO
`
`PROVIDE DIRECTION TO POTENTIAL USERS, PROVIDE PLANNING
`GUIDANCE, AND SET
`
`
`
`AHM, Exh. 1026, p. 5
`
`

`

`AMI-C SPEC 3001.0.0
`
`REQUIREMENTS FOR LONG LEAD TECHNOLOGIES. THIS INITIAL
`RELEASE 1 SET OF
`
`SPECIFICATIONS WILL BE DEVELOPED AND MATURED OVER THE NEXT
`PHASES OF AMI-C'S
`
`DEVELOPMENT AND SHOULD BE CONSIDERED LIVING DOCUMENTS,
`NOT SUITABLE AS
`
`"BUILD TO" SPECIFICATIONS.FOREWORD.................................................. 1
`
`INTRODUCTION................................................................................................ 1
`
`1. SCOPE ....................................................................................................... 1
`
`1.1. Related Documents ........................................................................................ 2
`
`2. NORMATIVE REFERENCES ..................................................................... 2
`
`2.1. AMI-C Documents ........................................................................................... 2
`
`2.2. Other Documents............................................................................................ 2
`
`3. TERMS AND DEFINITIONS ....................................................................... 2
`
`4. SPECIFICATION ........................................................................................ 3
`
`4.1. Requirements for Compliance ....................................................................... 3
`
`4.2. Vehicle Requirements .................................................................................... 3
`
`5. VEHICLE INTERFACE PHYSICAL / ELECTRICAL SPECIFICATION...... 4
`
`5.1.
`
`IDB-C Interface................................................................................................ 4
`
`5.2. High-Speed Network Interface ....................................................................... 4
`
`5.3. Power and Ground Interface .......................................................................... 4
`
`5.4. Boot Sequence................................................................................................ 4
`
`6. SERVICES.................................................................................................. 6
`6.1.1. Worst Case Response Times.................................................................... 8
`
`6.2. Vehicle Services ............................................................................................. 9
`6.2.1.
`Core Services ........................................................................................... 9
`
`
`
`AHM, Exh. 1026, p. 6
`
`

`

`AMI-C SPEC 3001.0.0
`
`6.2.1.1. VIN (Vehicle Identification Number) ....................................................................9
`6.2.1.2. Manufacturer / Model.........................................................................................10
`6.2.1.3. Vehicle Description Data ...................................................................................10
`6.2.1.4. AMI-C Version / Release ...................................................................................11
`6.2.1.5. Configured Services ..........................................................................................11
`6.2.1.6. System State .....................................................................................................12
`6.2.1.7. Power Mode.......................................................................................................13
`6.2.1.8. Boot Sequence Messages.................................................................................13
`6.2.1.9. Shutdown Sequence Messages ........................................................................14
`6.2.1.10.
`Networks Activity / Error Status.....................................................................14
`6.2.1.11.
`AMI-C Diagnostics.........................................................................................16
`6.2.1.12.
`Time / Date....................................................................................................17
`6.2.2.
`Security Services .................................................................................... 17
`6.2.3.
`Vehicle Status Group .............................................................................. 20
`6.2.3.1. Vehicle Speed....................................................................................................20
`6.2.3.2. Odometer Reading ............................................................................................21
`6.2.3.3. High-Resolution Odometer Reading .................................................................22
`6.2.3.4. Fuel Level ..........................................................................................................23
`6.2.3.5. Battery Charge...................................................................................................23
`6.2.3.6. Airbag Status .....................................................................................................23
`6.2.3.7. Brake Status ......................................................................................................24
`6.2.3.8. Traction Control .................................................................................................24
`6.2.3.9. Anti-Lock Brakes ...............................................................................................25
`6.2.3.10.
`Cruise Control ...............................................................................................25
`6.2.3.11.
`Set Point Speed ............................................................................................25
`6.2.3.12. Warning Light Status .....................................................................................25
`6.2.3.13.
`Variable Suspension Status ..........................................................................26
`6.2.4.
`Vehicle Diagnostics Group ...................................................................... 26
`6.2.4.1. OBD Codes........................................................................................................27
`6.2.4.2. Run Diagnostics ................................................................................................27
`6.2.4.3. OEM Specific Diagnostics .................................................................................27
`6.2.4.4. Encapsulated Diagnostics .................................................................................28
`6.2.5.
`Body Status and Control Group............................................................... 28
`6.2.5.1. Door Lock Status ...............................................................................................28
`6.2.5.2. Door Lock Control..............................................................................................29
`6.2.5.3. Door Ajar / Trunk Open .....................................................................................29
`6.2.5.4. Window Status...................................................................................................30
`6.2.5.5. Window Control .................................................................................................30
`6.2.5.6. Sun / Moon Roof Status ....................................................................................30
`6.2.5.7.
`Lights Status ......................................................................................................30
`6.2.5.8. Parking Lights Status.........................................................................................31
`6.2.5.9.
`Lights Control.....................................................................................................31
`6.2.5.10.
`Parking Lights Control...................................................................................31
`6.2.5.11.
`Turn Signal Status.........................................................................................32
`6.2.5.12.
`Hazard Signal Status ....................................................................................32
`6.2.5.13.
`Mirror Status..................................................................................................32
`6.2.5.14.
`Mirror Control ................................................................................................33
`6.2.5.15.
`Seat Position .................................................................................................33
`6.2.5.16.
`Seat Adjust ....................................................................................................34
`6.2.5.17.
`Antenna Status and Control ..........................................................................34
`6.2.5.18.
`Tire Pressure.................................................................................................34
`6.2.5.19.
`Seat Belt........................................................................................................35
`6.2.5.20.
`Horn...............................................................................................................35
`6.2.5.21.
`Trigger security alert......................................................................................35
`6.2.5.22. Wiper Status..................................................................................................36
`
`
`
`AHM, Exh. 1026, p. 7
`
`

`

`AMI-C SPEC 3001.0.0
`
`Interior Temperature .....................................................................................36
`6.2.5.23.
`6.2.6.
`Powertrain Status and Control Group...................................................... 36
`6.2.6.1. Engine Start Enable Status ...............................................................................37
`6.2.6.2. Disable Engine...................................................................................................37
`6.2.6.3. Engine Performance Status...............................................................................37
`6.2.6.4. Engine Performance Control .............................................................................38
`6.2.6.5. Remote Start......................................................................................................38
`6.2.6.6. Engine Speed ....................................................................................................38
`6.2.6.7. Engine Coolant Temperature ............................................................................39
`6.2.6.8. Current Gear......................................................................................................39
`6.2.6.9. PRNDL Position.................................................................................................39
`6.2.6.10.
`Oil Pressure...................................................................................................39
`6.2.7.
`Entertainment (Audio) System Status and Control .................................. 40
`6.2.7.1. Audio Volume Status .........................................................................................40
`6.2.7.2. Mute / Unmute ...................................................................................................40
`6.2.7.3. Set Volume ........................................................................................................40
`6.2.7.4. Audio Fade / Balance Status .............................................................................41
`6.2.7.5. Set Fade / Balance ............................................................................................41
`6.2.7.6. Equalizer Status ................................................................................................41
`6.2.7.7. Equalizer............................................................................................................41
`6.2.7.8. Connect Audio Channel.....................................................................................41
`6.2.7.9. Play Audio File (.au, .wav).................................................................................42
`6.2.7.10.
`Chime ............................................................................................................42
`6.2.7.11.
`Radio Setting Status .....................................................................................42
`6.2.7.12.
`Set Radio Frequency ....................................................................................43
`6.2.7.13.
`Radio Presets Status ....................................................................................43
`6.2.7.14.
`Set Radio Presets .........................................................................................43
`6.2.8.
`OEM Reserved Services ......................................................................... 43
`
`6.3. Quasi-Public Functions ................................................................................ 43
`6.3.1.
`HMI ......................................................................................................... 44
`6.3.1.1. Display Text Message .......................................................................................44
`6.3.1.2. Recognize Speech Input ...................................................................................44
`6.3.1.3.
`ISO Display Outputs ..........................................................................................45
`6.3.1.4. Button / Dial Input ..............................................................................................45
`6.3.1.5. Display Graphics ...............................................................................................46
`6.3.2.
`Positioning .............................................................................................. 46
`6.3.3.
`E-Call ...................................................................................................... 47
`
`APPENDIX A: REQUIREMENT AND RECOMMENDATION LANGUAGE ... 48
`
`APPENDIX B: INPUTS AND OUTPUTS TO THE VEHICLE FROM THE
`VEHICLE INTERFACE .................................................................................... 49
`
`
`
`AHM, Exh. 1026, p. 8
`
`

`

`AMI-C SPEC 3001.0.0
`
`Table of Figures
`
`
`
`
`Figure 1. Power Mode State Transitions .................................................................. 5
`Figure 2. Vehicle Interface Reset Actions................................................................. 6
`
`
`
`AHM, Exh. 1026, p. 9
`
`

`

`AMI-C SPEC 3001.0.0
`
`AMI-C SPEC 3001.0.0
`
`Vehicle Interface Specification – Release 1
`
`
`
`Foreword
`
`The Vehicle Interface Specification is part of the AMI-C Release 1 Specification
`Set.
`
`Release 1 specifications are not the definitive source by which AMI-C compliant
`components are to be designed and constructed, but they do serve as the
`foundation for the continuation of specification development activities and
`provide a method for identifying and resolving any discrepancies and
`deficiencies that may be present.
`
`The specification set resulting from the next phase of development will provide
`the “build-to” requirements for ensuring the interoperability, expandability and
`upgrade-ability of AMI-C compliant components.
`
`Introduction
`
`This document describes the services provided by the vehicle interface in a
`system that is compliant with the Automotive Multimedia Interface
`Collaboration, Inc. (AMI-C) specification. There are two levels of interfaces
`defined for each vehicle service: 1) a network application layer message set,
`and 2) a software application programming interface (API). These interfaces
`are defined in detail in AMI-C SPEC 3002, Common Message Set, and Vehicle
`API documents.
`
`The network application layer interfaces are defined in Release 1 of the AMI-C
`Specification. The software interfaces for these services are to be defined in
`the next specification release.
`
`Vehicle services are separated into a number of groups, covering different
`functional areas. Within each group, there may be several levels of service. If
`the group is implemented by the vehicle interface at a given level, all of the
`services defined for that level must be present. One group -- the core group --
`must be present in all AMI-C compliant systems.
`
`1. Scope
`
`The physical and electrical requirements for the AMI-C side of the vehicle
`interface, including network connectors and power moding, are specified in
`Section 5 - Vehicle Interface Physical / Electrical Specification.
`
`Vehicle Interface Specification – Release 1 Page 1 of 51
`
`AHM, Exh. 1026, p. 10
`
`

`

`AMI-C SPEC 3001.0.0
`
`Vehicle interface requirements for the original equipment manufacturer (OEM)
`are the responsibility of the OEM and are not specified in this document. This
`document also specifies mandatory and optional services provided by the
`vehicle interface to components, via AMI-C compliant networks.
`
`1.1. Related Documents
`
`This document should be read in conjunction with AMI-C SPEC 4001, Physical
`Specification, and the AMI-C SPEC 3002, Common Message Set.
`
`2. Normative References
`
`The following documents form part of the specification to the extent specified
`herein. Unless otherwise noted, this specification refers to the most recent
`version of a particular document.
`In the event of a conflict between the text of this specification and the
`documents cited herein, the text of this specification takes precedence. Nothing
`in this specification, however, supersedes applicable laws and regulations,
`unless a specific exemption has been obtained.
`
`
`2.1. AMI-C Documents
`
`AMI-C SPEC 4001 Physical Specification
`
`AMI-C SPEC 3002 Common Message Set
`
`AMI-C SPEC 3003 OEM to IDB-C Gateway
`
`AMI-C SPEC 3004 1394 to IDB-C Gateway
`
`AMI-C SPEC 3005 MOST to IDB-C Gateway
`
`AMI-C REF DOC 6001
`
`AMI-C Technical Glossary
`
`2.2. Other Documents
`
`ISO 3779
`
`
`3. Terms and Definitions
`
`Refer to the AMI-C REF DOC 6001, AMI-C Technical Glossary, for definitions of
`terms and acronyms used throughout this document. Also refer to Appendix A:
`Requirement and Recommendation Language for guidance on verbal
`
`Vehicle Interface Specification – Release 1 Page 2 of 51
`
`AHM, Exh. 1026, p. 11
`
`

`

`AMI-C SPEC 3001.0.0
`
`expressions used throughout this specification that are indicative of
`requirements and recommendations.
`
`
`4. Specification
`
`4.1. Requirements for Compliance
`
`The features and functions that must be present in a vehicle interface are
`indicated in this document. Specifically, a vehicle interface must support at
`least one of the AMI-C compliant network interfaces defined below, and must
`support the set of core vehicle services defined in Section 6.
`
`Beyond this set of core functions, no specific functions or signals are required to
`be present in a vehicle by this document. If the optional features or signals
`described in this document are provided by the vehicle interface, they must be
`provided in the manner described in this document.
`
`The vehicle interface need not provide interfaces to more than one network,
`regardless of the number of networks in a vehicle. However, if it does provide
`interfaces to multiple networks, then it must support the bridging function
`described in either AMI-C SPEC 3004, 1394 to IDB-C Gateway Specification, or
`AMI-C SPEC 3005, IDB-C to MOST Gateway, between each pair of networks
`for which it provides an interface.
`
`4.2. Vehicle Requirements
`
`The vehicle side of the vehicle interface is not specified by AMI-C. However,
`certain inputs and outputs must be passed between the vehicle and the vehicle
`interface, in order to implement the services specified in this document. How
`these are passed between the vehicle and the vehicle interface (e.g., on an
`OEM proprietary network or as hard-wired signals) is up to the implementer.
`
`A table listing the required inputs and outputs from the vehicle side is given in
`Appendix B to this document, but it is intended for informational use only.
`
`Different implementations of the vehicle interface or different vehicle
`architectures may require a different set of signals from the vehicle. For
`example, vehicle configuration information, such as the VIN (vehicle
`identification number) number, may be obtained from a module on the OEM
`network or may be encoded in a ROM in the vehicle interface itself.
`
`Vehicle Interface Specification – Release 1 Page 3 of 51
`
`AHM, Exh. 1026, p. 12
`
`

`

`AMI-C SPEC 3001.0.0
`
`5. Vehicle Interface Physical / Electrical Specification
`
`The vehicle interface must conform to the AMI-C Physical and Electrical
`Specifications, as defined in AMI-C SPEC 4001, Physical Specification. This
`document should be consulted for a detailed description of the specifications in
`this section.
`
`5.1. IDB-C Interface
`
`The vehicle interface may provide an IDB-C interface. The connector and
`electrical specifications for this interface are described in AMI-C SPEC 4001,
`Physical Specification.
`
`5.2. High-Speed Network Interface
`
`The vehicle interface may provide a high-speed network interface (this will
`either be IEEE 1394b or MOST). The connector and electrical requirements of
`this interface are described in AMI-C SPEC 4001, Physical Specification.
`
`The vehicle interface shall provide at least one network interface to either IDB-C
`or a high-speed network. If both an IDB-C interface and a high-speed network
`interface are present, then the vehicle interface must incorporate the
`functionality of the IDB-C to high-speed network gateway, as defined in AMI-C
`SPEC 3004, 1394 to IDB-C Gateway, or the AMI-C SPEC 3005, MOST to IDB-
`C Gateway. This functionality should be viewed as logically distinct from the
`vehicle interface functionality. It is not covered in this document.
`
`5.3. Power and Ground Interface
`
`The vehicle interface supplies power to the devices connected to the AMI-C
`compliant system through the vehicle interface connector set. The requirements
`for this power supply are detailed in AMI-C SPEC 4001, Physical Specification.
`
`5.4. Boot Sequence
`
`Normally, the vehicle interface should be the first component to boot in an AMI-
`C compliant system. In any case, it must boot independently of any other
`components in the system, as other components may require information from
`the vehicle to complete their boot.
`
`Some anti-theft devices, for example, require the VIN to be available when a
`component boots. Furthermore, some components may also require vehicle
`configuration information to boot correctly.
`
`Vehicle Interface Specification – Release 1 Page 4 of 51
`
`AHM, Exh. 1026, p. 13
`
`

`

`AMI-C SPEC 3001.0.0
`
`The vehicle interface is also responsible for managing the P-Mode line on each
`network. The P-Mode line must be set to ON when the vehicle power state
`goes to ON or to certain signals from the attached networks (reference AMI-C
`SPEC 4001, Physical Specification, “Power States” and “P-Mode Line
`Operation” sections.)
`
`Following the transition of the P-Mode line to ON, there may be a network reset
`on each attached network, during which the network is configured (physical
`addresses assigned and network topology identified). This process may be
`managed by the vehicle interface or it may be managed by another node on the
`network. However, it should be handled by the vehicle interface, unless the
`alternate node is a mandatory component of the network in question on all
`vehicles on which the network is installed.
`
`Following network reset, there is a discovery phase, in which services offered
`by each component on the network are published in the network. The vehicle
`interface must announce the core vehicle services and any optional services
`that it supports to each attached AMI-C network at the beginning of the
`discovery phase.
`
`If the vehicle interface module is serving as a bridge between two or more AMI-
`C networks, it will also be required to publish the services that it discovers on
`the first network to the second, and vice versa. However, the vehicle services
`must be published prior to, and independently of, the cross network services.
`
`The following diagrams show, respectively, the Power Mode State Transitions,
`and the vehicle interface actions during reset. The first figure is from AMI-C
`SPEC 4001, Physical Specification. The second illustrates the vehicle interface
`process described above.
`
`
`
`
`
`
`
`ON
`
`Reset
`
`OFF
`
`PMODE pulse or
`Net reset signal
`
`Reset
`
`
`
`
`
`
`
`REDUCED
`POWER
`
`
`Figure 1. Power Mode State Transitions
`
`Vehicle Interface Specification – Release 1 Page 5 of 51
`
`AHM, Exh. 1026, p. 14
`
`

`

`AMI-C SPEC 3001.0.0
`
`
`Set
`P-Mode
`
`ON
`
`
`
`6. Services
`
`Boot
`Vehicle
`Interface
`
`Reset
`Networks
`
`NW
`Stable?
`
`Publish
`Vehicle
`Services
`
`Figure 2. Vehicle Interface Reset Actions
`
`This section describes the services that are provided by the vehicle interface to
`nodes on an AMI-C compliant network. The services described as “core
`services” must be provided by any vehicle interface. The remaining services are
`optional, but if they are provided, they must conform to the descriptions given in
`this specification.
`
`In this specification, sections at the fourth level of numbering represent the
`smallest level of granularity, at which optional services may be implemented. If
`a vehicle interface implements any services in a section, it shall implement all of
`the services in that section. For example, the services in section 6.2.3.3 – High
`Resolution Odometer – are optional, but if a vehicle interface implements any
`service in this section, it must implement all of the services in that section.
`
`The description of these functions as IDB-C messages, 1394 messages or
`MOST messages is not covered by this document. For that description, refer to
`the Vehicle Interface ASN.1 message set definitions (AMI-C SPEC 3002,
`Common Message Set).
`
`IMPORTANT:
`
`In the description below, individual functions are identified using courier
`font. Parameters are indicated with angle brackets, and alternatives are
`indicated with square brackets.
`
`There are several types of services:
`
`A request-reply service consists of a request to the vehicle interface for
`information, together with the reply sent by the vehicle interface. These services
`are described using the syntax:
`
`Get Group Service
`
`Vehicle Interface Specification – Release 1 Page 6 of 51
`
`AHM, Exh. 1026, p. 15
`
`

`

`AMI-C SPEC 3001.0.0
`
`Where Group is the vehicle services group and Service is the name of the
`specific service, the response is written as:
`
`Group Service <value> where <value> is the data returned.
`
`A periodic service is a request for information that will be sent out at a fixed
`frequency. This frequency is a multiple of the base update frequency provided
`by the vehicle interface. The syntax used to specify an update request (periodic
`service request) is:
`
`Update Group Service <frequency mult> where <frequency
`mult> is an integer, specifying the requested update frequency as a
`multiple of the Vehicle interface base frequency.
`
`Periodic messages can be turned off with an EndUpdate command:
`
`EndUpdate Group Service
`
`A command service is a command to the vehicle interface to perform a
`specific control function or action on the vehicle (such as locking the doors).
`The syntax used to describe a command service is:
`
`Group Verb <data1> <data2> ...
`where <data1> etc. are the parameters to the command (if any).
`
`A notification request is a request that the vehicle interface send a message
`to the requesting node when a specific event occurs. These services are
`described with the syntax:
`
`Notify if Group Event
`
`A broadcast service is a command or information sent to all nodes on the
`network by the vehicle interface when a specific event occurs. A broadcast
`service is described using the same syntax as a command.
`
`The vehicle interface shall respond to each command with a success / failure
`acknowledgement. If the success of the command is not immediately kno