BS ISO 22902-6-2006 Road vehicles - Automotive multimedia interface - Vehicle interface requirements《道路车辆 车用多媒体接口 车辆接口设备》.pdf

《BS ISO 22902-6-2006 Road vehicles - Automotive multimedia interface - Vehicle interface requirements《道路车辆 车用多媒体接口 车辆接口设备》.pdf》由会员分享，可在线阅读，更多相关《BS ISO 22902-6-2006 Road vehicles - Automotive multimedia interface - Vehicle interface requirements《道路车辆 车用多媒体接口 车辆接口设备》.pdf（64页珍藏版）》请在麦多课文档分享上搜索。

1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58Part 6: Vehicle interface requirementsICS 43.040.15Road vehicles Automotive multimedia interface BR

2、ITISH STANDARDBS ISO 22902-6:2006BS ISO 22902-6:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 November 2006 BSI 2006ISBN 0 580 49715 1Amendments issued since publicationAmd. No. Date Commentscontract. Users are responsible for its co

3、rrect application.Compliance with a British Standard cannot confer immunity from legal obligations.National forewordThis British Standard was published by BSI. It is the UK implementation of ISO 22902-6:2006.The UK participation in its preparation was entrusted to Technical Committee AUE/16, Electri

4、cal and electronic equipment.A list of organizations represented on AUE/16 can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a Reference numberISO 22902-6:2006(E)INTERNATIONAL STANDARD ISO22902-6First edition2006-11-01Road vehicl

5、es Automotive multimedia interface Part 6: Vehicle interface requirements Vhicules routiers Interface multimdia pour lautomobile Partie 6: Exigences pour linterface du vhicule BS ISO 22902-6:2006ii iiiContents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references . 1 3 Terms and definit

6、ions. 2 4 Vehicle services 3 4.1 Core services 3 4.2 Vehicle status and control group 8 4.3 Security services 34 4.4 Vehicle diagnostics group . 36 4.5 AMI-C diagnostics. 37 5 Power management services 37 5.1 Power state 37 5.2 System power mode. 37 5.3 Boot sequence messages 38 5.4 Shutdown sequenc

7、e messages 38 5.5 Time / date . 38 6 HMI services 39 6.1 AmicHMIRequest 39 6.2 AmicHmiSend 40 6.3 AmicHMISetupAudio 40 6.4 AmicIsHMIResourceAvailable . 40 6.5 AmicHMIReleaseAudio. 41 7 Audio services 41 7.1 Audio configuration 41 7.2 Audio volume state. 41 7.3 Mute / unmute 41 7.4 Set volume. 42 7.5

8、 Audio fade state 42 7.6 Audio balance state 42 7.7 Set fade 42 7.8 Set balance 42 7.9 Equalizer configuration 43 7.10 Equalizer state. 43 7.11 Equalizer 43 7.12 Audio channel configuration . 43 7.13 Allocate audio channel. 43 7.14 Open audio channel 44 8 Requirements for compliance . 44 Annex A (In

9、formative) HMI services . 45 Annex B (Informative) I/O to the vehicle from the vehicle interface . 51 Annex C (Informative) Subscription and notification services . 53 BS ISO 22902-6:2006iv Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standa

10、rds 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 organ

11、izations, 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 i

12、n 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 %

13、 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 of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 22902-6 was prepared by Technical Committee ISO/TC 22, Road

14、 vehicles, Subcommittee SC 3, Electrical and electronic equipment. ISO 22902 consists of the following parts, under the general title Road vehicles Automotive multimedia interface: Part 1: General technical overview Part 2: Use cases Part 3: System requirements Part 4: Network protocol requirements

15、for vehicle interface access Part 5: Common message set Part 6: Vehicle interface requirements Part 7: Physical specification BS ISO 22902-6:2006vIntroduction A Vehicle Interface is defined as a component that provides access to vehicle services from a compliant network. It may act as a gateway to a

16、 vehicle-manufacturer-defined network, or it may implement some or all of the vehicle services directly. The Vehicle Services Interface is defined as the logical collection of vehicle services implemented by all Vehicle Interfaces in the vehicle. This document describes the services typically associ

17、ated with the Vehicle Interface in a system that is compliant with the “AMI-C” specification. These services are grouped into four categories: vehicle services, power management services, Human-Machine Interface (HMI) services, and audio services. A vehicle service is a function that controls vehicl

18、e operations such as door locking and unlocking, data related to the vehicle itself such as diagnostic information, or a system signal indicating vehicle status information such as vehicle speed or fuel level. Vehicle services must be implemented in a Vehicle Interface component. Power management se

19、rvices control the states, and transition between power states, of the multimedia system, and provide for orderly startup and shutdown of system components. The policy for managing the power states and transitions is derived from carmaker-specific requirements but is implemented as a standard interf

20、ace on the “AMI-C” system. Power Management Services must be implemented in a Vehicle Interface component. HMI services provide a standard interface to displays and/or audible interfaces intended for occupants of the vehicle. The policy for displaying and/or annunciating conditions and information i

21、n the vehicle is owned by the carmaker. The HMI services are likely to be implemented in a Vehicle Interface component, however they may be partitioned elsewhere at the carmakers discretion. Audio services provide a method for devices in the “AMI-C” system to access audio resources. Since it is poss

22、ible that more than one source may be vying for the use of a resource at a single time, the policy regarding the priority of individual services requesting access to audio services and the arbitration scheme used to ultimately grant access to one or more functions is owned by the carmaker. The audio

23、 services are likely to be implemented in a Vehicle Interface component; however, they may be partitioned elsewhere if the carmaker deems this appropriate. BS ISO 22902-6:2006blank1Road vehicles Automotive multimedia interface Part 6: Vehicle interface requirements 1 Scope This part of ISO 22902 def

24、ines the services provided by the Vehicle Interface. Those services are implemented in an “AMI-C” system in one or both of two ways: 1) as messages on a multimedia network, and 2) as Java Classes in the vehicle interface API (Application Programming Interface). These are described in separate specif

25、ications. This part of ISO 22902 has the following sections: Vehicle services. This section presents core services, the vehicle body status and control group, audio services, the powertrain status and control group, security services, and the vehicle diagnostics group. Power management systems. This

26、 section presents system state, power mode, boot sequence messages and shutdown sequence messages. HMI services. This section provides information about messages sent to the HMI manager as well as the messages that form HMI manager responses. Details about HMI manager are included in Annex A. Audio

27、services. This section describes elements of audio services typically found in vehicles. Requirements for compliance. This section presents requirements for “AMI-C” compliance of an implementation of vehicle interface. 2 Normative references The following referenced documents are indispensable for t

28、he application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. Reference specifications may change. The user must check with the publishing organization and/or automakers

29、 for the current requirements. ISO 22902-1, Road vehicles Automotive multimedia interface Part 1: General technical overview ISO 3779, Road vehicles Vehicle identification number (VIN) Content and structure ISO 639-1, Codes for the representation of names of languages Part 1: Alpha-2 code ISO 639-2,

30、 Codes for the representation of names of languages Part 2: Alpha-3 code BS ISO 22902-6:20062 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 22902-1 and the following apply. 3.1 subscription types service that allows a requestor to register for upda

31、tes to a parameter without explicitly requesting each update NOTE There are two types of subscription services, periodic and notification. 3.2 periodic subscription subscription where the basis for a message being sent is the expiration of a timer 3.3 notification subscription where the basis for th

32、e transmission of the message is that the parameter contained in the message has changed 3.4 service primitive reference terms which are used in the definitions of the Vehicle Interface Services 3.5 Request term used in the service primitive to indicate the part of the service where the value of a p

33、arameter is being queried EXAMPLE Request: Inquire VehicleCore Make-Model 3.6 Reply term used in the service primitive to indicate the part of the service where the value of a parameter is being provided EXAMPLE Reply: Report VehicleCore Make-Model 3.7 Inquire term used in the service primitive as t

34、he key word for the process of querying a parameter EXAMPLE Request: Inquire VehicleCore Make-Model 3.8 Report term used in the service primitive as the key word for the process of responding with the value of a parameter EXAMPLE Reply: Report VehicleCore Make-Model 3.9 Command term used in the serv

35、ice primitive to indicate the part of the service where control is being exercised over the value of a parameter EXAMPLE Command: Audio SoundChime on, off BS ISO 22902-6:200633.10 Update term used in the service primitive to indicate the part of the service where a periodic subscription is being ini

36、tiated EXAMPLE Request: Update VehicleStatus Speed 3.11 EndUpdate term used in the service primitive to indicate the part of the service where a periodic subscription is being cancelled EXAMPLE Request: EndUpdate VehicleStatus Speed 3.12 Notify term used in the service primitive to indicate the part

37、 of the service where a notification subscription is being initiated EXAMPLE Request: Notify If VehicleStatus OdometerDelta 3.13 EndNotify term used in the service primitive to indicate the part of the service where a notification subscription is being cancelled EXAMPLE Request: EndNotify VehicleSta

38、tus OdometerDelta 4 Vehicle services 4.1 Core services The core services must be present in every vehicle interface to comply with the specification. These services represent the basic elements needed to implement a compliant vehicle interface. The first group of core services provides vehicle ident

39、ification and configuration information to components. The configuration information is required to allow compliant components to inter-operate between different vehicles. In the descriptions below, individual functions are identified using courier font. Parameters are enclosed in angle brackets, an

40、d alternatives are enclosed in square brackets. 4.1.1 VIN (vehicle identification number) status This service shall provide the VIN to any node on the network that requests it. The associated messages are: Request: Inquire VehicleCore VIN Reply: Report VehicleCore VIN Where is a (17 character) strin

41、g, the format of the string will correspond to that specified in ISO 3779 or one of the regional variants of that standard. BS ISO 22902-6:20064 4.1.2 Manufacturer, model, and model year status This service shall return information regarding the vehicle manufacturer, model and date of manufacture. R

42、equest: Inquire VehicleCore Make-Model Reply: Report VehicleCore Make-Model Where is a triplet consisting of two strings and a date. The first string (32 characters max) contains the manufacturer name, the second the model name (also 32 characters max). The date is the vehicles model year as a four

43、digit number. This should correspond to the model year encoded in the VIN. 4.1.3 Manufacturing date and location status This service returns the date the vehicle was manufactured and the location. Request: Inquire VehicleStatus DateOfManufacture Reply: Report VehicleStatus DateOfManufacture where =

44、(131), = (112), = (09999), and is a string (max length of 32 characters). The vehicle manufacturer defines the possible values of this string. 4.1.4 Language status The service returns the default language code to be used by the vehicle HMI. Request: Inquire VehicleStatus Language Reply: Report Vehi

45、cleStatus Language where is a field encapsulating the two-digit ISO 639 value for the default language. Examples of the these codes are listed in the table below: ISO 639 Language Codes (2 byte character) en = English es = Spanish fr = French it = Italian de = German ja = Japanese zh = Chinese ru =

46、Russian pt = Portuguese ko = Korean el = Greek sv = Swedish nl = Netherlands 4.1.5 Vehicle description data status This service shall return information about the physical description of the vehicle and systems that are present in the vehicle, such as number of doors, number of power windows, number

47、 of power seats, fuel tank capacity, cruise control, ABS, etc. Request: Inquire VehicleCore VehicleDescription Reply: Report VehicleCore VehicleDescription The vehicle data structure shall contain the following data: Display Units - This field indicates the units displayed by the vehicle HMI: Displa

48、yed Units of Speed 0=Metric 1=English Displayed Units of Distance 0=Metric 1=English BS ISO 22902-6:20065 Displayed Units of Volume 0=Metric 1=English Displayed Units of Temp 0=Metric 1=English Number of Doors the number of doors in the vehicle. A door with any of the following characteristics is a

49、candidate for inclusion in this count: the open/closed status can be determined the locked/unlocked status can be determined the locked/unlocked status can be changed Door Configuration - This field provides a door description including: the capability of the vehicle to report the closed or not closed status of doors (0=no capability; 1=other, 2=driver door explicit, all others combined; 3=all doors explicit). the capability to determine the locked vs unlocked status