This document defines the work activities, deliverables and timeline to develop and implement a complete Software Over the Air system to upload, manage, queue, transmit, validate, install, and report software images on vehicles.
As a complete system, it will include implementation of a server, definition of an API to interact with the server, creation of a web interface to manage the software updates and a client side application / service to interface with the update server.
Project Background
Today, GENIVI compliance defines basic components for Software Management and Download Management, but has no end-to-end architecture to manage the software installed and running on a GENIVI-compliant system. Since management of software updates is a mandatory feature of a production IVI system, SOTA is considered to be non-differentiate functionality and therefore a valuable area for collaboration between GENIVI members.
This SOW is based heavily on a Design Requirements Document from Jaguar Land Rover, which itself was based on JLR's experience with SOTA systems and projects. The project has clear overlaps with Networking and Systems Infrastructure, and complements the existing Remote Vehicle Interaction work published by JLR.
Objectives
The objective of this project is to develop and demonstrate an end-to-end system for Software Over the Air management. Based on the completed project, any distributor of IVI systems should be able to quickly implement a basic SOTA system that meets their production needs.
Name
|
Company
|
Role
|
E-mail
|
Telephone
|
Magnus Feuer
|
JLR
|
OEM
|
mfeuer@jaguarlandrover.com
|
+1 949 294 7871
|
Arthur Taylor
|
ATS
|
SI Member
|
arthur@advancedtelematic.com
|
+49 30 959997540
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Architecture 1.1Overview
The SOTA system domain and general architecture is described in the figure below
Figure 1. General Architecture. Green boxes are covered by this Statement of Work.
The SOTA requirements describe a system that is as thin as possible in order to ease integration into existing vehicle and backend environments. Large parts of package management, logistics and installation procedures are outsourced to external components.
The SOTA Server, consisting both of the Core Server and the External resolver, retains enough information to know what is needed in installed vehicle hardware components and prerequisite dependent-on packages for a package to be installed.
The SOTA Client resides on the vehicle and interacts with the Genivi Software Management system.
Share with your friends: |