1. A Device and Service Description Framework for Discovering and Reasoning in Autonomous P2P Environment N. Shimizu chiko@tom.sfc.keio.ac.jp Keio university

2. Talk outline Goal of our project – Basic motivations – Assumptions Our framework – Service model – Device model – XML syntax

3. Original motivation

4. Objectives New functionality creation support Ex. – Speaker + Amp. + CD player = speaker system – Scanner + Modem = FAX – Mpg encoder + Storage = Video

5. Autonomous P2P environment Established P2P connection No yellow pages Multi-user Device variety – Capability – Underlying APIs E.g. IEEE1394, UPnP, Bluetooth etc.

6. Autonomous P2P environment P2P network Established P2P connection No yellow pages Multi-user Device variety – Capability – Underlying APIs E.g. IEEE1394, UPnP, Bluetooth etc.

7. To archive our objectives Establishment of description framework Device discovery by – Device name – Providing services Reasoning to – Determine the most appropriate device – Solve dependencies between services

8. To archive our objectives Who has printing functionality? I have it, send my information.

9. Issues Functionality abstraction Resource competition Dependency solution Status notification

10. Description framework Device description – Devices’ structure – Functionality information – Specifications Service description – Capability information

11. Device description SPEC information Primitive services which it provides Primitive devices which it has

12. Status notification Static status Dynamic status – Failure – Occupied / released – Other status

13. SPEC information value_of_aaa value_of_bbb Attribute – value list “key” – attribute name – string

14. Primitive service Abstracted device functionality Resource in our P2P network Atomic operation I’m busy!

15. Composite service New functionality composed with devices Composition of primitive services Converting servicePrinting service Image printing service

16. Primitive service description <PrimitiveService type=“uri_to_indentify_it” name=“human_readable_name”> Capability information …

17. Commitment dependency I can print BMP file I can print PDF and BMP file I can convert png into JPG or BMP

18. Primitive service capability parameter information parameter information

19. Parameter information img/jpg img/png

20. Summary Several issues for functionality composition – Functionality abstraction – Resource competition – Dependency solution – Status notification Our framework – Primitive service – Dependency solution support

21. Future work Formalization Expand description framework – Service composition – Semantic description Arguments: JPG, JPEG, jpeg, Jpeg, JpG …. Service behavior – Dynamic status notification Trust model

22. Thank you for your attention And Have Questions or Comments?