BRIDGING ON PREMISE AND CLOUD SYSTEMS VIA CANONICAL CACHE

• US 20140122569A1
• Filed: 10/30/2012
• Published: 05/01/2014
• Est. Priority Date: 10/30/2012
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Abel, Todd J., Pan, Zhengkai Kenneth, James, David C., Healy, Michael, Flegg, Brett D.A.
• Application Number:
  US13/664,001
• Publication Number:
  US 20140122569A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Sending data using a remote based cache. A method includes receiving at a remote based cache, data from a first system. The data from the first system is intended for a second system. The method further includes caching the data from the first system that is intended for the second system at the cache. The method further includes providing the data from the cache to a third system prior to the data being provided to the second system.

Claims

1. In a computing environment, a method of sending data, the method comprising:

receiving at a remote based cache, data from a first system, wherein the data from the first system is intended for a second system;

caching the data from the first system that is intended for the second system at the cache; and

providing the data from the cache to a third system prior to the data being provided to the second system.

2. The method of claim 1, wherein caching the data from the first system comprises caching the data in a canonical form such that different data consumers can consume the data in a uniform way including when the different data consumers are not specifically designed to interoperate with each other.

3. The method of claim 1, wherein the first system is a client system, the second system is a remote based client management system and the third system is an on-premises client management system.

4. The method of claim 1, wherein the first system is a client system, the second system is an on-premise based client management system and the third system is a remote based client management system.

5. The method of claim 1, wherein the first system is a client management system, the second system is client system and the third system is a client system.

6. The method of claim 1, wherein the data comprises policy information.

7. The method of claim 1, wherein the data comprises configuration information.

8. A computing system comprising:

one or more processors; and

one or more computer readable media, wherein the one or more computer readable media comprise computer executable instructions that when executed by at least one of the one or more processors cause at least one of the one or more processors to perform the following;

receiving at a remote based cache, data from a first system, wherein the data from the first system is intended for a second system;

caching the data from the first system that is intended for the second system at the cache; and

providing the data from the cache to a third system prior to the data being provided to the second system.

9. The computing system of claim 8, wherein caching the data from the first system comprises caching the data in a canonical form such that different data consumers can consume the data in a uniform way including when the different data consumers are not specifically designed to interoperate with each other.

10. The computing system of claim 8, wherein the first system is a client system, the second system is a remote based client management system and the third system is an on-premises client management system.

11. The computing system of claim 8, wherein the first system is a client system, the second system is an on-premise based client management system and the third system is a remote based client management system.

12. The computing system of claim 8, wherein the first system is a client management system, the second system is client system and the third system is a client system.

13. The computing system of claim 8, wherein the data comprises policy information.

14. The computing system of claim 8, wherein the data comprises configuration information.

15. A computing system comprising:

a remote based client management system deployed in a remote environment, the client management system configured to provide policy information to clients; and

a remote based cache deployed in the remote environment, the remote based cache configured to receive policy information from the remote based client management system for clients of the remote based client management system and to cache the policy information prior to the policy information being sent to the clients of the remote based client management system, such that a different system is able to access the policy information prior to the clients of the remote based client management system receiving the policy information.

16. The computing system of claim 15, further comprising a self service module configured to allow a user to manually insert policy information into the remote based cache.

17. The computing system of claim 15, wherein the remote based cache is a canonical cache such that data is cached in a canonical form such that different data consumers can consume the data in a uniform way including when the different data consumers are not specifically designed to interoperate with each other.

18. The computing system of claim 15, wherein the remote based cache is further configured to receive configuration from clients of the client management system.

19. The computing system of claim 15, wherein the remote based cache is a multi-enterprise cache, but wherein the remote based cache is walled-off on an enterprise basis such that entities can only view portions of the cache for enterprises to which they belong.

20. The computing system of claim 15, wherein the remote based cache comprises entity based access restrictions.