Eddystone-EID - 它有什么用，它有作用吗？
Eddystone-EID - what is it for and does it work?
简单地说，Eddystone-EID 是如何工作的，主要用例是什么？
这是我在 developers.google.com 页面 here 上找到的解释。
What happens when a client sights an Eddystone-EID beacon?
When a client device sights an Eddystone-EID beacon as a result of a Nearby1 subscription, the current EID is sent to the Google Proximity Beacon API2 along with the API key of the calling app. The Google Proximity Beacon API establishes whether the supplied API key is authorized to fetch attachments that have been associated with the beacon. If resolution is allowed, the attachments are served back as Nearby message objects in the normal way. Otherwise, Google Proximity Beacon API returns an empty value, as it would if the beacon had not been registered.
1 - Google信标平台的信标扫描组件
2 - Proximity Beacon API 是一种云服务，允许您使用 REST 接口管理与 BLE 信标关联的数据。
这是我发现的另一段内容，对于理解该技术的工作原理很重要。
Eddystone-EID is designed to give developers control over which clients can make use of their beacon signals. The beacon identifier changes pseudo-randomly in such a way that it can only be resolved to stable information by a resolution service that shares an encryption key with the beacon. Without access to the resolution service, the beacon identifier is of little use.
Eddystone-EID is appropriate for cases where beacon deployers wish to:
- Prevent other parties from using their beacons.
- Preserve user privacy in scenarios involving wearables or other equipment carried by the user.
- Lease their beacon network to other parties in a way that allows a provable 'off switch' for access.
- Provide a strong signal that a user is at a particular place, that is not easily spoofed.
标准信标传输一个唯一的标识符，这样应用程序就可以知道它们何时位于特定位置。但是因为这个标识符是明文的，任何应用程序都可以读取这个标识符，并使用传输来知道它在哪里。 未经授权的第三方应用程序可以使用应用程序作者未部署的标准信标。
Eddystone-EID 加密它的标识符并定期轮换它以防止其他人使用信标标识符。 授权的应用程序可以使用 "trusted resolver" 来获得稳定来自传输中旋转加密的标识符。需要调用服务器才能将 8 字节 AES 加密标识符转换为稳定标识符。
Google 的 Proximity Beacon API 提供此转换。理论上可以在 Google 之外构建一个独立的可信解析器（我这样做是为了测试目的），但否则你必须向 Google 注册你的 EID 信标并使用他们的网络服务来解析他们的标识符.
临时标识符示例如下所示：
0a194f562c97d2ea.
这是我写的关于这个主题的文章：http://altbeacon.github.io/android-beacon-library/eddystone-eid.html
简单地说，Eddystone-EID 是如何工作的，主要用例是什么？
这是我在 developers.google.com 页面 here 上找到的解释。
What happens when a client sights an Eddystone-EID beacon?
When a client device sights an Eddystone-EID beacon as a result of a Nearby1 subscription, the current EID is sent to the Google Proximity Beacon API2 along with the API key of the calling app. The Google Proximity Beacon API establishes whether the supplied API key is authorized to fetch attachments that have been associated with the beacon. If resolution is allowed, the attachments are served back as Nearby message objects in the normal way. Otherwise, Google Proximity Beacon API returns an empty value, as it would if the beacon had not been registered.
1 - Google信标平台的信标扫描组件
2 - Proximity Beacon API 是一种云服务，允许您使用 REST 接口管理与 BLE 信标关联的数据。
这是我发现的另一段内容，对于理解该技术的工作原理很重要。
Eddystone-EID is designed to give developers control over which clients can make use of their beacon signals. The beacon identifier changes pseudo-randomly in such a way that it can only be resolved to stable information by a resolution service that shares an encryption key with the beacon. Without access to the resolution service, the beacon identifier is of little use.
Eddystone-EID is appropriate for cases where beacon deployers wish to:
- Prevent other parties from using their beacons.
- Preserve user privacy in scenarios involving wearables or other equipment carried by the user.
- Lease their beacon network to other parties in a way that allows a provable 'off switch' for access.
- Provide a strong signal that a user is at a particular place, that is not easily spoofed.
标准信标传输一个唯一的标识符，这样应用程序就可以知道它们何时位于特定位置。但是因为这个标识符是明文的，任何应用程序都可以读取这个标识符，并使用传输来知道它在哪里。 未经授权的第三方应用程序可以使用应用程序作者未部署的标准信标。
Eddystone-EID 加密它的标识符并定期轮换它以防止其他人使用信标标识符。 授权的应用程序可以使用 "trusted resolver" 来获得稳定来自传输中旋转加密的标识符。需要调用服务器才能将 8 字节 AES 加密标识符转换为稳定标识符。
Google 的 Proximity Beacon API 提供此转换。理论上可以在 Google 之外构建一个独立的可信解析器（我这样做是为了测试目的），但否则你必须向 Google 注册你的 EID 信标并使用他们的网络服务来解析他们的标识符.
临时标识符示例如下所示：
0a194f562c97d2ea.
这是我写的关于这个主题的文章：http://altbeacon.github.io/android-beacon-library/eddystone-eid.html