IP Library Granted Patent US 11,403,415
Granted Patent B2
US 11,403,415 · App. 16/997,568 · Granted Aug 2, 2022

System and method for implementing data sovereignty safeguards in a distributed services network architecture

Inventors: Richard D. Shriver (Tinton Falls, NJ); Edward T. Pieluc, Jr. (Howell, NJ); Daniel J. McDonald (Whitehouse Station, NJ); Hugh Beverly Appling (Hickory, NC); David Alan Hammaker (Oakland Park, FL); Zheng Sun (Greenacres, FL)
Assignee: OPEN TEXT HOLDINGS, INC.
G06F21/6218H04L63/20H04L67/1095H04L67/306G06F2221/2111H04L63/102H04L67/10H04W4/021
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,403,415
App. No.
16/997,568
Granted
Aug 2, 2022
Kind
B2
Abstract

Embodiments of systems and methods for implementing data sovereignty safeguards in a distributed services network architecture are disclosed. Embodiments of a distributed services system may have a number of distributed nodes that each implements a set of services. When a user requests a service at a particular node of a distributed services system, the node is configured to determine if that node is not (or is) data sovereign for a region associated with the user. If the node is not data sovereign for the user's region, the user may be directed to a corresponding service at a node of the distributed service system that is data sovereign for the user's region.

Claims (46)

1. A system that enforces data sovereignty for users, comprising:

a set of nodes coupled via a computer network, each of the nodes implementing a set of services, a first service on a first node including a first interface accessible at a first network address for receiving a request for the first service from a user over the network; and

a data sovereignty module, the data sovereignty module:

identifying a data sovereign region for the user based on a user account record for the user, the user account record for the user including a region identifier for use in the identification of the data sovereign region for the user;

identifying one or more non-data sovereign regions or data sovereign regions associated with the first node on which the first service is implemented;

determining that the first node on which the first service is implemented is not data sovereign for the region identified for the user based on the one or more non-data sovereign regions or data sovereign regions associated with the first node and the identified data sovereign region for the user; and

when it is determined that the first node is not data sovereign for the region identified for the user:

determining a response to the request, and

returning the response to the user without implementing the request at the first service.

2. The system of claim 1 , wherein determining a response includes:

determining a second network address for a second interface of a second service based on the identified data sovereign region for the user, wherein the second service is implemented on a second node that is data sovereign for the data sovereign region identified for the user, and including the second network address in the response.

3. The system of claim 2 , wherein the response is determined based on response configuration associated with the first node or the second node.

4. The system of claim 1 , wherein identifying the one or more non-data sovereign regions or data sovereign regions associated with the first node on which the first service is implemented comprises accessing a data sovereignty configuration for the first node.

5. The system of claim 4 , wherein the data sovereignty configuration is replicated across each of the set of nodes.

6. The system of claim 1 , wherein identifying the data sovereign region for the user is based on a location identified based on the request.

7. The system of claim 6 , wherein the user account record for the user, including the region identifier, is updated based on the location.

8. A method for enforcing data sovereignty, comprising:

receiving a request for a first service from a user over a network at a first interface accessible at a first network address, wherein the first service is on a first node of a set of nodes coupled via a computer network, each of the nodes implementing a set of services;

identifying a data sovereign region for the user based on a user account record for the user, the user account record for the user including a region identifier for use in the identification of the data sovereign region for the user;

identifying one or more non-data sovereign regions or data sovereign regions associated with the first node on which the first service is implemented;

determining that the first node on which the first service is implemented is not data sovereign for the region identified for the user based on the one or more non-data sovereign regions or data sovereign regions associated with the first node and the identified data sovereign region for the user; and

when it is determined that the first node is not data sovereign for the region identified for the user:

determining a response to the request, and

returning the response to the user without implementing the request at the first service.

9. The method of claim 8 , wherein determining a response includes:

determining a second network address for a second interface of a second service based on the identified data sovereign region for the user, wherein the second service is implemented on a second node that is data sovereign for the data sovereign region identified for the user, and including the second network address in the response.

10. The method of claim 9 , wherein the response is determined based on response configuration associated with the first node or the second node.

11. The method of claim 8 , wherein identifying the one or more non-data sovereign regions or data sovereign regions associated with the first node on which the first service is implemented comprises accessing a data sovereignty configuration for the first node.

12. The method of claim 11 , wherein the data sovereignty configuration is replicated across each of the set of nodes.

13. The method of claim 8 , wherein identifying the data sovereign region for the user is based on a location identified based on the request.

14. The method of claim 13 , wherein the user account record for the user, including the region identifier, is updated based on the location.

15. A non-transitory computer readable medium comprising instructions for:

receiving a request for a first service from a user over a network at a first interface accessible at a first network address, wherein the first service is on a first node of a set of nodes coupled via a computer network, each of the nodes implementing a set of services;

identifying a data sovereign region for the user based on a user account record for the user, the user account record for the user including a region identifier for use in the identification of the data sovereign region for the user;

identifying one or more non-data sovereign regions or data sovereign regions associated with the first node on which the first service is implemented;

determining that the first node on which the first service is implemented is not data sovereign for the region identified for the user based on the one or more non-data sovereign regions or data sovereign regions associated with the first node and the identified data sovereign region for the user; and

when it is determined that the first node is not data sovereign for the region identified for the user:

determining a response to the request, and

returning the response to the user without implementing the request at the first service.

16. The non-transitory computer readable medium of claim 15 , wherein determining a response includes:

determining a second network address for a second interface of a second service based on the identified data sovereign region for the user, wherein the second service is implemented on a second node that is data sovereign for the data sovereign region identified for the user, and including the second network address in the response.

17. The method of claim 16 , wherein the response is determined based on response configuration associated with the first node or the second node.

18. The non-transitory computer readable medium of claim 15 , wherein identifying the one or more non-data sovereign regions or data sovereign regions associated with the first node on which the first service is implemented comprises accessing a data sovereignty configuration for the first node.

19. The non-transitory computer readable medium of claim 18 , wherein the data sovereignty configuration is replicated across each of the set of nodes.

20. The non-transitory computer readable medium of claim 15 , wherein identifying the data sovereign region for the user is based on a location identified based on the request.

21. The non-transitory computer readable medium of claim 20 , wherein the user account record for the user, including the region identifier, is updated based on the location.

Assignments (3)
MERGER Recorded May 18, 2026
From: OPEN TEXT HOLDINGS, INC.
To: OPEN TEXT INC.
Reel/Frame 074679/0083 →
MERGER Recorded Oct 14, 2020
From: XPEDITE SYSTEMS, LLC
To: OPEN TEXT HOLDINGS, INC.
Reel/Frame 054047/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 14, 2020
From: SHRIVER, RICHARD D.; PIELUC, EDWARD T., JR.; MCDONALD, DANIEL J.; APPLING, HUGH BEVERLY; HAMMAKER, DAVID ALAN; SUN, ZHENG
To: XPEDITE SYSTEMS, LLC
Reel/Frame 054047/0619 →
Continuity (3)
Continuation 15956045 · Apr 18, 2018
Provisional Application 62486757 · Apr 18, 2017
Related Publication 20200380152A1 · Dec 3, 2020