Secure beacon identity
A method may include receiving, from an endpoint device, a request to register a service that is supported by the endpoint device, identifying, in view of the service identified in the request, a service provider of interest that relates to the service, receiving, from the endpoint device, a service connection request to initiate data flow related to the service, validating the endpoint device, and responsive to validating the endpoint device, establishing the service connection to a device associated with the service.
1. A system, comprising:
a memory to store a set of instructions; and
one or more hardware processors coupled to the memory, the one or more hardware processors being configured to execute the set of instructions to cause the system to perform operations comprising:
receive, from an endpoint device, a beacon including a request to register a service that is supported by the endpoint device, the beacon including data from a plurality of services that are run by the endpoint device within a decentralized network, the beacon including a time-based precomputed hash value;
identify, in view of the service identified in the request, a service provider of interest that is capable of providing the service;
receive, from the endpoint device, a service connection request to initiate data flow to provide the service;
validate the beacon of the endpoint device by determining that the time-based precomputed hash value included with the beacon has not been invalidated; and
responsive to validating the beacon of the endpoint device, establish a service connection within the decentralized network between the endpoint device and a particular device associated with the service to provide the service.
2. The system of claim 1 , wherein identifying the service provider of interest includes identifying an associated endpoint manager server.
3. The system of claim 1 , wherein validating the endpoint device includes:
identifying an identifier of the endpoint device; and
validating the endpoint device based on the identifier of the endpoint device.
4. The system of claim 1 , wherein the identifier of the endpoint device includes a manufacturer of the endpoint device, wherein the endpoint device is validated based on the manufacturer of the endpoint device.
5. The system of claim 4 , wherein the service connection is established with a server associated with the manufacturer of the endpoint device, the particular device associated with the service including the server.
6. The system of claim 1 , wherein the request to register the service that is supported by the endpoint device is received as a broadcast by the endpoint device.
7. The system of claim 1 , wherein the request to register the service that is supported by the endpoint device includes a characteristic of the endpoint device, wherein the endpoint device is validated based on the characteristic of the endpoint device.
8. The system of claim 1 , wherein establishing the service connection to a device associated with the service includes configuring a data communication mechanism between the endpoint device and the device associated with the service.
9. The system of claim 1 , wherein execution of the set of instructions further cause the system to void the service connection to the device associated with the service in response to an identification of a predetermined condition.
10. A method, comprising:
receiving, from an endpoint device, a beacon including a request to register a service that is supported by the endpoint device, the beacon including data relating to a plurality of services that are capable of being run by the endpoint device within a decentralized network, the beacon including a time-based precomputed hash value;
identifying, in view of the service identified in the request, a service provider of interest that is capable of providing the service;
receiving, from the endpoint device, a service connection request to initiate data flow to provide the service;
validating the endpoint device by determining that the time-based precomputed hash value included with the beacon received from the endpoint device has not been invalidated; and
responsive to validating the endpoint device, establishing a service connection between the endpoint device and a particular device associated with the service the decentralized network.
11. The method of claim 10 , wherein identifying the service provider of interest includes identifying an associated endpoint manager server.
12. The method of claim 10 , wherein validating the endpoint device includes:
identifying an identifier of the endpoint device; and
validating the endpoint device based on the identifier of the endpoint device.
13. The method of claim 10 , wherein the identifier of the endpoint device includes a manufacturer of the endpoint device, wherein the endpoint device is validated based on the manufacturer of the endpoint device.
14. The method of claim 13 , wherein the service connection is established with a server associated with the manufacturer of the endpoint device, the particular device associated with the service including the server.
15. The method of claim 10 , wherein the request to register the service that is supported by the endpoint device is received as a broadcast by the endpoint device.
16. The method of claim 10 , wherein the request to register the service that is supported by the endpoint device includes a characteristic of the endpoint device, wherein the endpoint device is validated based on the characteristic of the endpoint device.
17. The method of claim 10 , wherein establishing the service connection between the endpoint device and the particular device associated with the service includes configuring a data communication mechanism between the endpoint device and the particular device associated with the service.
18. The method of claim 10 , further comprising voiding the service connection to the device associated with the service in response to an identification of a predetermined condition.
19. A non-transitory computer-readable storage medium storing executable instructions that, in response to execution, cause one or more processors to perform operations comprising:
receive, from an endpoint device, a beacon including a request to register a service that is supported by the endpoint device, the beacon including data relating to a plurality of services that are capable of being executed on the endpoint device within a decentralized network, the beacon including a time-based precomputed hash value;
identify, in view of the service identified in the request, a service provider of interest that is capable of providing the service;
receive, from the endpoint device, a service connection request to initiate data flow to provide the service;
validate the endpoint device by determining that the time-based precomputed hash value included with the beacon has not been invalidated; and
responsive to validating the endpoint device, establish a service connection between the endpoint device and a particular device associated with the service within the decentralized network.
20. The non-transitory computer-readable storage medium of claim 19 , the operations further comprising to void the service connection to the device associated with the service in response to an identification of a predetermined condition.