m Mobi VID2
- jim mason
- Jim Mason
Key Points
MOBI VID2 - POC to create standards
- every Tuesday meeting
- project charter is our roadmap
- use cases
- problems to address
- solution options
- standards draft and validation
use case worksheet for VID2
https://docs.google.com/spreadsheets/d/1lRwd9uHuFnFjf5v2zlXle0eBmIrKH2-KWtskLveIRNc/edit
version 2 of use case gsheet
https://docs.google.com/spreadsheets/d/1d7-H8Quhoxpux8KLn_oXytRR4KF94z208FB8tPQkT7o/edit#gid=0
References
MOBI VID2 team
chris wood - filament ewallet
divyesh jadav - ibm bc
dan bachenheimer - accenture
todd - luxoft
hans otten - autodata cto - chromedata - oem data mgr
klaus uwe roehm - bosch iot
ryan tabibian - car iq - car payments net - use hlf
johannes klepsch - bmw - chair - mobility pm
sebastian banescu - quantstamp - security - solns hlf
michael vo - mobi cto
joe bannon - kar global - dealer markets
alan gordon - ford vc - tech lead ai
Key Concepts
OBD2 diagnostic codes
https://www.outilsobdfacile.com/data-trouble-code-obd2.php
As the list of generic OBD codes is not always sufficient, manufacturers can add as many of their own codes as they need.
The last 3 digits correspond to an incremented number (purple digits).
This may be a hexadecimal number (i.e. from 0 to 9 + from A to F). For P family codes, sub-families have been defined using the 1st digit (in this example the "3"):
- 0 , 1 and 2: for the air/fuel mixture
- 3 : for the ignition system
- 4 : for checking auxiliary emissions
- 5 : for engine idling
- 6 : for the onboard computer and ancillary outputs
- 7, 8 and 9: for the transmission (gearbox)
- A, B and C : for hybrid propulsion
These OBD codes were standardized using SAE J2012 and ISO 15031-6 standards which, to our knowledge, contain about 11 000 definitions in the most recent version.
IEEE specs
https://www.globalspec.com/MyGlobalSpec/NewProfile
Define Visual Appearance Standards
Every appraisal or inspection includes visual appearance evaluations
2 Schemas - header and detail
Automated Visual Appearance Solutions
Paint meter thickness - shows potential useful life of an existing body panel before repainting required
Collision industry standards on visual appearance
CIECA - Collision Industry E Commerce Assoc
Repair diagnostic stds by area
https://www.cieca.com/info.php?pnum=45906088ac2fac
The purpose of this report is to begin committee work to define and publish the repair steps from loss initiation to final delivery and documentation. The committee will determine, define, and standardize the event points that are required within the process
Vehicle Diagnostic and Imaging
https://www.cieca.com/info.php?pnum=55906088ac7d59
The Vehicle Damage & Imaging committee is chartered with developing and maintaining the next generation XML standards that will be used by the collision industry in the appraisal of and/or restoration of a vehicle that has incurred a loss. All standards will be based on the BMS (Business Message Specification) developed by CIECA
Repair Industry Segments
- VDI Provider - A Company whose main businesses concern is providing vehicle damage repairs to the collision repair industry. The provider can perform vehicle damage repairs solely or can coordinate repair operations on a vehicle in conjunction with conventional repairs.
- Damage Appraisers - Any entity whose role is to estimate or appraise vehicle damage and/or record and process appraisal information.
- Information Technology Providers – Any entity that develops and/or maintains applications and/or services related to damage appraisals, appraisal data communications and/or appraisal data consolidation.
- Data Recipients - Any company that utilizes vehicle damage appraisals, vehicle damage data communications and/or vehicle damage data.
Participants
- Insurers
- Repairers
- Glass Vendors
- Appraisers
- Consumers
- Information Providers
- Paint Vendors
- Sublet Repair Vendors
industry ratings etc
Potential Value Opportunities
MOBI VID2 solution models
Preferences report out○
1 >> one chain everyone plugs into○
1a >> we spin up chains from the protocols and OEMs plug into as you see fit insub-groups○
2 >> OEMs build their own solution with interoperability
Potential Challenges
BIO - Blockchain Interoperability
VID2 requires multiple blockchains on different protocols that can execute:
- a lookup transaction - gets information from remote
- an update transaction - updates one or both nodes ( requestor and responder )
- a spend transaction - updates one or both nodes ( requestor and responder ) with a token spend ( actual or virtual )
non-functional requirements include: scale, performance, automated configuration, identity validation, scope ( session or transaction ), duration, transaction rules, authorization, audits
Blockchain Interop Transaction Use Case Types
- Oracle - read-only access to another blockchain from a first blockchain
- Standard Transaction - eg ship a vehicle from one blockchain to another
- Spend Transaction - eg buy something from one blockchain on another blockchain involving payment or future payment
Steps to connect 2 different blockchains
PRCT
- Protocol Support - connect 2 different types of blockchains using standard service interfaces implementing Hub, Adapter or Bridge patterns from a bc protocol adapter repo
- Register a blockchain on another chain
- Connect to a chain
- Transactions
Tasks to connect to 2 different blockchains
BIO metadata definitions
BIO needs chain registries for a purpose to find service chains
BIO needs service chains to manage directory of approved client chains
BIO needs a common protocol for BIO - tcp sockets, https web sockets or ???
BIO depends on decentralized ids ( self sovreign ids ) and proxy ids, wallets etc
BIO needs common metadata for: contract, authorizations, identities, transactions, mapping, contract management, BIO requests, BIO grants ( similar to Kerberos )
BIO create a connection definition - flow
bc.a issues a connection.request to bc.b OR bc.b creates a connection request for bc.a to bc.b for a smart contract transaction sub set for a group
bc.b reviews the request and responds with: declines or grants an approval for a duration ( transaction, session duration or permanent )
bc.b issues connection certificates for specified roles and contracts to other chains with an expiration and duration
bc.a creates API for the other chain's contract context
map the API to existing local chain services
save the BIO definition
BIO issue lookup transaction request
BIO issue an update request
BIO issue a spend request
Candidate Solutions
Compare IBC protocol
Interblockchain Communication (IBC) is a TCP/IP-like messaging protocol for blockchains.
Meetings
Step-by-step guide for Example
sample code block