File Download
  Links for fulltext
     (May Require Subscription)
Supplementary

Conference Paper: An architecture enabling Bluetooth™/JINI™ interoperability

TitleAn architecture enabling Bluetooth™/JINI™ interoperability
Authors
KeywordsBluetooth
Bluetooth Service Discovery Protocol (SDP)
Jini
XML
Issue Date2004
PublisherIEEE.
Citation
The 15th International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC 2004), Barcelona, Spain, 5-8 September 2004. In Conference Proceedings, 2004, v. 4, p. 3013-3018 How to Cite?
AbstractService discovery protocols allow clients to discover services without actual knowledge of the locations or characteristics of the services. Jini and Bluetooth SDP are two common service discovery protocols. They may meet each other in many environments. But there is still no general architecture to bring them together. We introduce an architecture for Bluetooth client to discover Jini services. We introduce the Jini/sup TM/ profile for Bluetooth, which runs in three modes of operations, namely, surrogate, bridge, and client. We describe the implementation of a Jini/Bluetooth surrogate as well as the bridge which acts as a proxy and allows a multihop connection to a Jini network. To enable reliable end to end connection, we also incorporate session management into our design.
Persistent Identifierhttp://hdl.handle.net/10722/45816
References

 

DC FieldValueLanguage
dc.contributor.authorChau, OSen_HK
dc.contributor.authorHui, Pen_HK
dc.contributor.authorLi, VOKen_HK
dc.date.accessioned2007-10-30T06:36:11Z-
dc.date.available2007-10-30T06:36:11Z-
dc.date.issued2004en_HK
dc.identifier.citationThe 15th International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC 2004), Barcelona, Spain, 5-8 September 2004. In Conference Proceedings, 2004, v. 4, p. 3013-3018en_HK
dc.identifier.urihttp://hdl.handle.net/10722/45816-
dc.description.abstractService discovery protocols allow clients to discover services without actual knowledge of the locations or characteristics of the services. Jini and Bluetooth SDP are two common service discovery protocols. They may meet each other in many environments. But there is still no general architecture to bring them together. We introduce an architecture for Bluetooth client to discover Jini services. We introduce the Jini/sup TM/ profile for Bluetooth, which runs in three modes of operations, namely, surrogate, bridge, and client. We describe the implementation of a Jini/Bluetooth surrogate as well as the bridge which acts as a proxy and allows a multihop connection to a Jini network. To enable reliable end to end connection, we also incorporate session management into our design.en_HK
dc.languageengen_HK
dc.publisherIEEE.en_HK
dc.relation.ispartofInternational Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC 2004) Proceedings-
dc.rights©2004 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.-
dc.subjectBluetoothen_HK
dc.subjectBluetooth Service Discovery Protocol (SDP)en_HK
dc.subjectJinien_HK
dc.subjectXMLen_HK
dc.titleAn architecture enabling Bluetooth™/JINI™ interoperabilityen_HK
dc.typeConference_Paperen_HK
dc.identifier.emailLi, VOK: vli@eee.hku.hk-
dc.identifier.email3018-
dc.identifier.authorityLi, VOK=rp00150-
dc.description.naturepublished_or_final_versionen_HK
dc.identifier.doi10.1109/PIMRC.2004.1368873en_HK
dc.identifier.scopuseid_2-s2.0-11244275933-
dc.identifier.hkuros105462-
dc.relation.referenceshttp://www.scopus.com/mlt/select.url?eid=2-s2.0-11244275933&selection=ref&src=s&origin=recordpage-
dc.identifier.volume4-
dc.identifier.spage3013-
dc.identifier.scopusauthoridChau, OS=8342979900-
dc.identifier.scopusauthoridHui, P=36901726300-
dc.identifier.scopusauthoridLi, VOK=7202621685-
dc.customcontrol.immutablesml 160113 - merged-

Export via OAI-PMH Interface in XML Formats


OR


Export to Other Non-XML Formats