Multi-tenancy support in a cloud based data grid

US2016149882A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016149882-A1
Application numberUS-201414552927-A
CountryUS
Kind codeA1
Filing dateNov 25, 2014
Priority dateNov 25, 2014
Publication dateMay 26, 2016
Grant date

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 system with a tenant aware in-memory data grid includes a data grid configured to store data in memory. A request manager is configured to receive a data grid label and a tenant identifier and to request a data grid entry based on the data grid label and tenant identifier. A data grid controller is configured to receive a request for data from the data grid based on a combined data grid label and tenant identifier. A security provider is configured to authenticate and authorize the request for data.

First claim

Opening claim text (preview).

What is claimed is: 1 . A system of providing a tenant aware in-memory data grid comprising: a data grid configured to store data in memory; a request manager configured to receive a data grid label and a tenant identifier and to request a data grid entry based on the data grid label and tenant identifier; a data grid controller configured to receive a request for data from the data grid based on a combined data grid label and tenant identifier; and a security provider configured to authenticate and authorize the request for data. 2 . The system of claim 1 , wherein the request manager is further configured to receive requester identification information, wherein the security provider authenticates the request by checking a credential cache based on the requester identification information, and if no entry is returned, checking a credential store and creating an entry in the credential cache for the requester identification information. 3 . The system of claim 1 , wherein the data grid is an application memory cache. 4 . The system of claim 3 , wherein the tenant identifier is associated with a website and the requester is associated with an agent of the website. 5 . The system of claim 4 , wherein the application memory cache stores information about a visitor to the website. 6 . The system of claim 5 , wherein the data grid label is associated with a data grid entry for browser history of website visitors and the requester is a chat application used by the agent. 7 . The system of claim 1 , wherein the data grid request manager is further configured to: receive data, a second data grid label, and a second tenant identifier; determine if a tenant data grid element exists in the data grid based on the second data grid label and second tenant identifier; if not, create the tenant data grid element; and store the data in an entry in the data grid based on the tenant data grid element. 8 . A method of providing a tenant aware in-memory data grid, the method comprising: receiving a data grid label and a tenant identifier; requesting a data grid entry based on the data grid label and tenant identifier; authenticating and authorizing the request for the data grid entry; and providing the data grid entry. 9 . The method of claim 8 , further comprising: receiving requester identification information, wherein the authenticating includes checking a credential cache based on the requester identification information, and if no entry is returned, checking a credential store and creating an entry in the credential cache for the requester identification information. 10 . The method of claim 8 , wherein the data grid entry is an entry in an application memory cache. 11 . The method of claim 10 , wherein the tenant identifier is associated with a website and the requester is associated with an agent of the website. 12 . The method of claim 11 , wherein the application memory cache stores information about a visitor to the website. 13 . The method of claim 12 , wherein the data grid entry is for browser history of website visitors and the requester is a chat application used by the agent. 14 . The method of claim 8 , further comprising: receiving a data entry, a second data grid label, and a second tenant identifier; determining if a tenant data grid element exists in the data grid based on the second data grid label and second tenant identifier; if not, creating the tenant data grid element; and storing the data entry in the data grid based on the tenant data grid element. 15 . A computer readable medium with instructions stored thereon to provide an entry from a tenant aware in-memory data grid, the providing comprising: receiving a data grid label and a tenant identifier; requesting a data grid entry based on the data grid label and tenant identifier; authenticating and authorizing the request for the data grid entry; and providing the data grid entry. 16 . The computer readable medium of claim 15 , the providing further comprising: receiving requester identification information, wherein the authenticating includes checking a credential cache based on the requester identification information, and if no entry is returned, checking a credential store and creating an entry in the credential cache for the requester identification information. 17 . The computer readable medium of claim 15 , wherein the data grid entry is an entry in an application memory cache, and the tenant identifier is associated with a website and the requester is associated with an agent of the website. 18 . The computer readable medium of claim 17 , wherein the application memory cache stores information about a visitor to the website. 19 . The computer readable medium of claim 18 , wherein the data grid entry is for browser history of website visitors and the requester is a chat application used by the agent. 20 . The computer readable medium of claim 15 , the providing further comprising: receiving a data entry, a second data grid label, and a second tenant identifier; determining if a tenant data grid element exists in the data grid based on the second data grid label and second tenant identifier; if not, creating the tenant data grid element; and storing the data entry in the data grid based on the tenant data grid element.

Assignees

Inventors

Classifications

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

  • in the application layer [OSI layer 7] · CPC title

  • Interoperability with other network applications or services · CPC title

  • in semiconductor storage media, e.g. directly-addressable memories · CPC title

  • Entity profiles · 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 US2016149882A1 cover?
A system with a tenant aware in-memory data grid includes a data grid configured to store data in memory. A request manager is configured to receive a data grid label and a tenant identifier and to request a data grid entry based on the data grid label and tenant identifier. A data grid controller is configured to receive a request for data from the data grid based on a combined data grid label…
Who is the assignee on this patent?
Oracle Int Corp
What technology area does this patent fall under?
Primary CPC classification H04L63/08. Mapped technology areas include Electricity.
When was this patent published?
Publication date Thu May 26 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). 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).