You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bluetooth SIG has a process called New Work Proposal (NWP) and that should be used to create a beacon standard. It will allow to define Extended Inquiry Response (EIR) and Advertising Data (AD) types for beacon data.
Using the EIR and AD manufacturer field is not helping since you need to fill in Bluetooth SIG assigned manufacturer ID. If everybody fills in their own this is still not interoperable.
The text was updated successfully, but these errors were encountered:
I think that's a great way to go.
When we put together this spec, we did consciously limit ourselves to existing AD structures in order to get something to market as fast as possible.
But I think superceding this version with a new AD structure specifically for proximity advertisement would be fantastic.
If I put together an NWP would you be interested in signing as a representative of a supporting member company?
have you made any progress toward a SIG-approved solution since Marcel's comment? Do you have any guidance as to how long it will take to get anything approved by the SIG?
The Bluetooth SIG has a process called New Work Proposal (NWP) and that should be used to create a beacon standard. It will allow to define Extended Inquiry Response (EIR) and Advertising Data (AD) types for beacon data.
Using the EIR and AD manufacturer field is not helping since you need to fill in Bluetooth SIG assigned manufacturer ID. If everybody fills in their own this is still not interoperable.
The text was updated successfully, but these errors were encountered: