Account interoperability methods, devices, equipment and computer-readable media

Abstract

This application relates to a method, apparatus, device, and computer-readable medium for account interoperability. The method includes: upon receiving a login request from a first account, obtaining an account interoperability identifier for the first account; identifying a second account that is jointly bound to the first account with the account interoperability identifier; and responding to the login request by logging in with the first account using the account data of the second account, thereby enabling data interoperability between the first account and the second account. This application maps multiple accounts used by a user on a target platform to a single account through the account interoperability identifier, thus enabling multi-account data interoperability. This ensures that regardless of the login method used by the user, the same account data will be displayed, preventing data loss due to forgotten passwords or account information. It solves the technical problem of inconsistent user experience caused by multiple incompatible accounts on the same platform.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus, device and computer-readable medium for account interoperability. Background Technology

[0002] In today's digital age, various applications are emerging in endless streams, with social software occupying an important part of people's daily lives. Social platforms such as WeChat and QQ, as well as login via mobile phone number, have become common login methods for many apps. However, the current situation is that when the same user logs into the same app using different login methods, multiple independent accounts are often created. For example, if a user registers and logs into a shopping app using their mobile phone number, and then logs into the app using WeChat, the system will generate a completely new WeChat login account unrelated to the mobile phone number login account. This situation brings many inconveniences, requiring users to manage multiple accounts separately, which can easily lead to confusion. When a user forgets the password for one of the accounts, such as the password for the mobile phone number login, and wants to log in using WeChat, because the accounts are not interconnected, they cannot switch directly and must go through a cumbersome password retrieval process to regain access to the mobile phone number account, which greatly reduces the user experience. Moreover, from an information security perspective, if a user accidentally cancels the account associated with a certain login method, such as canceling the WeChat login account, it may result in the loss of some associated personalized settings, shopping records, and other information. Although accounts for other login methods still exist, there are obvious deficiencies in terms of data integration and the continuity of user experience.

[0003] There is currently no effective solution to the problem of data incompatibility and inconsistent user experience caused by multiple user accounts on the same platform not being interconnected. Summary of the Invention

[0004] This application provides a method, apparatus, device, and computer-readable medium for account interoperability, to solve the technical problem that multiple user accounts on the same platform are not interoperable, resulting in data incompatibility and inconsistent user experience.

[0005] According to one aspect of the embodiments of this application, this application provides an account interoperability method, including: upon receiving a login request from a first account, obtaining an account interoperability identifier of the first account; determining a second account that is jointly bound to the first account with the account interoperability identifier; and responding to the login request by logging in with the first account using the account data of the second account, so as to enable data interoperability between the first account and the second account.

[0006] Optionally, the method further includes pre-associating the first account and the second account through the account interoperability identifier in the following manner: upon receiving a registration request to register on the target platform using account information from a third-party platform, generating the first account to log in using the account information from the third-party platform; upon receiving the account interoperability identifier added to the first account, binding the first account to the account interoperability identifier, and searching for other accounts also bound to the account interoperability identifier; upon finding that the second account is bound to the account interoperability identifier, associating the first account with the second account, and sharing the account data of the second account with the first account.

[0007] Optionally, after generating the first account that logs in using the account information of the third-party platform, the method further includes: generating a platform feature code based on the account information of the third-party platform, and binding the platform feature code to the first account, so as to use the platform feature code as an account-independent identifier of the first account; or, generating a random number and binding the random number to the first account, so as to use the random number as an account-independent identifier of the first account.

[0008] Optionally, the method further includes: upon receiving an account cancellation request, obtaining the account interoperability identifier and the account independence identifier carried in the account cancellation request; identifying all accounts bound to the account interoperability identifier as candidate accounts to be cancelled; identifying the target account bound to the account independence identifier from the candidate accounts; and cancelling the target account in response to the account cancellation request.

[0009] Optionally, responding to the account cancellation request and cancelling the target account includes: if the target account is a second account that has shared its own account data, saving the account data of the second account, deleting the account information of the second account, and randomly selecting one of the remaining candidate accounts to inherit the account data of the second account as a new second account; if the target account is a first account that uses shared account data, deleting the first account and the account information of the third-party platform that registered the first account.

[0010] Optionally, pre-associating the first account and the second account through the account interoperability identifier further includes: generating a user profile of the first account based on the account information of the third-party platform on which the first account depends, wherein the account interoperability identifier includes the user profile; performing feature matching between the user profile of the first account and the user profiles of other accounts to determine the matching degree; pushing third accounts with a matching degree greater than or equal to a target threshold to the first account; and associating the first account with the second account upon receiving user selection information for the second account among the third accounts.

[0011] Optionally, the method further includes: acquiring user behavior data on multiple third-party platforms; determining the trust level of multiple accounts of the user on the target platform based on the behavior data of each third-party platform, wherein the multiple accounts are all first accounts that log in to the target platform using account information from different third-party platforms; determining the data sharing scope of the second account to each first account based on the trust level of each first account; and when the first account logs in to the target platform, exchanging data between the first account and the second account according to the data sharing scope.

[0012] According to another aspect of the embodiments of this application, this application provides an account interoperability device, including: an acquisition module, configured to acquire an account interoperability identifier of the first account upon receiving a login request from the first account; a determination module, configured to determine a second account that is jointly bound to the first account with the account interoperability identifier; and an interoperability module, configured to respond to the login request and log in using the account data of the second account with the first account, so as to interoperate data between the first account and the second account.

[0013] According to another aspect of the embodiments of this application, this application provides an electronic device, including a memory, a processor, a communication interface and a communication bus. The memory stores a computer program that can run on the processor. The memory and the processor communicate with each other through the communication bus and the communication interface. When the processor executes the computer program, it implements the steps of the above method.

[0014] According to another aspect of the embodiments of this application, this application also provides a computer-readable medium having processor-executable non-volatile program code that causes the processor to perform the above-described method.

[0015] Compared with related technologies, the technical solutions provided in this application have the following advantages:

[0016] This application provides an account interoperability method, comprising: upon receiving a login request from a first account, obtaining an account interoperability identifier for the first account; identifying a second account that is jointly bound to the first account with the account interoperability identifier; and responding to the login request by logging in with the first account using the account data of the second account, thereby enabling data interoperability between the first account and the second account. This application maps multiple accounts used by a user on a target platform to a single account through the account interoperability identifier, thus enabling multi-account data interoperability. This ensures that regardless of the login method used by the user, the same account data will be displayed, preventing data loss due to forgotten passwords or account information. It solves the technical problem of inconsistent user experience caused by multiple incompatible accounts on the same platform. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the hardware environment for an optional account interoperability method provided according to an embodiment of this application;

[0020] Figure 2 This is a schematic diagram of an optional account interoperability method provided according to an embodiment of this application;

[0021] Figure 3 This is a block diagram of an optional account interoperability device provided according to an embodiment of this application;

[0022] Figure 4 This is a schematic diagram of an optional electronic device structure provided in an embodiment of this application. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

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

[0025] To address the problems mentioned in the background art, according to one aspect of the embodiments of this application, an embodiment of an account interoperability method is provided.

[0026] Optionally, in the embodiments of this application, the above-described account interoperability method can be applied to, for example... Figure 1 The hardware environment shown consists of terminal 101 and server 103. Figure 1 As shown, server 103 is connected to terminal 101 via a network and can be used to provide services to the terminal or clients installed on the terminal. Database 105 can be set up on the server or independently of the server to provide data storage services for server 103. The network mentioned above includes, but is not limited to, wide area network, metropolitan area network or local area network. Terminal 101 includes, but is not limited to, PC, mobile phone, tablet computer, etc.

[0027] One account interoperability method in this application embodiment can be executed by server 103, or it can be jointly executed by server 103 and terminal 101, such as... Figure 2 As shown, the method may include the following steps:

[0028] Step S202: Upon receiving a login request from the first account, obtain the account interoperability identifier of the first account;

[0029] Step S204: Determine the second account that is jointly bound to the first account with the account interoperability identifier;

[0030] Step S206: In response to the login request, the first account logs in using the account data of the second account, so as to enable data exchange between the first account and the second account.

[0031] In this embodiment, the first account is the account the user attempts to log in to on the target platform. It can be an account registered or logged in via various methods such as a mobile phone number or a third-party platform account (e.g., WeChat, QQ). The account interoperability identifier is a unique identifier used to identify a group of accounts that can exchange data. This identifier can be used to associate accounts corresponding to different login methods, achieving account data integration. Specifically, the account interoperability identifier can be a mobile phone number, email address, hardware address, user-defined content, etc. The second account is another account that is jointly bound to the first account and has an account interoperability identifier. This second account's data is interoperable with the first account on the target platform, and it can be considered as the same account to be operated by the user.

[0032] In this embodiment, when a user opens the client of the target platform on a terminal device (such as a mobile phone or computer), enters account information, and clicks the login button, the client sends a login request for the first account to the server (for example, a user enters their mobile phone number and password on a shopping platform and clicks login). Upon receiving the login request, the server first parses the account information in the request and extracts the account interoperability identifier of the first account. (The account interoperability identifier can be pre-stored in the account database or uploaded in real-time when the account requests login). Next, the server searches the database for other accounts bound to the account interoperability identifier to determine the second account. For example, it can use a database query statement to find related account records based on the account interoperability identifier as a filter. Finally, the server processes the login of the first account using the account data of the second account, including loading the second account's user information, preferences, history, and other data, so that the first account displays the same interface and functional permissions as the second account after login, thus completing account data interoperability.

[0033] Taking an online music platform as an example, a user previously registered and logged into the platform using their WeChat account (at this time, the WeChat account corresponds to a second account), and collected some songs and created personalized playlists. Later, the user registered another account using their mobile phone number (this is the first account). When the user logs in using the mobile phone number account, the server finds the associated WeChat account based on the account interoperability identifier of the mobile phone number account, and then uses the WeChat account's collected song list, personalized playlists, and other data to log in. After logging in, the user sees the music collection and playlist content from the previous WeChat account login, as if it were the same account operating experience.

[0034] By linking accounts using different login methods through account interoperability identifiers, seamless integration of account data is achieved when users use multiple login methods on the same platform. Users no longer need to manage account data for different login methods separately, avoiding the problem of data inaccessibility due to forgetting a login method's password or account. This greatly improves the consistency and convenience of the user experience, while also increasing user stickiness to the platform. It also solves the technical problem of data incompatibility and inconsistent user experience caused by multiple incompatible accounts on the same platform.

[0035] In an optional embodiment, the method further includes pre-associating the first account and the second account through the account interoperability identifier in the following manner:

[0036] Step 1: Upon receiving a registration request to register on the target platform using account information from a third-party platform, generate the first account that logs in using the account information from the third-party platform;

[0037] Step 2: Upon receiving the account interoperability identifier added to the first account, bind the first account to the account interoperability identifier, and check if there are other accounts that are also bound to the account interoperability identifier;

[0038] Step 3: If the second account is found to be bound to the account interoperability identifier, associate the first account with the second account and share the account data of the second account with the first account.

[0039] In this embodiment, the account information of the third-party platform refers to the user's registered account and related information on other external platforms (such as social platforms, payment platforms, etc.), such as account name and unique identifier, used for registration or association operations on the target platform. The registration request is an operation instruction initiated by the user when choosing to register using the third-party platform account information on the target platform, including the selected third-party platform and its corresponding account information.

[0040] In this embodiment, account data sharing can be achieved by using one account as the primary account, with all data generated by this primary account and other associated accounts recorded under it. When a user logs in using another account, the account data of the primary account is displayed. Alternatively, account data sharing can involve multiple accounts sharing a single storage address, with all associated accounts accessing the same storage address to read data; essentially, it's sharing storage space. Furthermore, account data sharing can also involve associated accounts exchanging and using each other's user information, business data, such as user profiles, transaction records, and operation history, enabling data interoperability and synchronization between different accounts.

[0041] In this embodiment, when a user chooses to register and log in using a third-party platform account (such as a QQ account) on the target platform client, the client sends a registration request containing QQ account information to the server. Upon receiving the registration request, the server generates a new first account that can be logged in using the QQ account information (this process involves creating a new account record in the target platform's account database and associating it with the QQ account information). If the server subsequently receives an operation to add an account interoperability identifier to this first account (e.g., user-initiated setting or automatic allocation by the platform according to certain rules), the server binds the first account to the account interoperability identifier and searches the database for other accounts also bound to this identifier (by traversing the account interoperability identifier field in the account database). If a second account is found to be bound to the identifier, the server associates the first account with the second account, establishing a data interoperability relationship between them, and shares the second account's account data (such as user avatar, nickname, historical orders, etc.) with the first account, enabling the first account to access and use this data.

[0042] Suppose a user registers on a food recommendation platform using their Alipay account (which is then a third-party platform account), creating their first account. The user then enables account sharing in their personal settings, and the platform assigns an account sharing identifier. If the platform discovers that a previously registered WeChat account (the second account) is linked to the same account sharing identifier, the food recommendation platform will share data such as the WeChat account's profile picture and saved restaurant list with the first Alipay account. After logging in with their Alipay account, the user will then be able to see the saved restaurants associated with their WeChat account, achieving cross-account data sharing.

[0043] By allowing users to quickly register and log in to the target platform using existing third-party platform accounts, the registration process is simplified, lowering the barrier to entry for users. Simultaneously, account interoperability enables account association and data sharing, allowing user accounts across different login methods to be integrated, avoiding data silos, improving user convenience and personalized experience on the platform, and enhancing its attractiveness to users.

[0044] In an optional embodiment, after generating the first account that logs in using the account information of the third-party platform, the method further includes:

[0045] A platform feature code is generated based on the account information of the third-party platform, and the platform feature code is bound to the first account to serve as an independent identifier for the first account; or, a random number is generated and bound to the first account to serve as an independent identifier for the first account.

[0046] In this embodiment, the platform feature code can be a code generated by a specific algorithm based on specific attributes of third-party platform account information (such as account type, registration time, platform rules, etc.) to uniquely identify the first account registered on the target platform. This code can serve as a basis for distinguishing the source and nature of different accounts. The independent account identifier can be a marker used to differentiate each individual account even when accounts are interconnected, ensuring accurate location of a specific account during certain operations (such as account cancellation, permission management, etc.), thus guaranteeing the independence and security of the account system.

[0047] In this embodiment, after the server generates a first account using third-party platform account information (e.g., a user registers and logs into a game platform using a Weibo account to generate the first account), the server begins generating a platform feature code. The server can extract some key information from the Weibo account (such as account ID, registration region, whether it is verified, etc.), calculate it according to a preset algorithm (e.g., a hash algorithm), and obtain a unique platform feature code. Then, the server binds the platform feature code to the first account and stores it in the field associated with the first account in the account database, using it as the unique identifier of the first account (meaning that this platform feature code can be used to identify the uniqueness of the first account in subsequent operations). Alternatively, the server can choose to generate a random number (e.g., use a random number generation function to generate a 16-bit random number string), and similarly bind this random number to the first account as the unique identifier of the account.

[0048] Taking an online education platform as an example, when a user registers and logs in using a Baidu account, the platform generates a platform feature code "EDF56GH78IJKL" based on the Baidu account information (such as username length, registration duration, and whether a mobile phone number is linked), and binds it to the primary account registered with that Baidu account. When a user queries course learning records on the platform, the platform accurately identifies the operation records of the primary account corresponding to this Baidu account through this platform feature code, rather than other accounts. If a random number is used as an independent identifier for the account, assuming the generated random number is "9876543210ABCDEF", it is also used to accurately locate the account when the user performs account-related operations.

[0049] Platform signatures, serving as unique account identifiers, generate meaningful and easily identifiable identifiers based on the inherent attributes of third-party platform accounts. This facilitates better management and tracking of account origins and characteristics within complex account systems. Random numbers, on the other hand, provide a simple and highly randomized method for unique account identifiers, enhancing the security and independence of account identification. Both ensure the distinguishability of each account during operation in an interconnected account environment, providing accurate location data for subsequent operations such as account cancellation and permission allocation, thus guaranteeing the stability and security of the account system.

[0050] In an optional embodiment, the method further includes:

[0051] Step 1: Upon receiving an account cancellation request, obtain the account interoperability identifier and the account independence identifier carried in the account cancellation request;

[0052] Step 2: Identify all accounts bound to the account interoperability identifier as candidate accounts to be cancelled;

[0053] Step 3: Determine the target account that is bound to the account's unique identifier from the candidate accounts; respond to the account cancellation request and cancel the target account.

[0054] In this embodiment, the candidate accounts to be cancelled are selected from the database based on the account interoperability identifier carried in the account cancellation request. All accounts bound to this identifier that may need to be cancelled are filtered out, and these accounts are in a pending cancellation state until further confirmation. The target account is the specific account to be actually cancelled from the candidate accounts to be cancelled, determined by its unique account identifier, ensuring that the cancellation operation accurately targets the account desired by the user.

[0055] In this embodiment, when a user selects the account cancellation function on the target platform client and submits a cancellation request, the client sends the cancellation request to the server. This request includes an account interoperability identifier and an account-specific identifier carried in the cancellation request (for example, when a user decides to cancel an account registered with their mobile phone number on an e-commerce platform, they upload both the account interoperability identifier and the account-specific identifier along with the cancellation request). Upon receiving the cancellation request, the server first searches the database for all accounts bound to the account interoperability identifier, identifying these accounts as candidate accounts to be cancelled (possibly by executing a database query, using the account interoperability identifier as a filter to obtain relevant account records). Then, the server further filters these candidate accounts based on the account-specific identifier, determining the target account that perfectly matches the account-specific identifier in the cancellation request (for example, among multiple accounts bound to the same account interoperability identifier, finding the account whose account-specific identifier matches the uploaded random number). Finally, the server performs the account cancellation operation, deleting the target account's information, including the third-party platform account information used to register the target account, but without changing other associated accounts.

[0056] For example, on a social media platform, a user has an account logged in using QQ (Account 1) and an account logged in using a mobile phone number (Account 2), linked by an account interoperability identifier. If a user wants to cancel their QQ account, they initiate a cancellation request and upload the QQ account's interoperability identifier and unique identifier (let's say the platform feature code "XYZ123"). The server first finds all accounts bound to this interoperability identifier (i.e., the QQ login account and the mobile phone number login account) as candidate accounts. Then, based on the unique identifier "XYZ123", it determines the QQ login account as the target account and ultimately deletes the QQ login account and its related data from the database and storage system. The login account corresponding to the mobile phone number remains unaffected.

[0057] The dual identification mechanism of account interoperability and independent account identifiers ensures the accuracy of account cancellation operations. While enabling account interoperability, it avoids the accidental cancellation of other associated accounts. Users can confidently manage their accounts, precisely deleting unnecessary accounts as needed, while ensuring the integrity and availability of other account data. This enhances users' sense of control over account management and improves platform security.

[0058] In an optional embodiment, responding to the account cancellation request and cancelling the target account includes:

[0059] In the case where the target account is the second account that shared its own account data, the account data of the second account is saved, the account information of the second account is deleted, and one of the remaining candidate accounts is selected to inherit the account data of the second account as a new second account.

[0060] If the target account is the first account that uses shared account data, delete the first account and the account information of the third-party platform that registered the first account.

[0061] In this embodiment, when the server determines that the target account is a second account that has shared its own account data (for example, in a multi-platform membership system, a primary account acts as a second account to share membership benefits data with other associated primary accounts), the server first backs up the second account's account data (copying the data to a specific backup storage area, such as a backup database or cloud storage). Next, the server deletes the second account's account information (including account name, login credentials, etc., but retains the backed-up data) from the database, preventing it from logging in with the original account. Finally, the server selects one from the remaining candidate accounts (i.e., other accounts bound to the account's interoperability identifier) ​​(for example, selecting the first account in order of account registration time), inherits the second account's account data, including membership benefits, personalized settings, etc., making it a new second account, which continues to provide data sharing services to other associated accounts.

[0062] In this embodiment of the application, when the target account is the first account that uses shared account data (such as a sub-account using the membership benefits shared by the main account), the server directly deletes the first account and the account information of the third-party platform that registered the first account (deletes the account record from the target platform database and disconnects the association with the third-party platform account), because the first account mainly relies on shared data and has relatively little data of its own and is not independent, so it can be directly deleted when canceling the account.

[0063] Taking a video streaming platform as an example, a user has a premium membership account registered via WeChat (the second account) and linked to a regular account registered with a mobile phone number (the first account). If the user decides to cancel the WeChat-registered premium membership account (which serves as the second account sharing its data), the platform first backs up the premium membership account's viewing history, favorite videos, membership expiration date, and other data, then deletes the WeChat account's login information. Next, the user selects the mobile phone number-registered account, inherits the backed-up premium membership data, and the mobile phone number account becomes the new account with premium membership benefits. If the user wants to cancel the mobile phone number-registered regular account (which serves as the first account using the shared account data), the platform directly deletes the mobile phone number account and its associated mobile phone number information. The WeChat-registered premium membership account remains unaffected, and its shared data can still be used by other potentially linked accounts.

[0064] The cancellation process for a second account that shares its own account data ensures data security (through backup) and a smooth transition of the account system (through account data inheritance), preventing disruption to the use of other related accounts and maintaining a consistent user experience. The cancellation of the first account using shared account data effectively and efficiently cleans up non-independent accounts and their associated information, avoiding data redundancy and potential security risks. It also protects the data integrity and availability of shared accounts (such as the second account), optimizing the efficiency and security of account management.

[0065] In an optional embodiment, pre-associating the first account and the second account via the account interoperability identifier further includes:

[0066] Step 1: Generate a user profile for the first account based on the account information of the third-party platform on which the first account depends, wherein the account interoperability identifier includes the user profile;

[0067] Step 2: Perform feature matching between the user profile of the first account and the user profiles of other accounts to determine the matching degree;

[0068] Step 3: Push third accounts with a matching degree greater than or equal to the target threshold to the first account;

[0069] Step 4: Upon receiving the user's selection information for the second account among the third accounts, associate the first account with the second account.

[0070] In this embodiment, the user profile is a collection of multi-dimensional information describing user characteristics, interests, and behavioral patterns, constructed based on the user's account information on a third-party platform (such as browsing history, consumption records, social relationships, etc.). It can be used for personalized recommendations, account association matching, and other operations. The target threshold is a pre-set numerical standard used to determine whether the user profile matching degree is high enough for account association recommendations. When the matching degree is greater than or equal to the target threshold, the two accounts are considered to have a high degree of correlation and recommendability.

[0071] In this embodiment, when the server wants to pre-associate a first account and a second account through an account interoperability identifier, it first collects data such as the browsing product categories, purchase history, and review content of the Taobao account based on the account information of the third-party platform on which the first account depends (for example, a user registers and logs into a travel platform using a Taobao account to generate the first account, where the Taobao account information is the account information of the dependent third-party platform). Through data analysis and modeling techniques (such as cluster analysis and feature extraction in machine learning algorithms), the server constructs a user profile of the first account (for example, generating a user profile containing features such as the user's preferred travel destination type, spending power level, and travel time preference), and uses this profile as part of the account interoperability identifier (meaning the account interoperability identifier contains user profile information for more accurate account association). Next, the server performs feature matching between the user profile of the first account and the user profiles of other accounts (accounts that already exist on the target platform and may be associated). This process involves comparing and calculating various feature dimensions (such as travel destination preference and spending power) in the two user profiles, and using a suitable similarity algorithm (such as cosine similarity algorithm) to obtain the matching degree (for example, calculating the similarity score of the two user profiles on multiple features). Then, the server filters out third accounts with a matching degree greater than or equal to the target threshold (assuming the target threshold is set to 0.7, indicating a high similarity). These accounts have a high similarity to the first account in terms of user profile features and are pushed to the first account (for example, when the first account logs into the travel platform, these potentially associated third accounts are displayed in the recommendation list). Finally, when the server receives the user's selection information for a second account among the third accounts (such as when the user clicks to confirm associating an account in the recommendation list), the server officially associates the first account with the second account, establishing a data exchange relationship between the two and realizing account integration.

[0072] Taking a fitness app as an example, a user registers and logs in using their Keep account (as a third-party platform account), generating their first account. The server builds a user profile based on the user's exercise records in the Keep account (such as frequent aerobic exercise, following weight loss and fitness courses, etc.). This profile is then matched against the user profiles of other existing accounts in the app. If another account (a third account) is found whose user profile also shows frequent aerobic exercise and following similar fitness courses, with a match score of 0.8 (greater than the target threshold of 0.7), this third account is pushed to the user. If the user confirms that this account is associated with their first account as a second account, then when the user logs in to the fitness app using their first account, they can access personalized training plans, exercise achievements, and other data from the second account, achieving precise account association and data exchange based on user profiles.

[0073] By building user profiles and performing feature matching, the potential connections between different user accounts can be discovered more accurately, providing users with account association recommendations that better match their needs and habits. This improves the accuracy and user acceptance of account association, making account integration smoother and more targeted for users, further optimizing the user experience. It also helps the platform better understand user behavior, providing stronger data support for personalized services.

[0074] In an optional embodiment, the method further includes:

[0075] Step 1: Obtain user behavior data across multiple third-party platforms;

[0076] Step 2: Based on the behavioral data of each of the third-party platforms, determine the trust level of multiple accounts of the user on the target platform, wherein the multiple accounts are all the first account that logs into the target platform using account information from different third-party platforms;

[0077] Step 3: Determine the scope of data sharing between the second account and each first account based on the trust level of each first account;

[0078] Step 4: When the first account logs into the target platform, the first account and the second account exchange data according to the data sharing scope.

[0079] In this embodiment, the behavioral data of a third-party platform refers to various data records generated when a user operates on a third-party platform, including but not limited to browsing records (such as pages viewed, dwell time, etc.), search keywords, likes and favorites, comment content, transaction records (details of purchased goods or services, amount, time, etc.), and social interaction behaviors (following, adding friends, participating in groups, etc.). These data comprehensively reflect the user's interests, consumption habits, social relationships, and behavioral patterns. Trust level is an indicator used to measure the credibility and security of accounts logged in using different third-party platform account information on a target platform. It is derived from a comprehensive evaluation of the user's behavioral data on the third-party platform. The higher the trust level, the higher the reliability of the account in the process of account interoperability and data sharing, and the wider the scope of data sharing and the higher the operational permissions it can enjoy. The scope of data sharing refers to the degree and scope to which an account (such as a second account) allows other associated accounts (such as a first account) to access and use its data during account interoperability, determined according to the account's trust level. Accounts with high trust levels may grant more sensitive data and functional permissions, while accounts with low trust levels may only share some basic data to balance user experience and data security.

[0080] In this embodiment, the server first obtains user behavior data from multiple third-party platforms (such as WeChat, Taobao, Weibo, etc.) (for example, by connecting to the data interfaces of third-party platforms and obtaining user-authorized data according to agreed data formats and permissions). During the data acquisition process, relevant laws and regulations and the privacy policies of the third-party platforms are strictly followed to ensure the compliance of data acquisition. The platform clearly informs users of the purpose, scope, and usage of the data acquisition, and only collects data after obtaining explicit authorization from the user. For example, when a user logs into the target platform for the first time using a third-party account, a detailed privacy prompt pops up, explaining which third-party platform behavior data will be obtained and how this data will be used for account interoperability and personalized services. The data acquisition process will only begin after the user clicks to agree to the authorization.

[0081] Next, for the behavioral data of each third-party platform, the server uses data analysis algorithms (such as machine learning-based classification algorithms, statistical analysis methods, etc.) to process it to determine the trust level of multiple accounts of the user on the target platform (i.e., the first account logged into the target platform using different third-party platform account information). For example, if the behavioral data of an account shows that the user has a long-term and stable consumption record, positive social interaction, and no bad behavior (such as fraud, illegal transactions, etc.) on the platform, then the trust level of the account may be assessed as high; conversely, if the behavioral data is abnormal (such as frequently changing login devices, involving fraudulent risk transactions, etc.), the trust level will be low. Specifically, a weight may be assigned to each factor affecting the trust level (such as a weight of 0.4 for consumption record, 0.3 for social interaction, and -0.3 for risky behavior), and a trust score may be obtained by weighted calculation (e.g., trust score = consumption record score * 0.4 + social interaction score * 0.3 + risky behavior score * (-0.3)).

[0082] Then, based on the trust level of each primary account, the server determines the scope of data sharing between the secondary account and each primary account. Generally, a primary account with a high trust level may be allowed to access more sensitive data from the secondary account, such as detailed personal information, complete transaction history, and data related to premium membership benefits; while a primary account with a low trust level may only be able to obtain some basic data, such as publicly available usernames, avatars, and limited historical operation records. This process can be achieved through a pre-defined trust level-data sharing scope mapping table, with different data sharing configurations corresponding to different trust level ranges (for example, a trust level between 80-100 points allows sharing of all data; a trust level between 60-80 points allows sharing of most data except for financially sensitive information; and a trust level below 60 points only allows sharing of basic public information).

[0083] Finally, when the first account logs into the target platform, the server facilitates data exchange between the first and second accounts according to the previously determined data sharing scope. For example, when a highly trusted first account logs in, the server retrieves the complete data of the second account from the database, integrates and pushes it according to business logic, enabling the first account to display and use the relevant data of the second account on the login interface, achieving personalized services and experiences. For a low-trust first account, the server only pushes basic data, ensuring data security while providing certain basic services.

[0084] Taking an online financial services platform as an example, a user registers and logs in using an Alipay account (a third-party platform account) to generate account A, and simultaneously registers and logs in using a JD.com account to generate account B. The server obtains data from Alipay showing large and stable transaction amounts, indicating frequent Alipay use for financial investments. From JD.com, it obtains data showing occasional purchases of electronic products and some product reviews. Explicit authorization from the user was obtained before obtaining this data, adhering to relevant privacy regulations and platform policies. Data analysis reveals that Alipay behavior data for account A indicates high financial activity and stability, thus assigning account A a high trust score (e.g., 90 points). In contrast, JD.com behavior data for account B is relatively ordinary, resulting in a trust score of 65 points. According to the trust-data sharing scope mapping table, when logging into the financial services platform, account A can access comprehensive data, including all investment portfolio information and detailed financial statement analysis of the platform's core account (second account), enabling more in-depth financial management and decision-making. However, when account B logs in, it can only access basic account balances and recent transaction records, and cannot view sensitive investment strategies and detailed financial information. This approach ensures user data security while providing personalized data sharing services based on user behavior on third-party platforms.

[0085] By introducing behavioral data from third-party platforms to assess account trust levels and determine the scope of data sharing accordingly, a personalized account interoperability experience based on user behavior characteristics is achieved while ensuring data security. On the one hand, for high-trust accounts, richer and deeper data sharing is provided, improving service quality and operational convenience for users on the target platform, enhancing user stickiness and satisfaction. On the other hand, for low-trust accounts, limiting the scope of data sharing effectively reduces the risk of data leakage, protecting users' core interests and the platform's security and stability. Simultaneously, this dynamic trust assessment and data sharing mechanism based on behavioral data can adapt to the diverse needs and changing behavioral patterns of different users, making the platform's account management and services more intelligent, flexible, and secure. Furthermore, throughout the entire data acquisition and usage process, strict compliance measures ensure that user privacy is fully respected and protected, complying with legal and regulatory requirements, and enhancing the platform's reputation and user trust.

[0086] This application provides an account interoperability method, comprising: upon receiving a login request from a first account, obtaining an account interoperability identifier for the first account; identifying a second account that is jointly bound to the first account with the account interoperability identifier; and responding to the login request by logging in with the first account using the account data of the second account, thereby enabling data interoperability between the first account and the second account. This application maps multiple accounts used by a user on a target platform to a single account through the account interoperability identifier, thus enabling multi-account data interoperability. This ensures that regardless of the login method used by the user, the same account data will be displayed, preventing data loss due to forgotten passwords or account information. It solves the technical problem of inconsistent user experience caused by multiple incompatible accounts on the same platform.

[0087] According to another aspect of the embodiments of this application, such as Figure 3 As shown, an account interoperability device is provided, comprising:

[0088] The acquisition module 301 is used to acquire the account interoperability identifier of the first account when a login request of the first account is received.

[0089] The determination module 303 is used to determine a second account that is jointly bound to the first account and has the account interoperability identifier.

[0090] Interoperability module 305 is used to respond to the login request and log in using the account data of the second account with the first account, so as to enable data interoperability between the first account and the second account.

[0091] It should be noted that the acquisition module 301 in this embodiment can be used to execute step S202 in this application embodiment, the determination module 303 in this embodiment can be used to execute step S204 in this application embodiment, and the communication module 305 in this embodiment can be used to execute step S206 in this application embodiment.

[0092] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the content disclosed in the above embodiments. It should also be noted that the above modules, as part of a device, can operate in environments such as... Figure 1 The hardware environment shown can be implemented either through software or through hardware.

[0093] Optionally, the device further includes:

[0094] According to another aspect of the embodiments of this application, this application provides an electronic device, such as... Figure 4As shown, the system includes a memory 401, a processor 403, a communication interface 405, and a communication bus 407. The memory 401 stores a computer program that can run on the processor 403. The memory 401 and the processor 403 communicate through the communication interface 405 and the communication bus 407. When the processor 403 executes the computer program, it implements the steps of the above method.

[0095] The memory and processor in the aforementioned electronic devices communicate with each other via a communication bus and a communication interface. The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0096] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0097] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0098] According to another aspect of the embodiments of this application, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of any of the above embodiments.

[0099] Optionally, in embodiments of this application, the computer-readable medium is configured to store program code for the processor to perform the following steps:

[0100] Upon receiving a login request from the first account, obtain the account interoperability identifier of the first account;

[0101] Identify a second account that is jointly bound to the first account and has the account interoperability identifier;

[0102] In response to the login request, the first account logs in using the account data of the second account, so as to enable data exchange between the first account and the second account.

[0103] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments, and will not be repeated here.

[0104] In specific implementation, the embodiments of this application can be referred to the above embodiments and have corresponding technical effects.

[0105] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described herein, or combinations thereof.

[0106] For software implementation, the techniques described herein can be implemented by units that perform the functions described herein. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0107] 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 this application.

[0108] Those skilled in the art will 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.

[0109] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0110] 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 can be selected to achieve the purpose of this embodiment according to actual needs.

[0111] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0112] If the aforementioned function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several 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 methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks. It should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. In the absence of further restrictions, an element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0113] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for account interoperability, characterized in that, include: Upon receiving a login request from the first account, obtain the account interoperability identifier of the first account; Identify a second account that is jointly bound to the first account and has the account interoperability identifier; In response to the login request, the first account logs in using the account data of the second account, so as to enable data exchange between the first account and the second account; The step of logging in with the first account using the account data of the second account includes: logging in with the first account and loading the user information, preference settings and history of the second account, so that the first account presents the same interface and functional permissions as the second account after logging in, thereby completing the interoperability of account data; The method further includes: acquiring user behavior data on multiple third-party platforms; determining the trust level of multiple accounts of the user on the target platform based on the behavior data of each third-party platform, wherein the multiple accounts are all first accounts that log in to the target platform using account information from different third-party platforms; determining the data sharing scope of the second account to each first account based on the trust level of each first account; and exchanging data between the first account and the second account according to the data sharing scope when the first account logs in to the target platform. The trust score is calculated as follows: consumption record score * 0.4 + social interaction score * 0.3 + risk behavior score * (-0.3). If the trust score is between 80 and 100, all data is shared; if the trust score is between 60 and 80, data other than financially sensitive information is shared; if the trust score is below 60, only basic public information is shared.

2. The method according to claim 1, characterized in that, The method further includes pre-associating the first account and the second account through the account interoperability identifier in the following manner: Upon receiving a registration request that uses account information from a third-party platform to register on the target platform, a first account is generated that logs in using the account information from the third-party platform; Upon receiving the account interoperability identifier added to the first account, bind the first account to the account interoperability identifier, and check whether there are other accounts that are also bound to the account interoperability identifier; If the second account is found to be bound to the account interoperability identifier, the first account and the second account are associated, and the account data of the second account is shared with the first account.

3. The method according to claim 2, characterized in that, After generating the first account that logs in using the account information of the third-party platform, the method further includes: A platform feature code is generated based on the account information of the third-party platform, and the platform feature code is bound to the first account to serve as an independent identifier for the first account; or, A random number is generated and bound to the first account, so that the random number serves as an independent identifier for the first account.

4. The method according to claim 3, characterized in that, The method further includes: Upon receiving an account cancellation request, obtain the account interoperability identifier and the account independence identifier carried in the account cancellation request; All accounts bound to the aforementioned account interoperability identifier will be identified as candidate accounts to be cancelled; From the candidate accounts, determine the target account that is bound to the account's unique identifier; In response to the account cancellation request, the target account is cancelled.

5. The method according to claim 4, characterized in that, The process of responding to the account cancellation request and canceling the target account includes: In the case where the target account is the second account that shared its own account data, the account data of the second account is saved, the account information of the second account is deleted, and one of the remaining candidate accounts is selected to inherit the account data of the second account as a new second account. If the target account is the first account that uses shared account data, delete the first account and the account information of the third-party platform that registered the first account.

6. The method according to claim 2, characterized in that, Pre-associating the first account and the second account using the account interoperability identifier also includes: Based on the account information of the third-party platform on which the first account depends, a user profile of the first account is generated, wherein the account interoperability identifier includes the user profile; The user profile of the first account is matched with the user profiles of other accounts to determine the degree of matching. Push third accounts with a matching degree greater than or equal to the target threshold to the first account; Upon receiving the user's selection information for the second account among the third accounts, the first account is associated with the second account.

7. An account interoperability device for implementing the account interoperability method as described in any one of claims 1 to 6, characterized in that, include: The acquisition module is used to acquire the account interoperability identifier of the first account when a login request for the first account is received. The determination module is used to determine a second account that is jointly bound to the first account with the account interoperability identifier; The interoperability module is used to respond to the login request and log in using the account data of the second account with the first account, so as to enable data interoperability between the first account and the second account.

8. An electronic device comprising a memory, a processor, a communication interface, and a communication bus, wherein the memory stores a computer program executable on the processor, and the memory and the processor communicate via the communication bus and the communication interface, characterized in that... When the processor executes the computer program, it implements the account interoperability method according to any one of claims 1 to 6.

9. A computer-readable medium having processor-executable non-volatile program code, characterized in that, The program code causes the processor to execute the account interoperability method according to any one of claims 1 to 6.

Images