A piconet is a computer network which links a wireless user group of devices using Bluetooth technology protocols. A piconet consists of two or more devices occupying the same physical channel (synchronized to a common clock and hopping sequence). It allows one master device to interconnect with up to seven active slave devices. Up to 255 further slave devices can be inactive, or parked, which the master device can bring into active status at any time, but an active station must go into parked first.
A group of devices are connected via Bluetooth technology in an ad hoc fashion. A piconet starts with two connected devices, and may grow to eight connected devices. Bluetooth communication always designates one of the Bluetooth devices as a main controlling unit or master unit. Other devices that follow the master unit are slave units. This allows the Bluetooth system to be non-contention based (no collisions). This means that after a Bluetooth device has been added to the piconet, each device is assigned a specific time period to transmit and they do not collide or overlap with other units operating within the same piconet.
Piconet range varies according to the class of the Bluetooth device. Data transfer rates vary between about 200 and 2100 kilobits per second.
Because the Bluetooth system hops over 79 channels, the probability of interfering with another Bluetooth system is less than 1.5%. This allows several Bluetooth Piconets to operate in the same area at the same time with minimal interference.
- Tsang, Will; Carey, Paul; O'Connor, Gerald; Connaughton, Paul (2001). "Bluetooth Terminology". Undergraduate Projects and Coursework. Network and Telecommunications Research Group. Piconet.
- Bray, Jennifer (11 May 2001). "Masters and Slaves: Roles in a Bluetooth Piconet". Informit. Pearson Educations. Retrieved 5 April 2012.
|This computer networking article is a stub. You can help Wikipedia by expanding it.|
|This article about wireless technology is a stub. You can help Wikipedia by expanding it.|
The Bluetooth security architecture relies on PIN codes for establishing trusted relationships between devices. While not practical to go through all the combinations of uses of PIN codes, it should be noted that once a trusted pairing is established between devices, these codes can be stored within the device to allow more automatic/simple connections. The key to Bluetooth simplicity will be establishing the trusted relationship between commonly used devices. For random ad-hoc connections that require authenticated connections (such as ensuring you are connecting to who you think you are connecting to, something that is not always obvious with invisible radio waves)