User profile management method, device, equipment and computer medium

Abstract

The present application discloses a user profile management method, apparatus, device, and computer-readable storage medium, which obtains a target user profile in a target device; determines whether to back up the target user profile; if the target user profile is to be backed up, sends preset information of the target user profile to a cloud server; determines whether an upload instruction sent by the cloud server is received; if an upload instruction is received, uploads the target user profile to the cloud server for backup; wherein the upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time. In the present application, the target user profile can be backed up on the cloud server, allowing the user to manage the required user profile with the help of the backed-up target user profile, thereby improving the application flexibility of the user profile; and avoiding multiple backups of the same user profile, thereby improving backup efficiency.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a user profile management method, apparatus, device, and computer medium. Background Art

[0002] In computers, a user profile is a collection of settings and files that define the environment required to load the system when a user logs in. With the advancement of communication technology, the applications of user profiles have become increasingly diverse. For example, in the Windows operating system, user profile roaming is now possible. This allows a user profile for a specific domain user to be generated locally and then synchronized to a CIFS (Common Internet File System) shared network drive, allowing the user to use the most recently modified version of the profile across multiple hosts.

[0003] However, during the roaming process of user profiles, the user profile may be lost, or the latest user profile may overwrite the old user profile, resulting in the user profile being unable to be restored, making the application flexibility of the user profile poor and affecting the user experience.

[0004] In summary, how to improve the application flexibility of user profiles is an urgent problem to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a user profile management method, which can, to a certain extent, solve the technical problem of how to improve the application flexibility of user profiles. This application also provides a user profile management device, an electronic device, and a computer-readable storage medium.

[0006] To achieve the above objectives, in a first aspect, the present application provides a user profile management method, applied to a client, comprising:

[0007] Obtain the target user profile in the target device;

[0008] Determining whether to back up the target user configuration file;

[0009] If the target user profile is backed up, the preset information of the target user profile is sent to the cloud server, where the preset information is used to represent characteristic information of the target user profile;

[0010] Determining whether an upload instruction sent by the cloud server is received;

[0011] If the upload instruction is received, the target user configuration file is uploaded to the cloud server for backup;

[0012] The upload instruction includes an instruction sent by the cloud server after it determines that it has received the preset information for the first time.

[0013] In the present application, the target user profile can be backed up on the cloud server, so that the user can manage the required user profile with the help of the backed up target user profile, thereby improving the application flexibility of the user profile; and the cloud server will send an upload instruction to back up the target user profile only after receiving the preset information for the first time, thereby avoiding multiple backups of the same user profile and improving the backup efficiency.

[0014] Preferably, after determining whether the upload instruction sent by the cloud server is received, the method further includes:

[0015] If the upload instruction is not received within the preset time, the backup of the target user profile is terminated.

[0016] Preferably, the determining whether to back up the target user configuration file includes:

[0017] Obtain the file version information that records the attribute information of the historical user configuration file;

[0018] Determining file attribute information of the target user configuration file;

[0019] Determining whether the file attribute information belongs to the file version information;

[0020] If the file attribute information does not belong to the file version information, it is determined to back up the target user configuration file.

[0021] Preferably, before obtaining the file version information recording the attribute information of the historical user configuration file, the method further includes:

[0022] Determine whether to perform data restoration after the target device is restarted;

[0023] If the target device does not perform data restoration after restarting, the file version information is stored in a hidden directory with a specified name in the root directory of the user configuration file.

[0024] Preferably, after determining whether to perform data restoration after the target device is restarted, the method further includes:

[0025] If data restoration is performed on the target device after restart, determining whether the target device is configured with non-restoration storage;

[0026] If the target device is configured with the non-restoration storage, storing the file version information in the non-restoration storage;

[0027] If the target device is not configured with the non-restoration storage, the file version information is stored in the hidden directory.

[0028] In the present application, when data restoration is performed after the target device is restarted, it can be determined whether the target device is configured with non-restoration storage; if the target device is configured with non-restoration storage, the file version information is stored in the non-restoration storage, so that after the target device is restarted, the file version information can still be obtained from the non-restoration storage, and whether the target user configuration file is to be backed up can be quickly determined based on the file version information; and when the target device is not configured with non-restoration storage, the file version information is directly stored in a hidden directory, so that the file version information can be quickly obtained from the hidden directory when the target device is not restarted, which can improve the efficiency of determining whether to back up the target user configuration file based on the file version information to a certain extent.

[0029] Preferably, after uploading the target user configuration file to the cloud server for backup, the method further includes:

[0030] The file attribute information is recorded in the file version information.

[0031] Preferably, the preset information includes the file attribute information.

[0032] Preferably, the process of uploading the target user configuration file to the cloud server for backup includes:

[0033] Determine whether there is an opened and occupied preset user registry file in the target user configuration file;

[0034] If the preset user registry file exists in the target user configuration file, the preset user registry file is dumped into a temporary hive file, and the temporary hive file is uploaded to the cloud server.

[0035] Preferably, obtaining the target user profile in the target device includes:

[0036] Obtaining an initial user configuration file in the target device;

[0037] The initial user profile is filtered to obtain the target user profile.

[0038] In a second aspect, the present application provides a user profile management method, applied to a cloud server, comprising:

[0039] Obtain preset information of the target user profile sent by the client;

[0040] Determining whether it is the first time for the user to receive the preset information;

[0041] If it is the first time for the user to receive the preset information, the user sends an upload instruction to the client, and receives the target user profile uploaded by the client after receiving the upload instruction for backing up;

[0042] The preset information includes information sent by the client after determining to back up the target user profile in the target device, and the preset information is used to represent feature information of the target user profile.

[0043] In a third aspect, the present application provides a user profile management device, applied to a client, comprising:

[0044] A user profile acquisition module is used to acquire a target user profile in a target device;

[0045] a backup determination module, configured to determine whether to back up the target user profile; if the target user profile is to be backed up, sending preset information of the target user profile to a cloud server, wherein the preset information is used to represent characteristic information of the target user profile;

[0046] an upload determination module, configured to determine whether an upload instruction sent by the cloud server has been received; if the upload instruction has been received, uploading the target user configuration file to the cloud server for backup;

[0047] The upload instruction includes an instruction sent by the cloud server after it determines that it has received the preset information for the first time.

[0048] In a fourth aspect, the present application provides an electronic device, comprising:

[0049] memory for storing computer programs;

[0050] A processor is configured to implement the steps of any of the above user profile management methods when executing the computer program.

[0051] In a fifth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above user profile management methods are implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without any creative work.

[0053] Figure 1 A system framework diagram of the user profile management solution provided in an embodiment of the present application;

[0054] Figure 2 A first flow chart of a user profile management method provided in an embodiment of the present application;

[0055] Figure 3 A second flow chart of a user profile management method provided in an embodiment of the present application;

[0056] Figure 4 A third flow chart of a user profile management method provided in an embodiment of the present application;

[0057] Figure 5 A schematic diagram of the structure of a user profile management device provided in an embodiment of the present application;

[0058] Figure 6 Another structural diagram of a user profile management device provided in an embodiment of the present application

[0059] Figure 7 Schematic diagram of the hardware structure of the electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0060] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0061] The system framework used in the user profile management solution of this application can be found in Figure 1 As shown, it may specifically include: a client 01, a target device 02 that establishes a communication connection with the client 01, and a cloud server 03 that establishes a communication connection with the client 01.

[0062] In the present application, the client 01 is used to execute the steps of the user profile management method, including obtaining a target user profile in a target device; determining whether to back up the target user profile; if the target user profile is to be backed up, sending preset information of the target user profile to a cloud server, where the preset information is used to characterize characteristic information of the target user profile; determining whether an upload instruction sent by the cloud server is received; if an upload instruction is received, uploading the target user profile to the cloud server for backup; wherein the upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time.

[0063] Furthermore, the client 01 may also be provided with a user profile database, a preset information database, and an instruction database. The user profile database is used to store various user profiles. The preset information database can specifically store preset information for user profiles. The instruction database can be used to store received upload instructions.

[0064] It should be noted that the types of the client and target device can be determined according to actual needs, and the client and target device can be the same device or two different devices, etc. For example, the client and target device can both be the user's computer, or the client can be the user's mobile phone and the target device can be the user's computer, etc. This application does not make specific limitations here.

[0065] See also Figure 2 , Figure 2 This is a first flow chart of a user profile management method provided in an embodiment of the present application.

[0066] An embodiment of the present application provides a user profile management method, which is applied to a client and may include the following steps:

[0067] Step S101: Obtain a target user profile in a target device.

[0068] In actual applications, the target user profile on the target device can be obtained first. The conditions for obtaining the target user profile can be determined based on actual needs, such as real-time acquisition, scheduled acquisition, or acquisition when the user needs it, etc. This application does not impose specific restrictions here. In addition, the type of target device and the content of the target user profile can be determined based on actual needs, and this application does not impose specific restrictions here.

[0069] Step S102: Determine whether to back up the target user configuration file; if the target user configuration file is to be backed up, execute step S103.

[0070] Step S103: Sending preset information of the target user profile to the cloud server, where the preset information is used to represent characteristic information of the target user profile.

[0071] In actual applications, after obtaining the target user profile, you can first determine whether to back up the target user profile. If the target user profile is not backed up, you can end subsequent operations. If the target user profile is backed up, you can send preset information of the target user profile to the cloud server, and the preset information is used to characterize the characteristic information of the target user profile. In this way, after the cloud server receives the preset information, it can determine whether it is necessary to receive the target user profile for backup based on the preset information.

[0072] It should be noted that the conditions for determining whether to back up the target user configuration file can be determined based on the specific application scenario. For example, various backup time nodes can be set to determine whether the current time falls within a backup time node. If so, the target user configuration file is backed up; if not, the target user configuration file is not backed up. Of course, a corresponding backup can be performed when the user configuration file is modified. For example, the time when the target user configuration file is modified and a backup is required is determined, and the target user configuration file is backed up at that time. It is understood that the method for determining the time when the target user configuration file is modified and a backup is required can be determined based on the specific application scenario. For example, on a target device running a Windows operating system, the time can be determined using the ReadDirectoryChanges(Ex) API, on a target device running a Linux operating system, the time can be determined using the inotifywatch mechanism, and on a target device running a macOS operating system, the time can be determined using the FSEvents API. In addition, the preset information of the target user configuration file can also be determined based on the specific application scenario. For example, the preset information can be the 64-byte information in the file header of the target user configuration file.

[0073] Step S104: Determine whether an upload instruction sent by the cloud server is received; if an upload instruction is received, execute step S105.

[0074] Step S105: uploading the target user configuration file to the cloud server for backup; wherein the upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time.

[0075] In actual applications, after receiving the preset information, the cloud server can determine whether it is the first time to receive the preset information. Specifically, it can determine whether the preset information is consistent with the user configuration file backed up by itself. If the preset information is consistent with the user configuration file backed up by itself, it indicates that the target user configuration file has been backed up on the cloud server. At this time, the cloud server can complete the background processing of the upload record by itself, and return an instruction to the client that no file upload is required to end the backup operation. If the preset information is inconsistent with the user configuration file backed up by itself, it indicates that the target user configuration information has not been backed up on the cloud server. At this time, the cloud server can return the upload instruction to receive the target user configuration file for backup.

[0076] It should be noted that after backing up the various user configuration files on the target device, they will be stored on the cloud server. This allows users to directly access the backed-up user configuration files from the cloud server when needed, for example, to restore, view, or analyze the user configuration files on the target device using the backed-up user configuration files. Furthermore, if the client does not receive an upload instruction within a preset time, it can directly terminate the backup of the target user configuration files. Alternatively, it can re-execute the step of sending the preset information to the cloud server, etc., which is not specifically limited in this application.

[0077] The present application provides a user profile management method, which includes obtaining a target user profile in a target device; determining whether to back up the target user profile; if the target user profile is to be backed up, sending preset information of the target user profile to a cloud server, where the preset information is used to characterize characteristic information of the target user profile; determining whether an upload instruction sent by the cloud server is received; and if an upload instruction is received, uploading the target user profile to the cloud server for backup; wherein the upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time. In the present application, the target user profile can be backed up on the cloud server, so that the user can manage the required user profile with the help of the backed-up target user profile, thereby improving the application flexibility of the user profile; and the cloud server will only send the upload instruction to back up the target user profile after receiving the preset information for the first time, thereby avoiding multiple backups of the same user profile and improving backup efficiency.

[0078] See also Figure 3 , Figure 3 This is a second flow chart of a user profile management method provided in an embodiment of the present application.

[0079] An embodiment of the present application provides a user profile management method, which is applied to a client and may include the following steps:

[0080] Step S201: Obtain a target user profile in a target device.

[0081] Step S202: Obtain file version information recording attribute information of historical user configuration files.

[0082] Step S203: Determine the file attribute information of the target user configuration file.

[0083] Step S204: Determine whether the file attribute information belongs to file version information; if the file attribute information does not belong to file version information, execute step S205.

[0084] In actual applications, if the user configuration file changes or is a newly configured file, the user configuration file needs to be backed up. The attribute information of the user configuration file can reflect the characteristics of the user configuration file itself, and after comparing the characteristics of the user configuration file with the characteristics of the existing user configuration file, it can be reflected whether the user configuration file has changed or is newly generated. Therefore, the attribute information of the user configuration file can be used to determine whether to back up the target user configuration file. In this process, it is necessary to record the attribute information of the historical user configuration files that have been backed up in real time, such as recording the attribute information of the historical user configuration files with the help of file version information, and then determine the file attribute information of the target user configuration file; determine whether the file attribute information belongs to the file version information; if the file attribute information does not belong to the file version information, determine to back up the target user configuration file; if the file attribute information belongs to the file version information, determine not to back up the target user configuration file.

[0085] It should be noted that the type of attribute information of the user configuration file can be determined according to actual needs. For example, the attribute information of the user configuration file may include: file size, modification time, creation time, hash value information, file header data items, etc.

[0086] Step S205: Sending preset information of the target user profile to the cloud server, where the preset information is used to represent characteristic information of the target user profile.

[0087] Step S206: Determine whether an upload instruction sent by the cloud server is received; if an upload instruction is received, execute step S207.

[0088] Step S207: uploading the target user configuration file to the cloud server for backup; wherein the upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time.

[0089] In a user profile management method provided in an embodiment of the present application, it is taken into account that the restart of the target device will affect the saved data. For example, if the target device needs to restore the data after restarting, the file version information in the target device will be restored accordingly, affecting the backup of the user profile. In order to reduce the impact of the restart of the target device on the backup of the user profile, the storage location of the file version information can be selected according to the restart characteristics of the target device. That is, before obtaining the file version information that records the attribute information of the historical user profile, it can also be determined whether the data will be restored after the target device is restarted; if the data is not restored after the target device is restarted, the file version information is stored in a hidden directory with a specified name in the root directory of the user profile. At this time, the file version information will not be restored after the target device is restarted. Original; if the target device performs data restoration after restarting, determine whether the target device is configured with non-restoration storage; if the target device is configured with non-restoration storage, store the file version information in the non-restoration storage. At this time, the file version information will not be restored after the target device is restarted; if the target device is not configured with non-restoration storage, store the file version information in a hidden directory. At this time, the file version information can only be retained during this boot process, and the file version information will still be restored after the target device is restarted. All user configuration files of the target device need to be backed up, but due to the restrictions of the cloud server upload instructions, the backed up user configuration files will not be backed up again on the cloud server, ensuring the simplicity and accuracy of the backup. It should be noted that the file version information can be stored anywhere on the target device.

[0090] In actual applications, after uploading the target user configuration file to the cloud server for backup, in order to avoid performing a backup operation on the target user configuration file again in the future, the file attribute information can be recorded in the file version information.

[0091] In actual applications, in order to facilitate users to obtain and apply the file attribute information of the target user configuration file, and also to facilitate the cloud server to apply the file attribute information, the client can place the file attribute information in the preset information and send it to the cloud server. In this way, users can manage the backed up user configuration files in the cloud server through the file attribute information.

[0092] In a user profile management method provided by an embodiment of the present application, if there is an open or occupied user registry file in the target user profile during the process of uploading the target user profile to the cloud server for backup, such user registry file cannot be uploaded to the cloud server. For example, in a target device with a Windows operating system, the registry files NTUSER.DAT and UsrClass.dat in the user profile cannot be uploaded to the cloud server because they are opened and occupied by the system. At this time, in order to ensure that such registry files can be backed up by the cloud server, it can be determined whether there is an open or occupied preset user registry file in the target user profile; if there is a preset user registry file in the target user profile, the preset user registry file is dumped as a temporary hive file, for example, by using the registry API RegSaveKey to dump the preset user registry file as a temporary hive file, and the temporary hive file is uploaded to the cloud server instead of uploading the preset registry file.

[0093] In a user profile management method provided in an embodiment of the present application, in order to improve the backup efficiency of the user profile, the backed-up user profile can also be filtered and screened. That is, in the process of obtaining the target user profile in the target device, the initial user profile in the target device can be obtained; the initial user profile is filtered to obtain the target user profile.

[0094] It should be noted that the method and conditions for filtering the initial user configuration files can be determined according to the specific application scenario. For example, the user configuration files can be filtered according to the extension name and file format of the user configuration files, etc. This application does not make specific limitations here.

[0095] See also Figure 4 , Figure 4 This is a third flow chart of a user profile management method provided in an embodiment of the present application.

[0096] A user profile management method provided in an embodiment of the present application, applied to a cloud server, may include the following steps:

[0097] Step S301: Acquire preset information of a target user profile sent by a client.

[0098] Step S302: Determine whether it is the first time for the device to receive the preset information; if it is the first time for the device to receive the preset information, execute step S303.

[0099] Step S303: Send an upload instruction to the client, and receive the target user profile uploaded by the client after receiving the upload instruction for backing up; wherein the preset information includes information sent by the client after determining to back up the target user profile in the target device, and the preset information is used to characterize characteristic information of the target user profile.

[0100] For the corresponding description in this embodiment, please refer to the above corresponding embodiments and will not be repeated here.

[0101] See also Figure 5 , Figure 5 A schematic diagram of the structure of a user profile management device provided in an embodiment of the present application.

[0102] An embodiment of the present application provides a user profile management device, which is applied to a client and may include:

[0103] A user profile acquisition module 101 is used to acquire a target user profile in a target device;

[0104] The backup determination module 102 is used to determine whether to back up the target user profile; if the target user profile is to be backed up, the preset information of the target user profile is sent to the cloud server, where the preset information is used to represent the characteristic information of the target user profile;

[0105] The upload determination module 103 is used to determine whether an upload instruction sent by the cloud server has been received; if an upload instruction has been received, the target user configuration file is uploaded to the cloud server for backup;

[0106] The upload instruction includes an instruction sent by the cloud server after it determines that it has received the preset information for the first time.

[0107] An embodiment of the present application provides a user profile management device, which is applied to a client. The backup judgment module can also be specifically configured to terminate the backup of the target user profile if no upload instruction is received within a preset time.

[0108] An embodiment of the present application provides a user profile management device, which is applied to a client. The backup determination module may include:

[0109] A version information acquisition unit, used to acquire file version information recording attribute information of a historical user configuration file;

[0110] An attribute information determining unit, configured to determine the file attribute information of a target user configuration file;

[0111] The backup judgment unit is used to judge whether the file attribute information belongs to the file version information; if the file attribute information does not belong to the file version information, it is determined to back up the target user configuration file.

[0112] An embodiment of the present application provides a user profile management device, which is applied to a client and may further include:

[0113] The restart and restore judgment unit is used to judge whether data restoration is performed after the target device is restarted before the version information acquisition unit obtains the file version information that records the attribute information of the historical user configuration file; if the target device does not restore data after the restart, the file version information is stored in a hidden directory with a specified name in the root directory of the user configuration file; if the target device restores data after the restart, it is judged whether the target device is configured with non-restoration storage; if the target device is configured with non-restoration storage, the file version information is stored in the non-restoration storage; if the target device is not configured with non-restoration storage, the file version information is stored in the hidden directory.

[0114] An embodiment of the present application provides a user profile management device, which is applied to a client and may further include:

[0115] The recording unit is configured to record the file attribute information in the file version information after the upload judgment module uploads the target user configuration file to the cloud server for backup.

[0116] An embodiment of the present application provides a user configuration file management device, which is applied to a client, and the preset information may include file attribute information.

[0117] An embodiment of the present application provides a user profile management device, which is applied to a client. The upload judgment module may include:

[0118] The occupancy judgment unit is used to judge whether there is an opened and occupied preset user registry file in the target user configuration file; if the preset user registry file exists in the target user configuration file, the preset user registry file is dumped into a temporary hive file and the temporary hive file is uploaded to the cloud server.

[0119] An embodiment of the present application provides a user profile management device, which is applied to a client. The user profile acquisition module may include:

[0120] A user configuration file acquisition unit, configured to acquire an initial user configuration file in a target device;

[0121] The filtering unit is used to filter the initial user profile to obtain a target user profile.

[0122] See also Figure 6 , Figure 6This is another structural diagram of a user profile management device provided in an embodiment of the present application.

[0123] An embodiment of the present application provides a user profile management device, which is applied to a cloud server and may include:

[0124] The preset information acquisition module 201 is used to acquire the preset information of the target user profile sent by the client.

[0125] The receiving judgment module 202 is used to determine whether it is the first time to receive the preset information; if it is the first time to receive the preset information, it sends an upload instruction to the client, and receives the target user configuration file uploaded by the client after receiving the upload instruction for backup; wherein, the preset information includes information sent by the client after determining to back up the target user configuration file in the target device, and the preset information is used to represent the characteristic information of the target user configuration file.

[0126] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiment of the present invention, the embodiment of the present invention further provides an electronic device, Figure 7 FIG. 1 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present invention. Figure 7 As shown, the electronic equipment includes:

[0127] Communication interface 1, capable of exchanging information with other devices such as network devices;

[0128] The processor 2 is connected to the communication interface 1 to implement information exchange with other devices and is used to execute the user profile management method provided by one or more of the above technical solutions when running a computer program. The computer program is stored in the memory 3.

[0129] Of course, in actual application, the various components in the electronic device are coupled together through the bus system 4. It can be understood that the bus system 4 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 4 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 7 Various buses are labeled as bus system 4.

[0130] The memory 3 in the embodiment of the present invention is used to store various types of data to support the operation of the electronic device. Examples of such data include: any computer program used to operate on the electronic device.

[0131] It is understood that the memory 3 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk memory or a magnetic tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memory 2 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memories.

[0132] The method disclosed in the above embodiment of the present invention can be applied to processor 2 or implemented by processor 2. Processor 2 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the hardware integrated logic circuit in processor 2 or by instructions in software form. The above processor 2 can be a general-purpose processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. Processor 2 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment of the present invention. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in memory 3. Processor 2 reads the program in memory 3 and completes the steps of the above method in combination with its hardware.

[0133] When the processor 2 executes the program, the corresponding processes in the various methods of the embodiments of the present invention are implemented, which will not be described here for the sake of brevity.

[0134] In an exemplary embodiment, the present invention further provides a storage medium, namely, a computer storage medium, specifically, a computer-readable storage medium, such as a memory 3 storing a computer program. The computer program can be executed by a processor 2 to perform the steps of the aforementioned method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface mount storage, optical disk, or CD-ROM.

[0135] In the several embodiments provided in this application, it should be understood that the disclosed devices, terminals and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0136] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0137] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0138] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: mobile storage devices, ROM, RAM, disks or optical disks, etc. Various media that can store program codes.

[0139] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling an electronic device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0140] For descriptions of the relevant portions of the user profile management system, device, and computer-readable storage medium provided in the embodiments of this application, please refer to the detailed description of the corresponding portions of the user profile management method provided in the embodiments of this application, and will not be repeated here. In addition, portions of the above-mentioned technical solutions provided in the embodiments of this application that are consistent with the implementation principles of corresponding technical solutions in the prior art are not described in detail to avoid excessive elaboration.

[0141] It should also be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0142] The above description of the disclosed embodiments will enable one skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user profile management method, characterized in that: Applied to the client, including: Obtain the target user profile in the target device; Determining whether to back up the target user configuration file; If the target user profile is backed up, the preset information of the target user profile is sent to the cloud server, where the preset information is used to represent characteristic information of the target user profile; Determining whether an upload instruction sent by the cloud server is received; If the upload instruction is received, the target user configuration file is uploaded to the cloud server for backup; The upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time; The process of uploading the target user configuration file to the cloud server for backup includes: Determine whether there is an opened and occupied preset user registry file in the target user configuration file; If the preset user registry file exists in the target user configuration file, the preset user registry file is dumped into a temporary hive file, and the temporary hive file is uploaded to the cloud server.

2. The method according to claim 1, characterized in that After determining whether the upload instruction sent by the cloud server is received, the method further includes: If the upload instruction is not received within the preset time, the backup of the target user profile is terminated.

3. The method according to claim 1, characterized in that The determining whether to back up the target user configuration file includes: Obtain the file version information that records the attribute information of the historical user configuration file; Determining file attribute information of the target user configuration file; Determining whether the file attribute information belongs to the file version information; If the file attribute information does not belong to the file version information, it is determined to back up the target user configuration file.

4. The method according to claim 3, characterized in that Before obtaining the file version information of the attribute information of the historical user configuration file, the method further includes: Determine whether to perform data restoration after the target device is restarted; If the target device does not perform data restoration after restarting, the file version information is stored in a hidden directory with a specified name in the root directory of the user configuration file.

5. The method according to claim 4, characterized in that After determining whether to restore data after the target device is restarted, the method further includes: If data restoration is performed on the target device after restart, determining whether the target device is configured with non-restoration storage; If the target device is configured with the non-restoration storage, storing the file version information in the non-restoration storage; If the target device is not configured with the non-restoration storage, the file version information is stored in the hidden directory.

6. The method according to claim 3, characterized in that After uploading the target user configuration file to the cloud server for backup, the method further includes: The file attribute information is recorded in the file version information.

7. The method according to claim 3, characterized in that The preset information includes the file attribute information.

8. The method according to claim 1, characterized in that The step of obtaining the target user profile in the target device includes: Obtaining an initial user configuration file in the target device; The initial user profile is filtered to obtain the target user profile.

9. A user profile management method, characterized in that: Applied to cloud servers, including: Obtain preset information of the target user profile sent by the client; Determining whether it is the first time for the user to receive the preset information; If it is the first time for the user to receive the preset information, the user sends an upload instruction to the client, and receives the target user configuration file uploaded by the client after receiving the upload instruction for backup; The preset information includes information sent by the client after determining to back up the target user profile in the target device, and the preset information is used to represent characteristic information of the target user profile; The process of uploading the target user configuration file to the cloud server for backup by the client includes: determining whether there is an opened and occupied preset user registry file in the target user configuration file; if the preset user registry file exists in the target user configuration file, dumping the preset user registry file into a temporary hive file, and uploading the temporary hive file to the cloud server.

10. A user profile management device, characterized in that: Applied to the client, including: A user profile acquisition module is used to acquire a target user profile in a target device; a backup determination module, configured to determine whether to back up the target user profile; if the target user profile is to be backed up, sending preset information of the target user profile to a cloud server, wherein the preset information is used to represent characteristic information of the target user profile; an upload determination module, configured to determine whether an upload instruction sent by the cloud server has been received; if the upload instruction has been received, uploading the target user configuration file to the cloud server for backup; The upload instruction includes an instruction sent by the cloud server after determining that it has received the preset information for the first time; Wherein, the upload judgment module includes: The occupancy judgment unit is used to judge whether there is an opened and occupied preset user registry file in the target user configuration file; if the preset user registry file exists in the target user configuration file, the preset user registry file is dumped into a temporary hive file, and the temporary hive file is uploaded to the cloud server.

11. An electronic device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the user profile management method according to any one of claims 1 to 8 or claim 9 when executing the computer program.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the user profile management method according to any one of claims 1 to 8 or claim 9 is implemented.

Images