CN115659367A

CN115659367A - Data processing method, device, terminal equipment and medium

Info

Publication number: CN115659367A
Application number: CN202211301869.0A
Authority: CN
Inventors: 孙哲; 张亚芹; 孙晓
Original assignee: Hisense Mobile Communications Technology Co Ltd
Current assignee: Hisense Mobile Communications Technology Co Ltd
Priority date: 2022-10-24
Filing date: 2022-10-24
Publication date: 2023-01-31

Abstract

The embodiment of the application provides a data processing method, a data processing device, a terminal device and a medium, which are used for solving the problem that a file to be encrypted is damaged due to abnormal interruption of an encryption process in the prior art.

Description

Data processing method, device, terminal equipment and medium

Technical Field

The present application relates to the field of information security technologies, and in particular, to a data processing method, an apparatus, a terminal device, and a medium.

Background

With the continuous development of information security technology, the application of encryption technology is more and more extensive, and in order to ensure the security of a file to be encrypted, the prior art generally reads data in the file to be encrypted, adds the read data into a new encrypted file, encrypts the new encrypted file, and deletes the file to be encrypted after the encryption is completed. However, by using this method, a new encrypted file can be stored only when the device has a space at least as large as that of the file to be encrypted, and if there is not enough space, encryption cannot be performed because there is no space for storing the new encrypted file, for example, when there is a file to be encrypted that needs to be encrypted that has 2GB currently, and the remaining space of the device is only 1GB, a new encrypted file cannot be created because the remaining space is less than 2GB, resulting in encryption failure.

In order to encrypt a file to be encrypted under the condition of insufficient space, the prior art proposes to encrypt the file by using a duplicate encryption method, wherein partial data is sequentially read from the file to be encrypted, and the encrypted partial data is written back to a position corresponding to the partial data before encryption after the partial data is encrypted, namely, the partial data is written back while being encrypted. However, if the encryption process is interrupted abnormally, the file to be encrypted becomes partially encrypted and partially unencrypted, and the abnormal interruption may cause the abnormality of partially encrypted data, which directly results in the damage of the file to be encrypted and the file cannot be used.

Disclosure of Invention

The embodiment of the application provides a data processing method, a data processing device, terminal equipment and a medium, which are used for solving the problem that a file to be encrypted is damaged due to abnormal interruption of an encryption process in the prior art.

In a first aspect, an embodiment of the present application provides a data processing method, where the method includes:

the method comprises the steps that an application layer obtains a File to be encrypted corresponding to an encryption request, and the File to be encrypted is stored in a partition of a Flash Friendly File System (f 2 fs);

the application layer informs the vold process to add an archive point (checkpoint) for the partition;

and the application layer encrypts the file to be encrypted and informs the vold process to clear the checkpoint after the encryption is finished.

In a second aspect, an embodiment of the present application further provides a data processing apparatus, where the apparatus includes:

the acquisition and storage module is used for acquiring a file to be encrypted corresponding to the encryption request by the application layer and storing the file to be encrypted in a partition of the f2fs file system;

the notification module is used for notifying the vold process to add checkpoint to the partition by the application layer;

and the processing module is used for encrypting the file to be encrypted by the application layer and informing the vold process to clear the checkpoint after the encryption is finished.

In a third aspect, an embodiment of the present application further provides a terminal device, where the terminal device includes:

a display, a processor, and a memory;

the display is used for displaying a screen display area;

the memory to store the processor-executable instructions;

the processor is configured to execute the instructions to implement the steps in the data processing method as described in any of the above.

In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps in the data processing method described in any one of the foregoing.

In the embodiment of the application, an application layer of a terminal device obtains a file to be encrypted corresponding to an encryption request, stores the file to be encrypted in a partition of an f2fs file system, notifies a vold process to add checkpoint to the partition, encrypts the file to be encrypted, and notifies the vold process to clear checkpoint after encryption is completed. In the embodiment of the application, before the terminal device encrypts the file to be encrypted, the application layer of the terminal device notifies the vold process to add checkpoint to the partition for storing the file to be encrypted, and after the file to be encrypted is encrypted, the application layer of the terminal device notifies the vold process to clear checkpoint, so that if the encryption process is abnormally interrupted, the corresponding f2fs file system can be restored to the storage state when checkpoint is added by restarting the terminal device, and the file to be encrypted can be restored to the state before encryption is started, that is, even if the encryption process is abnormally interrupted, the file to be encrypted can still be ensured not to be damaged.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 shows a schematic structural diagram of a terminal device 100;

fig. 2 is a block diagram of a software structure of a terminal device 100 according to an embodiment of the present application;

fig. 3 is a schematic diagram of a data processing process according to an embodiment of the present application;

fig. 4 is a schematic diagram of a process of adding checkpoint provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a process of encrypting a plurality of files to be encrypted according to an embodiment of the present application;

fig. 6 is a complete schematic diagram of an encryption process provided in an embodiment of the present application;

fig. 7 is a schematic diagram of an encryption process provided in an embodiment of the present application;

FIG. 8 is a complete diagram of a data processing process according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application;

fig. 10 is another schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

The present application will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

With the continuous development of information security technology, the application of encryption technology is also more and more extensive, in order to ensure the security of a file to be encrypted, the prior art generally reads data in the file to be encrypted, adds the read data into a new encrypted file, encrypts the new encrypted file, and deletes the file to be encrypted after encryption is completed. However, by using this method, a new encrypted file can be stored only when the device has a space at least as large as that of the file to be encrypted, and if there is not enough space, encryption cannot be performed because there is no space for storing the new encrypted file, for example, when there is a 2GB file to be encrypted that needs to be encrypted currently, and at this time, the remaining space of the device is only 1GB, a new encrypted file cannot be created because the remaining space is less than 2GB, and encryption fails.

In order to ensure that a file to be encrypted is not damaged, embodiments of the present application provide a data processing method, an apparatus, a terminal device, and a medium. The data processing method comprises the following steps: and the application layer of the terminal equipment acquires a file to be encrypted corresponding to the encryption request, stores the file to be encrypted in a partition of the f2fs file system, informs the vold process to add checkpoint to the partition, encrypts the file to be encrypted, and informs the vold process to clear checkpoint after encryption is completed. If the encryption process is interrupted abnormally, the f2fs file system can be restored to the state of adding checkpoint by restarting, that is, even if the encryption process is interrupted abnormally, the file to be encrypted can still be ensured not to be damaged.

Fig. 1 shows a schematic structural diagram of a terminal device 100. It should be understood that the terminal device 100 shown in fig. 1 is only an example, and the terminal device 100 may have more or less components than those shown in fig. 1, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

A block diagram of a hardware configuration of a terminal device 100 according to an exemplary embodiment is exemplarily shown in fig. 1. As shown in fig. 1, the terminal device 100 includes: radio Frequency (RF) circuit 110, memory 120, display unit 130, camera 140, sensor 150, audio circuit 160, wireless Fidelity (Wi-Fi) module 170, processor 180, bluetooth module 181, and power supply 190.

The RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and may receive downlink data of a base station and then send the downlink data to the processor 180 for processing; the uplink data may be transmitted to the base station. Typically, the RF circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 120 may be used to store software programs and data. The processor 180 performs various functions of the terminal device 100 and data processing by executing software programs or data stored in the memory 120. The memory 120 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. The memory 120 stores an operating system that enables the terminal device 100 to operate. In the present application, the memory 120 may store an operating system and various application programs, and may also store program codes for executing the data processing method of the terminal device according to the embodiment of the present application.

The display unit 130 may be used to receive input numeric or character information and generate signal input related to user settings and function control of the terminal device 100, and specifically, the display unit 130 may include a touch screen 131 disposed on the front surface of the terminal device 100 and capable of collecting touch operations, such as button clicking, by the user thereon or nearby.

The display unit 130 may also be used to display a Graphical User Interface (GUI) of information input by or provided to the user and various menus of the terminal apparatus 100. Specifically, the display unit 130 may include a display screen 132 disposed on the front surface of the terminal device 100. The display screen 132 may be configured in the form of a liquid crystal display, a light emitting diode, or the like. The display unit 130 may be used to display a screen display area of the terminal device in the present application.

The touch screen 131 may cover the display screen 132, or the touch screen 131 and the display screen 132 may be integrated to implement the input and output functions of the terminal device 100, and after the integration, the touch screen may be referred to as a touch display screen for short. In the present application, the display unit 130 may display the application programs and the corresponding operation steps.

The camera 140 may be used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing elements convert the light signals into electrical signals which are then passed to the processor 180 for conversion into digital image signals.

The terminal device 100 may further comprise at least one sensor 150, such as an acceleration sensor 151, a distance sensor 152, a fingerprint sensor 153, a temperature sensor 154. The terminal device 100 may also be configured with other sensors such as a gyroscope, barometer, hygrometer, thermometer, infrared sensor, light sensor, motion sensor, and the like.

The audio circuitry 160, speaker 161, microphone 162 may provide an audio interface between the user and the terminal device 100. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161. The terminal device 100 may further be configured with a volume button for adjusting the volume of the sound signal, and may also be configured to combine other buttons to adjust the closed region. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, and then outputs the audio data to the RF circuit 110 to be transmitted to, for example, another terminal device, or outputs the audio data to the memory 120 for further processing.

Wi-Fi belongs to a short-distance wireless transmission technology, and the terminal device 100 can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the Wi-Fi module 170, and provides wireless broadband internet access for the user.

The processor 180 is a control center of the terminal device 100, connects various parts of the entire terminal device using various interfaces and lines, and performs various functions of the terminal device 100 and processes data by running or executing software programs stored in the memory 120 and calling data stored in the memory 120. In some embodiments, processor 180 may include one or more processing units; the processor 180 may also integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a baseband processor, which mainly handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 180. In the present application, the processor 180 may run an operating system, an application program, a user interface display, and a touch response, and the data processing method of the terminal device according to the embodiment of the present application. Further, the processor 180 is coupled with the display unit 130.

And the bluetooth module 181 is configured to perform information interaction with other bluetooth devices having bluetooth modules through a bluetooth protocol. For example, the terminal device 100 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) having a bluetooth module via the bluetooth module 181, so as to perform data interaction.

The terminal device 100 also includes a power supply 190 (such as a battery) to power the various components. The power supply may be logically connected to the processor 180 through a power management system to manage charging, discharging, power consumption, etc. through the power management system. The terminal device 100 may further be configured with a power button for powering on and off the terminal device, and locking the screen.

Fig. 2 is a block diagram of a software structure of a terminal device 100 according to an embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system may be divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer, from top to bottom, respectively.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include phone, multimedia message, wiFi, weChat, information, alarm, gallery, calendar, WLAN, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and answered, browsing history and bookmarks, phone books, short messages, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying a picture.

The phone manager is used to provide the communication function of the terminal device 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources, such as localized strings, icons, pictures, layout files, video files, etc., to the application.

The notification manager allows the application to display notification information (e.g., the message content of a short message) in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to notify download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scrollbar text in a status bar at the top of the system, such as a notification of a running application in the background, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the terminal device vibrates, an indicator light flickers, and the like.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

A 2D (one way of animation) graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The terminal device 100 in the embodiment of the present application may be an electronic device including, but not limited to, a smart phone, a tablet computer, a wearable electronic device (e.g., a smart watch), a notebook computer, and the like.

Fig. 3 is a schematic diagram of a data processing process provided in an embodiment of the present application, where the process includes the following steps:

s301: and the application layer acquires a file to be encrypted corresponding to the encryption request and stores the file to be encrypted in a partition of the f2fs file system.

The data processing process provided by the embodiment of the application is applicable to a terminal device, and the terminal device may be the terminal device shown in fig. 1 or fig. 2.

In the embodiment of the application, if there is a need for encrypting a file to be encrypted, the terminal device may be operated, and the terminal device may obtain a corresponding encryption request through an identification operation. Specifically, a user may select a file to be encrypted on a preset page of an application related to encryption installed in the terminal device, and click a preset button, for example, an "encryption" button, so that an application layer of the terminal device may obtain an encryption request, where the encryption request may carry a storage path corresponding to the file to be encrypted, and after obtaining the storage path, the application layer of the terminal device may obtain the corresponding file to be encrypted based on the storage path.

After the application layer of the terminal device obtains the corresponding file to be encrypted, the file to be encrypted can be stored in a partition of the f2fs file system, wherein the file to be encrypted can be stored in a data partition. Typically, the location where the file to be encrypted is actually stored is the data/media of the f2fs file system.

From the viewpoint of user viewing, a general storage location of a file to be encrypted is/storage/encrypted/this directory, this directory is a virtual directory, a corresponding file system is another file system other than the f2fs file system, usually a user space (file in user space, fuse) file system, the directory actually corresponding to the virtual directory is a subdirectory of a data partition, for example, the directory may be a/data/media directory, and the data partition uses a f2fs file system. Although the virtual directory and the actual directory share the space of the same partition, the virtual directory and the actual directory are completely different file systems, and the virtual directory and the actual directory are equivalent to shared storage and have a certain corresponding relation. For example, the user takes a photo, and the user can see the photo stored in/storage/organized/0/DCIM/1. Png through the application in the terminal device, but actually, the photo is stored in/data/media/0/DCIM/1. Png at the bottom layer of the terminal device.

S302: the application layer notifies the vold process to add checkpoint for the partition.

In order to ensure that the file to be encrypted is not damaged, after the application layer acquires the file to be encrypted, the checkpoint function of the f2fs file system may be utilized to add checkpoint to the partition for storing the file to be encrypted. Since the application layer does not have the authority to add checkpoint to the partition, in the embodiment of the application, an interface may be pre-packaged, and the application layer may add checkpoint to the partition storing the file to be encrypted through the pre-packaged interface.

Specifically, in the embodiment of the present application, the vold process may be notified by an application layer, the vold process adds checkpoint to the partition for storing the file to be encrypted, that is, an archive point is reserved for the f2fs file system, the specific application layer may notify the vold process through a first interface packaged in advance, and the vold process adds checkpoint to the partition for storing the file to be encrypted through a second interface packaged in advance.

It should be noted that, before checkpoint in a partition is cleared, all operations on files stored in the partition are recorded in the cache, and do not actually affect files saved in the partition, that is, files of the f2fs file system. For example, after checkpoint is added to the data partition, many files are modified, and some files are deleted, as long as the terminal device is powered off and restarted, all operations performed after checkpoint is added are invalid, and the f2fs file system is restored to the storage state when checkpoint is added. Therefore, in the embodiment of the application, before the file to be encrypted is encrypted, checkpoint can be added to the partition for storing the file to be encrypted, so that the problem that the file to be encrypted is damaged due to abnormal interruption of the encryption process is avoided.

S303: and the application layer encrypts the file to be encrypted and informs the vold process to clear the checkpoint after the encryption is finished.

After the application layer notifies the vold process to add checkpoint to the partition for storing the file to be encrypted, the application layer may encrypt the file to be encrypted, where in this embodiment of the application layer may encrypt the file to be encrypted by using a duplication encryption method in the prior art, that is, part of data in the file to be encrypted is extracted to encrypt the part of data, and the part of data is written back to the file to be encrypted after being encrypted, and part of data in the remaining unencrypted data is extracted, and the above steps are repeated until the data in the file to be encrypted is completely encrypted. Specifically, how to encrypt the file to be encrypted by using a duplicate encryption method is the prior art, and is not described herein again. It is worth mentioning that the duplicate encryption mode is adopted to encrypt the file to be encrypted, no extra space is occupied, the file to be encrypted can be effectively encrypted, and the security of the file to be encrypted can be improved due to the fact that the file to be encrypted is encrypted.

In the embodiment of the application, after the encryption of the file to be encrypted is completed, the file to be encrypted is not damaged due to the fact that the encryption process is interrupted abnormally, so that the added checkpoint can be cleared. Since the application layer does not have the right to clear checkpoint for the partition, in the embodiment of the present application, an interface may be pre-packaged, and the application layer may clear checkpoint through the pre-packaged interface.

Specifically, in the embodiment of the present application, the application layer may notify the vold process through the third interface packaged in advance, and the vold process clears the checkpoint through the fourth interface packaged in advance.

In the prior art, when a file to be encrypted is encrypted, a low-level encryption mode is usually adopted in order to improve the encryption speed, for example, partial data of the file to be encrypted is encrypted, but in the embodiment of the application, the file to be encrypted is encrypted in a duplicate encryption mode, so that high-level encryption can be realized, no extra storage space is required, and the file to be encrypted can be recovered to a state of not being damaged even if the encryption process is abnormally interrupted.

In the embodiment of the application, before the terminal device encrypts the file to be encrypted, the application layer of the terminal device notifies the vold process to add checkpoint to the partition for storing the file to be encrypted, and after the file to be encrypted is encrypted, the application layer of the terminal device notifies the vold process to clear checkpoint, so that if the encryption process is abnormally interrupted, the corresponding f2fs file system can be restored to the storage state when checkpoint is added by restarting the terminal device, the file to be encrypted can be restored to the state before encryption is started, that is, even if the encryption process is abnormally interrupted, the file to be encrypted can still be ensured not to be damaged.

In order to add checkpoint to a partition, on the basis of the foregoing embodiment, in an embodiment of the present application, notifying, by the application layer, a vold process to add checkpoint to the partition includes:

and the application layer informs the vold process to add checkpoint to the partition through a system service (SystemServer).

In an actual application scenario, the application layer cannot directly communicate with the vold process, and therefore the application layer cannot directly notify the vold process to add checkpoint to the partition, but the application layer may communicate with the SystemServer.

Specifically, since the application layer may communicate with the SystemServer, and the SystemServer may communicate with the vold process, in this embodiment of the application, an interface for communicating with the vold process may be packaged in the SystemServer in advance, and for convenience of distinguishing, the interface may be referred to as a fifth interface, where the fifth interface may be "SystemServer- > setDataCheckpoint ()", the application layer may send, to the SystemServer, a message that checkpoint is added to a partition where a file to be encrypted is stored, the SystemServer calls the fifth interface to implement communication with the vold process, and informs that the vold process currently has a requirement that checkpoint is added to the partition where the file to be encrypted is stored, and the vold process adds checkpoint to the partition where the file to be encrypted is stored.

In this embodiment of the application, when adding checkpoint to a partition storing a file to be encrypted, a vold process may implement checkpoint addition through an interface "vold- > setCheckpoint ()", specifically, may adjust a mount parameter of the partition through the interface and a preset instruction including the checkpoint parameter, and assign the checkpoint parameter to the partition storing the file to be encrypted, thereby implementing checkpoint addition. For example, a vold process may implement the addition of checkpoint via an instruction of "mount-o remount-o checkpoint = disable: 0/data".

It should be noted that, if the encryption process is abnormally interrupted due to a restart or abnormal shutdown in the process of duplicating and encrypting the file to be encrypted, the file to be encrypted can be restored to the state before encryption is started due to the checkpoint function when the computer is started next time, thereby avoiding the possibility of being damaged.

Fig. 4 is a schematic diagram of a process of adding checkpoint provided in an embodiment of the present application, where the process includes the following steps:

s401: and the application layer sends a message of adding checkpoint to the partition for storing the file to be encrypted to the SystemServer.

S402: and the SystemServer calls the fifth interface to realize the communication with the vold process and informs that the vold process currently has the requirement of adding checkpoint in the partition for storing the file to be encrypted.

S403: and adding checkpoint to the partition for storing the file to be encrypted by the vold process.

In order to accurately clear checkpoint, on the basis of the foregoing embodiments, in an embodiment of the present application, the notifying the vold process to clear checkpoint includes:

the application layer notifies the vold process to clear checkpoint via the SystemServer.

Similarly, in this embodiment of the present application, an interface for communicating with the vold process may be packaged in the SystemServer in advance, and for convenience of distinguishing, the interface may be referred to as a sixth interface, where the sixth interface may be "SystemServer- > clearDataCheckpoint ()", after the encryption of the file to be encrypted by the application layer is completed, the application layer may send a message to the SystemServer to clear the checkpoint of the partition where the file to be encrypted is stored, the SystemServer implements communication with the vold process by calling the sixth interface, informs that the vold process currently has a requirement to clear the checkpoint of the partition where the file to be encrypted is stored, and the vold process clears the checkpoint of the partition where the file to be encrypted is stored. Specifically, when clearing and saving checkpoint of a partition of a file to be encrypted, a vold process can clear checkpoint through an interface of 'vold- > clearCheckpoint ()', and specifically, when clearing checkpoint, a checkpoint parameter of the partition is cleared, so that checkpoint is cleared.

According to the above description, a path is opened from the application layer to the bottom layer, that is, a partition storing a file to be encrypted is opened, and when there is a need to add or remove checkpoint, checkpoint addition or deletion can be performed. The application layer can call the corresponding interface first to realize the addition of checkpoint, encrypt the file to be encrypted by a duplicate encryption mode in the prior art, call the corresponding interface after the file to be encrypted is completely encrypted, and synchronize the encrypted file to be encrypted into the corresponding partition.

In order to ensure that a file to be encrypted is not damaged, on the basis of the foregoing embodiments, in this application embodiment, if the encryption request carries multiple files to be encrypted, notifying the vold process to clear the checkpoint after the encryption is completed includes:

for each file to be encrypted, after the file to be encrypted is encrypted, notifying a vold process to clear the checkpoint; the vold process judges whether other files to be encrypted exist at present;

if not, the vold process clears the checkpoint.

In an actual application scenario, a user may have a need for encrypting a plurality of files to be encrypted, where an encryption request carries the plurality of files to be encrypted, and in this case, an encryption request acquired by a terminal device carries the plurality of files to be encrypted. Because the time length of each file to be encrypted may be different, if the checkpoint is cleared when one or some files to be encrypted are still in the encryption process, it cannot be ensured that the files to be encrypted in the encryption process are not damaged, and therefore in the embodiment of the present application, the checkpoint can be cleared by the vold process after the encryption of a plurality of files to be encrypted is completed.

Specifically, in the embodiment of the present application, if the encryption request carries multiple files to be encrypted, the application layer may start a number of threads of the files to be encrypted, and each thread encrypts the files to be encrypted respectively. For each file to be encrypted, after the corresponding thread completes the encryption of the file to be encrypted, an application layer of the terminal device may notify a vold process to clear checkpoint, the vold process may determine whether there are other files to be encrypted currently, if there are no other files to be encrypted currently, the vold process clears checkpoint added to the partition where the file to be encrypted is stored, and if there are other files to be encrypted currently, the vold process temporarily does not perform the operation of clearing checkpoint, and when there are no other files to be encrypted currently, the vold process clears checkpoint added to the partition where the file to be encrypted is stored.

In the embodiment of the application, when the encryption request carries a plurality of files to be encrypted, the vold process clears checkpoint added to the partition for storing the files to be encrypted under the condition that the files to be encrypted do not exist, so that the files to be encrypted can be ensured not to be damaged.

Fig. 5 is a schematic diagram of a process of encrypting a plurality of files to be encrypted according to an embodiment of the present application, where the process includes the following steps:

s501: the application layer starts a plurality of threads.

The number of the started threads is the same as the number of the files to be encrypted carried in the encryption request.

S502: for each thread, one file to be encrypted is encrypted by the thread.

S503: and for each file to be encrypted, after the file to be encrypted is encrypted, informing the vold process to clear checkpoint.

S504: the vold process determines whether other files to be encrypted exist, if yes, S503 is executed, and if no, S505 is executed.

S505: the vold process clears checkpoint.

In the embodiment of the application, when a plurality of files to be encrypted are encrypted, a multithreading synchronous processing encryption mode is used, namely a plurality of threads are started simultaneously, each thread is used for encrypting different files to be encrypted respectively, and the stability of the encryption process of the plurality of files to be encrypted can be ensured.

In order to ensure that the file to be encrypted is not damaged, on the basis of the foregoing embodiments, in an embodiment of the present application, after the file to be encrypted is encrypted, before the vold process is notified to clear the checkpoint, the method further includes:

updating the number of files which are encrypted currently;

the judging whether other files to be encrypted exist at present comprises the following steps:

and judging whether other files to be encrypted exist at present according to whether the number of the files which are encrypted at present is a preset value or not.

In this embodiment of the present application, the application layer may start a thread for each file to be encrypted, encrypt the file to be encrypted by the thread, update the number of files that are currently being encrypted, and update the number of files that are being encrypted again after the encryption of the file to be encrypted is completed. In the embodiment of the application, when the user selects the files to be encrypted on the preset page of the application related to encryption installed in the terminal device, the files to be encrypted are sequentially selected, and the application layer can sequentially encrypt the files to be encrypted according to the sequence selected by the user corresponding to each file to be encrypted, and can also encrypt the files to be encrypted simultaneously.

The vold process of the terminal device can judge whether other files to be encrypted exist at present according to whether the number of the files being encrypted at present is a preset value or not. The predetermined value may be 0. Specifically, if the number of the files being encrypted is 0, it is determined that no other files to be encrypted exist currently.

In actual implementation, each time a file to be encrypted is to be encrypted, the application layer notifies the vold process to add checkpoint to the partition for storing the file to be encrypted, the vold process judges whether the number of the file being encrypted is 0 through the counter, and if the number of the file being encrypted is 0, checkpoint is added to the partition for storing the file to be encrypted.

After the application layer starts the multiple threads, the multiple threads encrypt each file to be encrypted respectively, when each thread starts encrypting the file to be encrypted, the application layer notifies a vold process to add checkpoint, the vold process adds checkpoint only when determining that the number of the files being encrypted is 0, specifically, for each thread, when the thread prepares to encrypt the file to be encrypted, the application layer may notify the vold process to add checkpoint to a partition storing the file to be encrypted, the vold process globally records a counter, records the number of the files being encrypted through the counter, and after notifying the vold process to add checkpoint to the partition storing the file to be encrypted, the vold process determines whether to add checkpoint by judging whether the number of the files being encrypted is 0 or not, and if the number of the files being encrypted is 0, adds checkpoint and updates the number of the files being encrypted; if the number of the files being encrypted is not 0, not adding checkpoint, updating the number of the files being encrypted, and specifically adding a preset value, wherein the preset value is 1. That is, when the vold process receives the notification of adding checkpoint, if the number of files being encrypted is 0, the vold process actually performs the checkpoint adding step.

In actual implementation, when encryption of a file to be encrypted is completed each time, the application layer notifies the vold process to clear checkpoint for the partition storing the file to be encrypted, the vold process judges whether the number of files being encrypted is 0 through the counter, and if the number of files being encrypted is 0, checkpoint is cleared for the partition storing the file to be encrypted. Specifically, for each file to be encrypted, after the file to be encrypted is encrypted, the application layer notifies the vold process to clear checkpoint, the vold process updates the number of the files being encrypted, specifically subtracts a preset value, the preset value is 1, after the update is completed, whether the number of the files being encrypted is 0 is judged, and if the number of the files being encrypted is 0, checkpoint is cleared; if the number of files being encrypted is not 0, then checkpoint is not cleared. That is, when receiving the notification of clearing checkpoint, the vold process actually performs the checkpoint clearing step if the number of files being encrypted is 0.

Fig. 6 is a complete schematic diagram of an encryption process provided in the embodiment of the present application, where the process includes the following steps:

s601: the application layer obtains an encryption request.

S602: and the application layer acquires a file to be encrypted corresponding to the encryption request.

S603: the application layer notifies the vold process to add checkpoint.

S604: the vold process judges whether the number of the files which are encrypted currently is a preset value, if so, the step S605 is executed, and if not, the step S606 is executed.

S605: the vold process adds checkpoint to the partition for saving the file to be encrypted, and executes S606.

S606: the vold process updates the number of files being encrypted.

Specifically, 1 is added to the number of files being encrypted.

S607: and the application layer encrypts the file to be encrypted, and after the encryption is completed, the vold process is informed to clear checkpoint.

S608: the vold process updates the number of files being encrypted.

Specifically, the number of files being encrypted is decremented by 1.

S609: the vold process determines whether the number of files being encrypted is a preset value, if yes, S610 is executed, and if no, S611 is executed.

S610: the vold process clears checkpoint for the partition holding the file to be encrypted and executes S611.

S611: and (6) ending.

Fig. 7 is a schematic diagram of an encryption process provided in an embodiment of the present application, where an example is described in which an encryption request carries 5 files to be encrypted.

As can be seen from fig. 7, the application layer may start 5 threads, where the 5 threads may be referred to as encryption threads, and encrypt the files to be encrypted by the 5 encryption threads, respectively, where when an encryption thread 1 starts to encrypt the corresponding file to be encrypted, the number of files being encrypted at this time is 0, a checkpoint is added to the vold process, and the number of files being encrypted at this time is updated, and the number of files being encrypted at this time is 1; when the encryption thread 4 starts to encrypt the corresponding files to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 2; when the encryption thread 2 encrypts the corresponding file to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 3; when the encryption thread 3 starts to encrypt the corresponding files to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 4; when the encryption thread 5 starts to encrypt the corresponding file to be encrypted, the number of the files which are encrypted currently is updated, and at this time, the number of the files which are encrypted currently is 5.

When the encryption thread 1 finishes encrypting the corresponding file to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 4; when the encryption thread 4 finishes encrypting the corresponding file to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 3; when the encryption thread 2 completes the encryption of the corresponding file to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 2; when the encryption thread 3 completes the encryption of the corresponding file to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 1; when the encryption thread 5 finishes encrypting the corresponding files to be encrypted, updating the number of the files which are encrypted currently, wherein the number of the files which are encrypted currently is 0, the number of the files which are encrypted currently is a preset number, and clearing checkpoint by the vold process.

In order to ensure that a file to be encrypted is not damaged, on the basis of the foregoing embodiments, in an embodiment of the present application, the encrypting, by the application layer, the file to be encrypted includes:

the application layer encrypts the file to be encrypted to generate cache data, and the cache data is stored in a cache;

after the notifying the vold process to clear the checkpoint, the method further includes:

and synchronizing the cache data from the cache to the partition.

In the embodiment of the application, when the file to be encrypted is encrypted, the application layer generates cache data corresponding to the file to be encrypted and stores the cache data in the cache, wherein the cache data does not occupy the actual space of the disk, and after the application layer notifies the vold process to clear the checkpoint, the application layer synchronizes the cache data from the cache to the partition for storing the file to be encrypted. Specifically, the vold process clears the checkpoint parameter of the partition mount for storing the file to be encrypted, and the application layer can synchronize the cache data into the partition.

According to the embodiment of the application, the cache data is stored in the cache without occupying extra space, and the safety and stability of the complete encryption process of the file to be encrypted can be ensured on the premise of not occupying extra space.

In order to ensure that a file to be encrypted is not damaged, on the basis of the foregoing embodiments, in an embodiment of the present application, after the notifying the vold process adds checkpoint to the partition, and before the notifying the vold process to clear checkpoint, the method further includes:

and if the data synchronization operation is detected and the data is stored in the cache, the operation of synchronizing the data in the cache to the partition is not executed.

In an actual application scenario, after checkpoint is added to a partition storing a file to be encrypted, if data synchronization operations such as file system data synchronization (fsync), file system offload (umount), and the like are triggered, data already in a cache is written back to the partition, and at this time, if encryption of the file to be encrypted is not completed, part of data in the file to be encrypted may be encrypted, and part of data may not be encrypted and damaged.

In the embodiment of the application, when notifying the vold process to add checkpoint to a partition, the application layer may also notify the vold process to add a preset mount parameter to the partition for saving the file to be encrypted, for example, the preset mount parameter may be forcerecord, and specifically, the vold process may add forcerecord mount parameter to the partition by using an instruction of "mount-o remount-ocheckpoint = disable:0-o forcerecord/data", and add checkpoint, so that the partition may determine that the checkpoint is correspondingly added in the encryption process, and an encryption flag may be added to the partition, at this time, all data synchronization operations related to the file system will be ignored by default, thereby avoiding that cache data is wrongly written into the partition, and after the encryption of the encrypted file is completed, when the application layer notifies the vold process to delete the checkpoint, the notification of the preset mount parameter is deleted. It should be noted that the forcerecord mounting parameter is content that is not supported by the current file system, and a service person is required to package a corresponding interface, so that the forcerecord mounting parameter is added to the partition.

Fig. 8 is a complete schematic diagram of a data processing process provided in an embodiment of the present application, where the process includes the following steps:

s801: and the application layer acquires the file to be encrypted corresponding to the encryption request.

S802: and the application layer informs the vold process to add checkpoint and forcerecord mounting parameters for the partition for storing the file to be encrypted.

S803: the vold process adds a forcerecord mount parameter for the partition and adds checkpoint.

The partition may be added with an encryption flag, which prevents a data synchronization operation of the file system, i.e. if a data synchronization operation is detected, the corresponding step of data synchronization is not performed.

S804: and the application layer encrypts the file to be encrypted, and informs the vold process to clear the checkpoint and forcerecord mounting parameters after the encryption is finished.

S805: the vold process clears the checkpoint and forcerecord mount parameters.

The encryption mark in the partition can be cleared, and if the data synchronization operation is detected, the corresponding data synchronization step is executed.

Fig. 9 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application, where the apparatus includes:

an obtaining and saving module 901, configured to obtain, by an application layer, a file to be encrypted corresponding to an encryption request, and save the file to be encrypted in a partition of an f2fs file system;

a notifying module 902, configured to notify, by the application layer, the vold process to add checkpoint to the partition;

and the processing module 903 is configured to encrypt the file to be encrypted by the application layer, and notify the vold process to clear the checkpoint after the encryption is completed.

In a possible implementation, the notifying module 902 is specifically configured to notify, by the application layer, the vold process to add checkpoint to the partition through the SystemServer.

In a possible implementation manner, the processing module 903 is specifically configured to, if the encryption request carries multiple files to be encrypted, notify the vold process to clear the checkpoint after the file to be encrypted is encrypted for each file to be encrypted; the vold process judges whether other files to be encrypted exist at present; if not, the vold process clears the checkpoint.

In a possible implementation manner, the processing module is further configured to update the number of files currently being encrypted;

the method is specifically used for judging whether other files to be encrypted exist at present according to whether the number of the files being encrypted at present is a preset value.

In a possible implementation manner, the processing module 903 is specifically configured to encrypt the file to be encrypted by an application layer, generate cache data, and store the cache data in a cache;

and the cache data is synchronized from the cache to the partition.

In a possible embodiment, the processing module 903 is further configured to, if a data synchronization operation is detected and data is stored in a cache, not perform an operation of synchronizing the data in the cache to the partition.

Based on the same inventive concept, fig. 10 is another schematic structural diagram of the terminal device provided in the embodiment of the present application, as shown in fig. 10, including: one or more than two (including two) processors 1001 and a communication interface 1002.

The processor 1001 stores therein a computer program, which, when executed by the processor 1001, causes the processor 1001 to execute the steps of the data processing method in any of the embodiments described above.

Optionally, the terminal device further comprises a memory 1003, and the memory 1003 may comprise a read-only memory and a random access memory and provides the processor with operation instructions and data. The portion of memory may also include non-volatile random access memory (NVRAM).

In some embodiments, as shown in FIG. 10, memory 1003 stores elements, execution modules or data structures, or a subset thereof, or an expanded set thereof.

As shown in fig. 10, in some embodiments of the present application, the corresponding operation is performed by calling an operation instruction stored in the memory 1003 (the operation instruction may be stored in an operating system).

As shown in fig. 10, a processor 1001, which may also be referred to as a Central Processing Unit (CPU), controls the processing operations of the head-end device.

As shown in fig. 10, the memory 1003 may include a read-only memory and a random access memory, and provides instructions and data to the processor. A portion of the memory 1003 may also include NVRAM. Such as application communication interfaces, and memory, are coupled together by a bus system 1004, where the bus system 1004 may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus. But for the sake of clarity the various busses are labeled in fig. 10 as the bus system 1004.

On the basis of the foregoing embodiments, the present application further provides a computer-readable storage medium, in which a computer program executable by a processor is stored, and when the program runs on the processor, the processor is caused to execute the steps of the data processing method in any of the foregoing embodiments.

Since the principle of solving the problem of the computer readable medium is similar to that of the data processing method, after the processor executes the computer program in the computer readable medium, the implementation steps can be referred to the above embodiments, and the repeated parts are not described again.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A data processing method is applied to a terminal device, and the method comprises the following steps:

the application layer acquires a file to be encrypted corresponding to the encryption request, and stores the file to be encrypted in a partition of a flash friendly f2fs file system;

the application layer informs the vold process to add an archiving point checkpoint to the partition;

2. The method of claim 1, wherein the application layer notifying a vold process to add an archive point checkpoint for the partition comprises:

and the application layer informs the vold process to add checkpoint to the partition through a system service SystemServer.

3. The method of claim 1, wherein if the encryption request carries a plurality of files to be encrypted, the notifying the vold process to clear the checkpoint after the encryption is completed comprises:

for each file to be encrypted, after the file to be encrypted is encrypted, informing a vold process to clear the checkpoint; the vold process judges whether other files to be encrypted exist at present;

if not, the vold process clears the checkpoint.

4. The method of claim 3, wherein after encrypting the file to be encrypted and before notifying the vold process to clear the checkpoint, the method further comprises:

updating the number of files which are encrypted currently;

and judging whether other files to be encrypted exist at present according to whether the number of the files which are encrypted at present is a preset value.

5. The method of claim 1, wherein the application layer encrypting the file to be encrypted comprises:

and synchronizing the cache data from the cache to the partition.

6. The method as claimed in claim 5, wherein after notifying the vold process to add an archive point checkpoint to the partition, and before notifying the vold process to clear the checkpoint, the method further comprises:

7. A data processing apparatus, characterized in that the apparatus comprises:

the acquisition and storage module is used for acquiring a file to be encrypted corresponding to the encryption request by the application layer and storing the file to be encrypted in a partition of the flash-friendly f2fs file system;

the notification module is used for notifying the vold process to add an archiving point checkpoint to the partition by the application layer;

and the processing module is used for encrypting the file to be encrypted by the application layer and informing the vold process of clearing the checkpoint after the encryption is finished.

8. The apparatus according to claim 7, wherein the notification module is specifically configured to notify, by the application layer through a system service SystemServer, a vold process to add checkpoint to the partition.

9. A terminal device, characterized in that the terminal device comprises:

a display, a processor, and a memory;

the display is used for displaying a screen display area;

the memory to store the processor-executable instructions;

the processor is configured to execute the instructions to implement the steps in the data processing method of any of claims 1-6.

10. A computer-readable storage medium, characterized in that a computer program is stored thereon which, when being executed by a processor, carries out the steps of a data processing method according to any one of claims 1-6.