IP Library Granted Patent US 9,367,646
Granted Patent B2
US 9,367,646 · App. 13/827,504 · Granted Jun 14, 2016

Document and user metadata storage

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 9,367,646
App. No.
13/827,504
Granted
Jun 14, 2016
Kind
B2
Abstract

Techniques are disclosed for providing services to a client device via a shared cloud service. In one embodiment, a method is disclosed that includes storing information on a first device relating to a subject, saving the stored information in a serialized format data file to the shared cloud service, the data file having a filename generated as a function of the subject, providing authenticated access to the data file for a second device via the shared cloud service, synchronizing a copy of the data file via the shared cloud service to the second device, the copied data file reflecting a single up-to-date state of the data file in the shared cloud service, and de-serializing the serialized format data file at the second device.

Claims (65)

1. A computerized method for providing services to a client device via a shared cloud service, the method comprising:

determining, at a second device, selection criteria for suggestion of relevant documents to a local user of the second device, including a set of keywords;

synchronizing, to the shared cloud service, the selection criteria as a first serialized data file;

receiving at a first device the first serialized data file, wherein the first device is a computer system that includes a memory and a processor;

creating metadata relating to a subject on the first device in response to a remote content file on the first device being opened and the remote content file including one or more of the selection criteria from the first serialized data file, the metadata including data indicative of one or more keywords occurring in the remote content file and document metadata identifying the file;

saving the created metadata in a second serialized format data file to the shared cloud service, the second serialized data file having a filename generated as a function of the subject and is saved separately from the subject;

identifying the subject using a globally-unique identifier for a file, wherein the globally-unique identifier is embedded in the filename of the second serialized data file, thereby identifying the subject of the second serialized data file by the filename so that the metadata can be located in a particular location on the shared cloud service using the filename, wherein the second serialized data file is in a Javascript Object Notation data format (JSON);

providing, by identifying a globally-unique identifier for the local user (UserGuid), authenticated access to the second serialized data file for the second device via the shared cloud service, wherein the UserGuid is used for tracking all statistics regarding file accesses associated with the local user;

synchronizing a copy of the second serialized data file via the shared cloud service to the second device, the copy of the second serialized data file reflecting a single up-to-date state of the second serialized data file in the shared cloud service;

de-serializing the second serialized data file at the second device to generate a de-serialized data file;

determining, at the second device, using the metadata from the de-serialized data file, and the selection criteria that the remote content file is a relevant document, wherein the remote content file has been identified based on the metadata of the remote content file and the selection criteria determined at the second device; and

suggesting, by the second device, the remote content file to the local user in response to the determined selection criteria in a table of suggestions.

2. The method of claim 1 , wherein the subject comprises one of a user and a file.

3. The method of claim 1 , further comprising copying the de-serialized data file into a database at the second device.

4. The method of claim 1 , further comprising collecting the metadata relating to the subject at the first device.

5. The method of claim 1 , further comprising sharing the second serialized data file among a plurality of users of the shared cloud service.

6. The method of claim 1 , further comprising saving the second serialized data file in a metadata directory in a file hierarchy at the shared cloud service.

7. The method of claim 1 , further comprising:

applying an action corresponding to the metadata at a second subject at the second device; and

synchronizing a result of the action with the first device.

8. The method of claim 7 , wherein applying the action comprises searching a keyword.

9. A non-transitory computer readable medium having executable instructions operable to cause an apparatus to:

determine, at a second device, selection criteria for suggestion of relevant documents to a local user of the second device, including a set of keywords;

synchronize, to the shared cloud service, the selection criteria as a first serialized data file;

receive at a first device the first serialized data file;

create metadata relating to a subject on the first device in response to a remote content file on the first device being opened and the remote content file including one or more of the selection criteria from the first serialized data file, the metadata including data indicative of one or more keywords occurring in the remote content file and document metadata identifying the file;

save the created metadata in a second serialized format data file to the shared cloud service, the second serialized data file having a filename generated as a function of the subject and is saved separately from the subject;

identify the subject using a globally-unique identifier, wherein the globally-unique identifier is embedded in the filename of the second serialized data file, thereby identifying the subject of the second serialized data file by the filename so that the metadata can be located in a particular location on the shared cloud service using the filename, wherein the second serialized data file is in a Javascript Object Notation data format (JSON);

provide, by using a globally-unique identifier for the local user (UserGuid), authenticated access to the second serialized data file for the second device via the shared cloud service, wherein the userGuid is used for tracking all statistics regarding file accesses associated with the local user;

synchronize a copy of the second serialized data file via the shared cloud service to the second device, the copy of the second serialized data file reflecting a single up-to-date state of the second serialized data file in the shared cloud service;

de-serialize the second serialized data file at the second device to generate a de-serialized data file;

determine, at the second device, using the metadata from the de-serialized data file, and the selection criteria that the remote content file is a relevant document, wherein the remote content file has been identified based on the metadata of the remote content file and the selection criteria determined at the second device; and

suggest, by the second device, the remote content file to the local user in response to the determined selection criteria in a table of suggestions.

10. The non-transitory computer readable medium of claim 9 , wherein the subject comprises one of a user and a file.

11. The non-transitory computer readable medium of claim 9 , wherein the executable instructions are further operable to cause the apparatus to share the second serialized data file among the plurality of users of the shared cloud service.

12. The non-transitory computer readable medium of claim 9 , wherein the executable instructions are further operable to cause the apparatus to collect the metadata relating to the subject at the first device.

13. The non-transitory computer readable medium of claim 9 , wherein the subject is associated with a globally-unique identifier, and wherein the executable instructions are further operable to cause the apparatus to use a Javascript Object Notation (JSON) data format for serializing the information.

14. The non-transitory computer readable medium of claim 9 , wherein the executable instructions are further operable to cause the apparatus to save the second serialized data file in a metadata directory in a file hierarchy at the shared cloud service.

15. The non-transitory computer readable medium of claim 8 , wherein the executable instructions are further operable to cause the apparatus to:

apply an action corresponding to the metadata at a second subject at the second device; and

synchronize a result of the action with the first device.

16. The non-transitory computer readable medium of claim 15 , wherein the action is to search a keyword.

17. A networked computing system comprising:

a memory that stores a module;

a processor configured to run the module stored in the memory that is configured to cause the processor to:

determine, at a second device, selection criteria for suggestion of relevant documents to a local user of the second device, including a set of keywords;

synchronize, to the shared cloud service, the selection criteria as a first serialized data file;

receive at a first device the first serialized data file;

create metadata relating to a subject on the first device in response to a remote content file on the first device being opened and the remote content file including one or more of the selection criteria from the first serialized data file, the metadata including data indicative of one or more keywords occurring in the remote content file and document metadata identifying the file;

save the created metadata in a second serialized format data file to the shared cloud service, the second serialized data file having a filename generated as a function of the subject and is saved separately from the subject;

identify the subject using a globally-unique identifier, wherein the globally-unique identifier is embedded in the filename of the second serialized data file, thereby identifying the subject of the second serialized data file by the filename so that the metadata can be located in a particular location on the shared cloud service using the filename, wherein the second serialized data file is in a Javascript Object Notation data format (JSON);

provide, by using a globally-unique identifier for the local user (UserGuid), authenticated access to the second serialized data file for the second device via the shared cloud service, wherein the userGuid is used for tracking all statistics regarding file accesses associated with the local user;

synchronize a copy of the second serialized data file via the shared cloud service to the second device, the copy of the second serialized data file reflecting a single up-to-date state of the second serialized data file in the shared cloud service;

de-serialize the second serialized data file at the second device to generate a de-serialized data file;

determine, at the second device, using the metadata from the de-serialized data file, and the selection criteria that the remote content file is a relevant document, wherein the remote content file has been identified based on the metadata of the remote content file and the selection criteria determined at the second device; and

suggest, by the second device, the remote content file to the local user in response to the determined selection criteria in a table of suggestions.

18. The networked computer system of claim 17 , wherein the subject comprises one of a user and a file.

19. The networked computing system of claim 17 , wherein the module is further configured to cause the processor to copy the de-serialized data file into a database at the second device.

20. The networked computing system of claim 17 , wherein the module is further configured to cause the processor to collect the metadata relating to the subject at the first device.

21. The networked computing system of claim 17 , wherein the module is further configured to cause the processor to share the second serialized data file among a plurality of users of the shared cloud service.

22. The networked computing system of claim 17 , wherein the module is further configured to cause the processor to save the second serialized data file in a metadata directory in a file hierarchy at the shared cloud service.

23. The networked computing system of claim 17 , wherein the module is further configured to cause the processor to:

apply an action corresponding to the metadata at a second subject at the second device; and

synchronize a result of the action with the first device.

24. The networked computing system of claim 23 , wherein the action is to search a keyword.

Assignments (17)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 3, 2025
From: IVANTI US LLC
To: ALTER DOMUS (US) LLC
Reel/Frame 071165/0089 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 054665/0873 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071123/0386 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; IVANTI, INC.; MOBILEIRON, INC.; IVANTI US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 054665/0062 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; INVANTI, INC.; MOBILEIRON, INC.; INVANTI US LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 054665/0873 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 43971/0495 Recorded Dec 1, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: APPSENSE US LLC
Reel/Frame 054560/0278 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 43971/0549 Recorded Dec 1, 2020
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: APPSENSE US LLC
Reel/Frame 054560/0389 →
CHANGE OF NAME Recorded Mar 5, 2019
From: APPSENSE US LLC
To: IVANTI US LLC
Reel/Frame 048511/0832 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Sep 15, 2017
From: APPSENSE US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 043971/0495 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Sep 15, 2017
From: APPSENSE US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 043971/0549 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 25, 2017
From: APPSENSE LIMITED
To: APPSENSE US LLC
Reel/Frame 043406/0821 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT R/F 038333/0821 Recorded Sep 28, 2016
From: JEFFERIES FINANCE LLC
To: APPSENSE LIMITED
Reel/Frame 040171/0172 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT R/F 038333/0879 Recorded Sep 28, 2016
From: JEFFERIES FINANCE LLC
To: APPSENSE LIMITED
Reel/Frame 040169/0981 →
SECURITY INTEREST Recorded Apr 20, 2016
From: APPSENSE LIMITED
To: JEFFERIES FINANCE LLC
Reel/Frame 038333/0821 →
SECURITY INTEREST Recorded Apr 20, 2016
From: APPSENSE LIMITED
To: JEFFERIES FINANCE LLC
Reel/Frame 038333/0879 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 19, 2013
From: BRANTON, PAUL K.
To: APPSENSE LIMITED
Reel/Frame 030043/0818 →