# US 11,907,169 B2 · Delta set information management device and system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,907,169 B2 - Document ID: US11907169B2 - Status: Granted - Kind: B2 - Application number: 16/713,504 - Filed: 2019-12-13 - Published: 2021-06-17 - Granted: 2024-02-20 - Earliest claimed: 2019-12-13 - Applicants: Steven Reynolds - Inventors: Steven Reynolds - Web page: https://patentgrep.com/patent/US11907169B2 ## CPC - G06F 16/1756: {based on delta files} - G06F 16/1873: {Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files} - G06F 16/13: File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06) - G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs} - G06F 16/176: Support for shared access to files; File sharing support - G06F 16/9027: {Trees} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A delta set information management device (delta device) stores full versions of files and updates such files based upon delta information. The delta device can be a web server running delta software. It can store original files as either seed files or node files in a tree structure and store modifications to seed files and node files based upon the time and identity of the entity (e.g., user or computer) that requested or made such modifications. ## Claims ### Claim 1 A file control device including: a processor; memory; and software; wherein the file control device is configured to be connected to a network and wherein the software is configured to: establish a connection with one or more users over the network; share files or file information with the one or more users; receive from the one or more users (1) instructions relating to changes to be made to one or more files and (2) at least one value associated with each of at least two criteria related to the changes, where the values are created based upon information related to the instructions; create nodes based upon at least one value associated with each of at least two of the at least two criteria and upon the identity of the one or more files; and store the instructions as change information in at least one node of a tree structure that has at least two nodes, where the at least two nodes are arranged based upon at least one value associated with each of at least two of the at least two criteria and upon the identity of the one or more files. ### Claim 2 (depends on 1) The file control device of claim 1 further configured to allow a user to modify a file stored at the file control device whereby the user (1) modifies a file stored locally with the user that is substantially similar to the file stored at the file control device and (2) creates instructions relating to the user changes; and whereby the file control device (1) receives such instructions from the user and (2) stores the instructions as change information in a tree structure, specifically in a node that is connected, directly or indirectly, to a node corresponding to the file stored at the file control device. ### Claim 3 (depends on 2) The file control device of claim 2 further configured to receive the instructions in the form of a blockchain, or a portion of a blockchain, that contains one or more transactions and that stores one or more sets of change information as transactions. ### Claim 4 (depends on 1) The file control device of claim 1 wherein the criteria include at least a temporal criterion and a criterion related to the identity of a user that provided the change information. ### Claim 5 (depends on 1) The file control device of claim 1 further configured to modify files stored in memory of the file control device based upon the received change information. ### Claim 6 (depends on 1) The file control device of claim 1 further configured to allow a user to request the combination of two or more sets of change information stored in two or more nodes in the tree structure to create a new node. ### Claim 7 (depends on 1) The file control device of claim 1 further configured to control modifications to the tree structure based upon the identity of a user that submitted change information. ### Claim 8 (depends on 7) The file control device of claim 7 further configured to provide to a user a graphical user interface by which the user can control access to one or more nodes to other users using a drag and drop interface. ### Claim 9 (depends on 1) The file control device of claim 1 further configured to (1) store files as nodes in the tree structure and (2) convert nodes into node files by applying at least one set of change information to a file. ### Claim 10 A method of controlling changes to files based upon change data using a centralized server connected to a network, the method including establishing a connection with one or more users over the network; sharing files or file information with the one or more users; receiving from the one or more users (1) instructions relating to changes to be made to one or more files and (2) at least one value associated with each of at least two criteria related to the changes, where the values are created based upon information related to the instructions; creating nodes based upon at least one value associated with each of at least two of the at least two criteria and upon the identity of the one or more files; and storing the instructions as change information in at least one node of a tree structure that has at least two nodes, where the at least two nodes are arranged based upon at least one value associated with each of at least two of the at least two criteria and upon the identity of the one or more files. ### Claim 11 (depends on 10) The method of claim 10 further including the step of allowing a user to modify a file by (1) receiving the instructions from the user and (2) storing the instructions as change information in a tree structure, specifically in a node that is connected, directly or indirectly, to a node corresponding to the file. ### Claim 12 (depends on 11) The method of claim 11 further including receiving the instructions in the form of a blockchain, or a portion of a blockchain, that contains one or more transactions and that stores one or more sets of change information as transactions. ### Claim 13 (depends on 10) The method of claim 10 wherein the receiving step includes receiving at least a temporal criterion and a criterion related to the identity of a user that provided the instructions. ### Claim 14 (depends on 10) The method of claim 10 further including the step of modifying files stored in memory based upon the received instructions. ### Claim 15 (depends on 10) The method of claim 10 further including the step of receiving instructions from a user to combine two or more sets of change information stored in two or more nodes in the tree structure to create a new node. ### Claim 16 (depends on 10) The method of claim 10 further including the step of controlling modifications to the tree structure based upon the identity of a user that submitted the instructions. ### Claim 17 (depends on 16) The method of claim 16 further including the step of providing to a user a graphical user interface by which the user controls access to one or more nodes to other users using a drag and drop interface. ### Claim 18 (depends on 10) The method of claim 10 further including the steps of (a) storing complete files as nodes in the tree structure and (b) converting nodes into node files by applying at least one set of change information to a file.