IP Library Granted Patent US 8,589,343
Granted Patent B2
US 8,589,343 · App. 12/603,026 · Granted Nov 19, 2013

Systems and methods for digital file change monitoring

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 8,589,343
App. No.
12/603,026
Granted
Nov 19, 2013
Kind
B2
Abstract

Systems and methods for monitoring changes to a digital file are described. Examples include a computer system for monitoring digital file changes that includes a processing unit that accepts a request to write an input data stream to a first file accessible within the computer system, and a storage device coupled to the processing unit and including a second file (the first file being a virtualized representation of the second file). The processing unit parses an input attribute from the input data stream, wherein the attribute includes an input identifier and an associated input value. The processing unit signals an event if the input attribute matches an identifier designated as a monitored attribute identifier of the second file.

Claims (62)

1. A computer system that monitors digital file changes, comprising:

a processing unit having one or more processors, the processing unit configured to receive a request to write an input data stream of a text format to a text configuration file accessible within the computer system; and

a storage device coupled to the processing unit and comprising a relational database including a physical file having an attribute-value format, the text configuration file being a virtualized representation of the physical file, the physical file including a plurality of attribute identifiers, each attribute identifier having a stored identifier and stored value corresponding to a portion of the text configuration file;

wherein the processing unit is configured to convert the input data stream of the text format to an input data stream of the attribute-value format compatible to the physical file, the input data stream of the attribute-value format including an input attribute having an input identifier and an associated input value;

wherein the processing unit is configured to determine whether the input identifier matches the stored identifier in the physical file and, if so, whether the input value is different from the stored value;

wherein the processing unit is configured to determine whether the attribute identifier corresponding to the matched stored identifier is a monitored attribute identifier from a list of monitored attribute identifiers when the input value is determined as different from the stored value, the monitored attribute identifier being an attribute flagged for monitoring; and

wherein the processing unit is configured to signal a file change event based on the attribute identifier corresponding to the matched stored identifier being determined as the monitored attributed identifier, the file change event indicating that the request to write the input data stream is monitored.

2. The computer system of claim 1 , wherein the processing unit is further configured to overwrite the stored value with the input value.

3. The computer system of claim 1 , wherein the processing unit is further configured to determine a difference between the input value and the stored value as exceeding a threshold value.

4. The computer system of claim 1 , wherein the processing unit is further configured to write the input value to the physical file if each of one or more conditions associated with the physical file are met, and further writes the input identifier to the physical file if each of the one or more conditions are met and the input identifier does not match an identifier value already stored within the physical file.

5. The computer system of claim 1 , wherein the processing unit is further configured to write the input value to the physical file if at least one of one or more conditions associated with the physical file is met, and further writes the input identifier to the physical file if at least one of the one or more conditions is met and the input identifier does not match an identifier value already stored within the physical file.

6. The computer system of claim 1 , wherein the stored identifier corresponds to a database record name and the stored value corresponds to a database record value of the relational database.

7. The computer system of claim 1 , wherein the processing unit further receives a request to read data from the text configuration file and in response reads an attribute identifier from the physical file; and

wherein the processing unit further converts the stored identifier and the stored value into the text format compatible with the the text configuration file, and outputs the converted stored identifier and converted stored value as text file data within an output data stream.

8. A method for monitoring digital file changes, comprising:

receiving a request to write an input data stream of a text format to a text configuration file, the text configuration file being a virtualized representation of a physical file having an attribute-value format, the physical file associated with a relational database and including a plurality of attribute identifiers, each attribute identifier having a stored identifier and stored value corresponding to a portion of the text configuration file;

converting the input data stream of the text format to an input data stream of the attribute-value format compatible to the physical file, the input data stream of the attribute-value format including an input attribute having an input identifier and an associated value;

determining whether the input identifier matches the stored identifier in the physical file and, if so, whether the input value is different from the stored value;

determining whether the attribute identifier corresponding to the matched stored identifier is a monitored attribute identifier from a list of monitored attribute identifiers when the input value is determined as different from the stored value, the monitored attribute identifier being an attribute flagged for monitoring; and

signaling a file change event based on the attribute identifier corresponding to the matched stored identifier being determined as the monitored attribute identifier, the file change event indicating that the request to write the input data stream is monitored.

9. The method of claim 8 , further comprising:

overwriting the stored value with the input value.

10. The method of claim 8 , wherein the determining whether the input value is different from the stored value includes determining a difference between the input value and the stored value as exceeding a threshold value.

11. The method of claim 8 , further comprising:

writing the input value to the physical file if each of one or more conditions associated with the physical file is met; and

writing the input identifier to the physical file if each of the one or more conditions is met and the input identifier does not match an identifier already stored in the physical file.

12. The method of claim 8 , further comprising:

writing the input value to the physical file if at least one of one or more conditions associated with the physical file is met; and

writing the input identifier to the physical file if at least one of the one or more conditions is met and the input identifier does not match an identifier already stored in the physical.

13. The method of claim 8 , wherein the stored identifier corresponds to a database record name and the stored value corresponds to a database record value of the relational database.

14. The method of claim 8 , further comprising:

receiving a request to read data from the text configuration file;

responding to the request by reading an attribute identifier from the physical file;

converting the stored identifier and the stored value into the text format compatible with of the text configuration file; and

outputting the converted stored identifier and converted stored value as data within an output data stream from the text configuration file.

15. The method of claim 8 , wherein a virtual file system accessible within the computer system comprises the text configuration file.

16. The method of claim 8 , wherein a virtual file system accessible by one or more computer systems across a network comprises the text configuration file.

17. The method of claim 16 , wherein the text configuration file is accessible using at least one network protocol selected from the group consisting of the network file system (NFS) protocol, the server message block/common Internet file system (SMB/CIFS) protocol, and the file transfer protocol (FTP).

18. A computer-readable storage medium comprising software that can be executed on a processor to cause the processor to perform the method of claim 8 .

19. A networked configuration management system that monitors digital file changes, comprising:

a configuration management station;

a computer system monitored by the configuration management station, comprising:

a processing unit having one or more processors, the processing unit configured to receive a request to write an input data stream of a text format to a text configuration file; and

a storage device coupled to the processing unit and comprising a relational database including a physical file having an attribute-value format, the text configuration file being a virtualized representation of the physical file, the physical file including a plurality of attribute identifiers, each attribute identifier having a stored identifier and stored value corresponding to a portion of the text configuration file;

a communication network that couples the configuration management station to the computer system;

wherein the processing unit is configured to convert the input data stream of the text format to an input data stream of the attribute-value format compatible to the physical file, the input data stream of the physical format including an input attribute having an input identifier and an associated input value;

wherein the processing unit is configured to determine whether the input identifier matches the stored identifier in the physical file and, if so, whether the input value is different from the stored value;

wherein the processing unit is configured to determine whether the attribute identifier corresponding to the matched stored identifier is a monitored attribute identifier from a list of monitored attribute identifiers when the input value is determined as different from the stored value, the monitored attribute identifier being an attribute flagged for monitoring;

wherein the processing unit is configured to signal a file change event and cause a message to be sent to the configuration management station based on the attribute identifier corresponding to the matched stored identifier being determined as the monitored attribute identifier, the file change event indicating that the request to write the input data stream is monitored.

20. The networked configuration management system of claim 19 , wherein the processing unit is further configured to overwrite the stored value with the input value.

21. The networked configuration management system of claim 19 , wherein the processing unit is further configured to determine a difference between the input value and the stored value as exceeding a threshold value.

22. The networked configuration management system of claim 19 , wherein the processing unit writes the input value to the file if each of one or more conditions associated with the physical file are met, and further writes the input identifier to the physical file if each of the one or more conditions are met and the input identifier does not match an identifier value already stored within the physical file.

23. The networked configuration management system of claim 19 , wherein the processing unit writes the input value to the physical file if at least one of one or more conditions associated with the physical file is met, and further writes the input identifier to the physical file if at least one of the one or more conditions is met and the input identifier does not match an identifier value already stored within the physical file.

24. The networked configuration management system of claim 19 , wherein the stored identifier corresponds to a database record name and the stored value corresponds to a database record value of the relational database.

25. The networked configuration management system of claim 19 , wherein the processing unit causes a message to be sent to the configuration management station if a write of the input attribute to the physical file is disallowed.

26. The networked configuration management system of claim 19 , wherein the processing unit further receives a request to read data from the text configuration file and in response reads an attribute identifier from the physical file; and

wherein the processing unit further converts the stored identifier and the stored value into the text format compatible with the configuration text file, and outputs the converted stored identifier and converted stored value as text file data within an output data stream.

27. The networked configuration management system of claim 19 , wherein a virtual file system accessible within the computer system comprises the text configuration file.

28. The networked configuration management system of claim 19 , further comprising:

one or more computer systems coupled to the communication network;

wherein the monitored computer system comprises a virtual file system accessible by the one or more computer systems across the communication network; and wherein the virtual file system comprises the text configuration file.

29. The networked configuration management system of claim 28 , wherein the text configuration file is accessible using at least one network protocol selected from the group consisting of the network file system (NFS) protocol, the server message block/common Internet file system (SMB/CIFS) protocol, and the file transfer protocol (FTP).

Assignments (14)
CHANGE OF NAME Recorded Jan 10, 2025
From: BLADELOGIC, INC.
To: BMC HELIX, INC.
Reel/Frame 069870/0796 →
GRANT OF FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0628 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0568 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052854/0139) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0617 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052844/0646) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0408 →
OMNIBUS ASSIGNMENT OF SECURITY INTERESTS IN PATENT COLLATERAL Recorded Mar 4, 2024
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING COLLATERAL AGENT
To: GOLDMAN SACHS BANK USA, AS SUCCESSOR COLLATERAL AGENT
Reel/Frame 066729/0889 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 1, 2024
From: ALTER DOMUS (US) LLC
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 066567/0283 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Sep 30, 2021
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 057683/0582 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052844/0646 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052854/0139 →
RELEASE OF PATENTS Recorded Oct 5, 2018
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.; BMC ACQUISITION L.L.C.
Reel/Frame 047198/0468 →
SECURITY INTEREST Recorded Oct 2, 2018
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE, AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047185/0744 →
SECURITY AGREEMENT Recorded Sep 11, 2013
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 031204/0225 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 21, 2009
From: SOLIN, DAVID ALLEN
To: BLADELOGIC, INC.
Reel/Frame 023403/0533 →