Federated access

• US 8,949,470 B2
• Filed: 12/31/2007
• Issued: 02/03/2015
• 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): Gorney, Boris
• Application Number:
  US11/967,508
• Publication Number:
  US 20090172025A1
• Time in Patent Office: 2,591 Days
• Field of Search: 709223-226, 709/245, 709/249, 709/250, 707/10, 707/103.R, 707/103.X, 707/104.1
• US Class Current: 709/249
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 50/184 Intellectual property management
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

A federation system operating in a first enterprise includes a configuration server and a database for creating and storing federation configuration data and a federation registrar having an interface for dealing with a second enterprise seeking to federate. In the system the second enterprise connects to the federation registrar, negotiation takes place concerning details of federation, agreement is reached, configuration is stored in the configuration database, and the second enterprise is then coupled to the first enterprise through a pair of federation proxy interfaces, one at the first enterprise and one at the second enterprise, the proxy interfaces configured by details of the federation.

Claims

1. A federation system for dynamically managing a federation including a first enterprise, the system comprising:

one or more processors;

a storage device configured to store data related to the federation;

one or more memory devices, wherein the one or more memory devices have stored thereon instructions that, when executed by the one or more processors, cause the one or more processors to respectively;

receive at a publicly known access point, from a device at a second enterprise, a request to join the federation associated with the first enterprise;

authenticate and admit the second enterprise into the federation in response to the request;

determine access rights of the second enterprise within the federation in response to authenticating and admitting the second enterprise into the federation, wherein the determining of the access rights is based upon rules regarding requests received at the publicly known access point

store, in the storage device, the access rights of the second enterprise

transmit to the device the access rights granted to the second enterprise;

transmit to the device an address of a federation proxy interface for establishing contact with the federation;

receive contact from the device to the federation proxy interface; and

exchange data with the device via the federation proxy interface in accordance with the granted access rights.

2. The system of claim 1, wherein, the data includes data relating to communication or workflow between the first enterprise and the second enterprise.

3. The system of claim 1, wherein the second enterprise is a call center and the data includes configuration details including at least agent identities and contact information.

4. The system of claim 3, wherein the instructions further cause the processor to share the configuration details of the second enterprise with other enterprises within the federation.

5. The system of claim 4, wherein the second enterprise and the other enterprises are enabled to federate, communicate, and share work and data via corresponding federation proxies.

6. The system of claim 1, wherein the instructions further cause one of the one or processors to push work assignments to the second enterprise.

7. The system of claim 1, wherein the second enterprise is configured to pull work assignments from the first enterprise.

8. The system of claim 1, wherein the second enterprise is configured to bid on work assignments against other enterprises within the federation.

9. The system of claim 1, wherein the program instructions for authenticating including program instructions that cause one of the one or more processors to consult a third party certifying authority.

10. The system of claim 1, wherein, after the second enterprise joins the federation, the instructions cause one of the one or more processors to outsource work from the first enterprise to the second enterprise.

11. The system of claim 1, wherein a degree and a type of the data the first enterprise shares with the second enterprise are determined by the rules.

12. The system of claim 1, wherein propagation of the data of the first enterprise and the second enterprise within the federation is restricted by the first enterprise and the second enterprise, respectively.

13. The system of claim 4, wherein different subsets of the configuration details are shared with different ones of the other enterprises.

14. A federation method for dynamically managing a federation including a first enterprise, the method comprising:

receiving at a publicly known access point provided by a computer system, from a device at a second enterprise, a request to join the federation associated with the first enterprise;

authenticating and admitting, by the computer system, the second enterprise into the federation in response to the request;

determining, by the computer system, access rights of the second enterprise within the federation in response to authenticating and admitting the second enterprise into the federation, wherein the determining of the access rights is based upon rules regarding requests received at the publicly known access point;

storing, by the computer system, in the storage device, the access rights of the second enterprise

transmitting, by the computer system, to the device, the access rights granted to the second enterprise;

transmitting, by the computer system, to the device, an address of a federation proxy interface for establishing contact with the federation;

receiving, by the computer system, contact from the device to the federation proxy interface; and

exchanging, by the computer system, data with the device via the federation proxy interface in accordance with the granted access rights.

15. The method of claim 14, wherein, the data includes data relating to communication or workflow between the first enterprise and the second enterprise.

16. The method of claim 14, wherein the data includes configuration details including at least agent identities and contact information.

17. The method of claim 16 further comprising sharing the configuration details of the second enterprise with other enterprises within the federation.

18. The method of claim 17, wherein the second enterprise and the other enterprises are enabled to federate, communicate, and share work and data via corresponding federation proxy interfaces.

19. The method of claim 14, further comprising pushing, via the federation proxy interface, work assignments to the second enterprise.

20. The method of claim 14, wherein the second enterprise is configured to pull work assignments from the first enterprise.

21. The method of claim 14, wherein the second enterprise is configured to bid on work assignments against other enterprises within the federation.

22. The method of claim 14, wherein the authenticating includes consulting, by one of the one or more processors, a third party certifying authority.