Building theWeb3 Economy

MAY 2024

VEHICLE IDENTITY II

REFERENCE IMPLEMENTATION ARCHITECTURE

Use Cases
Vehicle Registration and MaintenanceVersion 2.0: MOBI VID0004/RI/2024
Version 1.0: MOBI VID0004/RI/2021

INTRODUCTION
This standard was issued by MOBI and its members. MOBI is a nonprofit
alliance of many of the world’s largest vehicle manufacturers, startups,
governments/transit agencies, NGOs, financial institutions, e-mobility
providers, consultancies, suppliers, logistics providers, and more working tocreate standards and build the Web3 digital infrastructure for connectedecosystems and IoT commerce.
MOBI is creating standards for trusted self-sovereign data and identities(e.g. vehicles, people, businesses, things), verifiable credentials, and crossindustry interoperability, with the goal of making transportation more
efficient, equitable, decentralized, and sustainable, all while preserving thedata privacy of users and providers alike. MOBI is technology and ledger
agnostic. The work of preparing standards is carried out through MOBI
Working Groups. Each member of the consortium interested in a subject for
which a working group has been established has the right to be represented
and participate in that working group.
The procedures used to develop this document and those intended for its
further maintenance are described in the working group charter. In
particular, the different approval criteria needed for the different types of
MOBI documents should be noted. Approvals of MOBI Steering Committee
and Board of Directors are obtained upon the final document release.
Attention is drawn to the possibility that some of the elements of thisdocument may be the subject of intellectual property rights. In accordancewith MOBI IPLR policy, a 60-day review period is provided to the MOBI
community to disclose any and all IP matters pertaining to this standard.
MOBI shall not be held responsible for identifying any or all such rights.
Details of any IP rights identified during the development of the document
will be in the Introduction upon public release of this standard.
Any trade name used in this document is provided for the convenience ofusers and does not constitute an endorsement. The Working Group
responsible for this document is the Vehicle Identity II (VID II) Working Group.
Sincere thanks and appreciation are extended to those who contributed theirunique insights to the VID II Reference Implementation Architecture.

Authors
Johannes Sedlmeir, FIM Research Center
Griffin Haskins, MOBI

Rajat Rajbhandari, MOBIWG Co-Chairs
Alan Gordon, Ford

Johannes Klepsch, BMW

MOBI Team
Tram Vo, CEO + Founder
Chris Ballinger, Advisor + Founder
Rajat Rajbhandari, Head ofStandards & Certification
Andreas Freund, CTO

Matt Shi, Supply Chain Lead
Betul Kahya, Mobility Lead
Parth Bhatt, Technical Product Manager
Grace Pulliam, Communications Manager

Contributors
Steve Amancha, State FarmMark Anders, Ford
Hiromasa Aoki, TradeLog
Alessandro Arciero, Henshin Group
Mitsuharu Arinori, TradeLog
Daniel Bachenheimer, Accenture
Murad Baig, Netsoltech
Sebastian Banescu, Quantstamp
Joe Bannon, KAR Auction Services
Patrick Bartsch, AWS
Brian Behlendorf, Hyperledger
Foundation
Massimo Belluz, Henshin Group
Roger Berg, DENSO
Manuel Bolsinger, BMW
Bill Brewster, Olinda SolutionsPeter Busch, Trusted IoT Alliance
Lucie Chabert, Stellantis
Alex Choo, ASJade
Nicola Cianci, Stellantis

Randy Cole, Ownum
Etienne Costet, Stellantis
Michelle Corson, On The Road Lending
Claudia Damari, Henshin Group
Daisuke Date, Mazda
Pierre Delaunay, Stellantis
Martin Derka, Quantstamp
Steven Douglas, DENSO
Olivier Emsalem, Stellantis
Aaron Fong, Honda
Daniel Fox, Olinda Solutions
David Freeman, DLT Labs
Masahiro Fujita, TradeLog
Sanshiro Fukao, ITOCHU
Matteo Gandolfi, Henshin Group
Fabrizio Garetto, Stellantis
Todd Gehrke, Luxoft
John Gerryts, Oaken Innovations
Dante Giancola, Ownum
Alan Gordon, FordShigemitsu Hara, OricoSebastien Henot, Accenture
Kawanishi Hiromi, Mazda
Kinoshita Hiroshi, Mazda
Max Huang, Celebri AI
Haolun Huang, DENSO
Tooru Inoue, Orico
Alvin Ishiguro, TradeLog
Hitoshi Iwamoto, Honda
Divyesh Jadav, IBM
Nick James, AWS
Sajit Janardhanan, AWS
Sumita Jonak, USAA
Matthew Jones, IBM
Kazuya Kamata, TradeLog
Motohisa Kamijo, Nissan
Masaru Kakuchi, Orico
Yoji Kawanishi, ITOCHU
Sanjay Khunger, Ford
Johannes Klepsch, BMW
Toru Kimura, Honda
Christian Koebel, Honda
Yasuhiro Komine, Honda
Karthik Krishnamurthy, AWS
Audrius Kucinskas, CarVertical
Jignesh Kumar, DENSO
Subrata Kundu, Hitachi
Jonathan Lautenschlager, FIM
Research Center
Frederic Legrand, Stellantis
Chengnian Long, CPChain
Phebe Lu, ASJade
Kanishk Mahajan, Accenture
Ishii Makoto, Mazda
Will Maney, USAA

Domenico Mangiacapra, Henshin Group
Piyush Manocha, Accenture
Jim Mason, DMX
Hisashi Matsumoto, Anritsu
Eiji Matsumura, Anritsu
Lowell McComb, BMW
Richard Meszaros, Accenture
Takuya Mimori, Vitesco
Emmanuel Monzies, Stellantis
Takumi Mori, Hioki
Ryosuke Morisada, Mazda
Lukas Mueller, BMW
Tsunehiko Murai, OricoHiroaki Murase, ITOCHU
Ash Naik, AAIS
Hiroshi Nakajima, Orico
Yasuhiro Nakayama, AUCNET
Taro Nakata, Kaula Lab
Alberto Nasi, Stellantis
Andrea Neri, Stellantis
Keisuke Nisugi, TICO
Matsuo Naoya, TradeLog
Takehisa Obara, Hioki
Yasuhiko Ogushi, Kaula Lab
Shuichi Ohki, Kaula Lab
Harunobu Ohmae, ITOCHU
Katsuji Okamoto, Kaula Lab
Mitsuyuki Okano, Orico
Adewale Omoniyi, AWS
Hans Otten, Autodata Solutions
Sunil Paul, SpringFreeEVFrancesco Petrignani, Traent
Dean Phillips, AWS
Robin Pilling, MOBI
Boris Polania, Honda

Christian Poulain, Stellantis
Nick Pudar, GM
Mathias Reinhartz, Stellantis
Klaus Roehm, Bosch
Angela Ruthenberg, Autodata
Solutions
Sandeep Saini, Vitesco
Futoki Saito, ITOCHU
Yoshihide Sakai, ITOCHUDavide Salerno, Henshin Group
Shoki Sato, Orico
Takashi Sendo, TradeLog
Fabio Severino, Traent
Otto Schell, Stellantis
Vyacheslav Sharipov, Aucnet
Mark Shih, ASJade
Kikuchi Shinichi, Mazda
Arwen Smit, MintBit/MOBI
Sudha Sriram, Ford
Suresh Sundararaj, Ford
Srinivasa Sunil, Vitesco
Yoshinori Suzue, Nissan
Priya Tabaddor, Cognizant
Nobuaki Tabata, Mazda

Ryan Tabibian, CarIQ
Yasuhiro Takabe, Mazda
Yuhei Takai, ITOCHU
Takahara Shinji, Mazda
Tatsurou Takahashi, Mazda
Tetsuya Takahashi, Hioki
Leonardo Tapanelli, Stellantis
Sam Teng, ASJade
Sajjad Thaika, Accenture
Vitthal Thamke, Vitesco
Shinnosuke Tsuboyama, Mazda
Kaiho Tsuneki, Softbank Drive
Long Tran, AWS
Christain Umbach, Xapix
Hisakazu Usui, Mazda
Wanda Wang, AIOI Insurance
Takashi Watanabe, Anritsu
Spencer White, Ford
Xin Xu, DENSO
Katsutoshi Yamazaki, Honda
Kubota Yasuyuki, Mazda
Yasuhiko Yuasa, Honda
Xiaoliang Zhu, Hitachi

Table of Contents

01

Executive Summary

02

Glossary of Terms

03

Typographical Conventions

04

MOBI VID Standards

05

Use Case: Vehicle Registration
5.1. Use Case Summary
5.2. Technical Workflow
5.3. Further Considerations
5.4. Matching the Architecture to Business Case Requirements

06

Use Case: Vehicle Maintenance6.1. Use Case Summary
6.2. Technical Workflow
6.3. Further Considerations
6.4. Matching the Architecture to Business Case Requirements

07

Outlook: Further Use Cases and Next Steps

08

References

Executive
SummaryMOBI VID is a tool thatleverages technical building
blocks to support dynamicallydefined, multi-stakeholder,interoperable mobility
ecosystems,

Distributed ledger technologies (DLT), including blockchains andother cryptographic tools that enable decentralized
applications, have rapidly evolved in recent years. These
technologies are playing a pivotal role in accelerating andshaping the digital transformation within the mobility industry.
Fundamental to this transformation is the establishment of aninteroperable Vehicle Identity (VID). Shared ledger
technologies, Decentralized Identifiers (DIDs), and Verifiable
Credentials (VCs) for vehicle identities are crucial technicalbuilding blocks for the new mobility and transportation IoT
ecosystems of the future.
MOBI VID is a tool that leverages these technical building
blocks to support dynamically defined, multi-stakeholder,interoperable mobility ecosystems, yielding increasedtransparency, coordination, control, privacy, and automation
between stakeholders.

MOBI VID acts as a trust
anchor to support use cases
across the full mobility value
chain.

Use cases that depend on a secure digital VID include fully
automatic registration and titling, vehicle payments, supply
chain track-and-trace, automotive financing, autonomousvehicle data marketplaces, and many more. This document
introduces a technical standard for selected VID-based use
cases, describing repeated information flows that serve asbuilding blocks for more complicated use cases. Therefore it is1
the technical counterpart of the Vehicle
Identity Use Cases andBusiness Requirements (MOBI VID0002/UC/2021) standard.

1. “Vehicle Identity Use Cases and Business Requirements,” Standards, MOBI, last modified
January 2021, https://dlt.mobi/standards/.

© 2024 MOBI — VID II Reference Implementation Architecture2

Glossary of Terms

AccessCertificates (ACs)ACs are documents that allow a particular entity to access aparticular endpoint in the network’s data layer.

Accessor

An entity is an Accessor of a resource if it attempts to access the URI
endpoint. An Accessor may need to go through security andauthentication processes in order to actually access said endpoint.

Agent, Cloud
Agent, orSoftware AgentAn Agent, Cloud Agent, or Software Agent manages a digital walletand its communications, either on a local device (edge agent) or
remotely (cloud agent). Edge agents provide direct control but rely on
the device's connectivity, while cloud agents ensure continuous online
availability and data storage. The choice depends on needs related to
privacy, control, and communication, with "wallet" referring toapplications that integrate these functions.

Binding

Cryptographic binding ensures that private keys and credentials are
securely tied to their rightful owners, often challenging due to the easeof copying and sharing digital information. To enhance security,
methods like using secure hardware or multi-factor authentication,
including vehicle-specific attributes in credentials, are employed. In
remote interactions, additional measures like economic incentives or
all-or-nothing non-transferability (linking all credentials in a wallet)
help prevent unauthorized credential sharing. Stronger binding
methods, however, add complexity to processes like credential
transfer, which may require re-issuance by the issuer. Overall, binding
is a crucial aspect of digital security, applicable to both traditionaland decentralized identity management systems.

© 2024 MOBI — VID II Reference Implementation Architecture3

Glossary of Terms

Blockchain

Blockchains are distributed digital ledgers of cryptographically signed
transactions that are grouped into blocks. Each block is cryptographicallylinked to the previous one (making it tamper-evident) after validation andundergoing a consensus decision. As new blocks are added, older blocks
become more difficult to modify (creating tamper resistance). New
blocks are replicated across copies of the ledger within the network, andany conflicts are resolved automatically using established rules.

Certificate ofConformity (CoC)A CoC is an official document issued by a vehicle manufacturer,
declaring that the vehicle complies with the regulatory standards set
by a specific country or region. This certificate is essential for theregistration and homologation of vehicles, ensuring they meet safety,
environmental, and performance requirements. It typically includes
details about the vehicle's specifications, type approval number, andmanufacturer information. Although widely used in the European
Union, similar certificates are required in other regions to verify
compliance with local regulations, such as environmental standards
set by the United States Environmental Protection Agency.

Cryptographic
Fingerprint

A digital signature that uniquely identifies data and has the property
that changing a single bit in the data will cause a completely different
message to be generated.

Cryptographic
Obfuscation

Data that has been distorted by cryptographic or other means to hideinformation© 2024 MOBI — VID II Reference Implementation Architecture4

Glossary of Terms

Data Host

A Data Host is an entity that stores data and is trusted with properly
administering it, authenticating requests to access the data, anddistributing the data as needed.

Data Owner

The Data Owner is the owner of a certain piece of data, usually thesame as the entity that generated said data (referred to as the Data
Generator).

Data Host
Bootstrap
Certificate (DBC)

A DBC is a certificate that provides a cryptographic proof that a
particular entity (Data Host) is allowed to serve a particular type ofdata from a specific URI.

Decentralized
Identitifer (DID)

A W3C DID is a globally unique identifier that can be resolved to a DID
Document, or de-referenced on a specific distributed ledger network,
much like a URL on the Internet.

DID Document

A DID Document is a simple text document that describes how to usethat specific DID. Each DID Document may contain at least three
things: proof purposes, verification methods, and service endpoints. A
DID Document can specify that a particular verification method, suchas a cryptographic public key or a pseudonymous biometric protocol,
can be used to verify a proof that was created for the purpose ofauthentication. Service endpoints enable trusted interactions with the
DID controller. This document specifies a common data model, format,
and operations that all DIDs support.

© 2024 MOBI — VID II Reference Implementation Architecture5Glossary of Terms

Distributed Ledger
Technology (DLT)DLT enables consensus about the state of replicated, shared, andsynchronized digital data geographically spread across multiple sites,countries, or institutions. A peer-to-peer network is required as well as
consensus algorithms to ensure replication across nodes is undertaken.
Blockchains are the most well-known example, though generalpractical byzantine fault tolerant systems fall under this category as
well.

Data Bucket

A Data Bucket is a logical data abstraction for a persistent data store.
Data written to a Data Bucket can be used repeatedly over time.

Data Stream

A Data Stream is a logical data abstraction for data buffers. Acts as
an ephemeral “stream” of data and persists for a set period of time in
the network until it is purged in the online systems, thereafter, moved
to nearline data systems and ultimately moved to offline data systems.

Digital Wallet

A Digital Wallet is a software application that stores private keys andVerifiable Credentials (VCs), often running on devices likesmartphones, laptops, servers, or vehicle hardware. It is used forencrypting messages, proving control over digital identities, andmanaging permissions on distributed ledgers. Additionally, it can holdunique identifiers like a link secret for security. In the context ofvehicles, the wallet operates reactively, responding to authorized
requests for actions like digital signing or providing sensor data.
Access and functionality of the wallet are defined by manufacturer,
owner, or user policies, with different deployment options including on
a user's mobile device, vehicle's hardware, or a manufacturer's server.

© 2024 MOBI — VID II Reference Implementation Architecture

6

Glossary of Terms

Entity Certificate(EC)

An EC is a certificate that represents all of a particular entity’s
network-level information and metadata, including but not limited to
identifiers about who they are, the URIs to delegate trust to, and their
public keys. An EC is always paired with a corresponding EID.

EID

The bit string denoting the identifier associated with an entity.

EntityItem inside or outside an information and communication technology
system, such as a person, an organization, a device, a subsystem, or agroup of such items that has recognizably distinct existence,

VID System

A VID System is any implementation that is compliant with the VID I
Technical Specifications.

VID Event

A VID Event is any discrete event that produces a change in the stateof the system. Examples include writing data to a URI, reading datafrom a URI, registering a new EID and EC, etc..

Generalized
Timestamp

A generalized timestamp is an object, such as a Bitcoin/Ethereum
block number, verifiable delay function, etc. that enables any entity toverify the correctness of that timestamp

Identity

An attribute or set of attributes that uniquely describe a subject withina given context© 2024 MOBI — VID II Reference Implementation Architecture7

Glossary of Terms

Key-Value (KV)Store

A KV Store is a system that stores (key, value) pairs. The key is used toobtain access to the value in some way. Distributed KV stores are KV
stores spread across multiple machines and can effectively maintain a
global state table.

Know-YourCustomer (KYC)

KYC is the process of verifying the identity, risks, and other information
associated with a customer before initiating any business relationship.

Network

A system implemented with a collection of interconnectedcomponents. Such components may include routers, hubs, cabling,telecommunications controllers, key distribution centers, and technicalcontrol devices.

Node

A node is a participant in and a resource contributor to a network. The
more nodes in a network, the more resilient is the network against
node failures, thereby, enduring network availability. Furthermore, thelarger the number of nodes in a (public) network, the more difficult it isto censor network transactions and, typically, to collude against othernetwork participants.

Original Equipment
Manufacturer(OEM)

An OEM is an organization that makes devices from component parts
either made internally or sourced from other organizations. In thecontext of this document, this is (generally) a vehicle manufacturer.

© 2024 MOBI — VID II Reference Implementation Architecture8Glossary of Terms

PersonallyIdentifiable
Information (PII)

PII is any information: (1) that identifies or can be used to identify,
contact, or locate the person to whom such information pertains, (2)from which identification or contact information of an individual canbe derived, or (3) that is or might be directly or indirectly linked to anatural person

Revocation
Certificate (RC)A RC revokes AC permissions if the AC has not expired automatically.

Role

Roles regulate the creation of and access to data contained within the
network.

Secure Sockets
Layer (SSL)

An SSL provides privacy and data integrity between two
communicating applications. It is designed to encapsulate otherprotocols, such as HTTP. TLS v1.0 was released in 1999, providing slight
modifications to SSL 3.0.

Tamper-Evident

A process which makes alterations to the data easily detectable.

Transport Layer
Security (TLS)

A TLS is an authentication and encryption protocol widely
implemented in browsers and Web servers. HTTP traffic transmittedusing TLS is known as HTTPS.

© 2024 MOBI — VID II Reference Implementation Architecture9Glossary of Terms

Trust Anchor

A Trust Anchor is an authoritative entity represented by a public key
and associated data (see RFC 5914). Onboarding and offboarding ofentities is facilitated by the network governance in Section 6.

Uniform Resource
Identifier (URI)

A URI is a compact sequence of characters that identifies an abstract
or physical resource. This specification defines the generic URI syntax
and a process for resolving URI references that might be in relative
form, along with guidelines and security considerations for the use of
URIs on the Internet. The URI syntax defines a grammar that is asuperset of all valid URIs, allowing an implementation to parse thecommon components of a URI reference without knowing the schemespecific requirements of every possible identifier. This specification
does not define a generative grammar for URIs; that task is performedby the individual specifications of each URI scheme.

URL

A reference to a web resource that specifies its location on acomputer network and a mechanism for retrieving it. A typical URL
could have the form http://www.example.com/index.html, whichindicates a protocol (http), a host name (www.example.com), and afile name (index.html). Also sometimes referred to as a web address.

Universally Unique
Identifier (UUID)A UUID is a 128-bit value. There are three different basic types of
UUIDs: time-based, DCE security, and name-based. UUIDs are usedin many protocols and software products in a variety of ways, eachproviding different guarantees, such as uniqueness or persistence.

© 2024 MOBI — VID II Reference Implementation Architecture

10Glossary of Terms

This specification defines a uniform mechanism for using UUIDs in
protocols and software products that need to utilize either uniquenessor persistence, or both.

Unique Vehicle
Identifier (UVI)A UV is a distinct alphanumeric code within a specific system, differingfrom a Vehicle Identifier (VID). It acts as a specialized Digital Identifier(DID) for vehicles, linking uniquely to a particular vehicle through its
associated Verifiable Credential (VBC), representing the vehicle's
minimum digital identity. The UVI facilitates various functions such asverifying existence, controlling access, and confirming specifications.
In a simplified view, the UVI serves as a key in a key-value store,
allowing for the retrieval of vehicle data from an Original Equipment
Manufacturer's (OEM's) network.

Vehicle BirthCertificate (VBC)

A VBC is a data structure of strings and integers that records
information about a particular vehicle at its creation.

VehicleRegistration
Authority (VRA)

Vehicle registration authorities (e.g., Department of Motor Vehicles in
the US) typically are government agencies that administers vehicle
registration and driver licensing.

VehicleReigstration
Document

The registration certificate or vehicle registration document gives thedriver the official permission to participate in road traffic with thevehicle. The document contains information about the owner and thevehicle, such as the owner's name, the date of its manufacture, andthe© 2024 MOBI — VID II Reference Implementation Architecture11

Glossary of Terms

engine and chassis numbers. The registration certificate must always
be carried by the driver and must be available at a traffic stop. In thisway, the vehicle can be identified. A registration certificate is required
for all vehicles subject to registration.

VehicleRegistration
Workflow (VRW)

VRW is the process of (digitally) registering a vehicle throughinteraction of a vehicle (and typically other stakeholders such as thevehicle dealer or owner) with an authority.

Vehicle Title
Document (VTD)

The vehicle owner is referenced in the registration certificate part II(Vehicle Title Document). In some legislations, it also indicatesownership of the vehicle. If the vehicle is financed (credit/leasing), theVTD typically remains with the lender.

Verifiable Data
Registry

A verifiable data registry is an abstraction of databases deemed
reliable and trustworthy by a significant number of stakeholders. It
could be a platform like GitHub or an Interplanetary File System (IPFS),
contingent on stakeholder trust. These registries typically necessitate
robust integrity assurances and timestamping. Blockchains anddistributed ledgers serve as prime examples, offering exceptional
integrity and reliability. Their use ensures data authenticity andsecurity, making them ideal for sensitive and critical information
management.

VehicleIdentification
Number (VIN)

A VIN is a structured combination of characters assigned to a vehicle
by the manufacturer for identification purposes© 2024 MOBI — VID II Reference Implementation Architecture

12Full access to this Standard and other MOBI
Standards are available to MOBI members.
If you are not part of the MOBI community and would
like to become a member, please fill out our“Membership Inquiry Form” at dlt.mobi/participate
Members gain access to standards, working groups,
and many other benefits.
Join us in building the Web3 Economy!
If you have any questions regarding MOBI VID,
please email connect@dlt.mobi

dlt.MOBI@dltMOBI

MOBI@dltMOBI

connect@dlt.MOBI