<!--{{{-->
<link rel='alternate' type='application/rss+xml' title='RSS' href='index.xml' />
<!--}}}-->
Background: #fff
Foreground: #000
PrimaryPale: #8cf
PrimaryLight: #18f
PrimaryMid: #04b
PrimaryDark: #014
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #db4
SecondaryDark: #841
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88
/*{{{*/
body {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}

a {color:[[ColorPalette::PrimaryMid]];}
a:hover {background-color:[[ColorPalette::PrimaryMid]]; color:[[ColorPalette::Background]];}
a img {border:0;}

h1,h2,h3,h4,h5,h6 {color:[[ColorPalette::SecondaryDark]]; background:transparent;}
h1 {border-bottom:2px solid [[ColorPalette::TertiaryLight]];}
h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}

.button {color:[[ColorPalette::PrimaryDark]]; border:1px solid [[ColorPalette::Background]];}
.button:hover {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border-color:[[ColorPalette::SecondaryMid]];}
.button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}

.header {background:[[ColorPalette::PrimaryMid]];}
.headerShadow {color:[[ColorPalette::Foreground]];}
.headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
.headerForeground {color:[[ColorPalette::Background]];}
.headerForeground a {font-weight:normal; color:[[ColorPalette::PrimaryPale]];}

.tabSelected {color:[[ColorPalette::PrimaryDark]];
	background:[[ColorPalette::TertiaryPale]];
	border-left:1px solid [[ColorPalette::TertiaryLight]];
	border-top:1px solid [[ColorPalette::TertiaryLight]];
	border-right:1px solid [[ColorPalette::TertiaryLight]];
}
.tabUnselected {color:[[ColorPalette::Background]]; background:[[ColorPalette::TertiaryMid]];}
.tabContents {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::TertiaryPale]]; border:1px solid [[ColorPalette::TertiaryLight]];}
.tabContents .button {border:0;}

#sidebar {}
#sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
#sidebarOptions .sliderPanel a {border:none;color:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]]; background:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::Background]];}

.wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid [[ColorPalette::PrimaryMid]];}
.wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
.wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
.wizardStep {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];
	border:1px solid [[ColorPalette::PrimaryMid]];}
.wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
.wizardFooter {background:[[ColorPalette::PrimaryPale]];}
.wizardFooter .status {background:[[ColorPalette::PrimaryDark]]; color:[[ColorPalette::Background]];}
.wizard .button {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
	border-color:[[ColorPalette::SecondaryPale]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryPale]];}
.wizard .button:hover {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Background]];}
.wizard .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::Foreground]]; border: 1px solid;
	border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}

.wizard .notChanged {background:transparent;}
.wizard .changedLocally {background:#80ff80;}
.wizard .changedServer {background:#8080ff;}
.wizard .changedBoth {background:#ff8080;}
.wizard .notFound {background:#ffff80;}
.wizard .putToServer {background:#ff80ff;}
.wizard .gotFromServer {background:#80ffff;}

#messageArea {border:1px solid [[ColorPalette::SecondaryMid]]; background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]];}
#messageArea .button {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::SecondaryPale]]; border:none;}

.popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid [[ColorPalette::TertiaryMid]];}

.popup {background:[[ColorPalette::TertiaryPale]]; color:[[ColorPalette::TertiaryDark]]; border-left:1px solid [[ColorPalette::TertiaryMid]]; border-top:1px solid [[ColorPalette::TertiaryMid]]; border-right:2px solid [[ColorPalette::TertiaryDark]]; border-bottom:2px solid [[ColorPalette::TertiaryDark]];}
.popup hr {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
.popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
.popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:active {background:[[ColorPalette::SecondaryPale]]; color:[[ColorPalette::Foreground]]; border: none;}
.popupHighlight {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
.listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}

.tiddler .defaultCommand {font-weight:bold;}

.shadow .title {color:[[ColorPalette::TertiaryDark]];}

.title {color:[[ColorPalette::SecondaryDark]];}
.subtitle {color:[[ColorPalette::TertiaryDark]];}

.toolbar {color:[[ColorPalette::PrimaryMid]];}
.toolbar a {color:[[ColorPalette::TertiaryLight]];}
.selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
.selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}

.tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]]; background-color:[[ColorPalette::TertiaryPale]];}
.selected .tagging, .selected .tagged {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid [[ColorPalette::TertiaryMid]];}
.tagging .listTitle, .tagged .listTitle {color:[[ColorPalette::PrimaryDark]];}
.tagging .button, .tagged .button {border:none;}

.footer {color:[[ColorPalette::TertiaryLight]];}
.selected .footer {color:[[ColorPalette::TertiaryMid]];}

.error, .errorButton {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Error]];}
.warning {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryPale]];}
.lowlight {background:[[ColorPalette::TertiaryLight]];}

.zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px solid [[ColorPalette::TertiaryMid]];}

.imageLink, #displayArea .imageLink {background:transparent;}

.annotation {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border:2px solid [[ColorPalette::SecondaryMid]];}

.viewer .listTitle {list-style-type:none; margin-left:-2em;}
.viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
.viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}

.viewer table, table.twtable {border:2px solid [[ColorPalette::TertiaryDark]];}
.viewer th, .viewer thead td, .twtable th, .twtable thead td {background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
.viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid [[ColorPalette::TertiaryDark]];}

.viewer pre {border:1px solid [[ColorPalette::SecondaryLight]]; background:[[ColorPalette::SecondaryPale]];}
.viewer code {color:[[ColorPalette::SecondaryDark]];}
.viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::TertiaryDark]];}

.highlight, .marked {background:[[ColorPalette::SecondaryLight]];}

.editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
.editor textarea {border:1px solid [[ColorPalette::PrimaryMid]]; width:100%;}
.editorFooter {color:[[ColorPalette::TertiaryMid]];}
.readOnly {background:[[ColorPalette::TertiaryPale]];}

#backstageArea {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::TertiaryMid]];}
#backstageArea a {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstageArea a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; }
#backstageArea a.backstageSelTab {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
#backstageButton a {background:none; color:[[ColorPalette::Background]]; border:none;}
#backstageButton a:hover {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstagePanel {background:[[ColorPalette::Background]]; border-color: [[ColorPalette::Background]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]];}
.backstagePanelFooter .button {border:none; color:[[ColorPalette::Background]];}
.backstagePanelFooter .button:hover {color:[[ColorPalette::Foreground]];}
#backstageCloak {background:[[ColorPalette::Foreground]]; opacity:0.6; filter:alpha(opacity=60);}
/*}}}*/
/*{{{*/
* html .tiddler {height:1%;}

body {font-size:.75em; font-family:arial,helvetica; margin:0; padding:0;}

h1,h2,h3,h4,h5,h6 {font-weight:bold; text-decoration:none;}
h1,h2,h3 {padding-bottom:1px; margin-top:1.2em;margin-bottom:0.3em;}
h4,h5,h6 {margin-top:1em;}
h1 {font-size:1.35em;}
h2 {font-size:1.25em;}
h3 {font-size:1.1em;}
h4 {font-size:1em;}
h5 {font-size:.9em;}

hr {height:1px;}

a {text-decoration:none;}

dt {font-weight:bold;}

ol {list-style-type:decimal;}
ol ol {list-style-type:lower-alpha;}
ol ol ol {list-style-type:lower-roman;}
ol ol ol ol {list-style-type:decimal;}
ol ol ol ol ol {list-style-type:lower-alpha;}
ol ol ol ol ol ol {list-style-type:lower-roman;}
ol ol ol ol ol ol ol {list-style-type:decimal;}

.txtOptionInput {width:11em;}

#contentWrapper .chkOptionInput {border:0;}

.externalLink {text-decoration:underline;}

.indent {margin-left:3em;}
.outdent {margin-left:3em; text-indent:-3em;}
code.escaped {white-space:nowrap;}

.tiddlyLinkExisting {font-weight:bold;}
.tiddlyLinkNonExisting {font-style:italic;}

/* the 'a' is required for IE, otherwise it renders the whole tiddler in bold */
a.tiddlyLinkNonExisting.shadow {font-weight:bold;}

#mainMenu .tiddlyLinkExisting,
	#mainMenu .tiddlyLinkNonExisting,
	#sidebarTabs .tiddlyLinkNonExisting {font-weight:normal; font-style:normal;}
#sidebarTabs .tiddlyLinkExisting {font-weight:bold; font-style:normal;}

.header {position:relative;}
.header a:hover {background:transparent;}
.headerShadow {position:relative; padding:4.5em 0 1em 1em; left:-1px; top:-1px;}
.headerForeground {position:absolute; padding:4.5em 0 1em 1em; left:0; top:0;}

.siteTitle {font-size:3em;}
.siteSubtitle {font-size:1.2em;}

#mainMenu {position:absolute; left:0; width:10em; text-align:right; line-height:1.6em; padding:1.5em 0.5em 0.5em 0.5em; font-size:1.1em;}

#sidebar {position:absolute; right:3px; width:16em; font-size:.9em;}
#sidebarOptions {padding-top:0.3em;}
#sidebarOptions a {margin:0 0.2em; padding:0.2em 0.3em; display:block;}
#sidebarOptions input {margin:0.4em 0.5em;}
#sidebarOptions .sliderPanel {margin-left:1em; padding:0.5em; font-size:.85em;}
#sidebarOptions .sliderPanel a {font-weight:bold; display:inline; padding:0;}
#sidebarOptions .sliderPanel input {margin:0 0 0.3em 0;}
#sidebarTabs .tabContents {width:15em; overflow:hidden;}

.wizard {padding:0.1em 1em 0 2em;}
.wizard h1 {font-size:2em; font-weight:bold; background:none; padding:0; margin:0.4em 0 0.2em;}
.wizard h2 {font-size:1.2em; font-weight:bold; background:none; padding:0; margin:0.4em 0 0.2em;}
.wizardStep {padding:1em 1em 1em 1em;}
.wizard .button {margin:0.5em 0 0; font-size:1.2em;}
.wizardFooter {padding:0.8em 0.4em 0.8em 0;}
.wizardFooter .status {padding:0 0.4em; margin-left:1em;}
.wizard .button {padding:0.1em 0.2em;}

#messageArea {position:fixed; top:2em; right:0; margin:0.5em; padding:0.5em; z-index:2000; _position:absolute;}
.messageToolbar {display:block; text-align:right; padding:0.2em;}
#messageArea a {text-decoration:underline;}

.tiddlerPopupButton {padding:0.2em;}
.popupTiddler {position: absolute; z-index:300; padding:1em; margin:0;}

.popup {position:absolute; z-index:300; font-size:.9em; padding:0; list-style:none; margin:0;}
.popup .popupMessage {padding:0.4em;}
.popup hr {display:block; height:1px; width:auto; padding:0; margin:0.2em 0;}
.popup li.disabled {padding:0.4em;}
.popup li a {display:block; padding:0.4em; font-weight:normal; cursor:pointer;}
.listBreak {font-size:1px; line-height:1px;}
.listBreak div {margin:2px 0;}

.tabset {padding:1em 0 0 0.5em;}
.tab {margin:0 0 0 0.25em; padding:2px;}
.tabContents {padding:0.5em;}
.tabContents ul, .tabContents ol {margin:0; padding:0;}
.txtMainTab .tabContents li {list-style:none;}
.tabContents li.listLink { margin-left:.75em;}

#contentWrapper {display:block;}
#splashScreen {display:none;}

#displayArea {margin:1em 17em 0 14em;}

.toolbar {text-align:right; font-size:.9em;}

.tiddler {padding:1em 1em 0;}

.missing .viewer,.missing .title {font-style:italic;}

.title {font-size:1.6em; font-weight:bold;}

.missing .subtitle {display:none;}
.subtitle {font-size:1.1em;}

.tiddler .button {padding:0.2em 0.4em;}

.tagging {margin:0.5em 0.5em 0.5em 0; float:left; display:none;}
.isTag .tagging {display:block;}
.tagged {margin:0.5em; float:right;}
.tagging, .tagged {font-size:0.9em; padding:0.25em;}
.tagging ul, .tagged ul {list-style:none; margin:0.25em; padding:0;}
.tagClear {clear:both;}

.footer {font-size:.9em;}
.footer li {display:inline;}

.annotation {padding:0.5em; margin:0.5em;}

* html .viewer pre {width:99%; padding:0 0 1em 0;}
.viewer {line-height:1.4em; padding-top:0.5em;}
.viewer .button {margin:0 0.25em; padding:0 0.25em;}
.viewer blockquote {line-height:1.5em; padding-left:0.8em;margin-left:2.5em;}
.viewer ul, .viewer ol {margin-left:0.5em; padding-left:1.5em;}

.viewer table, table.twtable {border-collapse:collapse; margin:0.8em 1.0em;}
.viewer th, .viewer td, .viewer tr,.viewer caption,.twtable th, .twtable td, .twtable tr,.twtable caption {padding:3px;}
table.listView {font-size:0.85em; margin:0.8em 1.0em;}
table.listView th, table.listView td, table.listView tr {padding:0 3px 0 3px;}

.viewer pre {padding:0.5em; margin-left:0.5em; font-size:1.2em; line-height:1.4em; overflow:auto;}
.viewer code {font-size:1.2em; line-height:1.4em;}

.editor {font-size:1.1em;}
.editor input, .editor textarea {display:block; width:100%; font:inherit;}
.editorFooter {padding:0.25em 0; font-size:.9em;}
.editorFooter .button {padding-top:0; padding-bottom:0;}

.fieldsetFix {border:0; padding:0; margin:1px 0px;}

.zoomer {font-size:1.1em; position:absolute; overflow:hidden;}
.zoomer div {padding:1em;}

* html #backstage {width:99%;}
* html #backstageArea {width:99%;}
#backstageArea {display:none; position:relative; overflow: hidden; z-index:150; padding:0.3em 0.5em;}
#backstageToolbar {position:relative;}
#backstageArea a {font-weight:bold; margin-left:0.5em; padding:0.3em 0.5em;}
#backstageButton {display:none; position:absolute; z-index:175; top:0; right:0;}
#backstageButton a {padding:0.1em 0.4em; margin:0.1em;}
#backstage {position:relative; width:100%; z-index:50;}
#backstagePanel {display:none; z-index:100; position:absolute; width:90%; margin-left:3em; padding:1em;}
.backstagePanelFooter {padding-top:0.2em; float:right;}
.backstagePanelFooter a {padding:0.2em 0.4em;}
#backstageCloak {display:none; z-index:20; position:absolute; width:100%; height:100px;}

.whenBackstage {display:none;}
.backstageVisible .whenBackstage {display:block;}
/*}}}*/
/***
StyleSheet for use when a translation requires any css style changes.
This StyleSheet can be used directly by languages such as Chinese, Japanese and Korean which need larger font sizes.
***/
/*{{{*/
body {font-size:0.8em;}
#sidebarOptions {font-size:1.05em;}
#sidebarOptions a {font-style:normal;}
#sidebarOptions .sliderPanel {font-size:0.95em;}
.subtitle {font-size:0.8em;}
.viewer table.listView {font-size:0.95em;}
/*}}}*/
/*{{{*/
@media print {
#mainMenu, #sidebar, #messageArea, .toolbar, #backstageButton, #backstageArea {display: none !important;}
#displayArea {margin: 1em 1em 0em;}
noscript {display:none;} /* Fixes a feature in Firefox 1.5.0.2 where print preview displays the noscript content */
}
/*}}}*/
<!--{{{-->
<div class='header' macro='gradient vert [[ColorPalette::PrimaryLight]] [[ColorPalette::PrimaryMid]]'>
<div class='headerShadow'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
</div>
<div class='headerForeground'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
</div>
</div>
<div id='mainMenu' refresh='content' tiddler='MainMenu'></div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
</div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
</div>
<!--}}}-->
<!--{{{-->
<div class='toolbar' macro='toolbar [[ToolbarCommands::ViewToolbar]]'></div>
<div class='title' macro='view title'></div>
<div class='subtitle'><span macro='view modifier link'></span>, <span macro='view modified date'></span> (<span macro='message views.wikified.createdPrompt'></span> <span macro='view created date'></span>)</div>
<div class='tagging' macro='tagging'></div>
<div class='tagged' macro='tags'></div>
<div class='viewer' macro='view text wikified'></div>
<div class='tagClear'></div>
<!--}}}-->
<!--{{{-->
<div class='toolbar' macro='toolbar [[ToolbarCommands::EditToolbar]]'></div>
<div class='title' macro='view title'></div>
<div class='editor' macro='edit title'></div>
<div macro='annotations'></div>
<div class='editor' macro='edit text'></div>
<div class='editor' macro='edit tags'></div><div class='editorFooter'><span macro='message views.editor.tagPrompt'></span><span macro='tagChooser excludeLists'></span></div>
<!--}}}-->
To get started with this blank [[TiddlyWiki]], you'll need to modify the following tiddlers:
* [[SiteTitle]] & [[SiteSubtitle]]: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
* [[MainMenu]]: The menu (usually on the left)
* [[DefaultTiddlers]]: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <<option txtUserName>>
These [[InterfaceOptions]] for customising [[TiddlyWiki]] are saved in your browser

Your username for signing your edits. Write it as a [[WikiWord]] (eg [[JoeBloggs]])

<<option txtUserName>>
<<option chkSaveBackups>> [[SaveBackups]]
<<option chkAutoSave>> [[AutoSave]]
<<option chkRegExpSearch>> [[RegExpSearch]]
<<option chkCaseSensitiveSearch>> [[CaseSensitiveSearch]]
<<option chkAnimate>> [[EnableAnimations]]

----
Also see [[AdvancedOptions]]
<<importTiddlers>>
[[General Info]]

[img[http://cygnus.tele.pw.edu.pl/~rschoeneich/NoweZdjecie.png]]

''Radosław Olgierd SCHOENEICH''

''PhD'' in Mobile Telecommunications,

''Assistant Professor'' at Warsaw University of Technology, Faculty of Electronics and Information Technology, Institute of Telecommunications, Division of Telecommunications Systems 

Nowowiejska 15/19, room. 575, Warsaw, Poland
!!!Current:

[[Android mAV ]]

[[Lightwieght Sytem for Aircraft Testing]]

[[Delay and Disruptive Tolerant Networks]]

!!!Former:

[[ORANGE LTE - project founded by ORANGE Poland Company]]

[[MIDAS - (6FP STREP) Middleware Platform for Developing and Deploying Advanced Mobile Services]]

[[ROVERS - project funded by Polish Ministry of Science and Information Society Technologies]] 


The Project starts: March 2012
The Project ends: September 2012

''Brief project description:''
The goal of the project was to develop prof of concept applications on mobile devices for LTE testing.

[img[http://cygnus.tele.pw.edu.pl/~rschoeneich/Midas-logo.png]]

The Project starts: January 2006
The Project ends: December 2008
The Project budget: 4,9M EUR

''Brief project description:''

The project will define and implement a platform to simplify and speed up the task of developing and deploying mobile applications and services. It focuses in particular on making it feasible to provide mobile services where: (1) The number of users is very large; (2) The network may need to be set up at short notice, or for limited duration; (3) Infrastructure is limited and some users may have to use ad-hoc communications.
The platform will consist of an overall architecture, and middleware building blocks providing solutions to technical issues that must be addressed in developing mobile services.
The functions provided by the building blocks will include: (1) Maintaining connectivity between nodes, mixing infrastructure-based and infrastructure-free communications as needed; (2) Information sharing through development of a flexible distributed data management system; (3) Gathering, transforming and distributing context information in a form suitable for realizing mobile services.
A "horizontal" architecture will be used, meaning that applications can adapt to different underlying communications technologies.
The project will promote standardisation by aligning its work with the OMA (Open Mobile Alliance).
Two challenging application scenarios will be used as a source of requirements on mobility, and as a means to validate the approach: mobile support for emergency crews responding to a major incident, and a system for collecting and spreading information at sports events.
The consortium includes a major research institute [SINTEF], one of Europe's foremost system integrator companies [Capgemini], a major telecoms company [Telefonica], an SME (and IST prize winner) specialising in mobile services [Appear Networks], two organisations with expertise in the domains to be used for application scenarios [51pegasi and RATP], and two Universities with leading expertise in the technical areas addressed by the project [University of Oslo and Warsaw University of Technology].
The project duration will be 30 months, with a cost budget of 4.9 MEUR and requested grant of 2.9 MEUR. The project is expected to start in early 2006.

''Project Objectives:''

MIDAS will develop a platform that makes it commercially feasible for the wider IT industry (not just telecom companies) to develop distributed mobile applications offering innovative services to end users. The project will focus in particular on the challenge of making it possible to develop services for events or situations where:
There is a very large number of users (e.g. at a major sports event).
The service has to be set up at very short notice (e.g. for teams responding to an emergency), or for a limited time period (e.g. sports event, trade fair).
The availability of infrastructure is limited (or too expensive), and some users may in some cases have to use ad-hoc, peer-to-peer communications links.
There is potentially a large market for such services, and considerable scope for innovation. But technical difficulties and the resulting high development costs today make it commercially unattractive to develop them. To overcome these difficulties, the project will:
Identify commonly occurring technical issues that need to be solved each time a new mobile service is designed.
Specify and implement middleware "building blocks" which address these issues.
Include user terminals in the service provision architecture, so that the terminals take part in providing services - not just in accessing them.
Deal with the challenging problem of combining infrastructure-based communications (e.g. GPRS, UTMS, fixed-internet, ...) and infrastructure-less communications (e.g. Bluetooth, ad-hoc WLAN, ...) within one overall communications framework.
Provide structured mechanisms for representing and adapting to changes in user context in a distributed, mobile environment.
Define a service lifecycle model which takes full account of the different conditions and connectivity opportunities that may apply at different phases in providing a service.
Develop two proof-of-concept applications to drive the work of the project, provide concrete examples of technical challenges to be addressed, and validate project results.
Promote standardisation by aligning the MIDAS approach with the work of the OMA (Open Mobile Alliance).

The proof-of-concept applications for the two scenarios will be used as a means to measure the usefulness of the middleware platform. The criterion for success is that middleware makes it easy to implement the mobility-related aspects of the applications, where "easy" is interpreted as meaning that the time required will be in the order of weeks.
The proof-of-concept applications will use at least three different Radio Access Technologies (RATs), at least one of which will be used in peer-to-peer mode. The precise technologies to be used will be selected based on an assessment of the application requirements and the latest available technologies. Likely candidates are GPRS, WLAN and Bluetooth.

''Technical Approach:''

The MIDAS technical approach is based on the following key principles:
Services are realized by distributed software components installed on nodes owned by the service provider and on devices operated by the end-users. When providing services for a specific event (e.g. sports, major conference, emergency situation), the service provider sets up "Instant Infrastructure": a collection of nodes and communications facilities to support service provision. A flexible and adaptable node configuration is used, customised to the conditions applying at a particular event. Nodes exchange short messages asynchronously with each other in order to maintain a Distributed Data Management System - a mechanism for sharing information. These inter-node messages are exchanged using one or more communications mechanisms - depending on what other nodes are present and what communications means are available. Application developers do not need to access low-level functionalities provided in specific mobile networks, but rather use such infrastructure as a means to transport data between nodes. The type of information exchanged can be text, sound, still pictures, video clips or measurement data provided by sensors. Middleware provided by MIDAS adapts to changes in network topology so that the application developer need not be concerned with changes in the network. This is not only to compensate for problems (such as failure of particular links or network partitioning) but also to exploit the opportunities offered (e.g. when high-bandwidth connections to central machines are possible). The overall approach to service design takes account of the different infrastructure options that are likely to be available during different phases of providing a service. As an example, consider a service for emergency crews. During the operational phase (i.e. at the scene of the accident), infrastructure may be very limited and the terminals of staff in the field will probably have to depend on ad-hoc communications. However, in the pre-operational phase - when staff are still at their base - broadband internet connectivity will probably be available, allowing downloading of security certificates, local maps etc. immediately before attending the event.

''MIDAS Partners:''

-Stiftelsen for industriell og teknisk forskning ved NTH (SINTEF), Norway
-Appear Networks AB, Sweden
-Telefonica, Spain
-Capgemini BV, Netherlands
-Paris Local Transport Authority, France
-51Pegasi, France
-Universitetet i Oslo, Norway
-Warsaw University of Technology (WUT), Poland

project no. 3 T11D 011 28.
The project starts June 2005.
The project ends November 2006.

''The ROVERS project description:''

The aim of the ROVERS project is to develop a middleware for ubiquitous computing applications. Ubiquitous computing (ubicomp) is the art and science of creating applications (services) that (a) take advantage of the current state of the user and the environment (context-awareness) and (b) do not require the user to interact with them (ideally, the user can forget that a ubicomp service exists). Most ubicomp applications are distributed. ROVERS applications run on numerous cooperating intelligent nodes equipped with processing capability, sensors, actuators, and wireless connectivity. The nodes are tiny and embedded into everyday objects, e.g., lamps, refrigerators, digital thermometers, thermostats.
An important factor constituting the ROVERS project is a very strict constraint imposed on energy consumption. A node should run for a long time, possibly years, on a single battery. Techniques used in larger systems where energy is less critical (e.g., mobile phones, PDA's, personal computers) cannot be used.
The ROVERS middleware will enable a node to make its resources available to peers. More specifically, a ROVERS-based application running on a given node will be able to conveniently take advantage of resources (primarily sensors and actuators, but also memory, processing power, user interface devices, WAN connectivity) contributed by other nodes. The opportunistic computing approach to application functionality will be adopted. By using to the fullest all resources that happen to be available in a given environment, the application can offer better service to the user.
Some other basic assumptions guiding the development of the ROVERS middleware are the following.
The nodes collaborate in a peer-to-peer fashion.
No specific node configuration or infrastructure is assumed (ad-hoc collaboration).
A multi-node system forms an open platform for running applications. It should be possible to inject and start new applications at any time.

The overall problem to be addressed by the ROVERS project is (a) to design a middleware layer following the above principles, (b) to prove its feasibility, and (c) to validate it. As part of feasibility analysis and validation, an operational proof-of-concept system based on tiny, energy-constrained nodes will be produced.

''Specific research and development tasks are the following:''

To develop the architecture of the ROVERS middleware.
To define an API exposing ROVERS middleware services to the application layer.
To develop methods to systematically describe resources contributed by collaborating nodes.
To specify internal middleware modules and their interfaces.
To develop middleware algorithms and protocols.
To implement the ROVERS middleware. The proof-of-concept implementation will be based on the TinyOS operating system.
To validate the concept by experimenting with the TinyOS-based implementation
Routing protocols in Delay and Disruptive Tolerant Networks (DTN),
Unmanned Autonomous Message Ferries for DTN.
Data Storing in DTN.
Wireless Mobile Ad-hoc Networks (MANET),
Wireless Sensor Networks (WSN).
Context in Wireless Networks, Content-based Networks.
Alternative and descriptive ways of nodes addressing.

[[General Info]]
[[Interests]]
[[Projects]]
[[Publications]]
[[Student Projects & Thesis]]
[[Teaching at University]]
!!!Papers:

46. A. Dziekoński, R. Schoeneich “DTN Routing Algorithm for Networks with Nodes Social Behavior”, in: International Journal of Computers Communications & Control, vol. 11, nr 4, 2016, ss. 457-471, DOI:10.15837/ijccc.2016.4.1454, [[PDF|http://univagora.ro/jour/index.php/ijccc/article/view/1454/pdf]]

----

45. M. Kawecki, R. Schoeneich “Mobility-based routing algorithm in delay tolerant networks”, in: EURASIP Journal on Wireless Communications and Networking, vol. 81, 2016, ss. 1-9, DOI:10.1186/s13638-016-0578-4, [[PDF|http://jwcn.eurasipjournals.springeropen.com/articles/10.1186/s13638-016-0578-4]]

----

44. R. Schoeneich, M. Golański, B. Krok, P. Czerminski “Autonomous drone for delay-tolerant networks in indoor applications”, in: International Journal of Distributed Sensor Networks, Hindawi Publishing Corporation, vol. 12, nr 8, 2016, ss. 1-8, DOI:10.1177/1550147716662755, [[PDF|http://dsn.sagepub.com/content/12/8/1550147716662755]]

----

43. R. Schoeneich, P. Sutkowski “Performance of IP address auto-configuration protocols in Delay and Disruptive Tolerant Networks”, in: International Journal of Electronics and Telecommunications, Komitet Elektroniki i Telekomunikacji PAN, vol. 26, nr 2, 2016, ss. 173-178, DOI:10.1515/eletel-2016-0024, [[PDF|https://www.degruyter.com/view/j/eletel.2016.62.issue-2/eletel-2016-0024/eletel-2016-0024.xml]]

----

42. R. Schoeneich “Routing for context-addressable messages using Predefined Concept Connection Map in delay tolerant network”, in: International Journal of Distributed Sensor Networks, Hindawi Publishing Corporation, vol. 12, nr 8, 2016, ss. 1-9, DOI:10.1177/1550147716662946, [[PDF|http://dsn.sagepub.com/content/12/8/1550147716662946]]

----

41. R. Schoeneich, R. Surgiewicz “SocialRouting: The social-based routing algorithm for Delay Tolerant Networks”, in: International Journal of Electronics and Telecommunications, Komitet Elektroniki i Telekomunikacji PAN, vol. 62, nr 2, 2016, ss. 167-172, DOI:10.1515/eletel-2016-0023, , [[PDF|https://www.degruyter.com/view/j/eletel.2016.62.issue-2/eletel-2016-0023/eletel-2016-0023.xml]]

----

40. R. Myśliński, R. Schoeneich “Kierowanie i przenoszenie wiadomości przez statki powietrzne w niespójnych sieciach DTN opierając sie na informacjach o trasie lotu”, in: Studia Informatica Uniwersytet Szczecinski, nr 36/2015, 2015, ss. 165-175, doi:10.18276/si.2015.36-12, [[PDF|C:\Documents and Settings\radek\Pulpit\Nowy folder\40.pdf]] 

----

39. R. Surgiewicz, R. Schoeneich “Protokół rutingu oparty o własności społecznościowe”,: Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, SIGMA NOT, vol. LXXXVIII, nr 8-9/2015, 2015, ss. 1473-1477, doi:10.15199/59.2015.8-9.114, [[PDF|C:\Documents and Settings\radek\Pulpit\Nowy folder\39.pdf]]

----

38. K. Turek, R. Schoeneich “Rozpoznawanie emocji twarzy z wykorzystaniem active shape models i suport vector machine na platformie android”,: Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, SIGMA NOT, vol. LXXXVIII, nr 8-9/2015, 2015, ss. 1346-1349, doi:10.15199/59.2015.8-9.95, [[PDF|C:\Documents and Settings\radek\Pulpit\Nowy folder\38.pdf]]

----

37. M. Kawecki, R. Schoeneich “Algorytm routingu wykorzystujący mobilnośc wezłów w sieciach niespójnych DTN”,: Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, SIGMA NOT, vol. LXXXVIII, nr 8-9/2015, 2015, ss. 921-926, doi:10.15199/59.2015.8-9.34, [[PDF|C:\Documents and Settings\radek\Pulpit\Nowy folder\37.pdf]]

----

36. P. Prus, R. Schoeneich “Zmniejszanie redundancji buforowanych wiadomosci z wykorzystaniem klastrowania wezłów w sieciach DTN”,: Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, SIGMA NOT, vol. LXXXVIII, nr 8-9/2015, 2015, ss. 899-906, doi:10.15199/59.2015.8-9.31, [[PDF|C:\Documents and Settings\radek\Pulpit\Nowy folder\36.pdf]]

----

35. R. Schoeneich, M. Golański, R. Myślinski, S Luczak “Nośniki wiadomości dla bezprzewodowych sieci niespojnych DTN”, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne 2/3 2015, ISDN 1230-3496, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/35.pdf]]

----

34. A. Dziekonski, R. Schoeneich “Routing w oparciu zachowania spolecznosciowe wezlow w sieciach DTN”, KSTiT 2014, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne 8/9 2014, ISDN 1230-3496, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/34.pdf]]

----

33. M. Kucharski, B. Zareba, D. Zgid, M. Franciszkiewicz, M. Kucharski, R. Schoeneich, M. Golanski “Ukryty kanal agregujacy w sieciach sensorow”, KSTiT 2014, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne 8/9 2014, ISDN 1230-3496, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/33.pdf]]

----

32. D. Zgid, M. Franciszkiewicz, M. Kucharski, R. Schoeneich, M. Golanski “Protokol zarzadzania praca wezlow w sieciach WSN”, KSTiT 2014, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne 8/9 2013, ISDN 1230-3496, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/32.pdf]]

----

31. R. Schoeneich, P. Pałka “ABRA: Protokół routingu dla niespójnych sieci DTN oparty na teorii aukcji”, KSTiT 2013, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne 8/9 2013, ISDN 1230-3496, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/31.pdf]]

----

30. R. Schoeneich, P. Pałka, „System komunikacji wykorzystujący bezprzewodowe sieci niespójne w sytuacjach kryzysowych” 19-21 czerwca. ZET 2013. Nałęczów, Rynek Energii, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/30.pdf]]

----

29. R. Schoeneich, P. Pałka, “Multi-commodity Trade Application to the Routing Algorithm for the Delay and Disruptive Tolerant Networks”, New Trends in Databases and Information Systems, Advances in Intelligent Systems and Computing, ISBN 978-3-642-32517-5, pp. 241-250[[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/29.pdf]]

----

28. M. Andrzejewski, R. Schoeneich, “Aircraft tracking using mobile devices”, IEEE NATO Military Comunications Conference 2012, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/28.pdf]]

----

27. R. Schoeneich, „Kierowanie wiadomości adresowanych opisowo przy wykorzystaniu złożonych modeli kontekstu w sieciach DTN”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2011), Łódź, Polska, 2011, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, 8/9 2011, ISSN 1230-3496, pp. 740-743,[[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/27.pdf]]

----

26. Ł. Kietliński, K. Lembke, M. Golański, R. Schoeneich, „RoboMote – Mobilna platforma sensorowa”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2011), Łódź, Polska, 2011, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, 8/9 2011, ISSN 1230-3496, pp. 738-740, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/26.pdf]]

----

25. M. Antosik, P. Prus, R. Schoeneich, „Specjalizowany model mobilności węzłów sieci niespójnych DTN dla scenariuszy zagrożeń i ratowania życia w obszarach zamkniętych”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2011), Łódź, Polska, 2011, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, 8/9 2011, ISSN 1230-3496, pp. 938-943, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/25.pdf]]

----

24. R. Schoeneich, P. Pałka „Zastosowanie mechanizmów aukcyjnych w decyzjach routingowych dla bezprzewodowych sieci niespójnych DTN”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2011), Łódź, Polska, 2011, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, 8/9 2011, ISSN 1230-3496, pp. 1000-1003, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/24.pdf]]

----

23. M. Andrzejewski, R. Schoeneich, „Zastosowanie sieci niespójnych w monitorowaniu statków powietrznych”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2011), Łódź, Polska, 2011, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, 8/9 2011, ISSN 1230-3496, pp. 1322-1325, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/23.pdf]]

----
 
22. K. Lembke, Ł. Kietliński, R. Schoeneich, M. Golański, „RoboMote: Mobile Autonomous Hardware Platform for Wireless Ad-hoc Sensor Networks”, IEEE International Simposium on Indiustrial Electronics (ISIE 2011), 27-30 June, 2011, Gdańsk, Poland, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/22.pdf]]

----

21. M. Golański, R. Schoeneich, M. Siwko „ The algorithm for distribution of large-size data in the Wireless Ad-Hoc Sensor Network”,  Military Communications and Information Systems Conference - MCC 2010, 27-28 września, ISBN 978-83-61486-70-1, pp. 577-584 Wrocław, Polska, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/21.pdf]]

----

20. R. Schoeneich, „Trasowanie wiadomości adresowanych kontekstowo w środowisku sieci DTN”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2010), Wrocław, Polska, 2010, Przegląd Telekomunikacyjny i Wiadomości Telekomunikacyjne, 8/9 2010, ISSN 1230-3496, pp. 1426-1431, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/20.pdf]]

----
 
19. R. Schoeneich , J. Domaszewicz, M. Koziuk, „Conncept-Based Routing in Ad-hoc Networks”, 10th International Conference on Distributed Computing and Networking - ICDCN 2009, 3-6 stycznia, Hyderabad, Indie, Springer-Verlag LNCS 5408, pp 43-48, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/19.pdf]]

----
 
18. R. Schoeneich, J. Kotlarski, L. Otulak, „Comparison of deterministic and probabilistic algorithms of context based addressing for ad-hoc networks”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2009), Warszawa, Polska, 2009, Przeglad Telekomunikacyjny, 8/9 2009, ISSN 1230-3496, pp. 999-1006, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/18.pdf]]


----

17. R. Schoeneich, J. Kotlarski, L. Otulak, „Wpływ grupowania kontekstu na wyniki algorytmów obsługi adresowania kontekstowego w sieciach ad-hoc”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2009), Warszawa, Polska, 2009, Przegląd Telekomunikacyjny, 8/9 2009, ISSN 1230-3496, pp. 1007-1014, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/17.pdf]]

----

16. J. Domaszewicz, M. Koziuk, R. Schoeneich, “Context-Addressable Messaging with ontology-driven addresses”. The 7th International Conference on Ontologies, DataBases, and Applications of Semantics (ODBASE 2008), Monterrey, Meksyk, 11 – 13 listopada, Springer-Verlag LNCS 5332, pp. 1470-1480, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/16.pdf]]

----

15. M. Koziuk, J. Domaszewicz, R. Schoeneich, M. Jablonowski, P. Boetzel, „Mobile Context-Addressable Messaging with DL-Lite Domain Model” 3rd European Conference on Smart Sensing and Context (EuroSSC 2008), 29-31 października 2008, Zürich, Szwajcaria, Springer-Verlag LNCS 5279, pp. 168-181, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/15.pdf]]

----

14. M. Koziuk, J. Domaszewicz, R. Schoeneich, K. Kacperski, „Wykorzystanie ontologii na potrzeby kontekstowych aplikacji mobilnych”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2008), Bydgoszcz, Polska, 2008, Przegląd Telekomunikacyjny, 8/9 2008, ISSN 1230-3496, pp. 957-960, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/14.pdf]]

----

13. B. Zolnierkiewicz, R. Schoeneich, M. Koziuk, „Comparing Different Architectures for Routing Daemons in MIDAS Project”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2008), Bydgoszcz, Polska, 2008, Przegląd Telekomunikacyjny, 8/9 2008, ISSN 1230-3496, pp. 1469-1475, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/13.pdf]]

----

12. M. Frackowiak, R. Schoeneich, J. Domaszewicz, M. Koziuk, „Emulator bezprzewodowych mobilnych sieci ad-hoc oparty na sterowniku TUN/TAP”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2008), Bydgoszcz, Polska, 2008, Przegląd Telekomunikacyjny, 8/9 2008, ISSN 1230-3496, pp. 1194-1200, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/12.pdf]]

----

11. K. Kacperski, R. Schoeneich, M. Koziuk, J. Domaszewicz, „Praktyczna realizacja rozwiązań Instytutu Telekomunikacji w projekcie EU 6FP MIDAS”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2008), Bydgoszcz, Polska, 2008, Przegląd Telekomunikacyjny, 8/9 2008, ISSN 1230-3496, pp. 1462-1468, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/11.pdf]]

----

10. J. Domaszewicz, R. Schoeneich, M. Koziuk, M. Rój, K. Kacperski, „Prace Instytutu Telekomunikacji PW w projekcie STREP MIDAS”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2007), Bydgoszcz, Polska, 2007, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/10.pdf]]

----

9.  R. Schoeneich, M. Golanski, “Mesh Cluster Based Routing Protocol: Enhancing The Multihop Access using Cluster Paradigm”, IEEE EUROCON 2007 Computer as a Tool,  Warszawa, Poland, 9-12 września 2007, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/9.pdf]]

----

8.  J. Domaszewicz, M. Koziuk, M. Rój, R. Schoeneich, K. Kacperski, J. Gorman, „Projekt MIDAS: Platforma programistyczna do Tworzenia i Wdrażania Zaawansowanych Usług Mobilnych”, Krajowe Sympozjum Telekomunikacji i Teleinformatyki (KSTiT 2006), Bydgoszcz, Polska, 2006, [[PDF|http://cygnus.tele.pw.edu.pl/~rschoeneich/8.pdf]]

----
 

!!!Technical Raports:

7.  M. Koziuk, R. Schoeneich, J. Domaszewicz, K.Kacperski, B. Zolnierkiewicz, „D3.3 part II Final prototype: Context-Addressable Messaging, Context Knowledge Base and Context Based Routing”, Technical Report,  EU 6FP STREP MIDAS, nov 2008

----

6.  M. Koziuk, R. Schoeneich, J. Domaszewicz, K.Kacperski, B. Zolnierkiewicz, P. Boetzel, M. Jablonowski, „D3.2 part II First Prototype Context-Addressable Messaging, Context Knowledge Base and Context Based Routing ”, Technical Report, EU 6FP STREP MIDAS, feb 2008

----

5.  A. Devlic, E. Klintskog, J.Domaszewicz, M. Koziuk, R. Schoeneich, „D3.1 Design: Middleware for Monitoring and Responding to Changes in Context”, Technical Report EU 6FP STREP MIDAS, jan 2007

----

4.  P. Ganan, S. Perez, M. Puznar, R. Schoeneich, K. Skjelsvik, „D2.1 Design: Middleware for Connectivity and Information Sharing, Design of Opportunistic Connectivity Services”, Technical Report EU 6FP STREP MIDAS, jan 2007.

----

3.  J. Domaszewicz, M. Golanski, K. Kacperski, M. Koziuk, A. Pruszkowski, M. Rój, R. Schoeneich, „Middleware (Warstwa posrednia) dla systemów ubiquitous computing typu peer-to-peer dzialajacych w trybie ad-hoc”, Technical Report, Polish National Project no: 3 T11D 011 28, marc 2006
 

!!!Thesis: 

2.  R. Schoeneich, “Metody kierowania wiadomosci dla adresowania kontekstowego w sieciach ad-hoc”, PhD Thesis, Politechnika Warszawska, 2010.

----

1.  R. Schoeneich, “Mesh Cluster-Based Routing Protocol”, MSc Thesis, Politechnika Warszawska, 2005.

----
Institute of Telecommunications, Warsaw University of Technology
Radosław Olgierd Schoeneich - home site
!!!Currently, My Students are working on:

Delay and Disruptive Tolerant Networks:
- New indor mobility models for DTN.
- Social aware routing protocols
- DTN Routing for airplanes
- Data realocating in DTN

Autonomous Message Ferries:
- Quadrocopters for Indor Applications
- Wheel-based Autonomous Andriod-based Robots

Wireless Sensor Networks:
- Data spreading and storing in DTN alike sensor clouds.
- Data sceanography in WSN.

Mobile Application based on Android:
- Applications for routing, data sharing.
- Faces and humour recognition.
- Human activity and behaviour recognition.
!!! Students thesis:
- [[Wireless Ad-hoc Networks and Systems| http://bes.tele.pw.edu.pl]]
- [[Data Transmission Systems| http://stda.tele.pw.edu.pl]]