Umedia2011 - uP: A lightweight protocol for services in smart spaces

  • 589 views
Uploaded on

My presententation at the 4 th edition of the IEEE Ubi-Media Conference (uMedia) held at São Paulo - Brazil in 3-4 of July. …

My presententation at the 4 th edition of the IEEE Ubi-Media Conference (uMedia) held at São Paulo - Brazil in 3-4 of July.
The title is uP: A lightweight protocol for services in smart spaces

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
589
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This project is part of the UnBiquitous research group from the University of Brasilia
  • Our vision of ubicomp starts with the fact that presence of devices in everyday lives become more and more common as we speak
  • The task of ubicomp is to bring intelligence in such scenario in order for a better use of these devices.
  • But how can we bring intelligence to the environment? Who are responsible for this task?
  • Na the answer is the applications. But building applications in such a case can be very bothersome. Handling all the aspects individually is not a good idea.
  • So the most commom aproach in ubicomp environment is the use of middlewares. Ubicomp middlewares focuses on many challenges of building smart spaces. Among many of these initiatives we want to highlight three projects.
  • These projects were chosen given the fact that they address characteristics of the smart space that enhance the experience of the user. This characteristisc are
  • The different kind of interactions among devices and applicarions in the smart space. The capabilitie to handle the limitations of some devices, like CPU, memory and battery. And the wide variety of platforms available.
  • Since, among the sollutions found, none addressed the characteristics highlighted we’ve proposed this aproach. We’ve created a SOA based architecture in order to help organizing the smart space. A set of protocols for interfacing the communications in the smart space. And a middleware implementation for enabling this scenario.
  • The smart space is a set of two or more devices provided with computing power and interconnected by a communication network in a col laborative way.
  • A device is a computing equipment with communication capabilities, which must host applications or make resources available in the smart space.
  • RESOURCE: A resource is a group of functionalities logically related. These functionalities must be accessible in the environment through pre-defined inter- face. The concept of resource allows applications to be aware of a set of functionalities (services) in a more cohesive way. Resources can be either physical (like screen, keyboard, speaker, etc.) or logical (like user positioning, converters, etc.). Logical resources can provide new functionalities by accessing other resources. In SOA this is known as “composition”. A resource must be available to the smart space applications through a known public interface. In the DSOA a resource is uniquely identified by a name (or identifier ) and the set of services it provides.
  • (Resources, on the other hand, have their functionalities represented as services.) A service is the implementation of a functionality made available in the smart space through a resource with a known public interface. The service is responsible for providing the execution of functionalities of the resource. A service is only relevant if it’s capable of producing an effect that can be verified by other entities in the smart space. The interface of a service is defined by the resource the service is part of. A name (or identifier ) is responsible for uniquely identifying the service in a resource. The parameters that specify the information required for the execution of the service are also part of its interface.
  • The DSOA assumes two capabilities in order for its organizations to work. Firstly, the smart space must be able to aswer queries of which resources are available. And secondly, the resources must be able to answer to service calls.. That’s where the uP comes into scene.
  • We’ve chosen as message format for the uP the JSON format for its characteristics of being structured, multi-platform and lightweight. The first two characteriscts are common ground with the XML format but the later our testes shows that JSON takes a good advantage.
  • According to what we’ve seen, JSON shows less use of CPU and memory. Not to mention bandwidth which lead to its use in many web services nowadays.
  • Using json we not only represent our messages but also the concepts of DSOA like resources, represented as drivers and services.
  • -------------------------------------------------------------------------------Comentar a partir daqui ---------------------------------------------------------

Transcript

  • 1. uP: A lightweight protocol for services in smart spaces Msc Fabricio Nogueira Buzeto Prof. Dr. Carla Denise Castanho Prof. Dr. Ricardo Pezzuol Jacobi Departament of Computer Science University of Brasilia (UnB) This work was financially supported by DDP/UnB
  • 2. UnBiquitous Research Group Prof. Dr. Carla Denise Castanho Prof. Dr. Ricardo Pezzuol Jacobi 1 PHD Student 3 Master Students 6 Undergraduate Students https://sites.google.com/site/unbiquitous/
  • 3. http://stevenduque.com/wp-content/uploads/2010/10/too-many-devices.jpg
  • 4.  
  • 5. http://blog.mozilla.com/metrics/files/2009/07/voice_of_user2.jpg http://www.freeiconsdownload.com/site-images/Large/HardwareDevicesIcons.jpg
  • 6. http://icons.iconarchive.com/icons/deleket/sleek-xp-basic/256/Applications-Cascade-icon.png
  • 7. http://icons.iconarchive.com/icons/deleket/sleek-xp-basic/256/Applications-Cascade-icon.png Middleware
  • 8. Middleware MoCA MundoCore WSAMI
  • 9. MoCA MundoCore WSAMI
  • 10.  
  • 11.  
  • 12. DSOA Environment
  • 13. Device DSOA Environment
  • 14. Device Resource Application DSOA Environment
  • 15. Device Resource Service Application DSOA Environment
  • 16. Smart Space Query Resources Call Services Resource
  • 17.  
  • 18. JSON Structured Multi-platform Lightweight
  • 19. JSON XML JSON XML JSON
  • 20. Driver and Service
    • {
    • “ name” : “br.unb.ubiquitos.webcam.ns60” ,
    • “ services” :[
    • {
    • “ name” : “snapshot” ,
    • “ parameters” :{
    • “ width” : “MANDATORY” ,
    • “ height” : “MANDATORY” ,
    • “ encoding” : “OPTIONAL”
    • }
    • }
    • ]
    • }
    Resources are represented as drivers
  • 21. uP Protocols
  • 22. SCP : Service Call Protocol A B Service Call Service Response
  • 23. EVP: Event Protocol A B Service Call Service Response registerListener
  • 24. EVP: Event Protocol A B Notify
  • 25. EVP: Event Protocol A B Service Call Service Response unregisterListener
  • 26.  
  • 27. Complementary Protocols Device Smart Space
  • 28. Base Protocols Complementary Protocols
  • 29.  
  • 30. uOS Network Plugins Platform Drivers Aplications
  • 31. Adaptability Layer Connectivity Layer Network Layer
  • 32. Hydra Application
  • 33. Hydra Application
  • 34. Hydra Application Display Display Keyboard Mouse Keyboard Mouse Hydra
  • 35. Hydra Application
  • 36. Tests
  • 37. Latency NP : Number of parameters BP : Bytes in each parameter BP NP 16 128 512 1024 2048 1 1.537 ms 1.876 ms 2.239 ms 2.624 ms 1.843 ms 16 1.957 ms 2.369 ms 3.380 ms 3.313 ms 5.840 ms 128 2.530 ms 4.299 ms 9.665 ms 17.050 ms 41.135 ms 512 3.962 ms 7.580 ms 32.148 ms 63.395 ms 349.41 ms 1024 3.755 ms 11.95 ms 61.145 ms 135.66 ms 561.951 ms
  • 38. Latency BP NP 16 128 512 1024 2048 1 1.537 ms 1.876 ms 2.239 ms 2.624 ms 1.843 ms 16 1.957 ms 2.369 ms 3.380 ms 3.313 ms 5.840 ms 128 2.530 ms 4.299 ms 9.665 ms 17.050 ms 41.135 ms 512 3.962 ms 7.580 ms 32.148 ms 63.395 ms 349.41 ms 1024 3.755 ms 11.95 ms 61.145 ms 135.66 ms 561.951 ms Average 1.935 ms
  • 39. Latency Comparative
  • 40. Footprint Comparative kb
  • 41. Conclusions
    • uP provides :
      • a communication interface for DSOA smart spaces.
      • a way to address interaction details between devices in the smart space.
      • low consumption of computing resources.
      • multi-platform support.
  • 42. Future Work
    • Allow exhange of neighborhood information
    • Support for a hierarchy of resources
  • 43. uP: A lightweight protocol for services in smart spaces Departament of Computer Science University of Brasilia (UnB) This work was financially supported by DDP/UnB Msc Fabricio Nogueira Buzeto Prof. Dr. Carla Denise Castanho Prof. Dr. Ricardo Pezzuol Jacobi https://sites.google.com/site/unbiquitous/