Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 09/14/2026 has been entered.
Detailed Action
Applicant presented claims with the following status for reconsideration on 09/14/2026.
Amended claim(s): 11-19 and 22-29
Canceled claim(s): 1-10 and 21
Pending claim(s): 11-20 and 22-29
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory obviousness-type double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a nonstatutory double patenting ground provided the conflicting application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement.
Effective January 1, 1994, a registered attorney or agent of record may sign a terminal disclaimer. A terminal disclaimer signed by the assignee must fully comply with 37 CFR 3.73(b).
Claims 11-20, 22-29 of the instant application are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1-10 and 22-27 of U.S. Patent No. 11,144,510, (App. No. 15/179,459). Claims 11-20, 22-29 of the instant application are also rejected under the judicially created doctrine of provisional obviousness-type double patenting as being unpatentable over claims of App. No.: 17/480,891. As shown below for independent claims, although the conflicting claims are not identical, the feature as recited in the claims of instant application are covered by the claims in App. No. 15/179,459 and App. No.: 17/480,891.
Any feature included in instant application claims but not in claims of App. No. 15/179,459 and App. No.: 17/480,891will be rejected using the reference(s) shown below for rejecting claims 11-20, 22-29 of the instant application.
19/026,230
15/179,459
17/480,891
11
1
1
a remote file system (RFS) associated with a client, said RFS including a plurality of folders and a plurality of files, each folder of said plurality of folders being associated with folder metadata having a revision field and a global revision identifier associated with said RFS, said global revision identifier having a variable state; a user interface electrically coupled to said physical memory and to a network adapter and operative to establish a connection with a user of said client and to provide access to said RFS to said user; an RFS updater configured to update said revision field of folder metadata associated with a particular folder based on a state of said global revision identifier and responsive to said particular folder or a file contained within said particular folder being modified by said user; and a remote synchronizer configured to receive a prior revision identifier from a local file storage system, said prior revision identifier being indicative of a prior state of said global revision identifier, compare, for each folder of said plurality of folders, a value stored in said revision field of said folder metadata to said prior revision identifier, identify, based on a relationship between said value stored in said revision field of said metadata and said prior revision identifier, a subset of said plurality of file system objects that require synchronization, and transmit, to said local file storage system, metadata corresponding only to said subset of said plurality of file system objects that require synchronization.
maintaining a first global revision identifier associated with a first RFS of said plurality of said RFSs, said first global revision identifier being a data variable having a value that is updated responsive to a file system operation being performed on any of a plurality of different file system objects associated with said first RFS, but not on a file system object associated with a second RFS of said plurality of RFSs; maintaining a second global revision identifier associated with said second RFS, said second global revision identifier being a data variable having a value that is updated responsive to a file system operation being performed on any of a plurality of different file system objects associated with said second RFS, but not on a file system object associated with said first RFS; receiving from a first local file storage system storing a first one of said LFSs a prior value of said first global revision identifier associated with the occurrence of a prior synchronization of said file system objects of said first RFS with file system objects of said first one of said LFSs associated with said first RFS, at least a portion of said file system objects of said first one of said LFSs having been locally altered since said prior synchronization of said file system objects of said first RFS with file system objects of said first one of said LFSs; receiving from a second local file storage system storing a second one of said LFSs a prior value of said second global revision identifier associated with the occurrence of a prior synchronization of said file system objects of said second RFS with file system objects of said second one of said LFSs associated with said second RFS, at least a portion of said file system objects of said second one of said LFSs having been locally altered since said prior synchronization of said file system objects of said second RFS with file system objects of said second one of said LFSs; establishing a network connection over a wide area network with a first user associated with said first RFS and said first global revision identifier; providing access to said first RFS to said first user, said first RFS including said plurality of file system objects associated with said first RFS, each of said file system objects associated with said first RFS being associated with first metadata; receiving an instruction to modify a particular file system object of said plurality of file system objects of said first RFS from said first user; responsive to said particular file system object of said first RFS being modified, updating a first portion of said first metadata associated with said particular file system object of said first RFS based on a current value of said first global revision identifier and not said second global revision identifier; receiving an instruction to modify a different file system object of said plurality of file system objects of said first RFS from said first user or another user associated with said first RFS; responsive to said different file system object of said first RFS being modified, updating a second portion of said first metadata associated with said different file system object of said first RFS based on an updated value of said first global revision identifier; comparing said first metadata of said file system objects of said first RFS with said prior value of said first global revision identifier received from said first local file storage system to identify file system objects of said first RFS that have not yet been synchronized with said file system objects of said first LFS; comparing second metadata associated with said file system objects of said second RFS with said prior value of said second global revision identifier received from said second local file storage system to identify file system objects of said second RFS that have not yet been synchronized with said file system objects of said second LFS; responsive to receiving said prior value of said first global revision identifier providing to said first local file storage system only metadata corresponding to said identified file system objects of said first RFS that have not yet been synchronized and not metadata corresponding to file system objects of said first RFS that have been synchronized in order to facilitate synchronization of said first RFS with said first LFS; and responsive to receiving said prior value of said second global revision identifier providing to said second local file storage system only metadata corresponding to said identified file system objects of said second RFS that have not yet been synchronized and not metadata corresponding to file system objects of said second RFS that have been synchronized in order to facilitate synchronization of said second RFS with said second LFS.
providing said RFS including a plurality of RFS objects, said plurality of RFS objects including a first instance of a set of objects stored in persistent storage at a first physical location, each RFS object of said plurality of RFS objects being associated with RFS metadata indicative of a state of said each RFS object of said plurality of RFS objects; synchronizing said RFS with said LFS as of a first time, said LFS including a plurality of LFS objects, said plurality of LFS objects including a second instance of said set of objects stored in persistent storage at a second physical location remote from said first physical location, each LFS object of said plurality of LFS objects being synchronized with a corresponding RFS object and being associated with LFS metadata indicative of a state of said each LFS object of said plurality of LFS objects; defining a namespace, said namespace identifying said set of objects as including every object of said plurality of RFS objects and every object of said plurality of LFS objects that is accessible by a particular user; maintaining a global revision identifier associated with said RFS, said global revision identifier having a variable state; establishing a connection with said particular user; providing access to said RFS objects to said particular user by providing a proper subset of said set of objects to a client machine associated with said particular user responsive to a request by said particular user for said proper subset of said set of objects; receiving an instruction to modify a particular RFS object of said RFS from said particular user; modifying said particular RFS object in said remote physical location according to said instruction from said particular user; responsive to said particular RFS object being modified, updating data in global revision field of said RFS metadata corresponding to said particular RFS object to reflect a current state of said global revision identifier; establishing a second connection with a local file storage system associated with said LFS and storing said LFS objects; receiving from said local file storage system storing said LFS objects a prior state of said global revision identifier, said prior state of said global revision identifier representing a particular state of said global revision identifier at said first time, at least a portion of said LFS objects having been altered in said second physical location since said first time; comparing data in each of a plurality of global revision fields of said RFS metadata corresponding to said plurality of RFS objects with said prior sate of said global revision identifier received from said local file storage system to identify ones of said RFS objects that require synchronization with corresponding ones of said LFS objects; and responsive to receiving from said local file storage system said prior state of said global revision identifier providing to said local file storage system a proper subset of said RFS metadata corresponding only to said ones of said RFS objects that require synchronization, thereby facilitating a subsequent synchronization of said first instance of said set of objects stored in persistent storage at said first location with said second instance of said set of objects stored in persistent storage at said second location.
22
22
22
maintaining said RFS in association with a client, said RFS including a plurality of folders and a plurality of files, each folder of said plurality of folders being associated with folder metadata having a revision field; maintaining a global revision identifier in association with said RFS, said global revision identifier having a variable state responsive to a modification of a particular folder of said RFS or a file contained within said particular folder, updating said revision field of said folder metadata associated with said particular folder based on a state of said global revision identifier; establishing a network connection with a local file storage system associated with said LFS; receiving, from said local file storage system, a prior revision identifier indicative of a prior-state of said global revision identifier; comparing, for each folder of said plurality of file system objects of folders, a value stored in said revision field of said folder metadata to said prior revision identifier; identifying, based on a relationship between said value stored in said revision field of said metadata and said prior revision identifier, a subset of said plurality of folders that require synchronization; transmitting, to said local file storage system, folder metadata corresponding only to said subset of said plurality of folders that require synchronization; receiving, from said local file storage system, a request for file metadata associated with files stored in at least one folder of said subset of said plurality of folders that require synchronization; and transmitting said requested file metadata to said local file storage system.
establishing a network connection with a geographically remote multi-client file storage system having a plurality of RF Ss each associated with one of a plurality of clients stored thereon, said plurality of RFSs including said associated RFS; initiating a synchronization process with said remote multi-client file storage system; providing at least one namespace identifier to said remote multi-client file storage system via said network connection, said namespace identifier being indicative of at least a portion of a subscribed namespace synchronized on said associated RFS and said LFS, but not others of said plurality of RFSs; and providing at least one prior revision identifier to said remote multi-client file storage system, said prior revision identifier being associated with said associated RFS and the occurrence of a prior synchronization of said at least said portion of said subscribed namespace between said associated RFS and said LFS; receiving RFS metadata from said remote multi-client file storage system, said RFS metadata being associated with file system objects in said at least said portion of said subscribed namespace that have been modified since said prior synchronization; generating file system operations based at least in part on said received RFS metadata; providing at least a first portion of said file system operations to said remote multi-client file storage system; and applying at least a second portion of said file system operations to said LFS; and wherein said RFS and said LFS are synchronized when said portion of said file system operations is applied to said RFS and said second portion of said file system operations is applied to said LFS; and said prior revision identifier is a particular value of a data variable at a time of said prior synchronization, said data variable being updated when a file system operation is performed on any of a plurality of file system objects of said at least said portion of said subscribed namespace on said RFS.
providing said LFS including a plurality ofLFS objects, said plurality of LFS objects including a first instance of said set of objects stored in persistent storage at a first physical location, each LFS object of said plurality of LFS objects being associated with LFS metadata indicative of a state of said each LFS object of said plurality of LFS objects;
establishing a network connection with said remote file storage system associated with said RFS;
synchronizing said LFS with said RFS as of a first time, said RFS including a
plurality of RFS objects, said plurality of RFS objects including a second instance of said set of objects stored in persistent storage at a second physical location, each RFS object of said plurality of RFS objects being synchronized with a corresponding LFS object and being associated with RFS metadata indicative of a state of said each RFS object of said plurality of RFS objects;
defining a subscribed namespace, said subscribed namespace identifying said set of objects as including every object of said plurality of RFS objects and every object of said plurality of LFS objects that is accessible by a particular user; initiating a second synchronization process with said remote file storage system; providing at least one namespace identifier to said remote file storage system via said network connection, said namespace identifier being indicative of said subscribed
namespace synchronized between said RFS and said LFS; providing at least one prior revision identifier to said remote file storage system, said
prior revision identifier being indicative of a state of said second instance of said
set of objects at said first time;
receiving information from said remote file storage system, said information being indicative of differences between a current state of said second instance of said set of objects and a prior state of said second instance of said set of objects at said first time;
generating file system operations based at least in part on said received information; applying at least a first portion of said file system operations to said LFS objects; and
providing at least a second portion of said file system operations to said remote file storage system to be applied to said RFS objects; and wherein
said first instance of said set of objects and said second instance of said set of objects are synchronized when said first portion of said file system operations is applied to said LFS objects and said second portion of said file system operations is applied to said RFS objects; and said step of receiving information from said remote file storage system includes receiving RFS metadata from said remote file storage system, said RFS metadata being representative of file system objects of said subscribed namespace that have been modified since said first time.
26
25
26
said LFS including a plurality of LFS folders synchronized with a corresponding plurality of RFS folders and including a plurality of LFS files synchronized with a corresponding plurality of RFS files and a plurality of prior revision identifiers, each prior revision identifier being associated with a respective LFS folder synchronized with a corresponding respective RFS folder and defining a state of said RFS at a time when said respective LFS folder was last synchronized with said corresponding respective RFS folder; a remote cloud interface electrically coupled to said hardware processor and to said physical memory and configured to establish a connection with said remote file storage system; and; a synchronizer configured to provide, to said remote file storage system, data identifying at least a subset of said plurality of LFS folders and at least one of said plurality of prior revision identifiers associated with at least one prior state of said RFS, receive, from said remote file storage system, RFS folder metadata corresponding only to corresponding LFS folders determined, based on comparisons between revision data associated with respective ones of said corresponding plurality of RFS folders and said prior revision identifier, to have been modified since said corresponding LFS folders were last synchronized with said RFS, query said remote file storage system for RFS file metadata associated with RFS files stored in at least one folder identified by said received RFS folder metadata, and receive said RFS file metadata from said remote file storage system.
said LFS including a plurality of file system objects, each of said file system objects being associated with LFS metadata, and a plurality of prior revision identifiers, each prior revision identifier being associated with said associated RFS and the occurrence of a prior synchronization of at least an associated folder of a subscribed namespace between said LFS and said associated RFS; a remote cloud interface configured to establish a wide area network connection with said remote multi-client file storage system, said remote file storage system having a plurality of RFSs stored thereon, each RFS of said plurality of RFSs being associated with one of a plurality of different clients, said plurality of RFSs including said associated RFS; and a synchronizer including a subset of said predefined instructions configured to initiate a synchronization process with said remote multi-tenant file storage system, provide at least one namespace identifier to said remote multi-tenant file storage system via said wide area network connection, said namespace identifier being indicative of at least a portion of said subscribed namespace, said subscribed namespace being synchronized on said LFS and said associated RFS, but not other of said RFSs, provide at least one prior revision identifier associated with said namespace identifier to said remote multi-client file storage system, receive RFS metadata from said remote multi-client file storage system, said RFS metadata being associated with file system objects in said at least said portion of said subscribed namespace that have been modified since said prior synchronization, generate file system operations based at least in part on said received RFS metadata, provide at least a first portion of said file system operations to said remote multi-client file storage system, and apply at least a second portion of said file system operations to said LFS; and wherein said RFS and said LFS are synchronized when said portion of said file system operations is applied to said RFS and said second portion of said file system operations is applied to said LFS; and said prior revision identifier is a particular value of a data variable at a time of said prior synchronization, said data variable being updated when a file system operation is performed on any of a plurality of file system objects of said at least said portion of said subscribed namespace on said RFS.
a subscribed namespace, said subscribed namespace identifying a set of objects accessible by a particular user, said LFS including a plurality of LFS objects, said plurality of LFS objects including a first instance of said set of objects stored in persistent storage at a first physical location, each LFS object of said plurality of LFS objects being associated with LFS metadata indicative of a state of said each LFS object of said plurality of LFS objects, and a prior revision identifier, said prior revision identifier defining a state of a second instance of said set of objects; a remote cloud interface configured to establish a connection with said remote file storage system; and a synchronizer including a subset of said set of native instructions configured to synchronize said LFS with said RFS as of said first time, said RFS including a plurality of RFS objects, said plurality of RFS objects including said second instance of said set of objects stored in persistent storage at a second physical location, each RFS object of said plurality of RFS objects being synchronized with a corresponding LFS object and being associated with RFS metadata indicative of a state of said each RFS object of said plurality of RFS objects, initiate a second synchronization process with said remote file storage system, provide at least one namespace identifier to said remote file storage system, said namespace identifier being indicative of said subscribed namespace, provide said prior revision identifier associated with said namespace identifier to said remote file storage system, receive information from said remote file storage system, said information being indicative of differences between a current state of said second instance of said set of objects and a prior state of said second instance of said set of objects at said first time, generate file system operations based at least in part on said received information, apply at least a first portion of said file system operations to said LFS objects, and provide at least a second portion of said file system operations to said remote file storage system to be applied to said RFS objects; and wherein said set of objects includes every object of said plurality of RFS objects and every object of said plurality of LFS objects that is accessible by said particular user; said first instance of said set of objects and said second instance of said set of objects are synchronized when said first portion of said file system operations is applied to said LFS objects and said second portion of said file system operations is applied to said RFS objects; and said remote cloud interface receives RFS metadata from said remote file storage system, said RFS metadata being representative of file system objects in said subscribed namespace that have been modified since said first time.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 102 that forms the basis for all the rejections under this section made in this Office Action:
A person shall be entitled to a patent unless—
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention.
Claims 11-20, 22-29 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Chung, Patent No.: US 8,332,357 B1 (hereinafter Chung).
Chung teaches:
Claim 11. A remote file storage system comprising: a hardware processor configured to execute code; physical memory electrically coupled to said hardware processor for storing data and said code, said data including
a remote file system (RFS) associated with a client, said RFS including a plurality of folders and a plurality of files, (target and source devices are local and remote file systems: 1:6-17, “A synchronizing application may enable an electronic object such as a file of any type stored in a computerized file system to be shared and updated among multiple computing devices or endpoints that are remote from each other”, 3:42-57, “File synchronization system 100 may include a server system 102, a plurality of endpoint devices 104, and a network 106…The components of file synchronization system 100 may be positioned in a single location, a single facility, and/or may be remote from one another”; each folder of said plurality of folders being associated with folder metadata having a revision field and a global revision identifier associated with said RFS, said global revision identifier having a variable state;(a revision field is any metadata field used for identifying a previous metadata from a current metadata and a global revision identifier is the known state of synchronized file, a state is variable: 1:65-2:46, “Metadata is created to describe a synchronized folder in its current state. The synchronized folder includes a plurality of files that are replicated at a second computing device. The current metadata includes a filename and a hash identifier for each file of the plurality of files. The hash identifier is created based on the contents of a respective file of the plurality of files… The created current metadata is compared to previous metadata created for the synchronized folder.
a user interface electrically coupled to said physical memory and to a network adapter and operative to establish a connection with a user of said client and to provide access to said RFS to said user; (8:34-53, “A user may install and execute synchronization manager application 212 on an endpoint device such as source endpoint device 104a and/or target endpoint device 104b. Synchronization manager application 212 may provide a mechanism through which the user may select or otherwise identify a folder within file system 210 to synchronize at any number of endpoint devices of the plurality of endpoint devices 104”)
an RFS updater configured to update said revision field of folder metadata associated with a particular folder based on a state of said global revision identifier and responsive to said particular folder or a file contained within said particular folder being modified by said user; and (metadata related to a modified synchronized folder is updated: 9:1-64, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, “metadata associated with modified files identified within the synchronized folder, if any, is received by target endpoint device 104 b”; 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
a remote synchronizer configured to (6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”)
receive a prior revision identifier from a local file storage system, said prior revision identifier being indicative of a prior state of said global revision identifier, (a prior revision identifier from a device is a current state of a synchronized folder that is communicated from a device to another device; a change in the current state in another device is communicated with the device: 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
compare, for each folder of said plurality of folders, a value stored in said revision field of said folder metadata to said prior revision identifier, (a change in current state is identified with respect to a synchronized folder comprising metadata/ version identifiers: 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
identify, based on a relationship between said value stored in said revision field of said metadata and said prior revision identifier, a subset of said plurality of file system objects that require synchronization, and (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
transmit, to said local file storage system, metadata corresponding only to said subset of said plurality of file system objects that require synchronization. (only metadata related to changed folder/files are communicated: 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 12 The system of Claim 11, wherein said RFS updater is configured to alter said revision field of said folder metadata to reflect said state of said global revision identifier. (metadata related to a modified synchronized folder is altered/updated: 9:1-64, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, “metadata associated with modified files identified within the synchronized folder, if any, is received by target endpoint device 104 b”; 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 13. The system of Claim 12, wherein said RFS updater is configured to update said state of said global revision identifier to a new state prior to updating said revision field of said folder metadata based on said state of said global revision identifier. (a communicated state is a changed/new: 9:1-64, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, “metadata associated with modified files identified within the synchronized folder, if any, is received by target endpoint device 104 b”; 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 14. The system of Claim 11, wherein said RFS updater is configured to update folder metadata associated with a plurality of folders of said RFS responsive to said RFS being modified by said user. (6: 8-61, 10: 15-39, metadata of a synchronized folder comprising subfolders are modified by subfolder modification: “Based on the comparison, any added folders are identified in an operation 416. For example, any folder having a folder name that is included in the current metadata and not in the previous metadata may be identified as an added folder…”; 11: 28-61, “the current metadata created in operation 406 is saved in the metadata file and replaces the metadata created in operation 402 for subsequent comparisons initiated by receipt of a subsequent indicator indicating an interaction with a file system entity of the synchronized folder received in operation 404. In operations 440-452, one or more subsets of the created current metadata are communicated to a second device”)
Claim 15. The system of Claim 14, wherein said updated folder metadata is associated with a plurality of folders, said plurality of folders together constituting a filesystem pathway indicative of a virtual location of said particular folder, said particular folder containing a particular file therein, said particular file comprising at least a portion of said modification to said RFS by said user. (see claim 14 above, a synchronized folder comprises multiple subfolders: “File system 210, represented by file tree 500, may include a root folder 502, a child folder 504, and a file 506. A folder, also known as a directory, is a virtual container in which groups of computer files and other folders can be kept and organized. Thus, files can be organized by storing related files in the same folder. Although folders and directories are explicitly disclosed, example embodiments can be applied with any hierarchical data or file structure. A folder contained inside another folder is called a subfolder or subdirectory or child folder of that folder. Together, the folders form a hierarchy, or tree structure such as that represented by file tree 500”)
Claim 16. The system of Claim 11, wherein:
folder metadata includes a plurality of folder records each storing, in a plurality of metadata fields, data associated with folder of said RFS; (9:9-10:39, “The metadata includes the data that is used to synchronize endpoint devices such as source endpoint device 104a and target endpoint device 104b and may be saved in a file stored in computer readable storage medium 204. The metadata may include a file/folder type, a file/folder name, a parent folder name, a hash identifier, a file/folder size, a creation date, an edit date, etc. The metadata may be stored in a metadata file using a variety of digital formats such as a format defined using the extensible markup language (XML).folder and file have associated metadata and a new state replaces an old state”)
said file metadata includes a plurality of file records each storing, in a second plurality of metadata fields, data associated with file of said RFS; (9:9-10:39, “The metadata includes the data that is used to synchronize endpoint devices such as source endpoint device 104a and target endpoint device 104b and may be saved in a file stored in computer readable storage medium 204. The metadata may include a file/folder type, a file/folder name, a parent folder name, a hash identifier, a file/folder size, a creation date, an edit date, etc. The metadata may be stored in a metadata file using a variety of digital formats such as a format defined using the extensible markup language (XML).folder and file have associated metadata and a new state replaces an old state”)
said plurality of folder records each include said revision field storing said value indicative of said prior state of said global revision identifier. (9:9-10:39, “The metadata includes the data that is used to synchronize endpoint devices such as source endpoint device 104a and target endpoint device 104b and may be saved in a file stored in computer readable storage medium 204. The metadata may include a file/folder type, a file/folder name, a parent folder name, a hash identifier, a file/folder size, a creation date, an edit date, etc. The metadata may be stored in a metadata file using a variety of digital formats such as a format defined using the extensible markup language (XML).folder and file have associated metadata and a new state replaces an old state”; 13: 49-67, a state can be interpreted as current state or prior state based on comparison: “a synchronization state of the synchronized folder is determined. The synchronization state may indicate if the synchronized folder has or has not been changed on an endpoint of the plurality of endpoint devices 104”)
Claim 17. The system of Claim 11, wherein said remote synchronizer is configured to:
establish a second connection with said local file storage system associated with local file system (LFS); receive a synchronization request from said local file storage system; and transmit said folder metadata responsive to receiving said synchronization request. (4: 10-14, devices send/receive signal through network: 9:65-10:15, 3: 49-66, a device can request synchronization: “The indicator may be triggered as a result of a periodic scan of the synchronized folder, by a user requesting a synchronization between endpoint devices through interaction with synchronization manager application 212, by a File System Watcher application…by using a file system journaling method…”)
Claim 18. The system of Claim 17, wherein:
said synchronization request includes data indicative of at least one requested folder within said RFS; and said remote synchronizer is configured to provide, to said local file storage system, said folder metadata corresponding only to said subset of said plurality of folders based on said at least one requested folder of said RFS, said folder metadata including said revision field storing said value indicative of a state of said global revision identifier the last time at least one of said one or more identified folders of said RFS was modified. (Only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 19. The system of Claim 18, wherein:
said client interface is operative to receive a file listing request from said local file storage system for at least some of said subset of said plurality of folders associated to said folder metadata provided to said local file storage system; and said remote synchronizer is further configured to provide file metadata for files stored in each folder identified in said file listing request to said local file storage system. (5:55-6:26, a synchronization folder is a portion of the filesystem including folders/subfolders and files: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 20. The system of Claim 17, wherein said remote synchronizer is configured to provide a current state of said global revision identifier to said local file storage system. (13: 49-67, “a synchronization state of the synchronized folder is determined. The synchronization state may indicate if the synchronized folder has or has not been changed on an endpoint of the plurality of endpoint devices 104. For example, a user of target endpoint device 104b may request the synchronization state from server system 102 or from source endpoint device 104a”)
Claim 22. A method for synchronizing a remote file system (RFS) with an associated local file system (LFS), said LFS being located remotely from said RFS, said method comprising:
maintaining said RFS in association with a client, said RFS including a plurality of folders and a plurality of files, each folder of said plurality of folders being associated with folder metadata having a revision field; (target and source devices are local and remote file systems: 1:6-17, “A synchronizing application may enable an electronic object such as a file of any type stored in a computerized file system to be shared and updated among multiple computing devices or endpoints that are remote from each other”, 3:42-57, “File synchronization system 100 may include a server system 102, a plurality of endpoint devices 104, and a network 106…The components of file synchronization system 100 may be positioned in a single location, a single facility, and/or may be remote from one another”; a revision field is any metadata field used for identifying a previous metadata from a current metadata and a global revision identifier is the known state of synchronized file, the known state is variable: 1:65-2:46, “Metadata is created to describe a synchronized folder in its current state. The synchronized folder includes a plurality of files that are replicated at a second computing device. The current metadata includes a filename and a hash identifier for each file of the plurality of files. The hash identifier is created based on the contents of a respective file of the plurality of files… The created current metadata is compared to previous metadata created for the synchronized folder”)
maintaining a global revision identifier in association with said RFS, said global revision identifier having a variable state; (a revision field is any metadata field used for identifying a previous metadata from a current metadata and a global revision identifier is the known state of synchronized file, the known state is variable: 1:65-2:46, “Metadata is created to describe a synchronized folder in its current state. The synchronized folder includes a plurality of files that are replicated at a second computing device. The current metadata includes a filename and a hash identifier for each file of the plurality of files. The hash identifier is created based on the contents of a respective file of the plurality of files… The created current metadata is compared to previous metadata created for the synchronized folder”)
responsive to a modification of a particular folder of said RFS or a file contained within said particular folder, updating said revision field of said folder metadata associated with said particular folder based on a state of said global revision identifier; (metadata related to a modified synchronized folder is updated: 9:1-64, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, “metadata associated with modified files identified within the synchronized folder, if any, is received by target endpoint device 104 b”; 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
establishing a network connection with a local file storage system associated with said LFS; (4: 10-14, “The plurality of endpoint devices 104 may include one or more computing devices. The one or more computing devices send and receive signals through network 106 to/from another of the one or more computing devices and/or to/from server system 102”)
receiving, from said local file storage system, a prior revision identifier indicative of a prior-state of said global revision identifier; (a prior revision identifier from a device is a current state of a synchronized folder that is communicated from a device to another device; a change in the current state in another device is communicated with the device: 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
comparing, for each folder of said plurality of file system objects of folders, a value stored in said revision field of said folder metadata to said prior revision identifier; (a change in current state is identified with respect to a synchronized folder comprising metadata/ version identifiers: 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
identifying, based on a relationship between said value stored in said revision field of said metadata and said prior revision identifier, a subset of said plurality of folders that require synchronization; (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
transmitting, to said local file storage system, folder metadata corresponding only to said subset of said plurality of folders that require synchronization; (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
receiving, from said local file storage system, a request for file metadata associated with files stored in at least one folder of said subset of said plurality of folders that require synchronization; and (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
transmitting said requested file metadata to said local file storage system. (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 23. The method of Claim 22, wherein said step of transmitting folder metadata includes transmitting only folder metadata associated with folders and files that have been modified since a prior synchronization that occurred when said global revision identifier was in said prior state. (a synchronized folder in new state includes changes occurred since prior synchronization, 6: 42-46, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 24. The method of Claim 23, wherein:
said step of transmitting said requested file metadata includes transmitting only file metadata associated with all files stored in folders that have been modified since said prior synchronization; and thereby facilitating comparison between said requested file metadata of said RFS with corresponding file metadata of said LFS to determine which of said files stored in said folders that have been modified since said prior synchronization require synchronization; and further comprising synchronizing only said files determined to require synchronization. (a synchronized folder in new state includes folders/files changed occurred since prior synchronization, a comparison is performed for updating changed folders/files: 1:64-2:17, “Metadata is created to describe a synchronized folder in its current state. The synchronized folder includes a plurality of files that are replicated at a second computing device. The current metadata includes a filename and a hash identifier for each file of the plurality of files. The hash identifier is created based on the contents of a respective file of the plurality of files. The created current metadata is compared to previous metadata created for the synchronized folder. Based on the comparison, a first file added to the synchronized folder after creation of the previous metadata is identified”; 6: 42-46, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 25. The method of Claim 24, further comprising:
providing a current revision identifier to said local file storage system, said current revision identifier defining a current state associated with said RFS; and thereby facilitating storage of said current revision identifier in LFS folder metadata associated with at least one folder of said LFS said folders that have been modified since said prior synchronization. (a new state is associated with a current state compared with a previous state; 1:64-2:17, 6: 42-46, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 26. A local file storage system storing a local file system (LFS) that is synchronized with an associated remote file system (RFS) stored remotely from said LFS, said local file storage system comprising: a hardware processor configured to execute code; physical memory electrically coupled to said hardware processor for storing data and said code, said data including a remote file system (RFS) associated with a client, said RFS including a plurality of folders and a plurality of files,
said LFS including a plurality of LFS folders synchronized with a corresponding plurality of RFS folders and including a plurality of LFS files synchronized with a corresponding plurality of RFS files and (target and source devices are local and remote file systems: 1:6-17, “A synchronizing application may enable an electronic object such as a file of any type stored in a computerized file system to be shared and updated among multiple computing devices or endpoints that are remote from each other”, 3:42-57, “File synchronization system 100 may include a server system 102, a plurality of endpoint devices 104, and a network 106…The components of file synchronization system 100 may be positioned in a single location, a single facility, and/or may be remote from one another”);
a plurality of prior revision identifiers, each prior revision identifier being associated with a respective LFS folder synchronized with a corresponding respective RFS folder and defining a state of said RFS at a time when said respective LFS folder was last synchronized with said corresponding respective RFS folder; (a revision field is any metadata field used for identifying a previous synchronized metadata from a current metadata and a global revision identifier is the known state of synchronized file, the known state is variable: 1:65-2:46, “Metadata is created to describe a synchronized folder in its current state. The synchronized folder includes a plurality of files that are replicated at a second computing device. The current metadata includes a filename and a hash identifier for each file of the plurality of files. The hash identifier is created based on the contents of a respective file of the plurality of files… The created current metadata is compared to previous metadata created for the synchronized folder”)
a remote cloud interface electrically coupled to said hardware processor and to said physical memory and configured to establish a connection with said remote file storage system; and
a remote cloud interface electrically coupled to said hardware processor and to said physical memory and configured to establish a connection with said remote file storage system; and; (4: 10-14, “The plurality of endpoint devices 104 may include one or more computing devices. The one or more computing devices send and receive signals through network 106 to/from another of the one or more computing devices and/or to/from server system 102”)
a synchronizer configured to (6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”)
provide, to said remote file storage system, data identifying at least a subset of said plurality of LFS folders and at least one of said plurality of prior revision identifiers associated with at least one prior state of said RFS, (a prior revision identifier from a device is a current state of a synchronized folder that is communicated from a device to another device; a change in the current state in another device is communicated with the device: 13:8-67, “server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
receive, from said remote file storage system, RFS folder metadata corresponding only to corresponding LFS folders determined, based on comparisons between revision data associated with respective ones of said corresponding plurality of RFS folders and said prior revision identifier, to have been modified since said corresponding LFS folders were last synchronized with said RFS, (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
query said remote file storage system for RFS file metadata associated with RFS files stored in at least one folder identified by said received RFS folder metadata, and (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
receive said RFS file metadata from said remote file storage system. (only metadata related to the changed portion of the filesystem, e.g., folder/files are communicated: 6: 42-46, “Synchronization manager application 212 performs operations associated with maintaining synchronization between at least a portion of file system 210 stored at source endpoint 45 device 104a and at least a portion of the file system stored at target endpoint device 104b”, 13:8-67, “As an example and in response to the request, target endpoint device 104b may send an HTTP GET request to server computing device 108…server system 102 or source endpoint device 104 a may automatically send a notification to target endpoint device 104 b that the synchronization state has changed”, 14:1-36 “the metadata stored on target endpoint device 104b is updated based on the metadata received”)
Claim 27. The system of Claim 26, wherein said RFS folder metadata is associated with file system objects RFS folders that have been modified since a particular time when a particular folder of said LFS associated with said at least one prior revision identifier was last synchronized with said RFS. (11: 38-43, 13:8-26, 14:30-36, an updated metadata used for comparison is the last synchronized metadata)
Claim 28. The system of Claim 27, wherein said synchronizer is further configured to:
compare said RFS file metadata associated with said RFS files with corresponding LFS file metadata associated with corresponding LFS files to identify at least one of said RFS files that needs synchronized; and synchronize said at least one of said RFS files with at least one of said corresponding LFS files based at least in part on said comparison. (updated files in synchronized folder are senet to devices based on metadata comparison: 11: 44-12:53, “one or more subsets of the created current metadata are communicated to a second device…the added and modified files are sent to the second device”; 13: 8-67, “Operation 452 is performed to send the added and modified files to either server system 102 or target endpoint device 104b”)
Claim 29. The system of Claim 26, wherein:
said remote cloud interface is configured to receive a current revision identifier from said remote file storage system, said current revision identifier defining a current state associated with said RFS; and said synchronizer is configured to store said current revision identifier in LFS folder metadata associated with at least one folder of said LFS. (9:24-64, 11: 38-60: metadata related to a synchronized folder is saved in a corresponding file)
Response to Amendment and Arguments
Applicant’s arguments with respect to rejected claims have been fully considered but are moot in view of the new ground of rejections as provided above.
The following prior art(s) are provided to be considered by Applicant:
Parkison et al., Pub. No.: US 2015/0370827 A1:
¶ 7, “a cloud controller receives a request from a client to access a file in the distributed filesystem. The cloud controller sends a synchronization update request for the file to a second cloud controller and in response receives a synchronization update for the file from the second cloud controller”, ¶ 48, “A request server 304 in cloud controller 300 may receive file requests from either local processes or via a network from a client 306”,
¶10, “a cloud controller receiving a synchronization update request for a file: (1) uses the version identifier for the file that was included in the request to determine the metadata deltas that are needed to update the out-of-date version of the file on the requesting cloud controller to the updated version of the file that is available locally; (2) compresses the metadata deltas; and (3) sends the compressed metadata deltas to the requesting cloud controller in a synchronization update”,
¶ 46, “Each cloud controller maintains (e.g., stores and updates) metadata that describes the file and directory layout of the distributed filesystem and the location of the data blocks in the cloud storage system”;
¶ 48, “A request server 304 in cloud controller 300 may receive file requests from either local processes or via a network from a client 306”,
¶ 62, “cloud controllers may be configured to send two types of notification messages: 1. Registration notifications, which are used to indicate that a cloud controller is registering to request notification whenever a specified file, directory, and/or portion of the filesystem hierarchy is modified; and 2. Change notifications, which are sent whenever a cloud controller receives from a client a file close request (following a write) that is in the scope of a registered filesystem entity (e.g., a client file close request that follows a write to a file, directory, and/or portion of the filesystem that has been identified in a previous registration notification from another cloud controller)”.
Conclusion
The prior arts made of record in PTO-326 and not relied upon are considered pertinent to applicant's disclosure.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MOHSEN ALMANI whose telephone number is (571)270-7722. The examiner can normally be reached on M-F, 9:00 to 5:00.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ann J. Lo can be reached on 571-272-9767. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only.
For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MOHSEN ALMANI/Primary Examiner, Art Unit 2159
Prosecution Insights