ImageVerifierCode 换一换
格式:PDF , 页数:14 ,大小:335.27KB ,
资源ID:586475      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-586475.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(BS ISO 22902-3-2006 Road vehicles - Automotive multimedia interface - System requirements《道路车辆 车用多媒体接口 系统要求 》.pdf)为本站会员(fuellot230)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

BS ISO 22902-3-2006 Road vehicles - Automotive multimedia interface - System requirements《道路车辆 车用多媒体接口 系统要求 》.pdf

1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58Part 3: System requirementsICS 43.040.15Road vehicles Automotive multimedia interface BRITISH STAND

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

3、cation.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-3:2006.The UK participation in its preparation was entrusted to Technical Committee AUE/16, Electrical and ele

4、ctronic 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-3:2006(E)INTERNATIONAL STANDARD ISO22902-3First edition2006-11-01Road vehicles Automoti

5、ve multimedia interface Part 3: System requirements Vhicules routiers Interface multimdia pour lautomobile Partie 3: Exigences du systme BS ISO 22902-3:2006ii iiiForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodie

6、s). 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 organizations, governmental and n

7、on-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 in the ISO/IEC Directives, Pa

8、rt 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 % of the member bodies castin

9、g 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-3 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3

10、, 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 for vehicle interface access

11、 Part 5: Common message set Part 6: Vehicle interface requirements Part 7: Physical specification BS ISO 22902-3:2006blank1Road vehicles Automotive multimedia interface Part 3: System requirements 1 Scope This system requirements document captures system-level requirements and defines the expected f

12、unctional and physical capabilities of an AMI-C system. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (inclu

13、ding any amendments) applies. ISO 22902-1, Road vehicles Automotive multimedia interface Part 1: General technical overview ISO 22902-2, Road vehicles Automotive multimedia interface Part 2: Use cases ISO 22902-7, Road vehicles Automotive multimedia interface Part 7: Physical specification 3 Basis o

14、f system requirements 3.1 System attributes When fully implemented, an system shall be characterized by the following attributes. The requirements contained within this document are intended to support these attributes: Scalability Configure-ability Expandability Upgradeability Commonality Operabili

15、ty Interoperability Modularity Security Testability BS ISO 22902-3:20062 4 System requirements 4.1 General requirements An AMI-C system is a collection of compliant components interconnected in a manner that provides the intended set of functions and services. Interoperability is achieved by specify

16、ing common interfaces, signals, network messages, physical environment and power management requirements. 4.1.1 A system shall be logically or physically separated from other vehicle subsystems in a manner that inhibits undesirable interactions with those systems while promoting interchange of perti

17、nent vehicle data across the interfacing boundary. 4.1.2 A system shall support the capability to add or remove hardware and software components across multiple network technologies. 4.1.3 A system shall, through the use of vehicle interface and service APIs, allow the deployment of various telemati

18、cs and infotainment services over the lifetime of the vehicle. 4.1.4 A system shall support a common message set across multiple wired and wireless network technologies. 4.1.5 A system shall provide a common method of power management. 4.1.6 A system shall provide a common method of diagnostics. 4.1

19、.7 A system shall provide a common method of interconnection. 4.1.8 A system shall provide a standard interface to the vehicles HMI. 4.1.9 A system shall provide a common method to identify and coordinate functional services in the system, service discovery, and power-moding mechanisms. 4.1.10 A sys

20、tem shall support a mechanism to recover from a non-operational state. 4.1.11 A system shall have access to a minimum set of vehicle services including the audio subsystem, power management and some pre-defined body control functions. 4.1.12 A system shall be configured within the guidelines and fra

21、mework specified in ISO 22902-1 - system architecture. 4.1.13 A system shall maintain or enhance the safe operation of a vehicle. 4.2 Modularity The elements of an system shall have standardized interfaces so the elements can be modified, upgraded or replaced without requiring a change to the other

22、elements in the system. 4.3 Configure-ability 4.3.1 The system shall allow a configuration to be expanded by adding or deleting additional elements, in combination, to achieve different content levels. It is a typical practice that vehicle systems with many features have some features as options for

23、 end customer to select. Configure-ability enables scalability, expandability, and upgradeability. BS ISO 22902-3:200634.4 Interoperability The features and functions of a system require the coordinated effort by several components in a system to meet the intended performance levels of the manufactu

24、re. 4.4.1 A compliant components shall be compatible with all of the specifications related to the intended functions being provided. 4.4.2 A component placed on the network shall be compatible with the network message set, power-moding, device discovery and physical layer specifications. A componen

25、t shall not interfere with the operation of an system. 4.5 Interchangeability These elements of an AMI-C system shall be interchangeable with similar modules supplied by different manufacturers. 4.6 Security The AMI-C system shall provide security from several perspectives: 4.6.1 A system shall supp

26、ort a mechanism to prevent a malicious attack for the purpose of modifying, degrading, corrupting or otherwise intentionally disrupting normal operation by the owner. 4.6.2 A system shall support a mechanism to limit access to vehicle services to authorized entities. 4.6.3 A system shall support a m

27、echanism to limit access to stored information to authorized entities. 4.6.4 A system shall support a mechanism to restrict downloads to only trusted applications. 4.6.5 A system shall support a mechanism to prevent unauthorized wireless devices and services from accessing the system. 4.6.6 A system

28、 shall support a mechanism to protect private data during data transfer between local wired and wireless devices. 4.6.7 A system shall support a mechanism to protect data during data transfer between the system and an off-board system. 4.7 Serviceability and testing An AMI-C system shall comply with

29、 the following serviceability and testing requirements: 4.7.1 A system shall be testable and comply with diagnostics service practices in the automotive industry. 4.7.2 A system shall provide mechanisms to allow a service technician to isolate faulty components of AMI-C systems for replacement or re

30、pair. These mechanism may be off-board, on-board or a combination of these methods 4.7.3 A system shall provide the capability for a service technician to determine the configuration of a system under test by interrogating the system through a diagnostic port and to determine the services provided b

31、y the system. Services must be identified with software and/or hardware version numbers. 4.7.4 A system shall provide mechanisms to assist in testing for correct operation at the time of vehicle assembly. BS ISO 22902-3:20064 4.8 Service discovery requirements The service discovery requirements for

32、an AMI-C system include: 4.8.1 A system shall support service discovery mechanisms that identify active services available to the applications installed on the system. 4.8.2 The service discovery mechanism shall identify the services in a manner that is directly obtainable by controller running appl

33、ication programs. 4.8.3 The service being made available to controllers shall, at a minimum, provide the following information: name and version; features of service; device providing service. 4.8.4 The service discovery mechanism shall establish the services available when the system is initially p

34、owered and each time the system is reset. 4.8.5 The service discovery mechanism shall update the list of services available when a new service is added or deleted from the system. 4.8.6 In a system with a network, device discovery must be completed prior to service discovery. 4.8.7 If a component is

35、 capable of determining failure modes of services provided, it will, upon failure detection, remove the disabled services from the registry. 4.8.7.1 The component will restore the services to the registry when the service function is restored. 5 Architecture requirements The architecture is the fram

36、ework upon which the AMI-C system is formulated and configured. This framework defines how the various components of an system are interconnected, how the system logically operates, and how the system achieves all of AMI-Cs business and technical objectives. The key elements of the architecture are

37、the following: vehicle interface an interface to other vehicle subsystems, information and signals; network standard network and message sets to provide data interchange and control between components; host a computer used to execute cross-platform, downloadable application code; Consumer Convenienc

38、e Access (CCA) an interface to external consumer device(s). The actual implementation and use of these elements is dependent on the requirements by the individual carmakers. However, a vehicle interface must be present in a valid architectural implementation. The following are the general requiremen

39、ts for these key elements. BS ISO 22902-3:200655.1 Vehicle interface 5.1.1 A system shall have a vehicle interface that allows signals or data to be passed between the system and the vehicle. 5.1.2 The vehicle interface shall use a common message set instantiated in network messages or software APIs

40、 when interacting with the vehicle. 5.1.3 The vehicle interface shall contribute to the safe operation of a vehicle by complying with the requirements in Sections 4.1 and 4.6 of this document. 5.2 Network requirements An AMI-C network shall comply with the following set of requirements: 5.2.1 A netw

41、ork shall be capable of using the Transmission Control Protocol/Internet Protocol (TCP/IP). 5.2.2 A network shall be capable of expandability. 5.2.3 A network shall establish its access to the vehicle through a vehicle interface. 5.2.4 If there are two or more networks in a vehicle and if two networ

42、ks need to jointly perform certain functions, there shall be a gateway between the two networks. 5.2.4.1 A network gateway between two networks shall manage message translation between the networks. 5.2.4.2 A multiple network configuration using gateways shall inhibit a “circular“ passage of network

43、 messages that would result in errors or system failure. 5.2.5 A network shall contribute to the safe operation of a vehicle by complying with the requirements in Sections 4.1 and 4.6 of this document. 5.2.6 A network shall provide a device discovery service and support the service discovery require

44、ments in Section 4.8 of this document. 5.3 Host requirements An AMI-C host shall comply with the following set of requirements: 5.3.1 The host shall contain a common software platform that allows application portability. 5.3.1.1 The common software platform shall support libraries of software elemen

45、ts that support system and application functions. 5.3.1.2 The common software platform shall support execution of application software with the appropriate libraries. Several applications may co-exist on the platform at any time. 5.3.2 A host shall provide a uniform mechanism for provisioning of sof

46、tware components. 5.3.3 A host shall provide applications access to a pre-determined set of vehicle services. 5.3.4 A host shall contribute to the safe operation of a vehicle by complying with the requirements in of this document. BS ISO 22902-3:20066 5.4 Consumer Convenience Access (CCA) To provide

47、 compatibility with consumer devices, the system may provide an interface that allows an external device, such as a PDA, to connect to the system. Once connected, the device may share data with the vehicle, synchronize services, provide control functions or may use the vehicles human machine interfa

48、ce. A CCA shall comply with the following requirements: 5.4.1 The interfacing device (gateway, bridge, converter, cable adaptor, local wireless access point, etc.) shall make provisions to isolate the operation and function of the personal device such that failure or incorrect operation or attachmen

49、t will not permanently damage the system. 5.4.2 The CCA shall support device discovery and service discovery when it interfaces with an external device. 5.4.3 The CCA shall allow connection or removal of devices when the vehicle power is applied and operating normally. This feature shall not affect normal operation of features and functions not related to the device. BS ISO 22902-3:2006blankBS ISO BSI389 Chiswick High RoadLondonW4 4AL22902-3:2006BSI British Standards InstitutionBSI is the independent

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1