Difference between revisions of "Publications:Real-Time Communication"
From CERES
(Created page with "<div style='display: none'> == Do not edit this section == </div> {{PublicationSetupTemplate|Author=Magnus Jonsson |PID=239261 |Name=Jonsson, Magnus [magnusj] (Högskolan i Ha...") |
(No difference)
|
Latest revision as of 04:42, 26 June 2014
| Title | Real-Time Communication |
|---|---|
| Author | Magnus Jonsson |
| Year | 2006 |
| PublicationType | Book Chapter |
| Journal | |
| HostPublication | ARTES - A network for Real-Time research and graduate Education in Sweden 1997-2006 |
| DOI | |
| Conference | |
| Diva url | http://hh.diva-portal.org/smash/record.jsf?searchId=1&pid=diva2:239261 |
| Abstract | More and more real-time systems are complex and distributed systems consisting of many sub-systems that must cooperate. In other words, those sub-systems must communicate with each other and to do this, still fullling the overall system specfication, real-time communication must be supported. Moreover, real-time communication is also becoming widely needed in networks like the Internet, spanning over large distances. In for example Internet, the support for different traffic classes is often described as supporting different QoS (Quality of Service) levels and does normally include some kind of specifcation to meet real-time demands. Real-time communication often relies on some kind of scheduling like EDF (Earliest Deadline First), but there are some important differences compared to standard single-processor scheduling. First, the transmission of a packet is, in most cases, non-preemptive. The ongoing transmission, and possibly also some of the already queued messages, can then not be interrupted when a more important message (e.g., with a shorter relative deadline) arrives or is generated. Moreover, a network, instead of a single link, makes the situation much more complex and one must consider things like medium access method, topology, multiple users on multiple nodes, non-deterministic access delay etc. |
