MXC Data Submission Concept MXC E-Vehicle C.A.R.E. Project
Time to read
Use Case

MXC Data Submission Concept MXC E-Vehicle C.A.R.E. Project

The MXC C.A.R.E. (Certified Auto Reporting Engine) Project is revolutionizing how electric vehicles can improve efficiency, efficacy, and energy usage based on individual driver behavior.

The development team at the MXC Foundation sees this innovation as the future of the automotive industry. The authenticated data history related to an electric vehicle benefits driver and automobile safety and efficiency by sourcing data transmission feeds between the vehicle, charging station, and relevant stakeholders. Ultimately, this improves and allocates a unique and specific driving experience based on the automobile’s specific driver-induced behavior.

The MXC Foundation’s C.A.R.E. Project unlocks the potential for electric vehicles to receive better service and more accurate in- and output, preventing secondary markets from fraudulent activities. Moreover, it allows vehicle owners to travel more safely, with ease of mind thanks to added functionality and security layers. The data transfer from charging stations allows the vehicle to teach the cloud how its driver acts and reacts in certain driving conditions, making the entire experience smarter, based on each user’s individual movements and preferences. Responding to the individual driver and how they use the car allows for increased energy efficiency, automated automobile reaction, and improved response times, as well as pre-determined and predictive actions based on driver behavior.

Vehicular Blockchain Profile (VBP)

Each vehicle is equipped with a unique VBP. The VBP is a public-facing blockchain profile that allows car manufacturers, service providers, and users who have the right address of the VBP to look at the recorded data associated with the VBP. The recorded data is the following:

  • Total kilometers/miles driven
  • Average speed segmented per trip (between the time when the engine starts and when the engine stops)
  • Usage data
  • Trauma data such as water damage, fire damage, impact damage, tire pressure, tire wear and tear
  • Braking data, acceleration data, how often turns are made (This can assist driver safety to ensure the automobile learns when a driver needs a break to ensure they are well-rested and allows for fewer gear changes to preserve the gearbox for inner-city driving.)
  • Travel data
  • Optimization data
  • Registered license plate
  • Trip details (location)

Using MXC’s MXProtocol, this data is encrypted and transmitted to the VBP.

Obfuscation Layer (L2O)

Within the VBP, the L2O exists to ensure that the users are able to keep sensitive data away from prying eyes. For example, trip details and location data may not be a data set that vehicle owners wish to share with others. In this case, the owner can opt to have certain data sets pass through the L2O while the automobile is immobilized at a charging station. Data is sent via the MXProtocol within the free charging station, and the automobile communicates this data with the charging station.

Once a data set has been passed through the L2O, that data set is unreadable due to end-to-end encryption. To solve the encryption key, the owner must share the encryption master key with the specific parties they want to share this information with.

The data set passed through the L2O is stored in the data vault. The driver may choose to select to share this data with the automobile manufacturer, which will then allow for individual and matured data learnings to improve the individual’s personal driving experiences. The data that can be stored in the data vault can come from the VBP or external input. This allows drivers to enter their insurance details and registration papers into the data vault, and protect it with the L2O.

MXC Vehicular Data Hub Signature Management Key (SIGMA)

The owner of the vehicle is given the SIGMA once ownership has been transferred. The SIGMA has the authority to unlock the L2O and determine who gets access to the data that has been passed through the L2O.

The SIGMA is also the token of ownership for the vehicle. In the case of a shared vehicle, the holder of the SIGMA can create SIGMA-X to provide a time-limited “child” SIGMA. Once that time passes, SIGMA-X is rendered obsolete.

VBP and Charging Stations

When the vehicle is parked at a designated charging station, the owner (holder of the SIGMA or SIGMA-X) has the option to transmit the data stored on the VBP to the data collection node at the charging station. The data transmission takes place within a matter of seconds, thanks to MXC’s MXProtocol.

In return, the charging station rewards the owner with MXC tokens. These tokens are added to the wallet balance of the SIGMA holder (not SIGMA-X) and can be withdrawn and sold for monetary value.

This creates a value-adding loop. Charging stations collect optimization data and other relevant information for all the vehicles that use it in order to become a data hub of usage information that can feed into providing better updates and services for the vehicle owners. In turn, the vehicle owners receive some monetary benefits while also enjoying improved services in the near future.

VBP and Service Centers

One of the main issues many drivers have at service centers is that drivers are often unsure about the previous service records or other pertinent details. The VBP fixes precisely this issue.

When the vehicle is brought into the service center, mechanics can simply look up the VBP of the vehicle and see all the relevant information. If the mechanic requires more sensitive data, a request can be made in which the holder of SIGMA can grant temporary access to the data set filtered through the L2O.

Once the service has been completed, the mechanic uploads service completion certificates to the VBP using MXProtocol. This enables the vehicle to go to any service station at any time, without the owner having to worry about finding some service completion certificate that was issued years ago.

VBP and Secondary Market

The VBP is the most reliable record of a vehicle’s history, since data going into the VBP cannot be erased or edited. Only new data input is allowed.

Potential purchasers of used electric vehicles can rely on the VBP to provide the most accurate overview of the vehicle’s usage data, along with any accidents and provided services. This ensures that they are protected from fraudulent parties attempting to hide past incidents to ask for higher prices on a used vehicle.

This boosts the brand value of the vehicle, leading to higher demand within the secondary market. As a result, it encourages drivers to seek out the particular brand when purchasing the vehicle for the first time, as drivers can benefit from a relatively higher secondary market valuation when selling the car.

Transferring Ownership

Once the formal paperwork has been completed, the holder of the SIGMA transfers it to the new owner. No more than one person can hold the SIGMA. Transferring of the SIGMA triggers all other SIGMA-X to be rendered obsolete for security purposes.

Vehicle Sharing

If the vehicle’s owner opts for it, SIGMA and SIGMA-X can be linked to vehicle access. The SIGMA or SIGMA-X holder can signal the unlock mechanism embedded within the car door through MXProtocol. This allows for easy vehicle sharing, in which the owner (holder of SIGMA) can allow others to use the vehicle by granting SIGMA-X, and just as easily revoke access by rendering SIGMA-X obsolete and effectively locking out unauthorized individuals from accessing the vehicle.

Easy Control and Access

The steps mentioned above are integrated into a mobile application with an intuitive UI that empowers users to have fuller control over their vehicles, vehicular data, and how others may interact with their vehicle. Users can also use the mobile application to show the data stored in the data vault through the L2O, allowing them to always carry a digital copy of their insurance and registration.