10th annual workshop on
Operating Systems Platforms for Embedded Real-Time applications
July 8, 2014. Madrid, SpainMay 2, 2014:
Submission Deadline
(Extended)
May 23, 2014:
Acceptance Notification
June 13, 2014:
Submission of camera-ready papers
July 8, 2014:
Workshop
July 9-11,
2014:
ECRTS Conference
Björn B. Brandenburg
Max
Planck Institute for Software Systems
Shinpei Kato
Nagoya University, Japan
Jim Anderson
University of North Carolina
Andrea Bastoni
SYSGO AG
Robert Kaiser
Hochschule RheinMain University of Applied Sciences
Gabriel Parmer
George Washington University
Wolfgang Mauerer
Siemens
Gernot Heiser
NICTA
Sebastian Fischmeister
University of Waterloo
Daniel Lohmann
Friedrich-Alexander-Universitat Erlangen-Nurnberg
Michael Roitzsch
Technical University of Dresden
Giuseppe Lipari
Scuola Superiore Sant'Anna
Tuesday, July 8th 2014 | |
8:00-8:30 | Registration |
8:30-10:00 |
Keynote Talk by Paolo Gai (CEO, Evidence S.R.L.): Title: Open-source and Real-time in Automotive Systems: (not only) Linux, (not only) AUTOSAR Abstract: The talk will consider the current status of open-source and real-time in automotive systems, starting from the history of the open-source real-time OS ERIKA Enterprise. The current trends will also be considered including the usage of open-source Linux systems and the integration and safety qualification issues on modern automotive multicores. |
10:00-10:30 | Coffee Break |
10:30-12:00 | Session 1: RTOS Design and Implementation I
|
12:00-13:30 | Lunch |
13:30-15:00 | Session 2: Mixed-Criticality Systems
|
15:00-15:30 | Coffee Break |
15:30-16:30 | Session 3: RTOS Design and Implementation II
|
16:30-18:00 | Discussion and Closing Thoughts Open-ended discussion among all workshop participants. Suggested topics include:
|
Developers of embedded Real-Time Operating Systems (RTOS) are faced with many challenges arising from two opposite needs: the need for extreme resource usage optimization (processor, energy, network bandwidth, etc.) on the one hand, and an the other hand also increasing demands for scalability, flexibility, isolation, adaptivity, reconfigurability, predictability, serviceability, and certifiability. Further, while special-purpose RTOSs continue to be used in many small embedded applications, real-time services are increasingly introduced and used in general-purpose operating systems, and market pressures continue to blur the lines between the two formerly distinct classes of operating systems. Notable examples are the various flavors of real-time Linux that provide support to time-sensitive applications, as well as the emergence of commercial and open-source real-time hypervisors.
This workshop is intended as a forum for researchers and practitioners working on (and with) RTOSs and middlewares to discuss the recent advances in RTOS and middleware technology and the challenges that lie ahead. The workshop will consist of two categories of submitted papers:
Both types of papers have a page limit of six pages (+ optionally up to two pages may be used for an appendix), including references.
Additionally, the workshop will feature invited presentations and publications to aid in creating a lively, interactive forum. Upon acceptance, a complete version of the paper must be prepared and submitted. All papers will be made available to all participants a week before the workshop to facilitate discussions.
Submitted papers should follow the IEEE conference format (2 columns, 10 pt, single-line spacing) and should not exceed six pages (plus optionally a two pages appendix). Papers may be submitted in either PDF or Postscript format. The papers will be reviewed by the workshop program committee. All accepted papers will be made available to all participants one week before the workshop so that contributions can be examined prior to the event.
LaTeX and MS Word templates may be found at:
http://www.ieee.org/conferences_events/conferences/publishing/templates.html
Submission website:
https://ospert14.mpi-sws.org/
We want to encourage scientific reproducibility, and discourage redundant work within the community. Thus, code relevant to each submission must be publicly available, and a link to it included in the submission. Exceptions are possible for papers discussing proprietary systems. If you require an exception, please contact the chairs. If your submission does not include an implementation, there are no such restrictions.
By submitting a paper, the authors agree and confirm that: