WO2018076875A1 - 备份数据的同步方法、装置、存储介质、电子设备及服务器 - Google Patents

备份数据的同步方法、装置、存储介质、电子设备及服务器 Download PDF

Info

Publication number
WO2018076875A1
WO2018076875A1 PCT/CN2017/095696 CN2017095696W WO2018076875A1 WO 2018076875 A1 WO2018076875 A1 WO 2018076875A1 CN 2017095696 W CN2017095696 W CN 2017095696W WO 2018076875 A1 WO2018076875 A1 WO 2018076875A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared
account
data
backup
target
Prior art date
Application number
PCT/CN2017/095696
Other languages
English (en)
French (fr)
Inventor
何辉
Original Assignee
广东欧珀移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 广东欧珀移动通信有限公司 filed Critical 广东欧珀移动通信有限公司
Publication of WO2018076875A1 publication Critical patent/WO2018076875A1/zh
Priority to US16/290,579 priority Critical patent/US20190199795A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • the present invention relates to the field of cloud backup technologies, and in particular, to a method, device, storage medium, electronic device and server for synchronizing backup data.
  • Cloud backup is an emerging cloud computing service.
  • Cloud backup service providers bring together massive and heterogeneous storage devices in the network through virtualization, distributed processing and broadband networks to provide data storage backups. service. Users can centrally store and secure large numbers and scattered files or folders on the terminal through mobile Internet and broadband Internet access.
  • the cloud backup data synchronization is to back up data in a certain terminal to the cloud server, and send the data to other terminals through the cloud server to implement data synchronization between the terminals.
  • Embodiments of the present invention provide a method, an apparatus, a storage medium, an electronic device, and a server for synchronizing backup data, which can improve the security of backup data.
  • an embodiment of the present invention provides a method for synchronizing backup data, including:
  • the embodiment of the present invention further provides a synchronization device for backing up data, including:
  • An instruction receiving unit configured to receive a shared account adding instruction after logging in to the target backup account
  • An obtaining unit configured to acquire a shared account to be added according to the shared account adding instruction
  • An account adding unit configured to add the shared account to the target backup account
  • a sending unit configured to send, to the cloud server, a shared account setting request that carries the target backup account and the shared account, so that the cloud server performs backup data synchronization according to the shared account setting request.
  • the embodiment of the present invention further provides another method for synchronizing backup data, including:
  • the embodiment of the present invention further provides another synchronization device for backing up data, including:
  • a receiving unit configured to receive a shared account setting request sent by the first terminal, where the shared account setting request carries a target backup account and a shared account corresponding to the target backup account;
  • a creating unit configured to create a shared backup area corresponding to the shared account according to the shared account setting request
  • An adding unit configured to add target shared data in a private backup area corresponding to the target backup account to the shared backup area
  • the synchronization unit is configured to receive a data synchronization request that is sent by the second terminal and that carries the shared account, and synchronize the target shared data in the shared backup area to the second terminal according to the data synchronization request.
  • an embodiment of the present invention provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are adapted to be loaded by a processor to perform a data synchronization method provided by any one of the embodiments of the present invention.
  • an embodiment of the present invention provides an electronic device, including a processor and a memory, where the memory stores a plurality of instructions, and the processor loads an instruction in the memory to execute any one of the embodiments of the present invention.
  • a method of synchronizing backup data provided.
  • an embodiment of the present invention provides a server, including a processor and a memory, where the memory stores a plurality of instructions, and the processor loads an instruction in the memory to perform any of the embodiments of the present invention. Another method of synchronizing backup data.
  • Embodiments of the present invention provide a method, an apparatus, a storage medium, an electronic device, and a server for synchronizing backup data, which can improve the security of backup data.
  • FIG. 1 is a first flowchart of a method for synchronizing backup data according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a login interface according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a backup interface according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a shared account setting interface according to an embodiment of the present invention.
  • FIG. 5 is a second flowchart of a method for synchronizing backup data according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a first structure of a backup data synchronization system according to an embodiment of the present invention.
  • FIG. 7 is a third flowchart of a method for synchronizing backup data according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a third structure of a synchronization device for backing up data according to an embodiment of the present invention.
  • FIG. 9 is a fourth structural diagram of a synchronization device for backing up data according to an embodiment of the present invention.
  • FIG. 10 is a fifth structural diagram of a synchronization device for backing up data according to an embodiment of the present invention.
  • FIG. 11 is a sixth structural diagram of a synchronization device for backing up data according to an embodiment of the present invention.
  • FIG. 12 is a seventh structural diagram of a synchronization device for backing up data according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of an eighth structure of a synchronization device for backing up data according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • the embodiment of the invention provides a method for synchronizing backup data, including:
  • the synchronization method further includes: after receiving the shared account adding instruction, before acquiring the shared account to be added, the synchronization method further includes:
  • the step of obtaining the shared account to be added according to the shared account adding instruction is performed.
  • the sharing setting request further carries at least one of the authentication information, the sharing time information, the attribute information, and the operation authority; and the synchronization method adds a corresponding to the target backup account.
  • the method further includes at least one of the following steps:
  • the synchronization device may be integrated into a terminal or other device that needs to perform backup data synchronization.
  • the terminal may be a mobile phone, a tablet computer or the like.
  • the manner in which the synchronization device is integrated in the terminal may be various, for example, it may be installed in the terminal in the form of a terminal application.
  • the method in this embodiment may further include the process of logging in to the target backup account, as follows:
  • the backup account and its corresponding authentication information may be obtained, and then the account login request is sent to the cloud server according to the target backup account and the corresponding authentication information.
  • the method for obtaining the backup account and the authentication information may be various.
  • the user may input the backup account and the corresponding authentication information input by the user, or may be automatically obtained, for example, may be locally stored from the terminal.
  • the server automatically obtains the backup account and authentication information.
  • the cloud backup application can provide a login interface, which includes an account input interface, an authentication input interface, and a login interface. Then, the cloud backup application can obtain a target backup account input by the user through the account input interface.
  • the authentication input interface obtains the authentication information input by the user, and when receiving the login instruction triggered by the login interface, the user may send an account login request to the cloud server according to the login instruction, the target backup account, and the authentication information.
  • the interface has various forms of expression, such as input boxes, icons, etc., and the specific form can be set according to actual needs.
  • the login response information includes first indication information that allows login to the target backup account, or second indication information that denies login to the target backup account. For example, when the cloud server fails to verify the authentication information, the second indication information is sent, and when the verification succeeds, the first indication information is sent.
  • the step of “registering the target backup account according to the login response information” may include: when the login response information includes the first indication information, logging in to the target backup account.
  • the shared account addition instruction may be triggered by the operation of the user, or may be triggered by the system.
  • the shared account adding command can be triggered through the interface.
  • the cloud backup application can provide a shared account adding interface in the backup main interface, so that the user can add a shared account through the account adding interface. That is, the step of “receiving the shared account adding instruction” may include: receiving a shared account adding instruction triggered by the user adding the interface through the shared account.
  • the shared account has various forms of adding interfaces, such as an input box and an icon button.
  • the shared account may be input by the user or randomly generated by itself.
  • the shared account may be automatically obtained according to the shared account adding instruction, or the cloud backup application may provide a shared account adding interface after receiving the account adding instruction, and the shared account adding interface has a shared account input interface, so that the user
  • the shared account to be added may be input through the shared account input interface, that is, the step of "adding a shared account to be added according to the shared account adding instruction" may include:
  • the shared account input by the user is obtained through the shared account input interface.
  • the embodiment may further perform verification of the authentication information such as the password before adding the shared account. If the verification is passed, the shared account is added. That is, after receiving the shared account adding instruction, before obtaining the shared account to be added, before adding the shared account to the target backup account, the synchronization method further includes:
  • the step of obtaining the shared account to be added according to the shared account adding instruction is performed.
  • the method for verifying the authentication information input by the user may be multiple.
  • the verification request may be sent to the cloud server, where the verification request carries the target backup account and the authentication information input by the user, and then receives the cloud server according to the The verification result returned by the verification request, if the verification result is the verification pass, the step of adding the corresponding shared account to the target backup account is performed, for example, the jump to the shared account addition interface may be performed.
  • the shared account can be bound to the target backup account.
  • the receiving account setting sends a command, and then generating a shared account setting request carrying the target backup account and the shared account according to the command, and sending the shared account setting request to the cloud server.
  • the synchronization method in this embodiment may further include at least one of the following steps between steps 103 and 104:
  • the sharing setting request may also carry the authentication information.
  • the authentication information may be information such as a password or a biometric. Setting authentication information can improve the security of shared accounts and shared data.
  • the authentication setting instruction may be received, and then the authentication information corresponding to the shared account is set according to the authentication setting instruction.
  • the authentication information input by the user is obtained according to the authentication setting instruction, and the authentication information input by the user is used as the authentication information corresponding to the shared account.
  • the method for setting the shared account may be various.
  • the embodiment may provide a shared account. Set the interface, and set the corresponding setting interface on the interface, so that the user can set the shared account by setting the interface.
  • the shared account setting interface may include: an authentication setting interface (ie, “password setting” in FIG. 4).
  • the authentication setting information input by the user through the authentication setting interface may be received, and then, The authentication information corresponding to the shared account is set according to the authentication setting information, for example, the input authentication information is used as the authentication information corresponding to the shared account.
  • the sharing setting request may also carry the sharing time information.
  • Setting sharing time information can increase the security of shared data and save storage space on the cloud server.
  • the sharing time setting instruction may be received, and then the sharing time information corresponding to the shared account is set according to the sharing time setting instruction.
  • the time information input by the user may be received according to the sharing time setting instruction, or the time information selected by the user may be acquired, and then the sharing time information is set according to the time information input by the user or the selected time information.
  • the shared account setting interface may include: a time setting interface (ie, “shared time setting” in FIG. 4).
  • a time setting instruction triggered by the user to set the interface may be received, and then, according to the The time setting instruction acquires the time setting information input by the user, and finally sets the sharing time information corresponding to the shared account according to the time setting information, for example, the input time information is used as the shared time information corresponding to the shared account.
  • the sharing setting request may also carry attribute information of the data to be shared.
  • Setting attribute information can increase the speed and accuracy of data sharing.
  • the attribute setting instruction may be received, and then the attribute information of the data to be shared corresponding to the shared account is set according to the attribute setting instruction.
  • the plurality of candidate attribute information may be acquired according to the attribute setting instruction, and then the target attribute information is selected from the plurality of candidate attribute information, and the attribute information of the data to be shared corresponding to the shared account is set according to the target attribute information.
  • the target attribute information input by the user is obtained according to the attribute setting instruction, and then the attribute information of the data to be shared corresponding to the shared account is set according to the target attribute information.
  • the shared account setting interface may include: an attribute setting interface (ie, “data attribute setting” in FIG. 4), and at this time, an attribute setting instruction triggered by the user through the attribute setting interface may be received, and then, according to the attribute
  • the setting instruction provides an attribute list, receives a selection instruction input by the user for the attribute list, selects target attribute information from the attribute list according to the selection instruction, and finally sets attribute information of the to-be-shared data corresponding to the shared account according to the target attribute information.
  • the attribute information may include a data type, a data identification, and the like.
  • the sharing setting request can also carry the operation authority.
  • Setting operational permissions ensures the accuracy and consistency of data synchronization.
  • the operation authority setting instruction may be received, and then the attribute information of the to-be-shared data corresponding to the shared account is set according to the target attribute information according to the operation authority setting instruction.
  • the operation authority setting information input by the user may be acquired according to the operation authority setting instruction, and the attribute information of the data to be shared is set according to the operation authority setting information.
  • a plurality of candidate operation right items may be acquired according to the operation authority setting instruction, and then the target operation right item is selected from the plurality of candidate operation right items, and the operation right item corresponding to the shared account is set according to the target operation right item.
  • the candidate operation rights items include: a download right item, an upload right item, a data synchronization right item, a data change right item, and the like.
  • the shared account setting interface may include: an operation authority setting interface, and at this time, an operation permission setting instruction triggered by the user through the operation authority setting interface may be received, and then an operation permission list is provided according to the operation authority setting instruction ( Include a plurality of candidate operation rights), receive selection information of the user for the operation permission list, select a target operation right item from the operation authority list according to the selection information, and finally set an operation right corresponding to the shared account according to the target operation right item. item.
  • the steps (1)-(4) above may be arbitrarily combined, and the shared account interface may set the setting interface of the step, and the sharing setting request may also carry corresponding information.
  • the shared account setting interface is further provided with a setting sending interface.
  • the sending interface “setting completion” triggers the setting sending command, and the terminal can send according to the setting.
  • the instruction generates a sharing setting request carrying a target backup account, a shared account, (authentication information, sharing time information, attribute information, and operation authority), and sends the request to the cloud server.
  • the shared account adding instruction is received, and then the shared account to be added is obtained according to the shared account adding instruction, and the shared account is added to the target backup account to the cloud.
  • the server sends a shared account setting request carrying the target backup account and the shared account, so that the cloud server performs backup data synchronization according to the shared account setting request.
  • the solution can synchronize the backup data based on the shared account associated with the backup account and the shared backup area of the shared account.
  • other synchronous terminals can only obtain the backup data in the shared backup area, and cannot obtain the backup account.
  • the backup data in the private backup area can prevent the backup data from leaking. Therefore, the security of the backup data can be improved compared with the prior art.
  • the embodiment of the invention further provides another method for synchronizing backup data, including:
  • the shared account setting request further carries attribute information of the data to be shared corresponding to the shared account
  • Adding the target shared data in the private backup area corresponding to the target backup account to the shared backup area including:
  • the shared account setting request further carries the first authentication information corresponding to the shared account;
  • the data synchronization request further carries the second authentication information corresponding to the shared account;
  • the synchronization method further includes:
  • the shared account setting request further carries the shared time information corresponding to the shared account; after receiving the shared account setting request, the synchronization method further includes:
  • the shared account setting request further carries an operation right corresponding to the shared account
  • the synchronization method further includes:
  • the synchronization device may be integrated into a server or other device that needs to perform backup data synchronization, and the server may be a cloud server or the like.
  • the flowchart of the synchronization method of the backup data may be specifically as follows:
  • the shared account setting request sent by the first terminal may be received.
  • the target backup account may be a cloud backup account, and the terminal login to the backup account may perform operations such as uploading or downloading backup data.
  • the shared account is an associated account of the target backup account, which is used to share the backup data. In some embodiments, the shared account can be used as a subordinate account or sub-account of the target backup account.
  • a method for creating a shared backup area may be used.
  • a storage area may be designated as a shared backup area, that is, the step of creating a shared backup area corresponding to the shared account according to the shared account setting request may include:
  • a storage area may be allocated from the backup storage area corresponding to the target backup account according to the shared account setting request. For example, an empty storage area can be divided from the backup storage area corresponding to the target backup account.
  • the target shared data that needs to be shared may be first determined from the private backup area corresponding to the target backup account, and then the target share is added to the shared backup area.
  • the target shared data can be transferred to the shared backup area, or the target shared data can be copied to the shared backup area. Set according to actual needs.
  • the method for determining the target shared data to be shared is also various.
  • the unencrypted backup data in the private backup area may be determined as the target shared data, that is, the step “the private backup area corresponding to the target backup account”.
  • Adding target shared data to the shared backup area can include:
  • the backup data that needs to be shared can be set by the user.
  • the user can select the shared data to be shared on the terminal after adding the shared account, and after the user selects, the attribute information such as the identifier of the shared data selected by the user can be sent.
  • the cloud server determines the target shared data; that is, the shared account setting request may further carry the attribute information of the data to be shared corresponding to the shared account, and the step is to “take the target backup account corresponding to the private backup area.
  • Adding target shared data to the shared backup area can include:
  • the attribute information of the data may include information such as an identifier of the data, a type of the data, and the like.
  • the step of “determining the target shared data in the private backup area corresponding to the target backup account according to the attribute information” may include:
  • the corresponding target shared data is determined in the private backup area according to the data type of the backup data and the target data type.
  • the private backup area corresponding to the target backup account and the shared backup area corresponding to the shared account may be two storage areas or units that are isolated and independent from each other, for example, other may be on different storage media.
  • the second terminal and the first terminal are different terminals, for example, different terminals of the same user, terminals of different users, and the like.
  • the step of “synchronizing the target shared data in the shared backup area to the second terminal according to the data synchronization request” may include: sending the shared target data in the shared backup area to the second terminal according to the data synchronization request.
  • the embodiment may send the attribute information of the data in the shared backup area, such as an identifier, to the second terminal according to the data synchronization request, so that the second terminal performs selection, and then receives the second terminal. And the selected information is sent to the second terminal according to the selection information to implement data synchronization, that is, the step “synchronizes the target shared data in the shared backup area to the second according to the data synchronization request.
  • the terminal may include:
  • the cloud server may send the identifier of all the shared data in the shared backup area to the second terminal (which may be in the form of a list), and the second terminal may select the corresponding target identifier from the identifier, and provide feedback.
  • the cloud server may send corresponding target shared data in the shared backup area to the second terminal according to the target identifier to complete data synchronization.
  • authentication information such as a password may be set for the shared account, so that other terminals need to input or send correct authentication information when data synchronization is required, thereby ensuring protection.
  • the data security that is, the shared account setting request may further carry the first authentication information corresponding to the shared account, and the data synchronization request may further carry the second authentication information corresponding to the shared account;
  • the method of the embodiment of the present invention may further include: before the step of “synchronizing the data in the shared backup area to the second terminal according to the data synchronization request”.
  • the authentication information may include information such as a password, biometric information (fingerprint, iris, etc.).
  • the cloud server may save the first authentication information, and after receiving the data synchronization request, may extract the first authentication information from the storage, and according to the first The authentication information verifies the second authentication information carried in the request (that is, the matching process described above), and if the verification passes, the data synchronization is performed; otherwise, the data synchronization is not performed.
  • the embodiment may also delete the target shared data in the shared backup area under a certain time condition.
  • the shared account setting request also carries the shared account corresponding to the shared account.
  • the time information after receiving the shared account setting request, the synchronization method of the embodiment may further include: deleting the target shared data in the shared backup area according to the current system time information and the shared time information.
  • the sharing time information may include a sharing period, that is, a valid time of sharing the data; in this case, the step of deleting the target sharing data in the shared backup area according to the current system time information and the sharing time information may include:
  • the shared time information can be set by the user of the first terminal according to actual needs. For example, the sharing period can be set to 2016-9-5. If the system time reaches 2016-9-5, the shared backup area can be deleted. Targets share data, which reduces the risk of theft of shared data over time and saves storage space.
  • the embodiment may limit the operation of the shared account for the synchronization user, so as to prevent the synchronization user from modifying the shared data under the shared account, thereby ensuring synchronization data.
  • the shared account setting request further carries the operation authority corresponding to the shared account.
  • the step “synchronizes the target shared data in the shared backup area to the second according to the data synchronization request.
  • the method in this embodiment may further include:
  • the operation authority may be a permission for the operation of the shared account by the terminal (other than the terminal that sets the shared account), and specifically, the operation permission of the shared data of the shared backup area of the shared terminal by the other terminal.
  • the operation authority may include a plurality of operation items (such as an operation item list) that may be allowed to be executed, and the operation authority may include at least one of a synchronization operation, an upload operation, a data modification operation, and the like.
  • the operation authority can be set according to the actual needs of the user.
  • the step of “determining whether the operation corresponding to the data synchronization request satisfies the operation authority” may include: determining whether the operation corresponding to the data synchronization request is in the operation item list, and if yes, satisfying the operation authority, If it does not meet the operation authority otherwise.
  • the embodiment of the present invention when receiving the shared account setting request sent by the first terminal, creates a shared backup area corresponding to the shared account according to the shared account setting request, and then, in the private backup area corresponding to the target backup account.
  • the target shared data is added to the shared backup area, and receives a data synchronization request that is sent by the second terminal and carries the shared account, and synchronizes the target shared data in the shared backup area to the second terminal according to the data synchronization request.
  • the solution can synchronize the backup data based on the shared account associated with the backup account and the shared backup area of the shared account.
  • the backup data When the backup data is synchronized based on the shared account, other synchronous terminals can only obtain the backup data in the shared backup area, and cannot obtain the backup account.
  • the backup data in the private backup area can prevent the backup data from leaking. Therefore, the security of the backup data can be improved compared with the prior art.
  • the synchronization device is integrated in the terminal in the foregoing embodiment, and another synchronization device in the foregoing embodiment is integrated into the server as an example for detailed description.
  • the server can be a cloud server for backup
  • the terminal can be a device such as a mobile phone, a tablet computer, or a laptop computer.
  • a backup data synchronization system including: a terminal 601, a terminal 602, a terminal 603, and a server 604; in the system, the terminal and the server 604 are connected through a network such as a wireless network. In other embodiments the system may also include more terminals.
  • the synchronization method of the present invention is described in detail below based on the backup data synchronization system. As shown in FIG. 7, a specific method for synchronizing backup data is as follows:
  • the terminal 601 logs in to the target backup account.
  • the process of the terminal 601 logging in to the target backup account may include:
  • the terminal 601 sends an account login request to the server 604, where the account login request carries the target backup account and its corresponding authentication information.
  • the server 604 returns login response information to the terminal 601 according to the account login request.
  • the terminal 601 logs in to the target backup account based on the login response information.
  • the login process of the target backup account may refer to the related description of the second embodiment.
  • the terminal 601 receives a shared account addition instruction.
  • the cloud backup application can provide a shared account adding interface in the main interface, so that the user can add a shared account through the account adding interface, that is, the step of “receiving the shared account adding instruction” may include: receiving the user to add an interface through the shared account.
  • the triggered shared account is added with an instruction.
  • the shared account has various forms of adding interfaces, such as an input box and an icon button.
  • the terminal 601 acquires a shared account to be added according to the shared account adding instruction.
  • the shared account can be input by the user, or can be randomly generated by the terminal 601.
  • the cloud backup application of the terminal may provide a shared account adding interface, and the shared account adding interface has a shared account input interface, so that the user can input the to-be-added through the shared account input interface. Shared account.
  • the terminal 601 adds the shared account to the target backup account, and the terminal 601 further sets first authentication information corresponding to the shared account, attribute information of the data to be shared, and operation authority.
  • the terminal 601 sends a shared account setting request to the server 604, where the shared account setting request carries the target backup account, the shared account, the first authentication information, the attribute information, and the operation authority.
  • the server 604 creates a shared backup area corresponding to the shared account according to the shared account setting request.
  • a storage area may be designated as a shared backup area, that is, the step “the server 604 creates a shared backup area corresponding to the shared account according to the shared account setting request”.
  • a storage area may be designated as a shared backup area, that is, the step “the server 604 creates a shared backup area corresponding to the shared account according to the shared account setting request”.
  • the server 604 divides a storage area according to the shared account setting request
  • the server 604 designates the storage area as the shared backup area corresponding to the shared account.
  • the server 604 determines, according to the attribute information, the target shared data that needs to be shared from the private backup area corresponding to the target backup account, and adds the target shared data to the shared backup area.
  • the terminal 602 or 603 logs in to the shared account, and sends a data synchronization request to the server 604.
  • the data synchronization request carries the shared account and the corresponding second authentication information.
  • the process of logging in to the shared account by the terminal 602 or 603 may include:
  • the terminal 602 or 603 logs in to obtain the shared account and its corresponding third authentication information
  • the terminal 602 or 603 logs in to the server 604 to send a shared account login request, and the shared account login request carries the shared account and the corresponding third authentication information;
  • the server 604 matches the first authentication information with the third authentication information, and if the matching is successful, sends the corresponding shared account login response information to the terminal 602 or 603;
  • the terminal 602 or 603 logs in to the shared account according to the shared account login response information.
  • the server 604 determines whether the operation corresponding to the data synchronization request satisfies the operation authority. If yes, the process proceeds to step 710. If not, the synchronization process ends.
  • the operation authority includes: synchronous operation and downloading, it may be determined at this time that the operation corresponding to the data synchronization request satisfies the operation authority.
  • the server 604 operation authority includes the upload operation authority, the server 604 refuses to process the upload request when the terminal 602 or 603 initiates the upload request.
  • the server 604 matches the first authentication information with the second authentication information. When the authentication information is successfully matched, the server 604 sends the target shared data in the shared backup area to the terminal 602 or 603.
  • the server 604 sends the attribute information of the shared data in the shared backup area to the terminal 602 or 603 according to the data synchronization request; the server 604 receives the synchronization selection information returned by the terminal 602 or 603 according to the attribute information of the shared data; The corresponding target shared data in the shared backup area is sent to the terminal 602 or 603 according to the synchronization selection information.
  • the server 604 may further delete the target shared data in the shared backup area according to the current system time information and the shared time information.
  • the shared time information may include a sharing period, that is, an effective time of sharing data.
  • the server 604 determines whether the current system time has reached the sharing deadline, and if so, deletes the target shared data in the shared backup area. To reduce the risk of theft caused by the long-term existence of shared data, and to save storage space on the server.
  • the embodiment of the present invention uses the terminal 601 to send a shared account request to the server 604.
  • the server 604 creates a shared backup area corresponding to the shared account according to the shared account setting request, and then the server 604 uses the private backup corresponding to the target backup account.
  • the target shared data in the area is added to the shared backup area, and the server 604 receives the data synchronization request that is sent by the terminal 602 or 603 and carries the shared account, and synchronizes the target shared data in the shared backup area according to the data synchronization request.
  • Terminal 602 or 603. The solution can synchronize the backup data based on the shared account associated with the backup account and the shared backup area of the shared account.
  • the backup data When the backup data is synchronized based on the shared account, other synchronous terminals can only obtain the backup data in the shared backup area, and cannot obtain the backup account.
  • the backup data in the private backup area can prevent the backup data from leaking. Therefore, the security of the backup data can be improved compared with the prior art.
  • the embodiment of the invention further provides a synchronization device for backing up data, comprising:
  • a receiving unit configured to receive a shared account setting request sent by the first terminal, where the shared account setting request carries a target backup account and a shared account corresponding to the target backup account;
  • a creating unit configured to create a shared backup area corresponding to the shared account according to the shared account setting request
  • An adding unit configured to add target shared data in a private backup area corresponding to the target backup account to the shared backup area
  • the synchronization unit is configured to receive a data synchronization request that is sent by the second terminal and that carries the shared account, and synchronize the target shared data in the shared backup area to the second terminal according to the data synchronization request.
  • the shared account setting request further carries attribute information of the data to be shared corresponding to the shared account
  • the adding unit includes: a determining subunit and a copying subunit;
  • the determining subunit is configured to determine target shared data in a private backup area corresponding to the target backup account according to the attribute information;
  • the copying subunit is configured to copy the target shared data into the shared backup area.
  • the shared account setting request further carries the first authentication information corresponding to the shared account
  • the data synchronization request further carries the second authentication information corresponding to the shared account
  • the synchronization device further includes: a matching unit;
  • the matching unit is configured to: after the synchronization unit receives the data synchronization request, synchronize the data in the shared backup area to the second terminal according to the data synchronization request, and perform the second authentication The information is matched with the first authentication information;
  • the synchronization unit is configured to synchronize target shared data in the shared backup area to the second terminal according to the data synchronization request when the matching unit is successfully matched.
  • the shared account setting request further carries shared time information corresponding to the shared account;
  • the synchronization device further includes a deleting unit;
  • the deleting unit is configured to delete, after the receiving unit receives the shared account setting request, the target shared data in the shared backup area according to the current system time information and the shared time information.
  • the shared account setting request further carries an operation right corresponding to the shared account
  • the synchronization unit is configured to receive, by the second terminal, a data synchronization request that carries the shared account, and determine whether the operation corresponding to the data synchronization request satisfies the operation authority, and if yes, according to the data synchronization request
  • the target shared data in the shared backup area is synchronized to the second terminal.
  • the embodiment of the present invention further provides a synchronization device 80 for backing up data.
  • the synchronization device 80 includes a receiving unit 801, a creating unit 802, and an adding unit. 803 and synchronization unit 804 are as follows:
  • the receiving unit 801 is configured to receive a shared account setting request sent by the first terminal, where the shared account setting request carries a target backup account and a shared account corresponding to the target backup account;
  • a creating unit 802 configured to create a shared backup area corresponding to the shared account according to the shared account setting request;
  • the adding unit 803 is configured to add the target shared data in the private backup area corresponding to the target backup account to the shared backup area;
  • the synchronization unit 804 is configured to receive a data synchronization request that is sent by the second terminal and that carries the shared account, and synchronize the target shared data in the shared backup area to the second terminal according to the data synchronization request.
  • the shared account setting request in this embodiment further carries the attribute information of the data to be shared corresponding to the shared account, where the adding unit 803 may include: a determining subunit and a copying subunit;
  • the determining subunit is configured to determine target shared data in a private backup area corresponding to the target backup account according to the attribute information;
  • the copy subunit is configured to copy the target shared data into the shared backup area.
  • the shared account setting request in this embodiment further carries the first authentication information corresponding to the shared account, and the data synchronization request further carries the second corresponding to the shared account.
  • Authentication information referring to FIG. 9, the synchronization device 80 may further include a matching unit 805;
  • the matching unit 805 is configured to: after the synchronization unit 804 receives the data synchronization request, synchronize the data in the shared backup area to the second terminal according to the data synchronization request, and the second authentication information and the first The authentication information is matched;
  • the synchronization unit 804 is configured to synchronize the target shared data in the shared backup area to the second terminal according to the data synchronization request when the matching unit is successfully matched.
  • the shared account setting request also carries the shared time information corresponding to the shared account in this embodiment; referring to FIG. 10, the synchronization device 80 further includes a deleting unit 806;
  • the deleting unit is configured to delete the target shared data in the shared backup area according to the current system time information and the shared time information after the receiving unit 801 receives the shared account setting request.
  • the shared account setting request in this embodiment also carries the operation authority corresponding to the shared account
  • the synchronization device may further include: a determining unit
  • the determining unit is configured to determine, after the synchronization unit 804 receives the data synchronization request, the data in the shared backup area is synchronized to the second terminal according to the data synchronization request, and determine whether the operation corresponding to the data synchronization request satisfies the operation.
  • the synchronization unit 804 may be specifically configured to: when the determining unit determines to be YES, synchronize the data in the shared backup area to the second terminal according to the data synchronization request.
  • the foregoing units may be implemented as a separate entity, or may be implemented in any combination, and may be implemented as the same or a plurality of entities.
  • the foregoing method embodiments and details are not described herein.
  • the synchronization device can be specifically integrated into a server, such as a cloud server.
  • the receiving unit 801 receives the shared account setting request sent by the first terminal, where the shared account setting request carries the target backup account and the shared account corresponding to the target backup account, and then the creation unit 802 creates a request according to the shared account setting request.
  • the shared backup area corresponding to the shared account is added by the adding unit 803 to the shared backup area in the private backup area corresponding to the target backup account, and the synchronization unit 804 receives the shared account sent by the second terminal.
  • Data synchronization request and synchronize the target shared data in the shared backup area to the second terminal according to the data synchronization request.
  • the solution can synchronize the backup data based on the shared account associated with the backup account and the shared backup area of the shared account.
  • the backup data When the backup data is synchronized based on the shared account, other synchronous terminals can only obtain the backup data in the shared backup area, and cannot obtain the backup account.
  • the backup data in the private backup area can prevent the backup data from leaking. Therefore, the security of the backup data can be improved compared with the prior art.
  • the embodiment of the invention further provides another synchronization device for backing up data, including:
  • An instruction receiving unit configured to receive a shared account adding instruction after logging in to the target backup account
  • An obtaining unit configured to acquire a shared account to be added according to the shared account adding instruction
  • An account adding unit configured to add the shared account to the target backup account
  • a sending unit configured to send, to the cloud server, a shared account setting request that carries the target backup account and the shared account, so that the cloud server performs backup data synchronization according to the shared account setting request.
  • the synchronization device further includes a verification unit
  • the verification unit is configured to: after the instruction receiving unit receives the shared account adding instruction, obtain the authentication information corresponding to the target backup account input by the user, and obtain the authentication information input by the user, before acquiring the shared account to be added authenticating;
  • the obtaining unit is specifically configured to acquire a shared account to be added according to the shared account adding instruction when the verification unit passes the verification.
  • the synchronization device further includes: a verification unit;
  • the verification unit is configured to: after the instruction receiving unit receives the shared account adding instruction, obtain the authentication information corresponding to the target backup account input by the user, and obtain the authentication information input by the user, before acquiring the shared account to be added authenticating;
  • the obtaining unit is specifically configured to acquire a shared account to be added according to the shared account adding instruction when the verification unit passes the verification.
  • the embodiment of the present invention further provides another synchronization device 90 for backing up data.
  • the synchronization device 90 includes an instruction receiving unit 901, an obtaining unit 902,
  • the account adding unit 903 and the sending unit 904 are as follows:
  • the instruction receiving unit 901 is configured to receive a shared account adding instruction after logging in the target backup account
  • the obtaining unit 902 is configured to acquire a shared account to be added according to the shared account adding instruction
  • the sending unit 904 is configured to send, to the cloud server, a shared account setting request that carries the target backup account and the shared account, so that the cloud server performs backup data synchronization according to the shared account setting request.
  • the synchronization device 90 of this embodiment may further include: a verification unit 905;
  • the verification unit 905 is configured to: after the instruction receiving unit 901 receives the shared account adding instruction, the obtaining unit 902 obtains the authentication information corresponding to the target backup account input by the user before acquiring the shared account to be added; and authenticating the input by the user Information for verification;
  • the obtaining unit 902 is specifically configured to acquire a shared account to be added according to the shared account adding instruction when the verification unit passes the verification.
  • the synchronization device 90 of this embodiment may further include a setting list 906;
  • the setting unit 906 is configured to perform at least one of the following steps after the account adding unit 903 adds the corresponding shared account to the target backup account, and before the sending unit 904 sends the shared account setting request to the cloud server:
  • the corresponding sharing setting request further carries at least one of the authentication information, the sharing time information, the attribute information, and the operation authority.
  • the foregoing units may be implemented as a separate entity, or may be implemented in any combination, and may be implemented as the same or a plurality of entities.
  • the foregoing method embodiments and details are not described herein.
  • the synchronization device can be specifically integrated into the terminal, such as a mobile phone, a notebook computer, a tablet computer, and the like.
  • the instruction receiving unit 901 receives the shared account adding instruction after logging in the target backup account, and then the obtaining unit 902 obtains the shared account to be added according to the shared account adding instruction, and the account adding unit 903 is used by the obtaining unit 903.
  • the shared account is added to the target backup account, and the sending unit 904 sends a shared account setting request carrying the target backup account and the shared account to the cloud server, so that the cloud server synchronizes the backup data according to the shared account setting request.
  • the solution can synchronize the backup data based on the shared account associated with the backup account and the shared backup area of the shared account.
  • the backup data When the backup data is synchronized based on the shared account, other synchronous terminals can only obtain the backup data in the shared backup area, and cannot obtain the backup account.
  • the backup data in the private backup area can prevent the backup data from leaking. Therefore, the security of the backup data can be improved compared with the prior art.
  • An embodiment of the present invention further provides a server, including a processor and a memory, where the memory stores a plurality of instructions, and the processor loads the instructions in the memory for performing any one of the embodiments of the present invention.
  • the synchronization method of the server In an embodiment, the embodiment provides a server, wherein the synchronization device of the second embodiment can be integrated.
  • FIG. 14 it is a schematic structural diagram of a server according to an embodiment of the present invention. :
  • the server 140 can include one or more processing core processors 141, one or more computer readable storage media memories 142, radio frequency (Radio) Frequency, RF) circuit 143, power supply 144, input unit 145, and display unit 146 and the like. It will be understood by those skilled in the art that the server structure illustrated in FIG. 14 does not constitute a limitation to the server, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements. among them:
  • the processor 141 is the control center of the server, connecting various portions of the entire server using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 142, and recalling data stored in the memory 142, Execute the server's various functions and process data to monitor the server as a whole.
  • the processor 141 may include one or more processing cores; preferably, the processor 141 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
  • the modem processor primarily handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 141.
  • the memory 142 can be used to store software programs and modules, and the processor 141 executes various functional applications and data processing by running software programs and modules stored in the memory 142.
  • the RF circuit 143 can be used for receiving and transmitting signals during the transmission and reception of information, in particular, after receiving the downlink information of the base station, and processing it by one or more processors 141; in addition, transmitting data related to the uplink to the base station.
  • the server also includes a power source 144 (such as a battery) that supplies power to the various components.
  • the power source can be logically coupled to the processor 141 via a power management system to manage functions such as charging, discharging, and power management through the power management system.
  • the power supply 144 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
  • the server can also include an input unit 145 that can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • an input unit 145 can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • the server can also include a display unit 146 that can be used to display information entered by the user or information provided to the user and various graphical user interfaces of the server, which can be represented by graphics, text, icons, video, and It is composed of any combination.
  • the display unit 148 can include a display panel, and optionally, a liquid crystal display can be used. (LCD, Liquid Crystal Display), Organic Light Emitting Diode (OLED, Organic Light-Emitting) Diode) and other forms to configure the display panel.
  • LCD Liquid Crystal Display
  • OLED Organic Light Emitting Diode
  • the processor 141 in the server loads the executable file corresponding to the process of one or more applications into the memory 142 according to the following instructions, and is stored in the memory by the processor 141.
  • the application in 142 thus implementing various functions, as follows:
  • the shared account setting request carries the target backup account and the shared account corresponding to the target backup account
  • the shared backup area corresponding to the shared account is created, and the target is created.
  • the target shared data in the private backup area corresponding to the backup account is added to the shared backup area, and receives a data synchronization request that is sent by the second terminal and carries the shared account, and shares the target in the shared backup area according to the data synchronization request.
  • the data is synchronized to the second terminal.
  • the shared account setting request further carries attribute information of the data to be shared corresponding to the shared account; and the target shared data in the private backup area corresponding to the target backup account is added to the share.
  • the backup area includes: determining target shared data in the private backup area corresponding to the target backup account according to the attribute information; and copying the target shared data into the shared backup area.
  • An embodiment of the present invention further provides an electronic device, including a processor and a memory, where the memory stores a plurality of instructions, and the processor loads an instruction in the memory for executing any one of the embodiments of the present invention.
  • a synchronization method is provided for an electronic device or terminal.
  • a terminal 15 which can integrate the synchronization device according to the first embodiment, and the terminal 15 can include radio frequency (RF, Radio).
  • Circuit 151 memory 152 including one or more computer readable storage media, input unit 153, display unit 154, sensor 155, audio circuit 156, wireless fidelity (WiFi, Wireless)
  • the Fidelity module 157 includes a processor 158 having one or more processing cores, a power source 159, and a camera 150. It will be understood by those skilled in the art that the terminal structure shown in FIG. 15 does not constitute a limitation to the terminal, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.
  • the radio frequency circuit 151 can be used for transmitting and receiving information, or receiving and transmitting signals during a call, in particular, after receiving downlink information of the base station, and processing it by one or more processors 158; in addition, transmitting data related to the uplink to the base station .
  • the radio frequency circuit 151 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a subscriber identity module (SIM, Subscriber Identity Module) Card, Transceiver, Coupler, Low Noise Amplifier (LNA, Low Noise) Amplifier), duplexer, etc.
  • SIM Subscriber Identity Module
  • the radio frequency circuit 151 can also communicate with the network and other devices through wireless communication.
  • the wireless communication can use any communication standard or protocol, including but not limited to the global mobile communication system (GSM, Global System of Mobile communication), General Packet Radio Service (GPRS, General Packet Radio) Service), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA, Wideband Code) Division Multiple Access), Long Term Evolution (LTE), e-mail, short message service (SMS, Short) Messaging Service) and so on.
  • GSM Global System of Mobile communication
  • GPRS General Packet Radio Service
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • SMS Short message service
  • Memory 152 can be used to store software programs as well as modules.
  • the processor 158 executes various functional applications and data processing by running software programs and modules stored in the memory 152.
  • the memory 152 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the terminal (such as audio data, phone book, etc.).
  • the memory 152 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 152 may also include a memory controller to provide access to memory 152 by processor 158 and input unit 153.
  • the input unit 153 can be configured to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • input unit 153 can include a touch-sensitive surface as well as other input devices.
  • Touch-sensitive surfaces also known as touch screens or trackpads, collect touch operations on or near the user (such as the user using a finger, stylus, etc., any suitable object or accessory on a touch-sensitive surface or touch-sensitive Operation near the surface), and drive the corresponding connecting device according to a preset program.
  • the touch sensitive surface may include two parts of a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 158 is provided and can receive commands from the processor 158 and execute them.
  • touch-sensitive surfaces can be implemented in a variety of types, including resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 153 may also include other input devices.
  • other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, a joystick, a fingerprint recognition module, and the like.
  • function keys such as a volume control button, a switch button, etc.
  • trackball such as a mouse, a joystick, a fingerprint recognition module, and the like.
  • Display unit 154 can be used to display information entered by the user or information provided to the user as well as various graphical user interfaces of the terminal, which can be composed of graphics, text, icons, video, and any combination thereof.
  • the display unit 154 can include a display panel, and optionally, a liquid crystal display (LCD, Liquid) can be used. Crystal Display), Organic Light-Emitting (OLED) Diode) and other forms to configure the display panel.
  • the touch-sensitive surface can cover the display panel, and when the touch-sensitive surface detects a touch operation thereon or nearby, it is transmitted to the processor 158 to determine the type of the touch event, and then the processor 158 is displayed according to the type of the touch event. A corresponding visual output is provided on the panel.
  • the touch-sensitive surface and display panel are implemented as two separate components to perform input and input functions, in some embodiments, the touch-sensitive surface can be integrated with the display panel to implement input and output functions.
  • the terminal may also include at least one type of sensor 155, such as a light sensor, motion sensor, and other sensors.
  • the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel according to the brightness of the ambient light, and the proximity sensor may close the display panel and/or the backlight when the terminal moves to the ear.
  • the gravity acceleration sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity.
  • gesture of the mobile phone such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.;
  • Other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like that can be configured in the terminal are not described herein.
  • the audio circuit 156 can provide an audio interface between the user and the terminal through a speaker and a microphone.
  • the audio circuit 156 can convert the received audio data into an electrical signal, which is transmitted to a speaker, and converted into a sound signal output by the speaker.
  • the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 156 and converted into
  • the audio data is then processed by the audio data output processor 158, transmitted via the RF circuit 151 to, for example, another terminal, or the audio data is output to the memory 152 for further processing.
  • the audio circuit 156 may also include an earbud jack to provide communication between the peripheral earphone and the terminal.
  • Wireless Fidelity is a short-range wireless transmission technology.
  • the terminal can help users to send and receive emails, browse web pages and access streaming media through the wireless fidelity module 157, which provides users with wireless broadband Internet access.
  • the wireless fidelity module 157 shows the wireless fidelity module 157, it can be understood that it does not belong to the essential configuration of the terminal, and can be omitted as needed within the scope of not changing the essence of the invention.
  • the processor 158 is the control center of the terminal, connecting various portions of the entire terminal using various interfaces and lines, executing or executing software programs and/or modules stored in the memory 152, and invoking data stored in the memory 152, executing The terminal's various functions and processing data, so as to monitor the terminal as a whole.
  • the processor 158 may include one or more processing cores; preferably, the processor 158 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
  • the modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 158.
  • the terminal also includes a power source 159 (such as a battery) that supplies power to the various components.
  • the power source can be logically coupled to the processor 158 through the power management system to manage functions such as charging, discharging, and power management through the power management system.
  • the power supply 159 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
  • the terminal further includes a camera 150 having a shooting function (such as a front camera, a rear camera, etc.).
  • a shooting function such as a front camera, a rear camera, etc.
  • the camera can be logically connected to the processor 158 through a video processing system, a camera driver, etc., thereby implementing functions such as photographing and imaging through a video processing system and a camera driver.
  • the terminal may also include a Bluetooth module or the like, and details are not described herein again.
  • the processor 158 in the terminal loads the executable file corresponding to the process of one or more applications into the memory 152 according to the following instructions, and is stored in the memory by the processor 158.
  • the application in 152 to implement various functions:
  • the shared account adding instruction is received, and then the shared account to be added is obtained according to the shared account adding instruction, the shared account is added for the target backup account, and the target backup account and the share are sent to the cloud server.
  • the shared account setting request of the account is such that the cloud server synchronizes the backup data according to the shared account setting request.
  • the method further includes: obtaining authentication information corresponding to the target backup account input by the user; and verifying the authentication information input by the user; If the verification is passed, the step of obtaining the shared account to be added according to the shared account adding instruction is performed.
  • the synchronization method further includes at least one of the following steps:
  • the corresponding sharing setting request further carries at least one of the authentication information, the sharing time information, the attribute information, and the operation authority.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Read only memory (ROM, Read Only Memory), Random Access Memory (RAM), disk or CD.
  • ROM Read only memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本发明实施例公开了一种备份数据的同步方法、装置、存储介质、电子设备及服务器;该方法在登录目标备份账号之后,接收共享账号添加指令,根据该指令获取共享账号,为目标备份账号添加共享账号,向云端服务器发送携带目标备份账号和共享账号的共享账号设置请求,使得云端服务器根据共享账号设置请求进行备份数据同步。

Description

备份数据的同步方法、装置、存储介质、电子设备及服务器
本申请要求于2016年10月25日提交中国专利局、申请号为201610942150.3、发明名称为“一种备份数据的同步方法和装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及云备份技术领域,具体涉及一种备份数据的同步方法、装置、存储介质、电子设备及服务器。
背景技术
云备份是一种新兴的云计算业务,云备份服务提供商通过虚拟化、分布式处理和宽带网络等技术,将网络中海量、异构的存储设备集合起来协同工作,共同对外提供数据存储备份服务。用户可以通过移动互联网和宽带互联网接入,实现对终端上大量和分散的文件或文件夹的集中存储、安全保管。
随着人们对云备份数据同步的要求不断提高,云备份数据同步在云备份中的重要性也逐渐变高。其中,云备份数据同步是将某个终端中的数据备份至云端服务器,并且通过云端服务器将该数据发送给其他终端,以实现终端之间的数据同步。
技术问题
本发明实施例提供一种备份数据的同步方法、装置、存储介质、电子设备及服务器,可以提高备份数据的安全性。
技术解决方案
第一方面,本发明实施例提供一种备份数据的同步方法,包括:
在登录目标备份账号之后,接收共享账号添加指令;
根据所述共享账号添加指令获取待添加的共享账号;
为所述目标备份账号添加所述共享账号;
向云端服务器发送携带所述目标备份账号和所述共享账号的共享账号设置请求,以使得所述云端服务器根据所述共享账号设置请求进行备份数据同步。
第二方面,本发明实施例还提供了一种备份数据的同步装置,包括:
指令接收单元,用于在登录目标备份账号之后,接收共享账号添加指令;
获取单元,用于根据所述共享账号添加指令获取待添加的共享账号;
账号添加单元,用于为所述目标备份账号添加所述共享账号;
发送单元,用于向所述云端服务器发送携带所述目标备份账号和所述共享账号的共享账号设置请求,以使得所述云端服务器根据所述共享账号设置请求进行备份数据同步。
第三方面,本发明实施例还提供另一种备份数据的同步方法,包括:
接收第一终端发送的共享账号设置请求,所述共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
根据所述共享账号设置请求创建所述共享账号对应的共享备份区域;
将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中;
接收第二终端发送的携带所述共享账号的数据同步请求,并根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
第四方面,本发明实施例还提供另一种备份数据的同步装置,包括:
接收单元,用于接收第一终端发送的共享账号设置请求,所述共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
创建单元,用于根据所述共享账号设置请求创建所述共享账号对应的共享备份区域;
添加单元,用于将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中;
同步单元,用于接收第二终端发送的携带所述共享账号的数据同步请求,并根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
第五方面,本发明实施例提供了一种存储介质,所述存储介质中存储有多条指令,所述指令适于由处理器加载以执行本发明实施例任一提供的数据同步方法。
第六方面,本发明实施例提供了一种电子设备,包括处理器和存储器,所述存储器存储有多条指令,所述处理器加载所述存储器中的指令用于执行本发明实施例任一提供的备份数据的同步方法。
第七方面,本发明实施例提供了一种服务器,包括处理器和存储器,所述存储器存储有多条指令,所述处理器加载所述存储器中的指令用于执行本发明实施例任一提供的另一备份数据的同步方法。
有益效果
本发明实施例提供一种备份数据的同步方法、装置、存储介质、电子设备及服务器,可以提高备份数据的安全性。
附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的备份数据的同步方法的第一种流程图。
图2是本发明实施例提供的一种登录界面的示意图。
图3是本发明实施例提供的一种备份界面的示意图。
图4是本发明实施例提供的一种共享账号设置界面的示意图。
图5是本发明实施例提供的备份数据的同步方法的第二种流程图。
图6是本发明实施例提供的备份数据同步系统的第一种结构示意图。
图7是本发明实施例提供的备份数据的同步方法的第三种流程图。
图8是本发明实施例提供的备份数据的同步装置的第三种结构示意图。
图9是本发明实施例提供的备份数据的同步装置的第四种结构示意图。
图10是本发明实施例提供的备份数据的同步装置的第五种结构示意图。
图11是本发明实施例提供的备份数据的同步装置的第六种结构示意图。
图12是本发明实施例提供的备份数据的同步装置的第七种结构示意图。
图13是本发明实施例提供的备份数据的同步装置的第八种结构示意图。
图14是本发明实施例提供的一种服务器的结构示意图。
图15是本发明实施例提供的一种终端的结构示意图。
本发明的最佳实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
本发明实施例提供了一种备份数据的同步方法,包括:
在登录目标备份账号之后,接收共享账号添加指令;
根据所述共享账号添加指令获取待添加的共享账号;
为所述目标备份账号添加所述共享账号;
向云端服务器发送携带所述目标备份账号和所述共享账号的共享账号设置请求,以使得所述云端服务器根据所述共享账号设置请求进行备份数据同步。
在一实施例中,在接收共享账号添加指令之后,获取待添加的共享账号之前,所述同步方法还包括:
获取用户输入的所述目标备份账号对应的鉴权信息;
对用户输入的鉴权信息进行验证;
若验证通过,则执行根据所述共享账号添加指令获取待添加的共享账号的步骤。
在一实施例中,所述共享设置请求还携带所述鉴权信息、共享时间信息、所述属性信息以及所述操作权限中的至少一种;则所述同步方法在为目标备份账号添加对应的共享账号之后,向云端服务器发送共享账号设置请求之前,所还包括以下步骤中的至少一种:
设置所述共享账号对应的鉴权信息;
设置所述共享账号对应的共享时间信息;
设置所述共享账号对应的待共享数据的属性信息;
设置所述共享账号对应的操作权限。
在一实施例中,将从一种备份数据的同步装置的角度进行描述,该同步装置具体可以集成终端或者其他需要进行备份数据同步的设备中,该终端可以为手机、平板电脑等。
其中,该同步装置集成在终端中的方式可以有多种,比如,可以以终端应用的形式安装在终端中。
如图1所示,一种备份数据的同步方法,具体流程如下:
101、在登录目标备份账号之后,接收共享账号添加指令。
在步骤101之前,本实施例方法还可以包括登录目标备份账号的过程,具体如下:
向云端服务器发送账号登录请求,该账号登录请求携带目标备份账号及其对应的鉴权信息;
接收该云端服务器根据该账号登录请求返回的登录响应信息,并根据该登录响应信息登录该目标备份账号。
具体地,可以获取备份账号及其对应的鉴权信息,然后,根据目标备份账号及其对应的鉴权信息向云端服务器发送账号登录请求。
其中,获取备份账号和鉴权信息的方式可以有多种,比如,可以为用户输入,即获取用户输入的备份账号及其对应的鉴权信息,也可以为自动获取,如可以从终端本地存储或者服务器中自动获取备份账号和鉴权信息。
例如,参考图2,云备份应用可以提供一登录界面,该登录界面包括账号输入接口、鉴权输入接口以及登录接口,然后,云备份应用可以通过账号输入接口获取用户输入的目标备份账号,通过鉴权输入接口获取用户输入的鉴权信息,在接收到用户通过该登录接口触发的登录指令时,可以根据登录指令、目标备份账号、以及鉴权信息向云端服务器发送账号登录请求。
其中,接口的表现形式有多种,比如,输入框、图标等形式,具体形式可以根据实际需求设定。
其中,登录响应信息包括允许登录目标备份账户的第一指示信息、或者拒绝登录目标备份账号的第二指示信息。比如,当云端服务器对鉴权信息验证失败时发送第二指示信息,验证成功时发送第一指示信息。
此时,步骤“根据该登录响应信息登录该目标备份账号”可以包括:当登录响应信息包括第一指示信息时,则登录该目标备份账号。
本实施例中共享账号添加指令可以由通过用户的操作触发, 也可以由系统自行触发。
比如,在实际应用中,共享账号添加指令可以通过接口触发,参考图3,云备份应用可以在备份主界面中提供一共享账号添加接口,这样用户便可以通过该账号添加接口添加共享账号,也即步骤“接收共享账号添加指令”可以包括:接收用户通过共享账号添加接口触发的共享账号添加指令。其中该共享账号添加接口的形式有多种,如输入框、图标按钮等形式。
102、根据该共享账号添加指令获取待添加的共享账号。
本实施例中,获取共享账号的方式有多种,比如该共享账号可以由用户输入,也可以自行随机生成。具体地,可以根据该共享账号添加指令自动获取共享账号,也可以在接收到账号添加指令之后云备份应用可以提供一共享账号添加界面,该共享账号添加界面设有共享账号输入接口,这样用户便可以通过共享账号输入接口输入待添加的共享账号,即步骤“根据该共享账号添加指令获取待添加的共享账号”可以包括:
生成一共享账号添加界面,该共享账号添加界面包括共享账号输入接口;
通过该共享账号输入接口获取用户输入的共享账号。
在一实施例中,为了提高备份账号以及备份数据的安全性,本实施例还可以在添加共享账号之前进行密码等鉴权信息的验证,若验证通过,则添加共享账号。也即在接收共享账号添加指令之后,获取待添加的共享账号之前,为目标备份账号添加共享账号之前,该同步方法还包括:
获取用户输入的该目标备份账号对应的鉴权信息;
对用户输入的鉴权信息进行验证;
若验证通过,则执行根据该共享账号添加指令获取待添加的共享账号的步骤。
具体地,对用户输入的鉴权信息进行验证的方式可以有多种,比如,可以向云端服务器发送验证请求,该验证请求携带目标备份账号以及用户输入的鉴权信息,然后,接收云端服务器根据该验证请求返回的验证结果,若验证结果为验证通过,则执行为目标备份账号添加对应的共享账号的步骤,如可以跳转进入共享账号添加界面。
103、为该目标备份账号添加该共享账号。
具体地,可以将共享账号与目标备份账号进行绑定。
104、向云端服务器发送携带该目标备份账号和该共享账号的共享账号设置请求,以使得该云端服务器根据该共享账号设置请求进行备份数据同步。
比如,接收账号设置发送指令,然后,根据该指令生成携带该目标备份账号和该共享账号的共享账号设置请求,向该云端服务器发送该共享账号设置请求。在一实施例中,为了提高共享账号以及共享数据的安全性,本实施例同步方法在步骤103和104之间,还可以包括如下步骤中的至少一种:
(1)、设置该共享账号对应的鉴权信息。
此时,共享设置请求还可以携带该鉴权信息。其中,鉴权信息可以为密码、生物特征等信息。设置鉴权信息可以提高共享账号以及共享数据的安全性。
具体地,可以接收鉴权设置指令,然后,根据该鉴权设置指令设置该共享账号对应的鉴权信息。比如,根据该鉴权设置指令获取用户输入的鉴权信息,将该用户输入的鉴权信息作为共享账号对应的鉴权信息。
本实施例中设置共享账号对应的(鉴权信息、共享信息、属性信息以及操作权限)的方式可以有多种,为了便于用户设置鉴权信息以及提升用户体验,本实施例可以提供一共享账号设置界面,并在该界面上上设置相应的设置接口,这样用户便可以通过设置接口对共享账号进行相应设置。
如,参考图4,共享账号设置界面可以包括:鉴权设置接口(即图4中的“密码设置”),此时,可以接收用户通过该鉴权设置接口输入的鉴权设置信息,然后,根据该鉴权设置信息设置共享账号对应的鉴权信息,如将输入的鉴权信息作为共享账号对应的鉴权信息。
(2)、设置该共享账号对应的共享时间信息。
此时,共享设置请求还可以携带该共享时间信息。设置共享时间信息可以提高共享数据的安全性以及节省云端服务器的存储空间。
具体地,可以接收共享时间设置指令,然后,根据该共享时间设置指令设置共享账号对应的共享时间信息。
比如,可以根据共享时间设置指令接收用户输入的时间信息、或者获取用户选择的时间信息,然后,根据用户输入的时间信息或者选择的时间信息设置共享时间信息。
例如,参考图4,共享账号设置界面可以包括:时间设置接口(即图4中的“共享时间设置”),此时,可以接收用户通过该时间设置接口触发的时间设置指令,然后,根据该时间设置指令获取用户输入的时间设置信息,最后,根据该时间设置信息设置共享账号对应的共享时间信息,例如将输入的时间信息作为共享账号对应的共享时间信息。
(3)、设置该共享账号对应的待共享数据的属性信息。
此时,共享设置请求还可以携带该待共享数据的属性信息。设置属性信息可以提高数据共享的速度以及准确性。
具体地,可以接收属性设置指令,然后,根据该属性设置指令设置该共享账号对应的待共享数据的属性信息。比如,可以根据该属性设置指令获取多个候选属性信息,然后,从多个候选属性信息中选取目标属性信息,根据该目标属性信息设置该共享账号对应的待共享数据的属性信息。又比如,根据该属性设置指令获取用户输入的目标属性信息,然后,根据该目标属性信息设置该共享账号对应的待共享数据的属性信息。
如,参考图4,共享账号设置界面可以包括:属性设置接口(即图4中的“数据属性设置”),此时,可以接收用户通过属性设置接口触发的属性设置指令,然后,根据该属性设置指令提供一属性列表,接收用户针对该属性列表输入的选择指令,根据该选择指令从属性列表中选取目标属性信息,最后,根据目标属性信息设置共享账号对应的待共享数据的属性信息。该属性信息可以包括数据类型、数据标识等等。
(4)、设置该共享账号对应的操作权限。
此时,共享设置请求还可以携带该操作权限。设置操作权限可以保证数据同步的准确性和一致性。
具体地,可以接收操作权限设置指令,然后,根据该操作权限设置指令设置根据该目标属性信息设置该共享账号对应的待共享数据的属性信息。又比如,可以根据操作权限设置指令获取用户输入的操作权限设置信息,根据该操作权限设置信息设置待共享数据的属性信息。
比如,可以根据操作权限设置指令获取多个候选操作权项,然后,从该多个候选操作权项中选取目标操作权项,根据该目标操作权项设置共享账号对应的操作权项。其中候选操作权项包括:下载权项、上传权项、数据同步权项、数据更改权项等等。
例如,参考图4,共享账号设置界面可以包括:操作权限设置接口,此时,可以接收用户通过该操作权限设置接口触发的操作权限设置指令,然后,根据操作权限设置指令提供一操作权限列表(包括多个候选操作权项),接收用户针对该操作权限列表的选择信息,根据该选择信息从操作权限列表中选取目标操作权项,最后,根据该目标操作权项设置共享账号对应的操作权项。
以上(1)-(4)的步骤可以任意组合,共享账号界面可以设置步骤的设置接口,共享设置请求还可以携带相应的信息。
参考图4,本实施例中共享账号设置界面还设有设置发送接口,在用户针对共享账号设置完信息之后,可以通过该设置发送接口“设置完成”触发设置发送指令,终端可以根据该设置发送指令生成携带目标备份账号、共享账号、(鉴权信息、共享时间信息、属性信息以及操作权限中的至少一种)的共享设置请求,并向云端服务器发送该请求。
由上可知,本发明实施例采用在登录目标备份账号之后,接收共享账号添加指令,然后,根据该共享账号添加指令获取待添加的共享账号,为该目标备份账号添加该共享账号,向该云端服务器发送携带该目标备份账号和该共享账号的共享账号设置请求,以使得该云端服务器根据该共享账号设置请求进行备份数据同步。该方案可以基于备份账号关联的共享账号以及共享账号的共享备份区域实现备份数据同步,在基于共享账号进行备份数据同步时,其他同步终端只能获取共享备份区域内的备份数据,无法获取备份账号的私有备份区域内的备份数据,可以防止备份数据发生泄漏,因此,相对于现有技术而言,可以提高备份数据的安全性。本发明实施例还提供了另一种备份数据的同步方法,包括:
接收第一终端发送的共享账号设置请求,所述共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
根据所述共享账号设置请求创建所述共享账号对应的共享备份区域;
将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中;
接收第二终端发送的携带所述共享账号的数据同步请求,并根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
在一实施例中,所述共享账号设置请求还携带所述共享账号对应的待共享数据的属性信息;
所述将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中,包括:
根据所述属性信息在所述目标备份账号对应的私有备份区域中确定目标共享数据;
将所述目标共享数据复制到所述共享备份区域中。
在一实施例中,所述共享账号设置请求还携带所述共享账号对应的第一鉴权信息;所述数据同步请求还携带所述共享账号对应的第二鉴权信息;
在接收到数据同步请求之后,根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端之前,所述同步方法还包括:
将所述第二鉴权信息与所述第一鉴权信息进行匹配;
若匹配成功,则执行根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端的步骤。
在一实施例中,所述共享账号设置请求还携带共享账号对应的共享时间信息;在接收到共享账号设置请求之后,所述同步方法还包括:
根据当前系统时间信息和所述共享时间信息删除所述共享备份区域中的目标共享数据。
在一实施例中,所述共享账号设置请求还携带共享账号对应的操作权限;
在接收到数据同步请求之后,根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端之前,所述同步方法还包括:
判断所述数据同步请求对应的操作是否满足所述操作权限;
若是,则执行根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端的步骤。
在一实施例中,将从另一种备份数据的同步装置角度进行描述,该同步装置具体可以集成服务器或者其他需要进行备份数据同步的设备中,该服务器可以为云端服务器等。
如图5所示,该备份数据的同步方法的流程图具体可以如下:
201、接收第一终端发送的共享账号设置请求,该共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号。
比如,可以在第一终端登录该目标备份账号之后,接收第一终端发送的共享账号设置请求。
其中,目标备份账号可以为云备份账号,终端登录该备份账号可以进行上传或者下载备份数据等操作。该共享账号为目标备份账号的关联账号,其用于实现备份数据的共享,在一些实施方式中,该共享账号可以作为目标备份账号的从属账号或子账号。
202、根据该共享账号设置请求创建该共享账号对应的共享备份区域。
本实施例中,创建共享备份区域的方式有多种,比如,可以指定一个存储区域作为共享备份区域,也即步骤“根据该共享账号设置请求创建该共享账号对应的共享备份区域”可以包括:
根据共享账号设置请求划分一存储区域;
将该存储区域指定为该共享账号对应的共享备份区域。
具体地,可以根据共享账号设置请求从目标备份账号对应的备份存储区域中划分出一存储区域。比如,可以从目标备份账号对应的备份存储区域中划分出一空的存储区域。
203、将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中。
具体地,可以先从该目标备份账号对应私有备份区域中确定需要共享的目标共享数据,然后,在将该目标共享添加到共享备份区域。
其中,将目标共享数据添加至共享备份区域的方式有多种,比如,可以将目标共享数据转移到共享备份区域,或者,也可以将目标共享数据复制到共享备份区域中,具体的添加方式可以根据实际需求设定。
本实施例中确定需要共享的目标共享数据的方式也有多种,比如,可以将私有备份区域内未加密的备份数据确定为目标共享数据,也即步骤“将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中”可以包括:
在该目标备份账号对应的私有备份区域中确定未加密的备份数据;
将未加密的备份数据添加子该共享备份区域。
又比如,需要共享的备份数据可以由用户设定,如用户可以在添加共享账号之后在终端上选择需要共享的共享数据,在用户选择之后,可以将用户选择的共享数据的标识等属性信息发送给云端服务器,以便云端服务器确定目标共享数据;也即该共享账号设置请求还可以携带该共享账号对应的待共享数据的属性信息,此时步骤“将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中”可以包括:
根据该属性信息在该目标备份账号对应的私有备份区域中确定目标共享数据;
将该目标共享数据复制到该共享备份区域中。
其中,数据的属性信息可以包括数据的标识、数据的类型等信息。例如,当属性信息包括目标数据类型时;步骤“根据该属性信息在该目标备份账号对应的私有备份区域中确定目标共享数据”可以包括:
获取该目标备份账号对应的私有备份区域中备份数据的数据类型;
根据备份数据的数据类型和目标数据类型在私有备份区域内确定相应的目标共享数据。
本实施例中,目标备份账号对应的私有备份区域和共享账号对应的共享备份区域可以为相互隔离且独立的两个存储区域或者单元,例如,其他可以在不同的存储介质上。
204、接收第二终端发送的携带该共享账号的数据同步请求,并根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端。
本实施例中,第二终端和第一终端为不同的终端,比如,可以为同一用户的不同终端,也可以为不同用户的终端等等。
其中,步骤“根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端”可以包括:根据数据同步请求将共享备份区域内的共享目标数据发送给第二终端。
具体地,为了提高数据同步的灵活性,本实施例可以根据数据同步请求将共享备份区域内的数据的属性信息如标识发送给第二终端,以便第二终端进行选择,然后,接收第二终端反馈的选择信息,并根据该选择信息将该目标共享数据发送给第二终端,以实现数据同步,也即步骤“根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端”可以包括:
根据该数据同步请求将该共享备份区域中共享数据的属性信息发送给第二终端;
接收该第二终端根据该共享数据的属性信息返回的同步选择信息;
根据该同步选择信息将该共享备份区域中相应的目标共享数据发送给该第二终端。
例如,云端服务器在接收到数据同步请求之后,可以将共享备份区域内所有共享数据的标识发送给第二终端(可以以列表形式),第二终端可以从标识中选取相应的目标标识,并反馈给云端服务器,云端服务器可以根据目标标识将共享备份区域内相应的目标共享数据发送给第二终端,以完成数据同步。
在一实施例中,为了提高数据以及账号的安全性,本实施例中还可以对共享账号设置密码等鉴权信息,以便其他终端需要数据同步时需要输入或发送正确的鉴权信息,进而保障数据安全,也即共享账号设置请求还可以携带该共享账号对应的第一鉴权信息,该数据同步请求还可以携带该共享账号对应的第二鉴权信息;
此时,接收到数据同步请求之后,步骤“根据该数据同步请求将该共享备份区域中的数据同步给该第二终端”之前,本实施例方法还可以包括:
将该第二鉴权信息与该第一鉴权信息进行匹配;
若匹配成功,则执行根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端的步骤。
其中,鉴权信息可以包括:密码、生物特征信息(指纹、虹膜等)等信息。
比如,云端服务器在接收到共享账号对应的第一鉴权信息之后,可以保存该第一鉴权信息,在接收到数据同步请求之后,可以从存储中提取第一鉴权信息,并根据第一鉴权信息对该请求中携带的第二鉴权信息进行验证(即上述的匹配过程),若验证通过,则进行数据同步,否则,不进行数据同步。
在一实施例中,为了提高数据安全以及节省存储空间,本实施例还可以在一定时间条件下删除共享备份区域内的目标共享数据,具体地,该共享账号设置请求还携带共享账号对应的共享时间信息,在接收到共享账号设置请求之后,本实施例同步方法还可以包括:根据当前系统时间信息和该共享时间信息删除该共享备份区域中的目标共享数据。
该共享时间信息可以包括共享期限,即共享数据的有效时间;此时,步骤“根据当前系统时间信息和该共享时间信息删除该共享备份区域中的目标共享数据”可以包括:
判断当前系统时间是否达到该共享期限,若是,则删除该共享备份区域中的目标共享数据。
该共享时间信息可以由第一终端的用户根据实际需求自行设定,比如,可以设置共享期限为2016-9-5,若系统时间到达2016-9-5时,可以自行删除共享备份区域中的目标共享数据,这样可以减少共享数据长时间存在导致的被盗风险,以及节省存储空间。
在一实施例中,为了提高同步数据的准确性和一致性,本实施例可以限制同步用户针对的共享账号的操作,以防止同步用户对共享账号下的共享数据进行改动,从而保证同步数据的准确性和一致性。具体地,该共享账号设置请求还携带共享账号对应的操作权限,此时,在接收到数据同步请求之后,步骤“根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端”之前,本实施例方法还可以包括:
判断该数据同步请求对应的操作是否满足该操作权限;
若是,则执行根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端的步骤。
其中,该操作权限可以为其他终端(除设置共享账号外的终端)针对共享账号进行操作的权限,具体地,可以为其他终端对共享账号下共享备份区域的目标共享数据的操作权限等等。该操作权限可以包括可以允许执行的若干操作项(如操作项列表),比如该操作权限可以包括:同步操作、上传操作、数据修改操作等等操作中至少一种。该操作权限可以根据用户的实际需求设定。
在操作权限包括:操作项列表时,步骤“判断该数据同步请求对应的操作是否满足该操作权限”可以包括:判断数据同步请求对应的操作是否在操作项列表中,若是则,满足操作权限,若否则不满足操作权限。
由上可知,本发明实施例在接收第一终端发送的共享账号设置请求时,根据该共享账号设置请求创建该共享账号对应的共享备份区域,然后,将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中,接收第二终端发送的携带该共享账号的数据同步请求,并根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端。该方案可以基于备份账号关联的共享账号以及共享账号的共享备份区域实现备份数据同步,在基于共享账号进行备份数据同步时,其他同步终端只能获取共享备份区域内的备份数据,无法获取备份账号的私有备份区域内的备份数据,可以防止备份数据发生泄漏,因此,相对于现有技术而言,可以提高备份数据的安全性。
在一实施例中,将在上述实施例所述方法的基础上作进一步描述。
本发明实施例以上述实施例中同步装置集成在终端、上述实施例中另一种同步装置集成在服务器中为例来作详细说明。该服务器可以为用于备份的云端服务器,该终端可以手机、平板电脑、笔记本电脑等设备。
参考图6,在一实施例中,提供了一种备份数据同步系统,包括:终端601、终端602、终端603以及服务器604;该系统中终端与服务器604通过网络如无线网络连接。在其他实施例中该系统还可以包括更多的终端。
以下基于该备份数据同步系统来详细介绍本发明的同步方法,如图7所示,一种备份数据的同步方法具体流程如下:
701、终端601登录目标备份账号。
具体地,终端601登录目标备份账号的过程可以包括:
终端601向服务器604发送账号登录请求,该账号登录请求携带目标备份账号及其对应的鉴权信息。
服务器604根据账号登录请求返回登录响应信息给该终端601。
终端601根据登录响应信息登录该目标备份账号。具体地,目标备份账号的登录过程可以参考实施例二种的相关描述。
702、终端601接收共享账号添加指令。
比如,云备份应用可以在主界面中提供一共享账号添加接口,这样用户便可以通过该账号添加接口添加共享账号,也即步骤“接收共享账号添加指令”可以包括:接收用户通过共享账号添加接口触发的共享账号添加指令。其中该共享账号添加接口的形式有多种,如输入框、图标按钮等形式。
703、终端601根据共享账号添加指令获取待添加的共享账号。
获取共享账号的方式有多种,比如该共享账号可以由用户输入,也可以由终端601自行随机生成。
在实际应用中,在接收到账号添加指令之后终端的云备份应用可以提供一共享账号添加界面,该共享账号添加界面设有共享账号输入接口,这样用户便可以通过共享账号输入接口输入待添加的共享账号。
704、终端601为目标备份账号添加该共享账号,并且终端601还设置该共享账号对应的第一鉴权信息、待共享数据的属性信息以及操作权限。
其中,各信息的设置过程中可以参考实施例二的相关描述,此处不再赘述。
705、终端601向服务器604发送共享账号设置请求,该共享账号设置请求携带目标备份账号、该共享账号、第一鉴权信息、属性信息以及操作权限。
706、服务器604根据该共享账号设置请求创建该共享账号对应的共享备份区域。
本实施例中,创建共享备份区域的方式有多种,比如,可以指定一个存储区域作为共享备份区域,也即步骤“服务器604根据该共享账号设置请求创建该共享账号对应的共享备份区域”可以包括:
服务器604根据共享账号设置请求划分一存储区域;
服务器604将该存储区域指定为该共享账号对应的共享备份区域。
707、服务器604根据属性信息从该目标备份账号对应私有备份区域中确定需要共享的目标共享数据,并将该目标共享数据添加至共享备份区域中。
708、终端602或者603登录该共享账号,并向服务器604发送数据同步请求,该数据同步请求携带共享账号及其对应的第二鉴权信息。
其中,终端602或者603登录该共享账号的过程可以包括:
终端602或者603登录获取共享账号及其对应的第三鉴权信息;
终端602或者603登录向服务器604发送共享账号登录请求,该共享账号登录请求携带该共享账号及其对应的第三鉴权信息;
服务器604将第一鉴权信息与第三鉴权信息匹配,若匹配成功则发送相应的共享账号登录响应信息给终端602或者603;
终端602或者603根据共享账号登录响应信息登录该共享账号。
709、服务器604判断数据同步请求对应的操作是否满足操作权限,若是,则执行步骤710,若否,则结束同步流程。
若操作权限包括:同步操作和下载时,此时可以判断数据同步请求对应的操作满足操作权限。
若服务器604操作权限包含上传操作权限,终端602或者603发起上传请求时服务器604拒绝对上传请求进行处理。
710、服务器604将第一鉴权信息与第二鉴权信息匹配当鉴权信息匹配成功时,服务器604将该共享备份区域内的目标共享数据发送给终端602或者603。
比如,服务器604根据该数据同步请求将该共享备份区域中共享数据的属性信息发送给终端602或者603;服务器604接收该终端602或者603根据该共享数据的属性信息返回的同步选择信息;服务器604根据该同步选择信息将该共享备份区域中相应的目标共享数据发送给终端602或者603。
此外,本实施例中服务器604在接收到共享账号设置请求之后,服务器604还可以根据当前系统时间信息和该共享时间信息删除该共享备份区域中的目标共享数据。
该共享时间信息可以包括共享期限,即共享数据的有效时间。例如,服务器604判断当前系统时间是否达到该共享期限,若是,则删除该共享备份区域中的目标共享数据。以减少共享数据长时间存在导致的被盗风险,以及节省服务器的存储空间。
由上可知,本发明实施例采用终端601向服务器604发送共享账号请求,服务器604根据该共享账号设置请求创建该共享账号对应的共享备份区域,然后,服务器604将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中,服务器604接收终端602或者603发送的携带该共享账号的数据同步请求,并根据该数据同步请求将该共享备份区域中的目标共享数据同步给终端602或者603。该方案可以基于备份账号关联的共享账号以及共享账号的共享备份区域实现备份数据同步,在基于共享账号进行备份数据同步时,其他同步终端只能获取共享备份区域内的备份数据,无法获取备份账号的私有备份区域内的备份数据,可以防止备份数据发生泄漏,因此,相对于现有技术而言,可以提高备份数据的安全性。
本发明实施例还提供了一种备份数据的同步装置,包括:
接收单元,用于接收第一终端发送的共享账号设置请求,所述共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
创建单元,用于根据所述共享账号设置请求创建所述共享账号对应的共享备份区域;
添加单元,用于将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中;
同步单元,用于接收第二终端发送的携带所述共享账号的数据同步请求,并根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
在一实施例中,所述共享账号设置请求还携带所述共享账号对应的待共享数据的属性信息;
所述添加单元包括:确定子单元以及复制子单元;
所述确定子单元,用于根据所述属性信息在所述目标备份账号对应的私有备份区域中确定目标共享数据;
所述复制子单元,用于将所述目标共享数据复制到所述共享备份区域中。
在一实施例中,所述共享账号设置请求还携带所述共享账号对应的第一鉴权信息,所述数据同步请求还携带所述共享账号对应的第二鉴权信息;
所述同步装置还包括:匹配单元;
所述匹配单元,用于在所述同步单元接收到数据同步请求之后,根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端之前,将所述第二鉴权信息与所述第一鉴权信息进行匹配;
所述同步单元,用于在所述匹配单元匹配成功时,根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
在一实施例中,所述共享账号设置请求还携带共享账号对应的共享时间信息;所述同步装置还包括删除单元;
所述删除单元,用于在所述接收单元接收到共享账号设置请求之后,根据当前系统时间信息和所述共享时间信息删除所述共享备份区域中的目标共享数据。
在一实施例中,所述共享账号设置请求还携带共享账号对应的操作权限;
所述同步单元,用于接收第二终端发送的携带所述共享账号的数据同步请求,判断所述数据同步请求对应的操作是否满足所述操作权限,若是,则根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
在一实施例中,为了更好地实施以上方法,本发明实施例还提供一种备份数据的同步装置80,如图8所示,该同步装置80包括接收单元801、创建单元802、添加单元803和同步单元804,如下:
接收单元801,用于接收第一终端发送的共享账号设置请求,该共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
创建单元802,用于根据该共享账号设置请求创建该共享账号对应的共享备份区域;
添加单元803,用于将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中;
同步单元804,用于接收第二终端发送的携带该共享账号的数据同步请求,并根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端。
在一实施例中,为便于数据同步,本实施例中共享账号设置请求还携带该共享账号对应的待共享数据的属性信息,其中,添加单元803可以包括:确定子单元以及复制子单元;
该确定子单元,用于根据该属性信息在该目标备份账号对应的私有备份区域中确定目标共享数据;
该复制子单元,用于将该目标共享数据复制到该共享备份区域中。
在一实施例中,为了提高数据同步和账号的安全性,本实施例中共享账号设置请求还携带该共享账号对应的第一鉴权信息,该数据同步请求还携带该共享账号对应的第二鉴权信息;参考图9,该同步装置80还可以包括匹配单元805;
该匹配单元805,用于在同步单元804接收到数据同步请求之后,根据该数据同步请求将该共享备份区域中的数据同步给该第二终端之前,将该第二鉴权信息与该第一鉴权信息进行匹配;
该同步单元804,用于在匹配单元匹配成功时,根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端。
在一实施例中,为了节省存储空间,本实施例中该共享账号设置请求还携带共享账号对应的共享时间信息;参考图10,该同步装置80还包括删除单元806;
该删除单元,用于在接收单元801接收到共享账号设置请求之后,根据当前系统时间信息和该共享时间信息删除该共享备份区域中的目标共享数据。
在一实施例中,为保证数据同步的一致性,本实施例共享账号设置请求还携带共享账号对应的操作权限,该同步装置还可以包括:判断单元;
该判断单元,用于在同步单元804接收到数据同步请求之后,根据该数据同步请求将该共享备份区域中的数据同步给该第二终端之前,判断该数据同步请求对应的操作是否满足该操作权限;
此时,同步单元804可以具体用于:当判断单元判断为是时根据该数据同步请求将该共享备份区域中的数据同步给该第二终端。
具体实施时,以上各个单元可以作为独立的实体来实现,也可以进行任意组合,作为同一或若干个实体来实现,以上各个单元的具体实施可参见前面的方法实施例,在此不再赘述。
该同步装置具体可以集成服务器中,比如云端服务器等设备中。
本发明实施例采用接收单元801接收第一终端发送的共享账号设置请求,该共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号,然后,由创建单元802根据该共享账号设置请求创建该共享账号对应的共享备份区域,由添加单元803将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中,由同步单元804接收第二终端发送的携带该共享账号的数据同步请求,并根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端。该方案可以基于备份账号关联的共享账号以及共享账号的共享备份区域实现备份数据同步,在基于共享账号进行备份数据同步时,其他同步终端只能获取共享备份区域内的备份数据,无法获取备份账号的私有备份区域内的备份数据,可以防止备份数据发生泄漏,因此,相对于现有技术而言,可以提高备份数据的安全性。
本发明实施例还提供了另一种备份数据的同步装置,包括:
指令接收单元,用于在登录目标备份账号之后,接收共享账号添加指令;
获取单元,用于根据所述共享账号添加指令获取待添加的共享账号;
账号添加单元,用于为所述目标备份账号添加所述共享账号;
发送单元,用于向所述云端服务器发送携带所述目标备份账号和所述共享账号的共享账号设置请求,以使得所述云端服务器根据所述共享账号设置请求进行备份数据同步。
在一实施例中,所述同步装置还包括验证单元;
所述验证单元,用于在指令接收单元接收共享账号添加指令之后,获取单元获取待添加的共享账号之前,获取用户输入的所述目标备份账号对应的鉴权信息;对用户输入的鉴权信息进行验证;
所述获取单元,具体用于在验证单元验证通过时,根据所述共享账号添加指令获取待添加的共享账号。
在一是失落中红,所述同步装置,还包括:还包括验证单元;
所述验证单元,用于在指令接收单元接收共享账号添加指令之后,获取单元获取待添加的共享账号之前,获取用户输入的所述目标备份账号对应的鉴权信息;对用户输入的鉴权信息进行验证;
所述获取单元,具体用于在验证单元验证通过时,根据所述共享账号添加指令获取待添加的共享账号。
在一实施例中,为了更好地实施以上方法,本发明实施例还提供另一种备份数据的同步装置90,如图11所示,该同步装置90包括指令接收单元901、获取单元902、账号添加单元903和发送单元904,如下:
指令接收单元901,用于在登录目标备份账号之后,接收共享账号添加指令;
获取单元902,用于根据该共享账号添加指令获取待添加的共享账号;
账号添加单元903,用于为该目标备份账号添加该共享账号;
发送单元904,用于向云端服务器发送携带该目标备份账号和该共享账号的共享账号设置请求,以使得该云端服务器根据该共享账号设置请求进行备份数据同步。
在一实施例中,为了保证数据同步的安全性,参考图12,本实施例同步装置90还可以包括:验证单元905;
该验证单元905,用于在指令接收单元901接收共享账号添加指令之后,获取单元902获取待添加的共享账号之前,获取用户输入的该目标备份账号对应的鉴权信息;对用户输入的鉴权信息进行验证;
该获取单元902,具体用于在验证单元验证通过时,根据该共享账号添加指令获取待添加的共享账号。
在一实施例中,参考图13,本实施例的同步装置90还可以包括设置单906;
该设置单元906,用于在账号添加单元903为目标备份账号添加对应的共享账号之后,发送单元904向云端服务器发送共享账号设置请求之前,执行以下步骤中的至少一种:
设置该共享账号对应的鉴权信息;
设置该共享账号对应的共享时间信息;
设置该共享账号对应的待共享数据的属性信息;
设置该共享账号对应的操作权限;
对应的该共享设置请求还携带该鉴权信息、共享时间信息、该属性信息以及该操作权限中的至少一种。
具体实施时,以上各个单元可以作为独立的实体来实现,也可以进行任意组合,作为同一或若干个实体来实现,以上各个单元的具体实施可参见前面的方法实施例,在此不再赘述。
该同步装置具体可以集成终端中,比如手机、笔记本电脑、平板电脑等设备中。
由上可知,本发明实施例采用指令接收单元901在登录目标备份账号之后,接收共享账号添加指令,然后,由获取单元902根据该共享账号添加指令获取待添加的共享账号,由账号添加单元903为该目标备份账号添加该共享账号,由发送单元904向该云端服务器发送携带该目标备份账号和该共享账号的共享账号设置请求,以使得该云端服务器根据该共享账号设置请求进行备份数据同步。该方案可以基于备份账号关联的共享账号以及共享账号的共享备份区域实现备份数据同步,在基于共享账号进行备份数据同步时,其他同步终端只能获取共享备份区域内的备份数据,无法获取备份账号的私有备份区域内的备份数据,可以防止备份数据发生泄漏,因此,相对于现有技术而言,可以提高备份数据的安全性。
本发明实施例还提供了一种服务器,包括处理器和存储器,所述存储器存储有多条指令,所述处理器加载所述存储器中的指令用于执行本发明实施例任一项提供适用于服务器的同步方法。在一实施例中,本实施例提供了一种服务器,其中可以集成实施例二所述的同步装置,参考图14,其示出了本发明实施例所涉及的服务器的结构示意图,具体来讲:
该服务器140可以包括一个或者一个以上处理核心的处理器141、一个或一个以上计算机可读存储介质的存储器142、射频(Radio Frequency,RF)电路143、电源144、输入单元145、以及显示单元146等部件。本领域技术人员可以理解,图14中示出的服务器结构并不构成对服务器的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。其中:
处理器141是该服务器的控制中心,利用各种接口和线路连接整个服务器的各个部分,通过运行或执行存储在存储器142内的软件程序和/或模块,以及调用存储在存储器142内的数据,执行服务器的各种功能和处理数据,从而对服务器进行整体监控。可选的,处理器141可包括一个或多个处理核心;优选的,处理器141可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器141中。
存储器142可用于存储软件程序以及模块,处理器141通过运行存储在存储器142的软件程序以及模块,从而执行各种功能应用以及数据处理。
RF电路143可用于收发信息过程中,信号的接收和发送,特别地,将基站的下行信息接收后,交由一个或者一个以上处理器141处理;另外,将涉及上行的数据发送给基站。
服务器还包括给各个部件供电的电源144(比如电池),优选的,电源可以通过电源管理系统与处理器141逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。电源144还可以包括一个或一个以上的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
该服务器还可包括输入单元145,该输入单元145可用于接收输入的数字或字符信息,以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。
该服务器还可包括显示单元146,该显示单元146可用于显示由用户输入的信息或提供给用户的信息以及服务器的各种图形用户接口,这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。显示单元148可包括显示面板,可选的,可以采用液晶显示器 (LCD,Liquid Crystal Display)、有机发光二极管(OLED,Organic Light-Emitting Diode)等形式来配置显示面板。
具体在本实施例中,服务器中的处理器141会按照如下的指令,将一个或一个以上的应用程序的进程对应的可执行文件加载到存储器142中,并由处理器141来运行存储在存储器142中的应用程序,从而实现各种功能,如下:
接收第一终端发送的共享账号设置请求,该共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号,然后,根据该共享账号设置请求创建该共享账号对应的共享备份区域,将该目标备份账号对应的私有备份区域中的目标共享数据添加至该共享备份区域中,接收第二终端发送的携带该共享账号的数据同步请求,并根据该数据同步请求将该共享备份区域中的目标共享数据同步给该第二终端。
在一实施例中,所述共享账号设置请求还携带所述共享账号对应的待共享数据的属性信息;所述将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中,包括:根据所述属性信息在所述目标备份账号对应的私有备份区域中确定目标共享数据;将所述目标共享数据复制到所述共享备份区域中。
上述操作具体可参见前面的方法实施例,在此不再赘述。
本发明实施例还提供了一种电子设备,其中,包括处理器和存储器,所述存储器存储有多条指令,所述处理器加载所述存储器中的指令用于执行本发明实施例任一项提供的适用于电子设备或者终端的同步方法。
在一实施例中,参考图15,还提供了一种终端15,可以集成实施例一所述的同步装置,该终端15可以包括射频(RF,Radio Frequency)电路151、包括有一个或一个以上计算机可读存储介质的存储器152、输入单元153、显示单元154、传感器155、音频电路156、无线保真(WiFi,Wireless Fidelity)模块157、包括有一个或者一个以上处理核心的处理器158、电源159、以及摄像头150等部件。本领域技术人员可以理解,图15中示出的终端结构并不构成对终端的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
射频电路151可用于收发信息,或通话过程中信号的接收和发送,特别地,将基站的下行信息接收后,交由一个或者一个以上处理器158处理;另外,将涉及上行的数据发送给基站。通常,射频电路151包括但不限于天线、至少一个放大器、调谐器、一个或多个振荡器、用户身份模块(SIM, Subscriber Identity Module)卡、收发信机、耦合器、低噪声放大器(LNA,Low Noise Amplifier)、双工器等。此外,射频电路151还可以通过无线通信与网络和其他设备通信。该无线通信可以使用任一通信标准或协议,包括但不限于全球移动通讯系统 (GSM,Global System of Mobile communication)、通用分组无线服务(GPRS ,General Packet Radio Service)、码分多址(CDMA,Code Division Multiple Access)、宽带码分多址(WCDMA,Wideband Code Division Multiple Access)、长期演进(LTE,Long Term Evolution)、电子邮件、短消息服务(SMS,Short Messaging Service)等。
存储器152可用于存储软件程序以及模块。处理器158通过运行存储在存储器152的软件程序以及模块,从而执行各种功能应用以及数据处理。存储器152可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据终端的使用所创建的数据(比如音频数据、电话本等)等。此外,存储器152可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地,存储器152还可以包括存储器控制器,以提供处理器158和输入单元153对存储器152的访问。
输入单元153可用于接收输入的数字或字符信息,以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。具体地,在一个具体的实施例中,输入单元153可包括触敏表面以及其他输入设备。触敏表面,也称为触摸显示屏或者触控板,可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触敏表面上或在触敏表面附近的操作),并根据预先设定的程式驱动相应的连接装置。可选的,触敏表面可包括触摸检测装置和触摸控制器两个部分。其中,触摸检测装置检测用户的触摸方位,并检测触摸操作带来的信号,将信号传送给触摸控制器;触摸控制器从触摸检测装置上接收触摸信息,并将它转换成触点坐标,再送给处理器158,并能接收处理器158发来的命令并加以执行。此外,可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触敏表面。除了触敏表面,输入单元153还可以包括其他输入设备。具体地,其他输入设备可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆、指纹识别模组等中的一种或多种。
显示单元154可用于显示由用户输入的信息或提供给用户的信息以及终端的各种图形用户接口,这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。显示单元154可包括显示面板,可选的,可以采用液晶显示器(LCD,Liquid Crystal Display)、有机发光二极管(OLED,Organic Light-Emitting Diode)等形式来配置显示面板。进一步的,触敏表面可覆盖显示面板,当触敏表面检测到在其上或附近的触摸操作后,传送给处理器158以确定触摸事件的类型,随后处理器158根据触摸事件的类型在显示面板上提供相应的视觉输出。虽然在15中,触敏表面与显示面板是作为两个独立的部件来实现输入和输入功能,但是在某些实施例中,可以将触敏表面与显示面板集成而实现输入和输出功能。
终端还可包括至少一种传感器155,比如光传感器、运动传感器以及其他传感器。具体地,光传感器可包括环境光传感器及接近传感器,其中,环境光传感器可根据环境光线的明暗来调节显示面板的亮度,接近传感器可在终端移动到耳边时,关闭显示面板和/或背光。作为运动传感器的一种,重力加速度传感器可检测各个方向上(一般为三轴)加速度的大小,静止时可检测出重力的大小及方向,可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等; 至于终端还可配置的陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器,在此不再赘述。
音频电路156可通过扬声器、传声器提供用户与终端之间的音频接口。音频电路156可将接收到的音频数据转换成电信号,传输到扬声器,由扬声器转换为声音信号输出;另一方面,传声器将收集的声音信号转换为电信号,由音频电路156接收后转换为音频数据,再将音频数据输出处理器158处理后,经射频电路151以发送给比如另一终端,或者将音频数据输出至存储器152以便进一步处理。音频电路156还可能包括耳塞插孔,以提供外设耳机与终端的通信。
无线保真(WiFi)属于短距离无线传输技术,终端通过无线保真模块157可以帮助用户收发电子邮件、浏览网页和访问流式媒体等,它为用户提供了无线的宽带互联网访问。虽然15示出了无线保真模块157,但是可以理解的是,其并不属于终端的必须构成,完全可以根据需要在不改变发明的本质的范围内而省略。
处理器158是终端的控制中心,利用各种接口和线路连接整个终端的各个部分,通过运行或执行存储在存储器152内的软件程序和/或模块,以及调用存储在存储器152内的数据,执行终端的各种功能和处理数据,从而对终端进行整体监控。可选的,处理器158可包括一个或多个处理核心;优选的,处理器158可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器158中。
终端还包括给各个部件供电的电源159(比如电池)。优选的,电源可以通过电源管理系统与处理器158逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。电源159还可以包括一个或一个以上的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
终端还包括具备拍摄功能的摄像头150(比如可以包括前置摄像头、后置摄像头等)。优选的,摄像头可以通过视频处理系统、摄像头驱动等与处理器158逻辑相连,从而通过视频处理系统、摄像头驱动实现拍照、摄像等功能。
尽管未示出,终端还可以包蓝牙模块等,在此不再赘述。
具体在本实施例中,终端中的处理器158会按照如下的指令,将一个或一个以上的应用程序的进程对应的可执行文件加载到存储器152中,并由处理器158来运行存储在存储器152中的应用程序,从而实现各种功能:
在登录目标备份账号之后,接收共享账号添加指令,然后,根据该共享账号添加指令获取待添加的共享账号,为该目标备份账号添加该共享账号,向云端服务器发送携带该目标备份账号和该共享账号的共享账号设置请求,以使得该云端服务器根据该共享账号设置请求进行备份数据同步。
在一实施例中,在接收共享账号添加指令之后,获取待添加的共享账号之前,还包括:获取用户输入的所述目标备份账号对应的鉴权信息;对用户输入的鉴权信息进行验证;若验证通过,则执行根据所述共享账号添加指令获取待添加的共享账号的步骤。
在一实施例中,在为目标备份账号添加对应的共享账号之后,向云端服务器发送共享账号设置请求之前,所述同步方法还包括以下步骤中的至少一种:
设置所述共享账号对应的鉴权信息;
设置所述共享账号对应的共享时间信息;
设置所述共享账号对应的待共享数据的属性信息;
设置所述共享账号对应的操作权限;
对应的所述共享设置请求还携带所述鉴权信息、共享时间信息、所述属性信息以及所述操作权限中的至少一种。
上述操作具体可参见前面的方法实施例,在此不再赘述。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,该程序可以存储于一计算机可读存储介质中,存储介质可以包括:只读存储器(ROM,Read Only Memory)、随机存取记忆体(RAM,Random Access Memory)、磁盘或光盘等。
以上对本发明实施例所提供的一种备份数据的同步方法、装置、存储介质、电子设备及服务器进行了详细介绍,本文中应用了具体个例对本发明的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本发明的方法及其核心思想;同时,对于本领域的技术人员,依据本发明的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本发明的限制。

Claims (20)

  1. 一种备份数据的同步方法,其中,包括:
    在登录目标备份账号之后,接收共享账号添加指令;
    根据所述共享账号添加指令获取待添加的共享账号;
    为所述目标备份账号添加所述共享账号;
    向云端服务器发送携带所述目标备份账号和所述共享账号的共享账号设置请求,以使得所述云端服务器根据所述共享账号设置请求进行备份数据同步。
  2. 如权利要求1所述的同步方法,其中,在接收共享账号添加指令之后,获取待添加的共享账号之前,所述同步方法还包括:
    获取用户输入的所述目标备份账号对应的鉴权信息;
    对用户输入的鉴权信息进行验证;
    若验证通过,则执行根据所述共享账号添加指令获取待添加的共享账号的步骤。
  3. 如权利要求1所述的同步方法,其中,所述共享设置请求还携带所述鉴权信息、共享时间信息、所述属性信息以及所述操作权限中的至少一种;则所述同步方法在为目标备份账号添加对应的共享账号之后,向云端服务器发送共享账号设置请求之前,所还包括以下步骤中的至少一种:
    设置所述共享账号对应的鉴权信息;
    设置所述共享账号对应的共享时间信息;
    设置所述共享账号对应的待共享数据的属性信息;
    设置所述共享账号对应的操作权限。
  4. 一种备份数据的同步方法,其中,包括:
    接收第一终端发送的共享账号设置请求,所述共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
    根据所述共享账号设置请求创建所述共享账号对应的共享备份区域;
    将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中;
    接收第二终端发送的携带所述共享账号的数据同步请求,并根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
  5. 如权利要求4所述的同步方法,其中,所述共享账号设置请求还携带所述共享账号对应的待共享数据的属性信息;
    所述将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中,包括:
    根据所述属性信息在所述目标备份账号对应的私有备份区域中确定目标共享数据;
    将所述目标共享数据复制到所述共享备份区域中。
  6. 如权利要求4所述的同步方法,其中,所述共享账号设置请求还携带所述共享账号对应的第一鉴权信息;所述数据同步请求还携带所述共享账号对应的第二鉴权信息;
    在接收到数据同步请求之后,根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端之前,所述同步方法还包括:
    将所述第二鉴权信息与所述第一鉴权信息进行匹配;
    若匹配成功,则执行根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端的步骤。
  7. 如权利要求4所述的同步方法,其中,所述共享账号设置请求还携带共享账号对应的共享时间信息;在接收到共享账号设置请求之后,所述同步方法还包括:
    根据当前系统时间信息和所述共享时间信息删除所述共享备份区域中的目标共享数据。
  8. 如权利要求4所述的同步方法,其中,所述共享账号设置请求还携带共享账号对应的操作权限;
    在接收到数据同步请求之后,根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端之前,所述同步方法还包括:
    判断所述数据同步请求对应的操作是否满足所述操作权限;
    若是,则执行根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端的步骤。
  9. 一种备份数据的同步装置,其中,包括:
    接收单元,用于接收第一终端发送的共享账号设置请求,所述共享账号设置请求携带目标备份账号、目标备份账号对应的共享账号;
    创建单元,用于根据所述共享账号设置请求创建所述共享账号对应的共享备份区域;
    添加单元,用于将所述目标备份账号对应的私有备份区域中的目标共享数据添加至所述共享备份区域中;
    同步单元,用于接收第二终端发送的携带所述共享账号的数据同步请求,并根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
  10. 如权利要求9所述的同步装置,其中,所述共享账号设置请求还携带所述共享账号对应的待共享数据的属性信息;
    所述添加单元包括:确定子单元以及复制子单元;
    所述确定子单元,用于根据所述属性信息在所述目标备份账号对应的私有备份区域中确定目标共享数据;
    所述复制子单元,用于将所述目标共享数据复制到所述共享备份区域中。
  11. 如权利要求9所述的同步装置,其中,所述共享账号设置请求还携带所述共享账号对应的第一鉴权信息,所述数据同步请求还携带所述共享账号对应的第二鉴权信息;
    所述同步装置还包括:匹配单元;
    所述匹配单元,用于在所述同步单元接收到数据同步请求之后,根据所述数据同步请求将所述共享备份区域中的数据同步给所述第二终端之前,将所述第二鉴权信息与所述第一鉴权信息进行匹配;
    所述同步单元,用于在所述匹配单元匹配成功时,根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
  12. 如权利要求9所述的同步装置,其中,所述共享账号设置请求还携带共享账号对应的共享时间信息;所述同步装置还包括删除单元;
    所述删除单元,用于在所述接收单元接收到共享账号设置请求之后,根据当前系统时间信息和所述共享时间信息删除所述共享备份区域中的目标共享数据。
  13. 如权利要求9所述的同步装置,其中,所述共享账号设置请求还携带共享账号对应的操作权限;
    所述同步单元,用于接收第二终端发送的携带所述共享账号的数据同步请求,判断所述数据同步请求对应的操作是否满足所述操作权限,若是,则根据所述数据同步请求将所述共享备份区域中的目标共享数据同步给所述第二终端。
  14. 一种备份数据的同步装置,其中,包括:
    指令接收单元,用于在登录目标备份账号之后,接收共享账号添加指令;
    获取单元,用于根据所述共享账号添加指令获取待添加的共享账号;
    账号添加单元,用于为所述目标备份账号添加所述共享账号;
    发送单元,用于向所述云端服务器发送携带所述目标备份账号和所述共享账号的共享账号设置请求,以使得所述云端服务器根据所述共享账号设置请求进行备份数据同步。
  15. 如权利要求14所述的同步装置,其中,还包括验证单元;
    所述验证单元,用于在指令接收单元接收共享账号添加指令之后,获取单元获取待添加的共享账号之前,获取用户输入的所述目标备份账号对应的鉴权信息;对用户输入的鉴权信息进行验证;
    所述获取单元,具体用于在验证单元验证通过时,根据所述共享账号添加指令获取待添加的共享账号。
  16. 如权利要求14所述的同步装置,其中,还包括:设置单元;
    所述设置单元,用于在账号添加单元为目标备份账号添加对应的共享账号之后,发送单元向云端服务器发送共享账号设置请求之前,执行以下步骤中的至少一种:
    设置所述共享账号对应的鉴权信息;
    设置所述共享账号对应的共享时间信息;
    设置所述共享账号对应的待共享数据的属性信息;
    设置所述共享账号对应的操作权限;
    对应的所述共享设置请求还携带所述鉴权信息、共享时间信息、所述属性信息以及所述操作权限中的至少一种。
  17. 一种存储介质,其中,所述存储介质中存储有多条指令,所述指令适于由处理器加载以执行如权利要求1-3任一项所述的方法。
  18. 一种存储介质,其中,所述存储介质中存储有多条指令,所述指令适于由处理器加载以执行如权利要求4-8任一项所述的方法。
  19. 一种电子设备,其中,包括处理器和存储器,所述存储器存储有多条指令,所述处理器加载所述存储器中的指令用于执行如权利要求1-3任一项所述的方法。
  20. 一种服务器,其中,包括处理器和存储器,所述存储器存储有多条指令,所述处理器加载所述存储器中的指令用于执行如权利要求4-8任一项所述的方法。
PCT/CN2017/095696 2016-10-25 2017-08-02 备份数据的同步方法、装置、存储介质、电子设备及服务器 WO2018076875A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/290,579 US20190199795A1 (en) 2016-10-25 2019-03-01 Method and device for synchronizing backup data, storage medium, electronic device, and server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610942150.3A CN106453589B (zh) 2016-10-25 2016-10-25 一种备份数据的同步方法和装置
CN201610942150.3 2016-10-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/290,579 Continuation US20190199795A1 (en) 2016-10-25 2019-03-01 Method and device for synchronizing backup data, storage medium, electronic device, and server

Publications (1)

Publication Number Publication Date
WO2018076875A1 true WO2018076875A1 (zh) 2018-05-03

Family

ID=58177429

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/095696 WO2018076875A1 (zh) 2016-10-25 2017-08-02 备份数据的同步方法、装置、存储介质、电子设备及服务器

Country Status (3)

Country Link
US (1) US20190199795A1 (zh)
CN (1) CN106453589B (zh)
WO (1) WO2018076875A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453589B (zh) * 2016-10-25 2019-10-25 Oppo广东移动通信有限公司 一种备份数据的同步方法和装置
US10735514B2 (en) * 2017-08-29 2020-08-04 Western Digital Technologies, Inc. Remote application configuration on network-attached storage
CN108470302B (zh) * 2018-03-06 2023-06-02 北京京东尚科信息技术有限公司 客户端、服务器的交互方法和装置
CN110177169A (zh) * 2019-04-09 2019-08-27 努比亚技术有限公司 数据交互方法、第一终端、第二终端及计算机存储介质
CN110825564A (zh) * 2019-11-04 2020-02-21 北京联想协同科技有限公司 一种数据备份方法、装置及计算机存储介质
CN114024978A (zh) * 2020-07-15 2022-02-08 中移(苏州)软件技术有限公司 一种云资源的同步方法、装置、节点及存储介质
CN114490472A (zh) * 2021-12-06 2022-05-13 南京蒙柏信息产业有限公司 一种用于数据转换的一口多机并发共享终端
CN115987685B (zh) * 2023-03-17 2023-07-25 航天万源云数据河北有限公司 一种云服务数据共享方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130173553A1 (en) * 2011-12-29 2013-07-04 Anand Apte Distributed Scalable Deduplicated Data Backup System
CN103607469A (zh) * 2013-11-28 2014-02-26 东莞中国科学院云计算产业技术创新与育成中心 一种实现分布式异构数据共享的云平台及其数据共享方法
CN104243602A (zh) * 2014-09-26 2014-12-24 三星电子(中国)研发中心 用户信息同步装置、系统和方法
CN105100223A (zh) * 2015-07-01 2015-11-25 北京奇虎科技有限公司 基于云端存储的文件分享方法、装置与系统
CN106453589A (zh) * 2016-10-25 2017-02-22 广东欧珀移动通信有限公司 一种备份数据的同步方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101452454A (zh) * 2007-11-30 2009-06-10 华为技术有限公司 文件集共享方法及装置
CN103327037B (zh) * 2012-03-20 2017-09-29 中兴通讯股份有限公司 数据同步方法及装置
US9729614B2 (en) * 2012-10-01 2017-08-08 Datacastle Corporation Resilient data node for improving distributed data management and bandwidth utilization

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130173553A1 (en) * 2011-12-29 2013-07-04 Anand Apte Distributed Scalable Deduplicated Data Backup System
CN103607469A (zh) * 2013-11-28 2014-02-26 东莞中国科学院云计算产业技术创新与育成中心 一种实现分布式异构数据共享的云平台及其数据共享方法
CN104243602A (zh) * 2014-09-26 2014-12-24 三星电子(中国)研发中心 用户信息同步装置、系统和方法
CN105100223A (zh) * 2015-07-01 2015-11-25 北京奇虎科技有限公司 基于云端存储的文件分享方法、装置与系统
CN106453589A (zh) * 2016-10-25 2017-02-22 广东欧珀移动通信有限公司 一种备份数据的同步方法和装置

Also Published As

Publication number Publication date
US20190199795A1 (en) 2019-06-27
CN106453589A (zh) 2017-02-22
CN106453589B (zh) 2019-10-25

Similar Documents

Publication Publication Date Title
WO2018076875A1 (zh) 备份数据的同步方法、装置、存储介质、电子设备及服务器
WO2015163735A1 (en) Mobile device and method of sharing content
WO2018082482A1 (zh) 一种网络共享方法、接入网络方法及系统
WO2015137745A1 (en) System and method of encrypting folder in device
WO2015163736A1 (en) Methods of providing social network service and server performing the same
WO2015142133A1 (en) System and method for executing file by using biometric information
AU2015340213B2 (en) Method for controlling operation of electronic device and electronic device using the same
WO2016133338A1 (en) Electronic device and method for installing an application
WO2021049869A1 (en) Vehicle electronic device for performing authentication, mobile device used for vehicle authentication, vehicle authentication system, and vehicle authentication method
WO2013058423A1 (ko) 전자기기 및 전자기기의 동작 방법
WO2018090823A1 (zh) 一种系统分区关键数据的保护方法及系统、终端
WO2016195161A1 (en) Watch type terminal and method for controlling the same
WO2016010202A1 (en) Mobile terminal and control method for the mobile terminal
WO2018124343A1 (ko) 전자장치
WO2018076864A1 (zh) 一种数据同步方法、装置、存储介质及电子设备
WO2016129778A1 (ko) 이동 단말기 및 그 제어 방법
WO2017054481A1 (zh) 一种信息验证和处理方法、装置、以及信息处理系统
WO2017030387A1 (ko) 충전장치와 충전장치의 제어방법 및 이와 연결되는 이동 단말기
WO2019143081A1 (ko) 데이터 통신을 제어하는 방법 및 전자 장치
WO2016129920A1 (ko) 사용자의 사용 패턴에 기초하여 배터리 소모를 줄이는 방법 및 이를 위한 장치
WO2016052889A1 (en) Mobile terminal and method of controlling the same
WO2016036069A1 (en) Method and electronic device for providing data
WO2021241849A1 (ko) 에지 컴퓨팅 서비스를 수행하는 전자 장치 및 전자 장치의 동작 방법
WO2016108407A1 (ko) 주석 제공 방법 및 장치
WO2020032649A1 (en) Electronic device and communication relaying method thereof

Legal Events

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

Ref document number: 17866134

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17866134

Country of ref document: EP

Kind code of ref document: A1