Thanks to Bluetooth Application Developer’s Guide
Communication between electronic devices can only be achieved when they also abide by a set of predetermined rules and standards—the Open Systems Interconnect (OSI) model for communications systems protocol stacks being the primary example, and the basis from which many others have evolved.
New technologies are now emerging that allows wireless communication. The IEEE 802.11b or Wi-Fi standard is becoming accepted as the choice for the networking community. IEEE 802.11b has a data throughput of up to 11 Mbps, which gives it viability against wired networks. This technology is expensive and therefore not compatible with price-conscious consumer products, but we have now been provided with the means to create wireless, low-power, cost-effective, unconscious and ad-hoc connectivity between our devices. Its name: Bluetooth.
Wired and Wireless
In the wired solution scenario that we are all accustomed to, all of the mobile devices are used in the singular—the interaction between them is always user initiated.
The alternative – In Bluetooth - The simple act of utilizing Bluetooth technology as cable replacement removes the problem of the actual physical connections and the unconscious and ad-hoc connection capability of the technology can allow communication between the devices with no user intervention at all (OK, after some software configuration and initial device setup!)
This fully wireless scenario can be achieved because of the master/slave nature of the Bluetooth technology. All devices are peers, identified by their own unique 48-bit address, and can be assigned as a master either by function or user intervention. A master can connect to up to seven slaves at the same time, forming a piconet—this “point-to-multipoint” feature is what sets Bluetooth apart from other wireless technologies.
To be continue...
No comments:
Post a Comment