Key Points

1. MOBI is an open source organization for mobility blockchain solutions
2. DMX is a MOBI member
3. MOBI has a Vehicle Identity project ( VID )
   1. We had an active role in drafting the VID spec
   2. We also were appointed to the MOBI UBI ( Usage Based Insurance ) team to draft a spec for UBI based on actual vehicle data
4. Many OEMs use systems vendors like IAV, ZF, XAIN etc for integrated solutions on connected vehicles 

References

Key Concepts

MOBI members include: 

Vehicle Data Privacy

Consistent with GDPR, CCPA and other privacy regulations,

Vehicles need to ensure compliance with both regulations and consumer policy preferences for owners, drivers, passengers at all times

See updates on the MOBI site to CMDM rules 

See US regulation proposals from Gina Raimondo, US Secretary of Commerce, on China EV regulations

US to issue rules on Chinese connected vehicles this autumn _ Reuters.   link

US to issue rules on Chinese connected vehicles this autumn _ Reuters.pdf.  file

"We are going to do whatever we need to do to make sure China doesn't use Mexico to end run around these new tariffs," Raimondo said.

Connected cars have onboard integrated network hardware that allows internet access, allowing them to share data with devices both inside and outside the vehicle.

Raimondo said connected vehicles "have thousands of sensors, thousands of chips - they're controlled by software, which is coming from Beijing in the case of Chinese-made cars. They know where the driver goes, what the driving patterns are, what you're saying in your car. It's a lot of data around U.S. persons that goes right back to Beijing."

Potential Value Opportunities

1. We helped draft the Vehicle Identity Standard for MOBI ( the v.3 draft document is here )
2. We can leverage the MOBI model nicely for our related blockchains
3. MOBI is looking at the connected vehicle interfaces for related blockchains
4. Many vendors are working on independent projects for connected vehicles and some of those include proprietary blockchain
5. AGL ( Automotive Grade Linux project ) is probably the leading standard on this planet for connected vehicle integration and management
6. If we stay partnered with MOBI and AGL we will have the  vehicle integration on the vehicle and related blockchain, AI solutions that we can leverage

Managing Vehicle Data Systems on Blockchain

https://www.linkedin.com/posts/anthonyjjday_mercedes-benz-launches-blockchain-based-data-activity-6957960646982279168-3zQN?utm_source=linkedin_share&utm_medium=member_desktop_web

I am regularly asked ‘are there any use cases for Blockchain and AI, or Blockchain and Big Data’. Well here’s a good one.

Decentralising access to high volume specific, generic or real-time data as input to AIs or as ‘oracles’ to other automated processes (smart contracts or IoT automation) allows for more scalability and potentially demand for data assets.

In line with this approach, this platform will accept stablecoins, rather than having its own native cryptocurrency (showing theyyir revenue model is the data, rather than linking it to a token - nice move).

The data is not held on-chain, but minted as NFTs and brought through from decentralised file storage on-demand, which should improve performance and support GDPR and other privacy considerations.

To what extent other manufacturers will join this initiative will be interesting to see. Many car makers see data as proprietary (even though it may technically belong to the driver of the vehicle!) and have taken a more centralised approach to building walled-garden platforms to protect their own IP or maximise revenue (but not interoperability).

Do you think we’ll see car makers embracing decentralisation and Web3 in future? What’s your take on this Mercedes use case?

Mercedes Benz Ledger Insights Platform for Vehicles

https://www.ledgerinsights.com/mercedes-benz-launches-blockchain-based-data-sharing-platform/

Data Market to buy, sell data for many solutions including AI

Two years ago, we wrote about a Daimler pilot with AI organization Ocean Protocol for decentralized data exchange. This week Daimler South East Asia, part of the Mercedes Benz Group, went into production with its Acentrik blockchain platform, based on that pilot.

Artificial Intelligence and machine learning require data. A lot of it. And enterprises are sitting on massive volumes of data without earning the full financial benefits. Hence the concept of a data marketplace where enterprises can buy and sell data. 

If someone is concerned about privacy, they can share the data in a privacy-preserving manner purely for calculating results without disclosing the underlying data.

Acentrik is squarely targeted at enterprise users, including Know Your Business and extensive access controls. The data is not stored on the blockchain, but a non-fungible token (NFT) represents each dataset and a metadata hash is stored with it. 

Transactions are executed on public blockchains Polygon or the Ethereum Rinkeby test network, but users can pay for data with a stablecoin rather than a cryptocurrency. However, the MATIC crypto is required to pay Polygon gas fees. The underlying data can be stored on IPFS or AWS S3.

Jim >>

Decentralized data management for vehicles is a clear necessity. Like existing IT systems, vehicle systems require identity, role-based access, secure data in-flight, at-rest and in execution. There are many systems and application solutions on vehicles and in the mobility space. Some generate tons of data rapidly. A logical data architecture evolves from an RDD approach ( Responsibility Driven-Design ). ADC - application data controllers can locally process and respond to local events fulfilling the primary responsibilities those controllers  have. There are also many other potential applications that can benefit from access to vehicle data. Some of those applications would support vehicle wellness, the driver or passengers directly. Some link to off-vehicle solutions ( eg Google maps etc ). Normally 3rd party data access requires added governance: consent, anonymization, aggregation and access restrictions in compliance with GDPR and other regulations.

Some of these data use cases would also fit a variety of private, permissioned local blockchain DBs. 

Potential Challenges and Questions 

On-vehicle and off-vehicle systems

Is the VID a document in a ledger that is tied to the VIN?

The on-vehicle systems include local blockchains. The VID resides on the vehicle and will be accessed by external parties ( DMX etc ) who are authorized to access the VID views. The VID includes a digital version of the VIN along with the VBC ( Vehicle Birth Certificate ) issued by OEMs.

DMX solutions sit off-vehicle now and synch as needed with the vehicle. Our blockchain model reflects some of the blockchains on the vehicle ( VINblock similar to VID ). There will be many applications, services and related data and blockchains off-vehicle that will integrate with the on-vehicle systems.

Wallets and identities

Where are each of these various certificates referred to created and ledgered ?

There are hardware and software car wallets that OEMs can add to vehicles to securely store identities on the vehicle. The organizations issuing the identities will logically be able to provide recovery services. OEMs will issue a certificate for related data ( Vehicle Birth Certificate ) etc. Dealers, Insurers, payment providers etc can also issue certificates.

Implementation

This appears to me to be a mix of both defining standards but also defining a new system, which means I gather its defining a single system that would be built and hosted by finite private parties. Am I reading this correctly?

In theory, the standards and supporting recommendations on architecture, governance can be used by others to build solutions with common designs that should interoperate well with lower overall costs than independent design efforts. With well-defined blockchains, there isn't any reason multiple vendors can't benefit from shared, immutable, trusted ledgers with private data and access controls at lower costs than building independent systems.

Our team hasn't been looking at the economics of the vehicle ecosystem directly. We proposed a separate study for use cases on connected vehicle systems that focuses on business value delivered for different parties. The MOBI leaders haven't approved that yet. The UBI ( Usage Based Insurance ) team I'm part of now should look at the insurance use cases in detail.

That said, it's clear many parties are looking to invest in building these systems. OEMs and some vehicle component vendors are building them on their own now. With AGL, MOBI and other industry standardization efforts and the benefits of a trusted shared ledger ecosystem with tokens, accounts and payments, I expect it's easier to measure benefits accurately and transact between receivers and providers of value in the ecosystem.

Will many of these systems ( traffic, insurance, payments, maintenance etc) be hosted by finite private parties? I'll guess yes. Similar to the new shared systems of the IBM Food Trust network, the IBM - Maersk shipping system and others, you have dominant industry players in a segment ( Walmart, Maersk etc ) partnering with network providers: IBM, Microsoft, AWS etc ) to create dominant ecosystems. With 5G, you may also see governments award the entire network contract to a single vendor the way the Federal government awarded FirstNet to AT&T. Looking at ledger frameworks for related off-vehicle systems, I expect some will be proposed by lead vendors ( Fabric, Corda, Quorum, Ethereum ). I would be surprised to see other frameworks in consideration on a broad basis.

The question is who and how will DMX partner with on these efforts and what is our value-add in these ecosystems. In addition to direct efforts with OEMs and other industry leaders, our participation in these industry groups ( Hyperledger, MOBI, AGL ) can help find trends and opportunities.

Governance

Is governance of such an system subject to a new regulatory body and if so, how is that body going to be constituted?

In our VID specification draft, we anticipated the role for regulatory organizations and have defined a regulator role.

Clearly the model of connected, shared, immutable, trusted ledgers with private data and access controls makes governance relatively easy and low-cost. There are many existing regulatory bodies that have responsibilities on vehicles, titles, driving performance, tolls, compliance etc. The architecture allows an easier, secure, connected environment with clear access controls for these organizations to perform their duties.

Given the criticality of these new vehicle subsystems for safety, operation etc I think you are right that requirements and regulations will change. Some regulators may have expanded responsibilities and new ones may be required or legislated.

Vehicles now have digital identities, operate intelligently, wallets, accounts for payment, real-time integration with traffic systems, insurance, maintenance and emergency services. Vehicles can interact directly with any entity: OEMs, dealers, service providers, owners, drivers, regulators etc.

In my opinion, if this goes right you have governments providing regulations along with industry consortiums. For example, FINRA does a very good job in the financial services industry providing education and compliance oversight and reducing SEC audit audits and costs.

Candidate Solutions

Liechtenstein mobility innovations on blockchain - Otto Frommelt

https://ottocfrommelt.li/Blockchain/

MOBI on connected vehicle infrastructure initiative

https://dlt.mobi/

Step-by-step guide for Example

sample code block

Recommended Next Steps

Related articles