m Blockchain Mobility
- jim mason
Key Points
- MOBI VID spec is useful guidance for VID design
- Will VID be a DID, FID or both?
- Vehicle digital twins need to be secure, on-board with cloud recovery at a minimum
References
| Reference_description_with_linked_URLs___________________________ | Notes__________________________________________________________________ |
|---|---|
| Vehicle Digital Tiwn | |
| MOBI VID spec | |
| MOBI Vehicle Identity use cases | |
| https://www.coindesk.com/daimler-partners-with-riddle-code-to-produce-automotive-hard-wallet | Daimler vehicle hardware wallet |
| https://www.daimler.com/innovation/case/autonomous/safety-first-for-automated-driving-2.html | Daimler autonomous vehicle safety standards |
| https://www.daimler.com/documents/innovation/other/safety-first-for-automated-driving.pdf | Daimler autonomous vehicle safety standards |
Key Concepts
Daimler Vehicle Hardware Wallet
https://www.coindesk.com/daimler-partners-with-riddle-code-to-produce-automotive-hard-wallet
Mercedes Benz parent company Daimler has partnered with blockchain firm Riddle & Code to produce a hardware wallet for automobiles.
Long term, the business alliance looks to provide solutions for self-driving vehicles and car-sharing platforms, relay traffic patterns in real-time, mesh with smart city infrastructure, and transfer accident information to the proper authorities and insurance providers.
The wallet, a tamper-resistant piece of hardware that was presented at Startupautobahn in Stuttgart, creates a cryptographic identity for vehicles. It also integrates with the vehicle’s telematic control unit (TCU) to receive, sign, and attest to sensory data from the car and surrounding infrastructure.
This information can be used to record a vehicle’s performance and ensure it received proper maintenance. The wallet can be integrated into the hardware of trucks, luxury cars, and buses “to make car rental and fleet management more efficient,” said Ben Schwarz, Riddle & Code head of communications.
Schwarz said the pricing model hasn’t been finalized, but will be based on hardware costs and involve a license model for fleet owners who deploy the wallet. A transaction-based model is also under discussion.
Daimler Autonomous Vehicle Safety Standards
https://www.daimler.com/innovation/case/autonomous/safety-first-for-automated-driving-2.html
https://www.daimler.com/documents/innovation/other/safety-first-for-automated-driving.pdf
Together with 11 industry leaders across the automotive and automated driving technology spectrum Daimler is taking the lead in developing an industry-wide definition of safety with the SaFAD white paper.
Along with Aptiv, Audi, Baidu, BMW, Continental, Fiat Chrysler Automobiles, HERE, Infineon, Intel and Volkswagen, Daimler has published a white paper entitled Safety First for Automated Driving. As well as covering all relevant safety methods for Level 3/4 SAE automated driving, the paper introduces a traceability system, which extends from the primary goal – being safer than the average driver – right down to the individual safety objectives of the various components.
The foundation of the “Safety First for Automated Driving” white paper are its 12 Guiding Principles:
- Safe Operation: How the system reacts if critical components become unstable or cease functioning
- Safety Layer: The system recognizing its limits and minimizes risk in returning control to the driver
- Operational Design Domain (ODD): The operating conditions in which the system is designed to function
- Behavior in Traffic: The system behavior needs to be easy to understand and predictable for surrounding road users
- User Responsibility: The user’s state must be suitable for a takeover procedure
- Vehicle-Initiated Handover: If the driver does not comply with a takeover request, the automated driving system must perform a maneuver to minimize risk.
- Driver-Initiated Handover: Activating and deactivating the automated driving system shall require an explicit driver’s intent
- Effects of Automation: Overall evaluation of system safety shall take automation effects on the driver into account
- Safety Assessment: Verification and validation shall be used to ensure that the safety goals are met
- Data Recording: When an event or incident is recognized, automated vehicles shall record relevant data in a manner that complies with applicable privacy laws
- Security: Steps shall be taken to protect the automated driving system from security threats
- Passive Safety: Vehicle layout shall accommodate changes to crash scenarios brought about by vehicle automation
Personally I'm not satisfied with their safety list.
I was in a crash where multiple electronic systems failed and the vehicle was not designed to manage that failure combination.
This line in their overview: "accommodate changes to crash scenarios brought about by vehicle automation" should be extended to combinations of multiple failures which I'm guessing is out of scope so far.
Potential Value Opportunities
Potential Challenges
- Overlapping regulations from multiple jurisdictions
- lack of data standards for data sharing
- industry and public-private partnerships not fully effective in coordinating improvements in safety, vehicles, traffic management etc
Candidate Solutions
Step-by-step guide for Example
sample code block