Processing methods, smart terminals and storage media

Abstract

This application proposes a processing method, a smart terminal, and a storage medium. The method, applied to a smart terminal, includes: S1, responding to a configuration operation for a target application by not performing a persistent write operation on the data corresponding to the target application. In this way, the smart terminal intelligently identifies configuration operations and intercepts data that does not need to be stored permanently, reducing unnecessary data writes and thereby achieving the goals of reducing power consumption, improving performance, reducing storage space usage, and extending the overall lifespan of the smart terminal.

Description

Technical Field

[0001] This application relates to the field of terminal technology, specifically to a processing method, a smart terminal, and a storage medium. Background Technology

[0002] With the increasing functionality of smart devices (such as smartphones and tablets), the amount of data generated by applications has increased dramatically. A large portion of this data is cached, such as streaming media cache in short video applications, page cache in web browsers, and temporary application files. These cached files are typically only needed briefly while the application is running, and the probability of a user accessing the same content again is extremely low; therefore, they are data that does not need to be stored permanently.

[0003] In conceiving and implementing this application, the inventors discovered at least the following problems: Existing data writing mechanisms in smart terminal systems typically do not distinguish the long-term value of data. File data is usually cached in volatile memory first, and then written to non-volatile memory when specific conditions are met (such as a full buffer or periodic refresh). However, this data writing mechanism leads to increased power consumption, decreased performance, increased space usage, and reduced lifespan for smart terminals.

[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention

[0005] To address the aforementioned technical problems, this application provides a processing method, a smart terminal, and a storage medium, which can reduce power consumption, improve performance, reduce storage space usage, and extend the lifespan of the smart terminal.

[0006] This application provides a processing method applicable to smart terminals, comprising the following steps: S1. In response to the configuration operation for the target application, do not perform a persistent write operation on the data corresponding to the target application.

[0007] Optionally, step S1 includes: Obtain a save operation request for the target data, and in response to the target data belonging to a preset data type of the target application, return an operation success response without writing the target data to non-volatile memory.

[0008] Optionally, the save operation request includes at least one of the following: a file write request and a file update request.

[0009] Optionally, before obtaining the save operation request for the target data, the process includes: In response to the detection that the smart terminal meets the preset triggering conditions, it is determined whether the target data belongs to the preset data type of the target application.

[0010] Optionally, satisfying the preset triggering condition includes at least one of the following: An application of a preset type was detected to be launching. The remaining storage space of the non-volatile memory is lower than a preset storage threshold; The system input or output load of the smart terminal is higher than a preset load threshold. The remaining battery power of the smart terminal is lower than a preset battery power threshold.

[0011] Optionally, determining whether the target data belongs to a preset data type of the target application includes: Analyze the attribute information of the target data to identify the associated applications and data types of the target data; In response to identifying that the associated application of the target data is the target application and the data type is a preset data type, it is determined that the target data belongs to the preset data type of the target application.

[0012] Optionally, the preset data type includes at least one of the following types: application cache data, uninstallation residual data, application installation package data, and system temporary data.

[0013] Optionally, the smart terminal includes a first interface, which includes independent control options for different applications. In response to an operation on the independent control option, a configuration operation for the target application is performed. The independent control option is used to control whether the preset data corresponding to the application does not need to be saved.

[0014] Optionally, the method further includes: The data corresponding to the target application is temporarily stored in a memory-based temporary file system.

[0015] This application also provides a smart terminal, including: a memory and a processor, wherein the memory stores a processing program, and when the processing program is executed by the processor, it implements the above-described processing method.

[0016] This application also provides a storage medium storing a computer program that, when executed by a processor, implements the above-described processing method.

[0017] As described above, the processing method of this application can be applied to smart terminals, including: S1, responding to a configuration operation for a target application, not performing a persistent write operation on the data corresponding to the target application. Through the above technical solution, the smart terminal intelligently identifies configuration operations and intercepts data that does not need to be stored for a long time, reducing unnecessary data writing, thereby achieving the goals of reducing power consumption, improving performance, reducing storage space occupation, and extending the overall lifespan of the smart terminal. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0019] Figure 1 A schematic diagram of the hardware structure of a mobile terminal to implement the various embodiments of this application.

[0020] Figure 2 This is a schematic diagram of a communication network system architecture provided in an embodiment of this application.

[0021] Figure 3 This is a flowchart illustrating a processing method according to one embodiment.

[0022] Figure 4 This is a schematic diagram of a smart terminal interface according to one embodiment. Figure 1 .

[0023] Figure 5 This is a schematic diagram of a smart terminal interface according to one embodiment. Figure 2 .

[0024] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0025] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application.

[0026] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0027] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, type, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0028] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0029] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0030] It should be noted that step designations such as S1 are used in this paper for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial restriction on the order.

[0031] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0032] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0033] Smart terminals can be implemented in various forms. For example, the smart terminals described in this application may include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.

[0034] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminals.

[0035] Please see Figure 1This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0036] The following is combined with Figure 1 A detailed introduction to each component of the mobile terminal: The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, and a duplexer. Furthermore, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G, and 6G.

[0037] WiFi is a short-range wireless transmission technology. Mobile terminals, through the WiFi module 102, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0038] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0039] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0040] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0041] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0042] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, and sends it to processor 110, and can receive and execute commands from processor 110. In addition, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0043] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0044] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0045] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0046] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0047] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0048] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0049] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0050] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is an LTE system based on the universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.

[0051] Optionally, UE201 can be the aforementioned terminal 100, which will not be described in detail here.

[0052] E-UTRAN202 includes eNodeB2021 and other eNodeB2022s. Optionally, eNodeB2021 can connect to other eNodeB2022s via backhaul (e.g., X2 interface). eNodeB2021 connects to EPC203 and can provide UE201 with access to EPC203.

[0053] EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gateway) 2034, a PGW (Packet Data Network Gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as the Home Location Register (not shown in the figure) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).

[0054] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.

[0055] Although the above description uses the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., without limitation.

[0056] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0057] Reference Figure 3 , Figure 3 This is a flowchart illustrating a processing method according to an embodiment of this application. The processing method of this embodiment can be applied to smart terminals (such as mobile phones), and includes the following steps: S1. In response to configuration operations for the target application, do not perform persistent write operations on the data corresponding to the target application.

[0058] Optionally, after the user performs a configuration operation for the target application, the smart terminal will not perform a persistent write operation on the data corresponding to the target application in subsequent operation based on the configuration operation.

[0059] Optionally, configuration operations can be interactive behaviors where users actively set whether data corresponding to a certain application is allowed to undergo persistent write operations through system management applications (such as phone managers) on smart terminals or controls in their application information pages. This operation typically manifests as clicking a switch, checking a checkbox, or sliding a button. The target application refers to the application the user is currently configuring, and it is identified by a unique identifier. The data corresponding to the target application refers to data generated during the target application's operation that the system would normally perform persistent write operations on, such as writing to persistent storage, for example, application cache files (such as video clips, web page resources, thumbnails). A persistent write operation refers to the process of actually writing data to non-volatile storage (such as Flash memory, eMMC, UFS, SSD, etc.), which ensures that the data is retained even after the device is powered off.

[0060] For example, user Zhang San finds that his phone storage space is often insufficient and discovers that the live streaming short video application A is using more than 4GB of cache. Since he does not often watch videos, he configures the live streaming short video application A on his phone to not cache the video data corresponding to the live streaming short video application A. This allows the video data to still play smoothly every time Zhang San watches a video, but the system will no longer write this data to the phone storage.

[0061] Optionally, users can proactively configure whether persistent write operations are required for data corresponding to a target application through the system settings of the smart terminal or system management applications (such as "Phone Manager"). This information is stored in the system in the form of key-value pairs or database records and can be queried in real time. For example, after receiving a write request for data generated by a certain application, the smart terminal first queries the user configuration information to determine whether a persistent write operation needs to be performed on the data corresponding to that application.

[0062] By embedding intelligent identification configuration operations and interception mechanisms into the data writing process, smart terminals transform traditional post-event cleanup into pre-event prevention, achieving the following technical effects: avoiding a large number of unnecessary data writing operations, directly reducing power consumption, i.e., significantly reducing power consumption; reducing the load on the write queue, reducing IO resource contention, making the system response smoother, and improving IO performance; fundamentally preventing useless cached data from occupying persistent storage space, saving storage space; and reducing the number of write / erase cycles of storage units, extending the lifespan of devices.

[0063] Optionally, step S1 includes: Obtain a save operation request for the target data. In response to the target data belonging to the target application's preset data type, return a successful operation response and do not write the target data to non-volatile memory.

[0064] Optionally, after the smart terminal obtains a save operation request for the target data, if it determines that the target data belongs to the preset data type of the target application, it returns a successful operation response to the initiator of the operation request and does not write the target data to the non-volatile memory.

[0065] Optionally, the target data refers to the object to which the save operation request is targeting and the data persistence operation to be performed in the file system of the smart terminal. Non-volatile memory refers to storage media whose data is not lost after power failure, such as Flash memory (including eMMC, UFS, SSD, etc.). The save operation request includes at least one of the following: a file write request or a file update request. A file update request refers to a request to modify the content of an existing file and require persistent saving. Optionally, the save operation request must at least include the identifier of the target file (such as path, file descriptor, etc.) and the data to be operated on. Returning a successful operation response is a technical means of simulating operation completion, enabling the application or system service that initiated the operation request to continue operating normally without reporting errors or hanging due to operation interception.

[0066] For example, when a short video application needs to cache a piece of video data, it sends a file write request to the operating system of the smart terminal. At this point, the video data constitutes a target data. After receiving the request, the operating system of the smart terminal determines whether the target data belongs to the target application's preset data type. If so, it simulates a write operation, that is, it returns a success response to the short video application and does not write the target data to non-volatile memory; otherwise, it writes the target data to non-volatile memory.

[0067] In this way, before file data is written to non-volatile memory, smart terminals can intelligently identify and intercept cached files that do not need to be stored for a long time, reducing unnecessary data writing to non-volatile memory, thereby reducing power consumption and storage space usage for smart terminals.

[0068] Optionally, before obtaining a save operation request for the target data, the process includes: In response to the detection that the smart terminal meets the preset trigger conditions, it is determined whether the target data belongs to the preset data type of the target application.

[0069] Optionally, preset trigger conditions can be set only as needed based on actual circumstances. It is understood that under normal circumstances, smart terminals may adopt default strategies (such as directly executing operation requests or filtering according to simple rules). When a smart terminal is detected to meet preset trigger conditions, such as in a specific scenario, filtering is initiated to determine whether the target data belongs to a preset data type of the target application (such as application cache data, uninstallation residual data, etc.), thereby achieving the optimal balance between power consumption, performance, and data security.

[0070] Thus, when a smart terminal is detected to meet the preset trigger conditions, it can then determine whether the target data belongs to the preset data type of the target application, enabling dynamic and intelligent filtering management and improving the flexibility and practicality of management.

[0071] Optionally, the preset trigger conditions include at least one of the following: An application of a preset type was detected to be launching. The remaining storage space of the non-volatile memory is lower than a preset storage threshold; The system input or output load of the smart terminal exceeds a preset load threshold. The remaining battery power of the smart terminal is lower than the preset battery power threshold.

[0072] Optionally, the preset type of application may include at least one of the following: short video application, web browser, video communication application. Optionally, the preset type of application may also be an application pre-set by the user. It is understood that when the user launches a preset type of application, such as a short video application or web browser on a smart terminal, the smart terminal anticipates that a large amount of short-term cache will be generated, and thus immediately activates a filtering mechanism, that is, determines whether the target file is a cache file that does not need to be saved to non-volatile memory.

[0073] Optionally, when the remaining storage space of the non-volatile memory is lower than a preset storage threshold, such as 20%, it indicates that storage space is tight. Actively blocking useless cache writes can quickly alleviate space pressure and improve user experience. Optionally, when the system input or output load of the smart terminal is higher than a preset load threshold, such as 80%, it indicates that the IO load is high. Actively blocking useless cache writes can directly reduce the system burden and improve lag. Optionally, when the remaining battery power of the smart terminal is lower than a preset battery threshold, such as 15%, it indicates that the smart terminal is in low-power mode. Actively reducing power-consuming write operations will help extend battery life.

[0074] Optionally, determining whether the target data belongs to the target application's preset data type includes: Analyze the attribute information of the target data to identify its associated applications and data types; In response to the identification that the associated application of the target data is the target application and the data type is a preset data type, it is determined that the target data belongs to the preset data type of the target application.

[0075] Optionally, the attribute information of the target data refers to a set of metadata describing the characteristics of the target data itself and its source, which may include at least one of the following: file storage path, file owner information, file extension, and application package name. The associated application of the target data refers to the application determined by analyzing the attribute information of the target data (especially the package name directory or file owner information in the file path), i.e., the application to which the target data belongs. By matching the attribute information of the target data with a preset feature rule base, the data type of the target data can be identified, as detailed in existing technologies. For example, a smart terminal analyzes the file storage path of the target data and finds that its path contains the suffix " / cache / " or ".tmp". Based on the preset feature rule base, it determines that it is of the type "application cache data" or "system temporary data".

[0076] Optionally, the target application can be any application that the user has installed, and the default data types for all installed applications are not saved.

[0077] Optionally, the target application is a pre-set or selected application, and data corresponding to one or more target applications is not saved.

[0078] Optionally, the current application is a pre-set or selected application, and data of the corresponding preset data type in the data of one or more target applications is not saved.

[0079] Optionally, the preset data type may include at least one of the following types: application cache data, uninstallation residual data, application installation package data, and system temporary data.

[0080] Optionally, application cache data consists of regenerable, non-permanent data files created by the application for temporary or performance optimization purposes, typically stored in a standard cache directory. For example, if the target data path is / data / com.example.videoapp / cache / segment_001.mp4, which includes the application package name (com.example.videoapp) and the standard cache directory name (cache), then this data can be identified as application cache data. Optionally, uninstallation residual data refers to directories or files left behind after the application is uninstalled. Application installation package data refers to downloaded APK files, which typically do not need to be retained after installation. System temporary data refers to temporary logs, crash dump files, etc., generated during system operation.

[0081] In this way, by precisely defining the types of cached data that do not need to be saved, smart terminals can more clearly and efficiently filter data automatically, further improving the performance of smart terminals.

[0082] Optionally, the smart terminal includes a first interface, which includes independent control options for different applications. In response to an operation on the independent control option, a configuration operation for the target application is performed. The independent control option is used to control whether the application's preset data does not need to be saved.

[0083] Optionally, the smart terminal can provide a dedicated primary interface, such as an application cache management interface, in which the smart terminal lists all installed applications and can provide one or more independent control components (such as toggle buttons, checkboxes, or sliders) for each application. Users can intuitively access control components for each application's corresponding data through these components. For example, such as... Figure 4 As shown, users can access the application cache management interface to independently select "Cache Data," "Data Files," and "Ad Image Cache" options for different applications (such as "Social Media," "Games," "Browser," and "Shopping"). Once selected, the corresponding files for the data types will not be saved, and the corresponding user configuration information will be recorded. When cache data for a particular application is selected, the cache data generated by that application will be intercepted during the write process, meaning the corresponding data will not be written to non-volatile memory.

[0084] Optionally, such as Figure 5 As shown, users can access the space management interface through system settings or system management applications such as mobile phone manager provided by the smart terminal, and independently select whether application cache data, uninstallation residual data, application installation package data, and system temporary data need to be filtered so that they do not need to be saved to non-volatile storage.

[0085] In this way, by providing a unified management interface that allows different applications to have independent control options on whether or not to save preset data, users can intuitively and flexibly manage the caching behavior of each application.

[0086] Optionally, the method further includes: The data corresponding to the target application is temporarily stored in a memory-based temporary file system.

[0087] Optionally, when the data corresponding to the target application is determined not to need to be saved to non-volatile storage, in order to maintain the normal operation of the application (for example, video playback requires reading cached data), the data corresponding to the target application can be temporarily stored in a memory-based temporary file system (such as tmpfs in Linux). This makes the data corresponding to the target application visible and readable in memory, meeting the short-term access needs of the application, but it will automatically disappear after system restart or memory reclamation and will not be written to non-volatile storage such as Flash.

[0088] The method provided in this embodiment will be illustrated by two examples below.

[0089] Example 1: Taking a user browsing short videos as an example. When a user opens a short video app (the corresponding preset trigger conditions are met) and scrolls through short videos, the app continuously sends write requests to the viewed video clips as cached files. Based on the configuration setting "the user has turned off cache saving for the short video app," the smart terminal determines these write requests as unnecessary and immediately returns a write success response message to the app, but the data is only temporarily stored in memory. At this time, the user's viewing experience is smooth and imperceptible, but device power consumption is significantly reduced, Flash space is not occupied, and memory lifespan is protected. When the user closes the short video app or memory is low, this temporary data is automatically cleared.

[0090] Example 2: Taking system space cleanup as an example. When a smart terminal detects that the remaining Flash space is lower than a preset storage threshold (the corresponding preset trigger condition is met), it automatically activates the filtering mechanism. Afterward, all file write requests identified as "uninstallation remnants," "application installation packages (APKs)," etc., are blocked. This means the data is only temporarily stored in memory, preventing further reduction of storage space and buying time for manual cleanup by the user or automatic system cleanup, thus improving efficiency.

[0091] The examples listed above are for reference only. To avoid redundancy, they will not be listed one by one here. In actual development or application, they can be flexibly combined according to actual needs. However, any combination belongs to the technical solution of this application and is covered by the protection scope of this application.

[0092] This application also provides a smart terminal, including a memory and a processor. The memory stores a processing program, and when the processing program is executed by the processor, it implements the processing method in any of the above embodiments.

[0093] This application also provides a storage medium storing a processing program, which, when executed by a processor, implements the processing method in any of the above embodiments.

[0094] In the embodiments of the smart terminal and storage medium provided in this application, all the technical features of any of the above-described processing method embodiments may be included. The extended and explained contents of the specification are basically the same as the embodiments of the above methods, and will not be repeated here.

[0095] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0096] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0097] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0098] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0099] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0100] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0101] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0102] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0103] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0104] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.

[0105] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0106] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A processing method applied to a smart terminal, characterized in that, Including the following steps: S1. In response to the configuration operation for the target application, do not perform a persistent write operation on the data corresponding to the target application.

2. The method as described in claim 1, characterized in that, Step S1 includes: Obtain a save operation request for the target data, and in response to the target data belonging to a preset data type of the target application, return a successful operation response without writing the target data to non-volatile memory.

3. The method as described in claim 2, characterized in that, Before obtaining the save operation request for the target data, the following steps are included: In response to the detection that the smart terminal meets the preset triggering conditions, it is determined whether the target data belongs to the preset data type of the target application.

4. The method as described in claim 3, characterized in that, The preset triggering condition includes at least one of the following: An application of a preset type was detected to be launching. The remaining storage space of the non-volatile memory is lower than a preset storage threshold; The system input or output load of the smart terminal is higher than a preset load threshold. The remaining battery power of the smart terminal is lower than a preset battery power threshold.

5. The method as described in claim 3, characterized in that, The step of determining whether the target data belongs to a preset data type of the target application includes: Analyze the attribute information of the target data to identify the associated applications and data types of the target data; In response to identifying that the associated application of the target data is the target application and the data type is a preset data type, it is determined that the target data belongs to the preset data type of the target application.

6. The method as described in claim 5, characterized in that, The preset data types include at least one of the following: application cache data, uninstallation residual data, application installation package data, and system temporary data.

7. The method as described in claim 1, characterized in that, The smart terminal includes a first interface, which includes independent control options for different applications. In response to an operation on the independent control option, a configuration operation for the target application is performed. The independent control option is used to control whether the preset data corresponding to the application does not need to be saved.

8. The method as described in claim 1, characterized in that, The method further includes: The data corresponding to the target application is temporarily stored in a memory-based temporary file system.

9. A smart terminal, characterized in that, include: A memory and a processor, wherein the memory stores a processing program, and the processing program, when executed by the processor, implements the processing method as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium stores a processing program, which, when executed by a processor, implements the processing method as described in any one of claims 1 to 8.

Images