USER PORTAL TO A HUB-BASED SYSTEM FEDERATING DISPARATE UNIFIED COMMUNICATIONS SYSTEMS

• US 20140359457A1
• Filed: 05/30/2013
• Published: 12/04/2014
• Est. Priority Date: 05/30/2013
• Status: Abandoned Application

• Current Assignee: Nextplane, Inc.
• Original Assignee: Nextplane, Inc.
• Inventors: Bellan, Saravanan, Shahidi, Farzin, Pujare, Sanjay, Raina, Yogesh, Talla, Venky
• Application Number:
  US13/906,311
• Publication Number:
  US 20140359457A1
• Time in Patent Office: Days
• US Class Current: 715/736
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Abstract

An apparatus for managing connections of a hub-based federation system. The apparatus includes a user interface for receiving input from a user and a logic component for generating a checklist of action items based on the user input. The apparatus also includes a task manager for managing the checklist as a task and a hub interface for communicating with a hub capable of federating a plurality of unified communications systems.

Claims

1. An apparatus for managing connections of a hub-based federation system, the apparatus comprising:

a user interface for receiving input from a user;

a logic component for generating a checklist of action items based on the user input;

a task manager for managing the checklist as a task; and

a hub interface for communicating with a hub capable of federating a plurality of unified communications systems.

2. The apparatus of claim 1, wherein receiving input from a user includes receiving a request to provision a domain associated with a unified communications system.

3. The apparatus of claim 2, wherein generating a checklist of action items includes generating a domain provision readiness checklist based on the type of the unified communications system.

4. The apparatus of claim 2, wherein communicating with the hub includes configuring the hub to establish a connection with the unified communications system.

5. The apparatus of claim 2, wherein managing the checklist as a task includes providing the checklist as a task to the user.

6. The apparatus of claim 2, wherein communicating with the hub includes instructing the hub to send a validation message to the unified communications system when the task manager receives an indication that action items on the generated checklist have been completed.

7. The apparatus of claim 1, wherein receiving input from a user includes receiving a request to establish federation link between a first unified communications system and a second unified communications system.

8. The apparatus of claim 7, wherein generating a checklist of action items includes:

generating a first federation readiness checklist based on the type of the first unified communications system; and

generating a second federation readiness checklist based on the type of the second unified communications system.

9. The apparatus of claim 8, wherein managing the checklist as a task includes:

providing the first federation readiness checklist as a task to the user; and

providing the second federation readiness checklist as a task to an administrator of the second unified communications system.

10. The apparatus of claim 7, wherein communicating with the hub includes configuring the hub to establish a federation link between the first and second unified communications systems.

11. The apparatus of claim 1, wherein receiving input from a user includes receiving a request to provision a service for a domain associated with the user.

12. The apparatus of claim 11 further comprising a service manager for determining whether the user is entitled to the service.

13. The apparatus of claim 11, wherein generating a checklist of action items includes generating a service provision checklist based on the type of the service.

14. The apparatus of claim 11, wherein communicating with the hub includes configuring the hub to enable the service for the domain.

15. The apparatus of claim 1, wherein communicating with the hub includes administering a policy to restrict inter-domain communications between users in a first domain and users in a second domain.

16. The apparatus of claim 1, wherein communicating with the hub includes administering a policy to automatically attach predetermined message content to inter-domain between users in a first domain and users in a second domain.

17. The apparatus of claim 1, wherein the appearance of the user interface is customizable based on the user'"'"'s association.

32. The method of claim 1, wherein communicating with the hub includes administering a policy to restrict inter-domain communications between users in a first domain and users in a second domain.

33. The method of claim 1, wherein communicating with the hub includes administering a policy to automatically attach predetermined message content to inter-domain between users in a first domain and users in a second domain.

18. A method for managing connections of a hub-based federation system, the method comprising:

receiving input from a user;

generating a checklist of action items based on the received user input;

managing the checklist as a task; and

communicating with a hub capable of federating a plurality of unified communications systems.

19. The method of claim 18, wherein receiving input from a user includes receiving a request to provision a domain associated with a unified communications system.

20. The method of claim 19, wherein generating a checklist of action items includes generating a domain provision readiness checklist based on the type of the unified communications system.

21. The method of claim 19, wherein communicating with the hub includes configuring the hub to establish a connection with the unified communications system.

22. The method of claim 19, wherein managing the checklist as a task includes providing the checklist as a task to the user.

23. The method of claim 19, wherein communicating with the hub includes instructing the hub to send a validation message to the unified communications system after receiving an indication that action items on the generated checklist have been completed.

24. The method of claim 18, wherein receiving input from a user includes receiving a request to establish federation link between a first unified communications system and a second unified communications system.

25. The method of claim 24, wherein generating a checklist of action items includes:

generating a first federation readiness checklist based on the type of the first unified communications system; and

generating a second federation readiness checklist based on the type of the second unified communications system.

26. The method of claim 25, wherein managing the checklist as a task includes:

providing the first federation readiness checklist as a task for the user; and

providing the second federation readiness checklist as a task for an administrator of the second unified communications system.

27. The method of claim 24, wherein communicating with the hub includes configuring the hub to establish a federation link between the first and second unified communications systems.

28. The method of claim 18, wherein communicating with the user includes receiving a request to provision a service for a domain associated with the user.

29. The method of claim 28 further comprising determining whether the user is entitled to the service.

30. The method of claim 28, wherein generating a checklist of action items includes generating a service provision checklist based on the type of the service.

31. The method of claim 28, wherein communicating with the hub includes configuring the hub to enable the service for the domain.