CONSOLIDATING DISPARATE CLOUD SERVICE DATA AND BEHAVIOR BASED ON TRUST RELATIONSHIPS BETWEEN CLOUD SERVICES

• US 20130204994A1
• Filed: 05/30/2012
• Published: 08/08/2013
• Est. Priority Date: 02/06/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: DESHMUKH, ABHIJIT, SRIVASTAVA, ANURAG
• Granted Patent: US 8,826,408 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations

Abstract

A method for consolidating cloud service data and behaviors can begin with the compilation of user/service membership data that associates requesting entities with subscribed cloud services by a trusted cloud service consolidator. A federated trust library housing inter-service trust information for the cloud services contained in the user/service membership data can be created. In response to a service request from a requesting entity, trusted secondary cloud services can be identified for the requesting entity. Identification of the trusted secondary cloud services can be based upon trust factors synthesized from data contained in the federated trust library. Data satisfying the service request and associated behaviors from each trusted secondary cloud service can then be consolidated into a unified data structure. A behavior can be an executable action supported by a trusted secondary cloud service. The unified data structure can be conveyed to the requesting entity in a service response.

Claims

1. A method for consolidating cloud service data and behaviors comprising:

compiling of user/service membership data that associates a plurality of requesting entities with cloud services to which the plurality of requesting entities subscribe by a trusted cloud service consolidator;

creating a federated trust library of inter-service trust information for the cloud services contained in the user/service membership data;

in response to a service request from a requesting entity, identifying trusted secondary cloud services for the requesting entity, wherein the trusted secondary cloud services correspond to those cloud services that are associated with the requesting entity in the user/service membership data, wherein the trusted secondary cloud services are not a target of the service request, and, wherein said identification is based upon trust factors synthesized from data contained in the federated trust library;

consolidating data satisfying the service request and associated behaviors from each trusted secondary cloud service into a unified data structure, wherein a behavior is an executable action supported by a trusted secondary cloud service, wherein said behavior is executable upon the data satisfying the service request obtained from the trusted secondary cloud service; and

conveying the unified data structure to the requesting entity in a service response.

2. The method of claim 1, wherein compiling the user/service membership data further comprises:

for each requesting entity, identifying the cloud services to which the requesting entity subscribes; and

recording an association between the requesting entity and each identified cloud service in the user/service membership data.

3. The method of claim 1, wherein creating the federated trust library further comprises:

requesting inter-service trust information from each cloud service contained in the user/service membership data; and

upon receipt of the requested inter-service trust information, storing the inter-service trust information in the federated trust library.

4. The method of claim 1, wherein identifying the trusted secondary cloud services further comprises:

receiving the service request from the requesting entity, wherein the service request is for a specified cloud service and includes a plurality of contextual data;

determining a trust factor for the received service request using the plurality of contextual data, wherein the trust factor defines a confidence level that contents included in the service response must meet;

identifying secondary cloud services that the requesting entity consumed from the user/service membership data, wherein the specified cloud service is excluded from the secondary cloud services;

calculating trust factors for relationships between the specified cloud service and each identified secondary cloud service from the federated trust library;

comparing the calculated trust factors of the secondary cloud services with the trust factor of the service request; and

designating the identified secondary cloud services whose calculated trust factors satisfy the trust factor for the service request as trusted secondary cloud services.

5. The method of claim 1, further comprising:

periodically determining a validity of data contained within the user/service membership data and federated trust library;

when data is found to be invalid, modifying a corresponding entry of the user/service membership data or federated trust library accordingly.

6. The method of claim 1, further comprising:

presenting the unified data structure to the requesting entity in a user interface, wherein behaviors contained in the unified data structure are selectable within the user interface.

7. The method of claim 1, wherein the identification of trusted secondary cloud services and the consolidation of trusted secondary cloud service data and behaviors is performed in at least one of real-time and near real-time.