Contents
Annex 3 – Data Types and Data Formats proposed by a respondent
Annex 4: Technologies that may require specific testing
Annex 4 – Mandatory text in responses
1 Introduction
In September 2023, Moving Picture, Audio, and Data Coding by Artificial Intelligence (MPAI) has published Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) Architecture (CAV-ARC) V1.0.
This document concerns Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Technologies (CAV-TEC) V1.0, a new specification that MPAI is planning to develop. In accordance with the process established by the MPAI Statutes [2] and the MPAI Patent Policy [3], with this document MPAI requests parties having rights to technologies satisfying the CAV-TEC Use Cases and Functional Requirements [7] and CAV-TEC Framework Licence [8] to respond to this Call for Technologies preferably using the CAV-TEC Template for Responses [9].
MPAI [1] is an international unaffiliated non-profit organisation having the mission to develop standards for Artificial Intelligence-enabled data coding and technologies facilitating integration of data coding components into Information and Communication Technology (ICT) systems.
2 Scope and purpose
The CAV-ARC Technical Specification [6] specifies the Architecture of a Connected Autonomous Vehicle (CAV) based on Subsystems and Components having standard functions and interfaces. However, the scope of CAV-ARC was confined to the identification of connections between Subsystems and Components, so it did not address the Functional Requirements of the Data flowing through such connections.
With MPAI-TEC, MPAI intends to extend the scope of MPAI-CAV standardisation by developing a specification of JSON Syntax and Semantics of such CAV-ARC Data flowing through the CAV-ARC-specified connections. The specification will reference a future Technical Specification: Data Types, Formats, and Attributes (MPAI-TFA) that will specify the Data Formats used by Data Types that are referenced or intended to be referenced by MPAI Technical Specifications.
MPAI is issuing a parallel Call for Technologies: MPAI Metaverse Model (MPAI-MMM) – Technologies (MMM-TEC) that will similarly specify the JSON Syntax and Semantics of MMM-TEC Data Types and will reference the same future MPAI-TFA Technical Specification. It should also be noted that other MPAI Technical Specifications such as MPAI-CAE [10], MPAI-CUI [11], MPAI-HMC [12], MPAI-MMC [13], MPAI-MMM [14], MPAI-OSD [15], and MPAI-PAF [16] adopt a similar approach to the specification of their Data Types.
With this Call for Technologies MPAI is requesting comments on and proposals for:
- Amendment, extension, or replacement of Functional Requirements, Syntax, and Semantics of MPAI-CAV Items and Basic Data as specified in [7].
- Initial specification of Data Types, Formats, and Data Types (MPAI-TFA).
MPAI intends to use the material in [7] and the responses to this Call for Technologies to publish Technical Specification: MPAI-Connected Autonomous Vehicle (MPAI-CAV) – Technologies (CAV-TEC) V1.0.
3 How to respond
Those planning to respond to this Call are:
- Invited to attend the presentation of the Call to be held on 2024/06/06 at 16 UTC.
- Requested to communicate their intention to respond to this CfT with an initial version of the form of Annex 1 to the MPAI secretariat (secretariat@mpai.community) by 2024/06/07. Submission of Annex 1 helps MPAI to properly plan for the review of submissions. However, respondents to this Call who have not sent Annex 1 by the deadline will still be eligible to make a response to this Call.
- Encouraged to regularly visit the MPAI-CAV webpage where information related to this Call will be posted.
Table 1 – Dates and deadlines
| Step | Date | Time |
| Call for Technologies | 2024/05/15 | 17:00 UTC |
| Online presentation of the Call | 2024/06/06 | 16:00 UTC |
| Notification of intention to submit a proposal (Annex 1) | 2024/06/13 | 23.59 UTC |
| Submission deadline | 2024/07/05 | 23.59 UTC |
| Start of response evaluation | 2024/07/10 | (MPAI-45) |
Evaluation to be carried out at online sessions according to the calendar agreed at MPAI-44.
Responses to this CAV-TEC Call for Technologies shall/may include:
Table 2 – Optional and mandatory elements of a response
| Item | Status |
| Detailed documentation describing the proposal | mandatory |
| The completed version of Annex 1. | mandatory |
| The text of Annex 2 duly filled out with the table indicating which Data Types are addressed by the response. | mandatory |
| The text of Annex 5. | mandatory |
| Any other additional relevant information that may help evaluate the submission. | optional |
Respondents are invited to take advantage of the check list of Annex 3 before filling out Annex 1 and submitting their response.
Respondents are advised that, upon technical acceptance by MPAI of their submission in whole or in part for further evaluation and addition to the planned CAV-TEC, MPAI will require that a non-MPAI member immediately join MPAI. If the non-MPAI member elects not to do so, their submission will be discarded. Direction on how to join MPAI can be found online.
Further information on MPAI can be obtained from the MPAI website.
4 References
- MPAI; Moving Picture, Audio, and Data Coding by Artificial Intelligence (MPAI)
- MPAI; MPAI Standards.
- MPAI; MPAI Patent Policy.
- MPAI; Technical Specification: Governance of the MPAI Ecosystem (MPAI-GME)1.
- MPAI; Technical Specification: AI Framework (MPAI-AIF)1.
- MPAI; Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture (CAV-ARC) V1.1.
- MPAI; Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Technologies (CAV-TEC).
- MPAI; Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Technologies (CAV-TEC).
- MPAI; Template for Responses: Connected Autonomous Vehicle (MPAI-CAV) – Technologies (CAV-TEC).
- MPAI; Technical Specification: Context-based Audio Enhancement (MPAI-CAE) V2.2.
- MPAI; Technical Specification: Compression and Understanding of Industrial Data (MPAI-CUI) V1.1.
- MPAI; Human and Machine Communication (MPAI-HMC) V1.0.
- MPAI; Technical Specification: Multimodal Conversation (MPAI-MMC) V2.2.
- MPAI; Technical Specification: MPAI Metaverse Model (MPAI-MMM) – Architecture (MPAI-MMM) V1.2
- MPAI; Technical Specification: Object and Scene Description (MPAI-OSD) V1.1.
- MPAI; Technical Specification: Portable Avatar Format (MPAI-PAF) V1.2.
- MPAI; Call for Technologies: MPAI Metaverse Model (MPAI-MMM) – Technologies.
Annex 1 Information Form
This information form is to be filled in by a Respondent to this CAV-TEC Call for Technologies.
- Title of the proposal.
- Organisation: company name, position, e-mail of contact person.
- What are the main functionalities of your proposal?
- Does your proposal provide or describe a formal specification and APIs?
- Will you provide a demonstration to show how your proposal meets the evaluation criteria?
Annex 2 Evaluation Sheet
NB: This evaluation sheet will be filled out by Evaluation Team members.
Proposal title:
Main functionalities:
Response summary: (a few lines)
Comments on relevance to the Call:
Comments on possible CAV-TEC profiles[1]
Evaluation table:
Table 3 – Assessment of submission features
| Note 1 | The semantics of submission features is provided by Table 4 – Explanation of submission featuresTable 4. |
| Note 2 | Evaluation Elements indicate aspects used by evaluators in assessing the submission. |
| Note 3 | Final Assessment indicates the ultimate assessment based on the Evaluation Elements. |
| Submission features | Evaluation Elements | Final Assessment |
| Completeness of description | ||
| Understandability | ||
| Extensibility | ||
| Use of standard technology | ||
| Efficiency | ||
| Maturity of reference implementation | ||
| Relative complexity | ||
| Support of Functional Requirements | ||
| Support of new Functional Requirements |
Table 4 – Explanation of submission features
| Submission
features |
Criteria |
| Completeness of description | Evaluators should:
1. Compare the list of requirements (Annex 3) with the submission. 2. Check if respondents have described in sufficient detail how the requirements are supported by the proposal. Note: Submissions will be judged for their intrinsic merit. An excellent submission of a single technology may be considered instead of a complete submission with a less performing technology. |
| Understandability | Evaluators should identify items that are demonstrably unclear (inconsistencies, sentences with dubious meaning etc.) |
| Extensibility | Evaluators should check if respondent has proposed extensions to the Use Cases (Extensibility is the capability of the proposed solution to support use cases that are not supported by current requirements). |
| Use of standard Technology | Evaluators should check if new technologies are proposed where widely adopted technologies exist. If this is the case, the merit of the new technology shall be proved. |
| Efficiency | Evaluators should assess power consumption, computational speed, computational complexity. |
| Maturity of reference implementation | Evaluators should assess the maturity of the proposal.
Note1: measured by how well the HW/SW implementation of the submission disclosed. Note2: the implementation parts that are not disclosed but demonstrated will be considered if and only if such components can be replicated. |
| Relative complexity | Evaluators should identify issues that would make it difficult to implement the proposal compared to the state of the art. |
| Support of existing Functional Requirements | Evaluators should check how well the technologies proposed can support already identified Functional Requirements. |
| Support of new Functional Requirements | Evaluators should check the relevance of the proposed new functional requirements. |
Annex 3 Data Types and Data Formats proposed by a respondent
Table 5 is a suggested check list to inform MPAI about the Data Types and Data Formats contained in a response. The “Section” column of Table 5 refers to the Data Types of [7]
Table 5 – List of Data Types, Formats, and Attributes
| Section | Types | Formats | Attributes |
| 5 | Human-CAV Interaction (HCI) | ||
| 5.5.1 | Personal Preferences | ||
| 5.5.2 | Personal Profile | ||
| 5.5.3 | Input Text | ||
| 5.5.4 | Point of View | ||
| 5.5.5 | Audio Object | ||
| 5.5.6 | Visual Object | ||
| 5.5.7 | Audio-Visual Object | ||
| 5.5.8 | Audio-Visual Basic Scene Descriptors | ||
| 5.5.9 | Audio-Visual Scene Descriptors | ||
| 5.5.10 | Audio Scene Descriptors | ||
| 5.5.11 | Visual Scene Descriptors | ||
| 5.5.12 | Body Descriptors | ||
| 5.5.13 | Face Descriptors | ||
| 5.5.14 | Face ID | ||
| 5.5.15 | Speaker ID | ||
| 5.5.16 | Audio Object ID | ||
| 5.5.17 | Visual Object ID | ||
| 5.5.18 | Meaning | ||
| 5.5.19 | Personal Status | ||
| 5.5.20 | Avatar Model | ||
| 5.5.21 | Speech Model | ||
| 5.5.22 | Output Audio | ||
| 5.5.23 | Output Visual | ||
| 5.5.24 | HCI-AMS Messages | ||
| 5.5.25 | Semantics | ||
| 5.5.26 | Ego-Remote HCI Messages | ||
| 5.5.27 | Functional Requirements | ||
| 5.5.28 | Syntax | ||
| 5.5.29 | Semantics | ||
| 6 | Environment Sensing Subsystem (ESS) | ||
| 6.6.1 | Input Audio | ||
| 6.6.2 | Input Visual | ||
| 6.6.3 | RADAR Data | ||
| 6.6.4 | Input LiDAR | ||
| 6.6.5 | Ultrasound Data | ||
| 6.6.6 | GNSS Data | ||
| 6.6.7 | Offline Map Data | ||
| 6.6.8 | Audio-Visual Scene Descriptors | ||
| 6.6.9 | Traffic Signal Configuration | ||
| 6.6.10 | Basic Environment Representation | ||
| 7 | Autonomous Motion Subsystem (AMS) | ||
| 7.6.1 | CAV Identifier | ||
| 7.6.2 | Basic Environment Representation | ||
| 7.6.3 | Full Environment Representation | ||
| 7.6.4 | E-AMS to/from R-AMS messages | ||
| 7.6.5 | Offline map | ||
| 7.6.6 | Route | ||
| 7.6.7 | Path | ||
| 7.6.8 | Pose | ||
| 7.6.9 | Trajectory | ||
| 7.6.10 | Goal | ||
| 7.6.11 | AMS-HCI Message | ||
| 7.6.12 | AMS-MAS Message | ||
| 7.6.13 | MAS-AMS Message | ||
| 7.6.14 | Road State | ||
| 8 | Motion Actuation Subsystem (MAS) | ||
| 8.6.1 | Odometer Data | ||
| 8.6.2 | Speedometer Data | ||
| 8.6.3 | Accelerometer Data | ||
| 8.6.4 | Spatial Attitude | ||
| 8.6.5 | Other Environment Data | ||
| 8.6.6 | AMS-MAS Message | ||
| 8.6.7 | MAS-AMS Message | ||
| 8.6.8 | Brakes Command | ||
| 8.6.9 | Brakes Response | ||
| 8.6.10 | Steering Wheel Command | ||
| 8.6.11 | Steering Wheel Response | ||
| 8.6.12 | Wheel Motor Command | ||
| 8.6.13 | Wheel Motor Response |
Annex 4: Technologies that may require specific testing
Table 6 will be compiled based on the responses received.
Table 6 – Data Types/Data Formats that may require specific testing
| Section | Technology | Nature of Test |
Annex 5 Mandatory text in responses
A response to this CAV-TEC Call for Technologies shall mandatorily include the following text:
<Company/Member> submits this technical document in response to MPAI Call for Technologies for Connected Autonomous Vehicle (MPAI-CAV) – Technologies (CAV-TEC) (N1768).
<Company/Member> explicitly agrees to the steps of the MPAI standards development process defined in Annex 1 to the MPAI Statutes (N421), in particular <Company/Member> declares that <Company/Member> or its successors will make available the terms of the Licence related to its Essential Patents according to the CAV-TEC Framework Licence (N1769), alone or jointly with other IPR holders after the approval of the CAV-TEC Technical Specification by the General Assembly and in no event after commercial implementations of the CAV-TEC Technical Specification become available on the market.
In case the respondent is a non-MPAI member, the submission shall mandatorily include the following text:
If (a part of) this submission is identified for inclusion in a specification, <Company> understands that <Company> will be requested to immediately join MPAI and that, if <Company> elects not to join MPAI, this submission will be discarded.
Subsequent technical contributions shall mandatorily include the following text:
<Member> submits this document to MPAI as a contribution to the development of the planned MPAI-CAV-TEC Technical Specification.
<Member> explicitly agrees to the steps of the MPAI standards development process defined in Annex 1 to the MPAI Statutes (N421), in particular <Company> declares that <Company> or its successors will make available the terms of the Licence related to its Essential Patents according to the CAV-TEC Framework Licence (N1770), alone or jointly with other IPR holders after the approval of the CAV-TEC Technical Specification by the General Assembly and in no event after commercial implementations of the CAV-TEC Technical Specification become available on the market.
[1] Profile of a standard is a particular subset of the technologies that are used in a standard and, where applicable, the classes, subsets, options and parameters relevant for the subset.
