Objective

I'm working on the machine-to-machine applications in Mobility First project. It is specifically focused in sensor network. In Mobility First network, sensors, like other mobile devices, will be given Global Unique IDs(GUID) as their names recognizable to network. With GUIDs, sensor data are no longer isolated information which requires application specific gateways. M2M applications will be able to publish and access sensor data from different vendors by GUID, not requiring application specific gateways, through Mobility First network, which has a Global Name Resolution Service(GNRS) allowing fast updates on attach points, self-certifying of data source/destination, and dynamic connections of sensors.

Porject approach

Sensor Networks

• Sensor network I: Pipsqueak, 900MHz sensors, processed under "Grail rtls". ​Grail
• Sensor network II: WINS 2.4GHz sensors, processed under windows API.

Approach

• Step 1. Application level integration (Currently working on): integrate two sensor networks under Grail system.

• Step 2. Core network integration for Mobility First network (Future work): including sensor and Context(sensor data with certain context) GUID assignment, publish and lookup server.

About Application Level Integration

Data out of grail system could match different kinds of GUID in the Mobility First network more easily. So we will integrate two different groups of sensor networks from different vendors into grail. And through grail, we will publish and access sensor data by GUID through Mobility First network. The function of grail could be broken into five layers, as shown in the picture below. You can find more information about those layers here: ​Grail_layers.

The first step is to integrate two sensor networks on the aggregator layer. After this, all the raw data form two different sensor networks will be aggregated on an aggregator server. From that aggregator server we could get individual raw data or grouped data or data with context, which is corresponding to individual GUID, compound GUID and context GUID respectively, as long as we implement a certain analysis application based on the request.

I have already implemented this step. And under debug mode of aggregator sever, we could see the newly integrated sensor data from sensor network II--wins.

The next step is to implement an analysis application to request data from aggregator layer and push it to distributor layer where those data could be published to and accessed from network. An simple analysis application(solver) is implemented. And the raw data could be shown on the distributor.

Then, I need to modify the solver to translate the data.

After that, I will work on the word_server part, which deals with the sensor id, type and other information registration and lookup. Analysis applications could lookup in world_server which sensors they need from aggregator. And in the mobility first network, GNRS does the similar job for GUID.

Work Log

June 20: Modify network layer between Wins which is under Windows Visual Studio and Grail system which is under Linux.

According grail communication protocol, implement handshake function under windows visula studio.

June 21: Test and debug handshake communication between Wins and Grail.

June 22: Fetch updated Grail system code. Modify handshake protocol.

June 23: Modify Wins according to updated Grail. Test new handshake protocol between Wins and grail.

July 15: Intergration of Wins with Grail system on aggregator layer is implemented.

July 29: Working on the analysis application. Based on the grailV3_solver_client protocol, aggregator_solver_protocol, and solver_distributor_protocol, implemented a solver application connect to distributor first, and then connect to aggregator to request new integrated data.

August 5: Implemented a simple analysis application for new integrated wins data. The analysis application push the data to the distributor, and the raw sensor data is shown on the distributor. For the next step, I will modify the analysis application to translate the raw data , and work on the world_server part for the sensor ID registration and lookup.