Federated uptake throttling

• US 9,866,627 B2
• Filed: 11/20/2015
• Issued: 01/09/2018
• Est. Priority Date: 12/31/2007
• Status: Active Grant

• Current Assignee: Genesys Telecommunications Laboratories Incorporated (Genesys Cloud Services Incorporated)
• Original Assignee: Genesys Telecommunications Laboratories Incorporated (Genesys Cloud Services Incorporated)
• Inventors: Ristock, Herbert Willi Artur, Galvin, Brian
• Primary Examiner(s): BAYARD, DJENANE M
• Application Number:
  US14/948,036
• Publication Number:
  US 20160149998A1
• Time in Patent Office: 781 Days
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

In a first enterprise joined in a distributed, federated network of second enterprises, a system is provided for managing data flow between enterprises, the system including a data management server in the first enterprise having access to sets of rules for managing data flow to and from the first enterprise, a first data interface in the first enterprise dedicated to data transfer to a paired second dedicated data interface at a neighboring second enterprise in the federation, wherein the first data interface manages data sent to the second interface and/or data incoming from the second interface according to the sets of rules for managing data flow.

Claims

1. A system for managing data flow between a plurality of enterprises in a federation comprising:

a processor hosted by a first enterprise in the federation;

a memory, wherein the memory has stored thereon instructions that, when executed by the processor, causes the processor to;

admit a requesting entity into the federation;

identify data to be provided to the plurality of enterprises in the federation in response to admitting the requesting entity into the federation;

identify a rule for managing data flow between the plurality of enterprises; and

throttle transmission of the data to the plurality of the enterprises in the federation based on the rule, wherein the instructions that cause the processor to throttle transmission of the data includes instructions that cause the processor to transmit at least a portion of the data to a second enterprise of the plurality of enterprises in the federation, and refrain from transmitting the portion of the data to a third enterprise of the plurality of enterprises in the federation.

2. The system of claim 1, wherein the rule includes conditions for assigning bandwidth for transmitting the identified data, wherein the program instructions further cause the processor to:

identify a type of data contained in the portion of the identified data;

identify a first bandwidth allocated to the type of data based on the rule; and

transmit the portion of the data to the second enterprise in accordance with the allocated first bandwidth.

3. The system of claim 2, wherein the program instructions further cause the processor to:

identify a second bandwidth allocated to a second portion of the identified data based on the rule, wherein the second bandwidth is different from the first bandwidth; and

transmit the second portion of the identified data in accordance with the allocated second bandwidth.

4. The system of claim 3, wherein the portion of the identified data associated with the first bandwidth is data associated with routing of contacts, and the second portion of the data associated with the second bandwidth is configuration data.

5. The system of claim 1, wherein the program instructions further cause the processor to:

transmit a first notification to the second enterprise prior to transmitting the portion of the identified data to the second enterprise;

wait for a second notification from the second enterprise; and

transmit the portion of the identified data in response to receipt of the second notification.

6. The system of claim 5, wherein the second notification specifies timing of transmission of data to the second enterprise, wherein the instructions further cause the processor to transmit the portion of the identified data in accordance with the specified timing.

7. The system of claim 6, wherein the second notification specifies an amount of data to be transmitted to the second enterprise, wherein the instructions further cause the processor to transmit the portion of the identified data in accordance with the specified timing and specified amount of data.

8. The system of claim 1, wherein the refraining of transmitting the portion of the data to the third enterprise is based on refusal of the data based on a determination that the data is redundant.

9. The system of claim 1, wherein the refraining of transmitting the portion of the data to the third enterprise is based on refusal of the data based on a determination of latency in the data.

10. The system of claim 1, wherein instructions that cause the processor to refrain from transmitting the portion of the data to the third enterprise include instructions that cause the processor to:

receive a request from the third enterprise; and

transmit the portion of the data to the third enterprise in response to the request.

11. The system of claim 10, wherein the request is for new data.

12. The system of claim 1, wherein the portion of the data is refrained from being transmitted to the third enterprise in response to a fourth enterprise in the federation transmitting the portion of the data to the third enterprise.

13. The system of claim 12, wherein the third enterprise is configured to select between the first enterprise and the fourth enterprise from which to receive the portion of the data, and transmit a request to the fourth enterprise instead of the first enterprise for the data.

14. The system of claim 1, wherein the second enterprise is configured to select between the first enterprise and a fourth enterprise from which to receive the portion of the data, and transmit a request to the first enterprise instead of the fourth enterprise for the data.

15. The system of claim 1, wherein the instructions further cause the processor to:

determine access rights of the second and third enterprises to the portion of the data;

transmit the portion of the data to the second enterprise in response to determining that the second enterprise has access rights to the portion of the data; and

refrain from transmitting the portion of the data to the third enterprise in response to determining that the third enterprise does not have access rights to the portion of the data.

16. A method for managing data flow between a plurality of enterprises in a federation comprising:

admitting, by a processor in a first enterprise, a requesting entity into the federation;

identifying, by the processor, data to be provided to the plurality of enterprises in the federation in response to admitting the requesting entity into the federation;

identifying, by the processor, a rule for managing data flow between the plurality of enterprises; and

throttling, by the processor, transmission of the data to the plurality of the enterprises in the federation based on rules for managing data flow to the plurality of enterprises in the federation, wherein the instructions that cause the processor to throttle transmission of the data includes instructions that cause the processor to transmit at least a portion of the data to a second enterprise of the plurality of enterprises in the federation, and refrain from transmitting the portion of the data to a third enterprise of the plurality of enterprises in the federation.

17. The method of claim 16, wherein the rule includes conditions for assigning bandwidth for transmitting the identified data, the method further comprising:

identifying, by the processor, a type of data contained in the portion of the identified data;

identifying, by the processor, a first bandwidth allocated to the type of data based on the rule; and

transmitting, by the processor, portion of the data to the second enterprise in accordance with the allocated first bandwidth.

18. The method of claim 17, further comprising:

identifying, by the processor, a second bandwidth allocated to a second portion of the identified data based on the rule, wherein the second bandwidth is different from the first bandwidth; and

transmitting, by the processor, the second portion of the identified data in accordance with the allocated second bandwidth.

19. The method of claim 16, further comprising:

transmitting, by the processor, a first notification to the second enterprise prior to transmitting the portion of the identified data to the second enterprise;

waiting for a second notification from the second enterprise; and

transmitting, by the processor, the portion of the identified data in response to receipt of the second notification.

20. The method of claim 19, wherein the second notification specifies timing of transmission of data to the second enterprise, wherein the processor is configured to transmit the portion of the identified data in accordance with the specified timing.