Cloud federation as a service

US9749398B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9749398-B2
Application numberUS-201414584744-A
CountryUS
Kind codeB2
Filing dateDec 29, 2014
Priority dateDec 17, 2009
Publication dateAug 29, 2017
Grant dateAug 29, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A Cloud federator may be used to allow seamless and transparent access by a Cloud Client to Cloud services. Federation may be provided on various terms, including as a subscription based real-time online service to Cloud Clients. The Cloud federator may automatically and transparently effect communication between the Cloud Client and Clouds and desired services of the Clouds, and automatically perform identity federation. A Service Abstraction Layer (SAL) may be implemented to simplify Client communication, and Clouds/Cloud services may elect to support the SAL to facilitate federation of their services.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving a request from a cloud-based client computing device to access a first service of a first cloud-based server computing device and a second service of a second cloud-based server computing device; validating the cloud-based client computing device to access the first and second services, wherein validating includes establishing a single access account for the cloud-based client computing device to simultaneously access multiple services from multiple cloud service providers across a cloud network, wherein the single access account offers a single avenue for automatic migration of data relating to the multiple services and dynamic interoperability between the multiple service providers, wherein the multiple services includes the first and second services, and wherein the multiple cloud service providers include the first and second cloud-based server computing devices; determining an interface preference associated with the cloud-based client computing device; identifying a first interface of the first cloud-based server computing device corresponding to the interface preference; and mapping data between the cloud-based client computing device and the first cloud-based server computing device to make data from the first cloud-based server computing device having a first format to be in accord with the interface preference. 2. The method of claim 1 , in which the first service is based on a first access term, the method further comprising: receiving another request from the cloud-based client computing device to access a third service of a third cloud-based server computing device, the third service based on a second access term different from the first access term; and validating the cloud-based client computing device to access the third cloud service, wherein validating is based on the single access account to simultaneously access the multiple services from the multiple cloud service providers across the cloud network, wherein the multiple services includes the third services and wherein the multiple cloud service providers include the third cloud-based server computing device, wherein validating the cloud-based client computing device to access one or more of the first, second, and third services from one or more of the first, second, and third cloud-based server computing devices, respectively, based at least in part on the first and second access terms. 3. The method of claim 2 , wherein one or more of the first, second, and third services are accessed in real-time. 4. A non-transitory machine-readable medium comprising instructions which, when executed by a machine, cause the machine to perform operations comprising: receiving a request from a cloud-based client computing device to access a first service of a first cloud-based server computing device and a second service of a second cloud-based server computing device; validating the cloud-based client computing device to access the first and second services, wherein validating includes establishing a single access account for the cloud-based client computing device to simultaneously access multiple services from multiple cloud service providers across a cloud network, wherein the single access account offers a single avenue for automatic migration of data relating to the multiple services and dynamic interoperability between the multiple service providers, wherein the multiple services includes the first and second services, and wherein the multiple cloud service providers include the first and second cloud-based server computing devices; determining an interface preference associated with the Cloud Client; identifying a first interface of the first Cloud corresponding to the interface preference; and mapping data between the Cloud Client and the first Cloud to make data from the first Cloud having a first format to be in accord with the interface preference. 5. The non-transitory machine-readable medium of claim 4 , in which the first service is based on a first access term, the operations further comprise: receiving another request from the cloud-based client computing device to access a third service of a third cloud-based server computing device, the third service based on a second access term different from the first access term; and validating the cloud-based client computing device to access the third cloud service, wherein validating is based on the single access account to simultaneously access the multiple services from the multiple cloud service providers across the cloud network, wherein the multiple services includes the third services and wherein the multiple cloud service providers include the third cloud-based server computing device, wherein validating the cloud-based client computing device to access one or more of the first, second, and third services from one or more of the first, second, and third cloud-based server computing devices, respectively, based at least in part on the first and second access terms. 6. The non-transitory machine-readable medium of claim 5 , wherein one or more of the first, second, and third services are accessed in real-time.

Assignees

Inventors

Classifications

  • Entity profiles · CPC title

  • considering software capabilities, i.e. software resources associated or available to the machine · CPC title

  • providing single-sign-on or federations · CPC title

  • Electricity · mapped topic

  • H04L67/10Primary

    in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9749398B2 cover?
A Cloud federator may be used to allow seamless and transparent access by a Cloud Client to Cloud services. Federation may be provided on various terms, including as a subscription based real-time online service to Cloud Clients. The Cloud federator may automatically and transparently effect communication between the Cloud Client and Clouds and desired services of the Clouds, and automatically …
Who is the assignee on this patent?
Intel Corp
What technology area does this patent fall under?
Primary CPC classification H04L67/10. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 29 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).