Mobile and Embedded Applications Group meag@tele.pw.edu.pl
MEAG home Projects Publications Courses MEAG Lab Inside MEAG People
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
        Papers Theses Reports Workshops
 

 

Theses

 

 MobileSpaces - JavaSpaces for mobile devices PDF - 476 KB 
Tomasz Rybicki
Warszawa 2004
in English

Abstract:
The tuple space paradigm is an interesting concept when talking about data interchange in distributed applications. The goal of this work was to create a system that would allow mobile applications, run on java enabled mobile devices (mobile phones), to access a tuple space, in such a manner to hide from the user all the actions being a consequence of the device's limited resources and its mobility. The created system - MobileSpaces - employs JavaSpaces tuple space implementation presenting the user with an API that is similar to the JavaSpaces API, thus making mobile distributed applications not very different from such applications run on PCs.
Moreover, by the use of Jini technology and Jini Surrogate Architecture it was made possible to create distributed applications that run on both mobile devices and PCs at the same time.

 

 Mobilna Randka. Aplikacja Parlay/OSA PDF - 1,83 MB 
Michał Kunikowski
Warszawa 2004
in Polish

Abstract:
The main goal of the Mobile Date service is to enable making new contacts between people of matching preferences. Two service users are compatible when they mutually fulfill their specified preferences. The service is location-based. When two compatible users happen to be close to each other, the service takes an action depending on settings selected by the users. One possible action is to make a third-party call connecting them. Another action is to notify the both users with an SMS that a compatible party is nearby. Either of them can then call the other one or send the other one an SMS.
The service is anonymous. The users don't know real telephone numbers of each other. Every user has his own unique user id. The notification SMS generated by the service includes the user id of the other person. The user sends an SMS or calls another one using the other user's id.
Two interfaces to manage the service are available: one is based on SMS messages and the other one on a Web page. There are two actors: the user and the service administrator. The user has the both interfaces. The user can register with the service, provide a description of himself, specify his preferences, manage his service settings, and see history of connections generated by the service. The administrator uses the Web interface only. He can see traffic generated by the service and related to a specific user.

 

 RFID Reader/Writer  PDF - 1,38 MB 
Łukasz Geldner, Paweł Nowiński
Warszawa 2003
in English

Abstract:
This work describes a system which takes advantage of RFID and J2ME technologies. The system consists of two parts: an RFID reader/writer and J2ME application.
The RFID module is developed as a separate electronic device (based on AVR microcontroller) and can be connected to a J2ME phone through a serial line. The module is enabled with the RS232 interface and communicates with the J2ME application (located in the phone) using a special protocol (presented in the work in details). Since RFID tags use very specific data formats, various formats have been described in the work The RFID module "translates" the data into a more universal protocol to the application.
The application is a simple user interface to the RFID module: in the test version it is able to read the data written in the RFID tag and present it to the user. It also allows to write data on the tag. Since the application is a J2ME MIDlet, some important J2ME issues have been discussed in the work as well as how the application is built.
In the work, an overview of RFID and J2ME technologies have been included.

 

 An Introduction to Parlay/OSA APIs  PDF - 515 kB 
M. Rój
Warsaw 2002
in English

Abstract:
The goal of this work is to introduce the reader to Parlay/OSA APIs in concise way. The Parlay/OSA APIs is a set of programming interfaces that allow independent service vendors creating telecommunication services. The APIs include (among others): call control part, user interaction part, localization, charging and accounting features. Parlay/OSA interfaces are ETSI and 3GPP standards.
The first part of the work is the introduction to the Parlay/OSA information model. Next, whole the APIs' functionality is discussed. Finally, a simple telecommunications service is described. The service has been implemented in Java and tested with Ericsson OSA/Parlay Simulator.

 

:::::::::::::::::::::::::::::::::: ZST Division at Insitute of Telecommunications - Warsaw University of Technology ::::::::::::::::::::::::::::::::::
Site manager: M.Golanski@tele.pw.edu.pl