WO2015077861A1 - Camera supporting removable storage divided into multiple partitions - Google Patents
Camera supporting removable storage divided into multiple partitions Download PDFInfo
- Publication number
- WO2015077861A1 WO2015077861A1 PCT/CA2013/050920 CA2013050920W WO2015077861A1 WO 2015077861 A1 WO2015077861 A1 WO 2015077861A1 CA 2013050920 W CA2013050920 W CA 2013050920W WO 2015077861 A1 WO2015077861 A1 WO 2015077861A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- partition
- camera
- removable storage
- partitioning
- journaled
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B13/00—Burglar, theft or intruder alarms
- G08B13/18—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength
- G08B13/189—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems
- G08B13/194—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems
- G08B13/196—Actuation by interference with heat, light, or radiation of shorter wavelength; Actuation by intruding sources of heat, light, or radiation of shorter wavelength using passive radiation detection systems using image scanning and comparing systems using television cameras
- G08B13/19665—Details related to the storage of video surveillance data
- G08B13/19667—Details realated to data compression, encryption or encoding, e.g. resolution modes for reducing data volume to lower transmission bandwidth or memory requirements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/50—Constructional details
- H04N23/51—Housings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/60—Control of cameras or camera modules
- H04N23/66—Remote control of cameras or camera parts, e.g. by remote control devices
- H04N23/661—Transmitting camera control signals through networks, e.g. control via the Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N25/00—Circuitry of solid-state image sensors [SSIS]; Control thereof
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N5/00—Details of television systems
- H04N5/76—Television signal recording
- H04N5/765—Interface circuits between an apparatus for recording and another apparatus
- H04N5/77—Interface circuits between an apparatus for recording and another apparatus between a recording apparatus and a television camera
- H04N5/772—Interface circuits between an apparatus for recording and another apparatus between a recording apparatus and a television camera the recording apparatus and the television camera being placed in the same enclosure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N5/00—Details of television systems
- H04N5/76—Television signal recording
- H04N5/907—Television signal recording using static stores, e.g. storage tubes or semiconductor memories
Definitions
- the present disclosure is directed generally at a camera that supports removable storage divided into multiple partitions.
- Cameras that are able to write files to removable storage are becoming increasingly prevalent.
- An example type of camera is a security camera, and example types of files that can be written to removable storage are audio files, video files (including those video files that comprise an audio track), and still images.
- Security cameras that offer removable storage are gaining in popularity because they offer the convenience of permitting video files to be stored even when the cameras are disconnected from a network or when the network fails. Research and development accordingly continue into methods, systems, and techniques related to improving the ability of cameras to use removable storage.
- a camera comprising a camera body comprising an aperture to permit light to enter the camera body; an image sensor located within the camera body and positioned to receive at least some of the light entering the camera body; removable media circuitry configured to write to removable storage that is formatted to comprise: (i) a journaled partition that uses a journaling file system; and (ii) a non-journaled partition that uses a non-journaling file system supported natively by an operating system, wherein the non-journaled partition has stored thereon computer program code executable by a processor to use the operating system to access files stored on the journaled partition; and processing circuitry, communicatively coupled to the image sensor and the removable media circuitry, configured to store files to the journaled partition using the journaling file system.
- the usable capacity of the removable storage may be allocated entirely to the journaled and non-journaled partitions.
- the processing circuitry optionally does not write or erase data from the non-journaled partition.
- the journaled partition may have a larger capacity than the non-journaled partition.
- the camera may be a security camera.
- a camera comprising a camera body comprising an aperture to permit light to enter the camera body; an image sensor located within the camera body and positioned to receive at least some of the light entering the camera body; removable media circuitry, wherein the removable media circuitry is configured to write to removable storage; and processing circuitry, communicatively coupled to the image sensor and the removable media circuitry, configured to perform a method comprising: (i) partitioning the removable storage to comprise a journaled partition that uses a journaling file system and a non-journaled partition that uses a non-journaling file system supported natively by an operating system; and (ii) storing on the non-journaled partition computer program code executable by a processor to use the operating system to access files stored on the journaled partition.
- the usable capacity of the removable storage may be allocated entirely to the journaled and non-journaled partitions.
- the processing circuitry optionally does not write data to or erase data from the non-journaled partition following storing the computer program code on it.
- the processing circuitry may be further configured, following partitioning the removable storage, to store one or more of video files derived from the light incident on the image sensor, audio files, and still images.
- the journaled partition may have a larger capacity than the non-journaled partition.
- the method that the processing circuitry performs may further comprise, prior to partitioning the removable storage, any one or more of the following: determining whether the removable storage comprises only a first initial partition that uses the non-journaling file system and whether the first initial partition is empty; and when the removable storage comprises only the first initial partition and the first initial partition is empty, erasing the first initial partition; determining whether the removable storage comprises only a first initial partition that uses the non-journaling file system and a second initial partition that uses the journaling file system; and when the removable storage does not comprise only the first and second initial partitions, prompting a user to confirm the partitioning is to proceed and commencing the partitioning after receiving user confirmation; when the removable storage comprises only the first and second initial partitions, determining the size of the first initial partition; and when the size of the first initial partition does not equal a fixed non-journaled partition size, prompting the user to confirm the partitioning is to proceed and commencing the partitioning after receiving user confirmation; when the size of the first initial partition equals the journaled partition size
- the camera may be a security camera.
- a method for partitioning removable storage for a camera comprising determining whether the removable storage is connected to the camera; when the removable storage is connected to the camera, using the camera to: (i) partition the removable storage to comprise a journaled partition that uses a journaling file system and a non-journaled partition that uses a non-journaling file system supported natively by an operating system; and (ii) store on the non-journaled partition computer program code executable by a processor to use the operating system to access files stored on the journaled partition.
- the usable capacity of the removable storage may be allocated entirely to the journaled and non-journaled partitions.
- the camera may store one or more of video files derived from the light incident on the image sensor, audio files, and still images.
- the journaled partition may have a larger capacity than the non-journaled partition.
- the method may further comprise, prior to partitioning the removable storage, any one or more of the following:
- a non-transitory computer readable medium having encoded thereon statements and instructions to cause a camera to partition removable storage for the camera by performing a method comprising determining whether the removable storage is connected to the camera; and when the removable storage is connected to the camera, using the camera to perform any aspects of the methods recited above and any suitable variations and combinations thereof.
- FIGS. 1A and IB are front and rear perspective views, respectively, of a security camera that supports removable storage divided into multiple partitions, according to one embodiment.
- FIG. 2 is a block diagram of the security camera of FIG. 1.
- FIG. 3 is a memory map of the removable storage used in the security camera of FIG. 1.
- FIGS. 4A and 4B collectively depict a method for formatting the removable storage used in the security camera of FIG. 1, according to another embodiment.
- Coupled and variants of it such as “coupled”, “couples”, and “coupling” as used in this description is intended to include indirect and direct connections unless otherwise indicated. For example, if a first device is coupled to a second device, that coupling may be through a direct connection or through an indirect connection via other devices and connections. Similarly, if the first device is communicatively coupled to the second device, communication may be through a direct connection or through an indirect connection via other devices and connections.
- Removable storage for a camera can comprise various types of removable, non-transitory computer readable media.
- removable storage may take the form of memory cards, external hard drives, or solid state drives (SSDs) designed to interface with ports accessible from outside the camera's housing and that can be connected to and disconnected from the camera as the user desires.
- Removable storage may be directly connected to the camera, such as when a memory card is inserted into a memory card reader that comprises part of the camera or when an external SSD drive is connected to the camera's USB port, or alternatively may be indirectly connected to the camera via a wide or local area network, such as an Ethernet based network, the Internet, or another Internet protocol (IP) network.
- IP Internet protocol
- the camera writes data to, and optionally reads data from, the storage in accordance with a file system.
- file system many different types of file systems are known in the art.
- a common file system used with one type of removable storage a memory card (an example of which is labeled 128 in FIG. 2), is "FAT32".
- One common type of memory card is a Secure Digital (SD) memory card (SD card).
- SD Secure Digital
- FAT32 is commonly used is that both the WindowsTM and OS XTM operating systems natively support it.
- journaling filing systems are inherently more resilient to power loss and sudden disconnection than FAT32, which is an example of a non-journaling file system.
- a journaling file system a file called a "journal" is maintained that keeps track of changes made to files stored using the file system.
- journaling file system An example of a journaling file system is "ext4". However, most journaling file systems, including ext4, are not natively supported by the WindowsTM and OS XTM operating systems.
- journaling file systems there is a technical challenge to be overcome in order to maintain compatibility with computers running the WindowsTM and OS XTM operating systems.
- One way to address this challenge is to require users to install third party software on their computers that provide non-native support for the journaling file system being used.
- requiring users to do this is not user friendly or convenient.
- Another solution is to require users to access the removable storage via an IP network through either a web interface that comprises part of the camera's firmware or through proprietary software installed on one or both of the camera and the users' computers.
- using this solution requires the camera to be an IP camera that is connected to an IP network.
- the files stored using the removable storage are inaccessible if the network is down or if the camera becomes disconnected from the network. Additionally, accessing files via a web interface can be up to an order of magnitude slower than accessing files by directly connecting the removable storage to a computer.
- the embodiments described herein are directed at a camera that supports removable storage that has at least two partitions.
- the removable storage has journaled and non-journaled partitions, with the journaled partition using a journaling file system and the non-journaled partition using a non-journaling file system supported natively by an operating system such as the WindowsTM and OS XTM operating systems.
- the journaled partition is typically much larger than the non-journaled partition and is used as the main storage area on the removable storage.
- Computer program code is stored on the non-journaled partition, and this program code is executable by a processor, such as a processor used in a desktop computer, to use the operating system to access files stored on the journaled partition.
- Various embodiments herein also describe methods and techniques describing how and when to format the removable storage to support the journaling and non-journaling file systems.
- the security camera is accordingly able to use removable storage in a manner that is resilient against power loss and the removable storage's sudden disconnection. While the depicted embodiments are of a security camera, in alternative embodiments (not depicted) the camera may be another type of camera, such as a traffic camera or hand-held camera.
- the data the camera stores on the removable storage may be any type of data such as audio files, video files (including those video files that comprise an audio track), and still images.
- FIGS. 1A and IB there are shown front and rear perspective views, respectively, of a security camera 100 that supports removable storage divided into multiple partitions, according to one embodiment.
- the camera 100 is contained within a camera body 102.
- On the top and bottom of the body 102 are camera mounts 104, of which only the top one is visible in FIGS. 1A and IB.
- At the front of the body is an aperture 106 through which light may enter the camera body 102, be incident on an image sensor (not shown in FIGS. 1A or IB, but labeled 126 in FIG. 2), and consequently be processed to generate video images.
- an image sensor not shown in FIGS. 1A or IB, but labeled 126 in FIG. 2
- On the rear of the camera body 102 is a control plate 122 with various inputs and outputs relevant to camera operation.
- a power control block 108 for receiving a power plug; alternatively, in some embodiments Power over Ethernet (PoE) technology may be used to power the camera 100 in which case the power control block 108 may remain unused during camera operation.
- a network jack Adjacent to the power control block 108 is a network jack in the form of an RJ45 (Ethernet) jack 114.
- the RJ45 jack 114 receives an RJ45 plug (not shown) that connects the camera to an IP network.
- connection status LED 110 and a link LED 112 are examples of the camera's 100 status and on whether the camera 100 is connected to an active Ethernet connection.
- RJ45 jack 114 Below the RJ45 jack 114 is removable media circuitry in the form of a memory card reader and any associated host controller and similar circuitry (hereinafter, collectively "memory card reader 116) that accepts removable storage in the form of a memory card (not shown in FIG. 1, but labeled as 128 in FIG. 2). Between the RJ45 jack 114 and the right edge of the control plate 122 are an audio/video connector 118 that accepts a 3.5 mm plug for connecting to a microphone or monitor, and general purpose input/output ports 120 for connecting the camera 100 to various external devices.
- memory card reader 116 Between the RJ45 jack 114 and the right edge of the control plate 122 are an audio/video connector 118 that accepts a 3.5 mm plug for connecting to a microphone or monitor, and general purpose input/output ports 120 for connecting the camera 100 to various external devices.
- the removable storage may be any suitable type of non-transitory and removable computer readable medium.
- the removable storage may comprise any one or more of magnetic tapes, floppy disks, zip disks, optical discs, portable external hard drives and SSDs, and flash media such as USB flash drives.
- Removable storage may be directly connected to the camera 100, such as by inserting the memory card 128 into the memory card reader 116, it may be indirectly connected to the camera 100 such as by daisy chaining several USB hard drives together, or it may be indirectly connected to the camera 100 via a network such as the Internet or a local area network.
- FIG. 1 shows the camera 100 as being a box-body type of camera
- the camera 100 may be a different type of camera such as a dome camera, bullet camera, pan-tilt-zoom (PTZ) camera, or multi-headed camera.
- FIG. 2 there is shown a block diagram of the security camera 100.
- a lens 112 is positioned to refract light on to the image sensor 126, which outputs a digital signal to a system on a chip 136 (SoC) in response to this incident light.
- SoC system on a chip 136
- the SoC 136 comprises a processor 138, an image signal processor (ISP) 126, a Media Access Controller (MAC) 144, and an I2C interface 142.
- ISP image signal processor
- MAC Media Access Controller
- the processor 138 is communicative with each of the ISP 126, MAC 144, and I2C interface 142.
- the ISP 126 is communicative with the image sensor 126 via the MIPI protocol and the I2C interface 142 is communicative with the image sensor 126 using the I2C protocol.
- the I2C interface 142 is used to control camera parameters such as gain, exposure, and frame rate.
- the SoC 136 comprises part of the camera's 100 processing circuitry.
- SoC 136 is communicative with a variety of different components that comprise the camera 100.
- the SoC 136, and more particularly the processor 138, is communicative with removable media circuitry in the form of the memory card reader 116.
- the SoC 136 is also communicative with a physical layer integrated circuit (PHY) 146 that is communicative with the MAC 144; flash memory 148, which is an example non- transitory computer readable medium that is non-volatile and that stores statements and instructions to cause the SoC 136 to perform tasks such as image processing; RAM 150, which is another example non-transitory computer readable medium, but which is volatile and which the SoC 136 uses to temporarily store information and for working space while performing tasks; the connection status and link LEDs 110, 112; the audio/video connector 118 and the general purpose input/output ports 120.
- PHY physical layer integrated circuit
- the removable media circuitry comprises the memory card reader 116
- the removable media circuitry may be any suitable type of circuitry that permits the SoC 136 to communicate with removable media.
- the removable media circuitry may alternatively comprise a USB port and controller that permit the SoC 136 to communicate with an external and portable SSD or via other forms of removable media via eSATA, FireWireTM, ThunderBoltTM or proprietary connections.
- Ethernet magnetics 152 which are communicative with the RJ45 jack 114 and the PHY 146
- the power control block 108 which supplies power to the various electrical components comprising the camera 100.
- the power control block 108 accepts DC power as input
- the camera 100 may be powered using, for example, an AC adapter, with batteries, or using PoE technology as mentioned above in respect of FIG. 1.
- FIG. 1 shows the camera 100 as being contained within a single housing that is the camera body 102
- the camera 100 may be divided between multiple housings and collectively comprise several components that are communicative with each other.
- the camera circuitry may be split across several printed circuit boards placed in different housings and connected via cables in order to miniaturize various camera components, as described in PCT patent application PCT/CA2013/050334.
- FIGS. 1 and 2 show the lens 112 as comprising part of the camera 100, in alternative embodiments (not depicted) the camera 100 may be a lensless camera.
- FIG. 3 there is shown a memory map 300 of the memory card 128 after it has been formatted into a journaled partition 302, which uses the ext4 file system, and a non-journaled partition 304, which uses the FAT32 file system.
- a partition table 314 that describes, among other things, the location and nature of the journaled and non- journaled partitions 302,304.
- the partition table 314 may be, for example, a master boot record or a GUTD Partition Table.
- the journaled partition 302 comprises a journal 306, which ext4 uses to log changes made to files in the file system; camera metadata 313, which comprises information about the camera 100 such as its MAC, serial number, name, and location, which off-camera software applications can use when categorizing and processing data the camera 100 stores to the journaled partition 302; and storage space that the processor 138 can write data to and read data from. As shown in the memory map 300, a portion of this storage space is filled with video files 312, while the remainder of it is empty and available to the processor 138 as required.
- the non-journaled partition 304 comprises a file allocation table 308, which is an index table identifying the clusters comprising the non-journaled partition 304; instructional files 311, which comprise files such as a readme file or help file to explain to users how to use the ext4 access files 310; and the ext4 access files 310, which comprise computer program code executable by a processor, such as the processor in a desktop computer, to use an operating system, such as the WindowsTM and OS XTM operating systems, to access files stored on the journaled partition 302 (this processor is hereinafter the "client processor", and the operating system the client processor runs is hereinafter the "client OS").
- a processor such as the processor in a desktop computer
- an operating system such as the WindowsTM and OS XTM operating systems
- this computer program code comprises Ext2Read, available from http://sourceforge.net/projects/ext2read/, but in alternative embodiments (not depicted) the program code may vary depending on, for example, the type of file system used in the journaled partition 302. While in the depicted embodiment this computer program code comprises multiple files, in alternative embodiments (not depicted) this computer program code may be only a single file.
- the memory map 300 shows, in the depicted embodiment all usable capacity of the memory card 128 is allocated entirely to the journaled and non-journaled partitions 302,304. Furthermore, the non-journaled partition 304 has less capacity than the journaled partition 302, since the purpose of the non-journaled partition 304 is to store the ext4 access files 310 while the purpose of the journaled partition 304 is to store the video files 312, which are typically much larger.
- the client processor When the memory card 128 is inserted into a memory card reader connected to the client processor, the client processor reads the partition table 314 using the client OS. Assuming the client OS is the Windows or OS X operating systems, the user will be able to natively access the non-journaled partition 304 but not the journaled partition 302. The user can consequently use the client processor to run the ext4 access files 310, which will give the user access to the journaled partition 302 and, consequently, to the video files 312.
- the client OS is the Windows or OS X operating systems
- the non-journaled partition 304 may also store in its root directory an autorun.inf file configured to cause the WindowsTM operating system to automatically run the ext4 access files shortly after the client processor gains access to the memory card 128.
- FIGS. 4A and 4B collectively show a method 400 for formatting the removable storage used in the security camera 100, according to another embodiment.
- the method 400 is directed at embodiments in which the removable storage comprises the memory card 128 and in which formatting of the memory card 128 is consequently done by the user as opposed to the camera's 100 manufacturer. While the depicted embodiment of the method 400 contemplates the use of FAT32 as the non- journaling file system and ext4 as the journaling file system, in alternative embodiments (not depicted) different journaling and non-journaling file systems may be used.
- journaling file systems include ext2, ext3, NTFS, JFS, and exFAT
- alternative non-journaling file systems include FAT16, FAT32, CDFS, and UDF.
- the method 400 is directed at removable storage in the form of the memory card 128, in alternative embodiments (not depicted) removable storage comprising other types of computer readable media may be used.
- the memory card 128 is already properly formatted into the journaled and non-journaled partitions 302,304, and upon determining this the processor 138 does not again format the memory card 128 (this example is the "no formatting example").
- the processor 138 begins performing the method at block
- the processor 138 determines whether the memory card 128 is connected to the camera 100 by entering a loop waiting for the user to connect the memory card 128 to the removable media circuitry.
- the processor 138 proceeds to block 406 where it reads the partition table 314 on the memory card 128. Assuming the memory card 128 has already been formatted and comprises at least one partition ("first initial partition"), the processor 138 then determines at block 408 whether the first initial partition comprises the only partition on the memory card 128 and uses FAT32.
- the processor 138 proceeds to block 410 where it determines whether the memory card 128 includes another partition ("second initial partition"), whether the first and second initial partitions comprise the only partitions on the memory card 128, and whether the first and second initial partitions are FAT32 and ext4 partitions, respectively. If yes, then depending on the sizes of these partitions it may be that the memory card 128 has already been properly formatted and is ready for use.
- the initial partition that uses FAT32 is hereinafter the "FAT32 partition” and the other initial partition that uses ext4 is hereinafter the "ext4 partition”.
- a different journaling file system, a different non-journaling file system, or both may be used.
- the processor 138 accordingly proceeds to block 412 where it reads the size of the FAT32 partition, which is hereinafter "FAT32SIZE". Once the processor 138 has FAT32SIZE, the processor 138 proceeds to block 414 where it determines whether FAT32SIZE equals PI SIZE, which is the name of a constant that represents a fixed non- journaled partition size. If FAT32SIZE equals PI SIZE, the non-journaled partition 304 then proceeds to block 416 where it determines whether all the ext4 access files 310 are already on the ext4 partition.
- FAT32SIZE the size of the FAT32 partition
- the processor 138 reads the total capacity of the memory card 128 at block 418, reads the size of the ext4 partition at block 420, which is hereinafter "EXT4SIZE", and determines at block 422 whether all usable capacity of the memory card 128 is allocated entirely to the FAT32 and EXT4 partitions. If yes, then the processor 138 concludes that the memory card 128 has been properly formatted into the journaled and non-journaled partitions 302,304, treats the ext4 partition as the journaled partition 302, and consequently begins writing data to the ext4 partition as block 424. The processor 138 remains in this state at block 426 until the memory card 128 is removed, following which the processor 138 returns to the start 402 of the method 400.
- the processor 138 determines that the memory card
- the processor 138 begins performing the method 400 as in the no formatting example until the processor 138 determines whether the FAT32 partition is the only partition on the memory card 128 at block 408. Unlike in the no formatting example, in the automatic formatting example the FAT32 partition is the only partition on the memory card 128 and the processor 138 proceeds to block 444 where it determines whether the FAT32 partition is empty. If yes, the processor 138 determines it can safely reformat the memory card 128 without erasing any data the user may want to protect and proceeds to block 436 where it erases the FAT32 partition.
- the processor 138 proceeds to block 438 where it creates a new FAT32 partition of size PI SIZE, which is the non-journaled partition 304.
- the processor 138 then proceeds to block 440 where it creates a new ext4 partition encompassing the remaining usable capacity of the memory card 128; this new partition is the journaled partition 302.
- the processor 138 proceeds to block 442 where it copies the ext4 access files 310 to the journaled partition 302, and the processor 138 then begins writing data such as the video files 312 to the journaled partition 302 at block 424.
- the processor 138 remains in this state at block 426 until the memory card 128 is removed, following which the processor 138 returns to the start 402 of the method 400.
- the processor 138 determines that the memory card 128 has not been properly formatted into the journaled and non-journaled partitions 302,304, but does not automatically format the memory card 128 because there is a chance that by doing so data on the memory card 128 may be inadvertently erased (this example is the "user confirmation example"). In this user confirmation example, the processor 138 seeks user confirmation prior to formatting the memory card 128 into the journaled and non-journaled partitions 302,304.
- the processor 138 waits for any one of several triggering events before prompting the user to confirm he or she wishes to reformat the memory card 128.
- these events comprise the processor 138 determining any one or more of the following:
- the memory card 128 comprises only a single, FAT32 partition, but this partition is not empty (block 444);
- the memory card 128 does not comprise only a single, FAT32 partition, nor does it comprise only one FAT32 partition and one ext4 partition (block 410);
- the memory card 128 comprises only one FAT32 partition and one ext4 partition, but:
- FAT32SIZE does not equal PI SIZE (block 414);
- the processor 138 proceeds to block 430 where it prompts the user for confirmation that the memory card 128 is to be reformatted and checks to see if the user has provided this confirmation at block 432. Until the processor 138 receives this confirmation or until the memory card 128 is removed, the processor 138 loops between blocks 432 and 434 while waiting for user confirmation or for the user to remove the memory card 128. If the user removes the memory card 128 (block 434), the processor 138 proceeds to block 446 and returns to the beginning of the method 400. If the user provides confirmation that the memory card 128 is to be reformatted (block 432), the processor 138 proceeds to block 436 and proceeds as it does in the automatic formatting example.
- the processor 138 erases all partitions on the memory card 128 (block 436), creates the journaled and non-journaled partitions 302,304 (blocks 438 and 440), copies the ext4 access files 310 to the non- journaled partition 304 (block 442), and starts and continues using the journaled partition 302 (block 424) until the user removes the memory card 128 (block 426) in which case the processor 138 returns to the beginning of the method (block 428).
- the processor 138 does not write data to or erase data from the non-journaled partition 304 after having created it and copied the ext4 access files 310 to it. In alternative embodiments, however, the processor 138 may subsequently modify the non-journaled partition 304 even after having completed formatting the memory card 128 by performing the method 400.
- the processor 138 ensures that the memory card 128 is formatted to comprise the journaled and non- journaled partitions 302,304, and that these partitions 302,304 collectively utilize all the memory card's 128 usable capacity.
- the processor 138 may permit usage of a differently formatted memory card 128.
- the processor 138 may permit usage of a memory card 128 having three or more partitions so long as two of those partitions are the journaled and non-journaled partitions 302,304, even though the journaled and non-journaled partitions 302,304 do not collectively utilize all the memory card's 128 usable capacity.
- the processor 138 may not require FAT32SIZE to equal PI SIZE, and instead may allow the memory card 128 to be used so long as the FAT32 partition is large enough to store the ext4 access files 310.
- the processor 138 may simply copy the ext4 access files 310 to the FAT32 partition and, presuming the FAT32 partition is large enough to store those files 310 and the memory card 128 also comprises the ext4 partition, begin storing files on the ext4 partition.
- the processor 138 may automatically reformat the memory card 128 without waiting for user confirmation if the memory card 128 is not partitioned into the journaled and non-journaled partitions 302,304 that collectively utilize all the memory card's 128 usable capacity.
- the processor 138 may automatically partition the memory card 128 when it detects that the memory card 128 has been connected to the memory card reader 116. This embodiment can be used, for example, when each time the memory card 128 is removed its entire contents is presumed to be transferred to a desktop computer or server.
- the removable storage is partitioned via formatting.
- partitioning may be done without formatting.
- the SoC 136 may instead be, for example, a microprocessor, processor, microcontroller, controller, programmable logic controller, field programmable gate array, or an application-specific integrated circuit.
- Examples of computer readable media are non-transitory and include disc-based media such as CD- ROMs and DVDs, magnetic media such as hard drives and other forms of magnetic disk storage, and semiconductor based media such as flash media, SSDs, random access memory, and read only memory.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Television Signal Processing For Recording (AREA)
- Camera Bodies And Camera Details Or Accessories (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
- Management Or Editing Of Information On Record Carriers (AREA)
Abstract
Description
Claims
Priority Applications (12)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MX2016006987A MX362588B (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions. |
AU2013406700A AU2013406700B2 (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
JP2016535138A JP6200091B2 (en) | 2013-11-29 | 2013-11-29 | Camera that supports removable storage device divided into multiple partitions |
CN201380081199.9A CN105900414B (en) | 2013-11-29 | 2013-11-29 | Support the video camera for being divided into the removable Storage of multiple subregions |
NZ720281A NZ720281A (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
EP13898152.7A EP3075144A4 (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
CA2929999A CA2929999C (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
BR112016011973A BR112016011973A8 (en) | 2013-11-29 | 2013-11-29 | camera, method for storage partitioning and computer readable non-transitory medium |
PCT/CA2013/050920 WO2015077861A1 (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
KR1020167017130A KR102098442B1 (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
IL245614A IL245614A0 (en) | 2013-11-29 | 2016-05-11 | Camera supporting removable storage divided into multiple partitions |
ZA2016/04293A ZA201604293B (en) | 2013-11-29 | 2016-06-24 | Camera supporting removable storage divided into multiple partitions |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CA2013/050920 WO2015077861A1 (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015077861A1 true WO2015077861A1 (en) | 2015-06-04 |
Family
ID=53198130
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA2013/050920 WO2015077861A1 (en) | 2013-11-29 | 2013-11-29 | Camera supporting removable storage divided into multiple partitions |
Country Status (12)
Country | Link |
---|---|
EP (1) | EP3075144A4 (en) |
JP (1) | JP6200091B2 (en) |
KR (1) | KR102098442B1 (en) |
CN (1) | CN105900414B (en) |
AU (1) | AU2013406700B2 (en) |
BR (1) | BR112016011973A8 (en) |
CA (1) | CA2929999C (en) |
IL (1) | IL245614A0 (en) |
MX (1) | MX362588B (en) |
NZ (1) | NZ720281A (en) |
WO (1) | WO2015077861A1 (en) |
ZA (1) | ZA201604293B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102018110568A1 (en) * | 2018-05-03 | 2019-11-07 | Basler Ag | Network camera and system |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP7292291B2 (en) * | 2017-10-26 | 2023-06-16 | ユー・アール・フラッシュ エル・エル・シー | Media storage device with multiple partitions |
CN107908439B (en) * | 2017-11-16 | 2019-05-10 | 深圳华盟工程再担保有限公司 | The operation and guard method of a kind of large data processing software on movable storage device |
CN113961151B (en) * | 2021-11-02 | 2024-04-02 | 锐凌无线有限责任公司 | Storage method and device of fault log, electronic equipment and storage medium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120179730A1 (en) * | 2009-07-10 | 2012-07-12 | Walter Slegers | Data Storage System and Method |
US20120194702A1 (en) * | 2011-02-02 | 2012-08-02 | Canon Kabushiki Kaisha | Moving image data recording apparatus |
US20120194691A1 (en) * | 2011-02-02 | 2012-08-02 | Canon Kabushiki Kaisha | Imaging apparatus |
US20120221609A1 (en) * | 2009-07-10 | 2012-08-30 | Jaap-Jan Boor | Data Storage System and Method |
US8572310B2 (en) * | 2007-11-06 | 2013-10-29 | Samsung Electronics Co., Ltd. | Invalidating storage area of non-volatile storage medium based on metadata |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3182129B2 (en) * | 1998-10-19 | 2001-07-03 | 富士通株式会社 | Storage medium and control method thereof |
JP3522250B2 (en) * | 2000-10-27 | 2004-04-26 | 株式会社ソニー・コンピュータエンタテインメント | Partition creation method and deletion method, recording medium recording program, and information processing apparatus |
US7155460B2 (en) * | 2003-03-18 | 2006-12-26 | Network Appliance, Inc. | Write-once-read-many storage system and method for implementing the same |
JP2008027108A (en) * | 2006-07-20 | 2008-02-07 | Matsushita Electric Ind Co Ltd | Recorder, storage medium and recording method, and recording program |
JP2008050134A (en) * | 2006-08-25 | 2008-03-06 | Toshiba Elevator Co Ltd | Crime prevention camera of elevator |
US9501492B2 (en) * | 2006-10-24 | 2016-11-22 | Marvell World Trade Ltd. | Combination journaling/non-journaling file system |
US20100257218A1 (en) * | 2009-04-03 | 2010-10-07 | Konstantin Iliev Vassilev | Merging multiple heterogeneous file systems into a single virtual unified file system |
-
2013
- 2013-11-29 NZ NZ720281A patent/NZ720281A/en unknown
- 2013-11-29 CN CN201380081199.9A patent/CN105900414B/en active Active
- 2013-11-29 AU AU2013406700A patent/AU2013406700B2/en active Active
- 2013-11-29 EP EP13898152.7A patent/EP3075144A4/en not_active Withdrawn
- 2013-11-29 KR KR1020167017130A patent/KR102098442B1/en active IP Right Grant
- 2013-11-29 MX MX2016006987A patent/MX362588B/en active IP Right Grant
- 2013-11-29 WO PCT/CA2013/050920 patent/WO2015077861A1/en active Application Filing
- 2013-11-29 CA CA2929999A patent/CA2929999C/en active Active
- 2013-11-29 JP JP2016535138A patent/JP6200091B2/en active Active
- 2013-11-29 BR BR112016011973A patent/BR112016011973A8/en not_active Application Discontinuation
-
2016
- 2016-05-11 IL IL245614A patent/IL245614A0/en unknown
- 2016-06-24 ZA ZA2016/04293A patent/ZA201604293B/en unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8572310B2 (en) * | 2007-11-06 | 2013-10-29 | Samsung Electronics Co., Ltd. | Invalidating storage area of non-volatile storage medium based on metadata |
US20120179730A1 (en) * | 2009-07-10 | 2012-07-12 | Walter Slegers | Data Storage System and Method |
US20120221609A1 (en) * | 2009-07-10 | 2012-08-30 | Jaap-Jan Boor | Data Storage System and Method |
US20120194702A1 (en) * | 2011-02-02 | 2012-08-02 | Canon Kabushiki Kaisha | Moving image data recording apparatus |
US20120194691A1 (en) * | 2011-02-02 | 2012-08-02 | Canon Kabushiki Kaisha | Imaging apparatus |
Non-Patent Citations (1)
Title |
---|
See also references of EP3075144A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102018110568A1 (en) * | 2018-05-03 | 2019-11-07 | Basler Ag | Network camera and system |
DE102018110568B4 (en) | 2018-05-03 | 2019-12-19 | Basler Ag | Network camera and system |
Also Published As
Publication number | Publication date |
---|---|
ZA201604293B (en) | 2019-01-30 |
CA2929999A1 (en) | 2015-06-04 |
BR112016011973A8 (en) | 2020-05-05 |
AU2013406700A1 (en) | 2016-06-16 |
JP6200091B2 (en) | 2017-09-20 |
JP2017504926A (en) | 2017-02-09 |
CA2929999C (en) | 2020-05-05 |
CN105900414A (en) | 2016-08-24 |
KR102098442B1 (en) | 2020-04-08 |
KR20160091972A (en) | 2016-08-03 |
CN105900414B (en) | 2019-10-15 |
NZ720281A (en) | 2019-04-26 |
MX362588B (en) | 2019-01-25 |
MX2016006987A (en) | 2017-01-19 |
AU2013406700B2 (en) | 2018-09-27 |
BR112016011973A2 (en) | 2017-08-08 |
EP3075144A4 (en) | 2017-11-15 |
IL245614A0 (en) | 2016-06-30 |
EP3075144A1 (en) | 2016-10-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10334145B2 (en) | Camera supporting removable storage divided into a journaled partition and a non-journaled partition | |
US8868628B2 (en) | Sharing computer data among computers | |
US7184264B2 (en) | Connectable memory devices to provide expandable memory | |
US8135880B2 (en) | USB mass storage locking | |
US8495290B2 (en) | Methods for implementation of an array of removable disk drives | |
WO2016110004A1 (en) | Management method and apparatus for disk storage space, and storage device | |
CN102541475A (en) | Data storage method and data storage device | |
JP2008511916A (en) | Memory device with hub function | |
US20170220506A1 (en) | Modular Software Defined Storage Technology | |
CA2929999C (en) | Camera supporting removable storage divided into multiple partitions | |
US20050041459A1 (en) | Interface for removable storage devices | |
CN107526616B (en) | Method and device for writing and reading data of BMC by host | |
EP2227739A1 (en) | Device and method for integrating file systems | |
CN101189591A (en) | A portable data storage device | |
US20040054827A1 (en) | Large volume storage device with a memory card adapting interface | |
US20080183836A1 (en) | Network attached storage (nas) server having a plurality of automated media portals | |
CN103176832B (en) | One kind UNIX operating system runs method and the device of virtual opetrating system | |
US7734713B2 (en) | Method and system for arbitrating computer access to a shared storage medium using SCSI protocol | |
US20130132629A1 (en) | Apparatus of storage medium for interfacing both host and mobile device | |
US20030110300A1 (en) | Virtual storage interface device | |
JP2004055102A (en) | Large capacity storage medium provided with storage card conversion interface | |
CN112040162B (en) | Control method and control device for storing camera shooting video data and video acquisition equipment | |
US20240231656A9 (en) | Host independent formatting of storage devices | |
US20240134547A1 (en) | Host independent formatting of storage devices | |
JP3093136U (en) | Large-capacity storage carrier |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13898152 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 2929999 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 245614 Country of ref document: IL |
|
REEP | Request for entry into the european phase |
Ref document number: 2013898152 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2016/006987 Country of ref document: MX Ref document number: 2013898152 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016535138 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112016011973 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 2013406700 Country of ref document: AU Date of ref document: 20131129 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20167017130 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 112016011973 Country of ref document: BR Kind code of ref document: A2 Effective date: 20160525 |