AID.02 Automotive Identity Technical Specification - Version 2.1 - Security and API Procedures

Sep 2, 2026

Upload by Ezra

AID.02 Automotive Identity Technical Specification defines the security classification, copyright and usage restrictions for controlled distribution within the GSMA ecosystem. It provides an industry-specification framework covering scope, actors, and framework architecture, then details onboarding, provisioning, profile management, and withdrawal procedures across CMP and MSP touchpoints. The document specifies general API requirements and functional interfaces (AID1/AID2), including data elements, HTTP headers, identifiers, and error codes to support activation, token handling, and profile status synchronization.

LanguageEnglish

CategoryPresentations

FormatDOCX

Pages131

Reading Time46 min

AccessFree to download

Introduction

Scope

Abbreviations

Definitions

References

Conventions

Actors

Framework Architecture

Architecture Overview

Interfaces

Procedures

Onboarding via CMP Touchpoint (e.g. app)

Onboarding via MSP Touchpoint

Car Provisioning

Profile Swap

Withdraw Onboarding

Withdraw Onboarding via CMP Touchpoint

Withdraw Onboarding via MSP Touchpoint

Delete Operational Profile

Profile Status Synchronization

Send Profile Information

Update Subscription Info

Enable and Disable Profile

Request CSIM Info

Delete all profiles

Data Elements

Data Elements for AID1 Interface

HTTP Headers

Account ID

MSP Token

ICCID

Error Codes

Data Elements for AID2 Interface

RequestID

CmpUserId

General API Requirements

Functions

Functions for AiD1 Interface

Redirect to MSP Content

Redirect to CMP content

Redirect back to MSP content

Send MSP Token

Notify MSP Token Invalid

Send Profile Information

Update Subscription Info

Request Activation Code

Send CSIM Status

Request Invalidate MSP Token

Request Profile Status

Functions for AiD2 Interface

AID.02 Automotive Identity Technical Specification Version 2.1 26 January 2024 Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © DATE \@ "YYYY" \* MERGEFORMAT 20222026 GSM Association Disclaimer The GSMA makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Compliance Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. This Permanent Reference Document is classified by GSMA as an Industry Specification, as such it has been developed and is maintained by GSMA in accordance with the provisions set out in GSMA AA.35 – Procedures for Industry Specifications. . Table of Contents TOC \o "1-3" \h \z \u HYPERLINK \l "_Toc157432962" 1 Introduction PAGEREF _Toc157432962 \h 4 HYPERLINK \l "_Toc157432963" 1.1 Scope PAGEREF _Toc157432963 \h 4 HYPERLINK \l "_Toc157432964" 1.2 Abbreviations PAGEREF _Toc157432964 \h 5 HYPERLINK \l "_Toc157432965" 1.3 Defintions PAGEREF _Toc157432965 \h 5 HYPERLINK \l "_Toc157432966" 1.4 References PAGEREF _Toc157432966 \h 6 HYPERLINK \l "_Toc157432967" 1.5 Conventions PAGEREF _Toc157432967 \h 6 HYPERLINK \l "_Toc157432968" 2 Actors PAGEREF _Toc157432968 \h 6 HYPERLINK \l "_Toc157432969" 3 Framework Architecture PAGEREF _Toc157432969 \h 8 HYPERLINK \l "_Toc157432970" 3.1 Architecture Overview PAGEREF _Toc157432970 \h 8 HYPERLINK \l "_Toc157432971" 3.2 Interfaces PAGEREF _Toc157432971 \h 8 HYPERLINK \l "_Toc157432972" 4 Procedures PAGEREF _Toc157432972 \h 9 HYPERLINK \l "_Toc157432973" 4.1 Onboarding via CMP Touchpoint (e.g. app) PAGEREF _Toc157432973 \h 9 HYPERLINK \l "_Toc157432974" 4.2 Onboarding via MSP Touchpoint PAGEREF _Toc157432974 \h 11 HYPERLINK \l "_Toc157432975" 4.3 Car Provisioning PAGEREF _Toc157432975 \h 14 HYPERLINK \l "_Toc157432976" 4.3.1 Profile Swap PAGEREF _Toc157432976 \h 16 HYPERLINK \l "_Toc157432977" 4.4 Withdraw Onboarding PAGEREF _Toc157432977 \h 20 HYPERLINK \l "_Toc157432978" 4.4.1 Withdraw Onboarding via CMP Touchpoint PAGEREF _Toc157432978 \h 20 HYPERLINK \l "_Toc157432979" 4.4.2 Withdraw Onboarding via MSP Touchpoint PAGEREF _Toc157432979 \h 22 HYPERLINK \l "_Toc157432980" 4.5 Delete Operational Profile PAGEREF _Toc157432980 \h 24 HYPERLINK \l "_Toc157432981" 4.6 Profile Status Synchronization PAGEREF _Toc157432981 \h 26 HYPERLINK \l "_Toc157432982" 4.7 Send Profile Information PAGEREF _Toc157432982 \h 27 HYPERLINK \l "_Toc157432983" 4.8 Update Subscription Info PAGEREF _Toc157432983 \h 28 HYPERLINK \l "_Toc157432984" 4.9 Enable and Disable Profile PAGEREF _Toc157432984 \h 29 HYPERLINK \l "_Toc157432985" 4.1 Request CSIM Info PAGEREF _Toc157432985 \h 31 HYPERLINK \l "_Toc157432986" 4.2 Delete all profiles PAGEREF _Toc157432986 \h 32 HYPERLINK \l "_Toc157432987" 5 Data Elements PAGEREF _Toc157432987 \h 33 HYPERLINK \l "_Toc157432988" 5.1 Data Elements for AID1 Interface PAGEREF _Toc157432988 \h 33 HYPERLINK \l "_Toc157432989" 5.1.1 HTTP Headers PAGEREF _Toc157432989 \h 34 HYPERLINK \l "_Toc157432990"

FAQs

What security, copyright, and distribution restrictions apply to this specification?

The document states a non-confidential security classification and restricts access and distribution to permitted persons. It also includes copyright protection and requires prior written approval for disclosure beyond the permitted scope.

How does the document structure onboarding procedures across CMP and MSP touchpoints?

Onboarding is described through separate procedures for CMP touchpoint (e.g., app) and MSP touchpoint. Additional steps cover car provisioning, profile swap, and withdrawal workflows for each touchpoint.

Which interfaces and functions does the specification define for integrating systems?

It defines general API requirements and functions for AiD1 and AiD2 interfaces. The described functions include redirects, MSP token exchange and validation, sending profile information, updating subscription info, requesting activation codes, and managing profile/status synchronization.

Sep 2, 2026

Upload by Ezra