- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm starting with PSoC BLE now, got some kits, etc. I've some questions about the IDs used in a BLE system.
- Am I required to have a company ID assigned by SIG or can I use the Cypress company ID for products?
- The company ID in combination with a (preferrably) unique ID assigned by me is the 48-bit (24 + 24 bit) BLE MAC address, right?
- The UUID is independent from the BLE MAC address and is either 16-bit assigned by SIG for predefined characteristics, services etc. or 128-bit for custom service, etc. with 4A98xxxx-1CC4E7C1-C7571267-DD021E8, where 'xxxx' can be assigned by me?
- The UUID can be duplicate (e.g. in a totally different product), so to ensure that communication is established with the correct product, I've to check the BLE MAC address of the device, right?
I Hope someone can help me to understand it right or can point me to the right documentation.
Regards,
Ralf
Solved! Go to Solution.
- Labels:
-
BLE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
(Bump)
1. Yes, you are required to buy/use your own IDs registered with bluetooth SIG. See this page: http://www.cypress.com/knowledge-base-article/queries-ble-qualification-and-declaration-processes-kb...
2. Correct
3. You can assign the entire 128-bit UUID I believe; The idea is to keep it unique if possible though, hence using the RNG from the cypress IDE will help prevent accidental collisions with other UUIDs.
4. Each service/characteristic/GATT item has it's own UUID, and thus you would use the UUID to differentiate between services and data on a device you are already connected to, but you would use the BLE "MAC Address" to connect to correct devices. Or specific flags/data in the advertisement packets upon scanning for devices. (E.G. Logitech BLE keyboard would send out advertisement packets with "LG 7921837" for BLE software to discover)
Related pages that might be helpful:
http://www.cypress.com/forum/proc-ble/mac-address
http://www.cypress.com/knowledge-base-article/setting-bluetooth-device-address-kba211407
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Push...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
(Bump)
1. Yes, you are required to buy/use your own IDs registered with bluetooth SIG. See this page: http://www.cypress.com/knowledge-base-article/queries-ble-qualification-and-declaration-processes-kb...
2. Correct
3. You can assign the entire 128-bit UUID I believe; The idea is to keep it unique if possible though, hence using the RNG from the cypress IDE will help prevent accidental collisions with other UUIDs.
4. Each service/characteristic/GATT item has it's own UUID, and thus you would use the UUID to differentiate between services and data on a device you are already connected to, but you would use the BLE "MAC Address" to connect to correct devices. Or specific flags/data in the advertisement packets upon scanning for devices. (E.G. Logitech BLE keyboard would send out advertisement packets with "LG 7921837" for BLE software to discover)
Related pages that might be helpful:
http://www.cypress.com/forum/proc-ble/mac-address
http://www.cypress.com/knowledge-base-article/setting-bluetooth-device-address-kba211407
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi e.pratt,
thank you for clarification, that helps a lot.
Regards,
Ralf