You Are Here:

Community: Blogs

Arto Holopainen's Forum Nokia Blog

Connectivity with medical POC devices, bluejacking?

ahoccc | 16 June, 2006 00:52

What does bluejacking to do with medical measurement devices?

 

Let’s take closer look for the case where measurement device is active in creating connection to other device to deliver measurement results. In this case device functioning is as follows:

  • After person has taken measurement device activates Bluetooth communication automatically (person can not affect to this)
  • If there is no previously paired target in the memory, device starts to look Bluetooth targets that provide SPP service.
    • Device tries to create connection one after one to found Bluetooth targets with SPP service
    • When some Bluetooth target responds with correct PIN, device sends measurement results.
  • If there is previously paired target in device memory, it tries to connect and send measurements automatically.
    • If for some reason target is not available, or transmission fails. Device begins again Bluetooth inquiry for new possible target.
  • And all this happens “under the hood” without any indication to the measurement device user.
 

Here is one case that might happen when person is taking measurements at home and no initial pairing has been done. There isalso one PDA device and one PC with Bluetooth SPP service available in the next door neighbours (isn't wireless fun!). So the initial communication might not go as expected.

 Measurement device initiated communication, initial pairing

Not so nice Bluetooth planning from the measurement device manufacturer, eh? Neighbouring devices gets connection attempt notification from some obscurely named measurement device.

 

This does not end to this with this device. Let’s think about simpler case where there is only measurement device and correct target device in the range. But the target device is advertising two SPP services, both from different applications. Only one application is waiting for measurement results, other application is for some other purposes. Let’s see what could happen.

 

Measurement device initiated communication, two SPP service in one target

This case is hard reality with older Series 60 models (e.g. Nokia 6600). There is one Bluetooth SPP service advertised by system (for unknown reason). So it is impossible to get these Series 60 models to communicate with this measurement device, since the connection is always tried with system SPP service.

 

How could this multiple service problem be handled?

  • Measurement device should look for devices with SPP service and with specific service name -> service name separates multiple SPP services from each other. Of course this would need modifications to device itself…
  • One not so elegant solution could be that listening application could try to be the first application to register to SDP database with SPP service. This way it would be most likely the first service reported in SDP inquiry.
 

Let’s look how this “named service” principle works for these two presented problem cases.

Measurement device initiated communication, initial pairing with named service

 

Measurement device initiated communication,  two SPP service in one target with named service Now everything seems to work better…

And if you are wondering if this kind of measurement device could even exist, yes it does and the device is also quite a lot used with different kind of target devices.

 

Stay tuned for more…

Find more related topics in my blogs here.

RSSComments

Re: Connectivity with medical POC devices, bluejacking?

coultonp | 16/06/2006, 18:11

coultonp Arto

Excellent blog.! We developed a similar solution for a proximity based game we have called mobslinger which needs to transfer data between to devices using same application to trigger the game action. We faced many similar problems but you have come up with a very eloquent description of the problems and solution. I am glad to see people are using Bluetooth as I feel it has become somewhat second best to WiFi in some peoples eyes which is a great shame as it offers something completely different.
You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxSpecialistE20withE20healthcareE20andE20mobileE20workforceE20E28enterpriseE29E20relatedE20mobileE20solutionsE2eE20ahocccE20E7cE2016E20JuneE2cE202006E2000E3a52E20WhatE20doesE20bluejackingE20toE20doE20withE20medicalE20measurementE20devicesE3fE20Ea0E20E4cetE92sE20takeE20closerE20lookE20forE20theE20caseE20whereE20measurementE20deviceE20isE20activeE20inE20creatingE20connectionE20toE20otherE20deviceE20toE20deliverE20measurementE20resultsE2eE20InE20thisE20caseE20deviceE20functioningE20isE20asE20followsE3aAfterE20personE20hasE20takenE20measurementE20deviceE20activatesE20BluetoothE20communicationE20automaticallyE20E28personE20canE20notE20affectE20toE20thisE29E2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fartoE2dholopainensE2dforumE2dnokiaE2dblogE2f2006E2f06E2f16E2fconnectivityE2dwithE2dmedicalE2dpocE2ddevicesE2dbluejackingX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxArtoE20HolopainenE27sE20ForumE20NokiaE20BlogE20E7cE20ConnectivityE20withE20medicalE20POCE20devicesE2cE20bluejackingE3fX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZBlogE45ntryQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxSpecialistE20withE20healthcareE20andE20mobileE20workforceE20E28enterpriseE29E20relatedE20mobileE20solutionsE2eE20ahocccE20E7cE2016E20JuneE2cE202006E2000E3a52E20WhatE20doesE20bluejackingE20toE20doE20withE20medicalE20measurementE20devicesE3fE20Ea0E20E4cetE92sE20takeE20closerE20lookE20forE20theE20caseE20whereE20measurementE20deviceE20isE20activeE20inE20creatingE20connectionE20toE20otherE20deviceE20toE20deliverE20measurementE20resultsE2eE20InE20thisE20caseE20deviceE20functioningE20isE20asE20followsE3aAfterE20personE20hasE20takenE20measurementE20deviceE20activatesE20BluetoothE20communicationE20automaticallyE20E28personE20canE20notE20affectE20toE20thisE29E2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUqfnTopicZconnectivityQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZcppQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZenterpriseQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZBlogE45ntryQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZupdatedQDx2006E2d06E2d16X qfnZuserE5ftagQSxconnectivityX qfnZuserE5ftagQSxenterpriseX qfnZuserE5ftagQSxsymbianE2dcE2bE2bX qmarsZdescriptionQSxSpecialistE20withE20healthcareE20andE20mobileE20workforceE20E28enterpriseE29E20relatedE20mobileE20solutionsE2eE20ahocccE20E7cE2016E20JuneE2cE202006E2000E3a52E20WhatE20doesE20bluejackingE20toE20doE20withE20medicalE20measurementE20devicesE3fE20Ea0E20E4cetE92sE20takeE20closerE20lookE20forE20theE20caseE20whereE20measurementE20deviceE20isE20activeE20inE20creatingE20connectionE20toE20otherE20deviceE20toE20deliverE20measurementE20resultsE2eE20InE20thisE20caseE20deviceE20functioningE20isE20asE20followsE3aAfterE20personE20hasE20takenE20measurementE20deviceE20activatesE20BluetoothE20communicationE20automaticallyE20E28personE20canE20notE20affectE20toE20thisE29E2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZBlogE45ntryQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ