W3C

Submission request to W3C

Submitted Materials

We,

, hereby submit to the Consortium the following specification, comprising the following document(s) attached hereto:

  1. Volkswagen Infotainment Web Interface protocol definition
  2. Volkswagen Infotainment Web Interface service definition: viwi.service.car
  3. Volkswagen Infotainment Web Interface service definition: viwi.service.cdn
  4. Volkswagen Infotainment Web Interface service definition: viwi.service.media
  5. Volkswagen Infotainment Web Interface service definition: viwi.service.medialibrary
  6. Volkswagen Infotainment Web Interface service definition: viwi.service.mixer

which collectively are referred to as "the Submission". We request the Submission be known as the Volkswagen Infotainment Web Interface (viwi) Submission.

Abstract

With the Volkswagen Infotainment Web Interface (viwi), applications running on an in-vehicle infotainment (IVI) system or any device connected via TCP/IP get access to the systems resources and functionality. The interface is based on web technologies. The goal using web technologies (HTTP, WebSockets) is to create a convienient API for developers on both ends, the system and the application(s). Viwi is a restful service interface, which promotes (micro) service system design patterns. At the same time, viwi utilizes standardized web security mechanisms like TLS encryption, OAuth or JWT tokens. The API is designed in a graph-like fashion to allow interconnection between services. Viwi is treating the car like a web service from an API perspective - REST extended by publish/subscribe for high frequency changes.

With the Volkswagen Infotainment Web Interface (viwi), applications running on an in-vehicle infotainment (IVI) system or any device connected via TCP/IP get access to the systems resources and functionality. The interface is based on web technologies. The goal using web technologies (HTTP, WebSockets) is to create a convienient API for developers on both ends, the system and the application(s). Viwi is a restful service interface, which promotes (micro) service system design patterns. At the same time, viwi utilized standarized web secutrity mechanisms like TLS encryption, OAuth or JWT tokens. The API is design in a graph like fashion to allow interconnection between services. Viwi is treating the car like a web service from an API perspective - REST extended by publish/subscribe for high frequency changes.

Intellectual Property Statements

Copyrights

Volkswagen AG hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any Volkswagen AG copyrights on this contribution, to copy, publish and distribute the contribution under the W3C document licenses.
Additionally, should the Submission be used as a contribution towards a W3C Activity, Volkswagen AG grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. Volkswagen AG further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.
Should the Submission not be used as a contribution towards a W3C Activity, change control of the Submission shall remain with the Submitters/Authors.

Patents

DE10 2014 201 948 A1
Zustandslose Schnittstelle zum Zugriff auf Fahrzeug-Infotainment-Funktionen
DE10 2012 020 974 A1
Vorrichtung und Verfahren zur Bereitstellung multimedialer Daten in einem Kraftfahrzeug
PCT/EP2015/052244
DATA TRANSFER METHOD, COMMUNICATIONS NETWORK, SUBSCRIBER AND VEHICLE
The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in section 5 of the 5 February 2004 W3C Patent Policy for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

Required proprietary technology

none

Suggested action

We suggest that the Consortium hold a workshop to discuss the Submission within the automotive business group

Resources

To help with this work, we expect, but do not commit, to be able to provide at least one member of the working group to the Consortium.

Contact

Inquiries from the public or press about this Submission should be directed to: patrick.bartsch@audi.de or patrick.luennemann@carmeq.com

Submitted

this (9th day of December, 2016),

Mark Beckmann


Last updated: $Date: 2017/01/04 01:46:14 $ by $Author: ted $

Philippe Le H├ęgaret, W3C