Method of creating or updating a container file for storing image files

• US 9,501,806 B2
• Filed: 07/22/2015
• Issued: 11/22/2016
• Est. Priority Date: 09/16/2010
• Status: Active Grant

• Current Assignee: Cubic Digital Intelligence, Inc. (Cubic Corporation)
• Original Assignee: Pixia Corp. (Cubic Corporation)
• Inventors: Thakkar, Rahul C., Pakula, Scott L., Ernst, Rudolf O.
• Primary Examiner(s): Do, Anh
• Application Number:
  US14/806,143
• Publication Number:
  US 20150324452A1
• Time in Patent Office: 489 Days
• Field of Search: 382/305, 382/205, 382/173, 382/283, 382/224, 382/282, 382/175, 382/298, 348/143, 386/241, 705/14.69, 707/219, 707/609, 707/640, 707/679, 707/782, 707/792, 707/827, 707/E17.01
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2291 User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06F 16/50 of still image data
• CPC Class Codes: G06F 16/51 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/583 using metadata automatically derived from the content
• CPC Class Codes: G06T 1/00 General purpose image data processing
• CPC Class Codes: G06T 1/60 Memory management
• CPC Class Codes: G06T 7/90 Determination of colour characteristics
• CPC Class Codes: H04N 21/23424 involving splicing one content stream with another content stream, e.g. for inserting or substituting an advertisement
• CPC Class Codes: H04N 21/2353 specifically adapted to content descriptors, e.g. coding, compressing or processing of metadata
• CPC Class Codes: H04N 21/2383 Channel coding or modulation of digital bit-stream, e.g. QPSK modulation arrangements for detecting or preventing errors in the information received by adapting the channel coding H04L1/0009; analogue front ends or means for connecting modulators, demodulators or transceivers to a transmission line H04L27/0002
• CPC Class Codes: H04N 21/2662 Controlling the complexity of the video stream, e.g. by scaling the resolution or bitrate of the video stream based on the client capabilities
• CPC Class Codes: H04N 21/2665 Gathering content from different sources, e.g. Internet and satellite
• CPC Class Codes: H04N 21/6125 involving transmission via Internet transmission by internet of broadcast information H04H60/82

Abstract

A method of managing a container file for storing data files includes creating a container file including a container file metadata section by creating one or more empty records in a storage device. Each record of the one or more empty records has a data file section reserved for storing a data file, a file metadata section reserved for storing metadata about the data file, and a record metadata section including information about the record and having at least a record status mark indicating that the record is empty. The method further includes setting a container status mark in the container file metadata section to available, after creating the container file.

Claims

1. A method of managing a container file of data files, the method being implemented by a computer system that includes one or more processors configured to execute processing operations, the method comprising:

creating, by the one or more processors, a container file having a container file metadata section by creating one or more empty records in a storage device, each record of the one or more empty records comprising;

a data file section reserved for storing a data file,

a file metadata section reserved for storing metadata about the data file,

a record metadata section including information about the record and having at least a record status mark indicating that the record is empty, and

setting, by the one or more processors, a container status mark in the container file metadata section to available, after creating the container file.

2. The method according to claim 1, wherein the file metadata section starts from a location that is aligned to an integer multiple of a storage device block size (SDBS) of the storage device, the data file section starts from a location that is aligned to an integer multiple of a storage device block size (SDBS) of the storage device.

3. The method according to claim 1, wherein the record metadata section starts from a location that is aligned to an integer multiple of a storage device block size (SDBS) of the storage device.

4. The method according to claim 1, wherein the record metadata section is contained within an integer multiple of a storage device block size (SDBS) of the storage device.

5. The method according to claim 1, further comprising setting the container status mark to unavailable or being updated and extending the container file by adding one or more records to the container file.

6. The method according to claim 5, further comprising updating the container file metadata section to reflect a new number of records, after adding the one or more records to the container file.

7. The method according to claim 6, further comprising resetting the status of the container file metadata to available, after updating the container file metadata to reflect the new number of records.

8. The method according to claim 1, wherein the data file section is an image file section reserved for storing an image, and the file metadata section is an image metadata section reserved for storing metadata about the image, the image metadata section preceding or following the image file section.

9. The method according to claim 8, wherein the image metadata section includes a time of acquisition of the image, geospatial information about the image, parameters of a sensor device that captured the image, parameters on an environment in which the image is captured, a creation time of the image, geospatial information of the image, a modification time of the image, a file name of the image, or user notes, or any combination of two or more thereof.

10. The method according to claim 9, wherein parameters of the sensor device that captured the image include elevation, pitch, yaw, or roll, or any combination of two or more thereof, if the sensor device is airborne.

11. The method according to claim 8, wherein the record metadata section includes a compression parameter of the image, a number of tiles of the image, a size of each tile in the image, a position of each tile in the image, a creation time of the record, a modification time of the record, an application name that created or modified the record, an identification of a computer that created or modified the record, or user notes, or any combination of two or more thereof.

12. The method according to claim 8, further comprising defining a size of the image file section, a size of the image metadata section, a size of the record metadata section, and a size of the container metadata section using user input parameters.

13. The method according to claim 12, wherein defining the size of the image file comprises defining the size of the image file according to a size of the image that is anticipated to be stored in the container file.

14. The method according to claim 8, wherein the container metadata section includes a format of the image stored in the container file, a compression type applied to the image, owner information of the container file, security features for the container file, information about a user that processed the container file, a number of records, or user notes, or any combination of two or more thereof.

15. A method of updating a container file of data files, the container file having a container file metadata section including a container status mark, one or more empty records, each record of the one or more empty records comprising:

a data file section reserved for storing a data file, a file metadata section reserved for storing metadata about the data file, and a record metadata section including information about the record and having at least a record status mark indicating that the record is empty, the method being implemented by a computer system that includes one or more processors configured to execute processing operations, the method comprising;

setting the container status mark in the container file metadata section to unavailable or being updated;

setting the record status mark of the one or more empty records to being updated;

writing one or more records containing the data file into the one or more empty records within the container file;

if writing the one or more records is successful, resetting the record status mark to valid after writing the one or more records;

updating the container file metadata to reflect a number of records in the container file; and

resetting the container status mark to available, after updating the container file metadata.

16. The method according to claim 15, wherein writing the one or more records comprises writing the one or more records sequentially into the one or more empty records within the container file.

17. The method according to claim 15, wherein writing the one or more records comprises writing the one or more records in parallel into the one or more empty records within the container file.

18. The method according to claim 15, wherein writing the one or more records comprises writing the one or more records via a distributed computing system.

19. A computer system of managing a container file of data files, the computer system comprising one or more processors configured to:

create a container file having a container file metadata section by creating one or more empty records in a storage device, each record of the one or more empty records comprising;

a data file section reserved for storing a data file,

a file metadata section reserved for storing metadata about the data file,

a record metadata section including information about the record and having at least a record status mark indicating that the record is empty, and

set a container status mark in the container file metadata section to available, after the container file is created.

20. The computer system according to claim 19, wherein the file metadata section starts from a location that is aligned to an integer multiple of a storage device block size (SDBS) of the storage device, the data file section starts from a location that is aligned to an integer multiple of a storage device block size (SDBS) of the storage device.

21. The computer system according to claim 19, wherein the record metadata section starts from a location that is aligned to an integer multiple of a storage device block size (SDBS) of the storage device.

22. The computer system according to claim 19, wherein the record metadata section is contained within an integer multiple of a storage device block size (SDBS) of the storage device.

23. The computer system according to claim 19, wherein the one or more processors are configured to set the container status mark to unavailable or being updated and extend the container file by adding one or more records to the container file.

24. The computer system according to claim 23, wherein the one or more processors are configured to update the container file metadata section to reflect a new number of records, after the one or more records are added to the container file.

25. The computer system according to claim 24, wherein the one or more processors are configured to reset the status of the container file metadata to available, after the container file metadata is updated to reflect the new number of records.

26. The computer system according to claim 19, wherein the data file section is an image file section reserved for storing an image, and the file metadata section is an image metadata section reserved for storing metadata about the image, the image metadata section preceding or following the image file section.

27. The computer system according to claim 26, wherein the image metadata section includes a time of acquisition of the image, geospatial information about the image, parameters of a sensor device that captured the image, parameters on an environment in which the image is captured, a creation time of the image, geospatial information of the image, a modification time of the image, a file name of the image, or user notes, or any combination of two or more thereof.

28. The computer system according to claim 27, wherein parameters of the sensor device that captured the image include elevation, pitch, yaw, or roll, or any combination of two or more thereof, if the sensor device is airborne.

29. The computer system according to claim 26, wherein the record metadata section includes a compression parameter of the image, a number of tiles of the image, a size of each tile in the image, a position of each tile in the image, a creation time of the record, a modification time of the record, an application name that created or modified the record, an identification of a computer that created or modified the record, or user notes, or any combination of two or more thereof.

30. The computer system according to claim 26, wherein the one or more processors are configured to define a size of the image file section, a size of the image metadata section, a size of the record metadata section, and a size of the container metadata section using user input parameters.

31. The computer system according to claim 26, wherein the container metadata section includes a format of the image stored in the container file, a compression type applied to the image, owner information of the container file, security features for the container file, information about a user that processed the container file, a number of records, or user notes, or any combination of two or more thereof.

32. A computer system of managing a container file of data files, the container file having a container file metadata section including a container status mark, one or more empty records, each record of the one or more empty records comprising:

a data file section reserved for storing a data file, a file metadata section reserved for storing metadata about the data file, and a record metadata section including information about the record and having at least a record status mark indicating that the record is empty, the computer system comprising one or more processors configured to;

set the container status mark in the container file metadata section to unavailable or being updated;

set the record status mark of the one or more empty records to being updated;

write one or more records containing the data file into the one or more empty records within the container file;

if writing the one or more records is successful, reset the record status mark to valid after writing the one or more records;

update the container file metadata to reflect a number of records in the container file; and

reset the container status mark to available, after the container file metadata is updated.

33. The computer system according to claim 32, wherein the one or more processors are further configured to write the one or more records sequentially into the one or more empty records within the container file.

34. The computer system according to claim 32, wherein the one or more processors are further configured to write the one or more records in parallel into the one or more empty records within the container file.