Method and apparatus for multi-account synchronization, and communication device

Abstract

The application relates to the information technology field and discloses a method and device for multi-account synchronization and a communication device, wherein the method for multi-account synchronization comprises the following steps: after a user logs in a target application through a first account, obtaining an authorization result of the user for synchronizing the first account; in the case that the authorization is passed, synchronizing the first account and a second account; in the case that the first account is abnormal, sending synchronization information of the first account and the second account to a target application background, so that the user can handle the business of the first account through the second account. After the account synchronization is completed, in the case that the first account is abnormal, the application background can allow the user to log in the second account to continue to handle the business of the first account according to the synchronization information of the first account and the second account, ensures that the business process will not be interrupted due to the account problem, and improves the business continuity and reliability.

Description

Technical Field

[0001] This application relates to the field of information technology, such as a method and apparatus for synchronizing multiple accounts, and communication equipment. Background Technology

[0002] Currently, with the development of information technology, individuals and businesses are increasingly relying on digital accounts for daily communication and business processing. People may have multiple accounts for reasons such as work, life, or security. These accounts may be distributed across different platforms and devices, making account management a challenge. For many businesses, continuity and reliability are paramount. Any disruption can lead to financial losses and a decline in customer trust. Therefore, a system that can automatically switch to a backup account when the primary account becomes unavailable is essential.

[0003] In related technologies, one account can be authorized to log in without being associated with or synchronized with multiple accounts.

[0004] In the process of implementing the embodiments of this disclosure, at least the following problems were found in the related art:

[0005] The relevant technologies only support single account login, or even if they support multiple accounts, they lack a mechanism to automatically switch accounts when they are abnormal, which affects the business processing of the account.

[0006] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0007] To provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. This summary is not intended as a general commentary, nor is it intended to identify key / important components or describe the scope of protection of these embodiments, but rather as a prelude to the detailed description that follows.

[0008] This disclosure provides a method, apparatus, and communication device for multi-account synchronization, which automatically switches to another account when one account malfunctions, thereby improving business continuity.

[0009] In some embodiments, the method for multi-account synchronization includes: after a user logs into a target application with a first account, obtaining the user's authorization result for synchronizing the first account; if the authorization is successful, synchronizing the first account with a second account; and if the first account encounters an error, sending the synchronization information of the first account and the second account to the target application backend so that the user can handle the business of the first account through the second account.

[0010] Optionally, the user's authorization result for synchronizing the first account can be obtained, including: generating authorization information for the second account to be synchronized; and obtaining the user's authorization result for the authorization information.

[0011] Optionally, synchronizing the first account and the second account includes: associating the account information of the first account with the account information of the second account; and sending the association information of the first account and the second account to the target application requester to complete the synchronization of the first account and the second account.

[0012] Optionally, the second account includes multiple accounts; associating the account information of the first account with the account information of the second account includes: determining the priority information of the multiple accounts in the second account; and associating the account information of the first account with the account information of the multiple accounts in the second account in sequence according to the priority information of the multiple accounts in the second account.

[0013] Optionally, the association information of the first account and the second account may be sent to the target application requester, including: sending the association information of the first account and the second account to the target application requester via a mobile application, instant messaging platform or SMS service.

[0014] Optionally, the first account may experience an anomaly, including: the first account cannot be logged in; or, the phone number associated with the first account cannot be reached.

[0015] Optionally, the synchronization information of the first account and the second account is sent to the target application backend, including: according to the priority information of multiple accounts in the second account, sending the synchronization information of the target account with the highest priority in the second account to the target application backend; if the target account is also abnormal, sending the synchronization information of the next highest priority account in the second account to the target application backend.

[0016] Optionally, the method for multi-account synchronization further includes: in the absence of any abnormality in the first account, in response to the user's second account request instruction, sending the synchronization information of the first and second accounts to the target application backend, so that the user can handle the business of the first account through the second account.

[0017] In some embodiments, the apparatus for multi-account synchronization includes a processor and a memory storing program instructions, the processor being configured to execute the method for multi-account synchronization as described above when the program instructions are executed.

[0018] In some embodiments, the communication device includes: a communication device body; and the means for multi-account synchronization described above, which is installed on the communication device body.

[0019] The method, apparatus, and communication device for multi-account synchronization provided in this disclosure can achieve the following technical effects:

[0020] In this embodiment, after a user logs into the target application with a first account, obtaining the user's authorization information for synchronizing the first account ensures that account synchronization is performed after user authorization, improving user privacy protection during the synchronization process and preventing unauthorized information leakage. After account synchronization is complete, in the event of an anomaly with the first account, the application backend can, based on the synchronization information between the first and second accounts, allow the user to log in with the second account to continue processing the business of the first account, ensuring that business processes are not interrupted due to account issues and improving business continuity and reliability. Furthermore, synchronizing account information through user authorization reduces the risk of data loss due to account anomalies, improving data security.

[0021] The above general description and the description below are exemplary and illustrative only and are not intended to limit this application. Attached Figure Description

[0022] One or more embodiments are illustrated by way of example with reference to the accompanying drawings. These illustrations and drawings do not constitute a limitation on the embodiments. Elements having the same reference numerals in the drawings are shown as similar elements. The drawings are not to be scaled. And wherein:

[0023] Figure 1 This is a schematic diagram of a method for synchronizing multiple accounts provided in an embodiment of this disclosure;

[0024] Figure 2 This is a schematic diagram of another method for multi-account synchronization provided in this embodiment of the disclosure;

[0025] Figure 3 This is a schematic diagram of another method for multi-account synchronization provided in this embodiment of the disclosure;

[0026] Figure 4 This is a schematic diagram of another method for multi-account synchronization provided in this embodiment of the disclosure;

[0027] Figure 5 This is a schematic diagram of another method for multi-account synchronization provided in this embodiment of the disclosure;

[0028] Figure 6 This is a schematic diagram of an apparatus for synchronizing multiple accounts provided in an embodiment of this disclosure. Detailed Implementation

[0029] To provide a more detailed understanding of the features and technical content of the embodiments of this disclosure, the implementation of the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for illustrative purposes only and are not intended to limit the embodiments of this disclosure. In the following technical description, for ease of explanation, several details are used to provide a full understanding of the disclosed embodiments. However, one or more embodiments may still be implemented without these details. In other cases, well-known structures and devices may be simplified in their depiction to simplify the drawings.

[0030] The terms "first," "second," etc., used in the technical solutions described in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this disclosure described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0031] Unless otherwise stated, the term "multiple" means two or more.

[0032] In this embodiment of the disclosure, the character " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B means: A or B.

[0033] The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or A and B.

[0034] The term "correspondence" can refer to an association or binding relationship. The correspondence between A and B means that there is an association or binding relationship between A and B.

[0035] Combination Figure 1 As shown in the embodiments of this disclosure, a method for synchronizing multiple accounts is provided. The execution subject of this method can be a processor, and the method includes:

[0036] S101, after the user logs into the target application with the first account, the processor obtains the authorization result of the user for synchronizing the first account.

[0037] S102, if the authorization is successful, the processor will synchronize the first account with the second account.

[0038] S103, if the first account is abnormal, the processor sends the synchronization information of the first and second accounts to the target application backend so that the user can handle the business of the first account through the second account.

[0039] In this embodiment, after a user logs into the target application with a first account, obtaining the user's authorization information for synchronizing the first account ensures that account synchronization is performed after user authorization, improving user privacy protection during the synchronization process and preventing unauthorized information leakage. After account synchronization is complete, in the event of an anomaly with the first account, the application backend can, based on the synchronization information between the first and second accounts, allow the user to log in with the second account to continue processing the business of the first account, ensuring that business processes are not interrupted due to account issues and improving business continuity and reliability. Furthermore, synchronizing account information through user authorization reduces the risk of data loss due to account anomalies, improving data security.

[0040] Optionally, the user's authorization result for synchronizing the first account can be obtained, including: generating authorization information for the second account to be synchronized; and obtaining the user's authorization result for the authorization information.

[0041] Combination Figure 2 As shown in the embodiments of this disclosure, another method for multi-account synchronization is provided, including:

[0042] S201, after the user logs into the target application with the first account, the processor generates the authorization information for the second account to be synchronized.

[0043] S202, the processor obtains the authorization result of the user's authorization information.

[0044] S203, the processor synchronizes the first account with the second account if authorization is granted.

[0045] S204, if the first account is abnormal, the processor sends the synchronization information of the first and second accounts to the target application backend so that the user can handle the business of the first account through the second account.

[0046] In this embodiment, after a user logs into the target application with their first account, they are prompted to confirm whether they wish to link a second account. Based on the second account the user inputs or selects for synchronization, pending authorization information for that account is generated. This information is presented to the user in a clear and easily understandable manner, ensuring they know what information will be synchronized and its purpose. After reviewing the pending authorization information, the user confirms the authorization result, which is recorded by the system. If the user agrees to the authorization, the system will execute the synchronization operation. Therefore, account information synchronization is performed only after obtaining user authorization, enhancing user privacy protection during the synchronization process and preventing unauthorized information leakage.

[0047] Optionally, synchronizing the first account and the second account includes: associating the account information of the first account with the account information of the second account; and sending the association information of the first account and the second account to the target application requester to complete the synchronization of the first account and the second account.

[0048] Combination Figure 3 As shown in the embodiments of this disclosure, another method for multi-account synchronization is provided, including:

[0049] S301: After a user logs into the target application using the first account, the processor obtains the user's authorization result for synchronizing the first account.

[0050] S302, if authorization is granted, the processor associates the account information of the first account with the account information of the second account.

[0051] S303, the processor sends the association information of the first account and the second account to the target application requester to complete the synchronization of the first account and the second account.

[0052] S304, if the processor encounters an anomaly in the first account, it sends the synchronization information of the first and second accounts to the target application backend, so that the user can handle the business of the first account through the second account.

[0053] In this embodiment, an association is created to match the account information of a first account with that of a second account. The account information includes user ID, contact information, and permission settings. This association can be stored as records in a database or implemented through some form of mapping, ensuring quick identification and access to the second account when needed. After the association between the first and second accounts is established, this association information is sent to the target application requester, such as a server system, client application, or other authorized third-party service. The sent association information may include the identifiers of the two accounts, the association status, and the synchronization scope authorized by the user. This information transmission can be performed using a secure communication protocol to protect the privacy and security of user data.

[0054] Optionally, the second account includes multiple accounts; associating the account information of the first account with the account information of the second account includes: determining the priority information of the multiple accounts in the second account; and associating the account information of the first account with the account information of the multiple accounts in the second account in sequence according to the priority information of the multiple accounts in the second account.

[0055] In this embodiment, when associating the first account, it can be associated with multiple accounts. This allows for synchronization of the first account through multiple accounts should an anomaly occur. Therefore, when setting up the second account, multiple accounts can be specified, and each account can be assigned a priority. This priority can be based on user-defined rules, such as account usage frequency, importance, or other personal preferences. When the first account malfunctions, synchronization will first attempt to connect the first account to the highest-priority second account. If the highest-priority account fails to synchronize successfully, the next account will be synchronized sequentially according to priority.

[0056] Optionally, the association information of the first account and the second account may be sent to the target application requester, including: sending the association information of the first account and the second account to the target application requester via a mobile application, instant messaging platform or SMS service.

[0057] In this embodiment, different methods can be selected to send the association information of the first and second accounts to the target application user, based on factors such as personal preference, network conditions, and security requirements. Sending via a mobile application requires packaging the association information of the first and second accounts into a data packet or notification and sending it through the application's internal communication mechanism. Sending via an instant messaging platform requires sending the association information as a message to the target application user's instant messaging account. Sending via SMS requires converting the association information into SMS content and sending it to the target application user's mobile phone number through an SMS gateway. By securely and promptly sending account association information to the target application user through different communication channels according to user and scenario needs, it ensures that relevant services can seamlessly switch to the second account in the event of an anomaly in the first account, improving business continuity and user experience.

[0058] Optionally, the first account may experience an anomaly, including: the first account cannot be logged in; or, the phone number associated with the first account cannot be reached.

[0059] In this embodiment, the inability to log in to the first account may be due to reasons such as an incorrect username or password, the account being locked, or the account being suspended or disabled. The inability to connect to the phone associated with the first account may be due to reasons such as the phone being switched off, no signal, no network coverage, SIM card problems, or device malfunction. For example, for accounts with multiple networks, such as China Telecom, China Mobile, and China Unicom numbers, and with different phone models, poor network signal or a dead battery can cause the first account to become unreachable, resulting in an abnormal situation for the first account.

[0060] Optionally, the synchronization information of the first account and the second account is sent to the target application backend, including: according to the priority information of multiple accounts in the second account, sending the synchronization information of the target account with the highest priority in the second account to the target application backend; if the target account is also abnormal, sending the synchronization information of the next highest priority account in the second account to the target application backend.

[0061] Combination Figure 4 As shown in the embodiments of this disclosure, another method for multi-account synchronization is provided, including:

[0062] S401: After a user logs into the target application using the first account, the processor obtains the user's authorization result for synchronizing the first account.

[0063] S402, the processor synchronizes the first account with the second account if authorization is granted.

[0064] S403, if the first account is abnormal, the processor sends the synchronization information of the target account with the highest priority in the second account to the target application backend according to the priority information of multiple accounts in the second account.

[0065] S404: If the target account also becomes abnormal, the processor sends the synchronization information of the next priority account in the second account to the target application backend.

[0066] In this embodiment, when the first account malfunctions, the highest-priority target account is first identified based on the priority information of multiple accounts within the second account. Then, the synchronization information of the first account and the target account is packaged and sent securely to the target application's backend. If an anomaly is detected in the target account while attempting to synchronize to the highest-priority account, the system continues to identify the next-highest-priority account within the second account and attempts to send the synchronization information to the target application's backend. Therefore, according to the priority order set in the second account, synchronization information is sequentially attempted to be sent to the target application's backend until a usable account is found or all accounts have been tried. This improves the system's flexibility and reliability, ensuring that even when multiple accounts malfunction, a usable account can be found to maintain business operations.

[0067] Optionally, the method for multi-account synchronization further includes: in the absence of any abnormality in the first account, in response to the user's second account request instruction, sending the synchronization information of the first and second accounts to the target application backend, so that the user can handle the business of the first account through the second account.

[0068] Combination Figure 5 As shown in the embodiments of this disclosure, another method for multi-account synchronization is provided, including:

[0069] S501: After a user logs into the target application using the first account, the processor obtains the user's authorization result for synchronizing the first account.

[0070] S502, the processor synchronizes the first account with the second account if authorization is granted.

[0071] S503: In the event of an anomaly in the first account, the processor sends the synchronization information of the first and second accounts to the target application backend, so that the user can handle the business of the first account through the second account.

[0072] S504: If the first account is not abnormal, the processor responds to the user's second account request instruction by sending the synchronization information of the first and second accounts to the target application backend, so that the user can handle the business of the first account through the second account.

[0073] In this embodiment, even if the first account is functioning normally, the user may still need to handle the first account's transactions through the second account. The user can issue a request through the user interface to send synchronization information between the first and second accounts to the target application's backend. Upon receiving the synchronization information, the target application's backend will update or merge the data of the first and second accounts to ensure that the second account can handle the first account's transactions. Therefore, by proactively handling the first account's transactions through the second account when the first account is functioning normally, the user can improve the flexibility and convenience of account management.

[0074] Optionally, the first and second accounts can be logged in on different devices.

[0075] Because the synchronization information between the first and second accounts is confirmed through the target application's backend, synchronization between the first and second accounts can be achieved across different devices. If the device logged into the first account experiences an anomaly, the second account can be logged into directly using the second device to continue processing the business of the first account. For example, while using the first device to log into the first account for business processing, the second account is synchronized. If the first device runs out of battery, the business will be interrupted. If it is necessary to log into the first account on the second device, the first device needs to perform auxiliary verification. In this case, the second account, which is synchronized with the first account, can be logged into on the second device to continue processing the business of the first account.

[0076] The method for multi-account synchronization provided in this disclosure can, in the event of an anomaly in the first account (e.g., using the first account as a reserved contact method), record the abnormal call data when dialing the reserved contact method fails, and synchronize this record to the application backend or client. At this time, if the client receives a synchronization request for the second account, it can send the synchronization information of the second account to the target application backend. For example, taking a ride-hailing app as the target application, the first account is the user's mobile phone number, and the second account is the mobile phone number of the user's family member. After the user logs into the ride-hailing app using their own mobile phone number to hail a ride for a family member, the family member's mobile phone number is synchronized. If the user's phone battery runs out, the driver will be unable to contact the user, indicating an anomaly in the first account. In this case, the ride-hailing app backend will receive the synchronization information of the user's mobile phone number and the user's family member's mobile phone number, allowing the driver to directly contact the family member and ensure the ride-hailing service remains operational.

[0077] Combination Figure 6 As shown, this disclosure provides an apparatus 600 for multi-account synchronization, including a processor 700 and a memory 701. Optionally, the apparatus may further include a communication interface 702 and a bus 703. The processor 700, communication interface 702, and memory 701 can communicate with each other via the bus 703. The communication interface 702 can be used for information transmission. The processor 700 can call logical instructions in the memory 701 to execute the multi-account synchronization method described in the above embodiment.

[0078] Furthermore, the logic instructions in the aforementioned memory 701 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium.

[0079] The memory 701, as a computer-readable storage medium, can be used to store software programs and computer-executable programs, such as program instructions / modules corresponding to the methods in the embodiments of this disclosure. The processor 700 executes functional applications and data processing by running the program instructions / modules stored in the memory 701, thereby implementing the method for multi-account synchronization described in the above embodiments.

[0080] The memory 701 may include a program storage area and a data storage area. The program storage area may store the operating system and application programs required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 701 may include high-speed random access memory and may also include non-volatile memory.

[0081] This disclosure provides a communication device, including: a communication device body and the aforementioned device for multi-account synchronization. The device for multi-account synchronization is installed in the communication device body. The installation relationship described herein is not limited to placement within the communication device, but also includes installation connections with other components of the communication device, including but not limited to physical connections, electrical connections, or signal transmission connections. Those skilled in the art will understand that the device for multi-account synchronization can be adapted to feasible communication device bodies to achieve other feasible embodiments.

[0082] This disclosure provides a computer-readable storage medium storing computer-executable instructions configured to perform the above-described method for multi-account synchronization.

[0083] The technical solutions of this disclosure can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes one or more instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in this disclosure. The aforementioned storage medium can be a non-transitory storage medium, including: a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and other media capable of storing program code.

[0084] The foregoing description and accompanying drawings fully illustrate embodiments of this disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, procedural, and other changes. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the order of operation may vary. Parts and features of some embodiments may be included in or replace parts and features of other embodiments. Moreover, the terminology used in this application is for describing embodiments only and is not intended to limit the technical solutions described herein. As used in the technical solutions described herein, the singular forms “a,” “an,” and “the” are intended to equally include the plural forms unless the context clearly indicates otherwise. Similarly, the term “and / or” as used herein means including one or more of the associated listed items and all possible combinations thereof. Additionally, when used in this application, the term "comprise" and its variations "comprises" and / or "comprising" refer to the presence of stated features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof. Without further limitations, an element defined by the phrase "comprises a..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes said element. In this document, each embodiment may focus on the differences from other embodiments, and similar or identical parts between embodiments can be referred to mutually. For methods, products, etc., disclosed in the embodiments, if they correspond to the method section disclosed in the embodiments, the relevant parts can be referred to the description of the method section.

[0085] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this disclosure. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0086] The methods and products (including but not limited to devices and equipment) disclosed in the embodiments herein can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of units may be merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the shown or discussed units may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to implement this embodiment according to actual needs. Furthermore, the functional units in the embodiments of this disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0087] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than that shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. In the descriptions corresponding to the flowcharts and block diagrams in the accompanying drawings, the operations or steps corresponding to different blocks may also occur in a different order than disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. Each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

Claims

1. A method for synchronizing multiple accounts, characterized in that, include: After a user logs into the target application using their primary account, obtain the user's authorization result for synchronizing the primary account. If authorization is granted, the first account and the second account will be synchronized; In the event of an anomaly in the first account, the synchronization information between the first and second accounts will be sent to the target application's backend, enabling the user to handle the first account's business through the second account.

2. The method according to claim 1, characterized in that, Obtain the user's authorization result for synchronizing the first account, including: Generate authorization information for the second account to be synchronized; Obtain the authorization result of the user's authorization information.

3. The method according to claim 1, characterized in that, Synchronize the first account with the second account, including: Link the account information of the first account with the account information of the second account; Send the association information of the first and second accounts to the target application requester to complete the synchronization of the first and second accounts.

4. The method according to claim 3, characterized in that, The second account includes multiple accounts; the account information of the first account is linked to the account information of the second account, including: Determine the priority information of multiple accounts within the second account; Based on the priority information of multiple accounts in the second account, the account information of the first account is sequentially associated with the account information of multiple accounts in the second account.

5. The method according to claim 3, characterized in that, Send the association information of the first and second accounts to the target application requester, including: Send the association information of the first and second accounts to the target application requester via mobile applications, instant messaging platforms, or SMS services.

6. The method according to claim 4, characterized in that, Send the synchronization information of the first and second accounts to the target application's backend, including: Based on the priority information of multiple accounts in the second account, the synchronization information of the target account with the highest priority in the second account is sent to the target application backend; If the target account also becomes abnormal, the synchronization information of the next priority account in the second account will be sent to the target application's backend.

7. The method according to any one of claims 1 to 6, characterized in that, The first account exhibited abnormalities, including: The first account cannot be logged in; or, The phone number associated with the first account cannot be reached.

8. The method according to any one of claims 1 to 6, characterized in that, Also includes: If there are no abnormalities in the first account, in response to the user's request for a second account, the synchronization information of the first and second accounts is sent to the target application backend so that the user can handle the business of the first account through the second account.

9. An apparatus for multi-account synchronization, comprising a processor and a memory storing program instructions, characterized in that, The processor is configured to perform the method for multi-account synchronization as described in any one of claims 1 to 8 when executing the program instructions.

10. A communication device, characterized in that, include: The communication equipment itself; The apparatus for multi-account synchronization as described in claim 9 is installed on the main body of the communication device.

Images