Approach For Accessing Third-Party Content Collaboration Services On Interactive Whiteboard Appliances By An Application Using A Wrapper Application Program Interface
First Claim
1. An apparatus comprising:
- one or more processors, andone or more memories storing instructions which, when processed by the one or more processors, cause a management service to;
receive, from an application executing on an Interactive Whiteboard (IWB) appliance, a first request to perform a content collaboration function on a first collaboration service that is external to both the application executing on the IWB appliance and the apparatus, wherein the first request conforms to a common application program interface (API) that is supported by the management service and not supported by the first collaboration service,generate, based upon the first request to perform a collaboration function on a first collaboration service that is external to both the IWB appliance and the apparatus, and API data managed by the management service that defines requirements of an API of the first collaboration service, a second request to perform the content collaboration function on the first collaboration service that is external to both the IWB appliance and the apparatus, wherein the second request satisfies requirements of the API supported by the first collaboration service and not the common API supported by the management service; and
cause the second request to perform the content collaboration function on the first collaboration service to be transmitted to the first collaboration service for processing.
1 Assignment
0 Petitions
Accused Products
Abstract
An approach for managing collaboration on IWBs allows users of different third-party collaboration services to participate in collaboration meetings on IWBs. The approach allows the users to use collaboration functionality provided by IWBs, such as annotation, and to communicate with each other, even though the users are using different third party collaboration services. The approach uses a collaboration manager that provides a “single wrapper” application program interface (API) and centralized management of collaboration meetings, including license key and token management, cross-license collaboration, user management and meeting management. The collaboration manager acts as a mediation layer that handles the APIs of different third-party collaboration services and allows users using heterogeneous collaboration clients to participate in collaboration meetings.
26 Citations
20 Claims
-
1. An apparatus comprising:
-
one or more processors, and one or more memories storing instructions which, when processed by the one or more processors, cause a management service to; receive, from an application executing on an Interactive Whiteboard (IWB) appliance, a first request to perform a content collaboration function on a first collaboration service that is external to both the application executing on the IWB appliance and the apparatus, wherein the first request conforms to a common application program interface (API) that is supported by the management service and not supported by the first collaboration service, generate, based upon the first request to perform a collaboration function on a first collaboration service that is external to both the IWB appliance and the apparatus, and API data managed by the management service that defines requirements of an API of the first collaboration service, a second request to perform the content collaboration function on the first collaboration service that is external to both the IWB appliance and the apparatus, wherein the second request satisfies requirements of the API supported by the first collaboration service and not the common API supported by the management service; and cause the second request to perform the content collaboration function on the first collaboration service to be transmitted to the first collaboration service for processing. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. One or more non-transitory computer-readable media storing instructions which, when processed by one or more processors, cause:
a management service executing on one or more computing devices to; receive, from an application executing on an Interactive Whiteboard (IWB) appliance, a first request to perform a content collaboration function on a first collaboration service that is external to both the application executing on the IWB appliance and the one or more computing devices, wherein the first request conforms to a common application program interface (API) that is supported by the management service and not supported by the first collaboration service, generate, based upon the first request to perform a collaboration function on a first collaboration service that is external to both the IWB appliance and the one or more computing devices, and API data managed by the management service that defines requirements of an API of the first collaboration service, a second request to perform the content collaboration function on the first collaboration service that is external to both the IWB appliance and the one or more computing devices, wherein the second request satisfies requirements of the API supported by the first collaboration service and not the common API supported by the management service; and cause the second request to perform the content collaboration function on the first collaboration service to be transmitted to the first collaboration service for processing. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
19. A computer-implemented method comprising:
a management service executing on one or more computing devices; receiving, from an application executing on an Interactive Whiteboard (IWB) appliance, a first request to perform a content collaboration function on a first collaboration service that is external to both the application executing on the IWB appliance and the one or more computing devices, wherein the first request conforms to a common application program interface (API) that is supported by the management service and not supported by the first collaboration service, generating, based upon the first request to perform a collaboration function on a first collaboration service that is external to both the IWB appliance and the one or more computing devices, and API data managed by the management service that defines requirements of an API of the first collaboration service, a second request to perform the content collaboration function on the first collaboration service that is external to both the IWB appliance and the one or more computing devices, wherein the second request satisfies requirements of the API supported by the first collaboration service and not the common API supported by the management service; and causing the second request to perform the content collaboration function on the first collaboration service to be transmitted to the first collaboration service for processing. - View Dependent Claims (20)
Specification