1 / 20

N. Shimizu chiko@tom.sfc.keio.ac.jp Keio university

A Device and Service Description Framework for Discovering and Reasoning in Autonomous P2P Environment. N. Shimizu chiko@tom.sfc.keio.ac.jp Keio university. Talk outline. Goal of our project Basic motivations Assumptions Our framework Service model Device model XML syntax.

uma-ashley
Download Presentation

N. Shimizu chiko@tom.sfc.keio.ac.jp Keio university

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. To archive our objectives Who has printing functionality? I have it, send my information. I have it, send my information.

  7. Issues • Functionality abstraction • Resource competition • Dependency solution • Status notification

  8. Description framework • Device description • Devices’ structure • Functionality information • Specifications • Service description • Capability information

  9. Device description <Device type=“device.specific.uri”> <Specification> SPEC information </Specification> <PrimitiveServiceList> Primitive services which it provides </PrimitiveServiceList> <DeviceList> Primitive devices which it has </DeviceList> </Device>

  10. Status notification • Static status • Dynamic status • Failure • Occupied / released • Other status

  11. SPEC information <Specification> <Item key=“aaa”>value_of_aaa</Item> <Item key=“bbb”>value_of_bbb</Item> </Specification> • Attribute – value list • “key” • attribute name • string

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

  13. Composite service • New functionality composed with devices • Composition of primitive services Converting service Printing service Image printing service

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

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

  16. Primitive service capability <PrimitiveService type=“…” name=“…”> <InputParameterList> parameter information </InputParameterList> <OutputParameterList> parameter information <OutputParameterList> </PrimitiveService>

  17. Parameter information <Parameter name=“aaa” type=“string” /> <Parameter name=“bbb” type=“integer” /> <Parameter name=“ccc” type=“base64binary”> <AcceptableFileType”> img/jpg </AcceptableFileType> <AcceptableFileType> img/png </AcceptableFileType> </Parameter>

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

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

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

More Related