Jini Meets UPnP: An Architecture for Jini/UPnP Interoperability

  • Authors:
  • J. Allard;V. Chinta;S. Gundala;G. G. Richard III

  • Affiliations:
  • -;-;-;-

  • Venue:
  • SAINT '03 Proceedings of the 2003 Symposium on Applications and the Internet
  • Year:
  • 2003

Quantified Score

Hi-index 0.00

Visualization

Abstract

A service discovery framework provides a collectionof protocols for developing dynamic client/serverapplications, allowing clients to find and use serviceswithout any previous knowledge of the locations orcharacteristics of the services. There are currently manyservice discovery technologies available or indevelopment, including Jini, UPnP, SLP, Salutation,Bluetooth SDP, and Ninja. These have similar high-levelgoals, but quite different architectures. Each software orhardware product utilizing service discovery will typicallyuse only one of these protocols,meaning that clients andservices using different technologies will not be able tocooperate. Since it is likely that several protocols will bewidely used, there is a need for interoperabilityframeworks that allow clients and services written usingdifferent service discovery technologies to cooperate.This paper presents a Jini/UPnP interoperabilityframework that allows Jini clients to use UPnP servicesand UPnP clients to use Jini services, withoutmodification to service or client implementations. Asservice specifications are typically developedindependently for each protocol, a fully automaticinteroperability solution is not currently practical, so weintroduce service-specific proxies to bridge Jini andUPnP. Our goal is to reduce the amount of effort requiredto support new service types and our framework includesa substantial amount of support for rapid proxydevelopment. A modest development effort is required tosupport each new service type, and our initial (and highlyunscientific) measurements reveal that the level of effortis typically on the order of one day by a member of ourteam.