This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I would like some clarification of the difference between Public and static BLE addresses. I have an off-the-shelf Bluetooth Smart Watch that has a "Static" address type when scanned using BTool. Wit my products the address shows as "Public". As I understand both addresses expose the device MAC address - what is the difference between the two?
Essentially, static address is a random address while public is not.
From Core Spec:
The public address shall be created in accordance with section 9.2 ("48-bit universal LAN MAC addresses") of the IEEE 802-2001 standard (http://standards. ieee.org/getieee802/download/802-2001.pdf) and using a valid Organizationally Unique Identifier (OUI) obtained from the IEEE Registration Authority (see http://standards.ieee.org/regauth/oui/forms/ and sections 9 and 9.1 of the IEEE 802-2001 specification). The public device address is divided into the following two fields:• company_assigned field is contained in the 24 least significant bits• company_id field is contained in the 24 most significant bits
A static address is a 48-bit randomly generated address and shall meet the followingrequirements:• The two most significant bits of the static address shall be equal to ‘1’• All bits of the random part of the static address shall not be equal to ‘1’• All bits of the random part of the static address shall not be equal to ‘0’
Read more about static address in section 10.8.1 in Vol 3 of the Core spec. Device Address in general at section 1.3 Vol 6.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to J Lindh:
Sorry but the link you provided for Core spec ( http://e2e.ti.com/support/low_power_rf/f/538/t/247015/reply.aspx/Core%20spec) is not working.
Could you please provide the correct link.
Tanks in advance.
In reply to Alcatel W9141:
Dear Joakim Lindh
what's the risk when i use a static address? would it cause connect or function issue on some andriod or ios system?( did it require special central device?)
In reply to Lee Leon:
The TI guy has this marked as solved so he's not looking any more. Maybe I can help.
As I understand it:
The link-level "Access Address" on an advertisement may be:
I think the main risks with a private static address are:
The BLE stacks on ios devices hide the Access Address from the applications, so you have to identify your tags some other way.
In reply to Michael McClary:
I think you confused the access address vs the device address. There are two different concepts in BLE
In reply to Yuzhen Zhup:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.