Bluetooth Data Points

Network proximity pioneer ...

Bluetooth Data Points

BDP browse Bluetooth Data Points (BDP) let share and discover data in a local proximity. The main idea behind this approach is doing that without the preliminary scene preparation. BDP model does not require wireless tags, fingerprints (radio maps), etc. An ordinary smart phone is enough for creating own data channel and start sharing (distributing) own data.

BDP approach lets mobile users (enterprises) associate own data snippets with Bluetooth nodes. So, other mobile users in proximity (Bluetooth radio distance) will be able to discover and read them. You can think about the web browsing, where web pages provide some hyper-local data.

BDP. Starts node One user (publisher) describes own data (e.g., classified, coupons/discount info, service request/offer, etc.) and starts linked Bluetooth node right on the phone. Other users in proximity can browse (with the same application) local data and respond. For the moved phone (Bluetooth node) data will follow to the phone.

BDP is the only network proximity solution for the mass market. It is easy to use and has got a zero cost of entry. Your own smartphone is enough.

The main idea behind this approach is a network proximity. If two mobile users can see at this moment the same Bluetooth node than it is very probable that they can see each other. In other words, they are close to each other. Close in the geographical sense, of course. And our Bluetooth node could be switched on right on the smartphone.

So, if we associate (link) some information to that network node, we can show data to the local users only. We have a transparent mechanism to show our data to users in a local proximity only. Note, it works without opening a Bluetooth connection and without getting real geo-coordinates.

And here you can see step by step example for BDP. Actually, BDP is an extension of our previous context-aware projects: Spot Expert and WiFi Chat.

Contact info

Feel free to contact / connect with us:

email:info@servletsuite.com
blog:servletsuite
twitter:@t411