IP Library Granted Patent US 11,375,037
Granted Patent B2
US 11,375,037 · App. 17/149,518 · Granted Jun 28, 2022

Systems and methods for caching of managed content in a distributed environment using a multi-tiered architecture

Inventors: Nicolae Ionescu (Toronto, CA); Dan-Horia Trufasiu (Newmarket, CA); Peter Varga (Markham, CA); Tao Zhou (Richmond Hill, CA); Franz Pauthner (Zorneding, DE); Yue Kuk Wong (Toronto, CA)
Assignee: OPEN TEXT SA ULC
H04L67/2842G06F16/172G06F16/173G06F16/2329G06F16/2474H04L67/1097
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,375,037
App. No.
17/149,518
Granted
Jun 28, 2022
Kind
B2
Abstract

Embodiments as disclosed provide a distributed caching solution that improve the performance and functionality of a content management platform for sites that are physically or logically remote from the primary site of the content management platform. In particular, according to embodiments, a remote cache server may be associated with a remote site to store local copies of documents that are managed by the primary content management platform. Periodically, a portion of the remote site's cache may be synchronized with the content management platform's primary site using an extensible architecture to ensure that content at the remote cache server is current.

Claims (73)

1. A system for caching, comprising:

a cache system for use with a first content management system that manages content, including:

a processor;

a data store comprising a cache and metadata corresponding to content stored in the cache, wherein the content in cache comprises content managed by the first content management system; and

a non-transitory computer readable medium comprising instructions for:

accessing the data store to determine if first metadata associated with first content is stored in the data store;

sending a first request associated with the first content management system based on the determination if first metadata associated with the first content is stored in the data store;

receiving a first response including second metadata;

comparing the first metadata to the second metadata to determine if a version of the first content stored in the cache is a current version of the first content;

when the version of the first content stored in the cache is the current version, accessing the first content in the cache; and

when the version of the first content stored in the cache is not the current version:

sending a second request for the current version of the first content;

receiving the current version of the first content;

storing the current version of the first content in the cache; and

providing the current version of the first content in response to a third request, wherein the first content management system is adapted for:

receiving the first request associated with the first content;

obtaining second metadata associated with the first content;

returning the first response, including the second metadata;

receiving the second request for the current version of the first content;

obtaining the current version of the first content; and

returning the current version of the first content.

2. The system of claim 1 , wherein the first content is designated for storage in the cache by a first user.

3. The system of claim 1 , wherein the first content is stored in the cache in response to the third request, and the third request is associated with access to the content.

4. The system of claim 3 , wherein the third request was associated with an application at a client device.

5. The system of claim 4 , wherein the third request is a save request or a read request.

6. The system of claim 1 , wherein the cache system is a second content management system.

7. The system of claim 6 , wherein the second content management system is deployed at a site remote from the content management system.

8. A method for remote caching, comprising:

accessing a data store at a cache system to determine if first metadata associated with first content is stored in the data store, wherein the cache system is for use with a first content management system that manages content and the data store comprises a cache and metadata corresponding to content stored in the cache and the content in cache comprises content managed by the first content management system, including the first content;

sending a first request associated with the first content management system based on the determination if first metadata associated with the first content is stored in the data store;

receiving a first response including second metadata;

comparing the first metadata to the second metadata to determine if a version of the first content stored in the cache is a current version of the first content;

when the version of the first content stored in the cache is the current version, accessing the first content in the cache; and

when the version of the first content stored in the cache is not the current version:

sending a second request for the current version of the first content;

receiving the current version of the first content;

storing the current version of the first content in the cache; and

providing the current version of the first content in response to a third request, wherein the first content management system is adapted for:

receiving the first request associated with the first content;

obtaining second metadata associated with the first content;

returning the first response, including the second metadata;

receiving the second request for the current version of the first content;

obtaining the current version of the first content; and

returning the current version of the first content.

9. The method of claim 8 , wherein the first content is designated for storage in the cache by a first user.

10. The method of claim 8 , wherein the first content is stored in the cache in response to the third request, and the third request is associated with access to the content.

11. The method of claim 10 , wherein the third request was associated with an application at a client device.

12. The method of claim 11 , wherein the third request is a save request or a read request.

13. The method of claim 8 , wherein the cache system is a second content management system.

14. The method of claim 13 , wherein the second content management system is deployed at a site remote from the content management system.

15. A non-transitory computer readable medium, comprising instructions for:

accessing a data store at a cache system to determine if first metadata associated with first content is stored in the data store, wherein the cache system is for use with a first content management system that manages content and the data store comprises a cache and metadata corresponding to content stored in the cache and the content in cache comprises content managed by the first content management system, including the first content;

sending a first request associated with the first content management system based on the determination if first metadata associated with the first content is stored in the data store;

receiving a first response including second metadata;

comparing the first metadata to the second metadata to determine if a version of the first content stored in the cache is a current version of the first content;

when the version of the first content stored in the cache is the current version, accessing the first content in the cache; and

when the version of the first content stored in the cache is not the current version:

sending a second request for the current version of the first content;

receiving the current version of the first content;

storing the current version of the first content in the cache; and

providing the current version of the first content in response to a third request, wherein the first content management system is adapted for:

receiving the first request associated with the first content;

obtaining second metadata associated with the first content;

returning the first response, including the second metadata;

receiving the second request for the current version of the first content;

obtaining the current version of the first content; and

returning the current version of the first content.

16. The non-transitory computer readable medium of claim 15 , wherein the first content is designated for storage in the cache by a first user.

17. The non-transitory computer readable medium of claim 15 , wherein the first content is stored in the cache in response to the third request, and the third request is associated with access to the content.

18. The non-transitory computer readable medium of claim 17 , wherein the third request was associated with an application at a client device.

19. The non-transitory computer readable medium of claim 18 , wherein the third request is a save request or a read request.

20. The non-transitory computer readable medium of claim 15 , wherein the cache system is a second content management system.

21. The non-transitory computer readable medium of claim 20 , wherein the second content management system is deployed at a site remote from the content management system.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 30, 2024
From: OPEN TEXT CORP.
To: CROWDSTRIKE, INC.
Reel/Frame 068121/0609 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2024
From: OPEN TEXT SA ULC
To: OPEN TEXT CORP.
Reel/Frame 067400/0102 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 12, 2021
From: IONESCU, NICOLAE; TRUFASIU, DAN-HORIA; VARGA, PETER; ZHOU, TAO; PAUTHNER, FRANZ; WONG, YUE KUK
To: OPEN TEXT SA ULC
Reel/Frame 055656/0494 →
Continuity (6)
Continuation 16727556 · Dec 26, 2019
Continuation 16006317 · Jun 12, 2018
Continuation 15094524 · Apr 8, 2016
Provisional Application 62296329 · Feb 17, 2016
Provisional Application 62146030 · Apr 10, 2015
Related Publication 20210136172A1 · May 6, 2021
Cited By (1)
US 12,328,374