AMI-C SPEC 1002-0-0
`
`Functional
`Requirements
`– Release 1
`
`Release 1, 2001
`
`AHM, Exh. 1024, p. 1
`
`

`

`
`
`Functional Requirements –
`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. 1024, p. 2
`
`

`

`AMI-C SPEC 1002.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
`
`Document No.
`
`AMI-C SPEC 1002
`Document Title:
`
`Functional Requirements – Release 1
`
`
` 0
`
`Baseline No:
`
`
`
`
`Revision Date
`
`
`Affected Sections
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Revision No.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`AHM, Exh. 1024, p. 3
`
`

`

`AMI-C SPEC 1002.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
`
`
`
`Document No.
`
`AMI-C SPEC 1002
`Document Title:
`
`Functional Requirements – Release 1
`
`
` 0
`
`Baseline No.
`
`
`
`
`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. 1024, p. 4
`
`

`

`AMI-C SPEC 1002.0.0
`
`Table of Contents
`
`FOREWORD...................................................................................................... 1
`
`INTRODUCTION................................................................................................ 1
`
`1. SCOPE ....................................................................................................... 2
`
`1.1. Vehicle with AMI-C Compliant Networks and Components......................... 2
`
`1.2. Vehicle Segments ........................................................................................... 3
`1.2.1.
`Vehicle Services........................................................................................ 3
`1.2.2.
`AMI-C Compliant Networks and Components ........................................... 3
`1.2.3.
`AMI-C Compliant Customer Access Port................................................... 3
`
`1.3. Networks ......................................................................................................... 3
`1.3.1.
`Low-Speed Network.................................................................................. 3
`1.3.2.
`High-Speed Network ................................................................................. 3
`1.3.3. Wireless Network ...................................................................................... 3
`
`1.4. Physical Topology .......................................................................................... 4
`1.4.1.
`Customer Access Connector..................................................................... 4
`1.4.2.
`AMI-C Connector ...................................................................................... 4
`1.4.3.
`Vehicle Services Interface......................................................................... 4
`1.4.4.
`Vehicle Services........................................................................................ 4
`1.4.5.
`Vehicle Manufacturer Network Gateway ................................................... 4
`
`1.5. AMI-C Levels ................................................................................................... 4
`1.5.1.
`AMI-C Compliant Device ........................................................................... 4
`1.5.2.
`AMI-C Compliant Controller ...................................................................... 5
`1.5.3.
`AMI-C Java Host....................................................................................... 5
`
`2. NORMATIVE REFERENCES..................................................................... 5
`
`2.1. AMI-C Documents........................................................................................... 5
`
`2.2. Other Documents............................................................................................ 6
`
`3. TERMS AND DEFINITIONS....................................................................... 6
`
`4. SPECIFICATION ........................................................................................ 6
`
`4.1. General Requirements.................................................................................... 6
`4.1.1.
`AMI-C Compliant Networks ....................................................................... 6
`4.1.2.
`Scalability and Upgradability ..................................................................... 7
`4.1.3.
`Backward Compatibility............................................................................. 8
`4.1.4.
`Compliance............................................................................................... 8
`
`
`
`AHM, Exh. 1024, p. 5
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.2. Physical Requirements .................................................................................. 8
`4.2.1.
`AMI-C Compliant Customer Access Port................................................... 8
`4.2.2.
`Power Lines .............................................................................................. 9
`4.2.3.
`Power Mode.............................................................................................. 9
`4.2.4.
`Analog Audio Lines ................................................................................. 10
`4.2.5.
`Analog Video Lines ................................................................................. 10
`4.2.6.
`Antennas................................................................................................. 10
`4.2.7.
`Clock and Calendar................................................................................. 10
`4.2.8. Wiring Interconnection............................................................................. 11
`4.2.9.
`Connectors.............................................................................................. 11
`4.2.10. Component Environment......................................................................... 12
`4.2.11. Packaging ............................................................................................... 12
`
`4.3. Network Requirements................................................................................. 12
`
`4.4. Architecture Requirements .......................................................................... 13
`4.4.1.
`General Architecture Requirements ........................................................ 13
`4.4.2.
`Boot Procedure ....................................................................................... 13
`4.4.3.
`Reset Procedure ..................................................................................... 14
`4.4.4.
`Plug & Play ............................................................................................. 14
`4.4.5.
`Version Management .............................................................................. 15
`4.4.6.
`System Capacity and Performance ......................................................... 16
`4.4.7.
`Security................................................................................................... 16
`4.4.8.
`Diagnostics ............................................................................................. 17
`4.4.9.
`Preferences and Personal Data .............................................................. 18
`
`4.5. Software Requirements................................................................................ 18
`
`APPENDIX A: REQUIREMENT AND RECOMMENDATION LANGUAGE ... 20
`
`
`
`AHM, Exh. 1024, p. 6
`
`

`

`AMI-C SPEC 1002.0.0
`
`Table of Figures
`
`Figure 1. Representative Block Diagram.................................................................. 2
`
`
`
`AHM, Exh. 1024, p. 7
`
`

`

`AMI-C SPEC 1002.0.0
`
`AMI-C SPEC 1002.0.0
`
`Functional Requirements – Release 1
`
`
`
`Foreword
`
`The Functional Requirements 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
`
`The development of any significant system design or comprehensive set of
`specifications must start with a description of the system’s functional intent and
`be supplemented with examples of applications showing how the system is to
`be used. These descriptions provide direction to the design engineers who are
`charged with designing the system from the specifications. Furthermore, 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 on this
`Functional Specification and the Use Case document (reference AMI-C SPEC
`1003: Use Cases). These documents combined make a complete set of
`specifications to provide direction to potential users, provide planning guidance,
`and set 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.
`
`AMI-C Functional Requirements – Release 1 Page 1 of 20
`
`AHM, Exh. 1024, p. 8
`
`

`

`AMI-C SPEC 1002.0.0
`
`1. Scope
`
`AMI-C Functional Requirements apply to vehicles with AMI-C compliant
`networks and components, vehicle segments, networks, physical topology, and
`AMI-C levels of compliant controllers, devices and hosts. The following
`sections contain descriptions of AMI-C compliant networks and components
`that can bein a vehicle:
`
`1.1.
`
`Vehicle with AMI-C Compliant Networks and Components
`
`A vehicle with AMI-C compliant networks and components hasa setof
`networked components conforming to the AMI-C Specifications.
`
`Vehicle manufacturers can choose to implement any subset of the AMI-C
`Specifications. See “Network Requirements,” section 4.3.1 of this specification,
`for the minimum required configuration.
`
`Vehicle elements may be combined orintegrated in a variety of ways, but each
`vehicle will have one or more of the block-elements represented on the
`following graphic:
`
`AMI-C Compliant
`System
`——» ; + OEMProprietary —
`1
`_
`|
`Gustomer
`
`ae (minimumseti :
`
`
`(optional)
`:
`{optional)
`.
`
` Audio/
`Display
`
`Services
`
`
` Vehicle
`Network
`
`Gateway
`Vehicle Network
`
`'
`
`Note: Host has a JVM
`
`Figure 1. Representative Block Diagram
`
`AMI-C Functional Requirements — Release 1
`
`Page 2 of 20
`
`AHM, Exh. 1024, p. 9
`
`I I
`
`
`
`
`
`VehicleServicesInterface
`
`AHM, Exh. 1024, p. 9
`
`

`

`AMI-C SPEC 1002.0.0
`
`1.2.
`
`Vehicle Segments
`
`Three different areas can be identified:
`
`1.2.1.
`
`Vehicle Services
`
`Vehicle services are the information and services provided by the vehicle
`manufacturer through a Vehicle Services Interface (or Vehicle Manufacturer
`Gateway). These services are proprietary to the vehicle manufacturer.
`
`1.2.2.
`
`AMI-C Compliant Networks and Components
`
`AMI-C compliant networks and components conform to AMI-C Specifications.
`Services provided by these components shall be made available on the
`vehicle’s AMI-C compliant network.
`
`1.2.3.
`
`AMI-C Compliant Customer Access Port
`
`AMI-C compliant Customer Access Ports allow a direct interface to the AMI-C
`backbone signal set (network cables and signals, power lines), providing
`access for components added after in-line assembly.
`
`1.3. Networks
`
`AMI-C may provide specifications for three different types of networks:
`
`1.3.1.
`
`Low-Speed Network
`
`Providing basic control commands and packet data to connected components
`with a global low-cost target approach. The specifications must be able to
`support analog lines for audio and video streaming.
`
`1.3.2.
`
`High-Speed Network
`
`Providing the support to extended multimedia functions, with audio and video
`streaming support, as well as high-speed data transfer.
`
`1.3.3.
`
`Wireless Network
`
`Providing over-the-air networking of components.
`
`AMI-C Functional Requirements – Release 1 Page 3 of 20
`
`AHM, Exh. 1024, p. 10
`
`

`

`AMI-C SPEC 1002.0.0
`
`1.4.
`
`Physical Topology
`
`1.4.1.
`
`Customer Access Connector
`
`A specific external port that provides an electrical connector to access the AMI-
`C standard signal set (power, networks, P-mode, etc.).
`
`1.4.2.
`
`AMI-C Connector
`
`One of a set of standard connectors that comprises the network, audio/video,
`power/ground and wake-up signal set for attaching components to an AMI-C
`compliant network.
`
`1.4.3.
`
`Vehicle Services Interface
`
`The component that provides vehicle services to AMI-C compliant networks and
`components through an AMI-C compliant network.
`
`1.4.4.
`
`Vehicle Services
`
`A function, data or system signal related to the vehicle itself, such as diagnostic
`information or vehicle status (speed, fuel level, etc.), that controls vehicle
`functions, such as door locking and unlocking.
`
`1.4.5.
`
`Vehicle Manufacturer Network Gateway
`
`A protected message exchange between an AMI-C compliant network and the
`vehicle specific network.
`
`1.5. AMI-C Levels
`
`The AMI-C Specifications defines three levels of components connected to
`AMI-C compliant networks:
`
`1.5.1.
`
`AMI-C Compliant Device
`
`A piece of hardware connected to an AMI-C compliant network that
`understands and can answer to part of the AMI-C message set across this
`network, in order to achieve a function.
`
`AMI-C Functional Requirements – Release 1 Page 4 of 20
`
`AHM, Exh. 1024, p. 11
`
`

`

`AMI-C SPEC 1002.0.0
`
`1.5.2.
`
`AMI-C Compliant Controller
`
`A processor connected to an AMI-C compliant network that provides services
`to, or uses services of, other devices or controllers using the AMI-C message
`set across its network. An AMI-C compliant controller differs from an AMI-C
`Java Host in that it runs only embedded software.
`
`1.5.3.
`
`AMI-C Java Host
`
`A computer capable of running AMI-C Java Applications. An AMI-C Java Host
`shall run a Java Virtual Machine in order to export the high-level AMI-C Java
`Application Programming Interface (API).
`
`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 1001 Release 1 Architecture
`
`AMI-C SPEC 4001 Physical Specification
`
`AMI-C SPEC 3001 Vehicle Interface Specification – Release 1
`
`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 SPEC 1004 AMI-C Release 1 Message-Level Security
`
`AMI-C REF DOC 1003
`
`AMI-C Use Cases
`
`AMI-C Functional Requirements – Release 1 Page 5 of 20
`
`AHM, Exh. 1024, p. 12
`
`

`

`2.2. Other Documents
`
`AMI-C SPEC 1002.0.0
`
`
`
`IDB Physical Layer
`
`IDB Link Layer
`
`IDB Transport Layer
`
`IDB Application Message Layer
`
`IDB Lexicon
`
`IDB Message Set for Device Classes
`
`
`
`
`
`
`
`SAE J2366-1
`
`SAE J2366-2
`
`SAE J2366-4
`
`SAE J2366-7
`
`SAE J2366-7LX
`
`SAE J2366-7X
`
`
`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
`expressions used throughout this specification that are indicative of
`requirements and recommendations.
`
`
`4. Specification
`
`4.1. General Requirements
`
`4.1.1.
`
`AMI-C Compliant Networks
`
`An AMI-C compliant network configuration shall provide access to a minimum
`set of vehicle services using at least one AMI-C compliant network through at
`least one AMI-C Vehicle Manufacturer Network Gateway.
`
`4.1.1.1
`
`4.1.1.2
`
`4.1.1.3
`
`4.1.1.4
`
`The AMI-C Specifications shall define the list of minimum vehicle
`services that are available with an AMI-C compliant network.
`
`Any AMI-C compliant service offered shall be compliant with AMI-C
`standard APIs and network messages.
`
`An AMI-C compliant component shall use an AMI-C Interface
`Connector.
`
`The AMI-C Specifications shall define Gateways to connect all the
`AMI-C supported networks. The implementation of more than one
`network in a vehicle is up to each vehicle manufacturer.
`
`AMI-C Functional Requirements – Release 1 Page 6 of 20
`
`AHM, Exh. 1024, p. 13
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.1.1.5
`
`4.1.1.6
`
`Each vehicle manufacturer may define the presence and number of
`AMI-C compliant networks and components in the vehicle (devices,
`controllers and hosts).
`
`Any AMI-C compliant component should be able to run on any AMI-
`C compliant network (interoperability). Each vehicle manufacturer
`shall be able to define what components can be installed in their
`vehicles.
`
`4.1.2.
`
`Scalability and Upgradability
`
`The AMI-C Specifications shall provide the capability to expand and/or upgrade
`the system-supported features and components’ performance over the life cycle
`of the vehicle.
`
`4.1.2.1 Component manufacturers should be able to upgrade their
`components without affecting AMI-C compliant networks and other
`components in the vehicle.
`
`4.1.2.2 The AMI-C Specifications shall allow for new hardware components
`to be added to the vehicle, using the Customer Access Port (an
`adapter) on the AMI-C compliant network or using the AMI-C wireless
`interface. The policies for allowing the upgrading of AMI-C compliant
`hardware and execution procedures are up to each vehicle
`manufacturer.
`
`4.1.2.3
`
`If an AMI-C Java Host is present, the AMI-C Specifications shall
`provide methods for adding new functions and features through the
`installation of new software or updated versions of existing software.
`The policies for allowing of upgrading of AMI-C compliant software
`and execution procedures are up to each vehicle manufacturer.
`
`4.1.2.4 Software upgrades to an AMI-C compliant network can be made
`locally (e.g., through a local CD) or through an AMI-C compliant
`network (e.g., through networked CD/Customer Access Port/remote
`download). In the latter, the AMI-C Specifications shall provide for an
`acceptable level of security of these operations. It is up to each
`vehicle manufacturer to implement additional protection or to inhibit
`these operations.
`
`4.1.2.5 AMI-C shall not specify the replacement of hardware sub-
`components (e.g. boards, module) within AMI-C compliant networks
`and components. These decisions are at the discretion of each
`vehicle manufacturer.
`
`AMI-C Functional Requirements – Release 1 Page 7 of 20
`
`AHM, Exh. 1024, p. 14
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.1.3.
`
`Backward Compatibility
`
`The AMI-C Specifications may be changed and may evolve over time, based on
`changing requirements and available technologies. To minimize the complexity
`and obsolescence of systems based on these specifications, compatibility shall
`be maintained, where possible, over several levels of released specifications.
`Therefore, backward compatibility is an important attribute of component
`design.
`
`Succeeding AMI-C Specifications should not contain changes that preclude
`operation or compatibility with previous versions of the AMI-C Specifications,
`except when new technologies are adapted that preclude capability based on
`inherent design differences. A change that precludes compatibility with previous
`versions should be announced at least 2 years in advance of the release of the
`new AMI-C Specifications.
`
`If an enabling off-board technology or infrastructure is no longer available,
`making an on-board feature, function, or technology obsolete, an immediate
`change to the AMI-C Specifications may be made that is not backward
`compatible without waiting 2 years.
`
`4.1.4.
`
`Compliance
`
`4.1.4.1 The performance of any AMI-C compliant networks, components, or
`software interfaces shall be validated to the appropriate specification
`levels.
`
`4.1.4.2 A vehicle with an AMI-C compliant network shall have a Vehicle
`Services Interface with a minimum set of services provided.
`
`4.2.
`
`Physical Requirements
`
`4.2.1.
`
`AMI-C Compliant Customer Access Port
`
`An AMI-C compliant Customer Access Port is an adapter to an external device.
`The adapter contains an electrical connector to access AMI-C compliant
`networks.
`
`
`
`4.2.1.1
`
`The AMI-C Specifications shall allow each vehicle manufacturer to
`provide one or more AMI-C compliant Customer Access Ports. Their
`availability on the vehicles and their location are vehicle
`manufacturer dependent.
`
`AMI-C Functional Requirements – Release 1 Page 8 of 20
`
`AHM, Exh. 1024, p. 15
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.2.1.2
`
`Each component attached to an AMI-C compliant Customer Access
`Port shall support the specifications for the AMI-C compliant network
`to which it is connected. For instance, if the network requires plug-
`and-play, the Customer Access Port shall support it.
`
`4.2.2.
`
`Power Lines
`
`4.2.2.1 The AMI-C Specifications shall define supply voltage ranges and
`levels compatible with an automotive environment and for all
`operating situations, including cranking.
`
`4.2.2.2 Maximum current levels shall be defined whenever needed, such as
`consumption in off-state or maximum current flow through an AMI-C
`compliant Customer Access Port.
`
`4.2.2.3 Electrical grounding of components shall preclude ground loops and
`high-current flow from affecting normal system operation.
`
`4.2.3.
`
`Power Mode
`
`4.2.3.1 An AMI-C compliant network shall support:
`• On (active and powered)
`• Standby (partially active; not fully functional state)
`• Off (power down; non-active)
`
`4.2.3.2 The AMI-C Specifications shall indicate all the transitions between
`these three different modes, specifying when they should happen and
`what actions are required.
`
`4.2.3.3 The AMI-C Specifications shall allow for units having a self-powered
`wake-up mode to wake-up target units through the AMI-C compliant
`networks. Gateways should allow for wake-up internetworking. This
`applies only to AMI-C compliant networks and is not mandatory for
`non-AMI-C compliant components and networks.
`
`4.2.3.4 The AMI-C Specifications shall minimize current consumption when
`the key is in off mode and shall provide a way to alert the user or stop
`
`operations after a safe limit is reached or battery level drops under a
`threshold.
`
`
`
`AMI-C Functional Requirements – Release 1 Page 9 of 20
`
`AHM, Exh. 1024, p. 16
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.2.3.5 Component operation in stand-by mode shall be switched to the off
`mode after a predetermined period or when the battery drops to some
`pre-defined threshold level.
`
`4.2.4.
`
`Analog Audio Lines
`
`4.2.4.1 The low-speed network shall be extended to include an analog signal
`to interconnect audio components that need it.
`
`4.2.4.2 Multiple audio inputs can connect to this line. The arbitration of who is
`to transmit the signal (muting, etc.) shall be managed and defined in
`the low-speed network command set.
`
`4.2.4.3 The analog audio line shall be able to support at least mono voice
`and stereo music signals.
`
`4.2.5.
`
`Analog Video Lines
`
`4.2.5.1 The AMI-C Specifications shall allow the low-speed network to use an
`optional analog video line to forward video to a display.
`
`4.2.5.2 Multiple video inputs can connect to this line. The arbitration of who is
`to transmit the signal shall be managed and defined in the low-speed
`network command set.
`
`4.2.6.
`
`Antennas
`
`4.2.6.1 The AMI-C Specifications shall not specify antennas or antenna
`interconnects.
`
`4.2.7.
`
`Clock and Calendar
`
`4.2.7.1 A standard clock and calendar function shall be available in all AMI-C
`compliant vehicles as a service available through the network. The
`clock calendar may be reset and maintained under network message
`control from a user API. The clock should not reset or lose time when
`vehicle powered is removed for less than 30 minutes.
`
`AMI-C Functional Requirements – Release 1 Page 10 of 20
`
`AHM, Exh. 1024, p. 17
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.2.8.
`
`Wiring Interconnection
`
`4.2.8.1 Components that are compliant with AMI-C specifications should be
`connected in a manner that makes installation, service, and
`upgrading easy for vehicles that have been in service for awhile.
`
`4.2.8.2 Wiring between components should be facilitated in a manner that
`does not require cutting or modifying of any existing wire harnesses
`to add or remove additional components to or from a network.
`
`4.2.8.3 Service or replacement wiring components should be generally
`available to the public or service community so unnecessary
`complexity is avoided and an unskilled person can add new
`components.
`
`4.2.8.4 A standard interface to compliant components should be used so all
`similar components can interface with common connector and wiring
`sets. A unique cable and connector may be used for each high-
`speed interface and low-speed interface. Any unique cabling and
`connectors required by a component shall be separate so the unique
`requirements are separate from the AMI-C connector interface.
`
`4.2.8.5 The method to interconnect compliant components shall not require
`significant “give-away” costs for implementation in any vehicle.
`
`4.2.8.6 Any unique requirements by the network to mitigate EMC or
`transmission losses, such as termination resistors, shall be
`accommodated in the wiring so their use and facilitation is automatic
`and transparent to a servicing person.
`
`4.2.8.7 The wiring of a compliant network shall meet vehicle interior
`environmental requirements, such as 85 degrees centigrade. Under
`hood temperatures must be sustained.
`
`4.2.8.8 Wiring and connectors shall meet generally accepted requirements,
`such as those specified by standards organizations.
`
`4.2.9.
`
`Connectors
`
`4.2.9.1 The AMI-C Specifications shall provide for AMI-C connectors for all
`AMI-C specified components.
`
`4.2.9.2 Connector specifications shall be compatible with the automotive
`environment (mating force, durability, etc.).
`
`AMI-C Functional Requirements – Release 1 Page 11 of 20
`
`AHM, Exh. 1024, p. 18
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.2.10.
`
`Component Environment
`
`4.2.10.1 AMI-C compliant networks and components shall operate in the
`standard automotive environment, subject to a common set of
`environmental specifications such as:
`• Maximum power consumption
`• Electro-Magnetic Compatibility (EMC)
`• Physical damage and data loss
`• Temperature
`• Condensation
`• Vibration and shock
`• Acoustics
`
`4.2.11.
`
`Packaging
`
`4.2.11.1 The AMI-C Specifications shall provide for box-level physical
`interchangeability by specifying a range of packaging formats (e.g.,
`DIN-type boxes or even racks).
`
`4.3. Network Requirements
`
`4.3.1 For a vehicle with AMI-C compliant networks and components, at least
`one AMI-C compliant network is required. In its minimal form, the
`network may be just the Vehicle Manufacturer Gateway.
`
`4.3.2 The AMI-C Specifications shall cover all the possible gateways between
`the supported networks (low-speed – high-speed, low-speed – wireless,
`high-speed – wireless), as well as between those networks and the
`vehicle manufacturer side of the vehicle (low-speed – vehicle
`manufacturer, high-speed – vehicle manufacturer, wireless – vehicle
`manufacturer).
`
`4.3.3 The high-speed network shall transfer many audio and visual streams in
`parallel. The use of these channels shall be flexible, since many different
`sources can originate the streams that can be used by many destination
`nodes.
`
`4.3.4 Emergency and other high-priority applications shall always be able to
`acquire necessary bandwidth and resources in a timely fashion.
`
`AMI-C Functional Requirements – Release 1 Page 12 of 20
`
`AHM, Exh. 1024, p. 19
`
`

`

`AMI-C SPEC 1002.0.0
`
`4.3.5 The AMI-C Specifications shall allow for protection mechanisms for
`vehicle data flowing through the Vehicle Manufacturer Gateway. The
`AMI-C Specifications shall allow for different protection levels, according
`to different classes of data. It is up to each vehicle manufacturer to
`define what level of protection is required and for what data.
`
`4.3.6 The endorsed AMI-C compliant networks shall support plug- and-play
`capability.
`
`4.3.7 The AMI-C Specifications shall define a full set of vehicle services
`available to AMI-C compliant networks through the Vehicle Manufacturer
`Gateway and define a minimum set that shall be implemented by each
`vehicle manufacturer who chooses to install an AMI-C compliant
`network.
`
`4.4. Architecture Requirements
`
`4.4.1.
`
`General Architecture Requirements
`
`4.4.1.1 An AMI-C compliant network shall have access to a system clock and
`calendar. This clock shall be user-settable, adjustable for time zones
`and support daylight savings time conversions. Each AMI-C
`compliant component should have access to the system clock.
`
`4.4.1.2 The AMI-C Specifications shall allow a vehicle manufacturer to
`configure AMI-C compliant components to operate only with a
`specific vehicle so that a stolen component cannot operate