Contents
2 Scope of the Connected Autonomous Vehicle – Architecture CfT. 2
4 Evaluation Criteria and Procedure. 4
5 Expected development timeline. 4
Annex C: Check list of data formats proposed by a respondent 10
Annex D: Technologies that may require specific testing. 11
Annex E: Mandatory text in responses. 12
1 Introduction
Moving Picture, Audio and Data Coding by Artificial Intelligence (MPAI) is an international non-profit organisation with the mission of developing standards for Artificial Intelligence (AI)-enabled data coding and for technologies that facilitate integration of data coding components into ICT systems [1]. The MPAI Statutes also assign to MPAI the task to facilitate the creation of patent pools that rely on clear IPR licensing frameworks based on Framework Licences [2].
MPAI has developed several Technical Specifications relevant to its mission: execution environment of multi-component AI applications, context-based audio enhancements, multimodal human-machine conversation, company performance prediction, neural network watermarking, and governance of the MPAI ecosystem. Four Technical Specifications have been adopted by IEEE without modification and one more is in the pipeline.
MPAI is engaged in several other projects on AI health, connected autonomous vehicles, MPAI metaverse model, and XR Venues. When the functional requirements of a project are consolidated, MPAI principal members adopt a “Framework Licence” that sets some important elements of the future licence for the standard essential patents. Then MPAI issues a Call for Technologies, a document inviting the submission of contributions in response to the Call for Technologies by parties who accept to licence their technologies according to the Framework Licence, if their technologies are accepted to be part of the target Technical Specification.
This document is a Call for Technologies (CfT) for the Connected Autonomous Vehicle (MPAI-CAV) – Architecture Technical Specification. Three documents are attached to this Call for Technologies:
- Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Architecture – [3].
- Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [4].
- Template of Responses: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [5]
Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture is the first of a series of Technical Specifications that MPAI intends to develop to promote and support the Autonomous Vehicle industry.
2 Scope of the Connected Autonomous Vehicle – Architecture CfT
This Call for Technologies: Connected Autonomous Vehicle (MPAI-CAV) – Architecture invites any party wishing to contribute to the development of the planned Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture to submit a response. They may do so irrespective of their ownership of technologies that satisfy Functional Requirements of Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [3]. If they own such technologies, they are required to eventually license their technologies according to Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [4] if the technologies are selected by MPAI for possible modification and inclusion in the planned Technical Specification: Connected Autonomous Vehicle – Architecture (MPAI-CAV).
Any respondent who is not an MPAI member and wishes to participate in the development of the said Technical Specification shall join MPAI. If they own accepted technologies and do not join MPAI, they lose the opportunity to have their technologies included in the planned Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture.
MPAI is not aware of any essential IP in Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [3].
The planned Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture will be developed using technologies that comply with the following mandatory requirements:
- Be part of responses to this Call submitted by parties accepting Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [4] and satisfy Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [3].
- Be based on technologies specified in published MPAI standards, where relevant, desirable, and feasible [1].
Therefore, the goal of this Call is to elicit responses in line with the Use Cases and Functional Requirements of [3].
Respondents are welcome to additionally do one or more of the following:
- Make comments on any technical element of [3].
- Make motivated proposals of changes or proposal of technologies not included in [3] if they:
- Are in line with the scope of Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Architecture [3].
- Satisfy the Framework Licence [4].
At this stage, MPAI membership is not a prerequisite for responding to this Call for Technologies. However, proponents should be aware that, if their proposal or part thereof is accepted for inclusion in the planned Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture, they will be requested to immediately join MPAI, or lose the opportunity to have their accepted technologies included in the standard.
MPAI will select the most suitable technologies based on their technical merits. However, MPAI in not obligated, by virtue of this Call, to select a particular technology or to select any of the proposed technologies if those submitted are found inadequate.
Note that in the future, MPAI may decide to further extend the planned Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture as a part or an extension of it.
3 How to submit a response
Those planning to respond to this Call are:
- Advised that the Call for Technologies: Connected Autonomous Vehicle (MPAI-CAV) – Architecture will be presented at two online events on 2023/07/26.
- Requested to communicate their intention to respond to this Call with an initial version of the form of Annex A to the MPAI secretariat (secretariat@mpai.community) by 2023/07/31. Submission of a duly filled out Annex A helps MPAI to properly plan for the revision of submissions. This, however, is not a requirements and the submission of a respondent to this Call who did not the submit Annex A will still be accepted.
- Encouraged to regularly visit the Call for Technologies webpage where relevant additional information will be posted.
- Required to deliver their submissions to the MPAI secretariat (secretariat@mpai.community) by 2023/07/10 T23:59 UTC. The secretariat will acknowledge receipt of the submission via email.
- Required to attend the review of submissions according to the schedule that the 35th MPAI General Assembly (MPAI-35) will define at its online meeting on 2023/07/12. For details on how non MPAI members who have made a submission can attend the said review sessions should contact the MPAI secretariat (secretariat@mpai.community).
Responses to this Call for Technologies: MPAI Metaverse Model Architecture may/shall include:
Table 1 – Optional and mandatory elements of a response
| Item | Status |
| Detailed documentation describing the proposed technologies | mandatory |
| The final version of Annex A. | mandatory |
| The text of Annex B duly filled out with the table indicating to which Functional Requirements the response applies. | mandatory |
| Comments on the completeness and appropriateness of the MPAI-CAV – Architecture Functional Requirements and any motivated suggestion to amend and/or extend those Requirements. | optional |
| A preliminary demonstration, with a detailed document describing it. | optional |
| Any other additional relevant information that may help evaluate the submission, such as additional use cases. | optional |
| The text of Annex E. | mandatory |
Respondents are invited to take advantage of the check list of Annex C before filling out Annex A and submitting their response.
Respondents are mandatorily requested to present their submission at a teleconference meeting to be properly announced to submitters by the MPAI Secretariat. If no presenter of a submission will be in attendance to that meeting, the submission will be discarded.
Further information on MPAI can be obtained from the MPAI website.
4 Evaluation Criteria and Procedure
Proposals will be assessed using the following process:
- Evaluation panel is created from:
- MPAI members in attendance.
- Non-MPAI members who are respondents.
- Non respondents/non MPAI member experts invited in a consulting capacity.
- No one from 1.1.-1.2. is denied membership in the Evaluation panel.
- Respondents present their proposals.
- Evaluation Panel members ask questions.
- If required, subjective and/or objective tests are carried out with the following process:
- The required tests are defined.
- The required tests are carried out.
- A report is produced.
- If required, at least 2 reviewers are appointed to review and report about specific points in a proposal.
- Evaluation panel members fill out Annex B for each proposal.
- Respondents respond to evaluations.
- Proposal evaluation report is produced.
5 Expected development timeline
Timeline of the CfT, deadlines and response evaluation:
Table 2 – Dates and deadlines
| Step | Date | Time |
| Call for Technologies: MPAI-CAV – Architecture | 2023/07/12 | 17:00 UTC |
| Online presentations of Call for Technologies: MPAI-CAV – Architecture | 2023/07/26 | 08:00 UTC
15:00 UTC |
| Notification of intention to submit proposal | 2023/07/31 | 23.59 UTC |
| Submission deadline | 2023/08/15 | 23.59 UTC |
| Evaluation of responses starts | 2023/08/16 | |
| Publication of draft Technical Specification: MPAI-CAV – Architecture for Community Comments. | 2023/08/23 | |
| Adoption and publication of Technical Specification: MPAI-CAV – Architecture | 2023/09/29 | |
Evaluation will be carried out at online sessions of the Requirements (CAV) group according to the published calendar.
6 References
- MPAI Standards Resources; https://mpai.community/standards/resources/.
- MPAI Patent Policy; https://mpai.community/about/the-mpai-patent-policy/.
- MPAI; Use Cases and Functional Requirements: Connected Autonomous Vehicle (MPAI-CAV) – Architecture; N1303; https://mpai.community/standards/mpai-cav/mpai-metaverse-model/#Architecture
- MPAI; Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Architecture; N1304; https://mpai.community/standards/mpai-cav/framework-licence-mpai-metaverse-model-mpai-cav-architecture/
- MPAI; Template for Responses: Connected Autonomous Vehicle (MPAI-CAV) – Architecture; N1305; https://mpai.community/standards/mpai-cav/template-for-responses-mpai-cav-call-for-technologies/
Annex A: Information Form
This information form is to be filled in by a Respondent to this Call for Technologies: MPAI-CAV – Architecture.
- 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?
Annex B: 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 CfT (Requirements):
Comments on possible MPAI-CAV – Architecture profiles[1]
Evaluation table:
Table 3 – Assessment of submission features
| Note 1 | Table 4 gives the semantics of submission features. |
| Note 2 | Evaluation Elements indicate the elements used by the evaluator 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 | ||
| Test cases | ||
| Maturity of reference implementation | ||
| Relative complexity |
Content of the criteria table cells:
Evaluation facts should mention:
- Not supported / partially supported / fully supported.
- What supports these facts: submission/presentation/demo.
- The summary of the facts themselves, e.g., very good in one way, but weak in another.
Final assessment should mention:
- Possibilities to improve or add to the proposal, e.g., any missing or weak features.
- How sure the evaluators are, i.e., evidence shown, very likely, very hard to tell, etc.
- Global evaluation (Not Applicable/ –/ – / + / ++)
New Use Cases/Requirements Identified:
(Please describe)
Evaluation summary:
- Main strong points, qualitatively:
- Main weak points, qualitatively:
- Overall evaluation: (0/1/2/3/4/5)
0: could not be evaluated
1: proposal is not relevant.
2: proposal is relevant but requires significant more work.
3: proposal is relevant, but with a few changes.
4: proposal has some very good points, so it is a good candidate for standard.
5: proposal is superior in its category, very strongly recommended for inclusion in standard.
Additional remarks: (points of importance not covered above.)
The submission features in Table 3 are explained in the following Table 4.
Table 4 – Explanation of submission features
| Submission features | Criteria |
| Completeness of description | Evaluators should:
1. Compare the list of requirements (Annex C of the CfT) 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 the merit of what is proposed. A submission on a single technology that is excellent may be considered instead of a submission that is complete but has 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.
Note: 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. |
| Test cases | Evaluators should report whether a proposal contains suggestions for testing the technologies proposed. |
| Relative complexity | Evaluators should identify issues that would make it difficult to implement the proposal compared to the state of the art. |
Annex C: Check list of data formats proposed by a respondent
Table 5 is a suggested check list to inform MPAI about the data formats contained in a response.
Table 5 – Data formats in Use Cases and Functional Requirements: MPAI-CAV – Architecture [3]
Note: The numbers in the first column refer to the section numbers of [3].
Table 6 – Table of response areas
| # | MPAI-CAV Architecture elements | Response |
| 1 | Introduction | Y/N |
| 2 | Terms and definitions | Y/N |
| 3 | References | Y/N |
| 4 | Human-CAV Interaction (HCI) | Y/N |
| 4.1 | Subsystem description | Y/N |
| 4.2 | Reference architecture | Y/N |
| 4.3 | I/O Data of the HCI Subsystem | Y/N |
| 4.4 | AI Module functionalities | Y/N |
| 4.5 | Input/Output Data of the AIMs | Y/N |
| 5 | Environment Sensing Subsystem (ESS) | Y/N |
| 5.1 | Subsystem description | Y/N |
| 5.2 | Reference architecture | Y/N |
| 5.3 | Input and output data | Y/N |
| 5.4 | AI Module functionalities | Y/N |
| 5.5 | Input/Output Data of the AIMs | Y/N |
| 6 | Autonomous Motion Subsystem (AMS) | Y/N |
| 6.1 | Subsystem description | Y/N |
| 6.2 | Reference architecture | Y/N |
| 6.3 | Input and output data | Y/N |
| 6.4 | AI Module functionalities | Y/N |
| 6.5 | Input/Output Data of the AIMs | Y/N |
| 7 | Motion Actuation Subsystem (MAS) | Y/N |
| 7.1 | Subsystem description | Y/N |
| 7.2 | Reference architecture | Y/N |
| 7.3 | Input and output data | Y/N |
| 7.4 | AI Module functionalities | Y/N |
| 7.5 | Input/Output Data of the AIMs | Y/N |
| 8 | CAV-to-Everything (V2X) | Y/N |
| 8.1 | Description | Y/N |
| 8.2 | Input and output data | Y/N |
| 8.2.1 | CAVs within range | Y/N |
| 8.2.2 | CAV-aware equipment | Y/N |
| 8.2.3 | Other non-CAV vehicles | Y/N |
| 8.2.4 | Pedestrians | Y/N |
Respondent should in any case review the equivalent list in the table of contents of [3].
Annex D: Technologies that may require specific testing
Table 7 will be compiled based on the responses received.
Table 7 – Functional Requirements that may require specific testing
| Section | Technology | Nature of Test |
Annex E: Mandatory text in responses
A response to this MPAI-CAV – Architecture Call for Technologies shall mandatorily include the following text
<Company/Member> submits this technical document in response to Call for Technologies: MPAI Metaverse Model (MPAI-CAV) – Architecture V1 (N1304).
<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 Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Architecture (N1306), alone or jointly with other IPR holders after the approval of the planned Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture by the General Assembly and in no event after commercial implementations of the Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture become available on the market.
In case the respondent is a non-MPAI member, the submission shall mandatorily also 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 contribution shall mandatorily include the following text:
<Member> submits this document to MPAI as a contribution to the development of the planned the Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture.
<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 Framework Licence: Connected Autonomous Vehicle (MPAI-CAV) – Architecture (N1304), alone or jointly with other IPR holders after the approval of the Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture by the General Assembly and in no event after commercial implementations of the Technical Specification: Connected Autonomous Vehicle (MPAI-CAV) – Architecture 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 relevan for the subset.
