This document is provided as a help to those who intend to submit a response to Call for Technologies: Template for Responses: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC). Text in

  1. Blue (as in this sentence) provides guidance to submitters and should not be included in a submission.
  2. Green (as in this sentence) is text that must mandatorily be present. If the submission is in multiple files, each file shall include the statement marked as green. If a submission does not include the text marked as green, the submission will be rejected.
  3. Black  (as in this sentence) text that is suggested and respondents may use in a submission.


1          Introduction

This document is submitted by <organisation name> (if an MPAI Member) and/or by <organisation name>, a <company, university etc.> registered in <…> (if not an MPAI member) in response to the Call for Technologies: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC) [5] issued by Moving Picture, Audio and Data Coding by Artificial Intelligence (MPAI) on 2024/05/15.

In this document, the submitter, proposes technologies that satisfy the Functional Requirements of Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC) [6] and the Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC) [7] both issued by MPAI on 2024/05/15.


This document also contains comments on the Use Cases and Functional Requirements as requested by N1768.


This document also contains proposed technologies that satisfy additional requirements as allowed by N1768.


<Company and/or Member> explicitly agrees to the steps of the MPAI standards development process defined in Annex 1 to the MPAI Statutes (N421) and [1], in particular <Company and/or Member> declares that  <Company and/or Member> or its successors will make available the terms of the Licence related to its Essential IPR according to the Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC) [7], alone or jointly with other IPR holders after the approval of Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC) by the MPAI General Assembly and in no event after commercial implementations of the Technical Specification become available on the market.


< Company and/or Member> acknowledges the following points:

  1. MPAI in not obligated, by virtue of this CfT, to select a particular technology or to select any technology if those submitted are found inadequate.
  2. A representative of <Company and/or Member> shall present this submission at a Requirements (AIH) meeting communicated by the MPAI Secretariat. If no <Company and/or Member> will attend the meeting and present their submission, this will be discarded.
  3. <Company and/or Member> shall make available a working implementation – including source code – for use in the development of Reference Software Specification: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC) and eventual publication by MPAI before the technology submitted is published in Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC).
  4. The software submitted may be written in programming languages that can be compiled or interpreted and in hardware description languages, upon acceptance by MPAI for further eval­uation of their submission in whole or in part.
  5. <Company> shall immediately join MPAI upon acceptance by MPAI for further evaluation of this submission in whole or in part.
  6. If <Company> does not join MPAI, this submission shall be discarded.

2          Information about this submission

This information corresponds to Annex 1 of N1768. It is included here for submitter’s convenience.


  1. Title of the proposal
  2. Organisation: company name, position, e-mail of contact person
  3. What are the main functionalities of your proposal?
  4. Does your proposal provide or describe a formal specification and APIs?
  5. Will you provide a demonstration to show how your proposal meets the evaluation criteria?

3          Comments on/extensions to requirements (if any)


4          Overview of Functional Requirements supported by this submission

Please answer Y or N. Detail on the specific answers should be provided in Chapter 6.


Section Data Type Response
Human-CAV Interaction
5.5.1 Personal Preferences Y/N
5.5.2 Personal Profile Y/N
5.5.3 Input Text Y/N
5.5.4 Point of View Y/N
5.5.5 Point of View Y/N
5.5.6 Audio Object Y/N
5.5.7 Visual Object Y/N
5.5.8 Audio-Visual Object Y/N
5.5.9 Audio-Visual Basic Scene Descriptors Y/N
5.5.10 Audio-Visual Scene Descriptors Y/N
5.5.11 Audio Scene Descriptors Y/N
5.5.12 Visual Scene Descriptors Y/N
5.5.13 Body Descriptors Y/N
5.5.14 Face Descriptors Y/N
5.5.15 Face ID Y/N
5.5.16 Speaker ID Y/N
5.5.17 Audio Object ID Y/N
5.5.18 Visual Object ID Y/N
5.5.19 Meaning Y/N
5.5.20 Personal Status Y/N
5.5.21 Avatar Model Y/N
5.5.22 Speech Model Y/N
5.5.23 Output Audio Y/N
5.5.24 Output Visual Y/N
5.5.25 HCI-AMS Messages Y/N
5.5.26 Ego-Remote HCI Messages Y/N
6 Environment Sensing Subsystem (ESS)
6.6.1 Input Audio Y/N
6.6.2 Input Visual Y/N
6.6.3 RADAR Data Y/N
6.6.4 Input LiDAR Y/N
6.6.5 Ultrasound Data Y/N
6.6.6 GNSS Data Y/N
6.6.7 Offline Map Data Y/N
6.6.8 Audio-Visual Scene Descriptors Y/N
6.6.9 Visual Scene Descriptors Y/N
6.6.10 Lidar Scene Descriptors Y/N
6.6.11 RADAR Scene Descriptors Y/N
6.6.12 Ultrasound Scene Descriptors Y/N
6.6.13 Offline Maps Scene Descriptors Y/N
6.6.14 Audio Scene Descriptors Y/N
6.6.15 Traffic Signal Descriptors Y/N
6.6.16 Basic Environment Representation Y/N
6.6.17 Alert Y/N
7 Autonomous Motion Subsystem (AMS)
7.6.1 CAV Identifier Y/N
7.6.2 Basic Environment Representation Y/N
7.6.3 Full Environment Representation Y/N
7.6.4 Ego-Remote AMS Messages Y/N
7.6.5 Offline map Y/N
7.6.6 Route Y/N
7.6.7 Path Y/N
7.6.8 Pose Y/N
7.6.9 Trajectory Y/N
7.6.10 Goal Y/N
7.6.11 AMS-HCI Message Y/N
7.6.12 AMS-MAS Message Y/N
7.6.13 Road State Y/N
8 Motion Actuation Subsystem (MAS)
8.6.1 Odometer Data Y/N
8.6.2 Speedometer Data Y/N
8.6.3 Accelerometer Data Y/N
8.6.4 Spatial Attitude Y/N
8.6.5 Other Environment Data Y/N
8.6.6 MAS-AMS Message Y/N
8.6.7 Brake Command Y/N
8.6.8 Brakes Response Y/N
8.6.9 Steering Wheel Command Y/N
8.6.10 Steering Wheels Response Y/N
8.6.11 Wheel Motor Command Y/N
8.6.12 Wheel Motors Response Y/N
9 CAV-to-Everything (V2X) (Informative)
9.1 V2X Communication Y/N
9.2 Input and output data Y/N
9.2.1 CAVs within range Y/N
9.2.2 CAV-aware equipment Y/N
9.2.3 Other non-CAV vehicles Y/N
9.2.4 Pedestrians Y/N

5          New Proposed requirements (if any)


1. Y/N
2. Y/N
3. Y/N



6          Detailed description of submission

6.1        Proposal section #1

6.2        Proposal section #2


7          Conclusions


8          References

  1. MPAI Statutes
  2. MPAI Patent Policy
  3. MPAI Technical Specifications
  4. MPAI Patent Policy
  5. MPAI; Call for Technologies: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC); N1763
  6. MPAI; Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC); N1764
  7. MPAI; Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Technologies CAV-TEC); N1765