IP Library Granted Patent US 7,657,517
Granted Patent B2
US 7,657,517 · App. 11/327,742 · Granted Feb 2, 2010

Server for synchronization of files

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 7,657,517
App. No.
11/327,742
Granted
Feb 2, 2010
Kind
B2
Abstract

A server stores files. Distributed clients access the server, to learn about changes made to the files on the server, and to push local changes of the files onto the server. A synchronization application is used to synchronize the clients and server, synchronizing metadata and selected files.

Claims (105)

1. A synchronization file system installed on a server for synchronizing a first user account on the server with a second user account on a client, comprising:

a server sync index (SSI) for the first user account, the SSI identifying the current state of the first user account on the server;

a first directory entry for a file system directory in the first user account, including a first metadata item containing a directory sync index (DSI), the DSI identifying the last change to the file system directory or to an object within the file system directory;

a second directory entry for a file in the first user account, including a second metadata item containing a file sync index (FSI), the FSI identifying the last change to the file; and

means for assigning a server ID (SID) to at least one of the first metadata item for the first directory entry and the second metadata item for the second directory entry.

2. A synchronization file system according to claim 1 , further comprising means for updating the SSI when a change occurs to the first directory entry.

3. A synchronization file system according to claim 1 , further comprising means for storing a change time to the metadata item for the first directory entry.

4. A synchronization file system according to claim 1 , further comprising means for assigning a previous version file ID (PFID) to the second metadata item.

5. A synchronization file system according to claim 1 , wherein:

the second directory entry includes a name; and

the synchronization file system further comprises means for storing an encrypted version of the name in the metadata item for the second directory entry.

6. A synchronization file system according to claim 1 , further comprising means for storing an encrypted version of the file.

7. A synchronization file system according to claim 1 , wherein:

the file includes a message digest array (MDA), the MDA supporting identification of at least a portion of the file that has changed; and

the synchronization file system further comprises means for storing the MDA.

8. A synchronization file system according to claim 7 , wherein the means for storing includes means for storing the MDA with the file.

9. A synchronization file system according to claim 7 , wherein the means for storing includes means for storing the MDA in the second metadata item.

10. A synchronization file system according to claim 1 , further comprising means for generating a server sync data (SSD).

11. A synchronization file system according to claim 10 , wherein the for generating includes means for generating a SSD responsive to a client sync index (CSI), the CSI identifying the current state of the second user account on the client.

12. A synchronization file system installed on a server for synchronizing a first user account on the synchronization file system with a second user account on a client, comprising:

a file system directory in the first user account in the synchronization file system;

a server ID assigned to the file system directory;

a directory sync index (DSI) assigned to the file system directory, the DSI identifying the last change to the file system directory or to an object within the file system directory;

a file in the file system directory of the first user account;

a file sync index (FSI) assigned to the file, the FSI identifying the last change to the file; and

a server sync index (SSI) for the first user account, the SSI identifying the current state of the first user account.

13. A synchronization file system according to claim 12 , further comprising a metadata item for the directory storing the server ID assigned to the file system directory.

14. A synchronization file system according to claim 13 , wherein the metadata item for the file system directory further stores the directory sync index assigned to the file system directory.

15. A synchronization file system according to claim 13 , wherein the metadata item for the file system directory further stores a change time assigned to the file system directory.

16. A synchronization file system according to claim 13 , wherein:

the file system directory includes a name; and

the metadata item for the file system directory further stores an encrypted name assigned to the file system directory.

17. A synchronization file system according to claim 12 , further comprising a second server ID assigned to the file.

18. A synchronization file system according to claim 17 , further comprising a metadata item for the file storing the second server ID assigned to the file and the FSI assigned to the file.

19. A synchronization file system according to claim 18 , wherein the metadata item for the file further stores a previous version file ID (PFID) assigned to the file.

20. A synchronization file system according to claim 18 , wherein the metadata item for the file further stores a change time assigned to the file.

21. A synchronization file system according to claim 18 , wherein:

the file includes a name; and

the metadata item for the file further stores an encrypted name assigned to the file.

22. A synchronization file system according to claim 17 , wherein the file is an encrypted file.

23. A synchronization file system according to claim 17 , further comprising a message digest array (MDA), the MDA supporting identification of at least a portion of the file that has changed.

24. A synchronization file system according to claim 23 , wherein the MDA is stored with the file.

25. A synchronization file system according to claim 23 , wherein the MDA is stored in a metadata item for the file.

26. A synchronization file system according to claim 12 , further comprising a server sync data (SSD).

27. A synchronization file system according to claim 12 , further comprising:

a first metadata item for the file system directory to store the DSI; and

a second metadata item for the file to store the FSI.

28. A method for a synchronization file system of a server to synchronize a first user account on the synchronization file system with a second user account on a client, comprising:

receiving a client sync index (CSI) from the client, the CSI identifying the current state of the second user account on the client;

transmitting a server sync index (SSI) to the client, the SSI identifying the current state of the first user account on the synchronization file system;

using the CSI and the SSI to determine whether the server and client are synchronized; and

if the server and client are not synchronized:

generating a server sync data (SSD), the SSD including the SSI and a directory sync index (DSI), the DSI identifying the last change to a file system directory in the first user account or to an object within the file system directory; and

transmitting the SSD to the client.

29. A method according to claim 28 , further comprising:

receiving a request from the client for a file;

transmitting the file to the client.

30. A method according to claim 29 , wherein:

receiving a request includes receiving a request for a message digest array (MDA) for the file, the MDA supporting identification of at least a portion of the file that has changed and

transmitting the file includes transmitting the MDA to the client.

31. A method according to claim 30 , wherein:

receiving a request includes receiving a request from the client for a block of the file; and

transmitting the file includes transmitting the block of the file to the client.

32. A method according to claim 28 , wherein generating a server sync data (SSD) includes generating the server sync data (SSD), the SSD including the SSI, a directory sync index (DSI), and a file sync index (FSI), the FSI identifying the last change to a file in the first user account.

33. A method for a synchronization file system (SFS) of a server to synchronize a first user account on the synchronization file system with a second user account on a client, comprising:

receiving an instruction from the client to update a first directory entry and a second directory entry;

performing the instruction;

updating a server sync index (SSI), the SSI identifying the current state of the first user account on the synchronization file system;

updating a directory sync index (DSI) for the first directory entry, the DSI identifying the last change to the file system directory on the synchronization file system or to an object within the file system directory;

updating a file sync index (FSI) for the second directory entry, the FSI identifying the last change to the file; and

transmitting the updated SSI, the updated DSI, and the updated FSI to the client.

34. A method according to claim 33 , further comprising the synchronization file system assigning the SSI to a metadata item.

35. A method according to claim 33 , wherein:

receiving an instruction includes receiving a metadata item from the client; and

performing the instruction includes adding the metadata item to a server SFS database.

36. A method according to claim 33 , wherein performing the instruction includes modifying a metadata item.

37. A method according to claim 33 , wherein performing an instruction includes:

creating a third directory in the first directory;

assigning a server ID (SID) to the third directory; and

transmitting the SID for the third directory to the client.

38. A method according to claim 37 , wherein assigning a server ID (SID) to the third directory includes storing the SID in a metadata item for the third directory.

39. A method according to claim 33 , wherein performing an instruction includes:

receiving a file from the client;

adding the file into a server SFS database;

assigning a server ID (SID) to the file; and

transmitting the SID for the file to the client.

40. A method according to claim 39 , wherein receiving a file includes:

copying the file to a temporary file;

receiving a block of the file;

incorporating the block into the temporary copy of the file; and

adding the temporary copy of the file into a server SFS database.

41. Computer-readable media containing a program for a synchronization file system of a server to synchronize a first user account on the synchronization file system with a second user account on a client, comprising:

software for receiving a client sync index (CSI) from the client, the CSI identifying the current state of the second user account on the client;

software for transmitting a server sync index (SSI) to the client, the SSI identifying the current state of the first user account on the synchronization file system;

software for using the CSI and SSI to determine whether the server and client are synchronized; and

if the server and client are not synchronized:

software for generating a server sync data (SSD), the SSD including the SSI and a directory sync index (DSI), the DSI identifying the last change to a file system directory in the first user account or to an object within the file system directory; and

software for transmitting the SSD to the client.

42. Computer-readable media containing a program for a synchronization file system of a server to synchronize a first user account on the synchronization file system with a second user account on a client, comprising:

software for receiving an instruction from the client to update a first directory entry and a second directory entry;

software for performing the instruction;

software for updating a server sync index (SSI), the SSI identifying the current state of the first user account on the synchronization file system;

software for updating a directory sync index (DSI) for the first directory entry, the DSI identifying the last change to the file system directory on the synchronization file system or to an object within the file system directory;

software for updating a file sync index (FSI) for the second directory entry, the FSI identifying the last change to the file; and

software for transmitting the updated SSI, the updated DSI, and the updated FSI to the client.

Assignments (16)
RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.)
Reel/Frame 062623/0009 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TO CORRECT TYPO IN APPLICATION NUMBER 10708121 WHICH SHOULD BE 10708021 PREVIOUSLY RECORDED ON REEL 042388 FRAME 0386. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE OF SUCCESSION OF AGENCY. Recorded Jul 26, 2018
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 048793/0832 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
NOTICE OF SUCCESSION OF AGENCY Recorded May 2, 2017
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 042388/0386 →
CHANGE OF NAME Recorded Sep 13, 2016
From: NOVELL, INC.
To: MICRO FOCUS SOFTWARE INC.
Reel/Frame 040020/0703 →
SECURITY INTEREST Recorded May 13, 2015
From: MICRO FOCUS (US), INC.; BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; NOVELL, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 035656/0251 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0216 Recorded Nov 24, 2014
From: CREDIT SUISSE AG
To: NOVELL, INC.
Reel/Frame 034470/0680 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0316 Recorded Nov 24, 2014
From: CREDIT SUISSE AG
To: NOVELL, INC.
Reel/Frame 034469/0057 →
GRANT OF PATENT SECURITY INTEREST SECOND LIEN Recorded May 23, 2012
From: NOVELL, INC.
To: CREDIT SUISSE AG, AS COLLATERAL AGENT
Reel/Frame 028252/0316 →
GRANT OF PATENT SECURITY INTEREST FIRST LIEN Recorded May 23, 2012
From: NOVELL, INC.
To: CREDIT SUISSE AG, AS COLLATERAL AGENT
Reel/Frame 028252/0216 →
RELEASE OF SECURITY INTEREST IN PATENTS FIRST LIEN (RELEASES RF 026270/0001 AND 027289/0727) Recorded May 22, 2012
From: CREDIT SUISSE AG, AS COLLATERAL AGENT
To: NOVELL, INC.
Reel/Frame 028252/0077 →
RELEASE OF SECURITY IN PATENTS SECOND LIEN (RELEASES RF 026275/0018 AND 027290/0983) Recorded May 22, 2012
From: CREDIT SUISSE AG, AS COLLATERAL AGENT
To: NOVELL, INC.
Reel/Frame 028252/0154 →
GRANT OF PATENT SECURITY INTEREST (SECOND LIEN) Recorded May 13, 2011
From: NOVELL, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 026275/0018 →
GRANT OF PATENT SECURITY INTEREST Recorded May 12, 2011
From: NOVELL, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 026270/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 22, 2009
From: BROWN, DAVID K.; ROLANDER, THOMAS A.; SILBERSTEIN, ROBERT D.; WEIN, JOSEF
To: NOVELL, INC.
Reel/Frame 022858/0818 →