Building theWeb3 Economy

MOBI
TRUSTED TRIP
CREDENTIALTECHNICAL SPECIFICATIONOF DATA SCHEMASMay 2024

Version 2.0: MOBI TT0002/TS/2024
Version 1.0: MOBI TT0002/TS/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 moreworking to create standards and build the Web3 digital infrastructure
for connected ecosystems and IoT commerce.
MOBI is creating standards for trusted self-sovereign data andidentities (e.g. vehicles, people, businesses, things), verifiable
credentials, and cross-industry interoperability, with the goal of making
transportation more efficient, equitable, decentralized, and circular, allwhile preserving the data 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 theconsortium 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 theelements of this document may be the subject of intellectual property
rights. In accordance with MOBI IPLR policy, a 60-day review period
is provided to the MOBI community to disclose any and all IP matterspertaining to this standard. MOBI shall not be held responsible foridentifying 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 convenienceof users and does not constitute an endorsement. Sincere thanks
and appreciation are extended to those who contributed their uniqueinsights to the MOBI Trusted Trip Technical Specifications.

AUTHOR
Rajat Rajbhandari, PhD, MOBIREVIEWERS

Matt Shi, MOBI

Daniel Bar-Lev, MEF Forum

Christian Koebel, Honda

Xinxin Fan, IoTeX

Dermot O’Brien, EU Commission

Roger Berg, DENSO

Andreas Freund, MOBI

Garrett Graham, Accenture
Toru Kimura, Honda

Pramita Mitra, Ford

Johannes Sedlmeir, University of Bayreuth
Alexander Sorokin, Global Battery Alliance

CONTRIBUTORS
Praveen Abbaraju, Hitachi

Aaron Fong, Honda

Mark Anders, Ford

Masahiro Fujita, TradeLog

Steve Amancha, State Farm
Hiromasa Aoki, TradeLog

Alessandro Arciero, Henshin Group
Mitsuharu Arinori, TradeLog
Anna Baranskaya, Nissan
Patrick Bartsch, AWS

Massimo Belluz, Henshin Group
Roger Berg, DENSOBill Brewster, Olinda Solutions
Lucie Chabert, Stellantis
Alex Choo, ASJade

Nicola Cianci, Stellantis

Etienne Costet, Stellantis

Claudia Damari, Henshin Group
Daisuke Date, Mazda

Pierre Delaunay, Stellantis
Steven Douglas, DENSO

Olivier Emsalem, Stellantis

Daniel Fox, Olinda Solutions
Sanshiro Fukao, ITOCHU

Matteo Gandolfi, Henshin Group
Fabrizio Garetto, Stellantis
Alan Gordon, Ford

Shigemitsu Hara, Orico

Kawanishi Hiromi, Mazda
Kinoshita Hiroshi, Mazda
Haolun Huang, DENSO
Felix Huang, DENSO
Tooru Inoue, Orico

Alvin Ishiguro, TradeLog

Hitoshi Iwamoto, Honda
Nick James, AWS

Sajit Janardhanan, AWS

Kazuya Kamata, TradeLog
Motohisa Kamijo, Nissan
Masaru Kakuchi, OricoYoji Kawanishi, ITOCHU

Adewale Omoniyi, AWS

Christian Koebel, Honda

Francesco Petrignani, TraentToru Kimura, Honda

Yasuhiro Komine, Honda

Karthik Krishnamurthy, AWS
Jignesh Kumar, DENSO

Subrata Kundu, Hitachi

Frederic Legrand, Stellantis
Phebe Lu, ASJadeIshii Makoto, Mazda

Domenico Mangiacapra, HenshinGroupHisashi Matsumoto, Anritsu
Takuya Mimori, Vitesco

Emmanuel Monzies, Stellantis
Takumi Mori, Hioki

Ryosuke Morisada, Mazda
Tsunehiko Murai, OricoHiroaki Murase, ITOCHU
Ash Naik, AAIS

Hiroshi Nakajima, Orico

Yasuhiro Nakamaya, 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

Sunil Paul, Spring Free EV

Chrisitan Poulain, Stellantis

Mathias Reinhartz, Stellantis
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
Sudha Sriram, Ford

Suresh Sundararaj, Ford
Srinivasa Sunil, Vitesco

Yoshinori Suzue, Nissan

Katsutoshi Yamazaki, Honda
Hideo Yoshida, Nissan

Yasuhiko Yuasa, Honda

Nobuaki Tabata, Mazda

Yasuhiro Takabe, Mazda
Yuhei Takai, ITOCHU

Takahara Shinji, Mazda

Tatsurou Takahashi, Mazda
Tetsuya Takahashi, Hioki

Leonardo Tapanelli, Stellantis
Vitthal Thamke, Vitesco

Shinnosuke Tsuboyama, Mazda
Sam Teng, ASJadeLong Tran, AWS

Xin Xu, DENSO

Takashi Watanabe, Anritsu

Xiaoliang Zhu, Hitachi

Hisakazu Usui, Mazda
Spencer White, Ford

Kubota Yasuyuki, Mazda

MOBI TEAM
Tram Vo, CEO + Founder

Parth Bhatt, Technical Product Manager

Rajat Rajbhandari, Head ofMatt Shi, Supply Chain Lead

Chris Ballinger, Advisor + FounderStandards + Certification
Andreas Freund, CTO

CONTACT		
connect@dlt.mobi

Betul Kahya, Mobility Lead

Grace Pulliam, Communications Manager

TABLE OF CONTENTS
01

About MOBI Trusted Trip Tech Specs					

02Glossary of Terms								

03Typographical Conventions						

04Fundamental Components of MOBI Trusted Trip VC		4.1. MOBI Trusted Trip Verifiable Credential					4.2. MOBI Trusted Trip Specification						

05Conformance									5.1. Conformance Targets								5.2. Conformance Levels								

06Security Considerations							

07References

ABOUT MOBI TRUSTEDTRIP TECH SPECS

The convergence ofThe convergence of maturing technologies, such as AI, IoT, andmultiple rapidly maturing

blockchain, permits any entity — whether a person, vehicle,

technologies, such asdevice, package, piece of infrastructure, or a data set — to have

AI, IoT, and blockchain,

an identity, be intelligent, and transact with other things. Thesepermits any entity to haveusage-based

an identity, be intelligent,decentralized mobility applications such as seamless multimodal

and transact with othertransportation, urban road tolling, congestion pricing, usage-things.

based insurance, incentivizing green and sustainable behavior,economy-of-thingstransactions

willinclude

supply chain track and trace, and numerous other use cases yet
to be imagined. In order to facilitate decentralized transactions in
the New Economy of Movement, the need for security and rapid
throughput will demand a new type of identity solution, one that isblockchain-based, self-sovereign, decentralized, and machinereadable. MOBI Trusted Trip links an entity’s sovereign identitywith its timestamped location in the form of credentials (hence,MOBI Trusted Trip Verifiable Credentials or MTTVC) and enables
the linkage to be certified throughout a trip in a trusted network.

MOBI Trusted Trip is
the key primitive of themulti-trillion dollar “New
Economy of Movement.”

The MTTVC is based on W3C’s Decentralized Identity (DID) and
Verifiable Credential (VC) Specifications. Utilization of DID allows
holders, on their own terms, to share trusted data with anotherverified entity without disclosing identity-related informationand other selective attributes. MOBI Trusted Trip allows a holderof such credentials to prove to verifiers that it was present,
completed a trip, used a resource, provided a service, or
performed other relevant activities on the trip while safeguarding
its Personal (or organizational) Identifiable Information (PII).
MOBI Trusted Trip is the key primitive of the multi-trillion dollar“New Economy of Movement.” MOBI Trusted Trip is a higher level
concept and can be implemented as a physical presence: a trip
completed or in progress by a roaming entity (such as a person,vehicle, smartphone, EV battery, package, or part). Attributesof the Trusted Trip can be presented by the information holder
to anyone and easily verified by authorized entities (verifiers)
without a centralized third party.
© 2024 MOBI — TT Technical Specification of Data Schemas

2

GLOSSARY OF TERMS
W3C Decentralized

A World Wide Web Consortium (W3C) Decentralized Identifier

Identifier (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.

Geographic Location

A physical space that can be represented by either a single
latitude, longitude, or altitude, or a combination. Such locations
can be warehouses, intersections, fixed locations on a highway,etc.

HolderDevice/user/entity/application that holds a Verifiable Credential(VC) about a subject(s) and presents it to a verifier(s) in order toaccess goods/services.

IssuerDevice/user/entity/application that asserts claims about one ormore subjects by creating a VC and providing it to a holder.

Location Authority

Device/user/entity/application that owns/operates the physicallocation/segment/service used by the subject and has a way toidentify the subject, detect physical presence of the subject, orconfirm the service provided to the subject.

Location Presence

A specific type of MTTVC that contains attributes of evidence

Credential

to confirm the subject’s physical presence at a location. This
credential can be used to communicate something like “hereare the attributes to prove that I was present at a mile marker
6.4 on IH10. on 07.01.2021 at 8:00AM CST.”© 2024 MOBI — TT Technical Specification of Data Schemas

3

GLOSSARY OF TERMS
Personal Identifiable

PII is any information (1) that identifies or can be used to identify,

Information (PII)

contact, or locate the subject to whom such information
pertains, (2) from which identification or contact information of
an individual can be derived, or (3) that is or might be directly or
indirectly linked to a natural person.

Physical Location

A site (an area, a structure, or group of structures) or an area
within the site where something was, is, or will be located. For
example, loading dock #4, berth at Terminal 1. Physical locations
may be defined by an organization for its business operations
and identified using a Global Location Number (GLN).

Revocation

When entities use VCs or entries of a DLT/blockchain to provetheir claims in a VP, there must be a means to disable theircapability to create proofs from this when the reason why theissuance had happened ceases to be legitimate.

Service Provider

The service provider can play the role of an issuer to the holder
by virtue of using its services. It can be a ride-hailing service, EVcharging service, tolling service, carbon offsetting service, etc.
The holder may use the service to complete trips, charge EVs,
etc.

Trip Commencement

A specific type of MOBI Trusted Trip Verifiable Credential (MTTVC)

Verifiable Credentialthat contains attributes of evidence to confirm the subject’scommencement of a trip.

© 2024 MOBI — TT Technical Specification of Data Schemas

4

GLOSSARY OF TERMS
Subject

A subject may be a device, user, entity, or application. In manycases, the holder of a VC is subject.

MOBI Trusted Trip Verifiable

An abstract credential consisting of a subject’s information

Credential (MTTVC)

related to location and other attributes structured using W3C
Verifiable Credential Data Model 1.0 standards.

Trip as an Activity

An act of traversing from one location to another location using
any mode of transportation. For example, a trip from Chicago(location 1) to New York (location 2) using a vehicle.

Trip Completion Verifiable

A specific type of MTTVC that contains attributes of evidence toCredential

confirm the subject’s completion of a trip. This credential can beused to communicate something like, “here are the attributes toprove that I completed a trip from A to B on 07.01.2021 at 8:00AM
CST.

UbietyThe particular location in space and time of a person, entity,device, or thing.

Verifier

Device/user/entity/application that receives a VC from a holder
to verify the credentials presented by the holder in order toprovide goods/services to the holder.

© 2024 MOBI — TT Technical Specification of Data Schemas

5

GLOSSARY OF TERMSW3C Verifiable Credential

The W3C VCs specification defines VCs as “a part of our daily(VC)

lives; driver’s licenses are used to assert that we are capableof operating a motor vehicle, university degrees can be used toassert our level of education, and government-issued passports
enable us to travel between countries. This specification provides
a mechanism to express these sorts of credentials on the Web
in a way that is cryptographically secure, privacy-respecting,and machine-verifiable.” In the context of MOBI Trusted Trip, anissuer can provide a VC to a holder using a digital signature tovalidate that an activity/trip occurred at the given location andtime.

Verifiable Registry

It plays a role in mediating the creation and verification ofidentifiers, keys, VC schemas, revocation registries, the issuerof public keys, etc. It may be a trusted database, government
identity database, or distributed ledger/blockchain.

Verifiable Presentation (VP)

A holder sends a VP to a verifier. It includes various attributesby Holders

about an activity/trip that occurred along with proofs of issuerand holder.

© 2024 MOBI — TT Technical Specification of Data Schemas

6Full access to this Standard and other MOBI Standards
are available to MOBI members.
If you are not part of the MOBI community andwould 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 the
MOBI Trusted Trip, please email connect@dlt.mobi

dlt.MOBI@dltMOBI

MOBI@dltMOBI

connect@dlt.mobi