Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

6.1.1 Overview and objective of project

W3C first explored the impact of the Open Web Platform on the automotive industry at the November 2012 Web and Automotive Workshop. Participants discussed how location-based services, enhanced safety, entertainment and integration of social networking will benefit drivers and passengers. Since then, the Business and Working Groups have kept the conversation around standardization and specifications, through regular meetings with stakeholders. The Automotive Working Group develops APIs to expose vehicle data and information from an automotive network bus(es) (eg. MOST and CAN). The specification is broken into consists of two parts:

  1. Vehicle Information Specification containing durable, unchanging access methods for obtaining vehicle information;
  2. Vehicle Data Specification to specify agreed upon standardized data elements as well as the method for extending data elements to OEM specific elements.

Image RemovedImage Added

 

 

 

The W3C Automotive Specifications can be realized using follows a client server architecture. The W3C automotive compliant web clients "connect" to a server W3C Vehicle Server using secure websocket connection (wss://).

After the initial connection is established, the client is "Authorized" by the server.

The Vehicle Signal Server abstracts the communications with the underlying automotive networks (like CAN, MOST etc), and presents a simple set of Web API for the clients. Beyond this, the interactions between client and server follow a Request/Response model.

After the initial connection is established, the client is "Authorized" by the server.

The supported methods are : 

  1. Authorize
  2. GET
  3. SET
  4. Subscribe
  5. Unsubscribe
  6. getVSS - helps provide only a subset of the information.

The message format is JSON. The "Authorize" method helps the server to provide secure access to vehicle data based on 

Below is a simple flow diagram that explains the communication between W3C automotive clients and servers.

 

Image Added

 

As the name implies, the W3C Vehicle Data Specification The getVSS API provides a JSON payload representation of the entire set of VSS attributes accessible to the client.

...