Account management method, graphical interface, and related apparatus

Abstract

Disclosed in the present application are an account management method, a graphical interface, and a related apparatus. In the method, an electronic device can collect personalized data of a plurality of applications, different applications belong to different developers, wherein the personalized data is used for reflecting the preferences of a user when browsing the applications, and the personalized data is associated with a first account logged in on the electronic device; and the electronic device can log in to the first account on an application and notify a manufacturer server that the personalized data associated with the first account is to be sent to an application server of the application, such that the electronic device can display pushed content screened out by the application server from content provided by the application on the basis of the personalized data associated with the first account. It can be seen that in the method, an account can be used as a personalized-data storage and flowing medium of a user, such that when the user installs or updates an application and uses same for the first time, the application can precisely push content that the user is interested in, thereby enhancing the user's browsing experience.

Description

Account management method, graphical interface and related devices

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 22, 2023, with application number 202311577162.7, and priority to the Chinese patent application entitled “Account management method, graphical interface and related devices”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal and communication technology, and in particular to an account management method, a graphical interface, and related devices. Background Art

[0003] With the continuous development of the terminal market, a variety of applications have been developed to meet users' entertainment needs. Currently, applications with content recommendation functions are among the most popular. These applications, including e-commerce applications, video applications, music applications, and more, continuously collect personalized data such as user browsing history and personal information, analyze user interests and hobbies, and accurately push content of interest to users, including pictures, products, videos, music, etc., providing users with more personalized and intelligent entertainment services.

[0004] However, the content recommendation function of the application requires users to use the application for a period of time before it can achieve accurate content push. This means that when users first use such applications, they cannot experience the service of accurate content push, which reduces the user experience.

[0005] Summary of the Invention

[0006] This application provides an account management method, a graphical interface, and related devices, which utilize system accounts as a medium for transmitting personalized data between applications, thereby achieving more accurate content push services for applications.

[0007] In a first aspect, an embodiment of the present application provides an account management method, the method comprising: a first device sends personalized data of a first application and a second application to a manufacturer server, the first application and the second application belong to different developers, the personalized data is used to reflect the user's preferences when browsing application content, and the personalized data is associated with a first account logged in on the first device; the first device sends a first message to the manufacturer server; the manufacturer server responds to the first message and sends the personalized data associated with the first account to an application server of a third application; the first device displays the first content of the third application, the third application is logged in with the first account, and the first content is push content filtered by the application server of the third application from the content provided by the third application based on the personalized data associated with the first account.

[0008] By implementing the method provided in the first aspect, the system account can be used as the user's personalized data storage and flow intermediary, and the personalized data generated by the user when using the application can be bound to the system account, so that each application logged in to the system account can share the personalized data generated by each application. Even if the user has never used the application, as long as the system account is logged in to the application, the application can accurately push content that the user is interested in based on the personalized data collected under the system account, thereby solving the cold start problem when the user uses the application and improving the user's usage experience.

[0009] In combination with the first aspect, in one implementation, the developer of the third application is different from the developers of the first application and the second application.

[0010] It can be seen that this method can realize the sharing of personalized data between applications developed by different developers, break the information barriers between applications, and solve the current problem that personalized data cannot flow between applications.

[0011] In combination with the first aspect, in one implementation, before the first device sends the personalized data of the first application and the second application to the manufacturer server, the method further includes: the first device collecting the personalized data of the first application and the second application through a unified interface.

[0012] In combination with the first aspect, in one implementation, the method further includes: the manufacturer server generates a first identity code for the first account, the first identity code is used to indicate personalized data associated with the first account; the manufacturer server sends the first identity code to the first device; and the first device displays the first identity code.

[0013] In other words, this method uses an identity code to represent the user's personalized digital identity and protect the privacy of user data.

[0014] In combination with the first aspect, in one implementation, the method also includes: the first device obtains personalized data associated with the second account logged in on the second device; the first device sends a second message to the manufacturer server; the manufacturer server responds to the second message and sends the personalized data associated with the second account to the application server of the fourth application; the first device displays the second content of the fourth application, the fourth application is logged in with the first account, and the second content is push content filtered by the application server of the fourth application from the content provided by the fourth application based on the personalized data associated with the second account.

[0015] In other words, personalized data can be shared between devices, allowing users to browse content that other users are interested in on the devices they use, enabling information sharing among family and friends, and enriching the content recommended by recommendation applications.

[0016] In combination with the first aspect, in one implementation, the method also includes: the first device obtains personalized data associated with the second account logged in on the second device; the first device sends a second message to the manufacturer server; the manufacturer server responds to the second message and sends the personalized data associated with the first account and the personalized data associated with the second account to the application server of the fourth application; the first device displays the second content of the fourth application, the fourth application is logged in with the first account, and the second content is push content filtered by the application server of the fourth application based on the personalized data associated with the first account and the personalized data associated with the second account from the content provided by the fourth application.

[0017] In other words, personalized data can be shared between devices, allowing users to browse content that interests them and other users on the devices they use, enabling information sharing among family and friends, and enriching the content recommended by recommendation applications.

[0018] In combination with the first aspect, in one implementation, after the first device displays the second content of the fourth application, the method also includes: the first device updates the second content to third content based on a user operation, where the third content is push content filtered out by the application server of the fourth application from the content provided by the fourth application based on the personalized data associated with the first account or the personalized data associated with the second account.

[0019] That is to say, when a user can browse content of interest to multiple users through an application, the user can also update the displayed content to content of interest to some users according to their own needs, thereby meeting the user's personalized browsing needs when browsing application content.

[0020] In combination with the first aspect, in one implementation, before the first device obtains the personalized data associated with the second account logged in on the second device, the method also includes: the first device scans the second identity code of the second account, where the second identity code is used to indicate the personalized data associated with the second account.

[0021] It can be seen that the identity code of the system account can be used as a medium for sharing personalized data between devices, which improves the convenience of sharing personalized data between accounts, while also protecting the user's data privacy as much as possible and reducing the risk of information leakage.

[0022] In combination with the first aspect, in one implementation, after the first device displays the second content of the fourth application, the method also includes: the first device receives an instruction message sent by the second device to cancel sharing of personalized data, or detects a user operation to cancel sharing of personalized data; the first device sends a third message to the manufacturer server; the manufacturer server responds to the third message and sends the personalized data associated with the first account to the application server of the fifth application; the first device displays the fourth content of the fifth application, the fifth application is logged in with the first account, and the fourth content is push content filtered by the application server of the fifth application from the content provided by the fifth application based on the personalized data associated with the first account.

[0023] If the electronic device no longer uses the personalized data shared by other devices, the electronic device can switch back to the personalized data originally associated with the system account. In this way, when the application logs in to the system account, the personalized data originally associated with the system account can be used to push content.

[0024] In combination with the first aspect, in one implementation, the method further includes: the first device displays a first interface, where the first interface is used to display a sharing status of the personalized data associated with the first account in one or more accounts.

[0025] In this way, users can view the usage of the personalized data of the local account by accounts on other devices.

[0026] In combination with the first aspect, in one implementation, the first interface includes a first control, and the method further includes: the first device detects a user operation acting on the first control, and shares the personalized data associated with the first account with the second account, or cancels sharing with the second account.

[0027] In this way, users can control other accounts' access rights to the local account's personalized data and ensure the secure sharing of data.

[0028] In combination with the first aspect, in one implementation, the method further includes: the first device displays a second interface, where the second interface is used to display access status of personalized data associated with the first account in one or more applications.

[0029] In this way, users can view the usage of personalized data associated with the system account by each application at any time.

[0030] In combination with the first aspect, in one implementation, the second interface includes a second control, and the method further includes: the first device detects a user operation acting on the second control, and allows or denies the application to access personalized data associated with the first account.

[0031] In this way, users can control the permissions of each application to use personalized data.

[0032] In combination with the first aspect, in one implementation, after the first device displays the first content of the third application, the method also includes: the first device collects personalized data of the third application and sends it to the manufacturer server; the manufacturer server updates the personalized data associated with the first account based on the personalized data of the third application.

[0033] In other words, the electronic device can continue to collect personalized data generated by the application after logging into the system account, update the personalized data associated with the system account, and achieve more accurate content recommendations for the application.

[0034] In combination with the first aspect, in one implementation, the first device sends the personalized data of the first application and the second application to the manufacturer server, specifically including: the first device extracts features from the personalized data of the first application and the second application, and converts the personalized data into a first feature vector; the first device sends the first feature vector to the manufacturer server.

[0035] That is to say, the personalized data sent by the electronic device can be formatted data, which reduces the amount of computation on the manufacturer's server and also reduces the amount of data sent by the electronic device.

[0036] In combination with the first aspect, in one implementation, the manufacturer server sends the personalized data associated with the first account to the application server of the third application, specifically including: the manufacturer server sends the second feature vector to the application server of the third application, the second feature vector is used to indicate the personalized data associated with the first account, and the vector dimension of the second feature vector matches the vector dimension of the data used by the application server of the third application to determine the first content.

[0037] That is, the data sent by the manufacturer server to the application server can be personalized data after the data format is adapted, which can reduce the computation load of the application server.

[0038] In a second aspect, an embodiment of the present application provides an account management method, which includes: a first device sends personalized data of a first application and a second application to a manufacturer server, the first application and the second application belong to different developers, the personalized data is used to reflect the user's preferences when browsing application content, and the personalized data is associated with a first account logged in on the first device; the first device receives a first identity code sent by the manufacturer server, the first identity code is used to indicate the personalized data associated with the first account; the first device displays the first identity code; the first device displays the first content of a third application, the third application is logged in with the first account, and the first content is related to the personalized data associated with the first account.

[0039] By implementing the method provided in the second aspect, the system account can be used as the user's personalized data storage and flow intermediary, and the personalized data generated by the user when using the application can be bound to the system account, so that each application logged in to the system account can share the personalized data generated by each application. Even if the user has never used the application, as long as the system account is logged in to the application, the application can accurately push content that the user is interested in based on the personalized data collected under the system account, thereby solving the cold start problem when the user uses the application and improving the user's usage experience.

[0040] In combination with the second aspect, in one implementation, before the first device displays the first content of the third application, the method further includes: the first device sending the personalized data associated with the first account to the application server of the third application.

[0041] That is to say, when the electronic device needs to display the pushed content of the application, the electronic device can directly send the personalized data associated with the system account to the application server, avoiding the intervention of the manufacturer's server and speeding up the application server to obtain the personalized data.

[0042] It is understood that, in addition to directly sending the personalized data associated with the local system account to the application server, the electronic device may also notify the manufacturer server to send the personalized data to the application server. For example, the first device may send a first message to the manufacturer server, and the manufacturer server, in response to the first message, may send the personalized data associated with the first account to the application server of the third application.

[0043] In conjunction with the second aspect, in one implementation, the developer of the third application is different from the developers of the first application and the second application.

[0044] In conjunction with the second aspect, in one implementation, before the first device sends the personalized data of the first application and the second application, the method further includes: the first device collecting the personalized data of the first application and the second application through a unified interface.

[0045] In combination with the second aspect, in one implementation, the method also includes: the first device obtains personalized data associated with the second account logged in on the second device; the first device displays the second content of the fourth application, the fourth application is logged in with the first account, and the second content is related to the personalized data associated with the second account.

[0046] In other words, personalized data can be shared between devices, allowing users to browse content that other users are interested in on the devices they use, enabling information sharing among family and friends, and enriching the content recommended by recommendation applications.

[0047] In combination with the second aspect, in one implementation, the method also includes: the first device obtains personalized data associated with the second account logged in on the second device; the first device displays the second content of the fourth application, the fourth application is logged in with the first account, and the second content is related to the personalized data associated with the first account and the personalized data associated with the second account.

[0048] In other words, personalized data can be shared between devices, allowing users to browse content that interests them and other users on the devices they use, enabling information sharing among family and friends, and enriching the content recommended by recommendation applications.

[0049] In combination with the second aspect, in one implementation, before the first device displays the second content of the fourth application, the method further includes: the first device sending the personalized data associated with the first account and the personalized data associated with the second account to an application server of the fourth application.

[0050] That is to say, when an electronic device needs to display the pushed content of an application, the electronic device can directly send the personalized data associated with the local system account and the personalized data shared by other accounts to the application server, avoiding the intervention of the manufacturer's server and speeding up the application server to obtain personalized data.

[0051] It is understood that, in addition to directly sending the personalized data associated with the local system account and the personalized data shared by other accounts to the application server, the electronic device may also notify the manufacturer server to send the aforementioned personalized data to the application server. For example, the first device may send a second message to the manufacturer server, and the manufacturer server, in response to the second message, may send the personalized data associated with the first account and the personalized data associated with the second account to the application server of the fourth application.

[0052] In combination with the second aspect, in one implementation, after the first device displays the second content of the fourth application, the method also includes: the first device updates the second content to third content based on user operation, and the third content is related to the personalized data associated with the first account or the personalized data associated with the first account.

[0053] That is to say, when a user can browse content of interest to multiple users through an application, the user can also update the displayed content to content of interest to some users according to their own needs, thereby meeting the user's personalized browsing needs when browsing application content.

[0054] In combination with the second aspect, in one implementation, before the first device obtains the personalized data associated with the second account logged in on the second device, the method also includes: the first device scans the second identity code of the second account, where the second identity code is used to indicate the personalized data associated with the second account.

[0055] It can be seen that the identity code of the system account can be used as a medium for sharing personalized data between devices, which improves the convenience of sharing personalized data between accounts, while also protecting the user's data privacy as much as possible and reducing the risk of information leakage.

[0056] In combination with the second aspect, in one implementation, after the first device displays the second content of the fourth application, the method also includes: the first device receives an instruction message sent by the second device to cancel sharing of personalized data, or detects a user operation to cancel sharing of personalized data; the first device displays the fourth content of the fifth application, the fifth application is logged in with the first account, and the fourth content is related to the personalized data associated with the first account.

[0057] If the electronic device no longer uses the personalized data shared by other devices, the electronic device can switch back to the personalized data originally associated with the system account. In this way, when the application logs in to the system account, the personalized data originally associated with the system account can be used to push content.

[0058] In combination with the second aspect, in one implementation, the method further includes: the first device displays a first interface, where the first interface is used to display a sharing status of the personalized data associated with the first account in one or more accounts.

[0059] In combination with the second aspect, in one implementation, the first interface includes a first control, and the method further includes: the first device detects a user operation acting on the first control, and shares the personalized data associated with the first account with the second account, or cancels sharing with the second account.

[0060] In this way, users can view the usage of the personalized data of the local account by accounts on other devices, control the usage permissions of other accounts to the personalized data of the local account, and ensure the secure sharing of data.

[0061] In combination with the second aspect, in one implementation, the method further includes: the first device displays a second interface, where the second interface is used to display access status of personalized data associated with the first account in one or more applications.

[0062] In combination with the second aspect, in one implementation, the second interface includes a second control, and the method further includes: the first device detects a user operation acting on the second control, and allows or denies the application to access personalized data associated with the first account.

[0063] In this way, users can view the usage of personalized data associated with the system account by each application at any time and control the permission of each application to use personalized data.

[0064] In combination with the second aspect, in one implementation, after the first device displays the first content of the third application, the method further includes: the first device collects and sends personalized data of the third application, and the personalized data of the third application is used to update the personalized data associated with the first account.

[0065] In other words, the electronic device can continue to collect personalized data generated by the application after logging into the system account, update the personalized data associated with the system account, and achieve more accurate content recommendations for the application.

[0066] In combination with the second aspect, in one implementation, the first device sends the personalized data of the first application and the second application to the manufacturer server, specifically including: the first device extracts features from the personalized data of the first application and the second application, and converts the personalized data into a first feature vector; the first device sends the first feature vector to the manufacturer server.

[0067] That is to say, the personalized data sent by the electronic device can be formatted data, which reduces the amount of computation on the manufacturer's server and also reduces the amount of data sent by the electronic device.

[0068] In combination with the second aspect, in one implementation, the manufacturer server sends the personalized data associated with the first account to the application server of the third application, specifically including: the manufacturer server sends the second feature vector to the application server of the third application, the second feature vector is used to indicate the personalized data associated with the first account, and the vector dimension of the second feature vector matches the vector dimension of the data used by the application server of the third application to determine the first content.

[0069] That is, the data sent by the manufacturer server to the application server can be personalized data after the data format is adapted, which can reduce the computation load of the application server.

[0070] In a third aspect, an embodiment of the present application provides an electronic device comprising a memory, one or more processors, and one or more programs; when the one or more processors execute the one or more programs, the electronic device implements the method described in the second aspect or any one of the implementation methods of the second aspect.

[0071] In a fourth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions, which, when executed on an electronic device, enables a communication device to execute a method as described in the second aspect or any one of the implementations of the second aspect.

[0072] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method described in the second aspect or any one of the implementations of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] FIG1 is a schematic diagram of a communication system 1000 provided in an embodiment of the present application;

[0074] Figures 2A-2E, 3A-3C, and 4A-4D are some user interfaces provided in embodiments of the present application;

[0075] FIG5 is a schematic diagram of the hardware structure of the electronic device 100 provided in an embodiment of the present application;

[0076] FIG6 is a software structure block diagram of the electronic device 100 provided in an embodiment of the present application;

[0077] FIG7 is a hardware structure diagram of an electronic device 500 provided in an embodiment of the present application;

[0078] FIG8 is a software structure diagram of the manufacturer server 300 provided in an embodiment of the present application;

[0079] FIG9 is a software structure diagram of the application server 400 provided in an embodiment of the present application;

[0080] FIG10 is a flow chart of an account management method provided in an embodiment of the present application;

[0081] FIG11 is a diagram illustrating the module interaction for generating an identity code for a system account according to an embodiment of the present application;

[0082] FIG12 is a diagram showing a principle for generating a personalized feature vector according to an embodiment of the present application;

[0083] FIG13 is a schematic diagram showing the principle of generating an identity code of a system account based on a personalized feature vector according to an embodiment of the present application;

[0084] FIG14 is a flow chart of the digital identity sharing process provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] The following is a clear and detailed description of the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship between related objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0086] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0087] The term "user interface (UI)" in the following embodiments of this application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that the user can recognize. The commonly used form of user interface is graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

[0088] An embodiment of the present application provides an account management method, which involves a first device and a manufacturer server. The first device can collect personalized data of one or more applications, and the personalized data is used to reflect the user's preferences when browsing applications. The personalized data is associated with a first account logged in on the first device. When the first device starts the application, the account can be logged in on the application, so that the application can display content that meets the user's preferences from the content provided by the application based on the personalized data associated with the account.

[0089] The account may be a system account logged in on the first device. A system account is an account used to log in and manage electronic devices and related services. This account is an identity authentication tool provided by the device manufacturer. Users can use this account to log in to their device and manage cloud services, backup and recovery, and other functions.

[0090] If the first device collects personalized data from multiple applications, such as a first application and a second application, the first application and the second application may belong to different developers. In this way, the first device can collect personalized data from applications developed by different developers, breaking down information barriers between applications, enabling information sharing between applications, and effectively improving the accuracy of application content recommendations.

[0091] It can be seen that this account management method uses the system account as the user's personalized data storage and flow intermediary, binds the personalized data generated by the user when using the application to the system account, and enables each application that logs in to the system account to share the personalized data. Even if the user has never used the application, the application can accurately push content that the user is interested in based on the personalized data collected under the system account, thereby improving the user's usage experience.

[0092] In some embodiments, personalized data between system accounts can be shared between different devices. For example, the method also involves a second device, which can share personalized data associated with its own system account with the first device. This allows the first device to log in to the system account on an application, and the application can display content that is of interest to the user of the first device and the user of the second device, filtered from the content provided by the application based on the personalized data associated with the system accounts of the first and second devices.

[0093] It can be seen that the sharing of personalized data between accounts can enable users to present their own interests and hobbies in the content browsed by other users, facilitate information sharing among family and friends, and enrich the content recommended by recommendation applications.

[0094] FIG1 is a schematic diagram of a communication system 1000 provided in an embodiment of the present application.

[0095] The communication system 1000 may include: one or more terminal devices, one or more application servers, and a vendor server.

[0096] A terminal device is a device used by a user. The user can log in to a system account on the terminal device and use various applications, such as viewing content pushed by recommended applications. For example, the terminal device may be a mobile phone, tablet, computer, or other type of device. In embodiments of the present application, the terminal device can collect personalized data for one or more applications, send it to the manufacturer's server, and share the personalized data with system accounts logged in on other devices.

[0097] An application server is a server specifically used to host and process applications. It is mainly responsible for processing the business logic and dynamic content of the application, and providing the required information and functions to the terminal device. Among them, one application installed in the terminal device can correspond to one application server. In an embodiment of the present application, after the application logs into the system account, the application server can analyze the user's interests and hobbies based on the personalized data associated with the system account, and then push content that matches the user's interests and hobbies to the terminal device for display. Moreover, after the system account obtains the personalized data shared by other accounts, the application server can analyze the interests and hobbies of multiple users based on the personalized data associated with the system account and other accounts, and then push content that matches the interests and hobbies of multiple users to the terminal device for display.

[0098] The manufacturer's server can provide cloud computing services for terminal devices, backing up terminal device data and managing and maintaining system accounts registered on the terminal devices. In embodiments of the present application, the manufacturer's server can also obtain personalized data collected from one or more applications on the terminal device, bind the personalized data to the system account, and store it in the cloud. This allows the terminal device to display content recommended based on the personalized data after logging into the system account on the application.

[0099] Exemplarily, as shown in FIG1 , a communication system 1000 may include: an electronic device 100 , an electronic device 200 , a manufacturer server 300 , and an application server 400 .

[0100] Among them, electronic device 100 and electronic device 200 are terminal devices. Taking electronic device 100 as an example, electronic device 100 can collect personalized data of one or more applications and send it to the manufacturer server 300. The manufacturer server 300 can bind the personalized data with the system account of electronic device 100 to realize the association between personalized data and system account. Afterwards, when electronic device 100 logs in to the system account on the application, electronic device 100 can notify the manufacturer server 300 to send the personalized data associated with the system account to the application server 400. The application server 400 can analyze the user's interests and hobbies based on the personalized data, and then return content that meets the user's interests and hobbies, so that the electronic device 100 can display the content pushed by the application based on the personalized data associated with the system account.

[0101] Furthermore, the electronic device 100 can also share the personalized data associated with the system account with accounts logged in on other devices, or the account logged in on the electronic device 100 can obtain the personalized data shared by other accounts. Taking the other device as the electronic device 200, the electronic device 100 can obtain the instruction information indicating that the electronic device 200 shares the personalized data and send the instruction information to the manufacturer server 300. After that, the manufacturer server 300 can bind the personalized data associated with the system account of the electronic device 200 to the system account of the electronic device 100, so that the system account of the electronic device 100 is associated with the personalized data collected from the system accounts on the electronic devices 100 and 200. In this way, when the electronic device 100 logs in to the system account on the application, it can notify the manufacturer server 300 to send the personalized data associated with the system account to the application server 400. The application server 400 can analyze the user's interests and hobbies based on the personalized data and then return content that matches the interests and hobbies, so that the electronic device 100 can display the content pushed by the application based on the personalized data associated with multiple system accounts.

[0102] It is understandable that the interaction process between the electronic device 200 and the manufacturer server 300 and the application server 400 is similar to the above description of the electronic device 100, and will not be repeated here. In addition, the communication system 1000 may also include more or fewer devices, and the embodiments of the present application do not limit this.

[0103] In an embodiment of the present application, the electronic device 100 may also be referred to as a first device, the electronic device 200 may also be referred to as a second device, and different applications may correspond to different application servers 400, such as an application server 400 for a third application, an application server 400 for a fourth application, and so on.

[0104] In addition, it should be noted that the servers mentioned in the embodiments of the present application, such as application servers, manufacturer servers, etc., can be a single server or a server cluster consisting of multiple servers. For example, the manufacturer server 300 can be a server cluster in which multiple servers are deployed through a distributed architecture. The cluster can include one or more cloud computing servers, content delivery network (CDN) servers, network time protocol (NTP), domain name resolution system (DNS) servers, etc. The servers can coordinate with each other to jointly complete functions such as computing, data storage, and communication.

[0105] The following introduces some user interfaces involved in the embodiments of the present application in conjunction with Figures 2A-2E, Figures 3A-3C, and Figures 4A-4D.

[0106] 2A-2E show the relevant user interfaces for setting a system account through a setting application of the electronic device 100 provided in an embodiment of the present application.

[0107] Figure 2A illustrates an exemplary user interface 10 for a settings application according to an embodiment of the present application. For example, user interface 10 may be used to display options corresponding to one or more settings functions, such as system account, airplane mode, Wi-Fi, Bluetooth, personal hotspot, mobile network, permissions and privacy, display and brightness, and so on.

[0108] It is understandable that the electronic device 100 can trigger the launch of the settings application by detecting a user operation on the application icon of the settings application, such as a click operation, and display the user interface 10 as shown in Figure 2A. Alternatively, the electronic device 100 can also trigger the launch of the settings application by detecting a user's voice command. This embodiment of the present application is not limited to this.

[0109] As shown in FIG2A , the user interface 10 may include an option 101. The option 101 is an option corresponding to a system account. For example, the option 101 may display a nickname of the system account of the electronic device 100, such as “User XXX”.

[0110] It is understood that the system account on the electronic device 100 may be an account registered on the electronic device 100 when the user first uses the electronic device 100. During the registration and completion of the system account, the user may enter registration information for the system account, including a nickname, profile picture, password, gender, email address, etc. Subsequently, the electronic device 100 may collect personalized data generated by various applications during operation and send the data to the manufacturer's server corresponding to the electronic device 100, such as the manufacturer's server 300 mentioned above.

[0111] In some embodiments, when a user registers or logs in to a system account on the electronic device 100, the electronic device 100 may display a prompt message requesting the user to grant permission to obtain personalized data of the application. Only after the electronic device 100 detects that the user agrees to the authorization operation can the personalized data of the application be collected during the subsequent user's use of the application to implement the content recommendation function of the application, that is, push content that meets the user's interests and hobbies.

[0112] When the electronic device 100 detects a user operation on option 101, such as a click operation, in response to the operation, the electronic device 100 can display a user interface 20 as shown in Figure 2B. The user interface 20 can be used to display one or more functions in the system account. For example, the function may include: personal information, account security, digital identity, cloud services, device search, family sharing, etc.

[0113] For example, as shown in FIG2B , user interface 20 may include option 201. Option 201 corresponds to the digital identity of the system account. This digital identity indicates the personalized data associated with the system account. After an application logs in to the system account, it can use the digital identity of the system account and the personalized data associated with the system account to push content that matches the user's interests.

[0114] When the electronic device 100 detects a user operation on the option 201, such as a click operation, in response to the operation, the electronic device 100 may display a user interface 30 as shown in FIG2C . The user interface 30 may be used to display one or more functions included in the digital identity.

[0115] As shown in FIG2C , the user interface 30 may include: a QR code 301 , a reset option 302 , an application management option 303 , and an identity sharing option 304 .

[0116] QR code 301 is a QR code corresponding to the digital identity of the system account on the electronic device 100. The QR code 301 stores the account information of the system account and the personalized data collected under the system account. The account information may include the account ID, nickname, profile picture, password, gender, email address, etc. In a specific implementation, the manufacturer server 300 can obtain the account information of the system account of the electronic device 100 and the personalized data collected under the system account, then generate the QR code 301 based on the system account, and then send the QR code 301 to the electronic device 100.

[0117] The reset option 302 can be used to reset the QR code 301, triggering the manufacturer server to regenerate the QR code. In a specific implementation, after receiving the instruction from the electronic device 100 to reset the QR code, the manufacturer server 300 can clear the personalized data associated with the system account logged in on the electronic device 100, recollect the personalized data collected from the electronic device 100, and use the recollected personalized data to generate the QR code.

[0118] The application management option 303 may be used to manage applications in the electronic device 100 that use the system account.

[0119] The identity sharing option 304 may be used to manage users who share the digital identity of a system account on the electronic device 100 .

[0120] Exemplarily, when the electronic device 100 detects a user operation on the application management option 303 shown in Figure 2C, such as a click operation, in response to the operation, the electronic device 100 can display the user interface 40 shown in Figure 2D, which can be used to display the login status of the system account in one or more applications.

[0121] As shown in Figure 2D, user interface 40 may include an application list 401. Application list 401 may include three items: "APP," "Access Time," and "Access Status." "APP" represents an application installed on electronic device 100. "Access Time" indicates the time during which the application is allowed to use the digital identity. "Access Status" indicates the state of the application's access to the digital identity. "Access Status" can include two states: "Connected" and "Not Connected." "Connected" indicates that the application is currently granted permission to use the digital identity and can use the personalized data associated with the system account. "Not Connected" indicates that the application is currently not granted permission to use the digital identity and cannot use the personalized data associated with the system account. For example, "Connected" may be represented by a black dot as shown in icon 401A, and "Not Connected" may be represented by a white dot as shown in icon 401B. Optionally, application list 401 may also include "More" options 401C. This "More" option 401C can be used to add new applications to application list 401, making it easier for users to manage the application's permission to use personalized data.

[0122] In some embodiments, the electronic device 100 may also detect modification operations on the "access status" of different applications, allowing or denying the applications access to the digital identity. For example, in FIG2D , if the electronic device 100 detects a user operation on icon 401A, the electronic device 100 may switch icon 401A from a black dot to a white dot, denying application A access to the personalized data associated with the system account. If the electronic device 100 detects a user operation on icon 401B, the electronic device 100 may switch icon 401B from a white dot to a black dot, allowing application B to access the personalized data associated with the system account.

[0123] For example, when the electronic device 100 detects a user operation on the identity sharing option 304 shown in FIG2C , such as a click operation, in response to the operation, the electronic device 100 may display a user interface 50 as shown in FIG2E , which may be used to display the sharing of the digital identity on the electronic device 100 by other users.

[0124] As shown in Figure 2E, user interface 50 may include a QR code 501 and a user list 502. QR code 501 corresponds to the digital identity of the system account of electronic device 100. Electronic device 100 can share QR code 501 with other devices, allowing other devices to scan the QR code and obtain information indicating that electronic device 100 is sharing personalized data, thereby sharing the digital identity of the system account. User list 502 may include three items: "User," "Access Time," and "Access Status." "User" represents the nickname of the system account on another device sharing the digital identity with electronic device 100. "Access Time" represents the time when the other system account and electronic device 100 share their digital identity. "Access Status" represents the current status of the digital identity sharing between the other system account and the system account on electronic device 100. "Access Status" may include two states: "Shared Status" and "Not Shared Status." "Shared Status" indicates that the other system account currently has the digital identity shared with the system account on electronic device 100. "Not Shared Status" indicates that the other system account currently has not yet obtained the digital identity shared with the system account on electronic device 100. For example, the "shared state" may be represented by a black dot as shown in icon 502A, and the "unshared state" may be represented by a white dot as shown in icon 502B. Optionally, user list 502 may also include: More options 502C. This More options 502C can be used to add system accounts that share digital identities with the system account on electronic device 100 to user list 502, making it easier for users of electronic device 100 to manage the permissions of other system accounts to share the digital identities of the system accounts on electronic device 100.

[0125] In some embodiments, the electronic device 100 can also detect modification operations on the "access status" of different system accounts, share the digital identity of the system account logged in on the electronic device 100 with other system accounts, or cancel sharing with other system accounts. For example, in Figure 2E, if the electronic device 100 detects a user operation on icon 502A, the electronic device 100 can switch icon 502A from a black dot to a white dot, cancel or refuse to share the digital identity of the system account logged in on the electronic device 100 with "User_1". If the electronic device 100 detects a user operation on icon 502B, the electronic device 100 can switch icon 502B from a white dot to a black dot, and share the digital identity of the system account logged in on the electronic device 100 with "User_2". As can be seen from Figures 2A to 2E, the electronic device 100 can control system accounts by setting applications, and can also manage applications in the electronic device 100 that use the system account, as well as other accounts that share the digital identity of the system account with the electronic device 100, by setting applications.

[0126] Figures 3A-3C illustrate user interfaces related to logging into a system account on an electronic device 100 in an application, as provided in an embodiment of the present application. Figures 3A-3C use a music application as an example to illustrate user interfaces related to logging into a system account on the electronic device 100 in the music application. It should be understood that in other embodiments of the present application, the electronic device 100 may also log into a system account in other applications, and this embodiment of the present application does not limit this.

[0127] FIG3A is an exemplary user interface 60 corresponding to the desktop on the electronic device 100 provided in an embodiment of the present application.

[0128] As shown in FIG3A , the user interface 60 may include: a status bar 601 , a calendar and weather indicator 602 , and one or more application icons 603 .

[0129] The status bar 601 may include one or more signal indicators for mobile communication signals, one or more signal strength indicators for wireless high-fidelity (Wi-Fi) signals, a battery status indicator, and a time indicator. The calendar and weather indicator 602 may be used to indicate the current time and weather type. The one or more application icons 603 may include icons for one or more applications. For example, as shown in Figure 3A, the one or more application icons 603 may include application icon 603A, which is an application icon for a music application.

[0130] For example, the electronic device 100 may detect a user operation on the application icon 603A, such as a click operation, and open the music application in response to the operation.

[0131] It is understandable that the electronic device 100 can also open the music application in other ways. For example, the electronic device 100 can detect the user's voice input "open the music application" and trigger the opening of the music application. The embodiment of the present application does not limit the method of opening the music application.

[0132] If the operation of starting the music application shown in Figure 3A is the first operation of starting the application after installing or updating the music application, the electronic device 100 can display the user interface 70 shown in Figure 3B when starting the music. The user interface 70 can be used to display the account login page of the music application.

[0133] It is understandable that the electronic device 100 can also trigger the display of the user interface 70 shown in Figure 3B after detecting the user opening the account login page during the process of displaying the user interface of the music application. The embodiment of the present application does not limit the interactive method of the electronic device 100 triggering the display of the account login page of the application.

[0134] As shown in FIG3B , the user interface 70 may include an account login option 701 and an other login option 702. The account login option 701 may be used to trigger logging into the music app using a system account on the electronic device 100, while the other login option 702 may be used to trigger logging into the music app using other methods, such as logging into the music app using a WeChat account or a mobile phone number.

[0135] When the electronic device 100 detects a user operation on the account login option 701, such as a click operation, in response to the operation, the electronic device 100 can use the system account to complete the account login on the music application and display the user interface 80 as shown in Figure 3C, which is the home page of the music application.

[0136] In some embodiments, the user interface 70 may further include a scan option 703. The scan option 703 may be used to scan an identification code to log in to an account on a music application. For example, the electronic device 100 may detect a user operation on the scan option 703, open a camera, and scan a QR code corresponding to the digital identity of a system account on the electronic device 100, such as the QR code 301 shown in FIG. 2C , to log in to the system account on the electronic device 100 on the music application.

[0137] As shown in FIG3C , the user interface 80 may include a recommended content display area 801. The recommended content display area 801 may include a playlist pushed by the music application based on the user's interests and hobbies. In a specific implementation, after the electronic device 100 detects an operation of logging into a system account on the music application, the electronic device 100 may notify the manufacturer server 300 to send the personalized data associated with the system account to the application server of the music application, such as the application server 400. The application server 400 analyzes the user's interests and hobbies based on the personalized data, and then filters out songs that match the user's interests and hobbies and sends them to the electronic device 100 so that the electronic device 100 displays these songs in the recommended content display area 801. For example, as shown in FIG3C , the recommended content display area 801 may display song names such as "Song 1", "Song 2", "Song 3", etc. The electronic device 100 can detect a click operation on any of the songs and play the song.

[0138] As can be seen from Figures 3A to 3C, the electronic device 100 can log in to the system account on the application, so that the application can push content that suits the user's interests and hobbies based on the personalized data collected in the system account, so that the user can experience a more humane and intelligent content recommendation function while using the application and browse content that better suits the user's preferences.

[0139] 4A-4D are related user interfaces involved after the electronic device 100 according to an embodiment of the present application obtains the digital identity of a system account shared by other devices.

[0140] Figure 4A illustrates a user interface 90 for scanning a barcode on an electronic device 100 according to an embodiment of the present application. The user interface 90 may be displayed after the electronic device 100 detects that a user has initiated a barcode scanning function. For example, the barcode scanning function may be included in an application such as a settings application or a browser application. The embodiment of the present application does not limit the interactive method by which the electronic device 100 triggers the display of the user interface 90 shown in Figure 4A.

[0141] As shown in FIG4A , the user interface 90 may include a code scanning area 901 and a gallery icon 902. The code scanning area 901 may be used to display images captured in real time by the camera. When an identification code such as a QR code or a one-dimensional code is located in the code scanning area 901 , the electronic device 100 may recognize the information in the identification code and trigger a corresponding response.

[0142] For example, the user can move the QR code corresponding to the digital identity of the system account on other devices (taking electronic device 200 as an example below) into the camera shooting range of electronic device 100, so that the QR code is displayed in the scanning area 901, and electronic device 100 obtains the digital identity shared by the system account of electronic device 200.

[0143] In a specific implementation, since the QR code corresponding to the digital identity stores the account information of the system account and the personalized data collected under the system account, after the electronic device 100 scans the QR code corresponding to the digital identity of the system account of the electronic device 200, the electronic device 100 can obtain the account information of the system account of the electronic device 200 and the personalized data collected under the system account. Afterwards, the electronic device 100 can send the digital identity of the electronic device 100 and the indication information of the digital identity of the electronic device 200 to the manufacturer server. The manufacturer server can combine the two digital identities to regenerate a shared identity under the system account of the electronic device 100. The shared identity is used to indicate the personalized data associated with the system account of the electronic device 100 and the personalized data associated with the system account of the electronic device 200. The manufacturer server then sends the shared identity to the electronic device 100. In this way, the electronic device 100 can log in to the account on the application through the shared identity, and use the personalized data associated with the system accounts on the electronic device 100 and the electronic device 200 to implement the content recommendation function of the application.

[0144] It is understandable that after the electronic device 100 obtains the shared identity, the original digital identity on the electronic device 100 can be deleted, that is, the shared identity can be used to replace the original digital identity on the electronic device 100, so that when the electronic device 100 chooses to log in to the system account on the application, it can only select the shared identity to enable the application to use the personalized data associated with the two system accounts to push content. Alternatively, after the electronic device 100 obtains the shared identity, the digital identity originally generated on the electronic device 100 can still be retained. In this way, when the electronic device 100 needs to log in to the account on the application, the user can choose to use the original digital identity under the system account or the shared identity to implement the content push function of the application.

[0145] Since the gallery icon 902 can be used to trigger the opening of the gallery application and select a QR code stored in the gallery application for scanning, in some embodiments, the electronic device 100 can also obtain the digital identity shared by other devices by scanning the QR code corresponding to the digital identity of other devices stored in the gallery. In this case, the electronic device 200 can send the QR code of the digital identity to the electronic device 100 via short-range communication methods such as Bluetooth, WiFi, or sharing methods such as instant messaging applications.

[0146] FIG4B is a user interface 30 corresponding to the digital identity of the system account in the setting application provided in an embodiment of the present application. For a specific description of the user interface 30 , please refer to the relevant contents of the aforementioned FIG2B to FIG2C , which will not be repeated here.

[0147] In addition, unlike Figure 2C, since the electronic device 100 now obtains a shared identity account based on the digital identity shared by the electronic device 200, the information about the original digital identity in the electronic device 100 can be replaced with the information of the shared identity, for example, the QR code of the originally displayed digital identity is replaced with the QR code of the shared identity. The QR code can be used to indicate the personalized data associated with the system account in the electronic device 100, as well as the personalized data associated with the system account in the electronic device 200.

[0148] For example, as shown in Figure 4B, the QR code 301 originally displayed on the user interface 30 as shown in Figure 2C can be replaced with a QR code 305 corresponding to the shared identity. The electronic device 100 can use the QR code 305 to log in to the system account of the electronic device 100 on the application, and use the personalized data associated with the system account of the electronic device 100 and the personalized data associated with the system account of the electronic device 200 to implement the content recommendation function of the application.

[0149] In addition, the user interface 30 may further include a close option 306, which may be used to switch the shared identity under the system account back to the original digital identity, thereby stopping the system account of the electronic device 100 from continuing to use the personalized data shared by the system account of the electronic device 200. For example, the electronic device 100 may detect a user operation on the close option 306, such as a click operation. In response to the operation, the electronic device 100 may update the QR code 305 to the QR code 301 shown in FIG. 2C , thereby ending the sharing of the digital identity of the electronic device 200. In this way, after the electronic device 100 logs in to the application using the system account, content recommendations may be implemented using only the personalized data associated with the system account of the electronic device 100.

[0150] In some embodiments, the user interface 30 may also display a QR code for the original digital identity, such as QR code 301 shown in FIG2C , and a QR code for the shared identity, such as QR code 305 shown in FIG4B . Based on user operation, the electronic device 100 may choose to use the original digital identity or the shared identity when logging into the system account on the application.

[0151] It can be understood that Figures 4C and 4D again take the music application as an example to show the relevant user interfaces involved after the electronic device 100 obtains the digital identity shared by other devices and logs in to the system account on the music application. In other embodiments of the present application, the electronic device 100 can also log in to the system account on other applications, such as video playback applications and shopping applications, and the embodiments of the present application do not limit this.

[0152] As shown in Figure 4C, the user interface 70 can be used to display the account login page of the music application. For a specific description of the user interface 70, please refer to the relevant content of Figures 3A-3B above. In addition, as shown in Figure 4C, since the electronic device 100 has obtained the digital identity shared by the electronic device 200, a sharing prompt message 704 is also displayed in the user interface 70. The sharing prompt message 704 is used to prompt the user that the system account named "User_1" has shared the digital identity with the system account on the electronic device 100. If the system account of the electronic device 100 is used to log in to the application, the application can filter and push content based on the personalized data associated with the system accounts on the electronic devices 100 and 200.

[0153] Optionally, the electronic device 100 can detect the user's selection operation on the sharing prompt information 704 to select whether to enable or disable identity sharing of the system account "User_1". For example, if the sharing prompt information 704 is in a selected state, for example, the dot in the sharing prompt information 704 is a black dot, the electronic device 100 can use the shared identity of the system account to log in to the application; if the sharing prompt information 704 is in an unselected state, for example, the dot in the sharing prompt information 704 is a white dot, the electronic device 100 can use the original digital identity of the system account to log in to the application.

[0154] When the electronic device 100 detects a user operation on the account login option 701 shown in Figure 4C, such as a click operation, in response to the operation, the electronic device 100 can log in to the system account on the electronic device 100 on the music application and display the user interface 80 shown in Figure 4D, which is the home page of the music application.

[0155] As shown in FIG4D , the user interface 80 may include: a recommended content display area 801. The recommended content display area 801 may include a playlist pushed by a music application based on the user's interests and hobbies. In a specific implementation, the electronic device 100 may send information indicating the shared identity of the system account on the electronic device 100 to the manufacturer's server. The manufacturer's server may send personalized data associated with the system account on the electronic device 100 and personalized data associated with the system account on the electronic device 200 to the application server. The application server analyzes the user's interests and hobbies based on these personalized data, and then filters out songs that meet the user's interests and hobbies and sends them to the electronic device 100, so that the electronic device 100 displays these songs in the recommended content display area 801. For example, as shown in FIG4D , the recommended content display area 801 may display song names such as "Song 3", "Song 4", "Song 5", etc. The electronic device 100 may detect a click operation on any of the songs and play the song.

[0156] As can be seen from Figures 4A-4D, the electronic device 100 can obtain the digital identity shared by other devices, and obtain a shared identity based on the local digital identity and the shared digital identity. In this way, when the electronic device 100 logs in to the system account in the application, the application can use the personalized data corresponding to the shared identity to push content that meets the interests and hobbies of multiple users.

[0157] It is understandable that the above Figures 4A to 4D illustrate that after the electronic device 100 obtains the digital identity shared by the electronic device 200, the electronic device 100 can use the personalized data associated with the system account of the electronic device 100 and the electronic device 200 to implement the process of content recommendation for the application. In other embodiments of the present application, after the electronic device 100 obtains the digital identity shared by the electronic device 200, the shared identity generated by the electronic device 100 can also be used only to indicate the personalized data associated with the system account of the electronic device 200. In this way, after the electronic device 100 logs in to the system account of the electronic device 100 on the application, the application can use the personalized data associated with the system account of the electronic device 200 to push content that the user using the electronic device 200 is interested in.

[0158] FIG5 shows a schematic diagram of the hardware structure of the electronic device 100 .

[0159] The electronic device 100 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, and / or a smart city device. The embodiments of the present application do not impose any particular restrictions on the specific type of the electronic device.

[0160] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0161] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0162] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0163] In the embodiment of the present application, the processor 110 may be used to collect personalized data generated by a user when using one or more applications. Furthermore, the processor 110 may be used to clean and organize the personalized data, extract features from the personalized data, and convert them into vectors to facilitate subsequent retrieval and processing of the personalized data by the manufacturer server 300.

[0164] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0165] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0166] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0167] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0168] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0169] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0170] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0171] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0172] In an embodiment of the present application, the electronic device 100 can send personalized data to the manufacturer server 300 through the mobile communication module 150 and the wireless communication module 160, receive the digital identity of the system account and the QR code of the shared identity generated by the manufacturer server 300, send the login information of the system account to the application server 400, receive the application push content returned by the application server 400, and so on.

[0173] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0174] The display screen 194 is used to display images, videos, etc. In some embodiments, the electronic device may include 1 or N display screens 194 , where N is a positive integer greater than 1.

[0175] In an embodiment of the present application, the display screen 194 may be used to display the user interface of the application, and during the running of the application, display application recommended content, such as text, pictures, videos, audio, etc., in the user interface of the application.

[0176] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0177] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0178] In the embodiment of the present application, the internal memory 121 may be used to store personalized data generated by an application and account information of a system account logged in on the electronic device 100 .

[0179] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0180] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0181] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0182] The electronic device can be a portable terminal device equipped with Harmony, iOS, Android, Microsoft or other operating systems, such as a mobile phone, tablet computer, wearable device, etc., and can also be a non-portable terminal device such as a laptop computer with a touch-sensitive surface or touch panel, a desktop computer with a touch-sensitive surface or touch panel. The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present invention takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100.

[0183] FIG6 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present invention.

[0184] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0185] The application layer can include a series of application packages.

[0186] As shown in FIG6 , the application package may include recommended applications, setting applications, camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, short message and other applications.

[0187] Recommended apps can analyze users' interests and hobbies based on their personalized data and selectively display content that matches their interests. These recommended apps can include e-commerce apps, video apps, music apps, and more.

[0188] For example, video apps can collect user browsing history as they browse videos. Based on the frequency of viewing different types of videos, they can analyze the user's preferred video types and increase the frequency of pushing videos of that type. For example, if a user frequently views food videos, the video app can increase the frequency of pushing food videos.

[0189] In addition, in an embodiment of the present application, the electronic device 100 can log in to a system account on a recommendation application, and the account collects personalized data from one or more applications. Then, when the electronic device 100 runs the recommendation application, the recommendation application can analyze the user's interests and hobbies based on the personalized data of the one or more applications, and selectively display content that matches the user's interests and hobbies to the user.

[0190] For example, if the electronic device 100 has a system account logged into the e-commerce application, the e-commerce application can analyze the user's interests and hobbies based on the personalized data collected from various applications under the system account. For example, based on the user's high viewing frequency of food videos in a video application, the e-commerce application can analyze that the user has a greater interest in food products. Therefore, the e-commerce application can increase the frequency of pushing food products.

[0191] The settings application can be used to provide one or more settings functions, including: Wi-Fi function, Bluetooth function, permission management function, application management function, etc. Users can adjust the configuration of the electronic device 100 through these one or more settings functions to achieve better control and management of the electronic device.

[0192] In addition, in an embodiment of the present application, the electronic device 100 can manage the system account by setting up an application, manage the application's permission to use the system account, and manage the permission of other users to share the digital identity under the system account of the electronic device 100.

[0193] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0194] As shown in Figure 6, the application framework layer may include a data collection module, a data analysis module, a feature encoding module, a data reporting module, a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. Among them:

[0195] The data collection module can be used to collect personalized data of one or more applications, which may include the user's browsing history, personal information, etc.

[0196] The data parsing module can be used to clean and structure personalized data, converting it into structured data. For details on data structuring, please refer to the following content and will not be expanded here.

[0197] The feature encoding module can be used to perform feature vectorization calculations on structured data and convert it into vectorized data.

[0198] The data reporting module can be used to send vectorized personalized data to the server so that the server can store it in the cloud and bind the personalized data to the system account.

[0199] It is understood that the data parsing module and the feature encoding module are optional modules. After the electronic device 100 collects personalized data through the data collection module, it can also directly send this unprocessed personalized data to the server through the data reporting module. However, by comparison, the processing of personalized data by the data parsing module and the feature encoding module can reduce the amount of data sent by the electronic device 100 to the server. At the same time, the vectorized data is more convenient for the server to retrieve and process, reducing the workload of the server for data processing.

[0200] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0201] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0202] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0203] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0204] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0205] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0206] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0207] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0208] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0209] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

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

[0211] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0212] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0213] A 2D graphics engine is a drawing engine for 2D drawings.

[0214] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0215] The following describes the workflow of the software and hardware of the electronic device 100 in conjunction with capturing a photo scene.

[0216] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, touch operation timestamp, and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a touch single-click operation and the control corresponding to the single-click operation is the control of the camera application icon, the camera application calls the interface of the application framework layer to start the camera application, and then starts the camera driver by calling the kernel layer to capture a still image or video through the camera 193.

[0217] FIG7 is a hardware structure diagram of an electronic device 500 provided in an embodiment of the present application.

[0218] As shown in FIG7 , electronic device 500 may include: one or more processors 201, memory 202, communication interface 203, transmitter 205, receiver 206, coupler 207, and antenna 208. These components may be connected via bus 204 or other means, with FIG7 using bus connection as an example.

[0219] The communication interface 203 can be used for the electronic device 500 to communicate with other communication devices. Specifically, the communication interface 203 can be a 3G communication interface, a long-term evolution (LTE) (4G) communication interface, a 5G communication interface, a WLAN communication interface, a WAN communication interface, etc. Not limited to a wireless communication interface, the electronic device 500 can also be configured with a wired communication interface 203 to support wired communication. For example, the backhaul link between the electronic device 500 and other servers can be a wired communication connection.

[0220] In some embodiments of the present application, the transmitter 205 and the receiver 206 can be considered as a wireless modem. The transmitter 205 can be used to transmit and process the signal output by the processor 201. The receiver 206 can be used to receive signals. In the electronic device 500, the number of transmitters 205 and receivers 206 can be one or more. The antenna 208 can be used to convert electromagnetic energy in the transmission line into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in the transmission line. The coupler 207 can be used to split the mobile communication signal into multiple paths and distribute them to multiple receivers 206. It is understandable that the antenna 208 of the electronic device 500 can be implemented as a large-scale antenna array.

[0221] Memory 202 is coupled to processor 201 and is configured to store various software programs and / or multiple sets of instructions. Specifically, memory 202 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.

[0222] The memory 202 can store an operating system (hereinafter referred to as system), such as an embedded operating system such as uCOS, VxWorks, or RTLinux.

[0223] In the embodiment of the present application, the processor 201 may be configured to read and execute computer-readable instructions.

[0224] In the embodiment of the present application, when the electronic device 500 is the manufacturer server 300:

[0225] The receiver 206 may be configured to receive personalized data sent by the electronic device 100 and indication information of a system account shared by other devices sent by the electronic device 100 .

[0226] The processor 201 can be used to bind the system account of the electronic device 100 with the personalized data sent by the electronic device 100, so as to associate the system account with the personalized data collected under the system account, and generate an identification code corresponding to the digital identity of the system account. In addition, the processor 201 can also be used to bind the personalized data collected under other system accounts to the system account of the electronic device 100 after the system account of the electronic device 100 obtains a digital identity shared by other system accounts, so that the system account of the electronic device 100 is associated with the personalized data collected by multiple system accounts, and generate an identification code of the shared identity, which is used to indicate the personalized data collected by multiple system accounts.

[0227] The transmitter 205 can be used to return the digital identity of the system account of the electronic device 100 or the identification code of the shared identity, such as a QR code, to the electronic device 100, and send personalized data associated with the system account to the application server 400 so that the application server 400 can recommend content based on the personalized data.

[0228] The memory 202 may be used to store personalized data and account information of a system account.

[0229] In the embodiment of the present application, when the electronic device 500 is the application server 400:

[0230] The receiver 206 may be configured to receive login information of a system account or a shared account sent by the electronic device 100 , and receive personalized data sent by the manufacturer server 300 .

[0231] The processor 201 may be configured to analyze the user's interests and hobbies based on the personalized data, and filter out content that matches the user's interests and hobbies from the material candidate set.

[0232] The transmitter 205 may be configured to return the filtered content that matches the user's interests to the electronic device 100 .

[0233] It is understandable that in the embodiment of the present application, the electronic device 500 may also include more or fewer components, and the embodiment of the present application does not limit this.

[0234] FIG8 is a software structure diagram of the manufacturer server 300 provided in an embodiment of the present application.

[0235] As shown in FIG8 , the manufacturer server 300 may include but is not limited to the following software modules: a feature generation module 301 , a digital identity generation module 302 , a lifecycle management module 303 , and an identity verification module 304 .

[0236] The feature generation module 301 may be used to bind the account information of the system account and the personalized data to generate a preference feature vector that can uniquely identify the identity.

[0237] The digital identity generation module 302 may be configured to generate a digital identity of a system account or an identification code of a shared identity according to the preference feature vector.

[0238] The lifecycle management module 303 can be used to manage operations such as authorization, revocation, and data deletion of system accounts.

[0239] The identity verification module 304 may be used to verify the system account when the terminal device logs into the system account.

[0240] It is understandable that the manufacturer server 300 may also include more or fewer software modules, and the embodiments of the present application do not limit this.

[0241] FIG9 is a software structure diagram of the application server 400 provided in an embodiment of the present application.

[0242] As shown in FIG9 , the application server 400 may include but is not limited to the following software modules: a digital identity access protocol 401 and a recommendation system 402 .

[0243] The digital identity access protocol 401 refers to a standard protocol for connecting a system account to the recommendation system 402. The standard protocol defines the relevant standards for the application server 400 to use personalized data for content recommendation, including data format, recommendation system parameters, encryption algorithm, etc.

[0244] In a specific implementation, when electronic device 100 logs into a system account in an application, the application can use digital identity access protocol 401 to specify the format of the personalized data to be sent to application server 400, as well as relevant standards such as the data encryption algorithm. This allows manufacturer server 300 to convert the personalized data into a vector in the specified format before sending it, and then encrypt the vector-formatted personalized data using the specified data encryption algorithm before sending it to application server 400. Therefore, using digital identity access protocol 401 to receive personalized data can achieve low-cost integration between applications and system accounts, minimize the computational workload of application server 400, and reduce the difficulty of adapting application server 400 in this solution.

[0245] The recommendation system 402 includes a recommendation model, which can be used to filter out content that meets the user's interests from a large number of material candidate sets based on personalized data.

[0246] It is understandable that the application server 400 may also include more or fewer software modules, and this embodiment of the present application does not limit this.

[0247] FIG10 is a flow chart of an account management method provided in an embodiment of the present application.

[0248] As shown in FIG10 , the account management method provided in the embodiment of the present application may mainly include the following steps:

[0249] S101. The electronic device 100 sends personalized data of the first application and the second application to the manufacturer server 300. The first application and the second application belong to different developers. The personalized data is used to reflect the user's preferences when browsing application content. The personalized data is associated with the first account logged in on the electronic device 100.

[0250] The first account may be a system account logged into the electronic device 100. A system account is an account used to log in and manage the electronic device and related services. This account is an identity authentication tool provided by the device manufacturer. Users can use this account to log in to their device and manage cloud services, backup and recovery, and other functions.

[0251] A system account uniquely identifies a user. The first account can be considered a "tag" for the user's use of the electronic device 100. While the user is using the electronic device 100, the electronic device 100 can upload generated data, including photos, contacts, videos, files, and so on, to the manufacturer's server 300, and bind this data to the first account. This way, even if the user changes devices, they can still access historical data generated by using the electronic device 100 by logging into the first account on other devices.

[0252] For example, the electronic device 100 may log in to the system account when used for the first time. Specifically, the electronic device 100 may display a login page for the system account, and complete the login of the first account after the electronic device 100 detects that the user has input login information for the first account.

[0253] It is understandable that the electronic device 100 can also log in to the system account when registering the system account. The electronic device 100 can register the first account through the manufacturer server 300.

[0254] During the operation of the electronic device 100, the electronic device 100 may collect personalized data generated during the operation of one or more applications. The personalized data may include browsing history, personal information input by the user during the use of the application, etc.

[0255] When the electronic device 100 collects personalized data from multiple applications, different applications may belong to different developers, and the electronic device 100 can collect personalized data from different applications through a unified interface. Taking a first application and a second application as an example, the first application and the second application may belong to different developers, and the electronic device 100 can collect personalized data from the first application and the second application through a unified interface.

[0256] In this way, the electronic device 100 can collect personalized data from applications developed by different developers, break the information barriers between applications, and realize the interconnection of information between applications, so that applications can more comprehensively and accurately grasp the user's interests and hobbies, and push content that is more in line with user preferences.

[0257] For example, the electronic device 100 may collect personalized data in the following situations:

[0258] 1) The electronic device 100 can periodically collect personalized data of the application

[0259] That is to say, the electronic device 100 can trigger the collection of personalized data collected by each application at intervals.

[0260] 2) The electronic device 100 can collect personalized data of the application when the application logs into the system account

[0261] In this way, after the application logs in to the system account, the application can use the personalized data recently collected by the electronic device 100 to push content, and push content that the user may be interested in in the near future based on the user's recent interests and hobbies.

[0262] 3) The electronic device 100 can collect personalized data of the application when detecting user operation

[0263] That is, the user can manually start the collection of personalized data of the application, and the electronic device 100 can start the collection of personalized data in response to the operation after detecting that the user triggers the operation of collecting personalized data.

[0264] In some embodiments, to improve the processing efficiency of personalized data by the manufacturer server 300, the electronic device 100 may adjust the format of the personalized data to a format suitable for processing by the manufacturer server 300 before sending the personalized data to the manufacturer server 300. In this way, after obtaining the formatted personalized data, the manufacturer server 300 can directly use the personalized data to determine the push content, thereby speeding up the display of recommended content on the electronic device 100 and reducing the computational workload of the manufacturer server 300.

[0265] For example, the electronic device 100 can use a high-dimensional space to represent the personalized data, that is, adjust the personalized data into a preference feature vector in a vector format. Detailed description of how the electronic device 100 adjusts the format of the personalized data can be found in the subsequent FIG. 11 , which will not be expanded here.

[0266] S102 . The electronic device 100 sends a first message to the manufacturer server 300 .

[0267] For example, after detecting a user operation of logging into a third application using a first account, the electronic device 100 may send a first message to the manufacturer server 300 , where the first message is used to request personalized data associated with the first account.

[0268] The third application may refer to a recommendation application installed in the electronic device 100 . The recommendation application may analyze the user's interests and hobbies based on the user's personalized data, and selectively display content that matches the user's interests and hobbies to the user based on the user's interests and hobbies.

[0269] The developer of the third application can be different from the developer of the first application and the second application. In this way, the personalized data of the application can be circulated between applications developed by different developers, solving the current problem of personalized data not being able to flow between applications from different manufacturers and realizing data sharing between applications.

[0270] For example, taking FIG. 3A to FIG. 3C as an example, the third application may be a music application, and the user operation of logging into the third application using the first account may be the user operation acting on the account login option 701 shown in FIG. 3B .

[0271] S103 . In response to the first message, the manufacturer server 300 sends the personalized data associated with the first account to the application server 400 of the third application.

[0272] In some embodiments, since the application server 400 utilizes a recommendation model, personalized data is input into the recommendation model to filter out content that meets the user's interests and hobbies from the material candidate set. The recommendation models used by different applications may be different, resulting in different formats of personalized data input into the recommendation model by the application servers corresponding to different applications.

[0273] To reduce the computational effort required by the application server to adjust the data format, the vendor server 300 can convert the personalized data into a format compatible with the recommended model before sending it to the application server 400. The digital identity access protocol specifies the network layer structure of the recommended model. The vendor server 300 can convert the personalized data into a vector dimension corresponding to the network layer structure in the recommended model according to the relevant parameters specified in the digital identity access protocol, and then send the converted personalized data to the application server 400.

[0274] In addition, if the data sent by the manufacturer server 300 includes not only personalized data but also account information, for example, if the data sent by the manufacturer server 300 is a personalized feature vector that is fused with a preference feature vector and an identity vector, where the preference feature vector is used to indicate personalized data and the identity vector is used to indicate account information, then the data sent by the manufacturer server 300 may include, in addition to the personalized feature vector after format adaptation, the vector fusion method used by the manufacturer server 300 to fuse the identity vector and the preference feature vector. In this way, after obtaining the personalized feature vector, the application server 400 can obtain the preference feature vector therein according to the vector fusion method, thereby using the personalized data indicated by the preference feature vector to implement content recommendation.

[0275] Furthermore, the digital identity access protocol may also stipulate a data encryption algorithm. The manufacturer server 300 may also encrypt the personalized data after the adapted format according to the encryption algorithm, and then send the encrypted data to the application server 400, thereby ensuring the security of the data.

[0276] It is understood that, in addition to directly sending the personalized data associated with the first account to the application server 400, the manufacturer server 300 may also forward the personalized data to the application server 400 through the electronic device 100. In other words, in response to the first message, the manufacturer server 300 may send the personalized data associated with the first account to the electronic device 100, and the electronic device 100 may then send the personalized data to the application server 400 of the third application.

[0277] S104 . The application server 400 of the third application selects the first content from the content provided by the third application based on the personalized data associated with the first account.

[0278] The application server 400 can analyze the user's interests and hobbies based on the personalized data associated with the first account, and filter content provided by the third application that matches the user's interests and hobbies. The content can include images, videos, audio, news, articles, and other information. For example, if the third application is a music application, the first content can be songs. For another example, if the third application is a video playback application, the first content can be videos.

[0279] In some embodiments, after the application server 400 completes the calculation of a recommendation model using personalized data, the application server 400 can return the success or failure status to the manufacturer server 300 through the terminal device, so that the manufacturer server 300 can determine whether the application server 400 has successfully filtered out recommended content based on the personalized data based on the status.

[0280] S105 . The application server 400 of the third application sends the first content to the electronic device 100 .

[0281] Accordingly, the electronic device 100 obtains the first content sent by the application server 400 .

[0282] S106. The electronic device 100 displays the first content of the third application, and the third application is logged in with the first account.

[0283] Exemplarily, the first content may refer to the content in the recommended content display area 801 in FIG. 3C .

[0284] In some embodiments, the electronic device 100 may also continuously collect personalized data generated by the third application during the operation of the third application, and send it to the manufacturer server 300, so that the manufacturer server 300 can update the personalized data associated with the first account, thereby achieving more accurate content recommendations for applications logged in to the first account.

[0285] It is understandable that the electronic device 100 may log in to the first account on the third application before step S102, or log in to the first account on the third application before step S106. In other words, the electronic device 100 may first log in to the system account on the application, and then send a request to the manufacturer server 300 to obtain the personalized data associated with the system account, so as to display the pushed content filtered based on the personalized data on the application. Alternatively, the electronic device 100 may first send a request to the manufacturer server 300 to obtain the personalized data associated with the system account, and then log in to the system account on the application, and then display the pushed content filtered based on the personalized data on the application.

[0286] It can be seen from steps S101-S106 that the electronic device 100 can log in to the system account on the application, so that the application can push content that meets the user's interests and hobbies based on the personalized data associated with the system account, thereby realizing the flow of personalized data between applications, meeting the user's personalized needs in browsing application content, and avoiding the user spending a lot of time searching for content that meets their interests in the content pushed by the application.

[0287] To facilitate the sharing of digital identities between accounts, an identification code for the digital identity of a system account (hereinafter referred to as the system account identification code) can be generated based on the account information and the personalized data associated with the account. This identification code is used to represent the user's personalized digital identity. The electronic device 100 can use this identification code to share the digital identity of the system account with other accounts, making it easier to transfer digital identities between users. Furthermore, using the identification code to transfer personalized data between users can maximize the protection of user data privacy and reduce the risk of information leakage.

[0288] In one embodiment, after the electronic device 100 sends the personalized data of one or more applications to the manufacturer server 300, the manufacturer server 300 generates an identity code for the system account based on the personalized data, and the manufacturer server 300 then returns the identity code to the electronic device 100 for display. For example, the identity code may be the QR code 501 shown in FIG2E .

[0289] It is understood that since the identity code is used to indicate the personalized data associated with the system account, after electronic device 100 obtains the identity code, if electronic device 100 detects a user logging into the system account on an application, such as a third application, electronic device 100 can automatically send the personalized data associated with the system account to application server 400. Application server 400 then selects push content based on the personalized data and returns it to electronic device 100 for display. This avoids the intervention of manufacturer server 300 and speeds up the acquisition of personalized data by application server 400.

[0290] The following describes in detail the principle of generating the identity code of the system account in conjunction with the software structure block diagram of the electronic device 100 shown in FIG6 and the software structure diagram of the manufacturer server 300 shown in FIG8.

[0291] FIG11 is a module interaction diagram for generating an identity code for a system account provided in an embodiment of the present application.

[0292] As shown in FIG11 , the process of generating the identity code of the system account mainly involves the data collection module, data analysis module, feature encoding module, and data reporting module in the electronic device 100, and the feature generation module and digital identity generation module in the manufacturer server 300, including:

[0293] S201. The data collection module collects personalized data from the application and sends it to the data analysis module.

[0294] S202. The data parsing module performs structured processing on the personalized data and sends the processed personalized data to the feature encoding module.

[0295] The electronic device 100 can clean and process the personalized data to adjust the original personalized data into formatted data. For example, for one piece of personalized data, the electronic device 100 can adjust it into structured data containing multiple features shown in Table 1.

[0296] Table 1

[0297] In Table 1, "ID" may refer to the identifier of personalized data, "Timestamp" may refer to the time when the personalized data is obtained, and "Feature1, Feature2, ..., FeatureN" may refer to the N features contained in the personalized data. For example, the features may include: nickname, gender, application name, application type, keywords, etc.

[0298] S203. The feature encoding module vectorizes the processed personalized data to obtain a preference feature vector, and sends it to the data reporting module.

[0299] Exemplarily, performing vectorized representation on the processed personalized data refers to using a representation learning method to transform the processed personalized data into a high-dimensional space to obtain a preference feature vector.

[0300] S204 . The data reporting module sends the preference feature vector to the manufacturer server 300 .

[0301] That is, the electronic device 100 can send the personalized data after format adjustment, ie, the preference feature vector, to the manufacturer server 300 through the data reporting module. The manufacturer server 300 can receive the preference feature vector sent by the electronic device 100 through the feature generation module.

[0302] S205. The feature generation module fuses the preference feature vector and the identity vector of the system account to obtain a personalized feature vector, and sends it to the digital identity generation module.

[0303] The identity vector can be determined based on the account information of the system account, and the identity vector is used to uniquely identify a system account. In other words, the manufacturer server 300 can generate a personalized feature vector based on the account information of the system account of the electronic device 100 and the preference feature vector generated using the personalized data sent by the electronic device 100.

[0304] For example, FIG12 is a diagram showing the principle of generating a personalized feature vector according to an embodiment of the present application.

[0305] As shown in Figure 12, the feature generation module can convert various information in the account information into vectors. The account information includes: account ID, nickname, profile picture, gender, and other information. The account ID can refer to either the user identification (UID) or the device identification (DID). After vectorizing the account ID, the ID vector is obtained. After vectorizing the n other information in the account information, the attribute vector 1-n is obtained. The attribute vector 1-n is then dot-producted with the ID vector to obtain the identity vector. Finally, the identity vector is fused with the preference feature vector using a vector fusion method to obtain a personalized feature vector.

[0306] S206. The digital identity generation module generates a system account identity code based on the personalized feature vector, and the identity code is used to map the user's personalized digital identity. For example, FIG13 is a schematic diagram of a principle of generating a system account identity code based on a personalized feature vector provided by an embodiment of the present application.

[0307] As shown in FIG13 , generating the identity code of the system account may include the following steps:

[0308] Step 1: Use a QR code generator to randomly generate an identification code (such as a QR code).

[0309] Step 2: Use a convolutional neural network to convert the identification code into an N*M image matrix.

[0310] Step 3: Use the attention mechanism to fuse the personalized feature vector and the image matrix.

[0311] Step 4: Input the fused data into the self-encoder to output the identity code of the system account.

[0312] It can be seen that the identity code obtained through the above steps 1 to 4 stores a personalized feature vector, and the electronic device can obtain the personalized feature vector stored in the barcode by scanning the identity code of the system account.

[0313] It can be understood that Figure 13 only exemplifies a method of generating an identity code. In other embodiments of the present application, the manufacturer server 300 can also generate an identity code in other ways, and the embodiments of the present application do not limit this. In addition, in addition to directly storing the personalized feature vector in the identity code, the indication information of the personalized feature vector can also be stored. In this way, after scanning the identity code, the electronic device can still obtain the personalized feature vector through the information stored in the identity code.

[0314] In some embodiments, after generating the identity code, the manufacturer server 300 may also manage the reset, deletion, update, and sharing of the identity code through the lifecycle management module. For example, if the electronic device 100 detects a user operation to reset the identity code, the electronic device 100 may send an instruction to reset the identity code to the manufacturer server 300. The manufacturer server 300 may then re-collect the personalized data uploaded by the electronic device 100 and use the re-collected personalized data to generate the identity code.

[0315] FIG14 is a flow chart of the digital identity sharing process provided in an embodiment of the present application.

[0316] As shown in FIG14 , the digital identity sharing process mainly involves the interaction between the electronic device 100 , the manufacturer server 300 , and the application server 400 , and mainly includes:

[0317] S301 . The electronic device 100 obtains personalized data associated with the second account logged in on the electronic device 200 .

[0318] Exemplarily, the electronic device 100 can obtain the digital identity shared by the electronic device 200, that is, obtain the personalized data shared by the electronic device 200, by scanning the identity code (e.g., the second identity code) of the system account (i.e., the second account) logged in on the electronic device 200.

[0319] The identity code of the second account is used to indicate the personalized data associated with the second account. Specific principles for generating the identity code can be found in the above content and will not be repeated here.

[0320] It can be understood that the digital identity of the system account can be shared by scanning the identity code. In other embodiments of the present application, the electronic device 100 can also obtain the digital identity shared by the electronic device 200 in other ways. For example, the electronic device 200 can share the digital identity with the electronic device 100 by "touching" with the electronic device 100. The embodiments of the present application do not limit this.

[0321] S302 . The electronic device 100 sends a second message to the manufacturer server 300 .

[0322] For example, after detecting a user operation using a first account to log in to a fourth application, the electronic device 100 may send a second message to the manufacturer server 300, requesting the personalized data associated with the first account and the personalized data associated with the second account. In this way, via the second message, the manufacturer server 300 can send the personalized data associated with the first account and the personalized data associated with the second account to the application server for the application, facilitating the application's content recommendation based on the personalized data associated with multiple accounts.

[0323] Similar to the third application, the fourth application may also refer to a recommended application installed in the electronic device 100. The fourth application and the third application may be the same application or different applications, which is not limited in this embodiment of the present application.

[0324] For example, taking FIG. 4C and FIG. 4D as an example, the fourth application may refer to a music application, and the user operation of logging into the fourth application using the first account may refer to the user operation acting on the account login option 701 shown in FIG. 4C .

[0325] In some embodiments, after obtaining the personalized data shared by the electronic device 200, the electronic device 100 may send information indicating that the electronic device 200 has shared the personalized data to the manufacturer server 300 before sending the second message to the manufacturer server 300. In this way, the manufacturer server 300 can update the identity code of the first account in combination with the personalized data associated with the second account to obtain a shared identity code, and return the shared identity code to the electronic device 100. The electronic device 100 can then display the shared identity code, which is used to indicate the personalized data associated with the first account and the personalized data associated with the second account.

[0326] Exemplarily, the shared identity code may refer to the QR code 305 shown in FIG. 4B .

[0327] In a specific implementation, after the manufacturer server 300 obtains the instruction information indicating that the electronic device 200 shares the personalized data with the electronic device 100, the manufacturer server 300 can find the locally stored personalized feature vector corresponding to the first account (hereinafter referred to as personalized feature vector 1) and the personalized feature vector corresponding to the second account (hereinafter referred to as personalized feature vector 2), perform a dot product of personalized feature vector 1 and personalized feature vector 2 to obtain a shared feature vector 3, and finally generate a shared identity code using the shared feature vector 3. For a specific description of generating an identity code based on feature vectors, please refer to the relevant content of Figure 13 above and will not be repeated here.

[0328] Furthermore, the user operation of logging into the fourth application using the first account detected by the electronic device 100 may refer to a user operation of scanning the shared identity code on the fourth application.

[0329] It is understandable that after the electronic device 100 obtains the shared identity code, the shared identity code can be used to replace the original identity code of the first account, or the electronic device 100 can retain both the shared identity code and the original identity code of the first account.

[0330] S303 . In response to the second message, the manufacturer server 300 sends the personalized data associated with the first account and the personalized data associated with the second account logged in on the electronic device 200 to the application server 400 of the fourth application.

[0331] S304 . The application server 400 of the fourth application selects the second content from the content provided by the fourth application based on the personalized data associated with the first account and the personalized data associated with the second account.

[0332] S305 . The application server 400 of the fourth application sends the second content to the electronic device 100 .

[0333] S306. The electronic device 100 displays the second content of the fourth application, and the first account is logged in to the fourth application.

[0334] It is understood that steps S303-S306 are similar to steps S103-S106 described above, and for details not described in detail in steps S303-S306, reference may be made to steps S103-S106. The difference is that in steps S103-S106, the data sent by the manufacturer server 300 to the application server 400 is the personalized data associated with the first account, and the application server 400 also selects the push content based on the personalized data associated with the first account and sends it to the electronic device 100 for display. However, in steps S303-S306, because the first account obtains the digital identity shared by the second account, the data sent by the manufacturer server 300 to the application server 400 includes the personalized data associated with the first account and the personalized data associated with the second account. The application server 400 also selects the push content based on the personalized data associated with the first account and the personalized data associated with the second account and sends it to the electronic device 100 for display.

[0335] That is, the second content in steps S303-S306 is in line with the interests of the users of the electronic device 100 and the electronic device 200. For example, the second content may refer to the content in the recommended content display area 801 shown in FIG4D.

[0336] As can be seen from steps S301-S306, the digital identity of the system account can be shared between devices, so that personalized data collected under multiple accounts can be used to filter recommended content on the application. This allows the application to push content of interest to multiple users based on their interests, expand the usage scenarios of recommendation applications, realize information sharing between users, and help users better understand the preferences of other users when browsing applications.

[0337] It is understandable that after the electronic device 200 shares the digital identity with the electronic device 100, in addition to combining the personalized data associated with the first account and the personalized data associated with the second account to implement application content recommendations, in other embodiments of the present application, the electronic device 100 may also only use the personalized data associated with the second account to implement application content recommendations.

[0338] That is, in step S303, the manufacturer server 300, in response to the second message, can send the personalized data associated with the second account to the application server 400 of the fourth application. In step S304, the application server 400 can filter the second content from the content provided by the fourth application based on the personalized data associated with the second account. In this way, the second content displayed by the electronic device 100 is content that is pushed based on the interests and hobbies of the user of the electronic device 200.

[0339] In addition, since the electronic device 100 has obtained the personalized data associated with the second account, if the electronic device 100 detects a user logging into an application, such as a fourth application, using a system account, the electronic device 100 can automatically send the personalized data associated with the first account and the personalized data associated with the second account to the application server 400 of the application. The application server 400 then selects the push content based on the personalized data associated with the first account and the personalized data associated with the second account and returns it to the electronic device 100 for display. This avoids the intervention of the manufacturer server 300 and speeds up the acquisition of personalized data by the application server 400.

[0340] In some embodiments, because the second content matches the interests of both the user corresponding to the first account and the user corresponding to the second account, the electronic device 100 can also, based on user operation, switch the second content to content that only matches the interests of the user corresponding to one of the accounts. For example, based on user operation, the electronic device 100 can update the second content to third content, where the third content is push content selected by the application server of the fourth application from content provided by the fourth application based on the personalized data associated with the first account or the personalized data associated with the second account. In this way, content that meets the user's requirements can be selected, satisfying the user's personalized browsing needs.

[0341] In some embodiments, after electronic device 100 obtains the digital identity shared by electronic device 200, electronic device 100 may also receive an instruction from electronic device 200 to cancel sharing of personalized data, or detect a user operation to cancel sharing of personalized data and switch the shared identity of the first account back to the original digital identity. Subsequently, if electronic device 100 logs in to the system account again on an application, the application may use the personalized data associated with the first account for content recommendations, rather than the personalized data associated with the second account.

[0342] For example, if the electronic device 100 detects a user operation of logging into the first account on the fifth application after canceling sharing, the electronic device 100 can send a third message to the manufacturer server 300. The manufacturer server 300 can respond to the third message by sending the personalized data associated with the first account to the application server of the fifth application. The first application can display the fourth content of the fifth application, which is logged in with the first account. The fourth content is the push content filtered by the application server of the fifth application from the content provided by the fifth application based on the personalized data associated with the first account.

[0343] In some implementations, the electronic device 100 may display a first interface, where the first interface may be used to demonstrate sharing of personalized data associated with the first account in one or more accounts.

[0344] Furthermore, the first interface may include a first control, and the electronic device 100 may detect a user operation on the first control, and share the personalized data associated with the first account with other accounts (eg, a second account), or cancel sharing with other accounts.

[0345] Exemplarily, the first interface may refer to the user interface 50 shown in FIG. 2E , and the first control may include the icon 502A and the icon 502B shown in FIG. 2E .

[0346] In this way, users can view the usage of the personalized data of the local account by accounts on other devices, control the usage of the personalized data of the local account by other accounts, and ensure the secure sharing of data.

[0347] In some implementations, the electronic device 100 may display a second interface, which may be used to display access status of the personalized data associated with the first account in one or more applications.

[0348] Furthermore, the second interface may include a second control, and the electronic device 100 may detect a user operation on the second control, and allow or deny the application to access the personalized data associated with the first account.

[0349] Exemplarily, the second interface may refer to the user interface 40 shown in FIG. 2D , and the second control may include the icon 401A and the icon 401B shown in FIG. 2D .

[0350] In this way, users can view the usage of personalized data associated with the system account by each application at any time and control the permission of each application to use personalized data.

[0351] It should be understood that each step in the above method embodiment can be completed by hardware integrated logic circuits in a processor or by software instructions. The method steps disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.

[0352] The present application also provides an electronic device, which may include a memory and a processor. The memory may be used to store a computer program, and the processor may be used to call the computer program in the memory to enable the electronic device to execute the method executed by the electronic device 100 or the electronic device 200 or the manufacturer server 300 or the application server 400 in any of the above embodiments.

[0353] The present application also provides a chip system, which includes at least one processor for implementing the functions involved in the method executed by the electronic device 100 or the electronic device 200 or the manufacturer server 300 or the application server 400 in any of the above embodiments.

[0354] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0355] The chip system can be composed of chips, or can include chips and other discrete devices.

[0356] Optionally, there may be one or more processors in the chip system. The processor may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

[0357] Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited in the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or provided on different chips. The embodiments of the present application do not specifically limit the type of memory or the configuration of the memory and the processor.

[0358] Exemplarily, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

[0359] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute the method executed by any one of the electronic device 100, the electronic device 200, the manufacturer server 300, or the application server 400 in any of the above embodiments.

[0360] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, the computer executes the method executed by any one of the electronic device 100 or the electronic device 200 or the manufacturer server 300 or the application server 400 in any of the above embodiments.

[0361] It should be understood that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

[0362] In addition, embodiments of the present application further provide a device. Specifically, the device may be a component or module, and may include one or more processors and a memory connected to each other. The memory is configured to store a computer program. When the computer program is executed by one or more processors, the device performs the methods described in each of the above method embodiments.

[0363] The apparatus, computer-readable storage medium, computer program product, or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0364] The various implementation modes of this application can be combined arbitrarily to achieve different technical effects.

[0365] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described herein are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0366] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0367] In short, the above description is only an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made based on the disclosure of the present invention should be included in the scope of protection of the present invention.

Claims

1. An account management method, characterized in that: The method comprises: The first device sends personalized data of a first application and a second application to a manufacturer server, the first application and the second application belong to different developers, the personalized data is used to reflect the user's preference when browsing application content, and the personalized data is associated with a first account logged in on the first device; The first device sends a first message to the manufacturer server; The manufacturer server sends the personalized data associated with the first account to an application server of a third application in response to the first message; The first device displays first content of the third application, the third application is logged in with the first account, and the first content is push content selected by the application server of the third application from content provided by the third application based on personalized data associated with the first account.

2. The method according to claim 1, characterized in that A developer of the third application is different from developers of the first application and the second application.

3. The method according to claim 1 or 2, characterized in that: Before the first device sends the personalized data of the first application and the second application to the manufacturer server, the method further includes: The first device collects personalized data of the first application and the second application through a unified interface.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The manufacturer server generates a first identity code for the first account, where the first identity code is used to indicate personalized data associated with the first account; The manufacturer server sends the first identity code to the first device; The first device displays the first identity code.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The first device obtains personalized data associated with a second account logged in on the second device; The first device sends a second message to the manufacturer server; The manufacturer server sends the personalized data associated with the second account to an application server of a fourth application in response to the second message; The first device displays second content of the fourth application, the fourth application is logged in with the first account, and the second content is push content selected by the application server of the fourth application from content provided by the fourth application based on personalized data associated with the second account.

6. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The first device obtains personalized data associated with a second account logged in on the second device; The first device sends a second message to the manufacturer server; In response to the second message, the manufacturer server sends the personalized data associated with the first account and the personalized data associated with the second account to an application server of a fourth application; The first device displays second content of the fourth application, the fourth application is logged in with the first account, and the second content is push content filtered out by the application server of the fourth application from content provided by the fourth application based on personalized data associated with the first account and personalized data associated with the second account.

7. The method according to claim 6, characterized in that After the first device displays the second content of the fourth application, the method further includes: The first device updates the second content to third content based on a user operation, where the third content is push content selected by an application server of the fourth application from content provided by the fourth application based on personalized data associated with the first account or personalized data associated with the second account.

8. The method according to any one of claims 5 to 7, characterized in that: Before the first device acquires the personalized data associated with the second account logged in on the second device, the method further includes: The first device scans a second identity code of the second account, where the second identity code is used to indicate personalized data associated with the second account.

9. The method according to any one of claims 5 to 8, characterized in that: After the first device displays the second content of the fourth application, the method further includes: The first device receives instruction information sent by the second device to cancel sharing of personalized data, or detects a user operation to cancel sharing of personalized data; The first device sends a third message to the manufacturer server; The manufacturer server sends the personalized data associated with the first account to an application server of a fifth application in response to the third message; The first device displays fourth content of the fifth application, the first account is logged in to the fifth application, and the fourth content is push content selected by the application server of the fifth application from content provided by the fifth application based on personalized data associated with the first account.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: The first device displays a first interface, where the first interface is used to display sharing status of the personalized data associated with the first account in one or more accounts.

11. The method according to claim 10, characterized in that The first interface includes a first control, and the method further includes: The first device detects a user operation on the first control and shares the personalized data associated with the first account with the second account, or cancels sharing with the second account.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: The first device displays a second interface, where the second interface is used to display access status of personalized data associated with the first account in one or more applications.

13. The method according to claim 12, characterized in that The second interface includes a second control, and the method further includes: The first device detects a user operation on the second control and allows or denies the application to access the personalized data associated with the first account.

14. The method according to any one of claims 1 to 13, characterized in that After the first device displays the first content of the third application, the method further includes: The first device collects the personalized data of the third application and sends it to the manufacturer server; The manufacturer server updates the personalized data associated with the first account based on the personalized data of the third application.

15. An account management method, characterized in that: The method comprises: The first device sends personalized data of a first application and a second application to a manufacturer server, the first application and the second application belong to different developers, the personalized data is used to reflect the user's preference when browsing application content, and the personalized data is associated with a first account logged in on the first device; The first device receives a first identity code sent by the manufacturer server, where the first identity code is used to indicate personalized data associated with the first account; The first device displays the first identity code; The first device displays first content of the third application, the third application is logged in with the first account, and the first content is related to personalized data associated with the first account.

16. The method according to claim 15, characterized in that Before the first device displays the first content of the third application, the method further includes: The first device sends the personalized data associated with the first account to the application server of the third application.

17. The method according to claim 15 or 16, characterized in that A developer of the third application is different from developers of the first application and the second application.

18. The method according to any one of claims 15 to 17, characterized in that: Before the first device sends the personalized data of the first application and the second application, the method further includes: The first device collects personalized data of the first application and the second application through a unified interface.

19. The method according to any one of claims 15 to 18, characterized in that The method further comprises: The first device obtains personalized data associated with a second account logged in on the second device; The first device displays second content of the fourth application, the first account is logged in to the fourth application, and the second content is related to personalized data associated with the second account.

20. The method according to any one of claims 15 to 18, characterized in that The method further comprises: The first device obtains personalized data associated with a second account logged in on the second device; The first device displays second content of the fourth application, the first account is logged in to the fourth application, and the second content is related to personalized data associated with the first account and personalized data associated with the second account.

21. The method according to claim 20, characterized in that Before the first device displays the second content of the fourth application, the method further includes: The first device sends the personalized data associated with the first account and the personalized data associated with the second account to the application server of the fourth application.

22. The method according to claim 20 or 21, characterized in that After the first device displays the second content of the fourth application, the method further includes: The first device updates the second content to third content based on a user operation, where the third content is related to the personalized data associated with the first account or the personalized data associated with the first account.

23. The method according to any one of claims 19 to 22, characterized in that Before the first device acquires the personalized data associated with the second account logged in on the second device, the method further includes: The first device scans a second identity code of the second account, where the second identity code is used to indicate personalized data associated with the second account.

24. The method according to any one of claims 19 to 23, characterized in that After the first device displays the second content of the fourth application, the method further includes: The first device receives instruction information sent by the second device to cancel sharing of personalized data, or detects a user operation to cancel sharing of personalized data; The first device displays fourth content of the fifth application, the first account is logged in to the fifth application, and the fourth content is related to personalized data associated with the first account.

25. The method according to any one of claims 15 to 24, characterized in that The method further comprises: The first device displays a first interface, where the first interface is used to display sharing status of the personalized data associated with the first account in one or more accounts.

26. The method according to claim 25, characterized in that The first interface includes a first control, and the method further includes: The first device detects a user operation on the first control and shares the personalized data associated with the first account with the second account, or cancels sharing with the second account.

27. The method according to any one of claims 15 to 26, characterized in that The method further comprises: The first device displays a second interface, where the second interface is used to display access status of personalized data associated with the first account in one or more applications.

28. The method according to claim 27, characterized in that The second interface includes a second control, and the method further includes: The first device detects a user operation on the second control and allows or denies the application to access the personalized data associated with the first account.

29. The method according to any one of claims 15 to 28, characterized in that After the first device displays the first content of the third application, the method further includes: The first device collects and sends the personalized data of the third application, and the personalized data of the third application is used to update the personalized data associated with the first account.

30. An electronic device, characterized in that: It comprises a memory, one or more processors, and one or more programs; when the one or more processors execute the one or more programs, the electronic device implements the method as claimed in any one of claims 15 to 29.

31. A computer-readable storage medium comprising instructions, characterized in that: When the instructions are executed on an electronic device, the electronic device is caused to execute the method according to any one of claims 15 to 29.

Images