What problem does the Timpani project aim to solve in software-defined vehicles?<\/h3>\n\n\n\n
The Timpani project addresses three key challenges in software\u2011defined vehicles.<\/p>\n\n\n\n
First, guaranteeing the end\u2011to\u2011end execution time of sequential applications.<\/strong> Many in\u2011vehicle functions are composed of multiple applications that must run sequentially within a specific time window.<\/p>\n\n\n\n For example, a rear\u2011parking alert feature involves:<\/p>\n\n\n\n <\/p>\n\n\n\n These must be executed in order and within a defined deadline. Timpani ensures this deterministic end\u2011to\u2011end scheduling behaviour.<\/p>\n\n\n\n Second, scheduling sequential applications distributed across physically separated ECUs. <\/strong>Vehicle functions are often spread across different ECUs. Timpani enables sequential scheduling even when applications are running on different ECUs, effectively allowing the entire vehicle to operate like a single integrated computer.<\/p>\n\n\n\n Third, providing CPU scheduling at the Linux container level for cloud\u2011native architectures.<\/strong> Following cloud\u2011native principles, Timpani provides scheduling at the container level, regardless of the frameworks running inside the container. Even if a container includes its own execution\u2011management framework, Timpani coordinates with it and ensures a higher level of system\u2011wide determinism.<\/p>\n\n\n\n Vehicle systems place the highest priority on safety<\/strong>. This means certain functions must be executed or monitored within strict and guaranteed time bounds. This is exactly why deterministic scheduling is essential.<\/p>\n\n\n\n At the same time, as we move toward software\u2011defined vehicles, we must also consider scalability and flexibility<\/strong>. These requirements imply that the system must allow for changes and updates over time. However, a system that operates in a fully deterministic and fixed manner typically does not allow such changes. Once change is introduced, determinism can be weakened.<\/p>\n\n\n\n To address this fundamental conflict, we believe orchestration<\/strong> is required \u2013 an approach that can dynamically manage resources, recover from issues, and adapt the system to evolving conditions without sacrificing safety. This is why we are developing the Timpani project together with the Eclipse Pullpiri<\/a> project. By combining deterministic scheduling with orchestration\u2011driven adaptability, we aim to create an SDV platform that ensures both safety requirements and cloud\u2011native flexibility.<\/p>\n\n\n\n “Together, Eclipse Pullpiri and Timpani provide a tightly integrated orchestration\u2011plus\u2011deterministic\u2011scheduling solution for software\u2011defined vehicles.” <\/em><\/p><\/blockquote><\/figure>\n<\/blockquote>\n\n\n\n Timpani has the strongest synergy with the Eclipse Pullpiri<\/a> project, to which LG Electronics is already contributing and actively developing. <\/p>\n\n\n\n While Eclipse Pullpiri determines deployment locations, manages the runtime environment and required resources for each application like K8S in cloud environments, and orchestrates applications based on vehicle conditions, Timpani focuses on ensuring that critical applications meet their execution deadlines. When a deadline miss occurs, Timpani communicates with Eclipse Pullpiri to orchestrate the affected applications. This may involve changing the deployment location, adjusting resource allocations, or, in some cases, terminating lower\u2011priority applications. Together, Eclipse Pullpiri and Timpani provide a tightly integrated orchestration\u2011plus\u2011deterministic\u2011scheduling solution for software\u2011defined vehicles.<\/p>\n\n\n\n The project is called \u201cTimpani\u201d because, just like a timpani drum in an orchestra that keeps the beat for all the other instruments, the Timpani project helps keep the timing of all workloads in the vehicle.<\/p>\n\n\n\n It makes sure everything runs on time and in sync. We learned during the Eclipse Pullpiri naming process that trademark rules make it difficult to use common words for project names. So for Timpani, we are also looking for a unique, meaningful, and contribution\u2011friendly name that avoids trademark issues.<\/p>\n\n\n\n Want to learn more about Timpani? Join the SDV Community Days<\/a> on 24-25 February in Bonn, Germany.<\/strong><\/p>\n\n\n\n\n
<\/ol>\n\n\n\n
Why are deterministic real-time scheduling and dynamic orchestration important for SDVs?<\/h3>\n\n\n\n
\n
<\/ol>\n\n\n\n
How does Timpani fit into the broader SDV and Eclipse ecosystem?<\/h3>\n\n\n\n
Why is the project called \u201cTimpani\u201d?<\/h3>\n\n\n\n
![\"\"](\"https:\/\/eclipsesdv.org\/wp-content\/uploads\/2026\/02\/lg_0158-300x200.jpg\")