This standard adopts MPAI AI Framework (MPAI-AIF) Technical Specification Version 1.1 as an IEEE Standard. The MPAI-AIF Technical Specification specifies architecture, interfaces, protocols, and Application Programming Interfaces (API) of an AI Framework (AIF), especially designed for the execution of AI-based implementation, but also suitable for mixed AI and traditional data processing workflow.
- Sponsor Committee
- BOG/CAG - Entity Collaborative Activities Governance Board
- Status
- Active Standard
- PAR Approval
- 2022-11-10
- Board Approval
- 2022-12-03
- History
-
- Published:
- 2023-04-28
Working Group Details
- Society
- IEEE SA Board of Governors
- Sponsor Committee
- BOG/CAG - Entity Collaborative Activities Governance Board
- Working Group
-
AIFWG - Artificial Intelligence Framework Working Group
- IEEE Program Manager
- Jonathan Goldberg
Contact Jonathan Goldberg - Working Group Chair
- Stephen Dukes
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
P3301
IEEE Draft Standard for Adoption of Moving Picture, Audio and Data Coding by Artificial Intelligence (MPAI) Technical Specification Artificial Intelligence Framework (AIF) Version 2
The MPAI AI Framework (MPAI-AIF) Technical Specification (in the following also called MPAI-AIF V2) specifies the architecture, interfaces, protocols, and Application Programming Interfaces (API) of an AI Framework specially designed for execution of AI-based implementations, but also suitable for mixed AI and traditional data processing workflows. Basic functionalities: 1. Independent of the Operating System. 2. Component-based modular architecture with specified interfaces. 3. Interfaces encapsulate Components to abstract them from the development environment. 4. Interface with the Store enabling access to validated Components. 5. Component can be Implemented as: 5.1. Software only, from MCUs to HPC. 5.2. Hardware only. 5.3. Hybrid hardware-software. 6. Component system features are: 6.1. Execution in local and distributed Zero-Trust architectures [28]. 6.2. Possibility to interact with other Implementations operating in proximity. 6.3. Direct support to Machine Learning functionalities. 7. The AIF can download an AIW whose identifier has been specified by the User Agent or by a configuration parameter. Secure functionalities: 1. The AIF provides access to the following Trusted Services: 1.1. A selected range of ciphering algorithms. 1.2. A basic attestation function. 1.3. Secure storage (RAM, internal/external flash, or internal/external/remote disk). 1.4. Certificate-based secure communication. 2. The AIF can execute only one AIW containing only one AIM. The AIM has the following features: 2.1. The AIM may be a Composite AIM. 2.2. The AIMs of the Composite AIM cannot access the Secure API. 3. The AIF Trusted Services may rely on hardware and OS security features already existing in the hardware and software of the environment in which the AIF is implemented.
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
No Active Standards
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
No Superseded Standards
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards