A Device and Service Description Framework for Discovering and Reasoning in Autonomous P2P Environment N. Shimizu Keio university
Talk outline Goal of our project – Basic motivations – Assumptions Our framework – Service model – Device model – XML syntax
Original motivation
Objectives New functionality creation support Ex. – Speaker + Amp. + CD player = speaker system – Scanner + Modem = FAX – Mpg encoder + Storage = Video
Autonomous P2P environment Established P2P connection No yellow pages Multi-user Device variety – Capability – Underlying APIs E.g. IEEE1394, UPnP, Bluetooth etc.
Autonomous P2P environment P2P network Established P2P connection No yellow pages Multi-user Device variety – Capability – Underlying APIs E.g. IEEE1394, UPnP, Bluetooth etc.
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
To archive our objectives Who has printing functionality? I have it, send my information.
Issues Functionality abstraction Resource competition Dependency solution Status notification
Description framework Device description – Devices’ structure – Functionality information – Specifications Service description – Capability information
Device description SPEC information Primitive services which it provides Primitive devices which it has
Status notification Static status Dynamic status – Failure – Occupied / released – Other status
SPEC information value_of_aaa value_of_bbb Attribute – value list “key” – attribute name – string
Primitive service Abstracted device functionality Resource in our P2P network Atomic operation I’m busy!
Composite service New functionality composed with devices Composition of primitive services Converting servicePrinting service Image printing service
Primitive service description <PrimitiveService type=“uri_to_indentify_it” name=“human_readable_name”> Capability information …
Commitment dependency I can print BMP file I can print PDF and BMP file I can convert png into JPG or BMP
Primitive service capability parameter information parameter information
Parameter information img/jpg img/png
Summary Several issues for functionality composition – Functionality abstraction – Resource competition – Dependency solution – Status notification Our framework – Primitive service – Dependency solution support
Future work Formalization Expand description framework – Service composition – Semantic description Arguments: JPG, JPEG, jpeg, Jpeg, JpG …. Service behavior – Dynamic status notification Trust model
Thank you for your attention And Have Questions or Comments?