Peripheral/Slave serving multiple Central/Masters
Peripheral/Slave serving multiple Central/Masters
- Subject: Peripheral/Slave serving multiple Central/Masters
- From: Chip Keyes <email@hidden>
- Date: Sat, 09 Mar 2013 15:43:08 -0700
| This question may be more pertinent to a Bluetooth SIG group, which I am going to flow up with, but I thought it might be of interest to this group as well.
The issue deals with adherence to the 4.0 spec for allowing a peripheral/slave to be accessed concurrently by multiple Central/Managers.
I have coded a CBPeripheralManager based peripheral and found that it supports multiple concurrent connections from different Central devices. There is sufficient information in the CBATTRequest which identifies the requesting Central that intelligent handling of the server based resources (e.g. the immediate alert) can be managed effectively. Generally it is just a matter of storing transaction records based upon the requesting Central.
But, in reading the Bluetooth 4.0 spec, I found the following information .. my red highlight.
================ From Core_V4-1.0 [ Volume 1]
3.3.2.1.3 Topology
An LE piconet channel can be shared by any number of LE devices, limited
only by the resources available on the piconet master device. Only one device
is the piconet master; all others being piconet slaves. All communication is
between the master and slave devices. There is no direct communication
between slave devices on the piconet channel.
There is virtually no limit on the number of logical transports that can be sup-
ported within a piconet. This means that there is no theoretical limit to the num-
ber of Bluetooth devices that share a channel with the master.
At present an LE device is only permitted to belong to one piconet at a time. ================
So a Central/Master can connect to multiple peripherals but a slave can be connected to only a single Master at one time (else it would be in more than one piconet).
The iOS platforms enable peripherals to be concurrently accessed by multiple Masters (my empirical work), will doing so effectively result in the peripheral device being non-compliant to 4.0 spec?
-Chip
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden