JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
Some initial collection of topics to cover, concerns and challenges, and how to structure the definition of the "big picture" Vehicle Data reference architecture.
look at this diagram
What: Draw and list technical components that may be involved in the architecture. This includes both hardware and software components.
...
The order of definition is not fixed here and it is a challenge. The technical architecture is basically the intended end result but at the same time a rough architecture needs to be drawn to identify the parts we intend to talk about (data flows, protocols, actors, and so on).
Therefore, we likely need to iterate over all of these angles of attack.
What: List typical hardware and software components. This may be quite abstract at times (e.g. the exact hardware of course differs) but in that case list the assumed type of component.
--> HW / Operating System / Software stack
(likely not very strictly defined -- lots of variability and continuous change)
Example of system parts
- Vehicle ECUs
- Vehicle gateway ECUs
- OEM intermediate servers
- Neutral server
- "Developer" endpoints (Web services and/or end-user devices?)
- Final app. What are the developer final products, i.e. the outcome of 3rd party development? This could be for example web services, or apps on popular smartphones.
What: A block diagram containing interacting technical systems (and consequently interacting actors) focusing on the data flow links between them.
This is to identify primarily the links between technical systems that need a defined communication protocol, (and preceeding that of course quality requirements and similar input).
What: Based on the block diagram, and performance/quality/content requirements for each link, propose appropriate data protocol standards.
The choice may be affected also by the communicating software components
...
For each link in data flow architecture
- (Specify actors involved)
- Identify data set (limitations, + non-functional requirements)
- Identify data protocol
What: Define the different categories of 3rd party use-cases and the different technical needs for consuming the data.
...
Protocol for Vehicle -> OEM server
1) (W3C Gen 2)
2) Other? MQTT, etc...
3) Are those proprietary protocols (i.e. unspecified in this project)?
...