I would like to inquire whether there is a sample or guide to search for and connect to iPhone background advertising when operating with nRF52840/5340 Central.
https://medium.com/@shaharwie/ios-ble-peripheral-application-using-corebluetooth-7a93123e3e0f
Hi,
I am not aware of any samples or guides specifically for connecting to iPhone background advertising, but the general solution would be the same regardless of what device is the BLE advertiser. You should therefore be able to test this with a central sample from the nRF Connect SDK, with some minor modification.
Bluetooth Central samples are listed among other samples on the nRF Connect SDK Bluetooth samples and Zephyr Bluetooth samples documentation pages. Please note that the samples in the SDK are for specific BLE services, and so they typically connect to devices advertising those services or based on device name.
In order to do any useful work, you also must implement the central side of the services from the peripheral. You can use models already implemented in the SDK for reference, such as e.g. the Nordic UART Service (NUS) Client, which is the central side model for connecting to a NUS Server. The first step, however, would be to successfully establish the BLE connection.
If you are unfamiliar with Bluetooth Low Energy and/or the nRF Connect SDK, then I recommend having a look at Bluetooth Low Energy Fundamentals.
Regards,
Terje
Dear Terje
The part you mentioned was explained based on NCS operation and examples, but the part I was inquiring about is as follows.
Currently, I am developing product FW as a multi-nus project, so ncs development is possible to some extent.
nRF52 BLE central auto-reconnect to iPhone
https://stackoverflow.com/questions/73856952/ble-scanning-in-background-state-of-ios-app
https://medium.com/@cbartel/ios-scan-and-connect-to-a-ble-peripheral-in-the-background-731f960d520d
If the iPhone performs ble advertising in the foreground, it is recognized well. But when the iPhone is ble advertising in the background, the Name and UUID are not visible on the device. I would like to ask if there is a way to resolve this issue.
Regards,
Yeonsoo
Dear Terje
https://medium.com/@cbartel/ios-scan-and-connect-to-a-ble-peripheral-in-the-background-731f960d520d
In particular, we would like to inquire about whether there is a search and connection method that meets the Apple iPhone BLE advertising in background mode policy.
Regards,
Yeonsoo
Hi,
From the information under The bluetooth-peripheral Background Execution Mode in the Core Bluetooth Programming Guide from Apple, it looks like the Apple device in background mode does not advertise the device name, and does not advertise any service UUID. This is in accordance with what you have seen. Please note that those two are the main pieces of advertising data that a central uses to decide which device to connect to.
I assume that device name and service UUIDs are turned off in background mode primarily for privacy reasons. This means I would not expect there to be other static information in the advertisements which can be used to recognize the device.
You can use nRF Connect for Desktop with the BLE app, or nRF Connect for Mobile (iOs or Android), to investigate the contents of advertisements, and see if there are any other fields which you can use for identifying the advertising iOS device. If you have previously connected to the device, then there might be an option to recognize it based on device address. I would expect the adress in that case to be a resolvable random address, which requires you to have bonded with the device earlier in order to get the identity address, which would allow you to recognize the device.
If the iOS device is not using a resolvable address for the advertising, then most likely there is no easy way to recognize the device. One option then would be to connect to any device with unknown name and no service UUIDs, and figure out whether or not this was the correct device after connection.
Regards,
Terje
Hi,
From the information under The bluetooth-peripheral Background Execution Mode in the Core Bluetooth Programming Guide from Apple, it looks like the Apple device in background mode does not advertise the device name, and does not advertise any service UUID. This is in accordance with what you have seen. Please note that those two are the main pieces of advertising data that a central uses to decide which device to connect to.
I assume that device name and service UUIDs are turned off in background mode primarily for privacy reasons. This means I would not expect there to be other static information in the advertisements which can be used to recognize the device.
You can use nRF Connect for Desktop with the BLE app, or nRF Connect for Mobile (iOs or Android), to investigate the contents of advertisements, and see if there are any other fields which you can use for identifying the advertising iOS device. If you have previously connected to the device, then there might be an option to recognize it based on device address. I would expect the adress in that case to be a resolvable random address, which requires you to have bonded with the device earlier in order to get the identity address, which would allow you to recognize the device.
If the iOS device is not using a resolvable address for the advertising, then most likely there is no easy way to recognize the device. One option then would be to connect to any device with unknown name and no service UUIDs, and figure out whether or not this was the correct device after connection.
Regards,
Terje
