KR20240020138A - Electronic device and method for managinh shooting date and time of image file in the electronic device - Google Patents

Abstract

An electronic device according to an embodiment may include a memory and a processor that include a DB in which a first table in which the unique key value of the image file is matched with the shooting date and time information is stored.
The processor according to an embodiment, based on confirmation of a first image file in which metadata is not stored or a second image file in which metadata does not contain shooting date and time information, the first image file or the It may be set to generate a unique key value for the second image file.
The processor according to an embodiment generates date and time information related to the first image file or the second image file as shooting date and time information, and generates the unique key value and the It can be set to match and save the captured shooting and date information.

Description

Electronic devices and methods for managing the shooting date and time of image files in the electronic devices {ELECTRONIC DEVICE AND METHOD FOR MANAGINH SHOOTING DATE AND TIME OF IMAGE FILE IN THE ELECTRONIC DEVICE}

The present disclosure provides an electronic device for managing the shooting date and time of an image file having a file format in which metadata cannot be stored and/or an image file storing metadata that does not contain shooting date and time information, and in the electronic device It's about how to manage shooting dates and times.

The electronic device may arrange and provide files stored in the electronic device based on time. Depending on the type of file, the electronic device may sort and provide files based on creation date and time information, or may sort and provide files based on shooting date and time information.

For example, in the case of image files that can be sorted based on the shooting date and time information, the electronic device uses a database (DB) that manages the metadata of the image file to provide the user with the shooting date and time information. You can provide image files sorted by .

The electronic device may, in the case of image files having a file format in which metadata cannot be stored and/or image files storing metadata that do not contain capture date and time information, perform any last modifications to the image file, such as copying, editing, and /or travel) time The shooting date and time information of the image file is updated in the database (DB) that manages the metadata of the image file.

Accordingly, whenever the image file is modified, the capture date and time information of the image file changes, so the sorting order when displaying the image file may change.

An electronic device according to an embodiment may include a memory and a processor that include a DB in which a first table in which the unique key value of the image file is matched with the shooting date and time information is stored.

The memory according to one embodiment may, upon execution, the processor performs the operation based on confirmation of a first image file for which no metadata is stored or a second image file for which the metadata does not contain shooting date and time information. , an instruction for generating a unique key value for the first image file or the second image file may be stored.

When the memory according to an embodiment is executed, the processor generates date and time information related to the first image file or the second image file as shooting date and time information, and stores the first table of the DB. An instruction to match and store the unique key value and the generated capture and date information may be stored. A method of managing the capture date and time of an image file in an electronic device according to an embodiment includes storing metadata. An operation of generating a unique key value for the first image file or the second image file based on confirmation that the first image file or the second image file does not contain capture date and time information in the metadata. It can be included.

The method according to an embodiment may include generating date and time information related to the first image file or the second image file as shooting date and time information.

The method according to one embodiment may include an operation of matching and storing the unique key value and the generated shooting and date information in a first table of a DB included in the memory of the electronic device.

According to an embodiment of the present disclosure, the shooting date and time information of an image file having a file format in which metadata cannot be stored and/or an image file storing metadata that does not include shooting date and time information can be maintained.

1 is a block diagram of an electronic device in a network environment according to an embodiment.
Figure 2 is a block diagram of an electronic device according to an embodiment.
FIG. 3 is a diagram illustrating an operation of generating a unique key for an image file in an electronic device according to an embodiment.
FIGS. 4A and 4B are diagrams for explaining an operation in which the capture date and time information of an image file is maintained in an electronic device according to an embodiment.
FIGS. 5A and 5B are flowcharts for explaining an operation of storing shooting date and time information in an electronic device according to an embodiment.
FIG. 6 is a flowchart illustrating an operation of storing shooting date and time information in an electronic device according to an embodiment.
FIGS. 7A and 7B are flowcharts illustrating an operation of detecting shooting date and time information in an electronic device according to an embodiment.

FIG. 1 is a block diagram of an electronic device 101 in a network environment 100, according to one embodiment. Referring to FIG. 1, in the network environment 100, the electronic device 101 communicates with the electronic device 102 through a first network 198 (e.g., a short-range wireless communication network) or a second network 199. It is possible to communicate with at least one of the electronic device 104 or the server 108 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108. According to one embodiment, the electronic device 101 includes a processor 120, a memory 130, an input module 150, an audio output module 155, a display module 160, an audio module 170, and a sensor module ( 176), interface 177, connection terminal 178, haptic module 179, camera module 180, power management module 188, battery 189, communication module 190, subscriber identification module 196 , or may include an antenna module 197. In some embodiments, at least one of these components (eg, the connection terminal 178) may be omitted or one or more other components may be added to the electronic device 101. In some embodiments, some of these components (e.g., sensor module 176, camera module 180, or antenna module 197) are integrated into one component (e.g., display module 160). It can be.

The processor 120, for example, executes software (e.g., program 140) to operate at least one other component (e.g., hardware or software component) of the electronic device 101 connected to the processor 120. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of data processing or computation, the processor 120 stores commands or data received from another component (e.g., sensor module 176 or communication module 190) in volatile memory 132. The commands or data stored in the volatile memory 132 can be processed, and the resulting data can be stored in the non-volatile memory 134. According to one embodiment, the processor 120 includes a main processor 121 (e.g., a central processing unit or an application processor) or an auxiliary processor 123 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 101 includes a main processor 121 and a secondary processor 123, the secondary processor 123 may be set to use lower power than the main processor 121 or be specialized for a designated function. You can. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of it.

The auxiliary processor 123 may, for example, act on behalf of the main processor 121 while the main processor 121 is in an inactive (e.g., sleep) state, or while the main processor 121 is in an active (e.g., application execution) state. ), together with the main processor 121, at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) At least some of the functions or states related to can be controlled. According to one embodiment, co-processor 123 (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module 180 or communication module 190). there is. According to one embodiment, the auxiliary processor 123 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 101 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 108). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software structures.

The memory 130 may store various data used by at least one component (eg, the processor 120 or the sensor module 176) of the electronic device 101. Data may include, for example, input data or output data for software (e.g., program 140) and instructions related thereto. Memory 130 may include volatile memory 132 or non-volatile memory 134.

The program 140 may be stored as software in the memory 130 and may include, for example, an operating system 142, middleware 144, or application 146.

The input module 150 may receive commands or data to be used in a component of the electronic device 101 (e.g., the processor 120) from outside the electronic device 101 (e.g., a user). The input module 150 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, stylus pen).

The sound output module 155 may output sound signals to the outside of the electronic device 101. The sound output module 155 may include, for example, a speaker or a receiver. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 160 can visually provide information to the outside of the electronic device 101 (eg, a user). The display module 160 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the device. According to one embodiment, the display module 160 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by the touch.

The audio module 170 can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module 170 acquires sound through the input module 150, the sound output module 155, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 101). Sound may be output through the electronic device 102 (e.g., speaker or headphone).

The sensor module 176 detects the operating state (e.g., power or temperature) of the electronic device 101 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 176 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 177 may support one or more designated protocols that can be used to connect the electronic device 101 directly or wirelessly with an external electronic device (eg, the electronic device 102). According to one embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 178 may include a connector through which the electronic device 101 can be physically connected to an external electronic device (eg, the electronic device 102). According to one embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 179 can convert electrical signals into mechanical stimulation (e.g., vibration or movement) or electrical stimulation that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 can capture still images and moving images. According to one embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 188 can manage power supplied to the electronic device 101. According to one embodiment, the power management module 188 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101. According to one embodiment, the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

Communication module 190 is configured to provide a direct (e.g., wired) communication channel or wireless communication channel between electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108). It can support establishment and communication through established communication channels. Communication module 190 operates independently of processor 120 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 198 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (e.g., legacy It may communicate with an external electronic device 104 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 192 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199. The electronic device 101 can be confirmed or authenticated.

The wireless communication module 192 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 192 may support high frequency bands (eg, mmWave bands), for example, to achieve high data rates. The wireless communication module 192 uses various technologies to secure performance in high frequency bands, for example, beamforming, massive array multiple-input and multiple-output (MIMO), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 192 may support various requirements specified in the electronic device 101, an external electronic device (e.g., electronic device 104), or a network system (e.g., second network 199). According to one embodiment, the wireless communication module 192 supports Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mmTC, or U-plane latency (e.g., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 197 may transmit or receive signals or power to or from the outside (eg, an external electronic device). According to one embodiment, the antenna module 197 may include an antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 197 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is, for example, connected to the plurality of antennas by the communication module 190. can be selected. Signals or power may be transmitted or received between the communication module 190 and an external electronic device through the at least one selected antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 197.

According to one embodiment, the antenna module 197 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal ( (e.g. commands or data) can be exchanged with each other.

According to one embodiment, commands or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199. Each of the external electronic devices 102 or 104 may be of the same or different type as the electronic device 101. According to one embodiment, all or part of the operations performed in the electronic device 101 may be executed in one or more of the external electronic devices 102, 104, or 108. For example, when the electronic device 101 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 101 may perform the function or service instead of executing the function or service on its own. Alternatively, or additionally, one or more external electronic devices may be requested to perform at least part of the function or service. One or more external electronic devices that have received the request may execute at least part of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device 101. The electronic device 101 may process the result as is or additionally and provide it as at least part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can be used. The electronic device 101 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may include an Internet of Things (IoT) device. Server 108 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 104 or server 108 may be included in the second network 199. The electronic device 101 may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

Figure 2 is a block diagram 200 of an electronic device according to an embodiment.

Referring to FIG. 2, according to one embodiment, the electronic device 201 may include a processor 220, a memory 230, a display 260, a camera 280, and a communication module 290. .

At least some of the components of the electronic device 301 shown in FIG. 2 may be the same or similar to the components of the electronic device 101 shown in FIG. 1, and overlapping descriptions will be omitted below.

According to one embodiment, the processor 220 may be implemented substantially the same as or similar to the processor 120 of FIG. 1.

According to one embodiment, when the memory 230 is executed, when the processor 220 confirms the creation of an image file, if the image file is identified as a first image file in which metadata is not stored, Instructions for generating a unique key value and shooting date and time information of the first image file, and matching and storing the generated unique key value and the generated date and time information may be stored.

According to one embodiment, when the processor 220 confirms the creation of the image file, the instructions check whether metadata is stored in the image file by scanning and/parsing the image file, and If metadata is not stored in the image file, the image file can be confirmed as a first image file in which metadata is not stored.

According to one embodiment, the first image file in which metadata is not stored represents an image file having a file format in which metadata is not stored, for example, a gif (graphics interchange format) file and/or a png (portable network) file. graphics) file.

According to one embodiment, the instructions may cause the processor 220 to generate a unique key value by applying a byte code corresponding to the contents of the first image file to a hash algorithm.

According to one embodiment, the instructions are executed when the processor 220 checks the creation date and time information of the first image file and the modification date and time information of the first image, and executes the first image file according to priority information. One of the creation date and time information of the image file or the modification date and time information of the first image may be generated as the shooting date and time information of the first image.

According to one embodiment, when the processor 220 checks the creation date and time information of the first image file, the instructions set the creation date and time information of the first image file to the capture date of the first image. and time information.

According to one embodiment, when the processor 220 checks the modification date and time information of the first image file, the instructions set the modification date and time information of the first image file to the capture date of the first image. and time information.

According to one embodiment, the instructions are the creation date and time information or modification date of the first image file stored in the second table 231b included in the DB 231 of the memory 230 by the processor 220. And time information is detected and generated as shooting date and time information of the first image file, and the first table 231a included in the DB 231 of the memory 230 is generated for the first image file. You can save the unique key value by matching the shooting date and time information.

According to one embodiment, the instructions are such that the processor 220 provides creation date and time information or modification date and time information of the first image file stored in the second DB (not shown) included in the memory 230. Detected and generated as the shooting date and time information of the first image file, and matched with the unique key value generated for the first image file in the first DB (not shown) of the memory 230 and the shooting date and time information You can save it by doing so.

According to one embodiment, the instructions may cause the processor 220 to synchronize with the cloud and back up the unique key value and/or shooting date and time information generated for the first image file to the cloud. As the unique key value and/or shooting date and time information generated for the first image file is backed up to the cloud, the DB is updated according to a policy such as a specific cycle, and the unique key value generated for the first image file in the electronic device is updated. Even if the key value and/or shooting date and time information are deleted, the unique key value and/or shooting date and time information generated for the first image file backed up in the cloud can be used.

According to one embodiment, the instructions are because the processor 220 generates a unique key value by applying the byte code itself corresponding to the contents of the image file to a hash algorithm, so that the first image file is Even if it is edited, copied or moved to an external electronic device or within the electronic device, the shooting date and time information generated for the first image file can be maintained without change because the unique key value is unique.

According to one embodiment, the memory 230, upon execution, when the processor 220 confirms the creation of an image file, the image file is stored in a format that does not include the capture date and time information in the metadata. 2 When confirmed as an image file, instructions are stored to generate a unique key value and shooting date and time information of the second image file, and to match and store the generated unique key value and the generated date and time information. You can.

According to one embodiment, when the processor 220 confirms the creation of the image file, the instructions check whether metadata is stored in the image file by scanning and/parsing the image file, and If metadata is stored in the image file, check whether the metadata includes the capture date and time information, and if the metadata does not contain the capture date and time information, capture the image file in the metadata You can check with a second image file that does not contain date and time information.

According to one embodiment, the second image file represents an image file that has a file format in which metadata is stored, but does not include shooting date and time information in the metadata, for example, the image file is captured in the metadata. Can include jpeg (joint photographic experts group) files that do not contain date and time information.

According to one embodiment, the instructions may cause the processor 220 to generate a unique key value by applying a byte code corresponding to the contents of the second image file to a hash algorithm.

According to one embodiment, the instructions are executed when the processor 220 checks the creation date and time information of the second image file and the modification date and time information of the second image, based on priority information. 2 One of the creation date and time information of the image file or the modification date and time information of the second image may be generated as the shooting date and time information of the second image.

According to one embodiment, when the processor 220 checks the creation date and time information of the second image file, the instructions set the creation date and time information of the second image file to the capture date of the second image. and time information.

According to one embodiment, when the processor 220 checks the modification date and time information of the second image file, the instructions set the modification date and time information of the second image file to the capture date of the second image. and time information.

According to one embodiment, the instructions are provided by the processor 220 to the creation date and time information or modification date of the second image file stored in the second table 231b included in the DB 231 of the memory 230. And time information is detected and generated as shooting date and time information of the second image file, and the first table 231a included in the DB 231 of the memory 230 is generated for the second image file. You can save the unique key value by matching the shooting date and time information.

According to one embodiment, the instructions are such that the processor 220 provides creation date and time information or modification date and time information of the second image file stored in the second DB (not shown) included in the memory 230. Detected and generated as the shooting date and time information of the second image file, and matched with the unique key value generated for the second image file in the first DB (not shown) of the memory 230 and the shooting date and time information You can save it by doing so.

According to one embodiment, the instructions may cause the processor 220 to synchronize with the cloud and back up the unique key value and/or shooting date and time information generated for the second image file to the cloud. As the unique key value and/or shooting date and time information generated for the second image file are backed up to the cloud, the DB is updated according to a policy such as a specific cycle, and the unique key value generated for the second image file in the electronic device is updated. Even if the key value and/or shooting date and time information are deleted, the unique key value or shooting date and time information generated for the first image file backed up in the cloud can be used.

According to one embodiment, the instructions are because the processor 220 generates a unique key value by applying the byte code itself corresponding to the contents of the image file to a hash algorithm, so that the second image file Even if it is edited, copied or moved to an external electronic device or within the electronic device, the shooting date and time information generated for the second image file can be maintained without change because the unique key value is unique.

According to one embodiment, when the processor 220 confirms the creation of an image file during execution, the memory 230 converts the image file into a third image file that includes the shooting date and time information in metadata. If confirmed, instructions for detecting and storing the shooting date and time information included as metadata of the third image file can be stored.

According to one embodiment, when the processor 220 confirms the creation of the image file, the instructions check whether metadata is stored in the image file by scanning and/parsing the image file, and If metadata is stored in the image file, check whether the metadata includes the capture date and time information, and if the metadata contains the capture date and time information, then check whether the image file contains the capture date and time information in the metadata. and a third image file containing time information.

According to one embodiment, the third image file represents an image file that has a file format in which metadata is stored and includes capture date and time information in the metadata, for example, the capture date and time information in the metadata. Can include a jpeg (joint photographic experts group) file containing time information.

According to one embodiment, the instructions are stored by the processor 220 in the second table 231b among the first table 231a and the second table 231b included in the DB 231 of the memory 230. The shooting date and time information detected as metadata in the third image file can be stored.

According to one embodiment, the instructions are executed by the processor 220 in the third image file in the second DB among the first DB (not shown) and the second DB (not shown) included in the memory 230. You can save the detected shooting date and time information as metadata.

According to one embodiment, when the memory 230 is executed, when the processor 220 checks the first state of the electronic device, the memory 230 selects a first image file among image files stored in the file system of the memory and/ or detecting a second image file, generating a unique key value and shooting date and time information for the first image file and/or the second image file, and Instructions for matching and storing the generated unique key value and the generated shooting date and time information can be stored in the table 231a.

According to one embodiment, the first state of the electronic device may include at least one of a charging state or a state in which the display screen of the electronic device is off. As the unique key value and shooting date and time information for the first image and/or the second image are generated and stored in the first state of the electronic device, the processing time of an image file or video file with a large file size is increased. can reduce the burden.

According to one embodiment, the instructions allow the processor 220 to distinguish between when the electronic device is in the first state or when the creation of a file is confirmed, depending on the capacity of the file, and output the first image and/or the second image. A unique key value and shooting date and time information can be generated and stored. For example, the instructions are executed when the processor 220 confirms the creation of a file if the file size is less than a threshold value. Generate and store a unique key value and shooting date and time information for the first image and/or the second image, and if the capacity of the file is greater than or equal to the threshold value, the first image and/or the second image are stored in the first state of the electronic device. Alternatively, unique key value and shooting date and time information for the second image may be generated and stored.

According to one embodiment, the instructions are information provided by the processor 220 to a first provider (e.g., media provider) that manages the DB in which metadata is stored and to a specific application among applications included in the electronic device. Controls a second provider (e.g., a specific media provider provided by a product company) that manages the stored DB, and synchronizes the DB managed by the first provider with the DB managed by the second provider. The same information can be stored.

According to one embodiment, the first provider (e.g., media provider) scans and/or parses image files stored in the file system of the memory 230 and stores the shooting date and time information of the image file. A DB in memory can be managed, and information on the capture date and time of the image file stored in the DB can be provided upon request from at least one application included in the electronic device.

According to one embodiment, the second provider (e.g., a specific media provider provided by a product company) provides specific information requested by a specific application among applications included in the electronic device, and the first provider The unique key value and shooting date and time information stored in the first table 231a of the DB 231 of the memory 230 managed by the second provider can be managed in a separate DB. As the unique key value and the shooting date and time information stored in the first table 231a of the DB 231 of the memory 230 are stored in a separate DB managed by the second provider, the specific application is stored in the first table 231a. Without multiple operations of requesting shooting date and time information from the provider and requesting specific information from the second provider, shooting date and time information and specific information can be requested from the second provider. In addition, even if the unique key value and the shooting date and time information stored in the first table 231a of the DB 231 of the memory 230 are deleted, the synchronized second provider manages the unique key value stored in a separate DB. and shooting date and time information are available.

According to one embodiment, when the memory 230 is executed, if the processor 220 confirms a request to display an image file, the shooting date for at least one image file stored in the file system of the memory 230 is displayed. And based on time information, instructions for sorting the at least one image file and displaying it on the display 260 may be stored.

According to one embodiment, the instructions are executed when the processor 220 identifies a first image file among at least one image file stored in the file system of the memory 230 in response to a request for displaying the image file. 1 The byte code corresponding to the contents of the image file can be applied to the hash algorithm to generate a unique key value. The instructions are executed when the processor 220 confirms that the unique key value generated for the first image file is stored in the first table 231a of the DB of the memory 230, the first table ( In 231a), the stored shooting date and time information can be detected by matching the unique key value generated for the first image file. The instructions are executed when the processor 220 confirms that the unique key value generated for the first image file is stored in the first DB (not shown) of the memory 230. The stored shooting date and time information can be detected by matching the unique key value generated for the first image file.

According to one embodiment, the instructions are executed when the processor 220 identifies a second image file among at least one image file stored in the file system of the memory 230 in response to a request for displaying the image file. 2 The byte code corresponding to the contents of the image file can be applied to the hash algorithm to generate a unique key value. The instructions are executed when the processor 220 confirms that the unique key value generated for the second image file is stored in the first table 231a of the DB of the memory 230, the first table ( In 231a), the stored shooting date and time information can be detected by matching the unique key value generated for the second image file. The instructions are executed when the processor 220 confirms that the unique key value generated for the second image file is stored in the first DB (not shown) of the memory 230. The stored shooting date and time information can be detected by matching the unique key value generated for the second image file.

According to one embodiment, the instructions are executed when the processor 220 identifies a third image file among at least one image file stored in the file system of the memory 230 in response to a request for displaying the image file. The shooting date and time information of the third image file can be detected from the second table 231b of the DB 231 at 230. When the processor 220 confirms the third image file among the at least one image file, the instructions are stored in the second DB (not shown) of the memory 230, including the capture date and time of the third image file. Information can be detected.

According to one embodiment, the instructions are used by the processor 220 to generate byte codes corresponding to the contents of the first image file and/or the second file using various hash algorithms as shown in <Table 1> below. You can hash it to generate a unique key value.

file size: 246,271,827 bytes
goodFastHash: 1602ms => 5b02dccbbb1c8ec1de4eae2571924f027bca958a2c0e9378a405ffefdaeb0136
sha256: 268ms => 4688a198ecdd65746aaf22ea89194e9cdd53444be383ea4d143d06208ba38276
md5: 633ms => cc7540d8708db660e8b7763ddb9323da
murmur3_128: 866ms => 23346183c4ef952dad7e134a5fad106f
murmur3_32: 632ms => 497e4779

The instructions allow the processor 220 to generate a unique key value (e.g., 4688a198ecdd65746aaf22ea89194e9cdd53444be383ea4d1) in about 268ms when an image file with a file size of 220MB is applied to the hash algorithm sha256, as shown in <Table 1>.

43d06208ba 38276) can be created. Therefore, in the case of an image file with a file size of generally 10MB, a unique key can be generated without difficulty in the electronic device environment. In addition, in the case of video files having various capacities, the processor 220 is unique in the first state of the electronic device (e.g., in a charging state or in a state where the display screen of the electronic device is off) rather than at the time of file creation. You can generate a key.

According to one embodiment, the memory 230 may be implemented substantially the same as or similar to the memory 130 of FIG. 1 .

According to one embodiment, the memory 230 includes a DB 231, and the first table 231a and the second table 231b may be stored in the DB 231. The first table 231a may store a unique key value for the first image and/or the second image and information on the date and time of shooting that is stored by matching the unique key value. Information on the capture date and time of the third image may be stored in the second table 231b.

According to one embodiment, the memory 230 may include a first DB (not shown) and a second DB (not shown). The first DB (not shown) may store a unique key value for the first image and/or the second image and information on the date and time of shooting that is stored by matching the unique key value. Information on the capture date and time of the third image may be stored in the second DB (not shown).

According to one embodiment, the display 260 may be implemented substantially the same as or similar to the display module 160 of FIG. 1.

According to one embodiment, at least one image file stored in the file system of the memory 230 may be displayed on the display 260 based on the capture date and time information in response to a request to display the image file.

According to one embodiment, the camera 280 may be implemented substantially the same as or similar to the camera module 180 of FIG. 1.

According to one embodiment, the communication module 290 may be implemented substantially the same as or similar to the communication module 190 of FIG. 1 and may include a plurality of communication circuits using different communication technologies.

According to one embodiment, the communication module 290 may include at least one of a wireless LAN module (not shown) and a short-range communication module (not shown), and the short-range communication module (not shown) may be used to band) communication module, Wi-Fi communication module, NFC communication module, Bluetooth legacy communication module, and/or BLE communication module.

FIG. 3 is a diagram 300 for explaining an operation of generating a unique key for an image file in an electronic device according to an embodiment.

Referring to FIG. 3, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) displays a second image that does not include shooting date and time information in the metadata. The byte code 313 corresponding to the contents of the file 310 can be applied to the hash function 315 to generate a unique key value 317 (1k2s9Fk19zMdos...) of the second image file 310. In the electronic device, the generated unique key value is stored in the DB (e.g., DB 231 in FIG. 2) of the memory (e.g., memory 230 in FIG. 2) of the electronic device as shown in Table 2 below. It can be stored in one table (e.g., the first table 231a in FIG. 2).

Unique Key Date-taken GPS Coordinate ... 1k2s9Fk19zMdos… 2022-04-01 16:01 +09:00 123.456 / 789.012 ... d192flkfj10939fj… 2022-04-01 16:02 +09:00 214.590 / 21.907 ... zZod8f020112… 2020-12-06 00:01 +09:00 782.354 / 907.413 ... Udkro02dfkKdf9.. 2021-01-30 09:02 +09:00 213.978 / 657.290 ... kluJHkgLGl9090J… 2022-05-04 16:01 +09:00 68.478 / 856.54 ... ... ... ... ...

As shown in <Table 2>, the electronic device stores the shooting date and time information by matching a unique key as in the first table, and stores the shooting location information in addition to the shooting date and time information. Information related to the shooting of the first image file or the second image file, such as knowable GPS coordinate information, may be additionally stored.

FIGS. 4A and 4B are diagrams 400a and 400b for explaining an operation of maintaining the capture date and time information of an image file in an electronic device according to an embodiment.

Referring to FIG. 4A, in a general electronic device, when the first image file 410 without metadata is captured (created) at 10:43 am on May 10, 2022, the first image file ( The first image file 410 may be sorted and displayed based on the creation date and time information (e.g., 10:43 am on May 10, 2022) (411). When the first image file 410 is copied, the electronic device records the date and time information at which the first image file 410 was copied (e.g., 10:49 a.m. on May 10, 2022) (413). ) The first image file 410 can be sorted and displayed based on.

Referring to FIG. 4B, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) according to the present disclosure includes a first image file 430 in which metadata is not stored. ) was captured (generated) at 10:43 am on May 10, 2022, byte code 431 corresponding to the contents of the first image file is applied to the hash algorithm using a hash algorithm. A unique key value 433 is generated, and the creation date and time information of the first image file 430 (e.g., 10:43 a.m. on May 10, 2022) is combined with the shooting date and time of the first image file. Time information 435 is generated, and the generated unique key value 433 and the shooting date and time information 435 are matched to create a first table (e.g., the first table in FIG. 2) of the DB of the electronic device. When stored in 231a)), the first image file 430 can be sorted and displayed based on the shooting date and time information 435 of the first image file 430. When the first image file 430 is copied, the electronic device hashes the byte code 431 corresponding to the contents of the first image file 430 using a hash algorithm to create a unique key. A value 433 is generated, and the shooting date and time information 435 is stored by matching the unique key value 433 in the first table of the DB of the electronic device (e.g., the first table 231a in FIG. 3). , the first image file 430 can be sorted and displayed based on the same shooting date and time information 435 as before copying the first image file 430.

An electronic device (electronic device 101 in FIG. 1; electronic device 201 in FIG. 2) according to an embodiment includes a first table (FIG. 2) in which unique key values of image files are matched and stored with shooting date and time information. A memory (memory 130 in FIG. 1; memory 230 in FIG. 2) and a processor (processor 120 in FIG. 1) including a DB (DB 231 in FIG. 2) in which the second table 231a) is stored. ); may include the processor 220 of FIG. 2).

The memory according to one embodiment may, upon execution, the processor performs the operation based on confirmation of a first image file for which no metadata is stored or a second image file for which the metadata does not contain shooting date and time information. , an instruction for generating a unique key value for the first image file or the second image file may be stored.

When the memory according to an embodiment is executed, the processor generates date and time information related to the first image file or the second image file as shooting date and time information, and stores the first table of the DB. It can be set to match and store the unique key value and the generated shooting and date information.

The memory may store an instruction that, upon execution, allows the processor to check whether the created image file is the first image file or the second image file when the processor confirms the creation of the image file. , When executing, if the processor checks the first state of the electronic device, it may store an instruction to check whether it is the first image file or the second image file. According to one embodiment, the electronic device The first state may include at least one of a state in which the electronic device is charged or a state in which the display screen of the electronic device is turned off.

The memory according to one embodiment may store an instruction that, when executed, causes the processor to generate the unique key value using a byte code corresponding to the contents of the first image file or the second image file. .The processor according to one embodiment may store an instruction for generating the unique key value by applying a byte code corresponding to the contents of the first image file or the second image file to a hash algorithm. One embodiment The memory according to the, when executed, the processor, the date and time information related to the first image file or the second image file, the creation date and time information of the first image file or the second image file When the modification date and time information is confirmed, the creation date and time information of the first image file or the second image file, or the modification date and time information is changed to the first image file or the second image file based on priority information. An instruction for creating an image file with shooting date and time information may be stored. The DB according to one embodiment may include a second table in which shooting date and time information is stored.

The memory according to one embodiment is, when running, if the processor identifies a third image file in which metadata including the capture date and time information is stored in the image file, the capture date and time information of the third image file is stored. may store an instruction to store in the second table. The memory according to one embodiment is, when executed, the processor, based on a display request of a first image file or a second image file, 1 Generate a unique key value for an image file or the second image file, and if the unique key value exists in the first table of the DB, the unique key value matches the value to detect the stored shooting date and time information The memory according to one embodiment may store an instruction. When executed, the processor may, based on a request to display a third image file, determine the shooting date and Instructions for detecting time information can be stored.

FIGS. 5A and 5B are flowcharts 500a and 500b for explaining an operation of storing shooting date and time information in an electronic device according to an embodiment. Operations for storing the shooting date and time may include operations 501 to 525. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, at least two operations may be performed in parallel, or another operation may be added.

In operation 501, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may confirm the creation of an image file.

In operation 503, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may check whether metadata is stored in the image file.

According to one embodiment, the electronic device may check whether metadata is stored in the image file based on a scanning and/or parsing operation of the image file.

In operation 503, if the electronic device determines that metadata is not stored in the image file, in operation 505, the electronic device may confirm the image file as a first image file in which metadata is not stored.

According to one embodiment, the first image file in which metadata is not stored represents an image file having a file format in which metadata is not stored, for example, a gif (graphics interchange format) file and/or a png (portable network) file. graphics) file.

In operation 507, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate a unique key value of the first image file.

According to one embodiment, the electronic device may generate a unique key value by applying a byte code corresponding to the contents of the first image file to a hash algorithm.

In operation 509, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate capture date and time information of the first image file.

According to one embodiment, when the electronic device checks the creation date and time information of the first image file and the modification date and time information of the first image file, the electronic device generates the first image file according to priority information. One of date and time information or modification date and time information of the first image file may be generated as the shooting date and time information of the first image.

According to one embodiment, when the electronic device checks the creation date and time information of the first image file, the creation date and time information of the first image file is converted into the shooting date and time information of the first image file. can be created.

According to one embodiment, when the electronic device checks the modification date and time information of the first image file, it generates the modification date and time information of the first image file as the shooting date and time information of the first image. can do.

In operation 511, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) matches the unique key value generated for the first image file with the shooting date and time information. You can save it.

According to one embodiment, the electronic device stores a first table (e.g., the first table in FIG. 2) included in a DB (e.g., DB 231 in FIG. 2) of a memory (e.g., memory 230 in FIG. 2). The unique key value generated for the first image file and the shooting date and time information can be matched and stored in the first table among the table 231a) and the second table (e.g., the second table 231b in FIG. 2). there is.

According to one embodiment, the electronic device stores a unique key value generated for the first image file in the first DB among the first DB and the second DB included in the memory (e.g., memory 230 of FIG. 2). You can match and save the shooting date and time information.

According to one embodiment, the electronic device may synchronize and back up the unique key value and/or shooting date and time information generated for the first image file to the cloud.

In operation 503, if the electronic device confirms that metadata is stored in the image file, in operation 513, the electronic device may check whether the metadata of the image file includes shooting date and time information.

In operation 513, if the electronic device determines that the metadata of the image file does not include the capture date and time information, in operation 515, the electronic device includes the capture date and time information in the metadata of the image file. You can check it with the second image file that does not exist.

According to one embodiment, the second image file represents an image file that has a file format in which metadata is stored, but does not include shooting date and time information in the metadata, for example, the image file is captured in the metadata. Can include jpeg (joint photographic experts group) files that do not contain date and time information.

In operation 517, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate a unique key value of the second image file.

According to one embodiment, the electronic device may generate a unique key value by applying a byte code corresponding to the contents of the second image file to a hash algorithm.

In operation 519, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate capture date and time information of the second image file.

According to one embodiment, when the electronic device checks the creation date and time information of the second image file and the modification date and time information of the second image file, the electronic device generates the second image file according to priority information. One of date and time information or modification date and time information of the second image file may be generated as the shooting date and time information of the second image.

According to one embodiment, when the electronic device checks the creation date and time information of the second image file, it generates the creation date and time information of the second image file as the capture date and time information of the second image. can do.

According to one embodiment, when the electronic device checks the modification date and time information of the second image file, the modification date and time information of the second image file is converted into the shooting date and time information of the second image file. can be created.

In operation 521, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) matches the unique key value generated for the second image file with the shooting date and time information. You can save it.

According to one embodiment, the electronic device stores a first table (e.g., the first table in FIG. 2) included in a DB (e.g., DB 231 in FIG. 2) of a memory (e.g., memory 230 in FIG. 2). The unique key value generated for the second image file and the shooting date and time information can be matched and stored in the first table among the table 231a) and the second table (e.g., the second table 231b in FIG. 2). there is.

According to one embodiment, the electronic device stores a unique key value generated for the second image file in the first DB among the first DB and the second DB included in the memory (e.g., memory 230 of FIG. 2). You can match and save the shooting date and time information.

According to one embodiment, the electronic device may synchronize and back up the unique key value and/or shooting date and time information generated for the second image file to the cloud.

In operation 513, if the electronic device determines that the metadata of the image file includes the capture date and time information, in operation 523, the electronic device stores the image file as a second file including the capture date and time information in the metadata. 3 You can check by checking with the image file.

According to one embodiment, the third image file represents an image file that has a file format in which metadata is stored and includes capture date and time information in the metadata, for example, the capture date and time information in the metadata. Can include a jpeg (joint photographic experts group) file containing time information.

In operation 525, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may store shooting date and time information, which is metadata of the third image file.

According to one embodiment, the electronic device includes a first table (e.g., the first table in FIG. 2) included in a DB (e.g., DB 231 in FIG. 21) of a memory (e.g., memory 230 in FIG. 2). Among the table 231a) and the second table (e.g., the second table 231b in FIG. 2), the shooting date and time information detected as metadata from the third image file may be stored in the second table.

According to one embodiment, the processor 220 transfers metadata from the third image file to the second DB among the first DB and second DB included in the memory (e.g., memory 230 in FIG. 2). Detected shooting date and time information can be saved.

FIG. 6 is a flowchart 600 illustrating an operation of storing shooting date and time information in an electronic device according to an embodiment. Operations for storing the shooting date and time may include operations 601 to 623. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, at least two operations may be performed in parallel, or another operation may be added.

In operation 601, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may check the first state of the electronic device.

According to one embodiment, the first state of the electronic device may include at least one of a charging state or a state in which the display screen of the electronic device is off. As the unique key value and shooting date and time information for the first image and/or the second image are generated and stored in the first state of the electronic device, an image file (e.g., a video file) with a large file size is created and stored. The burden on processing time can be reduced.

In operation 603, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may check image files stored in the memory (e.g., the memory 230 of FIG. 2). there is.

In operation 605, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may check whether metadata is stored in the image file.

In operation 605, if the electronic device determines that metadata is not stored in the image file, in operation 607, the electronic device may confirm the image file as a first image file in which metadata is not stored.

According to one embodiment, the electronic device may check whether metadata is stored in image files based on a scanning and/or parsing operation of the image file.

According to one embodiment, the first image file in which metadata is not stored represents an image file having a file format in which metadata is not stored, for example, a gif (graphics interchange format) file and/or a png (portable network) file. graphics) file.

In operation 609, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate a unique key value of the first image file.

According to one embodiment, the electronic device may generate a unique key value by applying a byte code corresponding to the contents of the first image file to a hash algorithm.

In operation 611, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate capture date and time information of the first image file.

According to one embodiment, when the electronic device checks the creation date and time information of the first image file and the modification date and time information of the first image file, the electronic device generates the first image file according to priority information. One of date and time information or modification date and time information of the first image file may be generated as the shooting date and time information of the first image.

According to one embodiment, when the electronic device checks the creation date and time information of the first image file, the creation date and time information of the first image file is converted into the shooting date and time information of the first image file. can be created.

According to one embodiment, when the electronic device checks the modification date and time information of the first image file, it generates the modification date and time information of the first image file as the shooting date and time information of the first image. can do.

In operation 613, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) matches the unique key value generated for the first image file with the shooting date and time information. You can save it.

According to one embodiment, the electronic device stores a first table (e.g., the first table in FIG. 2) included in a DB (e.g., DB 231 in FIG. 2) of a memory (e.g., memory 230 in FIG. 2). The unique key value generated for the first image file and the shooting date and time information can be matched and stored in the first table among the table 231a) and the second table (e.g., the second table 231b in FIG. 2). there is.

According to one embodiment, the electronic device stores a unique key value generated for the first image file in the first DB among the first DB and the second DB included in the memory (e.g., memory 230 of FIG. 2). You can match and save the shooting date and time information.

According to one embodiment, the electronic device may synchronize and back up the unique key value and/or shooting date and time information generated for the first image file to the cloud.

In operation 605, if the electronic device confirms that metadata is stored in the image file, in operation 615, the electronic device may check whether the metadata of the image file includes shooting date and time information.

In operation 615, if the electronic device determines that the metadata of the image file does not include the capture date and time information, in operation 617, the electronic device includes the capture date and time information in the metadata of the image file. You can check it with the second image file that does not exist.

According to one embodiment, the second image file represents an image file that has a file format in which metadata is stored, but does not include shooting date and time information in the metadata, for example, the image file is captured in the metadata. Can include jpeg (joint photographic experts group) files that do not contain date and time information.

In operation 619, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate a unique key value of the second image file.

According to one embodiment, the electronic device may generate a unique key value by applying a byte code corresponding to the contents of the second image file to a hash algorithm.

In operation 621, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate capture date and time information of the second image file.

According to one embodiment, when the electronic device checks the creation date and time information of the second image file and the modification date and time information of the second image file, the electronic device generates the second image file according to priority information. One of date and time information or modification date and time information of the second image file may be generated as the shooting date and time information of the second image.

According to one embodiment, when the electronic device checks the creation date and time information of the second image file, the creation date and time information of the second image file is converted into the shooting date and time information of the second image file. can be created.

According to one embodiment, when the electronic device checks the modification date and time information of the second image file, it generates the modification date and time information of the second image file as the capture date and time information of the second image. can do.

In operation 623, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) matches the unique key value generated for the second image file with the shooting date and time information. You can save it.

According to one embodiment, the electronic device stores a first table (e.g., the first table in FIG. 2) included in a DB (e.g., DB 231 in FIG. 2) of a memory (e.g., memory 230 in FIG. 2). The unique key value generated for the second image file and the shooting date and time information can be matched and stored in the first table among the table 231a) and the second table (e.g., the second table 231b in FIG. 2). there is.

According to one embodiment, the electronic device stores a unique key value generated for the second image file in the first DB among the first DB and the second DB included in the memory (e.g., memory 230 of FIG. 2). You can match and save the shooting date and time information.

According to one embodiment, the electronic device may synchronize and back up the unique key value and/or shooting date and time information generated for the second image file to the cloud.

FIGS. 7A and 7B are flowcharts 700a and 700b for explaining an operation of detecting shooting date and time information in an electronic device according to an embodiment. Operations for detecting the shooting date and time may include operations 701 to 721. In the following embodiments, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, at least two operations may be performed in parallel, or another operation may be added.

In operation 701, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may confirm a request to display an image file.

In operation 703, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may check whether metadata is stored in the image file.

According to one embodiment, the electronic device may check whether metadata is stored in the image file based on a scanning and/or parsing operation of the image file.

In operation 703, if the electronic device determines that metadata is not stored in the image file, in operation 705, the electronic device may confirm the image file as a first image file in which metadata is not stored.

According to one embodiment, the first image file in which metadata is not stored represents an image file having a file format in which metadata is not stored, for example, a gif (graphics interchange format) file and/or a png (portable network) file. graphics) file.

In operation 707, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate a unique key value of the first image file.

According to one embodiment, the electronic device may generate a unique key value by applying a byte code corresponding to the contents of the first image file to a hash algorithm.

In operation 709, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) selects the capture date of the first image file matched by the unique key value in the first table of the DB. and time information can be detected.

According to one embodiment, the electronic device stores the unique key value generated for the first image file in the DB (e.g., DB 231 in FIG. 2) of the memory (e.g., memory 230 in FIG. 2). If it is confirmed that it is stored in a first table (e.g., the first table 231a in FIG. 2), the shooting date and time information stored by matching the unique key value generated for the first image file in the first table can be detected.

According to one embodiment, the electronic device stores the unique key value generated for the first image file in a first DB among the first DB and the second DB of the memory (e.g., memory 230 in FIG. 2). If it is confirmed that it is, the shooting date and time information stored by matching the unique key value generated for the first image file in the first DB can be detected.

According to one embodiment, the electronic device may align the first image based on the detected capture date and time information and display it on a display (eg, display 260 of FIG. 2).

In operation 703, if the electronic device confirms that metadata is stored in the image file, in operation 711, the electronic device may check whether the metadata of the image file includes shooting date and time information.

In operation 711, if the electronic device determines that the metadata of the image file does not include the capture date and time information, in operation 713, the electronic device includes the capture date and time information in the metadata of the image file. You can check it with the second image file that does not exist.

According to one embodiment, the second image file represents an image file that has a file format in which metadata is stored, but does not include shooting date and time information in the metadata, for example, the image file is captured in the metadata. Can include jpeg (joint photographic experts group) files that do not contain date and time information.

In operation 715, the electronic device (eg, the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may generate a unique key value of the second image file.

According to one embodiment, the electronic device may generate a unique key value by applying a byte code corresponding to the contents of the second image file to a hash algorithm.

In operation 717, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) selects the capture date of the second image file matched by the unique key value in the first table of the DB. and time information can be detected.

According to one embodiment, the electronic device stores the unique key value generated for the second image file in the DB (e.g., DB 231 in FIG. 2) of the memory (e.g., memory 230 in FIG. 2). If it is confirmed that it is stored in a first table (e.g., the first table 231a in FIG. 2), the shooting date and time information stored by matching the unique key value generated for the second image file in the first table can be detected.

According to one embodiment, the electronic device stores the unique key value generated for the second image file in a first DB among the first DB and the second DB of the memory (e.g., memory 230 in FIG. 2). If it is confirmed that it is, the shooting date and time information stored by matching the unique key value generated for the second image file in the first DB can be detected.

According to one embodiment, the electronic device may align the second image based on the detected capture date and time information and display it on a display (eg, display 260 of FIG. 2).

In operation 711, if the electronic device determines that the metadata of the image file includes the capture date and time information, in operation 719, the electronic device stores the image file as a first file whose metadata includes the capture date and time information. 3 You can check it with an image file.

According to one embodiment, the third image file represents an image file that has a file format in which metadata is stored and includes capture date and time information in the metadata, for example, the capture date and time information in the metadata. Can include a jpeg (joint photographic experts group) file containing time information.

In operation 721, the electronic device (e.g., the electronic device 101 of FIG. 1 and/or the electronic device 201 of FIG. 2) may detect shooting date and time information from the second table of the DB.

According to one embodiment, the electronic device stores a second table (e.g., the second table (e.g., the second table (e.g., the second table (e.g., In 231b)), the shooting date and time information of the third image file can be detected.

According to one embodiment, when the electronic device checks the third image file among the at least one image file, the second DB among the first and second DBs in the memory (e.g., memory 230 in FIG. 2) The shooting date and time information of the third image file can be detected from the DB.

A method of managing the capture date and time of an image file in an electronic device according to an embodiment includes: a first image file in which metadata is not stored or a second image file in which metadata does not contain capture date and time information Based on confirmation, the method may include generating a unique key value for the first image file or the second image file.

The method according to an embodiment may include generating date and time information related to the first image file or the second image file as shooting date and time information.

The method according to one embodiment may include an operation of matching and storing the unique key value and the generated shooting and date information in a first table of a DB included in the memory of the electronic device.

The method according to one embodiment may include, upon confirming the creation of an image file, checking whether the created image file is the first image file or the second image file.

The method according to one embodiment may include checking whether the first image file is the first image file or the second image file when the first state of the electronic device is checked.

In the method according to one embodiment, the first state of the electronic device may include at least one of a charging state or a state in which the display screen of the electronic device is off.

The method according to one embodiment may include generating the unique key value using a byte code corresponding to contents of the first image file or the second image file.

The method according to an embodiment may include generating the unique key value by applying a byte code corresponding to the contents of the first image file or the second image file to a hash algorithm.

The method according to one embodiment includes date and time information related to the first image file or the second image file, creation date and time information and modification date and time of the first image file or the second image file. Upon confirming the information, based on the priority information, the creation date and time information of the first image file or the second image file, or the modification date and time information of the first image file or the second image file is captured. It can include actions that generate date and time information.

The method according to one embodiment includes, when confirming a third image file in which metadata including capture date and time information is stored in an image file, the capture date and time information of the third image file is stored in the image file. It may include an operation of saving in the second table of the DB.

The method according to an embodiment may include generating a unique key value for the first image file or the second image file based on a request to display the first image file or the second image file. .

The method according to one embodiment may include, if the unique key value exists in the first table of the DB, detecting the shooting date and time information stored by matching the unique key value with the value.

The method according to one embodiment may include detecting capture date and time information of the third image file from a second table of the DB based on a request to display the third image file.

An electronic device according to an embodiment disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

An embodiment of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or substitutes for the embodiment. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to that component in other respects (e.g., importance or order) is not limited. One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.” When mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

The term “module” used in one embodiment of this document may include a unit implemented in hardware, software, or firmware, and may be interchangeable with terms such as logic, logic block, component, or circuit, for example. can be used A module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

An embodiment of the present document is a storage medium (e.g., built-in memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101 or electronic device 301). It may be implemented as software (e.g., program 140) including one or more instructions stored in . For example, a processor (e.g., processor 520) of a device (e.g., electronic device 301) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, a method according to an embodiment disclosed in this document may be provided and included in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or via an application store (e.g. Play Store ^TM ) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to one embodiment, each component (e.g., module or program) of the above-described components may include a single or multiple entities, and some of the multiple entities may be separately placed in other components. . According to one embodiment, one or more of the above-described corresponding components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to one embodiment, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or , or one or more other operations may be added.

According to an embodiment of the present disclosure, in a non-volatile storage medium storing instructions, the instructions are set to cause the electronic device to perform at least one operation when executed by the electronic device, and the at least one operation is , based on confirmation of a first image file for which metadata is not stored or a second image file for which metadata does not contain capture date and time information, a unique key value for the first image file or the second image file An operation of generating, an operation of generating date and time information related to the first image file or the second image file as shooting date and time information, and the unique information in the first table of the DB included in the memory of the electronic device It may include an operation of matching and storing the key value and the generated shooting and date information.

Claims (20)

In electronic devices,
A memory (130 in FIG. 1; and 230 in FIG. 2) including a DB (231 in FIG. 2) in which a first table (231a in FIG. 2) in which the unique key value of the image file is matched and stored and stored (231a in FIG. 2) is stored. ; and
Includes a processor (120 in FIG. 1; 220 in FIG. 2),
The memory, when executed, the processor,
Based on confirmation of a first image file for which no metadata is stored or a second image file for which the metadata does not contain capture date and time information, a unique key value for the first image file or the second image file is determined. create,
Date and time information related to the first image file or the second image file is generated as shooting date and time information, and the unique key value and the generated shooting and date information are matched and stored in the first table of the DB. An electronic device that stores instructions to do something.
The method of claim 1, wherein the instructions are configured to allow the processor to:
An electronic device that, upon confirming the creation of an image file, determines whether the created image file is the first image file or the second image file.
The method of claim 1 or 2, wherein the instructions allow the processor to:
An electronic device that checks whether the first state of the electronic device is the first image file or the second image file.
According to any one of claims 1 to 3,
The first state of the electronic device includes at least one of a charging state or a state in which the display screen of the electronic device is turned off.
The method of any one of claims 1 to 4, wherein the instructions are configured to allow the processor to:
An electronic device that generates the unique key value using a byte code corresponding to contents of the first image file or the second image file.
The method of any one of claims 1 to 5, wherein the instructions are configured to cause the processor to:
An electronic device that generates the unique key value by applying a byte code corresponding to the contents of the first image file or the second image file to a hash algorithm.
The method of any one of claims 1 to 6, wherein the instructions are configured to cause the processor to:
With the date and time information related to the first image file or the second image file, if the creation date and time information and modification date and time information of the first image file or the second image file are confirmed, priority information is obtained. Based on this, an electronic device generates the creation date and time information of the first image file or the second image file, or the modification date and time information as the shooting date and time information of the first image file or the second image file. .
According to any one of claims 1 to 7,
The DB includes a second table in which shooting date and time information is stored,
The processor,
An electronic device configured to store the shooting date and time information of the third image file in the second table when a third image file in which metadata including the shooting date and time information is stored in the image file is identified.
The method of any one of claims 1 to 8, wherein the instructions allow the processor to:
Based on a request to display a first image file or a second image file, generate a unique key value for the first image file or the second image file,
If the unique key value exists in the first table of the DB, the electronic device matches the unique key value with the value to detect stored shooting date and time information.
The method of any one of claims 1 to 9, wherein the instructions allow the processor to:
An electronic device that detects shooting date and time information of the third image file from a second table of the DB based on a request to display the third image file.
In a method of managing the capture date and time of an image file in an electronic device,
Based on confirmation of a first image file for which no metadata is stored or a second image file for which the metadata does not contain capture date and time information, a unique key value for the first image file or the second image file is determined. action that creates;
generating date and time information related to the first image file or the second image file as shooting date and time information; and
A method comprising matching and storing the unique key value and the generated shooting and date information in a first table of a DB included in the memory of the electronic device.
In clause 11
When confirming the creation of an image file, the method further includes checking whether the created image file is the first image file or the second image file.
The method of claim 11 or 12,
When checking the first state of the electronic device, the method further includes checking whether it is the first image file or the second image file.
According to any one of claims 11 to 13,
The first state of the electronic device includes at least one of a charging state or a state in which the display screen of the electronic device is turned off.
According to any one of claims 11 to 14,
The method further includes generating the unique key value using a byte code corresponding to contents of the first image file or the second image file.
According to any one of claims 11 to 15,
The method further includes generating the unique key value by applying a byte code corresponding to the contents of the first image file or the second image file to a hash algorithm.
According to any one of claims 11 to 16,
With the date and time information related to the first image file or the second image file, if the creation date and time information and modification date and time information of the first image file or the second image file are confirmed, priority information is obtained. Based on this, an operation of generating the creation date and time information of the first image file or the second image file, or the modification date and time information as the shooting date and time information of the first image file or the second image file. How to include more.
According to any one of claims 11 to 17,
When confirming a third image file in which metadata including shooting date and time information is stored in the image file, the shooting date and time information of the third image file is stored in the second table of the DB where the shooting date and time information is stored. A method that includes more actions.
The method according to any one of claims 11 to 18,
generating a unique key value for the first image file or the second image file based on a request to display the first image file or the second image file; and
If the unique key value exists in the first table of the DB, the method further includes detecting shooting date and time information stored by matching the unique key value with the value.
The method according to any one of claims 11 to 19,
The method further includes detecting capture date and time information of the third image file from a second table of the DB based on a request to display the third image file.

Images