WO2024219801A2 - Dispositif électronique et procédé de suppression de fichier de données d'application dans un dispositif électronique - Google Patents

Dispositif électronique et procédé de suppression de fichier de données d'application dans un dispositif électronique Download PDF

Info

Publication number
WO2024219801A2
WO2024219801A2 PCT/KR2024/005116 KR2024005116W WO2024219801A2 WO 2024219801 A2 WO2024219801 A2 WO 2024219801A2 KR 2024005116 W KR2024005116 W KR 2024005116W WO 2024219801 A2 WO2024219801 A2 WO 2024219801A2
Authority
WO
WIPO (PCT)
Prior art keywords
application
electronic device
application data
data file
processor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2024/005116
Other languages
English (en)
Korean (ko)
Other versions
WO2024219801A3 (fr
Inventor
최재호
소현빈
신석환
윤광혁
최형호
한원정
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020230062400A external-priority patent/KR20240153871A/ko
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of WO2024219801A2 publication Critical patent/WO2024219801A2/fr
Publication of WO2024219801A3 publication Critical patent/WO2024219801A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers

Definitions

  • Various embodiments of the present disclosure relate to an electronic device and a method of operating the same, and more particularly, to a method for deleting an application data file in an electronic device.
  • electronic devices include a central processing unit (CPU) and memory, and can execute programs (e.g., application programs) stored in the memory through the central processing unit.
  • the central processing unit may include a processor.
  • the memory may store data files associated with the application program.
  • the processor of the electronic device can execute or process at least one application program (hereinafter also referred to as an 'application').
  • the processor of the electronic device can create and/or store in memory a data file (hereinafter also referred to as an 'application data file') associated with the application while executing or processing the application.
  • the processor of the electronic device can store the application data file in an application area (e.g., an app-private area) or a shared area (e.g., a shared storage).
  • the application area can be a storage area accessible through the application, and the shared area can be a storage area accessible not only to the application but also to other programs (or other applications) other than the application.
  • the processor of the electronic device can store the application data file in the application area if the application data file is a data file used only by the application, and can store the application data file in the shared area if the application data file to be stored is a file to be shared.
  • the processor of the electronic device can also create the application data file as a hidden file or store it in the shared area with a deep directory path even though the application data file is a data file used only by the application so that the application can use it.
  • application data files stored in the shared area are not deleted even after the application is deleted, the application data files stored in the shared area may be hidden or have a deep directory path, making them difficult for users to use and may exist as meaningless data files that only take up storage space.
  • an electronic device may include a display, a memory, and a processor operatively connected to the display and the memory.
  • the memory may store instructions that, when executed, cause the processor to identify at least one application data file corresponding to a deleted application among data files stored in a shared area of the memory.
  • the memory may store instructions that, when executed, cause the processor to delete an application data file of a designated type if an application data file of a designated type exists among the at least one application data file.
  • the memory may store instructions that, when executed, cause the processor to display, on the display, information for confirming whether to delete an application data file of a non-designated type if an application data file of a non-designated type exists among the at least one application data file.
  • the memory may store instructions that, when executed, cause the processor to delete or maintain an application data file of a non-designated type based on a response to the information.
  • a method for deleting an application data file in an electronic device may include an operation of identifying at least one application data file corresponding to a deleted application among data files stored in a shared area of a memory of the electronic device.
  • the method according to one embodiment may include an operation of deleting an application data file of a specified type if an application data file of a specified type exists among the at least one application data file.
  • the method according to one embodiment may include an operation of displaying information for confirming whether to delete an application data file of a non-specified type on a display of the electronic device if an application data file of a non-specified type exists among the at least one application data file.
  • the method according to one embodiment may include an operation of deleting or maintaining an application data file of a non-specified type based on a response to the information.
  • a nonvolatile storage medium storing commands
  • the commands when executed by an electronic device, are set to cause the electronic device to perform at least one operation
  • the at least one operation may include: identifying at least one application data file corresponding to a deleted application among data files stored in a shared area of a memory of the electronic device; deleting an application data file of a specified type if an application data file of the specified type exists among the at least one application data file; displaying information confirming whether to delete an application data file of a type other than the specified type if an application data file of a type other than the specified type exists among the at least one application data file, on a display of the electronic device; and deleting or maintaining the application data file of the type other than the specified type based on a response to the information.
  • the application data file that does not exist may be notified to the user and the user may delete the file at his/her option.
  • FIG. 1 is a block diagram of an electronic device within a network environment according to one embodiment.
  • FIG. 2A is a block diagram of an electronic device according to one embodiment.
  • FIG. 2b is a diagram illustrating a storage area of a memory according to one embodiment.
  • FIG. 3 is a flowchart illustrating an application data file deletion operation in an electronic device according to one embodiment.
  • FIG. 4 is a flowchart illustrating an operation of deleting an application data file when deleting an application in an electronic device according to one embodiment.
  • FIG. 5 is a flowchart illustrating an operation of an electronic device deleting an application data file in an idle state according to one embodiment.
  • FIG. 6 is a flowchart illustrating an operation of an electronic device deleting an application data file stored in an external electronic device when the external storage device is connected according to one embodiment.
  • FIG. 7A is a diagram illustrating information displayed on a display when an application is deleted in an electronic device according to one embodiment.
  • FIG. 7b is a diagram showing information for confirming whether an application data file is deleted according to one embodiment.
  • FIG. 8A is a diagram illustrating information displayed on a display when an electronic device according to one embodiment of the present invention identifies application data files for an application that has been deleted in an idle state.
  • FIG. 10 is a diagram showing information for checking whether to delete an application data file for a deleted application among the data files of the SD card when the SD card is connected to an electronic device according to one embodiment of the present invention.
  • FIG. 1 is a block diagram of an electronic device (101) within a network environment (100) according to one embodiment.
  • the processor (120) may control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing, for example, software (e.g., a program (140)), and may perform various data processing or calculations.
  • the processor (120) may store a command or data received from another component (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the command or data stored in the volatile memory (132), and store result data in a non-volatile memory (134).
  • the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) (e.g., a graphic processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together therewith.
  • a main processor (121) e.g., a central processing unit or an application processor
  • an auxiliary processor (123) e.g., a graphic processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor
  • the secondary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a given function.
  • the secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.
  • the auxiliary processor (123) may control at least a part of functions or states associated with 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)), for example, while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state.
  • the auxiliary processor (123) e.g., an image signal processor or a communication processor
  • the auxiliary processor (123) may include a hardware structure specialized for processing an artificial intelligence model.
  • the artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, in the electronic device (101) itself on which the artificial intelligence model is executed, or may be performed through a separate server (e.g., server (108)).
  • the learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above.
  • the artificial intelligence model may include a plurality of artificial neural network layers.
  • the artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), deep Q-networks, or a combination of two or more of the above, but is not limited to the examples described above.
  • the artificial intelligence model may additionally or alternatively include a software structure.
  • the memory (130) can store various data used by at least one component (e.g., processor (120) or sensor module (176)) of the electronic device (101).
  • the data can include, for example, software (e.g., program (140)) and input data or output data for commands related thereto.
  • the memory (130) can include volatile memory (132) or nonvolatile memory (134).
  • the program (140) may be stored as software in memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).
  • the input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101).
  • the input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).
  • the audio output module (155) can output an audio signal to the outside of the electronic device (101).
  • the audio output module (155) can include, for example, a speaker or a receiver.
  • the speaker can be used for general purposes such as multimedia playback or recording playback.
  • the receiver can be used to receive an incoming call. According to one embodiment, the receiver can be implemented separately from the speaker or as a part thereof.
  • the display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101).
  • the display module (160) can include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device.
  • the display module (160) can include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.
  • the audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can obtain sound through an input module (150), or output sound through an audio output module (155), or an external electronic device (e.g., an electronic device (102)) (e.g., a speaker or a headphone) directly or wirelessly connected to the electronic device (101).
  • an electronic device e.g., an electronic device (102)
  • a speaker or a headphone directly or wirelessly connected to the electronic device (101).
  • the sensor module (176) can detect an operating state (e.g., power or temperature) of the electronic device (101) or an external environmental state (e.g., user state) and generate an electric signal or data value corresponding to the detected state.
  • the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.
  • the interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)).
  • 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.
  • HDMI high definition multimedia interface
  • USB universal serial bus
  • SD card interface Secure Digital Card
  • connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., the electronic device (102)).
  • the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).
  • the haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that a user can perceive through a tactile or kinesthetic sense.
  • the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.
  • the battery (189) can power at least one component of the electronic device (101).
  • the battery (189) can include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.
  • the communication module (190) may support establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., the electronic device (102), the electronic device (104), or the server (108)), and performance of communication through the established communication channel.
  • the communication module (190) may operate independently from the processor (120) (e.g., the application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication.
  • the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module).
  • a wireless communication module (192) e.g., a cellular communication module, a short-range wireless communication module, or a GNSS (global navigation satellite system) communication module
  • a wired communication module (194) e.g., a local area network (LAN) communication module, or a power line communication module.
  • a corresponding communication module may communicate with an external electronic device (104) via 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., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)).
  • a first network (198) e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)
  • a second network (199) e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)
  • a computer network e.g.,
  • the wireless communication module (192) may use subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196) to identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199).
  • subscriber information e.g., international mobile subscriber identity (IMSI)
  • IMSI international mobile subscriber identity
  • the wireless communication module (192) can support a 5G network and next-generation communication technology after a 4G network, for example, NR access technology (new radio access technology).
  • the NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), terminal power minimization and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable and low-latency communications
  • the wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate.
  • a high-frequency band e.g., mmWave band
  • the wireless communication module (192) may support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna.
  • the wireless communication module (192) may support various requirements specified in an electronic device (101), an external electronic device (e.g., an electronic device (104)), or a network system (e.g., a second network (199)).
  • the wireless communication module (192) may support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL) each, or 1 ms or less for round trip) for URLLC realization.
  • a peak data rate e.g., 20 Gbps or more
  • a loss coverage e.g., 164 dB or less
  • U-plane latency e.g., 0.5 ms or less for downlink (DL) and uplink (UL) each, or 1 ms or less for round trip
  • the antenna module (197) can transmit or receive signals or power to or from the outside (e.g., an external electronic device).
  • the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB).
  • the antenna module (197) may include a plurality of antennas (e.g., an array antenna).
  • 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) may be selected from the plurality of antennas by, for example, the communication module (190).
  • a signal or power may be transmitted or received between the communication module (190) and the external electronic device through the selected at least one antenna.
  • another component e.g., a radio frequency integrated circuit (RFIC)
  • RFIC radio frequency integrated circuit
  • the antenna module (197) can form a mmWave antenna module.
  • the mmWave antenna module can include a printed circuit board, an RFIC positioned on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) positioned on or adjacent a second side (e.g., a top side or a side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band.
  • a first side e.g., a bottom side
  • a plurality of antennas e.g., an array antenna
  • At least some of the above components may be connected to each other and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).
  • peripheral devices e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).
  • a command or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199).
  • Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101).
  • all or part of the operations executed 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) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of executing the function or service by itself or in addition, request one or more external electronic devices to perform at least a part of the function or service.
  • One or more external electronic devices that have received the request may execute at least a 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 provide the result, as is or additionally processed, as at least a part of a response to the request.
  • cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example.
  • the electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example.
  • the external electronic device (104) may include an IoT (Internet of Things) device.
  • the server (108) may be an intelligent server using machine learning and/or a neural network.
  • the external electronic device (104) or the server (108) may be included in the second network (199).
  • the electronic device (101) can 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. 2A is a block diagram of an electronic device according to one embodiment.
  • an electronic device (201) according to an embodiment may include a processor (220), a memory (230), a display (260), and/or a communication circuit (290).
  • the electronic device (201) according to an embodiment is not limited thereto and may be configured to further include various components or to exclude some of the components.
  • the electronic device (201) according to an embodiment may further include all or part of the electronic device (101) illustrated in FIG. 1.
  • a processor (220) may include an application processor (AP) and/or a central processing unit (CPU).
  • the processor (220) may generate and/or obtain a data file (hereinafter, also referred to as an 'application data file') associated with an application when executing, processing, or installing an application, and store the data file in the memory (230).
  • the processor (220) may store the application data file in an application area (e.g., app-private area) or a shared area (e.g., shared storage).
  • the application area may be a storage area accessible through the application, and the shared area may be a storage area that may be shared not only by the application but also by other programs (or other applications) other than the application.
  • the processor (220) may store an application data file designated to be stored in the application area in the application area, and may store an application data file not designated to be stored in the application area in the shared area.
  • the processor (220) may store file owner (or application data file creator or application name that created the application data file) information corresponding to each of at least one application data file stored in a shared area of the memory (230).
  • the processor (220) may store an owner package name (owner_package_name) as file owner information corresponding to an application data file stored in a shared area of the memory (230) in a database using a designated program (or a program that manages access to the shared area) (e.g., a media provider).
  • owner_package_name an owner package name
  • a designated program or a program that manages access to the shared area
  • a processor (220) may call a Method of a media provider in a file system when generating an application data file at the request of an application.
  • the processor (220) may store an owner package name (owner_package_name) as file owner information corresponding to the application data file being generated in a database using the Method of the media provider. If the application has a bypass (or skip) right for storing information of the application data file, the processor (220) may perform a scan request for a shared area (234) to the media provider after completing storing the application data file, and according to the scan result for the shared area (234), file information for the application data file stored in the stored shared area (234) in the database may be stored without the file owner information.
  • a database may include information such as Table 1 below as file information for each data file stored in a shared area.
  • the processor (220) may store file information for each of all data files stored in the shared area, and the file information for each of the data files stored in the shared area may include application file information corresponding to the application data file.
  • the application data file information may include an ID (_id) of the application data file, a storage path (or directory) and name (_data) of the application data file, a size (_size) of the application data file, a storage date (data_added) of the application data file, and an owner package name (owner_package_name) of the application data file may or may not be included.
  • the processor (220) may perform a shared area scan request based on application identification information (e.g., uid or package name of the application) to the mediaprovider when it is impossible to acquire application file information corresponding to an application data file stored in a shared area or when the owner package name (owner_package_name) of the application data file stored in the shared area does not exist (is null).
  • the processor (220) may store application identification information (e.g., uid or package name of the application) in the owner package name (owner_package_name) of the application data file based on the shared area scan result of the media provider by the shared area scan request.
  • the processor (220) when the processor (220) stores an application data file in a shared area, if the file owner information is not stored, the processor (220) may perform a shared area scan upon reboot and store application identification information (e.g., the uid or package name of the application) in the owner package name (owner_package_name) of the application data file in the database based on the scan result.
  • application identification information e.g., the uid or package name of the application
  • owner_package_name owner package name
  • the processor (220) may use a separate file owner information database instead of using a database using a program (e.g., media provider) that manages access to a shared area of the memory (230).
  • the processor (220) may store the id and file owner information of an application data file in the file owner information database.
  • the processor (220) may store the id and file owner information (e.g., application name) of an application in the file owner information database through a command (e.g., ACTION_PACKAGE_ADDED intent) when installing (or storing) an application.
  • the processor (220) may store (or insert) the same id (and/or file owner information) as the id stored in the file owner information database when creating an application data file into metadata of the application data file.
  • the processor (220) can identify at least one application data file corresponding to a deleted application by using file owner information corresponding to each of at least one application data file stored in a shared area of the memory (230).
  • the processor (220) may obtain first application identification information corresponding to the first application when deleting the first application (or after deleting it) and identify at least one application data file corresponding to the first file owner information that is identical to the first application identification information among file owner information corresponding to at least one application data file stored in the shared area.
  • the processor (220) may store an application deletion history including application identification information of an application that was installed in the electronic device (201) and then deleted. According to one embodiment, the processor (220) may add the first application identification information to the application deletion history when deleting (or after deleting) the first application. According to one embodiment, the processor (220) may identify at least one application data file corresponding to the first file owner information that is identical to the first application identification information included in the application deletion history among the file owner information corresponding to at least one application data file stored in the shared area.
  • the processor (220) may identify an application existing (or installed) in the electronic device (201) using a designated program (e.g., a package manager of Android) when a designated condition is satisfied or at designated time intervals in an idle state, and may identify at least one application data file corresponding to an application that does not exist (or is not installed or deleted) among data files stored in a shared area using a database.
  • a designated program e.g., a package manager of Android
  • the processor (220) may identify an application existing (or installed) in the electronic device (201) and read the application deletion history when a specified condition is satisfied in an idle state or at specified time intervals.
  • the processor (220) may identify at least one application data file corresponding to the application identification information that is not existing in the electronic device (201) and has been deleted among data files stored in a shared area by using the application identification information of the application existing in the electronic device (201) and the application identification information existing in the application deletion history.
  • the idle state may include a sleep state, a state in which there is no user input for a specified period of time or a state in a low power mode.
  • a state satisfying a specified condition in the idle state may include a state in which the electronic device is being charged in the idle state and the user does not use the electronic device for a specified period of time (e.g., 75 minutes) or longer.
  • the processor (220) may generate a trigger when the electronic device is being charged in the idle state and the user does not use the electronic device for a specified period of time (e.g., 75 minutes) or longer.
  • the processor (220) may identify at least one application data file corresponding to an application that does not exist (or is not installed or deleted) in the electronic device (201) among the data files stored in the external storage device by using metadata of each of the data files stored in the external storage device.
  • an external storage device e.g., an external memory (138) of FIG. 1
  • the processor (220) may identify at least one application data file corresponding to an application that does not exist (or is not installed or deleted) in the electronic device (201) among the data files stored in the external storage device by using metadata of each of the data files stored in the external storage device.
  • the processor (220) may receive file information for each of the received data files together, and identify at least one application data file corresponding to an application that does not exist in the electronic device (201) (or is not installed or deleted) among the received data files based on the file information.
  • the external server may store information on an application that frequently (a specified number of times or more) uses a specific application data file stored in a shared area.
  • a processor (220) may identify whether each of at least one application data file corresponding to a deleted application is of a designated type.
  • the designated type may include a hidden file type, a file type having a storage path longer than a designated length (or a file type having a deep directory structure), a file type having a designated extension, a type designated to be deleted immediately without deletion confirmation, or a type excluding a file type with high utilization (e.g., image, video, audio, text, or document).
  • a processor (220) may delete an application data file from a shared area if the type of the application data file corresponding to the deleted application is a specified type.
  • the processor (220) may output information for confirming whether the application data file is deleted if the type of the application data file corresponding to the deleted application is not a designated type. According to an embodiment, the processor (220) may identify an application data file corresponding to (or associated with) the deleted application but is not a designated type. According to an embodiment, the processor (220) may also output information for confirming whether the application data file is deleted for some files that satisfy a designated condition among application data files corresponding to (or associated with) the deleted application but are not a designated type.
  • some files that satisfy a designated condition may include application data files received (or provided) via the cloud (e.g., from an external server) or from an external memory, or application data files that have not been accessed by the processor (220) or have been accessed less than a designated number of times.
  • a processor (220) may classify a plurality of application files based on a specified condition (e.g., file type (e.g., image, video, audio, text, or document)) or priority when there are multiple application files that are not of a specified type, and output a list of classified application files and information for confirming whether an application data file in the list of classified application files has been deleted.
  • a specified condition e.g., file type (e.g., image, video, audio, text, or document)
  • priority e.g., image, video, audio, text, or document
  • priority e.g., image, video, audio, text, or document
  • the processor (220) may display a message for confirming whether an application data file has been deleted through a display (260) or output a sound for confirming whether an application data file has been deleted through a speaker (e.g., an audio output module (155) of FIG. 1).
  • the processor (220) can delete or maintain an application data file based on a response on whether to delete the application data file corresponding to the deleted application.
  • the processor (220) can delete or maintain an application data file to be deleted based on a user deletion selection input (e.g., touch input or voice input) of the application data file or no user selection input or a non-deletion selection input.
  • a user deletion selection input e.g., touch input or voice input
  • the memory (230) may provide a storage space for performing operations or storing data in the processor (220).
  • the data may include, for example, software (e.g., a program (140) of FIG. 1 (e.g., an operating system (142), a middleware (144), or an application (146))) and input data or output data for commands related thereto.
  • the memory (230) may include volatile memory or non-volatile memory.
  • the memory (230) may include an application area (e.g., an app-private area), a shared area (e.g., shared storage), and may further include a preference area and/or a database area.
  • a display (260) may visually provide information to an outside of the electronic device (201) (e.g., a user).
  • the display (260) may display information for confirming whether an application data file has been deleted if the type of an application data file corresponding to a deleted application is not a designated type based on the control of the processor (220).
  • a communication circuit (290) may perform communication with an external electronic device (e.g., an external server (or cloud server)) of the electronic device (201).
  • the communication circuit (290) may receive an application data file (or application data files) and file information about the application data file from the external electronic device through communication.
  • FIG. 2b is a diagram illustrating a storage area of a memory according to one embodiment.
  • a memory (230) may include an application area (e.g., an app-private area) (232), a shared area (e.g., a shared area) (234), a preference area (236), and a database area (238).
  • an application area e.g., an app-private area
  • a shared area e.g., a shared area
  • a preference area e.g., a preference area
  • database area e.g., a database area
  • the application area (232) can store application data files that are only available through the application.
  • the processor (220) according to one embodiment can store application data files that are only available through the application among the application data files generated and/or acquired when executing, processing, or installing the application in the application area (232).
  • the processor (220) according to one embodiment can delete the application data files stored in the application area (232) based on the deletion (or uninstallation) of the application.
  • the shared area (234) may store application data files that can be commonly used by not only the application but also other programs (or other applications) other than the application.
  • the processor (220) may store application data files that are commonly used among application data files generated and/or acquired when executing, processing, or installing an application in the shared area (234), or may store application data files received from an external server (e.g., a cloud server) via the communication circuit (290) in the shared area (234).
  • the shared area (234) may be a storage area of an external storage device (e.g., an external memory (138) of FIG. 1) (e.g., an SD card) identified by the processor (220) by mounting (or inserting or connecting), and may store at least one application data file corresponding to an application that does not exist in the electronic device (201) (or has not been installed or deleted).
  • the processor (220) may identify at least one application data file corresponding to the deleted application by using file owner information corresponding to each of at least one application data file stored in the shared area (234). According to an embodiment, the processor (220) may identify whether the type of each of at least one application data file corresponding to the deleted application is a designated type, and if the type of the application data file corresponding to the deleted application is a designated type, the processor (220) may delete the application data file from the shared area (234).
  • the processor (220) may output information for confirming whether the application data file is to be deleted, and may delete or maintain the application data file based on a response (e.g., a user's deletion selection input or a user's non-deletion selection input) for determining whether the application data file corresponding to the deleted application is to be deleted.
  • a response e.g., a user's deletion selection input or a user's non-deletion selection input
  • the preference area (236) can store application-related key-value pairs.
  • the preference area (236) according to one embodiment can store application setting information, such as a basic welcome greeting or text font that should be loaded whenever the application is executed.
  • the processor (220) according to one embodiment can use the information stored in the preference area (236) when the application is executed, and can delete information corresponding to the deleted application among the information in the preference area (236) based on the deletion (or uninstallation) of the application.
  • the database area (238) may store a database including file information for each of the application data files.
  • the processor (220) may store a database including application file information corresponding to an application data file stored in a shared area in the database area (238), and update the database when an application data file is created or deleted.
  • the application data file information may include an ID (_id) of the application data file, a storage path (or directory) and name (_data) of the application data file, a size (_size) of the application data file, a storage date (data_added) of the application data file, and an owner package name (owner_package_name) of the application data file.
  • An electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (201) of FIG. 2A) according to an embodiment may include a display (e.g., the display module (160) of FIG. 1 or the display (260) of FIG. 2), a memory (e.g., the memory (130) of FIG. 1 or the memory (230) of FIG. 2), and a processor (e.g., the processor (120) of FIG. 1 or the processor (220) of FIG. 2)) operatively connected to the display and the memory.
  • the memory may store instructions that, when executed, cause the processor to identify at least one application data file corresponding to a deleted application among data files stored in a shared area of the memory.
  • the memory may store instructions that, when executed, cause the processor to delete an application data file of a specified type if an application data file of a specified type exists among the at least one application data file.
  • the memory may store instructions that, when executed, cause the processor to display, on the display, information for determining whether to delete an application data file that is not of the designated type if an application data file that is not of the designated type exists among the at least one application data file.
  • the memory may store instructions that, when executed, cause the processor to delete or maintain an application data file that is not of the designated type based on a response to the information.
  • the shared area may be an area accessible by an application of the electronic device and other programs of the electronic device other than the application.
  • the above-mentioned specified type may include a hidden type or a type whose storage path length is longer than the specified length.
  • the instructions, when executed by the processor, may cause the electronic device to identify at least one application data file corresponding to the deleted application among data files stored in the shared area, using the file owner information.
  • the file owner information may include an owner package name or application identification information.
  • the instructions according to one embodiment when executed by the processor, may cause the electronic device to obtain application identification information corresponding to the deleted application based on deletion of the application, and to identify at least one application data file corresponding to the deleted application based on the file owner information being identical to the application identification information.
  • the instructions according to one embodiment when executed by the processor, may cause the electronic device to obtain application identification information corresponding to the deleted application in an idle state, and to identify at least one application data file corresponding to the deleted application based on the file owner information being identical to the application identification information.
  • the instructions according to one embodiment when executed by the processor, may cause the electronic device to obtain application identification information corresponding to the deleted application based on a connection of an external storage device to the electronic device, obtain file owner information of each of the data files stored on the external storage device using metadata of each of the data files, and identify at least one application data file corresponding to the deleted application based on the file owner information being identical to the application identification information.
  • the electronic device may further include a communication circuit (e.g., the communication module (190) of FIG. 1 or the communication circuit (290) of FIG. 2).
  • the instructions according to one embodiment when executed by the processor, may cause the electronic device to receive the at least one application data file from an external server through the communication circuit and to store the received at least one application data file in the shared area.
  • the instructions according to one embodiment when executed by the processor, may cause the electronic device to classify a plurality of application data files based on a specified condition when there are a plurality of application data files that are not of the specified type, and to display a list indicating groups of the classified application data files on the display.
  • Instructions according to one embodiment when executed by the processor, may cause the electronic device to display an icon on the display for selecting deletion of at least some of the classified application data file groups.
  • FIG. 3 is a flowchart illustrating an application data file deletion operation in an electronic device according to one embodiment.
  • a processor (220) e.g., processor (120) of FIG. 1) of an electronic device (201) (e.g., electronic device (101) of FIG. 1) according to one embodiment may perform at least one operation among operations 310 to 360.
  • the processor (220) may identify at least one application data file corresponding to a deleted application by using file owner information corresponding to each of at least one application data file stored in the shared area (234).
  • the processor (220) may obtain application identification information corresponding to the first application when deleting the first application (or after deleting it) and identify at least one application data file corresponding to the first file owner information that corresponds to or is identical to the application identification information among file owner information corresponding to at least one application data file stored in the shared area.
  • the processor (220) may store an application deletion history including application identification information of an application that was installed in the electronic device (201) and then deleted. According to one embodiment, the processor (220) may add the first application identification information to the application deletion history when deleting (or after deleting) the first application. According to one embodiment, the processor (220) may identify at least one application data file corresponding to the first file owner information that is identical to the first application identification information included in the application deletion history among the file owner information corresponding to at least one application data file stored in the shared area.
  • the processor (220) may identify an application existing (or installed) in the electronic device (201) by using a designated program (e.g., a package manager of Android) when a specified condition is satisfied in an idle state (e.g., when there is no user input for 24 hours) or at specified time intervals, and may identify at least one application data file corresponding to an application that does not exist (or has not been installed or deleted) among data files stored in a shared area by using a database.
  • the processor (220) may identify an application existing (or installed) in the electronic device (201) by using a specified condition or at specified time intervals in an idle state, and may read an application deletion history.
  • the processor (220) may identify at least one application data file corresponding to application identification information that does not exist in the electronic device (201) and has been deleted among data files stored in a shared area by using application identification information of an application existing in the electronic device (201) and application identification information existing in the application deletion history.
  • the processor (220) may use metadata of each of the data files stored in the external storage device to identify at least one application data file corresponding to an application that does not exist in the electronic device (201) (or is not installed or deleted) among the data files stored in the external storage device.
  • an external storage device e.g., an external memory (138) of FIG. 1
  • the processor (220) may use metadata of each of the data files stored in the external storage device to identify at least one application data file corresponding to an application that does not exist in the electronic device (201) (or is not installed or deleted) among the data files stored in the external storage device.
  • the processor (220) when the processor (220) receives a data file (or data files) from an external server (e.g., a cloud server) through the communication circuit (290), the processor (220) may receive file information on each of the received data files together, and identify at least one application data file corresponding to an application that does not exist in the electronic device (201) (or is not installed or deleted) among the received data files based on the file information.
  • an external server e.g., a cloud server
  • the processor (220) may receive file information on each of the received data files together, and identify at least one application data file corresponding to an application that does not exist in the electronic device (201) (or is not installed or deleted) among the received data files based on the file information.
  • the processor (220) may identify whether each of the at least one application data files corresponding to the deleted application is of a designated type.
  • the designated type may include a hidden file type, a file type having a storage path length longer than a designated length (or a file type having a deep directory structure), a file type having a designated extension, a type designated to be deleted immediately without deletion confirmation, or a type excluding a file type with high utilization (e.g., image, video, audio, text, or document).
  • the processor (220) may delete an application data file of a specified type from a shared area (234) if the type of the application data file corresponding to the deleted application is a specified type.
  • the processor (220) may output information for confirming whether the application data file is deleted if the type of the application data file corresponding to the deleted application is not a designated type.
  • the processor (220) may classify a plurality of application files based on designated conditions (e.g., file types (e.g., image, video, audio, text, or document) or priorities) if there are multiple application files that are not a designated type, and output a list of classified application files and information for confirming whether an application data file in the classified application file list is deleted.
  • designated conditions e.g., file types (e.g., image, video, audio, text, or document) or priorities
  • the processor (220) may display a message for confirming whether the application data file is deleted through the display (260) or output a sound for confirming whether the application data file is deleted through a speaker (e.g., the sound output module (155) of FIG. 1).
  • the processor (220) can delete or maintain the application data file based on a response on whether to delete the application data file corresponding to the deleted application.
  • the processor (220) can delete or maintain the application data file to be deleted based on a user deletion selection input (e.g., touch input or voice input) or a user non-deletion selection input of the application data file.
  • a method for deleting an application data file in an electronic device may include an operation of identifying at least one application data file corresponding to a deleted application among data files stored in a shared area of a memory of the electronic device.
  • the method may include an operation of deleting an application data file of a specified type if an application data file of the specified type exists among the at least one application data file.
  • the method may include an operation of displaying information for confirming whether to delete an application data file of a type other than the specified type on a display of the electronic device if an application data file of a type other than the specified type exists among the at least one application data file.
  • the method may include an operation of deleting or maintaining an application data file of a type other than the specified type based on a response to the information.
  • the shared area may be an area accessible by an application of the electronic device and another program of the electronic device other than the application.
  • the specified type may include a hidden type or a type whose storage path length is longer than the specified length.
  • the method may include an operation of identifying at least one application existing in the electronic device when a specified condition is satisfied, and reading an application deletion history stored in the electronic device.
  • the method may include an operation of identifying file owner information corresponding to an application that is not present in the electronic device and has been deleted by using the at least one application existing in the electronic device and the application deletion history.
  • the method may include an operation of identifying at least one application data file corresponding to the deleted application among the data files stored in the shared area by using the file owner information.
  • the file owner information may include an owner package name or application identification information.
  • the method according to one embodiment may include an operation of obtaining application identification information corresponding to the deleted application based on deletion of the application.
  • the method according to one embodiment may include an operation of identifying at least one application data file corresponding to the deleted application based on the file owner information and the application identification information being identical.
  • the method according to one embodiment may include an operation of obtaining application identification information corresponding to the deleted application in an idle state.
  • the method according to one embodiment may include an operation of identifying at least one application data file corresponding to the deleted application based on the file owner information and the application identification information being identical.
  • the method according to one embodiment may include an operation of obtaining application identification information corresponding to the deleted application based on a connection of an external storage device to the electronic device.
  • the method according to one embodiment may include an operation of obtaining file owner information of each of the data files stored in the external storage device using metadata of each of the data files.
  • the method according to one embodiment may include an operation of identifying at least one application data file corresponding to the deleted application based on the file owner information and the application identification information being identical.
  • the method according to one embodiment may include an operation of receiving the at least one application data file from an external server via a communication circuit of the electronic device.
  • the method according to one embodiment may include an operation of storing the received at least one application data file in the shared area.
  • the method according to one embodiment may include an operation of classifying a plurality of application data files based on a specified condition when a plurality of application data files that are not of the specified type exist.
  • the method according to one embodiment may include an operation of displaying a list representing the groups of the classified application data files on the display.
  • the method according to one embodiment may include an operation of displaying an icon for selecting deletion of at least some of the groups of the classified application data files on the display.
  • FIG. 4 is a flowchart illustrating an operation of deleting an application data file when deleting an application in an electronic device according to one embodiment.
  • a processor (220) e.g., processor (120) of FIG. 1) of an electronic device (201) (e.g., electronic device (101) of FIG. 1) according to one embodiment may perform at least one of operations 410 to 460.
  • the processor (220) may delete an application in response to a request for deleting an application and obtain application identification information corresponding to the deleted application.
  • the processor (220) may delete an application in response to a request for deleting an application installed in the electronic device (201) based on a user input or a specified command and obtain application identification information (e.g., id, uid, gid, owner_package_name) corresponding to the deleted application.
  • the processor (220) may receive a notification (e.g., ACTION_PACKAGE_REMOVED intent) from a specified program (e.g., mediaprovider or another application) when the application is deleted to identify the deletion of the application.
  • a notification e.g., ACTION_PACKAGE_REMOVED intent
  • the processor (220) may store application identification information of the deleted application in the application deletion history when the application is deleted. According to one embodiment, the processor (220) may receive a notification from a designated program each time an application is deleted, indicating which application has been deleted. According to one embodiment, the processor (220) may update an application deletion history including application identification information of an application that was installed on the electronic device (201) and then deleted each time an application is deleted.
  • the processor (220) may identify at least one application data file corresponding to the deleted application among the data files stored in the shared area (234) by using the file owner information stored in the database.
  • the processor (220) may identify at least one application data file having the same owner package name (owner_package_name) as the name of the application deleted from the database as the application data file to be deleted based on the reception of the notification regarding the deleted application.
  • the processor (220) may identify whether each of the at least one application data files corresponding to the deleted application is a designated type.
  • the designated type may include a hidden file type, a file type having a storage path length longer than a designated length (or a file type having a deep directory structure), a file type having a designated extension, a type designated to be deleted without deletion permission, or a type excluding a file type with high utilization (e.g., image, video, audio, text, or document).
  • the processor (220) can (immediately or directly) delete an application data file of a specified type from the shared area (234) if the type of the application data file corresponding to the deleted application is a specified type.
  • the processor (220) may output information for confirming whether the application data file is deleted if the type of the application data file corresponding to the deleted application is not a designated type.
  • the processor (220) may classify a plurality of application files based on a designated condition (e.g., file type (e.g., image, video, audio, text, or document) or priority) if there are a plurality of application files that are not a designated type, and output a list of classified application files and information for confirming whether an application data file in the classified application file list is deleted.
  • a designated condition e.g., file type (e.g., image, video, audio, text, or document) or priority
  • the processor (220) may display a message for confirming whether the application data file is deleted through the display (260) or output a sound for confirming whether the application data file is deleted through a speaker (e.g., the sound output module (155) of FIG. 1).
  • the processor (220) may delete or maintain the application data file based on a response as to whether to delete the application data file corresponding to the deleted application.
  • the processor (220) may delete or maintain the application data file to be deleted based on a user deletion selection input (e.g., touch input or voice input) or a user non-deletion selection input of the application data file.
  • the processor (220) may store maintenance information (e.g., is_owner_checked) indicating that the application data file selected to be maintained is the application data file selected to be maintained in the database.
  • the processor (220) may not guide to the application data file to be deleted based on the maintenance information.
  • the processor (220) may receive and set a non-deletion maintenance period of the application data file to be deleted when non-deletion is selected or set a designated period.
  • the processor (220) may delete the target application data file for deletion when the undelete retention period of the target application data file for deletion expires or when a periodic undelete retention period expired file deletion event occurs.
  • the processor (220) may output information notifying the target application data file for deletion whose undelete retention period has expired, and may also delete the target application data file for deletion whose undelete retention period has expired based on a user's deletion request input.
  • FIG. 5 is a flowchart illustrating an operation of an electronic device deleting an application data file in an idle state according to one embodiment.
  • a processor (220) e.g., processor (120) of FIG. 1) of an electronic device (201) (e.g., electronic device (101) of FIG. 1) according to one embodiment may perform at least one of operations 510 to 560.
  • the processor (220) may obtain application identification information corresponding to an application deleted in an idle state.
  • the processor (220) may use a specified program (e.g., a package manager of Android) to identify applications (e.g., a list of installed applications) existing (or installed) in the electronic device (201) when a specified condition is satisfied in the idle state (e.g., a 24-hour cycle in the idle state, or when there is no user input for a specified time, or when charging or when other conditions are satisfied), and may identify file owner information (e.g., metadata of a file or an owner package name (owner_package_name) of a database) corresponding to an application that does not exist (or is not installed or deleted) among data files stored in the shared area (234).
  • a specified program e.g., a package manager of Android
  • the processor (220) may identify at least one application (e.g., an installed application list) existing (or installed) in the electronic device (201) by using a designated program when a designated condition is satisfied in an idle state, and may read an application deletion history for at least one application deleted from the electronic device (201).
  • the processor (220) may identify file owner information (e.g., metadata of a file or an owner package name (owner_package_name) of a database) corresponding to an application that does not exist among data files stored in a shared area (234) by using application identification information of an application existing in the electronic device (201) and application identification information existing in the application deletion history.
  • the processor (220) may identify at least one application data file corresponding to a deleted application among data files stored in the shared area (234) using file owner information.
  • the processor (220) may identify whether each of the at least one application data files corresponding to the deleted application is of a designated type.
  • the designated type may include a hidden file type, a file type having a storage path length longer than a designated length (or a type of file having a deep directory structure), a file type having a designated extension, a type designated to be deleted without deletion permission, or a type excluding a file type with high utilization (e.g., image, video, audio, text, or document).
  • the processor (220) can (immediately or directly) delete an application data file of a specified type from the shared area (234) if the type of the application data file corresponding to the deleted application is a specified type.
  • the processor (220) may output information for confirming whether the application data file is deleted when the idle state is released if the type of the application data file corresponding to the deleted application is not a designated type.
  • the processor (220) may classify a plurality of application files based on a designated condition (e.g., file type (e.g., image, video, audio, text, or document) or priority) when there are a plurality of application files that are not a designated type, and output a list of classified application files and information for confirming whether the application data file in the classified application file list is deleted.
  • a designated condition e.g., file type (e.g., image, video, audio, text, or document) or priority
  • the processor (220) may display a message for confirming whether the application data file is deleted through the display (260) when the idle state is released, or output a sound for confirming whether the application data file is deleted through a speaker (e.g., the sound output module (155) of FIG. 1).
  • a speaker e.g., the sound output module (155) of FIG. 1.
  • the processor (220) may delete or maintain an application data file based on a response on whether to delete an application data file corresponding to a deleted application in a state where an idle state is released.
  • the processor (220) may delete or maintain a target application data file without deleting it based on a user deletion selection input (e.g., touch input or voice input) or a user non-deletion selection input of the application data file.
  • the processor (220) may update file owner information in a database with a null value for an application data file selected to be maintained, store maintenance information (e.g., is_owner_checked) indicating that the application data file is selected to be maintained, or update the owner information with a null value or insert the maintenance information into a metadata area within the application data file.
  • the processor (220) may not provide (or guide) the target application data file for deletion based on the maintenance information.
  • FIG. 6 is a flowchart illustrating an operation of an electronic device deleting an application data file stored in an external electronic device when the external storage device is connected according to one embodiment.
  • a processor (220) e.g., processor (120) of FIG. 1) of an electronic device (201) (e.g., electronic device (101) of FIG. 1) according to one embodiment may perform at least one of operations 610 to 640.
  • the processor (220) may display a message for confirming whether an application data file is deleted through the display (260) or output a sound for confirming whether an application data file is deleted through a speaker (e.g., an audio output module (155) of FIG. 1).
  • a speaker e.g., an audio output module (155) of FIG. 1.
  • the processor (220) may delete or maintain the application data file based on a response as to whether to delete the application data file corresponding to the deleted application.
  • the processor (220) may delete or maintain the application data file to be deleted based on a user deletion selection input (e.g., touch input or voice input) or a user non-deletion selection input of the application data file.
  • the processor (220) may update the file owner information in the database with a null value for the application data file selected to be maintained, store maintenance information (e.g., is_owner_checked) indicating that the application data file is selected to be maintained, or update the owner information with a null value or insert the maintenance information into a metadata area in the application data file.
  • the processor (220) may not provide (or guide) the application data file to be deleted based on the maintenance information.
  • FIG. 7a is a diagram showing information displayed on a display when an application is deleted in an electronic device according to one embodiment
  • FIG. 7b is a diagram showing information for confirming whether an application data file is deleted according to one embodiment.
  • the processor (220) of an electronic device (201) may display, on a display (260), notification information (710) notifying that there is at least one application data file corresponding to the deleted application among the data files stored in the shared area (234) when an application is deleted.
  • the processor (220) may display information (710) notifying that the application created by “test1” is in the shared area, “internal storage.”
  • the processor (220) may classify the multiple application data files based on a specified condition (e.g., file type (e.g., image, video, audio, text, or document)) or priority, and display information of the multiple classified application data files together as “image:101, Video: 1054, Audio:22, Texts:21, other files:221”.
  • file type e.g., image, video, audio, text, or document
  • image:101, Video: 1054, Audio:22, Texts:21, other files:221 may mean that among the multiple application data files, there are 101 image files, 1054 video files, 22 audio files, 21 text files, and 221 other files.
  • the processor (220) may further display a notification settings menu (notification settings) for setting notifications and/or a menu (clear) for stopping notification display in addition to the notification information (710).
  • the processor (220) may display information (720) for confirming whether to delete an application data file on the display (260) when the notification information (710) for notifying that there is at least one application data file corresponding to a deleted application is selected.
  • the information (720) for confirming whether to delete an application data file may include a list of classified application data file groups (722, 724, 726, 728, 729) and a delete icon for selecting to delete each of the classified application data file groups.
  • the processor (220) may delete all application data files (e.g., 101 images) corresponding to the first application file group (722) based on a user's input for selecting a delete icon corresponding to the first application data file group (722).
  • the processor (220) may display application data files (e.g., 101 images) included in the first application data file group (722) based on a user's input selecting the first application data file group (722) (not shown), and delete a selected application data file (e.g., at least one image selected from the 101 images) among the application data files (e.g., 101 images).
  • the processor (220) may also delete all application data files (e.g., 1054 Videos, 22 Audios, 21 Texts, or 221 files) corresponding to an application file group (724, 726, 728, or 729) based on a user's input selecting a delete icon for each of the other application file groups (724, 726, 728, and 729).
  • a processor (220) may display application data files (e.g., 1054 Videos, 22 Audios, 21 Texts, or 221 files) included in each application data file group (e.g., 724, 726, 728, or 729) based on a user's input for each of the other application file groups (724, 726, 728, and 729) (not shown).
  • a processor (220) may delete a selected application data file (e.g., at least one video file selected from 1054 Videos, at least one audio file selected from 22 Audios, at least one text file selected from 21 Texts, or at least one file selected from 221 files) among the application data files (e.g., 1054 Videos, 22 Audios, 21 Texts, or 221 files).
  • FIG. 8a is a diagram showing information displayed on a display when an electronic device according to one embodiment identifies application data files for an application deleted in an idle state
  • FIG. 8b is a diagram showing information for confirming whether application data files for a deleted application are deleted according to one embodiment.
  • the processor (220) of an electronic device (201) may display, on a display (260), notification information (810) notifying that there is at least one application data file corresponding to a deleted application among the data files stored in the shared area (234) as a result of scanning in an idle state.
  • the processor (220) may classify the multiple application data files based on a specified condition (e.g., file type (e.g., image, video, audio, text, or document) or priority) and display information of the multiple classified application data files together as “image: 1021, Video: 222, Audio: 31, Texts:1532, other files:2231.”
  • image: 1021, Video: 222, Audio: 31, Texts:1532, other files:2231 may mean that among the multiple application data files, there are 1021 image files, 222 video files, 31 audio files, 1532 text files, and 2231 other files.
  • the processor (220) may display a notification setting menu for setting the notification. settings) and/or a menu (clear) to stop displaying notifications.
  • the processor (220) may display, on the display (260), information (820) for confirming whether to delete the application data file when the notification information (810) for notifying that there is at least one application data file corresponding to the deleted application is selected.
  • the information (820) for confirming whether to delete the application data file may include a list of classified application data file groups (822, 824, 826, 828, 829) and a delete icon that can be selected to delete each of the classified application data file groups.
  • the processor (220) may delete all application data files (e.g., 1021 images) corresponding to the first application file group (822) based on a user's input for selecting the delete icon corresponding to the first application data file group (822).
  • the processor (220) may display application data files (e.g., 1021 images) included in the first application data file group (822) based on a user's input selecting the first application data file group (822) (not shown), and delete a selected application data file (e.g., at least one image selected from the 1021 images) among the application data files (e.g., 1021 images).
  • the processor (220) may also delete all application data files (e.g., 1222 Videos, 31 Audios, 1532 Texts, or 2231 files) corresponding to an application file group (824, 826, 828, or 829) based on a user's input selecting a delete icon for each of the other application file groups (824, 826, 828, and 829).
  • all application data files e.g., 1222 Videos, 31 Audios, 1532 Texts, or 2231 files
  • the processor (220) may also display application data files (e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files) included in each application data file group (e.g., 824, 826, 828, or 829) based on a user's input for each of the other application file groups (824, 826, 828, and 829) (not shown).
  • application data files e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files
  • the processor (220) may delete a selected application data file (e.g., at least one video file selected from 222 Videos, at least one audio file selected from 31 Audios, at least one text file selected from 1532 Texts, or at least one file selected from 2231 files) among the application data files (e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files).
  • a selected application data file e.g., at least one video file selected from 222 Videos, at least one audio file selected from 31 Audios, at least one text file selected from 1532 Texts, or at least one file selected from 2231 files.
  • FIG. 9 is a diagram showing information for confirming whether to delete an application data file for a deleted application among data files acquired from an external device by an electronic device according to one embodiment of the present invention.
  • the processor (220) of the electronic device (201) may display information (920) for confirming whether to delete the application data file if there is an application data file for a deleted application among data files acquired from an external device (e.g., an external server or a cloud) on the display (260).
  • the information (920) for confirming whether to delete the application data file may include a list of classified application data file groups (922, 924, 926, 928, 929) and a delete icon that can be selected to delete each of the classified application data file groups.
  • the processor (220) may delete all application data files (e.g., 1021 images) corresponding to the first application file group (922) based on a user's input selecting a delete icon corresponding to the first application data file group (922).
  • a processor (220) may display application data files (e.g., 1021 images) included in a first application data file group (922) based on a user's input selecting a first application data file group (922) (not shown), and delete a selected application data file (e.g., at least one image selected from among the 1021 images) among the application data files (e.g., 1021 images).
  • FIG. 10 is a diagram showing information for checking whether to delete an application data file for a deleted application among the data files of the SD card when an SD card (or memory card or external memory) is connected to an electronic device according to one embodiment of the present invention.
  • the processor (220) of the electronic device (201) may display information (1020) for confirming whether to delete the application data file if there is an application data file for a deleted application among the data files acquired from the SD card on the display (260).
  • the information (1020) for confirming whether to delete the application data file may include a list of classified application data file groups (1022, 1024, 1026, 1028) and a delete icon that can be selected to delete each of the classified application data file groups.
  • the processor (220) may delete all application data files (e.g., 1021 images) corresponding to the first application file group (1022) based on a user's input selecting a delete icon corresponding to the first application data file group (1022).
  • the processor (220) may display application data files (e.g., 1021 images) included in the first application data file group (1022) based on a user's input selecting the first application data file group (1022) (not shown), and delete a selected application data file (e.g., at least one image selected from the 1021 images) among the application data files (e.g., 1021 images).
  • the processor (220) may also delete all application data files (e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files) corresponding to an application file group (1024, 1026, 1028, or 1029) based on a user's input selecting a delete icon for each of the other application file groups (1024, 1026, 1028, and 1029).
  • all application data files e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files
  • the processor (220) can also display application data files (e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files) included in each application data file group (e.g., 1024, 1026, 1028, or 1029) based on a user's input for each of the other application file groups (1024, 1026, 1028, and 1029) (not shown).
  • application data files e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files
  • the processor (220) can delete a selected application data file (e.g., at least one video file selected from 222 Videos, at least one audio file selected from 31 Audios, at least one text file selected from 1532 Texts, or at least one file selected from 2231 files) among the application data files (e.g., 222 Videos, 31 Audios, 1532 Texts, or 2231 files).
  • a selected application data file e.g., at least one video file selected from 222 Videos, at least one audio file selected from 31 Audios, at least one text file selected from 1532 Texts, or at least one file selected from 2231 files.
  • Electronic devices may be devices of various forms.
  • the 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 appliance devices.
  • Electronic devices according to embodiments of the present disclosure are not limited to the above-described devices.
  • each of the phrases “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C” can include any one of the items listed together in the corresponding phrase among the phrases, or all possible combinations thereof.
  • Terms such as “first”, “second”, or “first” or “second” may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order).
  • a component e.g., a first
  • another component e.g., a second
  • the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.
  • module may include a unit implemented in hardware, software or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit.
  • a module may be an integrally configured component or a minimum unit of the component or a part thereof that performs one or more functions.
  • a module may be implemented in the form of an application-specific integrated circuit (ASIC).
  • ASIC application-specific integrated circuit
  • Various embodiments of the present disclosure may be implemented as software (e.g., a program (140)) including one or more commands stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)).
  • a processor e.g., a processor (120)
  • the machine e.g., the electronic device (101)
  • the one or more commands may include code generated by a compiler or code executable by an interpreter.
  • the machine-readable storage medium may be provided in the form of a non-transitory storage medium.
  • 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.
  • the method according to the various embodiments disclosed in the present document may be provided as included in a computer program product.
  • the computer program product may be traded between a seller and a buyer as a commodity.
  • the computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play StoreTM) or directly between two user devices (e.g., smartphones).
  • an application store e.g., Play StoreTM
  • at least a part of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as a memory of a manufacturer's server, a server of an application store, or an intermediary server.
  • each of the components may include a single or multiple entities.
  • one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added.
  • a plurality of components e.g., modules or programs
  • the integrated component may perform one or more functions of each of the components of the plurality of components identically or similarly to those performed by the corresponding component of the plurality of components prior to the integration.
  • the operations performed by the modules, programs or other components may be executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.
  • a non-volatile storage medium storing commands
  • the commands when executed by an electronic device, are set to cause the electronic device to perform at least one operation
  • the at least one operation may include: an operation of identifying at least one application data file corresponding to a deleted application among data files stored in a shared area of a memory of the electronic device; an operation of deleting an application data file of a specified type if an application data file of the specified type exists among the at least one application data file; an operation of displaying information confirming whether to delete an application data file of a type other than the specified type if an application data file of a type other than the specified type exists among the at least one application data file; and an operation of deleting or maintaining an application data file of a type other than the specified type based on a response to the information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Storage Device Security (AREA)
  • Stored Programmes (AREA)

Abstract

Un dispositif électronique selon divers modes de réalisation de la présente divulgation comprend un dispositif d'affichage, une mémoire et un processeur connecté fonctionnellement au dispositif d'affichage et à la mémoire, la mémoire pouvant stocker des instructions configurées de telle sorte que, lors de l'exécution, le processeur : identifie un ou plusieurs fichiers de données d'application correspondant à une application supprimée parmi des fichiers de données stockés dans une zone partagée de la mémoire ; supprime un fichier de données d'application d'un type désigné lorsque le fichier de données d'application du type désigné est présent parmi le ou les fichiers de données d'application ; affiche, sur le dispositif d'affichage, des informations pour vérifier s'il faut supprimer un fichier de données d'application non du type désigné lorsque le fichier de données d'application non du type désigné est présent parmi le ou les fichiers de données d'application ; et supprime ou maintient le fichier de données d'application non du type désigné sur la base de la réponse aux informations.
PCT/KR2024/005116 2023-04-17 2024-04-17 Dispositif électronique et procédé de suppression de fichier de données d'application dans un dispositif électronique Ceased WO2024219801A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR20230050087 2023-04-17
KR10-2023-0050087 2023-04-17
KR10-2023-0062400 2023-05-15
KR1020230062400A KR20240153871A (ko) 2023-04-17 2023-05-15 전자 장치 및 전자 장치에서 어플리케이션 데이터 파일 삭제 방법

Publications (2)

Publication Number Publication Date
WO2024219801A2 true WO2024219801A2 (fr) 2024-10-24
WO2024219801A3 WO2024219801A3 (fr) 2025-06-26

Family

ID=93152817

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/005116 Ceased WO2024219801A2 (fr) 2023-04-17 2024-04-17 Dispositif électronique et procédé de suppression de fichier de données d'application dans un dispositif électronique

Country Status (1)

Country Link
WO (1) WO2024219801A2 (fr)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103246595B (zh) * 2013-04-08 2016-06-08 小米科技有限责任公司 应用程序管理方法、装置、服务器及终端设备
US9652215B2 (en) * 2014-12-30 2017-05-16 Microsoft Technology Licensing, Llc Application installation/uninstallation across multiple systems
KR20190098516A (ko) * 2018-02-14 2019-08-22 삼성전자주식회사 어플리케이션과 관련된 데이터를 관리하기 위한 방법 및 그 전자 장치
KR102738300B1 (ko) * 2019-01-28 2024-12-06 삼성전자주식회사 전자 장치 및 전자 장치의 제어 방법
JP2021165961A (ja) * 2020-04-07 2021-10-14 キヤノン株式会社 端末装置、情報処理方法、及びプログラム

Also Published As

Publication number Publication date
WO2024219801A3 (fr) 2025-06-26

Similar Documents

Publication Publication Date Title
WO2019156411A1 (fr) Dispositif électronique destiné à être connecté à des dispositifs externes sur la base d'informations de connexion et son procédé de fonctionnement
WO2022103019A1 (fr) Dispositif électronique et procédé d'exécution d'application pour dispositif électronique
WO2021150037A1 (fr) Procédé pour fournir une interface utilisateur et dispositif électronique associé
WO2019164204A1 (fr) Dispositif électronique et son procédé de fonctionnement
WO2024219801A2 (fr) Dispositif électronique et procédé de suppression de fichier de données d'application dans un dispositif électronique
WO2023058860A1 (fr) Dispositif électronique pour le traitement d'un fichier apk à signatures multiples, et son procédé de fonctionnement
WO2022211285A1 (fr) Dispositif électronique de gestion de mémoire et procédé de fonctionnement associé
WO2022075621A1 (fr) Dispositif électronique, et procédé de fonctionnement de dispositif électronique
WO2025014158A1 (fr) Dispositif électronique et procédé de gestion de fichiers
WO2022240031A1 (fr) Dispositif électronique et procédé de gestion de fichier de dispositif électronique
WO2025100783A1 (fr) Procédé de notification et dispositif électronique pour la mise en œuvre de ce procédé
WO2024101878A1 (fr) Procédé de récupération de métadonnées endommagées, et dispositif électronique le prenant en charge
WO2025154939A1 (fr) Procédé de transmission de données et dispositif électronique pour sa mise en œuvre
WO2025048115A1 (fr) Dispositif électronique et procédé d'exécution, de stockage et d'affichage d'application
WO2025110490A1 (fr) Dispositif d'utilisateur et procédé d'exécution d'application l'utilisant
WO2026029486A1 (fr) Dispositif électronique et procédé de récupération de csme à l'aide de bios dans un dispositif électronique
WO2022191455A1 (fr) Dispositif électronique pour effectuer une rédaction de fichier et son procédé de fonctionnement
WO2024237712A1 (fr) Dispositif électronique pour le partage de contenu à l'aide d'un code qr et procédé de fonctionnement associé
WO2024172391A1 (fr) Procédé de gestion d'informations relatives à un fichier, et dispositif électronique le prenant en charge
WO2025143752A1 (fr) Dispositif électronique et procédé de restriction de ressource sécurisée l'utilisant
WO2025009886A1 (fr) Dispositif électronique inclus dans un réseau de chaîne de blocs et son procédé de fonctionnement
WO2025258849A1 (fr) Dispositif électronique pour commander les performances d'un processeur sur la base d'un courant déchargé d'une batterie, et procédé mis en œuvre par celui-ci
WO2025080028A1 (fr) Dispositif électronique et procédé de commande de la luminosité d'un écran
WO2026043063A1 (fr) Dispositif électronique, procédé et support de stockage non transitoire lisible par ordinateur permettant d'effectuer une mise à jour de micrologiciel
WO2024232610A1 (fr) Dispositif électronique et procédé de commande de la luminosité d'un écran

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24792986

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 24792986

Country of ref document: EP

Kind code of ref document: A2