1. D-OSDi + Android Progress Presentation Xinyi Dong Long Qiu

2. Project Goal  Fulfill SOA (Service Oriented Architecture) and CBD (Component Based Development)  Build up Distributed OSGi framework for mobile phone and virtual machines.  Develop network module which enables communication among different OSGis.  Implement service transition bundle that bridge various objects.

3. Group Project Description  Setting up Distributed OSGi framework on virtual machine.  Setting up Distributed OSGi framework on Android phone.  Develop network bundle.  Develop service transition bundle.  Develop demo bundles which utilize built platform to show its strength.

4. Current Project Status  Setting up Distributed OSGi framework on virtual machine. 100% done  Setting up Distributed OSGi framework on Android phone. 100% done  Develop network bundle. 100% done  Develop service transition bundle. 100% done  Develop demo bundles which utilize built platform to show its strength. 100% done

5. Roadmap TASK2/62/203/43/184/14/19 Task 2.1 Task 2.2 Task 2.3 Task 2.4 Task 2.5

6. Technical Details Task 1(previous)  Task 1: Setting up Distributed OSGi framework on virtual machine. (100% done) Using Felix OSGi Framework D-OSGis are running on Window 7

7. Technical Details Task 2(previous)  Task 2: Setting up Distributed OSGi framework on Android phone. Step 1: Transfer the Felix OSGi framework jar files from java machine code to Dalvit machine code. (done) Step 2: Transplant these files into Android device (currently, we’re using android emulator). (done) Step 3: Transfer the bundles which enable the Distribute OSGi framework. (get stuck) Step 4: Run the Distributed OSGi bundles on Android. (to do)

8. Technical Details Task 3,4 (previous)  Task 3: Develop network bundle. 50% done  Task 4: Develop service transition bundle. 100% done We successfully tested that different OSGis running collaboratively on different OSGi Framework on PC.

9. New solution  Rather than using Felix OSGi framework which has compatible issues running on Android platform.  We turned to another OSGi mobile framework mbs, which has Android code IDE and has Plug-ins in Eclipse platform.  The old one’s problem is…  Davit virtual machine and Java virtual machine  Develop from application level rather than machine code migration.

10. Comparison between two solutions  The main difference is between the development of bundles running in Android  Previous solution:  Code bundle in PC with Java and get Jar file  Turn Jar file to David machine code file and then push into Android file system.(Compatible issue occurred)  Recent solution  Code with Android compatible language.  Generate Android app with bundles running and then installed the app in Android phone.

11. Comparison between two solutions Java program Davit machine code Previous solution to develop bundle in Android Recent solution to develop bundle in Android Java program Android app Android App PC Android phone

12. New Tasks:  Setup Equinox OSGi implementation on PC  Provide Eclipse plug-in  Set up MBS OSGi framework on Andriod phone  It also provides Eclipse plug-in  We can be able to code in application level and install application in Android phone.  Create a demo shows bundles communication between PC and Android, we’ll show a get- location demo.

13. New Tasks:  Setup Equinox OSGi implementation on PC  Provide Eclipse plug-in  Set up MBS OSGi framework on Andriod phone  It also provides Eclipse plug-in  We can be able to code in application level and install application in Android phone.  Create a demo shows bundles communication between PC and Android, we’ll show a get- location demo.

14. Demo  Get location demo  This demo shows bundles communication between PC and Android Bundle requesting Android’s location Bundle get itself location OSGi framework on PC OSGi framework on Andoid

15. Conclusion  This project is completed.  Realized the communication in data level between different OSGi frameworks on PC and Android phone.

16. Thank you! Questions & Comments