20/12/2007


This is how new SIMS middleware looks like. With a component(application) browser, middleware manages the life cycle of the applications. Finally, user can "see" the middleware instead of asking where is the middleware. Middleware is instantiated before applications, takes charge of the resources and behaves like a simple OS. Sexy!Since the limitation of the Midp, for example we can only run one Midlet at one time, I put a lot effect to fulfill the multi-applications. I will talk more details of Midp and Midlet later.Web Services is also employed to be the communication protocol from this release! It's easy to generate WS mobile client using WSDL. All the sending and receiving between server and clients are done by WS. Instead of converting XML to objects by using KXml, which is I did in previous versions, WS takes care of the work. All I need to do is making and maintaining good WSDLs.


Read more about the progress on SIMS MW at http://simsmw.blogspot.com/

MIDAS 2007 - Gieten cycle race - first live field test




2007 Gieten cycle race - first live field test

important milestone in MIDAS: the first live field test, at a major cycling event

The race took place near the small town of Gieten. It is an annual event, attracting many amateur cyclists from a wide area, and (on the second day) professional cyclists from several countries. It attracts considerable media attention, including on this occasion coverage by Belgian television.

Members of the MIDAS team from Capgemini (Wybe, John, Lorenzo and Matthijs) were helped by Henk and Rick from NOC*NSF and staff from SmartPosition (the company we have allied ourselves with to obtain sensor data), to make sure everything worked. Joe from SINTEF also attended.

the names of competitors and their start numbers have to be entered into the system before the start of the race. We were able to equip a subset of the riders (20) with position sensors.

tension mounts even more as Matthijs starts up the applications -this time for the first REAL test.

MIDAS staff start to distribute sensors to competitors. The sensors are contained in small pouches that can easily be fastened round the arm. MIDAS staff must also ensure that they keep track of which cyclists have which sensors.

The cyclists had not previously been told that they were taking part in this experiment, and found out only just before the start. So some were a little puzzled. But the cycling federation had of course given their formal approval to allow us to do this.

word is received that the race is about to begin.

At least one competitor seems to be smiling and happy with his MIDAS sensor.

They're off! The race begins - and one of the front liners is part of the subset equipped with a MIDAS sensor.

It's a tough race - partly on road, but mostly off-road. Six laps of about 6km for the men.

Spectators (and race officials) can only see individuals going past checkpoints on the road - but for most of the time have no idea how the race is developing off-road, in the forest.

But at MIDAS HQ, Wybe is able to announce "Gentlemen: we are live!" - the software is working as intended. We can see the positions of all the riders, who is in what position, how they are formed into groups, and how far each has still to cycle. (Well, for the ones with MIDAS sensors at least). Screenshots are projected onto a large screen and we all gather round to see.

We use multiple terminals, to simulate different spectators.

One of the women cyclists who had been wearing one of our sensors visits MIDAS HQ after completing the race: she is interested to know what it is all about. As the mens part of the race is still continuing, she can follow the progress (in this case on a NOKIA handheld).

They can follow the progress using the NOKIA handheld, communicating wirelessly back to the MIDAS HQ.

The race is over, but now there is a practical problem: some of the competitors forget they have the sensors on, and leave the field before we have a chance to retrieve them. But we have our secret weapon: that we know exactly where they are. By giving some MIDAS staff sensors too, Henk is able - from MIDAS HQ - to direct retrieval operations.

But today is worse than on day 1: this time two of the culprits (SP.37 and SP.31) have left by car. But Matthijs sets off in the MIDAS pursuit vehicle (SP.22). With the help of instructions from Henk ("suspects moving east towards sports centre" etc.), he is able to track them down.

Matthijs is able to report to Henk that the car chase is over, and the MIDAS sensors have been retrieved. So we are all ready for the next MIDAS event - and can go home and celebrate a succesful first MIDAS field test!

12/11/2007

About this Blog

Mobile and wireless communication is playing an ever more increasingly central role in all aspects of business. Europe’s economy will be impacted by the mobile application capability beyond recognition in a few years time. We are in the process of a major shift from the wireless and communication concept of ‘anywhere, anytime’ to a new paradigm of ‘any device, with relevant content and context in a secure and trusted manner’. Many future innovative and technological projects will be based on this growing concept. We know that future systems and applications will be complex, consisting of a multitude of services and network types from Wide Area Networks to Home Networks. The increasing dependency of such communication infrastructures requires new approaches and an emphasis for European research to help overcome technical, business and citizen barriers, in order to remain the leader in mobile and wireless communications.




MUSIC
- Self-Adapting Applications for Mobile Users in Ubiquitous Computing Environments.

The MUSIC project is collaboration between fifteen partners from ten European countries. Partners include some of the largest companies in the industry, as well as leading research institutes. Some of the major partners are Hewlett Packard, SINTEF, Telecom Italia, European Media Laboratory, Telefónica I+D and RATP. The goal of the MUSIC project is to supply architecture, design tools and a framework to make it feasible for companies to develop next generation mobile services. Nowadays we see a need to provide a global access to context information regardless of where it is produced. The challenges that need to be solved are latencies, communication cost, intermittent connectivity, and limited battery capacity. Our research is directed to find optimal solutions to those challenges.




MIDAS
- Middleware Platform for Developing and Deploying Advanced Mobile Services

The main objective of MIDAS is to develop a platform with open APIs which will make it possible and economical to develop distributed mobile applications. The MIDAS platform will be used by application developers who want to create mobile applications/services connecting a large number of users. MIDAS will provide necessary basic functionality, which resolves important issues related to connectivity, deployment and information sharing. The distributed architecture used by MIDAS will give opportunities for innovative applications/services, in mobile devices, which ware not possible/feasible prior to MIDAS. These innovative applications/services include client-server and peer-to-peer networks, with or without a connection to Internet. Example applications are mobile service for emergency crews and mobile service at sporting events etc.







SIMS
- Methods and tools for developing Semantic Interfaces for Mobile Services

The main objective of SIMS is to develop a middleware for PDAs/phones, connected using WLAN or GPRS, and to develop design tools based on UML. The design tools will be available as components for the Eclipse platform. These components can by freely used by developers who want to build mobile applications/services using the SIMS-technology. The keyword in the SIMS middleware is the invention of dubbed semantic interfaces, a technology which supports service discovery and composition of services and components (vertical and horizontal composition) at runtime with guaranteed compatibility. Device A will automatically download functionality from Device B if device A supports and needs/wants that functionality. The middleware will validate opportunities between peers. In other words, only valid services/functionality will be available and presented to the end-user. If successful, SIMS will, in a low-level sense, enable learning of functionality.