Remote Diagnostics over IP (DoIP)

From WICE Wiki v2.89
Revision as of 12:30, 13 April 2021 by Mathias (talk | contribs) (Created page with "The Remote DoIP concept makes it possible to communicate with a WICE-equipped remote vehicle using the DoIP protocol, much in the same way as if connecting directly to the veh...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The Remote DoIP concept makes it possible to communicate with a WICE-equipped remote vehicle using the DoIP protocol, much in the same way as if connecting directly to the vehicle’s Ethernet interface.

Remote DoIP components

The WICE Remote DoIP system consists of the following components:

  1. The DoIP daemon doipd running in the WCU. This software component relays DoIP communication between vehicle and the back-end. It also takes care of waking up the vehicle when communication requests are pending.
  2. The DoIP proxy gateway doipp running in the WICE Gateway (WGW) back-end server infrastructure. The proxy multiplexes DoIP connections and relays traffic between connected vehicles and client interfaces.
  3. The DoIP client interface doipc, running in a Linux server machine at the end users’ premises. The client applications (e.g. testers) can when connected to the same Ethernet LAN as the doipc machine see Vehicle Announcements from the currently connected and properly configured vehicles, and connect a DoIP TCP communication session, whereupon data will be relayed between tester and vehicle until the session is terminated.