Browse Prior Art Database

Secondary Calculated Bluetooth ID for Presence

IP.com Disclosure Number: IPCOM000180734D
Original Publication Date: 2009-Mar-16
Included in the Prior Art Database: 2009-Mar-16
Document File: 2 page(s) / 41K

Publishing Venue

IBM

Abstract

Portable devices that have bluetooth have a builtin bluetooth id by which they may be recognied by other bluetooth devices, normally for communication purposes, i.e. for connecting to and communicating with another device. Another usages has been lately overloaded on the bluetooth id for the purpose of Presence (e.g. PresenceZones). Presence applications that may reside anywhere repeatedly inquire for devices in their vicinity. As these applications may do something useful for the owner of the device, a device owner may want his/her device to respond to the inquiries. However, the device's security is compromised by that since entities that know the device's bluetooth id may perform operations on the device that are harmful to the owner of the device.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Secondary Calculated Bluetooth ID for Presence

Portable devices that have bluetooth have a builtin bluetooth id by which they may be recognied by other bluetooth devices, normally for communication purposes, i.e. for connecting to and communicating with another device. Another usages has been lately overloaded on the bluetooth id for the purpose of Presence (e.g. PresenceZones).

    Presence applications that may reside anywhere repeatedly inquire for devices in their vicinity. As these applications may do something useful for the owner of the device, a device owner may want his/her device to respond to the inquiries. However, the device's security is compromised by that since entities that know the device's bluetooth id may perform operations on the device that are harmful to the owner of the device.

    Another solution is to install anti-virus software on the device to overcome the security holes created by broadcasting the bluetooth id to any inquiring entity. this is a problem for most users as anti-virus software requires the user's installation, attention and continuous maintenance. Additionally they cost money and it occupy precious space (memory).

    A solution is required by which the device would be able to repeatedly advertise an id that identifies its owner for presence purposes without compromising the device, and without requiring special anti-virus software .

    Since the problem is that the bluetooth id designated to the device is overloaded and used both for communication and presence the solution is to have the device manage two bluetooth id's, one only for normal bluetooth communications (called here "regular bluetooth id"), and the other (called here "the presence id") for Presence only. The user will be able to expose or hide any of them independently via the user interface and software on the device. The presence id will not compromises the device as communicating with the device using this id will not be possible.

    When the device receives an inquiry it will respond with any, none, or both of the two id's managed by it, as specified by the user. When the device receives a request to connect to the presence id, it will refuse it. When the device is prompted for services that the presence id supports, it will respond with none or a very small limited set which poses no harm.

    The Presence ID may be physical id stored in the device or it may be a virtual id generated/calculated by the device ea...