Granted Patent B2

US 11,076,003 · App. 16/236,406 · Granted Jul 27, 2021

Inventors: Christopher Smith (Sherwood, OR); Sudeep Das (Cupertino, CA)

Assignee: McAfee, LLC

H04L67/16G06F9/5027H04L41/20G06F2209/5015

Abstract

Claims (34)

1. A data exchange layer (DXL) broker, comprising:

a network interface to communicatively couple to a data exchange layer (DXL), the DXL comprising a two-layer enterprise service bus (ESB) configured to provide one-to-one device communications employing a private device topic on a publish-subscribe fabric, wherein the first layer is a traditional internet protocol (IP) network, and the second layer is a DXL service to operate on the traditional IP network;

hardware comprising at least a processor; and

instructions encoded on one or more computer-readable mediums to instruct the processor to provide DXL broker software configured to:

receive a DXL request message via the DXL, the request message directed to a DXL service via a non-private topic;

determine that the DXL service is available; and

forward the request message to a DXL endpoint via a private device topic for the DXL endpoint.

2. The DXL broker of claim 1 , further comprising a local database of registered services, and wherein determining that the DXL service is available comprises querying the local database.

3. The DXL broker of claim 1 , wherein determining that the DXL service is available comprises determining that a DXL domain master has registered as providing the DXL service.

4. The DXL broker of claim 1 , wherein the DXL broker software is further configured to determine that the DXL service is unavailable, and to notify the DXL endpoint that the service is unavailable.

5. The DXL broker of claim 1 , wherein the DXL broker software is further configured to parse routing information to a DXL domain master that is to service the DXL request message.

6. The DXL broker of claim 1 , wherein the DXL broker software is further configured to identify an optimal target for the DXL request message.

7. The DXL broker of claim 6 , wherein identifying the optimal target comprises identifying a DXL domain master in closest physical proximity to the DXL endpoint.

8. The DXL broker of claim 6 , wherein identifying the optimal target comprises identifying a DXL domain master previously identified as optimal.

9. The DXL broker of claim 6 , wherein identifying the optimal target comprises looking up a DXL domain master previously identified by a different DXL device as an optimal DXL domain master.

10. The DXL broker of claim 1 , wherein the request message comprises a DXL topic, and wherein forwarding the request message comprises querying a DXL domain master to identify one or more DXL endpoints that have subscribed to the DXL topic.

11. One or more tangible, non-transitory computer-readable mediums having stored thereon executable instructions for providing a data exchange layer (DXL) broker configured to:

provide a DXL software interface to communicatively couple to a two-layer, publish-subscribe enterprise service bus (ESB), wherein the first layer is a traditional internet protocol (IP) network, and the second layer is a DXL service to operate on the traditional IP network, and to provide on the ESB brokered one-to-one device communications employing a private device topic on the ESB;

receive a DXL request message via the ESB, the request message directed to a DXL service via a non-private topic;

determine that the DXL service is available; and

forward the request message to a DXL endpoint via a private device topic for the DXL endpoint.

12. The one or more tangible, non-transitory computer-readable mediums of claim 11 , wherein determining that the DXL service is available comprises querying a local database.

13. The one or more tangible, non-transitory computer-readable mediums of claim 11 , wherein determining that the DXL service is available comprises identifying a DXL domain master that has registered as providing the service.

14. The one or more tangible, non-transitory computer-readable mediums of claim 11 , wherein the DXL broker is further configured to determine that the DXL service is unavailable, and to notify the DXL endpoint that the service is unavailable.

15. The one or more tangible, non-transitory computer-readable mediums of claim 11 , wherein the DXL broker is further configured to parse routing information to a DXL domain master that is to service the DXL request message.

16. The one or more tangible, non-transitory computer-readable mediums of claim 11 , wherein the DXL broker is further configured to identify an optimal target for the DXL request message.

17. The one or more tangible, non-transitory computer-readable mediums of claim 11 , wherein the request message comprises a DXL topic, and wherein forwarding the request message comprises querying a DXL domain master to identify one or more other DXL endpoints that have subscribed to the DXL topic.

18. A computer-implemented method of providing a data exchange layer (DXL) broker service, comprising:

communicatively coupling to a two-layer enterprise service bus (ESB) that provides a publish-subscribe fabric, wherein the first layer is a traditional internet protocol (IP) network, and the second layer is a DXL service to operate on the traditional IP network, and providing on the ESB a DXL, including the ability to provide brokered one-to-one device communications employing a private device topic on the DXL;

receiving a DXL request message via the DXL, the request message directed to a DXL service via a non-private topic;

determining that the DXL service is available; and

forwarding the request message to a DXL endpoint via a private device topic for the DXL endpoint.

19. The method of claim 18 , further comprising querying a local database to determine that the DXL service is available.

20. The method of claim 18 , wherein determining that the DXL service is available comprises identifying a DXL domain master that was previously registered as providing the DXL service.

Assignments (13)