FEDERATED ACCESS

• US 20150106142A1
• Filed: 12/17/2014
• Published: 04/16/2015
• Est. Priority Date: 12/31/2007
• Status: Abandoned Application

• 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
• Application Number:
  US14/574,377
• Publication Number:
  US 20150106142A1
• Time in Patent Office: Days
• US Class Current: 705/7.12
• 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 operating in a first enterprise, comprising:

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;

wherein 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.

2. The system of claim 1 wherein communication, workflow and data exchange is accomplished after federation through the paired federation proxy interfaces.

3. The system of claim 1 wherein configuration details include at least agent identities and contact information.

4. The system of claim 3 wherein federation is accomplished by the first enterprise with two or more second enterprises, and after federation configuration details concerning one of the second enterprises are shared with the other of the second enterprises.

5. The system of claim 4 wherein the two second enterprises are enabled to federate, communicate and share work and data directly, rather than only through the first enterprise.

6. The system of claim 2 wherein work assignments are pushed from the first enterprise to the second enterprise.

7. The system of claim 2 wherein work assignments are pulled by the second enterprise from the first enterprise.

8. The system of claim 7 wherein the second enterprise bids on work assignments against other enterprises.

9. The system of claim 1 wherein, in negotiating for federation, a third party certifying authority is consulted.

10. The system of claim 1 wherein software enabling federation is proprietary to the first enterprise which retains control for distribution and licensing.

11. The system of claim 1 wherein software enabling federation is acquired and licensed from a third party, other than the first or second enterprises.

12. A federation method comprising steps of:

(a) a second enterprise connecting to a first enterprise through a federation registrar at the first enterprise;

(b) negotiating details of federation between the first and the second enterprise;

(c) storing details of the federation in a configuration database by a configuration server; and

(d) coupling the first and the second enterprise through a pair of federation proxy interfaces, one at the first enterprise and one at the second enterprise, the federation proxy interfaces configured by details of the federation.

13. The method of claim 12 including a step for exchanging workflow and data after federation through the paired federation proxy interfaces.

14. The method of claim 12 wherein configuration details include at least agent identities and contact information.

15. The method of claim 14 wherein federation is accomplished by the first enterprise with two or more second enterprises, and after federation configuration details concerning one of the second enterprises are shared with the other of the second enterprises.

16. The method of claim 15 including a step for enabling the two second enterprises to federate, communicate and share work and data directly, rather than only through the first enterprise.

17. The method of claim 13 including a step for pushing work assignments from the first enterprise to the second enterprise.

18. The method of claim 13 including a step for pulling work assignments from the first enterprise by the second enterprise.

19. The method of claim 18 wherein the second enterprise bids on work assignments against other enterprises.

20. The method of claim 12 wherein, in negotiating for federation, a third party certifying authority is consulted.

21. (canceled)

22. (canceled)