Use a unique app id for connection

[Pseudogelb]

Hi,

I would like to connect two centrals to one peripheral with >= BLE 4.3. I know,

normally one central is connected to multiple peripheral, but in this case,

a special sensor needs to serve multiple centrals.

So, it should only be allowed from the peripheral to connect to two centrals (Version A and B),

where each central runs a different application. The peripheral should only be able to connect

to one version A device and one version B device, so somehow I would like to filter out 

on the peripheral side we I get an advertising response, if I can accept the connection as specified

How can I filter out this connections? Normally when I have one central and multiple peripheral,

each peripheral has a unique target name, that I can filter, but I cannot filter from the peripheral 

what central target name I have?

[Kenneth]

Hi,

I don't see any easy solution to this problem. You could be swapping advertisement content (e.g. device name), e.g. such that you periodically switch between advertising with "A" and "B" (e.g. every 200ms), then once you are connected to "A" (or "B"), then you would only advertise with "B" (or "A"). You can also have some check when connected that the correct peer have connected, and disconnect if not.

Best regards,
Kenneth

[Pseudogelb]

Ok, I wonder if this should not be standard? Normally, Smartphones take the central role in BLE, so a normal usecase should be two smartphones connect to one sensor. Why is this not supported as standard?

[Kenneth]

There is technically no problem for a peripheral device to be connected to several central devices, but I am not aware of any standard that discuss how to solve the use case where you want only one central A and one central B to connect no.