KR20240066940A - Method for recovery of damaged metadata and electronic device supporting the same - Google Patents

Abstract

According to one embodiment, an electronic device comprising: a communication module; display module; Memory; and at least one processor operatively connected to the communication module, the display module, and the memory, wherein the at least one processor determines whether metadata of a file obtained from an external electronic device is damaged. , Based on confirming that the metadata is damaged, confirming at least one external electronic device connectable to the electronic device 101, and based on confirming the at least one external electronic device, through the communication module, Request metadata corresponding to the file from the at least one external electronic device, and send metadata corresponding to the file obtained by the at least one external electronic device based on the request through the communication module. An electronic device may be provided, configured to receive metadata from at least one external electronic device, and store the received metadata in the memory. Various other embodiments are possible.

Description

Method for recovering damaged metadata and electronic device supporting the same {METHOD FOR RECOVERY OF DAMAGED METADATA AND ELECTRONIC DEVICE SUPPORTING THE SAME}

Embodiments of the present disclosure relate to a method for recovering damaged metadata and an electronic device supporting the same.

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 .

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

According to one embodiment of the present disclosure, an electronic device may be configured to include a communication module, a display module, a memory, and at least one processor operatively connected to the communication module, the display module, and the memory. . The at least one processor may be configured to check whether metadata of a file acquired from an external electronic device is damaged. The at least one processor may be configured to check at least one external electronic device connectable to the electronic device based on confirmation that the metadata is damaged. The at least one processor may be configured to request metadata corresponding to the file from the at least one external electronic device through the communication module, based on identifying the at least one external electronic device. The at least one processor may be configured to receive metadata corresponding to the file obtained by the at least one external electronic device based on the request from the at least one external electronic device through the communication module. there is. The at least one processor may be configured to store the received metadata in the memory.

According to an embodiment of the present disclosure, a method of recovering damaged metadata of an electronic device may include checking whether metadata of a file acquired from an external electronic device is damaged. The method may include checking at least one external electronic device that can be connected to the electronic device based on confirmation that the metadata is damaged. The method may include requesting metadata corresponding to the file from the at least one external electronic device through a communication module, based on identifying the at least one external electronic device. The method may include receiving, through the communication module, metadata corresponding to the file obtained by the at least one external electronic device based on the request from the at least one external electronic device. . The method may include storing the received metadata in memory.

According to an embodiment of the present disclosure, in a non-transitory storage medium storing instructions, the instructions may be set to cause the electronic device to perform at least one operation when executed by at least one circuit of the electronic device. there is. The at least one operation may include checking whether metadata of a file acquired from an external electronic device is damaged. The at least one operation may include checking at least one external electronic device that can be connected to the electronic device based on confirmation that the metadata is damaged. The at least one operation may include requesting metadata corresponding to the file from the at least one external electronic device through a communication module, based on identifying the at least one external electronic device. The at least one operation includes receiving metadata corresponding to the file obtained by the at least one external electronic device based on the request from the at least one external electronic device through the communication module. can do. The at least one operation may include storing the received metadata in memory.

The means for solving the problem according to an embodiment of the present disclosure are not limited to the above-mentioned solution means, and the solution methods not mentioned may be used by those with ordinary knowledge in the technical field to which the present invention pertains from the present specification and the attached drawings. You will be able to understand it clearly.

1 is a block diagram of an electronic device in a network environment, according to an embodiment of the present disclosure.
FIG. 2 is a block diagram for explaining an example of the configuration of an electronic device according to an embodiment of the present disclosure.
FIG. 3 is a flowchart illustrating a method for an electronic device to recover damaged metadata, according to an embodiment of the present disclosure.
FIGS. 4A and 4B are diagrams illustrating an example of an electronic device recovering damaged metadata according to an embodiment of the present disclosure.
FIG. 5 is a flowchart illustrating an operation in which an electronic device changes metadata based on user input, according to an embodiment of the present disclosure.
FIGS. 6A and 6B are diagrams illustrating an example in which an electronic device changes metadata based on user input, according to an embodiment of the present disclosure.
FIG. 7 is a flowchart illustrating an operation in which an electronic device changes metadata of one or more files included in a file list, according to an embodiment of the present disclosure.
FIG. 8 is a flowchart illustrating an operation of an electronic device changing metadata based on options for changing metadata, according to an embodiment of the present disclosure.
FIGS. 9A, 9B, 9C, and 9D are diagrams illustrating an example of an electronic device changing metadata based on options for changing metadata, according to an embodiment of the present disclosure.
FIG. 10 is a flowchart illustrating an operation in which an electronic device changes metadata to match metadata of an external electronic device, according to an embodiment of the present disclosure.

Hereinafter, with reference to the drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components. Additionally, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

FIG. 1 is a block diagram of an electronic device 101 in a network environment 100 according to an embodiment of the present disclosure.

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 device) 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 may be 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 (enhanced mobile broadband (eMBB)), minimization of terminal power and access to multiple terminals (massive machine type communications (mMTC)), or ultra-reliable and low-latency (URLLC). -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 connected to the plurality of antennas by, for example, 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 must 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.

FIG. 2 is a block diagram for explaining an example of the configuration of an electronic device 101 (eg, the electronic device 101 of FIG. 1 ) according to an embodiment of the present disclosure.

Referring to FIG. 2, in one embodiment, the electronic device 101 includes a communication module 190, a display module 160, a memory 130, and the communication module 190, the display module 160, and It may include at least one processor 120 operatively connected to the memory 130.

In one embodiment, communication module 190 may be included in communication module 190 of FIG. 1 . In one embodiment, the communication module 190 communicates with an external electronic device (e.g., the electronic device 102 of FIG. 1) through a first network (e.g., the first network 198 of FIG. 1), or It is possible to communicate with an external electronic device (e.g., the electronic device 104 or the server 108 of FIG. 1) through a second network (e.g., the second network 199 of FIG. 1). In one embodiment, the external electronic device may be an electronic device that can perform an operation based on an application, such as a smartphone, tablet PC, laptop, smart TV, or desktop. In one embodiment, the external electronic device may be a cloud server that stores metadata. In one embodiment, the electronic device 101 (eg, communication module 190) may transmit data to and/or receive data from an external electronic device. In one embodiment, the electronic device 101 may transmit and/or receive a static image or video to and from an external electronic device.

In one embodiment, the display module 160 may be included in the display module 160 of FIG. 1 . In one embodiment, the display module 160 may display images (eg, static images or videos) received from an external electronic device. In one embodiment, the display module 160 may display a notification related to recovering damaged metadata.

In one embodiment, memory 130 may be included in memory 130 of FIG. 1 . In one embodiment, the memory 130 may store images received from an external electronic device. In one embodiment, the video may include metadata. For example, metadata may include at least one of the date, time, and location of the video, the file hash of the video, or the file size of the video.

In one embodiment, processor 120 may be included in processor 120 of FIG. 1 . In one embodiment, the processor 120 may determine whether metadata is damaged and perform overall operations to restore the damaged metadata. In one embodiment, processor 120 may include one or more processors for recovering metadata. One or more processors may be operatively connected to the communication module 190 and memory 130.

In FIG. 2 , the electronic device 101 is illustrated as including a communication module 190, a memory 130, and/or a processor 120, but is not limited thereto. For example, the electronic device 101 may further include at least one configuration shown in FIG. 2 . For example, the electronic device 101 may further include a sensor module (eg, sensor module 176 in FIG. 1) for acquiring (or detecting) a user input.

FIG. 3 is a flowchart illustrating a method for recovering damaged metadata by an electronic device (e.g., the electronic device 101 of FIG. 1 or the electronic device 101 of FIG. 2) according to an embodiment of the present disclosure. It is (300).

In one embodiment, the operations shown in FIG. 3 are not limited to the order shown and may be performed in various orders. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. According to one embodiment, more operations may be performed, or at least one operation less than the operations shown in FIG. 3 may be performed.

Referring to FIG. 3 , in operation 301, in one embodiment, the electronic device 101 (e.g., the processor 120 of FIG. 2) acquires from an external electronic device (e.g., the electronic device 104 of FIG. 1). You can check whether the metadata of a file is damaged.

In one embodiment, the electronic device 101 (e.g., the communication module 190 in FIG. 2) communicates with an external electronic device (e.g., the communication module 190 in FIG. 1) through a first network (e.g., the first network 198 in FIG. 1). A file can be obtained (or received) from the electronic device 102 of 1. The electronic device 101 obtains a file from an external electronic device (e.g., the electronic device 104 or server 108 of FIG. 1) through a second network (e.g., the second network 199 of FIG. 1). You can also (or receive). In one embodiment, the electronic device 101 may acquire a file through the second network 199 by executing an application. For example, the electronic device 101 may obtain a file from an external electronic device by executing a messaging application or a social network service (SNS) application. In one embodiment, the file acquired from an external electronic device may be a static image or a video, but is not limited thereto. In one embodiment, the electronic device 101 may store metadata of the acquired file in a memory (eg, the memory 130 of FIG. 1 or the memory 130 of FIG. 2). In one embodiment, memory 130 may include a database for storing metadata. The electronic device 101 may analyze the acquired metadata and store the analyzed metadata in a database. In one embodiment, the electronic device 101 may obtain (or calculate) the file size and/or file hash of the received file, and store the file size and/or file hash in the memory 130.

In one embodiment, the electronic device 101 may check (or determine) whether the metadata is damaged based on checking information included in the metadata of the acquired file. For example, the electronic device 101 may confirm that the metadata is damaged based on confirming that the metadata of the acquired file does not include at least one of information of the date the file was created, latitude, or longitude. there is. The electronic device 101 may confirm that the metadata is damaged based on confirming that the metadata in the file has been deleted. In one embodiment, the electronic device 101 may check whether the metadata of the acquired file is damaged based on confirming that the metadata of the acquired file satisfies conditions related to damage. The electronic device 101 may confirm that the metadata is damaged based on confirming that the time information of the file includes a date before the reference date. For example, the electronic device 101 may confirm that the metadata is damaged based on confirmation that the file is recorded as having been created 100 years ago, according to the time information of the file. The reference date for checking whether metadata is damaged may change in various ways according to embodiments of the present disclosure. In one embodiment, the electronic device 101 may check whether the metadata is damaged based on confirming that the information included in the metadata includes a data format that cannot be read by the electronic device 101.

In one embodiment, the electronic device 101 receives the metadata of the original file and the converted You can receive metadata of files. In one embodiment, the converted file may be an image whose resolution has been converted by a messaging application server or SNS server. In one embodiment, the electronic device 101 determines that the metadata of the original file or the metadata of the converted file is deleted or that at least some information in the metadata is lost, based on data parsing. Based on this, it can be confirmed that the metadata is damaged.

In operation 303, in one embodiment, the electronic device 101 may identify at least one external electronic device that can be connected to the electronic device 101.

In one embodiment, the electronic device 101 may identify at least one external electronic device that can be connected to the electronic device 101 based on confirmation that the metadata is damaged. At least one external electronic device connectable to the electronic device 101 may include an external electronic device containing intact metadata and an external electronic device containing damaged metadata.

In one embodiment, the electronic device 101 may identify at least one external electronic device (e.g., the electronic device 102 of FIG. 1) containing intact metadata through the first network 198. there is. For example, the at least one external electronic device is an electronic device confirmed to be connectable to the electronic device 101 based on a user identifier or a history of connecting short-range wireless communication (e.g., Bluetooth, WiFi direct, or IrDA). It can be. User identifiers may include, but are not limited to, IDs or email accounts. In one embodiment, the electronic device 101 connects, via the second network 199, to at least one external electronic device (e.g., the electronic device 104 of FIG. 1 or the server 108) containing intact metadata. You can also check )). For example, the at least one external electronic device may be a cloud server confirmed to be capable of connecting to the electronic device 101 based on the user identifier.

The electronic device 101 according to one embodiment may identify an external electronic device containing damaged metadata. If metadata of a file is damaged, the external electronic device may calculate metadata based on internal logic. The external electronic device may store the calculated metadata in a database (not shown) of the external electronic device. For example, if the metadata of an image file (e.g., the time the image was taken) is damaged or nonexistent, the external electronic device may detect the creation time or modification time of the image file recorded in the file system. It can be saved as data.

In operation 305, in one embodiment, the electronic device 101 may request metadata from at least one external electronic device.

In one embodiment, the electronic device 101 sends metadata corresponding to the file to the at least one external electronic device through the communication module 190, based on identifying the at least one external electronic device. You can request it. For example, the electronic device 101 may query the at least one external electronic device for a file identical to a file containing damaged metadata. The electronic device 101 may transmit the file size and/or file hash to the at least one external electronic device. In one embodiment, the at least one external electronic device may identify a file that is the same as the file requested by the electronic device 101 based on the file size and/or file hash. In one embodiment, the electronic device 101 may transmit metadata of the original file and/or metadata of the converted file to the at least one external electronic device. The at least one external electronic device may identify a file that is the same (or similar) to the file requested by the electronic device 101 based on the metadata of the original file and/or the metadata of the converted file.

In operation 307, in one embodiment, the electronic device 101 may receive metadata from at least one external electronic device.

In one embodiment, the electronic device 101 sends metadata corresponding to the file obtained by the at least one external electronic device based on the request to the at least one external electronic device through the communication module 190. It can be received from an electronic device. In one embodiment, the at least one external electronic device may transmit metadata corresponding to the file to the electronic device 101 based on obtaining the same file as the file requested by the electronic device 101. . The electronic device 101 may receive intact metadata from the at least one external electronic device through the first network 198 or the second network 199.

In one embodiment, if the external electronic device identified in operation 303 is an external electronic device containing damaged metadata, the electronic device 101 may receive metadata calculated by the external electronic device from the external electronic device. there is. In one embodiment, the electronic device 101 may receive metadata stored in a database of an external electronic device. For example, metadata stored in the database of the external electronic device may be information stored in Samsung extended format (SEF) or information recorded in a file system. An external electronic device can check the values stored as SEF if EXIF metadata such as DateTimeOriginal and/or TimeOffsetOriginal for the image file is damaged. If a value stored in SEF exists for the image file, the external electronic device may store the information stored in SEF as metadata of the image file in a database. The external electronic device may check the creation time (eg, mtime) of the file recorded in the file system when the value stored in SEF does not exist. The external electronic device may store the creation time of the file as metadata of the image file in a database. Based on confirmation that the EXIF metadata of the image file is damaged, the electronic device 101 may receive a value stored in the database of the external electronic device from the external electronic device including the damaged metadata. The electronic device 101 may change the metadata of an image file with damaged metadata based on a value stored in the database of the external electronic device. The electronic device 101 can maintain the same metadata for the image file as that of the external electronic device.

In operation 309, in one embodiment, the electronic device 101 may store the received metadata.

In one embodiment, the electronic device 101 may store metadata received from the at least one external electronic device in the memory 130. In one embodiment, the electronic device 101 may delete damaged metadata and store metadata received from the at least one external electronic device as metadata corresponding to the file.

In one embodiment, the electronic device 101 displays an object containing a notification related to modification of metadata through a display module (e.g., the display module 160 of FIG. 1 or the display module 160 of FIG. 2). It can be displayed. In one embodiment, the object may include an object that approves modification of the metadata and an object that rejects modification of the metadata. The electronic device 101 deletes the damaged metadata based on a user input for an object that approves modification of the metadata, and modifies the metadata received from the at least one external electronic device to the file corresponding to the file. It can be saved as metadata.

FIGS. 4A and 4B illustrate a process in which an electronic device 101 (e.g., the electronic device 101 of FIG. 1 or the electronic device 101 of FIG. 2) recovers damaged metadata, according to an embodiment of the present disclosure. This is a drawing showing an example.

Referring to FIG. 4A, in one embodiment, the electronic device 101 (e.g., the communication module 190 of FIG. 2) acquires a file from the first external electronic device 401 through the network 403 ( or receive). In one embodiment, network 403 may be a first network (e.g., first network 198 in FIG. 1) or a second network (e.g., second network 199 in FIG. 1). The first external electronic device 401 (e.g., the electronic device 102 in FIG. 1) may transmit a file to the electronic device 101 through the first network 198. The first external electronic device 401 (e.g., the electronic device 104 or the server 108 in FIG. 1) may transmit a file to the electronic device 101 through the second network 199. In one embodiment, the first external electronic device 401 may be an electronic device that transmits a file including metadata to the electronic device 101.

In one embodiment, the electronic device 101 may obtain a file from the first external electronic device 401 through the network 403 by executing an application. For example, the electronic device 101 may obtain (or receive) a file from the first external electronic device 401 by executing a messaging application or an SNS application. In one embodiment, the electronic device 101 may store metadata of the acquired file in a memory (eg, the memory 130 of FIG. 1 or the memory 130 of FIG. 2). In one embodiment, the electronic device 101 may obtain (or calculate) the file size and/or file hash of the received file, and store the file size and/or file hash in the memory 130.

In one embodiment, the electronic device 101 may check whether metadata of a file acquired from the first external electronic device 401 is damaged. In one embodiment, the electronic device 101 may check (or determine) whether the metadata is damaged based on checking information included in the metadata of the acquired file. For example, the electronic device 101 may confirm that the metadata is damaged based on confirming that the metadata of the acquired file does not include at least one of information of the date the file was created, latitude, or longitude. there is. The electronic device 101 may confirm that the metadata is damaged based on confirming that the metadata in the file has been deleted. In one embodiment, the electronic device 101 may check whether the metadata of the acquired file is damaged based on confirming that the metadata of the acquired file satisfies conditions related to damage. The electronic device 101 may confirm that the metadata is damaged based on confirming that the time information of the file includes a date before the reference date. For example, the electronic device 101 may confirm that the metadata is damaged based on confirmation that the file is recorded as having been created 100 years ago, according to the time information of the file. The reference date for checking whether metadata is damaged may change in various ways according to embodiments of the present disclosure. In one embodiment, the electronic device 101 may check whether the metadata is damaged based on confirming that the information included in the metadata includes a data format that cannot be read by the electronic device 101.

In one embodiment, the electronic device 101 may receive metadata of the original file and metadata of the converted file from the first external electronic device 401 through the network 403. In one embodiment, the converted file may be an image whose resolution has been converted by a messaging application server or SNS server. In one embodiment, the electronic device 101 determines, based on data parsing, that the metadata of the original file or the metadata of the converted file is deleted, or that at least some information in the metadata is lost, You can confirm that the metadata is damaged.

Referring to FIG. 4B, in one embodiment, the electronic device 101 may identify at least one external electronic device containing intact metadata based on confirming that metadata included in the file is damaged. . The at least one external electronic device may include a second external electronic device 411 and/or a cloud server 421. In one embodiment, the electronic device 101 may establish communication with the second external electronic device 411 through the first network 198. In one embodiment, the second external electronic device 411 may be capable of communicating with the electronic device 101 and may be an electronic device that includes intact metadata. Although not shown in FIG. 4B, the electronic device 101 may connect to the second external electronic device 411 for communication through the second network 199. In one embodiment, the electronic device 101 may establish communication with the cloud server 421 through the second network 199 based on the user identifier. User identifiers may include, but are not limited to, IDs and/or email accounts. In one embodiment, the cloud server 421 may establish communication with the electronic device 101 based on the user identifier received from the electronic device 101, and may connect a server containing intact metadata (e.g., It may be server 108 of 1.

In one embodiment, the electronic device 101 operates the communication module 190 based on identifying the at least one external electronic device (second external electronic device 411 and/or cloud server 421). Through this, metadata corresponding to the file may be requested from the at least one external electronic device 411 and/or 421. For example, the electronic device 101 may query the at least one external electronic device 411 and/or 421 for a file identical to a file containing damaged metadata. The electronic device 101 may transmit the file size and/or file hash to the at least one external electronic device 411 and/or 421. In one embodiment, the at least one external electronic device 411 and/or 421 may identify a file that is the same as the file requested by the electronic device 101 based on the file size and/or file hash. In one embodiment, the electronic device 101 may transmit metadata of the original file and/or metadata of the converted file to the at least one external electronic device 411 and/or 421. The at least one external electronic device 411 and/or 421 is the same as (or similar to) the file requested by the electronic device 101, based on the metadata of the original file and/or the metadata of the converted file. You can check one file.

In one embodiment, the electronic device 101, through the communication module 190, sends a meta message corresponding to the file obtained by the at least one external electronic device 411 and/or 421 based on the request. Data may be received from the at least one external electronic device 411 and/or 421. In one embodiment, the at least one external electronic device 411 and/or 421 responds to the file to the electronic device 101 based on obtaining the same file as the file requested by the electronic device 101. metadata can be transmitted. The electronic device 101 may receive intact metadata from the at least one external electronic device 411 and/or 421 through the first network 198 or the second network 199.

In one embodiment, the electronic device 101 may store metadata received from the at least one external electronic device 411 and/or 421 in the memory 130 . In one embodiment, the electronic device 101 may delete damaged metadata and store metadata received from the at least one external electronic device as metadata corresponding to the file.

In one embodiment, the electronic device 101 displays an object containing a notification related to modification of metadata through a display module (e.g., the display module 160 of FIG. 1 or the display module 160 of FIG. 2). It can be displayed. In one embodiment, the object may include an object that approves modification of the metadata and an object that rejects modification of the metadata. The electronic device 101 deletes the damaged metadata based on a user input for an object that approves modification of the metadata, and modifies the metadata received from the at least one external electronic device to the file corresponding to the file. It can be saved as metadata.

FIG. 5 is a flowchart 500 for explaining an operation in which the electronic device 101 changes metadata based on user input, according to an embodiment of the present disclosure.

In one embodiment, the operations shown in FIG. 5 are not limited to the order shown and may be performed in various orders. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. According to one embodiment, more operations may be performed, or at least one operation less than the operations shown in FIG. 5 may be performed.

Referring to FIG. 5 , in operation 501, in one embodiment, the electronic device 101 (e.g., processor 120 of FIG. 1 or processor 120 of FIG. 2) may display a file acquisition notification. .

In one embodiment, the electronic device 101 may display a notification of acquisition of the file through the display module 160. The electronic device 101 uses a display module (e.g., the display module of FIG. 1) to display a file acquisition notification based on acquiring a file from an external electronic device (e.g., the first external electronic device 401 of FIG. 4A). (160) or the display module 160 of FIG. 2) can be controlled. The electronic device 101 may display a file acquisition notification after operation 307 or operation 309 of FIG. 3 .

In operation 503, in one embodiment, the electronic device 101 may display an object regarding whether metadata has been modified.

In one embodiment, the electronic device 101 may display an object regarding whether the metadata has been modified through the display module 160, based on a user input for the acquisition notification. If the acquired file is a static image, the electronic device 101 may further display the static image and the name of the file. If the acquired file is a video, the electronic device 101 may further display a representative image of the video and the name of the file.

At operation 505, in one embodiment, the electronic device 101 may change the metadata to undamaged metadata.

In one embodiment, the electronic device 101 selects the at least one external electronic device (e.g., the second external electronic device 411 of FIG. 4B or the cloud server) based on a user input for the object regarding whether to modify it. The metadata for the acquired file can be changed with undamaged metadata received from (421)). In one embodiment, the user input may be a touch event for an object, but there is no limitation thereto. The electronic device 101 may change metadata based on user input based on intact metadata obtained in operations 301 to 309 of FIG. 3 .

FIGS. 6A and 6B are diagrams illustrating an example in which the electronic device 101 changes metadata based on user input, according to an embodiment of the present disclosure.

Referring to FIG. 6A, in one embodiment, the electronic device 101 (e.g., the processor 120 of FIG. 1 or the processor 120 of FIG. 2) includes a display module (e.g., the display module 160 of FIG. 1). Alternatively, a file acquisition notification 610 may be displayed through the display module 160 of FIG. 2. The electronic device 101 may control the display module to display a file acquisition notification 610 based on acquiring a file from an external electronic device (e.g., the first external electronic device 401 in FIG. 4A). . In one embodiment, the electronic device 101 displays a file acquisition notification 610 through the display module 160 based on confirmation that the metadata of the file acquired based on operation 301 of FIG. 3 is damaged. can do. In one embodiment, the electronic device 101 may display a file acquisition notification 610 after operation 307 or 309 of FIG. 3 . For example, the electronic device 101 requests metadata for the file from at least one external electronic device and receives undamaged metadata from the external electronic device or metadata stored in the database of the external electronic device. Based on this, an acquisition notification 610 for a file with damaged metadata may be displayed through the display module 160. In one embodiment, when the acquired file is a static image or video, the electronic device 101 may further display the acquired image 611 through the display module 160.

Referring to FIG. 6B, an object 620 regarding whether metadata has been modified may be displayed. In one embodiment, the electronic device 101 determines whether the metadata is modified through the display module 160, based on a user input for the acquisition notification (e.g., acquisition notification 610 in FIG. 6A). An object 620 related to can be displayed. In one embodiment, the user input may be a touch event for an object, but there is no limitation thereto. If the acquired file is a static image or video, the electronic device 101 may further display the acquired image 611 and the name 623 of the file. The electronic device 101 sends the metadata to at least one external electronic device (e.g., the second external electronic device 411 of FIG. 4B or the cloud server 421) along with the object 620 regarding whether the metadata has been modified. ) may further display a notification 621 guiding you to select whether to receive it from. In one embodiment, the electronic device 101 stores the acquired file with undamaged metadata received from the at least one external electronic device based on a user input for the object 620 regarding whether to modify it. You can change metadata about it. In one embodiment, the electronic device 101 detects an undamaged device from at least one external electronic device based on operations 303 to 307 of FIG. 3, based on a user input for the object 620 regarding whether to modify it. Based on receiving the metadata, the metadata for the obtained file may be changed to intact metadata. In one embodiment, after the electronic device 101 receives uncorrupted metadata from at least one external electronic device, a file acquisition notification (e.g., acquisition notification 610 of FIG. 6A) is sent through the display module 160. ) is displayed, the electronic device 101 may change the metadata for the acquired file to undamaged metadata based on the user input for the object 620 regarding whether or not to modify. The electronic device 101 may change metadata based on user input based on intact metadata obtained in operations 301 to 309 of FIG. 3 .

FIG. 7 is a flowchart 700 illustrating an operation in which the electronic device 101 changes metadata of one or more files included in a file list, according to an embodiment of the present disclosure.

In one embodiment, the operations shown in FIG. 7 are not limited to the order shown and may be performed in various orders. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. According to one embodiment, more operations may be performed, or at least one operation less than the operations shown in FIG. 7 may be performed.

Referring to FIG. 7 , in operation 701, in one embodiment, the electronic device 101 (e.g., processor 120 of FIG. 1 or processor 120 of FIG. 2) determines an event related to starting an idle mode. Based on this, files that contain the same file information and have different metadata can be identified.

In one embodiment, the electronic device 101 may identify one or more files that contain the same file information and have different metadata based on identifying an event related to the start of the idle mode. In one embodiment, events related to the start of idle mode may include, but are limited to, a state in which the user does not use the electronic device 101 for more than a reference time and/or a state in which the electronic device 101 is charging. There is no In one embodiment, referring to Table 1, the electronic device 101 may confirm that the one or more files with different metadata contain the same file information based on confirming that the file size and file hash are the same. there is.

In operation 703, in one embodiment, the electronic device 101 may obtain a file list including confirmed files.

In one embodiment, the electronic device 101 creates the file list by traversing metadata for one or more files stored in a memory (e.g., memory 130 of FIG. 1 or memory 130 of FIG. 2). It can be obtained. Based on detecting the start of the idle mode, the electronic device 101 can obtain a file list without interfering with other functions of the electronic device 101.

In operation 705, in one embodiment, the electronic device 101 may display a notification regarding the file list based on confirming an event related to the end of the idle mode.

In one embodiment, the electronic device 101 may display a notification regarding the file list through the display module 160 based on confirming an event related to the end of the idle mode. In one embodiment, the event related to the end of the idle mode may be, but is not limited to, a state in which the user uses the electronic device 101 again. The electronic device 101 may provide an option to modify metadata by displaying a list of files acquired during idle mode.

In operation 707, in one embodiment, the electronic device 101 may change metadata of at least some of one or more files included in the file list.

In one embodiment, the electronic device 101 may change metadata of at least some of one or more files included in the file list based on a user input for a notification regarding the file list. A specific method by which the electronic device 101 changes metadata will be described later with reference to FIGS. 8, 9A, 9B, 9C, and 9D.

FIG. 8 is a flowchart 800 for explaining an operation of the electronic device 101 changing metadata based on options for changing metadata, according to an embodiment of the present disclosure.

In one embodiment, the operations shown in FIG. 8 are not limited to the order shown and may be performed in various orders. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. According to one embodiment, more operations may be performed, or at least one operation less than the operations shown in FIG. 8 may be performed.

Referring to FIG. 8, in operation 801, in one embodiment, the electronic device 101 (e.g., the processor 120 of FIG. 1 or the processor 120 of FIG. 2) selects a file list containing the same file information. You can select files.

In one embodiment, the electronic device 101 may select files containing the same file information from the file list based on a user input for a notification regarding the file list.

At operation 803, in one embodiment, the electronic device 101 may display options for changing metadata.

In one embodiment, the electronic device 101 may display one or more options for changing metadata for files containing the same file information through the display module 160. The options may include, but are not limited to, at least one of metadata created first (oldest), metadata belonging to the most files (popular), or metadata based on user input values. For example, the option to change the metadata includes the option to change the metadata to that of another file created at a similar time as the file was created, and/or to change the metadata to the metadata of another file that has similar file information to the file. It may further include.

In operation 805, in one embodiment, the electronic device 101 may change metadata for files containing the same file information.

In one embodiment, the electronic device 101 stores the same file information so that metadata of files including the same file information match based on a user input for one option among the one or more options. You can change the metadata for the files it contains. In one embodiment, the electronic device 101 may collectively modify the metadata of files that include the same file information and have different metadata according to operations 801 to 805 so that the metadata matches.

9A, 9B, 9C, and 9D show an electronic device 101 (e.g., the electronic device 101 of FIG. 1 or the electronic device 101 of FIG. 2) according to an embodiment of the present disclosure. This is a diagram showing an example of changing metadata based on options for changing metadata.

Referring to FIG. 9A , in one embodiment, the electronic device 101 (e.g., processor 120 of FIG. 1 or processor 120 of FIG. 2), based on identifying an event related to the end of the idle mode, Through the display module 160, a notification 910 regarding the file list can be displayed. In one embodiment, when the file is an image, the electronic device 101 may further display images 911 included in the file list.

Referring to FIG. 9B, in one embodiment, the electronic device 101 may select files containing the same file information from a file list. In one embodiment, the electronic device 101, based on a user input for a notification regarding the file list (e.g., notification 910 in FIG. 9A), selects a file containing the same file information from among the file list 920. You can select files. The user input may be a touch event on the display module 160, but there is no limitation thereto. In one embodiment, the electronic device 101 stores images (921a, 921b, 921c, and/or 921d) corresponding to each of the files included in the file list and storage paths (923a, 923b, 923c, and/or 923d) may be further displayed.

Referring to FIG. 9C, in one embodiment, the electronic device 101 may display options for changing metadata. In one embodiment, the electronic device 101, through the display module 160, provides one or more options 931a, 931b, and/or 931c for changing metadata for files containing the same file information. ) can be displayed. The options may include, but are not limited to, at least one of metadata created first, metadata contained in the most files, or metadata based on user input values. For example, the option to change the metadata includes the option to change the metadata to that of another file created at a similar time as the file was created, and/or to change the metadata to the metadata of another file that has similar file information to the file. It may further include.

In one embodiment, the electronic device 101 may change metadata for files containing the same file information. In one embodiment, the electronic device 101 generates a meta file of files containing the same file information based on a user input for one of the one or more options 931a, 931b, and/or 931c. To ensure that the data matches, metadata for files containing the same file information can be changed. In one embodiment, the electronic device 101 may collectively modify the metadata of files that include the same file information and have different metadata according to operations 801 to 805 so that the metadata matches.

Referring to FIG. 9D, the electronic device 101, through the display module 160, changes the metadata of each file for all files included in the file list in the same manner as the option selected in FIG. 9C. A notification 941 regarding whether to perform may be displayed. For example, the electronic device 101 may display the notification 941 based on a user input for one option among one or more options 931a, 931b, and 931c of FIG. 9C. The electronic device 101 changes the metadata of all files included in the file list in the same manner as the option selected in FIG. 9C, based on the user input to the object 943 associated with the operation allowing change of metadata. You can. The electronic device 101 selects the remaining files except the file whose metadata has been modified based on the option selected in FIG. 9C, based on the user input to the object 945 associated with the operation of rejecting the change of the metadata of the remaining files. Their metadata may not be changed.

FIG. 10 shows an electronic device (e.g., the electronic device 101 of FIG. 1 or the electronic device 101 of FIG. 2) changing metadata to match the metadata of an external electronic device, according to an embodiment of the present disclosure. This is a flowchart (1000) to explain the operation.

In one embodiment, the operations shown in FIG. 10 are not limited to the order shown and may be performed in various orders. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. According to one embodiment, more operations may be performed, or at least one operation less than the operations shown in FIG. 10 may be performed.

Referring to FIG. 10 , in operation 1001, in one embodiment, the electronic device 101 (e.g., processor 120 of FIG. 1 or processor 120 of FIG. 2) determines an event related to starting an idle mode. Based on this, an external electronic device (e.g., the second external electronic device 411 or the cloud server 421 in FIG. 4B) that can connect to communication can be identified.

In one embodiment, the electronic device 101 may identify at least one external electronic device with which communication can be established based on identifying an event related to the start of the idle mode. In one embodiment, events related to the start of idle mode may include, but are limited to, a state in which the user does not use the electronic device 101 for more than a reference time and/or a state in which the electronic device 101 is charging. There is no

In operation 1003, in one embodiment, the electronic device 101 may obtain file hashes for files from an external electronic device.

In one embodiment, the electronic device 101 receives one signal from the at least one external electronic device 411 and/or 421 based on a communication connection with the at least one external electronic device 411 and/or 421. File hashes for the above files can be obtained.

In operation 1005, in one embodiment, the electronic device 101 may check a file that contains the same file information as a file stored in an external electronic device and has different metadata.

In one embodiment, the electronic device 101 includes the same file information as the file stored in the at least one external electronic device 411 and/or 421, based on the obtained file hashes, and the metadata is different from each other. At least one different file can be identified. In one embodiment, the electronic device 101 may confirm that the one or more files with different metadata include the same file information based on confirming that the file size and file hash are the same.

In operation 1007, in one embodiment, the electronic device 101 may display a notification regarding a change in metadata for the identified file based on confirming an event related to the end of the idle mode.

In one embodiment, the electronic device 101 provides, through the display module 160, a notification regarding a change in metadata for the identified at least one file, based on confirming an event related to the end of the idle mode. can be displayed. In one embodiment, the event related to the end of the idle mode may be, but is not limited to, a state in which the user uses the electronic device 101 again. In one embodiment, the electronic device 101 selects whether to change the metadata for at least one identified file to match the metadata of the corresponding file stored in the external electronic device 411 and/or 421. A notification can be displayed.

At operation 1009, in one embodiment, the electronic device 101 may change metadata of the identified file.

In one embodiment, the electronic device 101, based on a user input for a notification regarding a change in the metadata, determines that the metadata of the at least one confirmed file is transmitted to the at least one external electronic device 411 and /Or, the metadata of the at least one confirmed file may be changed so that the file information stored in 421) matches the metadata of the same file. In one embodiment, the user input may be a touch event on the display module 160, but is not limited thereto. The electronic device 101 may recover files whose metadata may be damaged based on file hashes obtained from the external electronic device 411 and/or 421 during the idle mode.

The electronic device 101 according to an embodiment of the present disclosure includes a communication module 190, a display module 160, a memory 130, and the communication module 190, the display module 160, and the memory. It may be configured to include at least one processor 120 operatively connected to 130 . The at least one processor 120 may be configured to check whether metadata of a file acquired from the external electronic device 401 is damaged. The at least one processor 120 may be configured to identify at least one external electronic device 411 or 421 that includes intact metadata based on confirmation that the metadata is damaged. The at least one processor 120, based on identifying the at least one external electronic device 411; 421, sends a message to the at least one external electronic device 411; 421 through the communication module 190. It may be configured to request metadata corresponding to the file. The at least one processor 120, through the communication module 190, sends metadata corresponding to the file acquired by the at least one external electronic device 411; 421 based on the request. It may be configured to receive from one external electronic device (411; 421). The at least one processor 120 may be configured to store the received metadata in the memory 130 .

According to one embodiment, the at least one processor 120 may be configured to display an acquisition notification 610 of the file through the display module 160. The at least one processor 120 may be configured to display an object 620 regarding whether the metadata has been modified through the display module 160, based on a user input for the acquisition notification 610. You can. The at least one processor 120 obtains the intact metadata received from the at least one external electronic device 411; 421 based on a user input for the object 620 regarding whether to modify it. It can be configured to change metadata for a file.

According to one embodiment, the at least one processor 120 may be configured to identify one or more files that contain the same file information and have different metadata, based on identifying an event related to the start of the idle mode. there is. The at least one processor 120 may be configured to obtain a file list 920 including the one or more confirmed files. The at least one processor 120 may be configured to display a notification regarding the file list 920 through the display module 160 based on confirming an event related to the end of the idle mode. The at least one processor 120 is configured to change at least some metadata among one or more files included in the file list 920 based on a user input for a notification regarding the file list 920. It can be.

According to one embodiment, the at least one processor 120 may be configured to confirm that the one or more files with different metadata contain the same file information, based on confirming that the file size and file hash are the same. You can.

According to one embodiment, the at least one processor 120, based on a user input for a notification regarding the file list 920, selects files 921a and 921b that include the same file information from among the file list 920; It can be configured to select 921c; 921d). The at least one processor 120, through the display module 160, provides one or more options (931a) for changing metadata for files (921a; 921b; 921c; 921d) including the same file information. It can be configured to display 931b; 931c). The at least one processor 120 is configured to match metadata of files containing the same file information based on a user input for one option among the one or more options 931a; 931b; 931c, It may be configured to change metadata for files containing the same file information.

According to one embodiment, the at least one processor 120 may be configured to identify at least one external electronic device 411; 421 with which communication can be connected based on identifying an event related to the start of an idle mode. You can. The at least one processor 120 processes one or more files from the at least one external electronic device 411; 421 based on communication with the at least one external electronic device 411; 421. It may be configured to obtain hashes. Based on the obtained file hashes, the at least one processor 120 includes at least one file information that is the same as a file stored in the at least one external electronic device (411; 421) and has different metadata. It can be configured to check files. The at least one processor 120 displays a notification regarding a change in metadata for the identified at least one file through the display module 160, based on confirming an event related to the end of the idle mode. It can be configured to do so. The at least one processor 120, based on a user input for a notification regarding a change in the metadata, transmits the metadata of the confirmed at least one file to the at least one external electronic device 411; 421. It may be configured to change the metadata of the at least one identified file so that the file information stored in matches the metadata of the same file.

According to one embodiment, in the electronic device 101, the metadata may include at least one of the latitude and longitude at which the file was created, or the date on which the file was created.

According to one embodiment, the at least one processor 120 may be configured to confirm that the metadata is damaged based on confirming that at least one of latitude, longitude, or date included in the metadata is lost. You can.

According to one embodiment, in the electronic device 101, a request for metadata corresponding to the file may include the file size and file hash for the file.

According to one embodiment, in the electronic device 101, a request for metadata corresponding to the file includes the file size and file hash of the original file for the file when the file is a file whose resolution has been converted. can do.

A method for recovering damaged metadata of the electronic device 101 according to an embodiment of the present disclosure may include checking whether metadata of a file acquired from the external electronic device 401 is damaged. The method may include an operation of confirming at least one external electronic device 411 (421) containing intact metadata, based on confirming that the metadata is damaged. The method provides metadata corresponding to the file to the at least one external electronic device (411; 421) through the communication module 190, based on identifying the at least one external electronic device (411; 421). It may include an action requesting . The method includes sending metadata corresponding to the file acquired by the at least one external electronic device (411; 421) based on the request to the at least one external electronic device (411; 421) through the communication module 190. It may include an operation of receiving from 411; 421). The method may include storing the received metadata in the memory 130.

In one embodiment, the method may include displaying an acquisition notification 610 of the file through the display module 160. The method may include an operation of displaying an object 620 regarding whether the metadata has been modified through the display module 160, based on a user input for the acquisition notification 610. The method includes metadata for the acquired file with undamaged metadata received from the at least one external electronic device (411; 421), based on a user input for the object 620 regarding whether or not to modify. It may further include an operation to change .

According to one embodiment, the method may include checking one or more files that contain the same file information and have different metadata, based on checking an event related to the start of the idle mode. The method may include obtaining a file list 920 including the identified one or more files. The method may include displaying a notification 910 regarding the file list 920 through the display module 160 based on confirming an event related to the end of the idle mode. The method further includes an operation of changing metadata of at least some of the one or more files included in the file list 920 based on a user input to the notification 910 regarding the file list 920. can do.

According to one embodiment, in the method, the operation of checking one or more files that contain the same file information and have different metadata is based on confirming that the file size and file hash are the same, and the operation of checking one or more files that have different metadata An operation may be included to confirm that the one or more files contain the same file information.

According to one embodiment, in the method, the operation of changing metadata of at least some of the one or more files included in the file list 920 is performed by the user receiving a notification 910 regarding the file list 920. Based on the input, the operation of selecting files containing the same file information from the file list 920 may be included. The operation of changing the metadata includes one or more options (931a) for changing metadata for files (921a; 921b; 921c; 921d) including the same file information through the display module 160; It may include an operation to display 931b; 931c). The operation of changing the metadata includes files (921a; 921b; 921c; An operation of changing metadata for files 921a, 921b, 921c, and 921d including the same file information may be included so that the metadata of 921d) matches.

The method may include an operation of identifying at least one external electronic device 411 (421) capable of establishing a communication connection, based on identifying an event related to the start of an idle mode. The method includes an operation of obtaining file hashes for one or more files from the at least one external electronic device (411; 421) based on connecting communication with the at least one external electronic device (411; 421). It can be included. The method includes the operation of checking at least one file that contains the same file information as a file stored in the at least one external electronic device (411; 421) and has different metadata, based on the obtained file hashes. It can be included. The method may include displaying, through the display module 160, a notification regarding a change in metadata for the identified at least one file, based on confirming an event related to the end of the idle mode. . The method includes, based on a user input for a notification regarding a change in the metadata, the metadata of the confirmed at least one file, and the metadata of the file with the same file information stored in the at least one external electronic device. It may further include an operation of changing metadata of the at least one identified file to match.

According to one embodiment, in the method, the metadata may include at least one of the latitude and longitude at which the file was created, or the date on which the file was created.

According to one embodiment, in the method, the operation of checking whether the metadata is damaged is based on confirming that at least one of latitude, longitude, or date included in the metadata is lost, It may include an operation to confirm that the is damaged.

According to one embodiment, in the method, a request for metadata corresponding to the file may include a file size and a file hash for the file.

According to one embodiment, in the above method, a request for metadata corresponding to the file may include the file size and file hash of the original file for the file when the file is a file whose resolution has been converted.

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 items, unless the relevant context clearly indicates otherwise. In this document: "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "either A, B, and C. Phrases such as “at least one”, and “at least one of A, B, or C” may each include any one of the items listed together in that phrase, or any possible combination thereof. there is. "First", "Second", or "First" Terms such as "second" may be used simply to distinguish one element from another, without limiting the elements in any other respect (e.g., importance or order). One (e.g. first) component is "functionally" dependent on another (e.g. second) component. or, with or without the term "communicatively", "coupled" or "connected", it means that any component can be connected to another component 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 is interchangeable with terms such as logic, logic block, component, or circuit, for example. It can be used negatively. 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).

One embodiment of the present document is one or more instructions stored in 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). It may be implemented as software (e.g., program 140) including these. For example, a processor (e.g., processor 120) of a device (e.g., electronic device 101) 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). This term refers to cases where data is stored semi-permanently 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 through 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 identically or similarly to 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.

Additionally, the data structure used in the above-described embodiments of the present invention can be recorded on a computer-readable recording medium through various means. The computer-readable recording media includes storage media such as magnetic storage media (eg, ROM, floppy disk, hard disk, etc.) and optical read media (eg, CD-ROM, DVD, etc.).

So far, the present invention has been examined focusing on its preferred embodiments. A person skilled in the art to which the present invention pertains will understand that the present invention may be implemented in a modified form without departing from the essential characteristics of the present invention. Therefore, the disclosed embodiments should be considered from an illustrative rather than a restrictive perspective. The scope of the present invention is indicated in the claims rather than the foregoing description, and all differences within the equivalent scope should be construed as being included in the present invention.

Claims (20)

In the electronic device 101,
Communication module 190;
display module 160;
memory (130); and
Comprising at least one processor 120 operatively connected to the communication module 190, the display module 160, and the memory 130,
The at least one processor 120,
Check whether the metadata of the file acquired from the external electronic device 401 is damaged,
Based on confirmation that the metadata is damaged, confirming at least one external electronic device (411; 421) that can be connected to the electronic device (101),
Based on confirming the at least one external electronic device (411; 421), request metadata corresponding to the file from the at least one external electronic device (411; 421) through the communication module 190; ,
Through the communication module 190, metadata corresponding to the file acquired by the at least one external electronic device 411; 421 is transmitted to the at least one external electronic device 411; 421 based on the request. receive from, and
An electronic device (101) configured to store the received metadata in the memory (130).
According to claim 1,
The at least one processor 120,
Displaying an acquisition notification 610 of the file through the display module 160,
Based on the user input for the acquisition notification 610, an object 620 regarding whether the metadata has been modified is displayed through the display module 160, and
Configured to change metadata for the acquired file into undamaged metadata received from the at least one external electronic device (411; 421) based on a user input on the object 620 regarding whether to modify or not. , electronic device (101).
The method of claim 1 or 2,
The at least one processor 120,
Based on identifying an event related to the start of idle mode, identifying one or more files that contain the same file information and have different metadata,
Obtaining a file list 920 containing the one or more identified files,
Based on confirming an event related to the end of the idle mode, displaying a notification regarding the file list 920 through the display module 160, and
An electronic device (101) configured to change metadata of at least some of one or more files included in the file list (920) based on a user input for a notification regarding the file list (920).
The method according to any one of claims 1 to 3,
The at least one processor 120,
The electronic device (101) is configured to confirm that the one or more files with different metadata contain the same file information, based on confirming that the file size and file hash are the same.
The method according to any one of claims 1 to 4,
The at least one processor 120,
Based on the user input for the notification regarding the file list 920, select files 921a; 921b; 921c; 921d) containing the same file information from the file list,
Through the display module 160, display one or more options (931a; 931b; 931c) for changing metadata for files (921a; 921b; 921c; 921d) containing the same file information, and
Based on the user input for one option among the one or more options (931a; 931b; 931c), metadata of the files including the same file information are matched to the files including the same file information. An electronic device (101) configured to change metadata about an electronic device (101).
The method according to any one of claims 1 to 5,
The at least one processor 120,
Based on identifying an event associated with the start of an idle mode, identify at least one external electronic device (411; 421) with which communication can be connected,
Based on establishing communication with the at least one external electronic device (411; 421), obtain file hashes for one or more files from the at least one external electronic device (411; 421),
Based on the obtained file hashes, identify at least one file that contains the same file information as a file stored in the at least one external electronic device (411; 421) and has different metadata,
Based on confirming an event related to the end of the idle mode, displaying a notification regarding a change in metadata for the confirmed at least one file through the display module 160, and
Based on the user input for the notification regarding the change of the metadata, the metadata of the confirmed at least one file is the metadata of the file with the same file information stored in the at least one external electronic device (411; 421). Electronic device (101), configured to change metadata of the at least one identified file to match data.
The method according to any one of claims 1 to 6,
The metadata includes at least one of the latitude and longitude at which the file was created, or the date on which the file was created.
The method according to any one of claims 1 to 7,
The at least one processor 120,
The electronic device (101) is configured to confirm that the metadata is damaged based on confirming that at least one of latitude, longitude, or date included in the metadata is lost.
The method according to any one of claims 1 to 8,
The request for metadata corresponding to the file includes a file size and a file hash for the file.
The method according to any one of claims 1 to 9,
The request for metadata corresponding to the file includes, when the file is a resolution-converted file, the file size and file hash of the original file for the file.
In a method for recovering damaged metadata of an electronic device 101,
An operation to check whether metadata of a file acquired from the external electronic device 401 is damaged;
Based on confirmation that the metadata is damaged, confirming at least one external electronic device (411; 421) connectable to the electronic device (101);
An operation of requesting metadata corresponding to the file from the at least one external electronic device (411; 421) through the communication module 190, based on confirming the at least one external electronic device (411; 421). ;
Through the communication module 190, metadata corresponding to the file acquired by the at least one external electronic device 411; 421 is transmitted to the at least one external electronic device 411; 421 based on the request. The operation of receiving from; and
A method including storing the received metadata in memory 130.
According to claim 11,
An operation of displaying an acquisition notification (610) of the file through the display module (160);
An operation of displaying an object 620 regarding whether the metadata is modified through the display module 160 based on a user input for the acquisition notification 610; and
An operation of changing metadata for the acquired file with undamaged metadata received from the at least one external electronic device (411; 421) based on a user input for the object 620 regarding whether or not to modify. A method further comprising:
The method of claim 11 or 12,
Based on identifying an event related to the start of an idle mode, identifying one or more files including the same file information and having different metadata;
Obtaining a file list 920 including the identified one or more files;
Based on confirming an event related to the end of the idle mode, displaying a notification 910 regarding the file list 920 through the display module 160; and
The method further includes changing at least some metadata among one or more files included in the file list 920 based on a user input to the notification 910 regarding the file list 920.
The method according to any one of claims 11 to 13,
The operation of checking one or more files that contain the same file information and have different metadata,
A method comprising confirming that the one or more files with different metadata contain the same file information, based on confirming that the file size and file hash are the same.
The method according to any one of claims 11 to 14,
The operation of changing at least some metadata among one or more files included in the file list 920,
An operation of selecting files containing the same file information from the file list 920 based on a user input in response to a notification 910 regarding the file list 920;
An operation of displaying one or more options (931a; 931b; 931c) for changing metadata for files (921a; 921b; 921c; 921d) including the same file information through the display module (160); and
Based on the user input for one of the one or more options (931a; 931b; 931c), the metadata of the files (921a; 921b; 921c; 921d) containing the same file information are matched, A method comprising changing metadata for files (921a; 921b; 921c; 921d) including the same file information.
The method according to any one of claims 11 to 15,
Based on confirming an event related to the start of an idle mode, identifying at least one external electronic device (411; 421) with which communication can be established;
Obtaining file hashes for one or more files from the at least one external electronic device (411; 421) based on establishing a communication connection with the at least one external electronic device (411; 421);
Based on the obtained file hashes, confirming at least one file containing the same file information as a file stored in the at least one external electronic device (411; 421) and having different metadata;
Based on confirming an event related to the end of an idle mode, displaying a notification regarding a change in metadata for the confirmed at least one file through the display module 160; and
Based on the user input for the notification regarding the change of the metadata, the metadata of the confirmed at least one file matches the metadata of the same file as the file information stored in the at least one external electronic device, The method further includes changing metadata of the at least one identified file.
The method according to any one of claims 11 to 16,
The metadata includes at least one of the latitude and longitude at which the file was created, or the date at which the file was created.
The method according to any one of claims 11 to 17,
The operation of checking whether the metadata is damaged is:
A method comprising confirming that the metadata is damaged based on confirming that at least one of latitude, longitude, or date included in the metadata is lost.
The method according to any one of claims 11 to 18,
The method of claim 1, wherein the request for metadata corresponding to the file includes a file size and a file hash for the file.
The method according to any one of claims 11 to 19,
The request for metadata corresponding to the file includes, when the file is a file whose resolution has been converted, the file size and file hash of the original file for the file.

Images