JP6200091B2 - Camera that supports removable storage device divided into multiple partitions - Google Patents

Description

  The present disclosure generally relates to a camera that supports a removable storage device that is divided into a plurality of partitions.

  Cameras that can write files to removable storage devices are becoming increasingly popular. Examples of camera formats are security cameras, and examples of file formats that can be written to removable storage devices are audio files, video files (including video files with audio tracks), and still images. Security cameras that provide removable storage devices are popular because they offer the convenience of allowing storage (memory) of video files even when the camera is disconnected from the network or when the network fails. It has become. Accordingly, there is ongoing research and development for methods, systems, and techniques related to improving the ability of cameras to use removable storage devices.

  According to the first aspect, a camera body having an opening that allows light to enter the camera body, and at least a part of the light that is disposed inside the camera body and enters the camera body. An image sensor positioned to receive; (i) a journaled partition using a journaling file system; and (ii) a non-journaled partition using a non-journaled file system natively supported by the operating system; And a removable media circuit configured to write to a removable storage device that is formatted to include, and communicatively connected to the image sensor and the removable media circuit, using the journaling file system And a processing circuit configured to store a file in the journaled partition, wherein the non-journaled partition accesses the file stored in the journaled partition using the operating system. Thus, a camera is provided that stores computer program code executable by a processor.

  All available capacity of the removable storage device can be fully allocated to the journaled and non-journaled partitions. The processing circuitry optionally does not write data to 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.

  According to another aspect, a camera body having an opening that allows light to enter the camera body, and at least a part of the light that is disposed inside the camera body and enters the camera body is received. An image sensor positioned as described above, a removable media circuit configured to write to a removable storage device, and communicatively connected to the image sensor and the removable media circuit to perform a particular method A processing circuit configured to: (i) a journaled partition using a journaling file system and a non-journaled file system natively supported by the operating system Unjournaled partitions Partitioning said removable storage device to include: (ii) computer program code executable by a processor to access a file stored in said journaled partition using said operating system And storing in the non-journaled partition.

  All available capacity of the removable storage device can be fully allocated to the journaled and non-journaled partitions. The processing circuitry optionally does not write data to or delete data from the non-journaled partition after storing the computer program code in the non-journaled partition. The processing circuit is further configured to store one or more of a video file, an audio file, and a still image obtained from the light incident on the image sensor after partitioning the removable storage device. Can be done. The journaled partition may have a larger capacity than the non-journaled partition.

The method performed by the processing circuit further includes the following steps before partitioning the removable storage device:
(A) determining whether the removable storage device includes only a first initial partition that uses the non-journaling file system and whether the first initial partition is empty; Erasing the first initial partition when the removable storage device includes only the first initial partition and the first initial partition is empty;
(B) Determining whether the removable storage device includes only a first initial partition that uses the non-journaling file system and a second initial partition that uses the journaling file system, and the removable storage device If it does not include only the first and second initial partitions, it prompts the user to confirm that the partitioning process will be performed and partitions the partition after receiving a user confirmation. Starting the process,
(C) When the removable storage device includes only the first and second initial partitions, the size of the first initial partition is determined, and the size of the first initial partition is journaled. Prompting the user to confirm that the partitioning process will be performed if not equal to a fixed size of the partition, and starting the partitioning step after receiving the user confirmation;
(D) determining whether the computer program code is present in the first initial partition if the size of the first initial partition is equal to the size of the non- journaled partition; If computer program code is not present in the first initial partition, prompts the user to confirm that the partitioning process will be performed and initiates the partitioning after receiving user confirmation The process of
When the (e) said computer program code is present in the first initial partition, whether all the capacity available in the removable storage device is fully allocated to the first and second initial partition And confirming that the partitioning process will be performed to the user when the capacity of the removable storage device is not completely allocated to the first and second initial partitions. Initiating the partitioning after receiving a user confirmation,
Any one or more of the above can be included.

  The camera may be a security camera.

  According to another aspect, a method of partitioning a removable storage device for a camera, the step of determining whether the removable storage device is connected to the camera, and the removable storage device to the camera Said connected to include (i) a journaled partition that uses a journaling file system and a non-journaled partition that uses a non-journaled file system that is natively supported by the operating system. Removable storage device can be partitioned and (ii) executable by a processor to access files stored in the journaled partition using the operating system The computer program code is stored in the journaling that is not partitioned, the method comprising the step of using said camera is provided so on.

  All available capacity of the removable storage device can be fully allocated to the journaled and non-journaled partitions. After partitioning the removable storage device, the camera can store one or more of a video file, an audio file, and a still image obtained from the light incident on the image sensor. The journaled partition may have a larger capacity than the non-journaled partition.

The method further includes the following steps before partitioning the removable storage device:
(A) determining whether the removable storage device includes only a first initial partition that uses the non-journaling file system and whether the first initial partition is empty; Using the camera to erase the initial partition if the storage device includes only the first initial partition and the first initial partition is empty;
(B) Determining whether the removable storage device includes only a first initial partition that uses the non-journaling file system and a second initial partition that uses the journaling file system, and the removable storage device If it does not include only the first and second initial partitions, it prompts the user to confirm that the partitioning process will be performed and partitions the partition after receiving a user confirmation. Using the camera, such as starting a process,
(C) When the removable storage device includes only the first and second initial partitions, the size of the first initial partition is determined, and the size of the first initial partition is journaled. If not equal to a fixed size of the partition, prompt the user to confirm that the partitioning process will be performed and start the partitioning step after receiving the user confirmation Using the camera as
(D) determining whether the computer program code is present in the first initial partition if the size of the first initial partition is equal to the size of the non- journaled partition; If computer program code is not present in the first initial partition, prompts the user to confirm that the partitioning process will be performed and initiates the partitioning after receiving user confirmation Using the camera, and so on.
When the (e) said computer program code is present in the first initial partition, whether all the capacity available in the removable storage device is fully allocated to the first and second initial partition And confirming that the partitioning process will be performed to the user when the capacity of the removable storage device is not completely allocated to the first and second initial partitions. Initiating the partitioning after receiving a user confirmation,
Any one or more of the above can be included.

  According to another aspect, there is provided a non-transitory computer readable medium encoding therein statements and instructions for partitioning a removable storage device for the camera by performing a particular method, The method includes the steps of determining whether the removable storage device is connected to the camera, and when the removable storage device is connected to the camera, any of the methods listed above Or using any suitable modification and combination thereof to use the camera.

  The summary of the invention does not necessarily describe the complete scope of all embodiments. Other aspects, features, and advantages will become apparent to those skilled in the art upon consideration of the following description of specific embodiments.

  The accompanying drawings illustrate one or more exemplary embodiments.

1 is a front perspective view of a security camera that supports a removable storage device that is divided into multiple partitions, according to one embodiment. FIG. 2 is a rear perspective view of a security camera that supports a removable storage device that is divided into multiple partitions, according to one embodiment. FIG.

It is a block diagram of the security camera of FIG.

It is a memory map of the removable storage device used with the security camera of FIG.

6 illustrates a method according to another embodiment for formatting a removable storage device used in the security camera of FIG. 6 illustrates a method according to another embodiment for formatting a removable storage device used in the security camera of FIG.

  The terms indicating directions such as “top”, “bottom”, “upward”, “downward”, “vertically” and “horizontally” are used in the following description merely to present relative references. And is not intended to suggest any limitation as to how any product is positioned during use or how it is installed in the assembly or to the environment Absent. In addition, as used herein, the term “coupled” as well as such as “coupled”, “couples” and “coupled” Terminology variations are intended to include indirect and direct connections, unless otherwise indicated. For example, when the first device is coupled to the second device, the coupling can be by direct connection or by indirect connection through other devices and connections. Similarly, if the first device is communicatively coupled to the second device, the communication can be by direct connection or by indirect connection through other devices and connections.

  Removable storage devices for cameras can include various types of removable non-transitory computer readable media. For example, a removable storage device is designed to interface with a port accessible from outside the camera housing and can be connected to and disconnected from the camera as desired by the user, such as a memory card, external hard drive Or may take the form of a solid state drive (SSD). A removable storage device can be connected directly to the camera, such as when a memory card is inserted into a memory card reader that forms part of the camera, or when an external SSD drive is connected to the camera's USB port, or In particular, it can 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.

  Regardless of which type of removable storage device is used, the camera writes data to the storage device and optionally reads data from the storage device according to the file system. Many different types of file systems are known in the art. For example, a common file system used in a memory card (an example labeled as 128 in FIG. 2), which is one type of removable storage device, is “FAT32”. One common type of memory card is a secure digital (SD) memory card (SD card). One reason that FAT32 is generally used is that both Windows® and OS X® operating systems support FAT32 natively. This allows the user to simply remove the memory card from the camera and insert the memory card into a card reader connected to a desktop computer running a Windows® or OS X® operating system. This makes it possible to access a video file stored in a memory card formatted in FAT32. However, FAT 32 does not have a recovery function, especially for power loss or if the removable storage device is disconnected from the camera without prior notification ("abrupt disconnection"). A power loss or sudden disconnect may result in corruption of files stored using FAT32.

  Other file systems, known as journaling file systems, are inherently more resilient to power loss and sudden disconnection than FAT32, which is an example of a non-journaling file system. In the journaling file system, a file called a journal that records the trajectory of changes made to a file stored using the file system is held. In case of power loss or sudden disconnection, the journal is accessed and used to restore or verify the remaining integrity of the file system. An example of a journaling file system is “ext4”. However, many journaling file systems, including ext4, are not natively supported by Windows® and OS X® operating systems.

  Thus, if ext4 or any one of several other journaling file systems are to be used for removable storage, run Windows® and OS X® operating systems There are technical challenges to be overcome in order to maintain compatibility with the computers inside. One way to address this challenge is to require the user to install third party software on the user's computer that provides non-native support for the journaling file system being used. However, requesting the user to do this is not user friendly and is not convenient. Another solution is to provide the user with removable storage via an IP network, either via a web interface that forms part of the camera's firmware, or via proprietary software installed on one or both of the camera and the user's computer. Requesting access to the device. However, using this solution requires that the camera be an IP camera connected to an IP network. Files stored using removable storage devices are inaccessible when the network is down or when the camera is disconnected from the network. In addition, accessing a file through the web interface may be one or more orders of magnitude slower than accessing the file by connecting a removable storage device directly to the computer.

  Embodiments described herein relate to a camera that supports a removable storage device having at least two partitions. In one embodiment, the removable storage device has a journaled partition and a non-journaled partition, the journaled partition using a journaling file system, and the non-journaled partition is, for example, Windows ( It uses a non-journaled file system that is natively supported by operating systems such as registered trademark and OS X operating system. Journaled partitions are typically much larger than non-journaled partitions and are used as main storage on removable storage devices. A computer program code is stored in a non-journaled partition, and the program code is stored in a journaled partition using an operating system, for example, by a processor such as a processor used in a desktop computer. Executable to access stored files. Various embodiments herein further describe how and when to format removable storage to support journaling and non-journaling file systems. A method and method for performing the above will be described. By including computer program code in the non-journaled partition that allows the operating system to access files on the journaled partition, the user must separately install third-party software on the user's computer. Benefit from the journaling file system without having to access the camera only via the IP network. Therefore, the security camera can use the removable storage device in a manner that has a recovery function against power loss and sudden disconnection of the removable storage device. The illustrated embodiment is a security camera, but in another embodiment (not shown), the camera can be another type of camera, such as a traffic camera or a handheld camera. The data that the camera stores in the removable storage device can be any type of data such as audio files, video files (including video files with audio tracks), and still images.

  Referring now to FIGS. 1A and 1B, there are shown a front perspective view and a rear perspective view, respectively, of a security camera 100 that supports a removable storage device divided into multiple partitions, according to one embodiment. The camera 100 is accommodated in the camera body 102. Although the camera mount 104 exists in the upper part and the lower part of the main body 102, only one of the upper parts of the camera mount 104 can be visually recognized in FIGS. An opening 106 exists in front of the main body 102, and light enters the camera main body 102 through the opening 106 and is not shown in FIG. 1A or 1B. And is processed as a result to produce a video image.

  A control plate 122 having various inputs and outputs related to camera operation is present on the rear surface of the camera body 102. At the left end of the control plate 122 is a power control block 108 for accepting a power plug, but alternatively, in some embodiments, the camera 100 uses Power over Ethernet (PoE) technology. Can be powered. In this case, the power control block 108 can remain unused during camera operation. A network jack in the form of an RJ45 (Ethernet) jack 114 is present adjacent to the power control block 108. The RJ45 jack 114 accepts an RJ45 plug (not shown) that connects the camera to the IP network. In opposite corners of the top surface of the RJ45 jack 114, a connection status LED 110 and a link LED 112 that provide information about the state of the camera 100 and information about whether the camera 100 is connected to an active Ethernet connection, respectively. Exists. Removable media circuitry in the form of a memory card reader, some associated host controller, and similar circuitry (hereinafter collectively “memory card reader 116”) resides below the RJ45 jack 114 and the removable media. The circuit accepts a removable storage device in the form of a memory card (not shown in FIG. 1, but labeled as 128 in FIG. 2). An audio / video connector 118 that accepts a 3.5 mm plug for connection to a microphone or monitor, and a universal input / output port 120 for connecting the camera 100 to various external devices are provided on the RJ45 jack 114 and control plate 122. It exists between the right end.

  The camera 100 of FIG. 1 uses a removable storage device in the form of a memory card 128, but in another embodiment (not shown), the removable storage device can be any non-transitory, removable computer-readable medium. It can be a suitable type. For example, the removable storage device may include one or more of magnetic tape, flexible disks, zip disks, optical disks, portable external hard drives and SSDs, and flash media such as USB flash drives. The removable storage device can be connected directly to the camera 100, for example by inserting the memory card 128 into the memory card reader 116, or indirectly connected to the camera 100 by daisy chaining several USB hard drives together. Alternatively, it can be indirectly connected to the camera 100 via a network such as the Internet or a local area network.

  Further, FIG. 1 shows a camera 100 that is a box body type camera, but in another embodiment (not shown), the camera 100 may be a dome type camera, a bullet type camera, a pan / tilt / zoom (PTZ). It can be a different type of camera, such as a camera or a multi-head camera.

  Referring now to FIG. 2, a block diagram of the security camera 100 is shown. A lens 112 is positioned to refract light onto the image sensor 126, and the image sensor 126 outputs a digital signal to the on-chip system 136 (SoC) in response to the incident light. The SoC 136 includes a processor 138, an image signal processor (ISP) 126, a media access controller (MAC) 144, and an I2C interface 142. The processor 138 communicates with each of the ISP 126, the MAC 144, and the I2C interface 142. The ISP 126 communicates with the image sensor 126 using the MIPI (registered trademark) protocol, and the I2C interface 142 communicates with the image sensor 126 using the I2C protocol. An I2C interface 142 is used to control camera parameters such as gain, exposure, and frame rate.

  The SoC 136 constitutes a part of the processing circuit of the camera 100. The SoC 136 communicates with various different components that make up the camera 100. The SoC 136, and more specifically, the processor 138 communicates with a removable media circuit in the form of a memory card reader 116. The SoC 136 is further a physical layer integrated circuit (PHY) 146 that communicates with the MAC 144; a flash memory that is an example of a non-transitory computer-readable medium that is non-volatile and stores statements and instructions for causing the SoC 136 to perform tasks such as image processing 148; another example of a non-transitory computer readable medium, but volatile and temporarily used by the SoC 136 to store information; a RAM 150 for the task executing workspace; connection status and link LEDs 110, 112 Audio / video connector 118; as well as general purpose input / output port 120;

  In the illustrated embodiment, the removable media circuit includes a memory card reader 116, but in another embodiment (not shown), the removable media circuit may be any suitable that allows the SoC 136 to communicate with the removable media. Can be a simple circuit. For example, alternatively, the removable media circuit may allow the SoC 136 to communicate with an external portable SSD or by other forms of removable media via eSATA, FireWire®, ThunderBolt®, or proprietary connection. A USB port and a controller that allow communication can be included.

  Further, Ethernet magnetics 152 that communicates with RJ45 jack 114 and PHY 146 and power control block 108 that supplies power to the various electrical components that make up camera 100 form part of camera 100. In the illustrated embodiment, the power control block 108 accepts DC power as an input, but in another embodiment (not shown), for example, using an AC adapter with a battery or using the PoE technology described above with respect to FIG. In use, power can be supplied to the camera 100.

  Although FIG. 1 shows a camera 100 housed in a single housing that is a camera body 102, in another embodiment (not shown), the camera 100 can be divided between multiple housings, Several components that communicate with each other may be collectively included. For example, camera circuitry may be arranged in different housings and connected via cables to reduce various camera components, as described in PCT patent application PCT / CA2013 / 050334. It can be split across the printed circuit board.

  In addition, although FIGS. 1 and 2 show a lens 112 that forms part of the camera 100, in another embodiment (not shown), the camera 100 may be a lensless camera.

  Referring now to FIG. 3, a memory map 300 of the memory card 128 after being formatted into a partition 302 journaled using the ext4 file system and a partition 304 not journaled using the FAT32 file system is shown. Has been. In particular, there is a partition table 314 that describes the location and nature of the journaled and non-journaled partitions 302 and 304 at the beginning of the memory card 128 address space. The partition table 314 can be, for example, a master boot record or a GUID partition table. The journaled partition 302 includes a journal 306 that ext4 uses to log changes made to files in the file system; and information about the camera 100 such as the MAC, serial number, name, and location of the camera 100. Including, camera metadata 313 that can be used by off-camera software applications in classifying and processing data stored by the camera 100 in the journaled partition 302; and storage in which the processor 138 can write data and then read data And a space. As shown in memory map 300, a portion of the storage space is filled with video file 312, while the remaining portion of the storage space is empty and is used by processor 138 as needed. Is possible.

  The non-journaled partition 304 is a file allocation table 308 that is an index table identifying the cluster that includes the non-journaled partition 304; and how to use the ext4 access file 310 to explain to the user A teaching file 311 including files such as a readme file or a help file; and a processor such as a processor in a desktop computer using an operating system such as Windows® and OS X® operating system Computer program code executable to access files stored in the journaled partition 302 No ext4 access file 310; including (hereinafter, this processor is a "client processor", the operating system in which the client processor executes is "client OS"). In one embodiment, the computer program code is http: // sourceforge. Ext2Read available from net / projects / ext2read /, but in another embodiment (not shown), this program code may vary depending on, for example, the type of file system used in the journaled partition 302 Can be. In the illustrated embodiment, the computer program code includes a plurality of files, but in another embodiment (not shown), the computer program code can be only a single file.

  As the memory map 300 shows, in the illustrated embodiment, all available capacity of the memory card 128 is fully allocated to the journaled and non-journaled partitions 302 and 304. Further, the non-journaled partition 304 is intended to store an ext4 access file 310, while the journaled partition 304 is typically intended to store a much larger video file 312. Thus, the capacity of the non-journaled partition 304 is smaller than the journaled partition 302.

  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. If the client OS is a Windows® and OS X® operating system, the user can natively access the non-journaled partition 304 but natively access the journaled partition 302 Can not do it. Thus, the user can use a client processor to execute an ext4 access file 310 that gives the user access to the journaled partition 302 and thus access to the video file 312. In another embodiment (not shown), the non-journaled partition 304 is placed in its root directory with autorun. inf files can also be stored, and the autorun. The inf file is configured to cause the Windows® operating system to automatically execute the ext4 access file as soon as the client processor gains access to the memory card 128.

  4A and 4B collectively illustrate a method 400 according to another embodiment for formatting a removable storage device used in the security camera 100. Specifically, the method 400 relates to an embodiment in which the removable storage device includes a memory card 128 and the memory card 128 is formatted by a user rather than the camera 100 manufacturer. The illustrated embodiment of the method 400 is intended to use FAT32 as the non-journaling file system and ext4 as the journaling file system, but in another embodiment (not shown), a different journaling file is used. System and non-journaling file systems can be used. For example, another journaling file system includes ext2, ext3, NTFS, JFS, and exFAT, while another non-journaling file system includes FAT16, FAT32, CDFS, and UDF. Similarly, the method 400 relates to a removable storage device in the form of a memory card 128, but in another embodiment (not shown), a removable storage device including other types of computer readable media is used. be able to.

  Various use cases embodied by the method 400 are described below.

[No formatting required]
In one embodiment, the memory card 128 is already properly formatted in the journaled and non-journaled partitions 302 and 304, and the processor 138 does not reformat the memory card 128 when this is determined (this An example is “Example not formatted”).

  In this illustrative example, processor 138 begins executing the method from block 402 and proceeds to block 404 where processor 138 enters a loop that waits for the user to connect memory card 128 to the removable media circuit. Thus, it is determined whether or not the memory card 128 is connected to the camera 100. If the user connects the memory card 128 to the removable media circuit, the processor 138 proceeds to block 406 where the processor 138 reads the partition table 314 on the memory card 128. If memory card 128 has already been formatted and includes at least one partition (“first initial partition”), processor 138 determines at block 408 that the first initial partition is the only partition on memory card 128. To determine whether the FAT32 is used. If no, the processor 138 proceeds to block 410 where the processor 138 determines whether the memory card 128 includes another partition (“second initial partition”), the first and second initial partitions. Configures the only partition on the memory card 128 and whether the first and second initial partitions are FAT32 and ext4 partitions, respectively. If YES, depending on the size of these partitions, the memory card 128 may already be properly formatted and ready for use. The initial partition using FAT32 is hereinafter referred to as “FAT32 partition”, and the other initial partition using ext4 is hereinafter referred to as “ext4 partition”. However, as described above, in other embodiments (not shown), different journaling file systems, different non-journaling file systems, or both can be used.

Accordingly, the processor 138 proceeds to block 412 where the processor 138 reads the size of the FAT32 partition. Hereinafter, it is “FAT32 size (FAT32SIZE)”. When processor 138 reads FAT32SIZE, processor 138 proceeds to block 414, where processor 138 determines whether FAT32SIZE is equal to P1SIZE, which is a constant name representing the fixed size of the non-journaled partition; Determine. If FAT32SIZE is equal to P1SIZE, the non-journaled partition 304 proceeds to block 416 where the processor 138 determines whether all ext4 access files 310 already exist in the FAT32 partition. . If all ext4 access files 310 are present, the processor 138 reads the entire capacity of the memory card 128 at block 418 and the size of the ext4 partition at block 420. Hereinafter, it is “EXT4SIZE”. The processor 138 then determines at block 422 whether all available capacity of the memory card 128 has been fully allocated to the FAT32 and ext4 partitions. If yes, the processor 138 concludes that the memory card 128 is properly formatted into the journaled and non-journaled partitions 302 and 304 and treats the ext4 partition as a journaled partition 302, resulting in: In block 424, data writing to the ext4 partition is started. The processor 138 remains in this state at block 426 until the memory card 128 is removed, after which the processor 138 returns to the start 402 of the method 400.

[Auto format execution]
In another embodiment, the processor 138 determines that the memory card 128 is not properly formatted in the journaled and non-journaled partitions 302 and 304 and automatically reformats the memory card 128 (this The example is an “example of automatically formatting”).

In this illustrative example, processor 138 begins executing the method 400 of the non-formatting example until the processor 138 determines at block 408 that the FAT32 partition is the only partition on the memory card 128. Unlike the unformatted embodiment, in the automatically formatted embodiment, the FAT32 partition is the only partition on the memory card 128 and the processor 138 proceeds to block 444 where the processor 138 is , It is determined whether the FAT32 partition is empty. If yes, the processor 138 determines that the processor 138 can safely reformat the memory card 128 without erasing any data that the user wishes to protect, and proceeds to block 436 where the processor 138 , Erase FAT32 partition. Once the FAT32 partition is erased, the processor 138 proceeds to block 438 where the processor 138 creates a new FAT32 partition of size P1SIZE, which is the non-journaled partition 304. The processor 138 then proceeds to block 440 where the processor 138 creates a new ext4 partition that includes the remaining usable capacity of the memory card 128, which is the journaled partition 302. is there. After the partition 302 journaled is generated, the processor 138 proceeds to block 442, where the processor 138 copies the partition 304 that is not journaled ext4 access file 310, then processor 138 may block At 424, start writing data such as video file 312 to journaled partition 302. As with the non-formatted embodiment, processor 138 remains in this state until memory card 128 is removed at block 426, after which processor 138 returns to start 402 of method 400.

[User confirmation obtained before formatting]
In another embodiment, the processor 138 determines that the memory card 128 is not properly formatted in the journaled and non-journaled partitions 302 and 304, but the memory card 128 automatically formats the memory card Since the data on 128 may be erased unintentionally, the memory card 128 is not automatically formatted (this embodiment is a “user verification embodiment”). In this user verification embodiment, processor 138 requests user verification before formatting memory card 128 into journaled and non-journaled partitions 302 and 304.

In the user confirmation embodiment, the processor 138 waits for any one of several trigger events before prompting the user to confirm that the person wishes to reformat the memory card 128. In the embodiment of FIG. 4, these events are handled by the processor 138 as follows:
(I) the memory card 128 contains only a single FAT32 partition, but this partition is not empty (block 444);
(Ii) the memory card 128 does not contain only a single FAT32 partition, nor does it contain only one FAT32 partition and one ext4 partition (block 410);
(Iii) The memory card 128 includes only one FAT32 partition and one ext4 partition,
(1) FAT32SIZE is not equal to P1SIZE (block 414);
(2) The ext4 access file 310 does not exist in the FAT32 partition (block 416), or (3) all available capacity of the memory card 128 is not completely allocated to the FAT32 and ext4 partitions (block 422),
Determining one or more of the above.

  If any one or more of the conditions listed above occurs, the processor 138 proceeds to block 430 where the processor 138 will reformat the memory card 128 to the user. Prompt to confirm, and at block 432, determine whether the user has presented this confirmation. Until the processor 138 receives this confirmation or until the memory card 128 is removed, the processor 138 waits for user confirmation or while waiting for the user to remove the memory card 128 while blocks 432 and 434 Loop between. If the user removes the memory card 128 (block 434), the processor 138 proceeds to block 446 and returns to the start of the method 400. If the user presents confirmation that the memory card 128 will be reformatted (block 432), the processor 138 proceeds to block 436 and proceeds in a manner similar to that performed by the processor 138 in the automatically formatting embodiment. Proceed. That is, processor 138 erases all partitions on memory card 128 (block 436), creates journaled and non-journaled partitions 302 and 304 (blocks 438 and 440), and journals ext4 access file 310. Copy to the un-partitioned partition 304 (block 442) and begin or continue to use the journaled partition 302 until the user removes the memory card 128 (block 426) (block 424). When the user removes the memory card 128, the processor 138 returns to the beginning of the method (block 428).

  In the method 400 of FIGS. 4A and 4B, the processor 138 creates a non-journaled partition 304 and copies the ext4 access file 310 to the partition, and then does not write data to the partition or writes data from the partition. Do not erase. However, in another embodiment, the processor 138 can continue to change the non-journaled partition 304 by performing the method 400, even after the memory card 128 has been formatted. .

  In addition, in the method 400 of FIGS. 4A and 4B, the processor 138 determines that the memory card 128 is formatted to include journaled and non-journaled partitions 302 and 304, and that these partitions 302 and 304 are It is guaranteed that all available capacity of the memory card 128 is used collectively. In another embodiment (not shown), the processor 138 may allow the use of a memory card 128 that is formatted differently. For example, the processor 138 may have the journaled and non-journaled partitions 302 and 304 of the memory card 128 as long as two of the three or more partitions are journaled and non-journaled partitions 302 and 304. The use of the memory card 128 having the three or four or more partitions can be permitted even though all the usable capacity is not collectively used. Alternatively or additionally, processor 138 does not require that FAT32 SIZE be equal to P1SIZE and instead indicates that memory card 128 is used as long as the FAT32 partition is large enough to store ext4 access file 310. Can be tolerated. Alternatively or additionally, if the ext4 access file 310 is not present in the FAT32 partition, the processor 138 may simply copy the ext4 access file 310 to the FAT32 partition, rather than reformatting the entire memory card 128, Assuming that the FAT32 partition is large enough to store those files 310, and the memory card 128 also includes an ext4 partition, storage of the files in the ext4 partition may begin.

  In another alternative embodiment (not shown), the memory cards 128 are in journaled and non-journaled partitions 302 and 304 that collectively utilize all available capacity of the memory card 128. If not, the processor 138 can automatically reformat the memory card 128 without waiting for user confirmation.

  As an example of another alternative embodiment not shown, if the processor 138 detects that the memory card 128 is connected to the memory card reader 116, the processor 138 automatically partitions the memory card 128. Can be divided. This embodiment may be used, for example, when it is assumed that the entire contents of the memory card 128 are transferred to a desktop computer or server each time the memory card 128 is removed.

  In the illustrated embodiment, the removable storage device is partitioned by formatting. In another embodiment (not shown), partitioning can be done without formatting.

  In the previous embodiment, SoC 136 is used, but in another embodiment (not shown), SoC 136 is instead used, for example, a microprocessor, processor, microcontroller, controller, programmable logic controller, field programmable gate. It can be an array or an application specific integrated circuit. Examples of computer-readable media are non-transitory, such as disk-based media such as CD-ROM and DVD, magnetic media such as hard drives and other forms of magnetic disk storage, semiconductor-based such as flash media, etc. Media, SSD, random access memory (RAM), and read only memory (ROM).

  Any element of any aspect or embodiment described herein may be implemented or combined with any element of any other aspect or embodiment described herein. It is intended to obtain.

  For convenience, the example embodiments are described as various functional blocks that are interconnected. However, this is not essential and these functional blocks may be equivalently aggregated into a single logical device, program, or operation that has ambiguous boundaries. Regardless, the functional block can be implemented alone or in combination with other elements of hardware or software.

  While specific embodiments have been described, it is to be understood that other embodiments are possible and are intended to be included herein. It will be apparent to those skilled in the art that changes and modifications can be made to the embodiments described above.

Claims (18)

(A) a camera body having an opening that allows light to enter the camera body;
(B) an image sensor disposed within the camera body and positioned to receive at least a portion of the light entering the camera body;
(C) (i) a journaled partition that uses a journaling file system that is not natively accessible by the operating system ;
(Ii) a partition that is not journaled to use a non-journaling file system supported natively by the operating system,
A removable media circuit configured to write to a removable storage device formatted to include:
(D) a processing circuit communicatively coupled to the image sensor and the removable media circuit and configured to store a file in the journaled partition using the journaling file system;
With
The non-journaled partition stores computer program code, and once the computer program code is executed , the operating system is allowed to access a file stored in the journaled partition. A camera characterized by that. The capacity of the removable storage device excluding the capacity of a partition table from all available capacity is fully allocated to the journaled and non-journaled partitions. camera. The camera according to claim 1 or 2, wherein the processing circuit does not write data to or delete data from the non-journaled partition. 4. The camera according to claim 1, wherein the journaled partition has a larger capacity than the non-journaled partition. The camera according to claim 1, wherein the camera is a security camera. (A) a camera body having an opening that allows light to enter the camera body;
(B) an image sensor disposed within the camera body and positioned to receive at least a portion of the light entering the camera body;
(C) a removable media circuit configured to write to a removable storage device;
(D) a processing circuit communicatively coupled to the image sensor and the removable media circuit and configured to perform a particular method;
A camera equipped with
The method
(I) to include a partition that is journaled to use inaccessible journaling file system natively by the operating system, and a partition that is not journaled to use a non-journaling file system supported natively by the operating system Partitioning the removable storage device;
And storing computer program code to (ii) the journaling that is not partitioned,
Only including,
The camera, wherein the operating system is allowed to access files stored in the journaled partition once the computer program code is executed . 7. The capacity of the usable capacity of the removable storage device excluding the capacity of a partition table is fully allocated to the journaled and non-journaled partitions. camera. The processing circuit is further configured to not write data to or delete data from the non-journaled partition after storing the computer program code in the non-journaled partition. The camera according to claim 6 or 7. The processing circuit is further configured to store one or more of a video file, an audio file, and a still image obtained from the light incident on the image sensor after partitioning the removable storage device. The camera according to claim 6, wherein the camera is provided. 10. A camera according to any one of claims 6 to 9, wherein the journaled partition has a larger capacity than the non-journaled partition. The method further includes prior to partitioning the removable storage device.
(A) determining whether the removable storage device includes only a first initial partition that uses the non-journaling file system and whether the first initial partition is empty; ,
(B) erasing the first initial partition if the removable storage device includes only the first initial partition and the first initial partition is empty;
The camera according to claim 6, comprising: The method further includes prior to partitioning the removable storage device.
(A) determining whether the removable storage device includes only a first initial partition that uses the non-journaling file system and a second initial partition that uses the journaling file system;
(B) If the removable storage device does not include only the first and second initial partitions, the user is prompted to confirm that the partitioning process will be performed, and the user confirmation is performed. Starting the process of partitioning after receiving;
The camera according to claim 6, comprising: The method further includes prior to partitioning the removable storage device.
(A) determining the size of the first initial partition when the removable storage device includes only the first and second initial partitions;
(B) If the size of the first initial partition is not equal to the fixed size of the non-journaled partition, prompt the user to confirm that the partitioning step will be performed; Starting the partitioning step after receiving a user confirmation;
The camera of claim 12 comprising: The method further includes prior to partitioning the removable storage device.
If (a) the magnitude of the first initial partition is equal to the size of the partition which is not the journaling whether the computer program code is present in the first initial partition, and determining the ,
(B) If the computer program code is not present in the first initial partition, prompt the user to confirm that the partitioning process will be performed, and after receiving the user confirmation, the partitioning Starting the step of
The camera according to claim 13, comprising: The method further includes prior to partitioning the removable storage device.
(A) When the computer program code is present in the first initial partition, the capacity obtained by subtracting the capacity of the partition table from all usable capacity of the removable storage device is the first and second initial partitions. Determining whether it is completely assigned to
(B) When the capacity of the removable storage device is not completely allocated to the first and second initial partitions, the user is confirmed to perform the partitioning process. Prompting and starting the partitioning after receiving user confirmation;
The camera of claim 14 comprising: The camera according to claim 6, wherein the camera is a security camera. A method of partitioning a removable storage device for a camera,
(A) determining whether the removable storage device is connected to the camera;
(B) when the removable storage device is connected to the camera;
(I) to include a partition that is journaled to use inaccessible journaling file system natively by the operating system, and a partition that is not journaled to use a non-journaling file system supported natively by the operating system Partition the removable storage device;
(Ii) storing a computer program code to the journaling that is not partitioned,
A method wherein the operating system is allowed to access a file stored in the journaled partition once the computer program code is executed . A non-transitory computer readable medium having encoded therein statements and instructions for causing a camera to partition a removable storage device for the camera by performing a particular method, the method comprising:
(A) determining whether the removable storage device is connected to the camera;
(B) when the removable storage device is connected to the camera;
(I) to include a partition that is journaled to use inaccessible journaling file system natively by the operating system, and a partition that is not journaled to use a non-journaling file system supported natively by the operating system Partition the removable storage device;
(Ii) storing a computer program code to the journaling that is not partitioned,
A non-transitory computer readable medium wherein the operating system is allowed to access a file stored in the journaled partition once the computer program code is executed .

Images