Account management method, graphical interface and related device

Abstract

The invention discloses an account management method, a graphical interface and a related device.In the method, electronic equipment can collect personalized data of multiple applications, different applications belong to different developers, the personalized data are used for reflecting preferences of a user when the user browses the applications, the personalized data are associated with a first account logged in the electronic equipment, and the first account is associated with a second account logged in the electronic equipment. In the embodiment of the invention, the electronic equipment can log in the first account on the application and notify the manufacturer server to send the personalized data associated with the first account to the application server of the application, so that the electronic equipment can display the push content screened from the content provided by the application based on the personalized data associated with the first account by the application server. Visibly, according to the method, the account can be used as a user personalized data storage and flowing medium, so that when the user uses the application for the first time after installing or updating, the application can accurately push the content which the user is interested in, and the browsing experience of the user is improved.

Description

Technical Field

[0001] 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

[0002] With the continuous development of the terminal field, various applications have met the entertainment needs of users. At present, applications with content recommendation functions are one of the most popular applications. This type of application includes e-commerce applications, video applications, music applications, etc., which continuously collect users' browsing history, personal information and other personalized data, analyze users' interests and hobbies, and accurately push content that users are interested in, including pictures, products, videos, music, etc., to provide users with more humane and intelligent entertainment services.

[0003] However, the content recommendation function of the application requires users to use the application for a period of time before accurate content push can be achieved. This means that when users first start using such applications, they cannot experience the service of accurate content push, which reduces the user experience. Summary of the invention

[0004] The present application provides an account management method, a graphical interface and related devices, which realize the use of system accounts as a medium for transmitting personalized data between various applications, thereby realizing a more accurate content push service for applications.

[0005] 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 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 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 first content of the third application, the third application is logged in with the first account, and the first content is push content filtered out by the application server of the third application from content provided by the third application based on the personalized data associated with the first account.

[0006] 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 that logs 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.

[0007] 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.

[0008] 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.

[0009] 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 collects the personalized data of the first application and the second application through a unified interface.

[0010] 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.

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

[0012] In combination with the first aspect, in one implementation, the method also includes: 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 responds to the second message and sends 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 selected 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.

[0013] 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, realize information sharing between family and friends, and enrich the content recommended by recommendation applications.

[0014] In combination with the first aspect, in one implementation, the method also includes: 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 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 a 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 the 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 and 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 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.

[0016] 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, and the third content is push content selected 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.

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

[0018] 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 a second identity code of the second account, where the second identity code is used to indicate the personalized data associated with the second account.

[0019] 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.

[0020] 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.

[0021] 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, so that when the application logs in to the system account, the personalized data originally associated with the system account can be used to push content.

[0022] In combination with the first aspect, in an implementation manner, 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.

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

[0024] 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.

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

[0026] 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.

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

[0028] 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.

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

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] That is to say, 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 amount of calculation of the application server.

[0036] In a second 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 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.

[0037] 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 that logs 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.

[0038] In combination with the second aspect, in an implementation manner, 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 an application server of the third application.

[0039] That is to say, when the electronic device needs to display the push 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 speed at which the application server obtains the personalized data.

[0040] It is understandable that, in addition to directly sending the personalized data associated with the local system account to the application server, the electronic device can also notify the manufacturer server to send the above personalized data to the application server. For example, the first device can send a first message to the manufacturer server, and the manufacturer server responds to the first message and sends the personalized data associated with the first account to the application server of the third application.

[0041] 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.

[0042] In combination 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 collects the personalized data of the first application and the second application through a unified interface.

[0043] In combination with the second aspect, in one implementation, the method also includes: the first device obtains personalized data associated with a second account logged in on the second device; the first device displays second content of a 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.

[0044] 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, realize information sharing between family and friends, and enrich the content recommended by recommendation applications.

[0045] In combination with the second aspect, in one implementation, the method also includes: the first device obtains personalized data associated with a second account logged in on the second device; the first device displays second content of a 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.

[0046] 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.

[0047] In combination with the second aspect, in an implementation manner, 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.

[0048] That is to say, when an electronic device needs to display the pushed content of an application, it 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's acquisition of personalized data.

[0049] It is understandable 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 can also notify the manufacturer server to send the above personalized data to the application server. For example, the first device can send a second message to the manufacturer server, and 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.

[0050] 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.

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

[0052] 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, and the second identity code is used to indicate the personalized data associated with the second account.

[0053] 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.

[0054] 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.

[0055] 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, so that when the application logs in to the system account, the personalized data originally associated with the system account can be used to push content.

[0056] 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.

[0057] 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.

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

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] That is to say, 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 amount of calculation of the application server.

[0068] 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 in the second aspect.

[0069] In a fourth aspect, an embodiment of the present application provides a computer storage medium, including 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.

[0070] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it 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

[0071] Figure 1 A schematic diagram of a communication system 1000 provided in an embodiment of the present application;

[0072] Figure 2A-2E , Figure 3A-3C , Figure 4A-4D Some user interfaces provided for embodiments of the present application;

[0073] Figure 5A schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of the present application;

[0074] Figure 6 A software structure block diagram of the electronic device 100 provided in an embodiment of the present application;

[0075] Figure 7 A hardware structure diagram of an electronic device 500 provided in an embodiment of the present application;

[0076] Figure 8 A software structure diagram of the manufacturer server 300 provided in the embodiment of the present application;

[0077] Fig. 9 A software structure diagram of the application server 400 provided in an embodiment of the present application;

[0078] Fig.10 A flowchart of an account management method provided in an embodiment of the present application;

[0079] Fig.11 A module interaction diagram for generating an identity code for a system account provided in an embodiment of the present application;

[0080] Fig.12 A schematic diagram of the generation principle of the personalized feature vector provided in the embodiment of the present application;

[0081] Fig.13 A schematic diagram of the principle of generating an identity code of a system account based on a personalized feature vector provided in an embodiment of the present application;

[0082] Fig.14 A flowchart of a digital identity sharing process provided in an embodiment of the present application. DETAILED DESCRIPTION

[0083] The technical solutions in the embodiments of the present application will be described clearly and in detail below 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 of associated 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.

[0084] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0085] The term "user interface (UI)" in the following embodiments of the present 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 can be recognized by the user. The commonly used form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operation 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.

[0086] 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, which is screened from the content provided by the application, based on the personalized data associated with the account.

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

[0088] If the first device collects personalized data of multiple applications, such as personalized data of 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, break down information barriers between applications, realize information sharing between applications, and effectively improve the accuracy of application content recommendation.

[0089] It can be seen that the 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 still 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.

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

[0091] 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 between family and friends, and enrich the content recommended by recommendation applications.

[0092] Figure 1 A schematic diagram of a communication system 1000 provided in an embodiment of the present application.

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

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

[0095] 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 the content that matches the user's interests and hobbies to the terminal device for display. In addition, 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 the content that matches the interests and hobbies of multiple users to the terminal device for display.

[0096] The manufacturer server can provide cloud computing services for the terminal device, back up the data of the terminal device, and manage and maintain the system account registered on the terminal device. In the embodiment of the present application, the manufacturer 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, so that after the terminal device logs in to the system account on the application, it can display the content recommended according to the personalized data.

[0097] For example, Figure 1 As shown, the communication system 1000 may include: an electronic device 100 , an electronic device 200 , a manufacturer server 300 , and an application server 400 .

[0098] 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 the electronic device 100 to achieve the association between the personalized data and the system account. Afterwards, when the electronic device 100 logs in to the system account on the application, the 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.

[0099] Furthermore, the electronic device 100 can also share the personalized data associated with the system account with the account 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 as an example, the electronic device 100 can obtain the indication information of the electronic device 200 sharing the personalized data, and send the indication 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 device 100 and the electronic device 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 interests and hobbies of the user according to the personalized data, and then return the content that meets the interests and hobbies, so that the electronic device 100 can display the content pushed by the application according to the personalized data associated with multiple system accounts.

[0100] 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 embodiment of the present application does not limit this.

[0101] 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.

[0102] In addition, it should be noted that the server mentioned in the embodiments of the present application, such as an application server, a manufacturer server, etc., can be a server or a server cluster composed of multiple servers. For example, the manufacturer server 300 can be a server cluster in which multiple servers are deployed through a distributed architecture, and the cluster can include one or more of a cloud computing server, a content delivery network (Content Delivery Network, CDN) server, a network time protocol (Network Time Protocol, NTP), a domain name resolution system (Domain Name System, DNS) server, etc. Among them, the various servers can coordinate with each other to jointly complete functions such as computing, data storage, and communication.

[0103] Combine the following Figure 2A-2E , Figure 3A-3C , Figure 4A-4DIntroduce some user interfaces involved in the embodiments of the present application.

[0104] Figure 2A-2E The relevant user interface for setting a system account by setting an application on the electronic device 100 provided in an embodiment of the present application is shown.

[0105] Figure 2A An exemplary user interface 10 of a settings application provided in an embodiment of the present application. Exemplarily, the user interface 10 may be used to display options corresponding to one or more settings functions, for example, the settings functions may include: system account, airplane mode, Wi-Fi, Bluetooth, personal hotspot, mobile network, permissions and privacy, display and brightness, etc.

[0106] It is understandable that the electronic device 100 can trigger the startup of the setting application by detecting a user operation on the application icon of the setting application, such as a click operation, and displaying the setting application. Figure 2A The user interface 10 shown, or the electronic device 100 can also trigger the start of the setting application by detecting the user's voice command, which is not limited in this embodiment of the present application.

[0107] like Figure 2A As shown, the user interface 10 may include: option 101. The option 101 is an option corresponding to the system account. Exemplarily, the option 101 may display the nickname of the system account of the electronic device 100, such as "user XXX".

[0108] It is understandable that the system account on the electronic device 100 can be an account registered on the electronic device 100 when the user first uses the electronic device 100, wherein the user can enter the registration information of the system account during the process of registering and completing the system account, including: nickname, avatar, password, gender, email address, etc. Afterwards, the electronic device 100 can collect personalized data generated by each application during operation and send it to the manufacturer server corresponding to the electronic device 100, such as the manufacturer server 300 mentioned above.

[0109] In some embodiments, when a user registers or logs into 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 application data. Only after the electronic device 100 detects that the user agrees to the authorization operation can the personalized application data be collected during the subsequent user's use of the application to implement the application's content recommendation function, that is, push content that matches the user's interests and hobbies.

[0110] When the electronic device 100 detects a user operation on the option 101, such as a click operation, in response to the operation, the electronic device 100 may display the following Figure 2BThe user interface 20 shown may 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.

[0111] For example, Figure 2B As shown, the user interface 20 may include: option 201. Option 201 is an option corresponding to the digital identity of the system account. The digital identity indicates the personalized data associated with the system account. After the application logs in to the system account, the digital identity of the system account and the personalized data associated with the system account can be used to push content that meets the user's interests.

[0112] 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 the following Figure 2C A user interface 30 is shown, which may be used to display one or more functions included in a digital identity.

[0113] like Figure 2C As shown, 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. Among them:

[0114] The QR code 301 is a QR code corresponding to the digital identity of the system account on the electronic device 100, and 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 identifier, nickname, avatar, password, gender, email address, etc. of the system account. In a specific implementation, the manufacturer server 300 may obtain the account information of the system account of the electronic device 100 and the personalized data collected under the system account, and then generate the QR code 301 based on the system account, and then send the QR code 301 to the electronic device 100.

[0115] 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 information of 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, and re-collect the personalized data collected from the electronic device 100, and generate the QR code using the re-collected personalized data.

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

[0117] 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 .

[0118] For example, when the electronic device 100 detects that the Figure 2C In response to a user operation of the application management option 303 shown, such as a click operation, the electronic device 100 may display a Figure 2D The user interface 40 shown may be used to display the login status of a system account in one or more applications.

[0119] like Figure 2D As shown, the user interface 40 may include: an application list 401. Among them, the application list 401 may include three items: "APP", "Access time", and "Access status". "APP" represents the application installed in the electronic device 100, "Access time" represents the time when the application is allowed to use the digital identity, and "Access status" represents the state of the application accessing the digital identity, wherein "Access status" may include two states: "Accessed state" and "Not accessed state". "Accessed state" means that the application is currently granted permission to use the digital identity, and the application can use the personalized data associated with the system account, and "Not accessed state" means that the application is currently not granted permission to use the digital identity, and the application cannot use the personalized data associated with the system account. Exemplarily, "Accessed state" can be expressed as a black dot as shown in icon 401A, and "Not accessed state" can be expressed as a white dot as shown in icon 401B. Optionally, the application list 401 may also include: More options 401C. The more options 401C can be used to add new applications to the application list 401, so that users can control the permission to use personalized data for the application.

[0120] In some embodiments, the electronic device 100 may also detect modification operations on the "access status" of different applications, allowing or denying applications to access the digital identity. Figure 2D In the example, 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, and deny application A from accessing 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, and allow application B to access the personalized data associated with the system account.

[0121] For example, when the electronic device 100 detects that the Figure 2C In response to a user operation of the identity sharing option 304 shown, such as a click operation, the electronic device 100 may display a Figure 2E The user interface 50 shown may be used to display the sharing status of the digital identity on the electronic device 100 by other users.

[0122] like Figure 2E As shown, the user interface 50 may include: a QR code 501 and a user list 502. The QR code 501 is a QR code corresponding to the digital identity of the system account of the electronic device 100. The electronic device 100 may share the QR code 501 with other devices, so that other devices can obtain the indication information of the electronic device 100 sharing personalized data by scanning the QR code, and realize the sharing of the digital identity of the system account. The user list 502 may include three items: "user", "access time" and "access status". "User" represents the nickname of the system account on other devices that share the digital identity with the electronic device 100, "access time" represents the time when the other system account shares the digital identity with the electronic device 100, and "access status" represents the state in which the other system account currently shares the digital identity with the system account in the electronic device 100, wherein "access status" may include two states: "shared state" and "unshared state". "Shared state" means that the other system account currently obtains the digital identity shared by the system account on the electronic device 100, and "unshared state" means that the other system account currently does not obtain the digital identity shared by the system account on the electronic device 100. Exemplarily, 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, the user list 502 may further include: more options 502C. The more options 502C may be used to add a system account that shares a digital identity with the system account on the electronic device 100 to the user list 502, so as to facilitate the user of the electronic device 100 to control the authority of other system accounts to share the digital identity of the system account on the electronic device 100.

[0123] In some implementations, the electronic device 100 may also detect the modification operation of the "access status" of different system accounts, and share the digital identity of the system account logged in on the electronic device 100 with other system accounts, or cancel the sharing with other system accounts. Figure 2E In the example, 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, canceling or refusing 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, sharing the digital identity of the system account logged in on the electronic device 100 with "User_2". Figure 2A-2EIt can be seen that the electronic device 100 can manage the system account 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.

[0124] Figure 3A-3C The following figure shows the user interface of the electronic device 100 provided in the embodiment of the present application for logging into the system account on the application. Figure 3A-3C Taking the music application as an example, the user interface related to the electronic device 100 logging into the system account on the music application is shown. It should be understood that in other embodiments of the present application, the electronic device 100 can also log into the system account on other applications, and the embodiments of the present application are not limited to this.

[0125] Figure 3A An exemplary user interface 60 corresponding to the desktop on the electronic device 100 provided in the embodiment of the present application.

[0126] like Figure 3A As shown, the user interface 60 may include: a status bar 601, a calendar and weather indicator 602, and one or more application icons 603. Among them:

[0127] The status bar 601 may include one or more signal indicators of mobile communication signals, one or more signal strength indicators of wireless 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 of one or more applications. For example, Figure 3A As shown, one or more application icons 603 may include application icon 603A, which is an application icon for a music application.

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

[0129] 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 way to open the music application.

[0130] like Figure 3A The operation of starting the music application shown is the operation of starting the application for the first time after installing or updating the music application. When the electronic device 100 starts the music, it can display Figure 3BThe user interface 70 shown may be used to display an account login page of a music application.

[0131] It is understandable that the electronic device 100 may also trigger the display of the music application user interface after detecting the user opening the account login page. Figure 3B As shown in the user interface 70 , 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.

[0132] like Figure 3B As shown, the user interface 70 may include: an account login option 701 and other login options 702. The account login option 701 may be used to trigger logging into a system account on the electronic device 100 on the music application, and the other login option 702 may be used to trigger logging into an account on the music application using other methods, for example, logging into the music application using a WeChat account, or logging into the music application using a mobile phone number, etc.

[0133] 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 following information: Figure 3C The user interface 80 shown is the home page of the music application.

[0134] 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 implement account login 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 a digital identity of a system account on the electronic device 100, for example Figure 2C The QR code 301 shown is used to log in to the system account on the electronic device 100 through the music application.

[0135] like Figure 3C As shown, 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 these personalized data, and then selects 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, Figure 3CAs shown, the recommended content display area 801 may display song names such as "Song 1", "Song 2", "Song 3", etc. The electronic device 100 may detect a click operation on any of the songs and play the song.

[0136] from Figure 3A-3C It can be seen that the electronic device 100 can log in to the system account on the application, so that the application can push content that matches 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.

[0137] Figure 4A-4D The electronic device 100 provided in the embodiment of the present application obtains the digital identity of the system account shared by other devices and involves the relevant user interface.

[0138] Figure 4A The user interface 90 for scanning a code on the electronic device 100 provided in the embodiment of the present application. The user interface 90 may be a user interface displayed after the electronic device 100 detects that the user has started the code scanning function. For example, the code scanning function may be a function included in an application such as a setting application, a browser application, etc. The embodiment of the present application triggers the display of the electronic device 100. Figure 4A The interactive manner of the illustrated user interface 90 is not limited.

[0139] like Figure 4A As shown, 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 by the camera in real time. 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 identify the information in the identification code and trigger a corresponding response.

[0140] For example, a 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.

[0141] 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, and the manufacturer server can combine the two digital identities to regenerate a shared identity under the system account of the electronic device 100, and 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, and the manufacturer server then sends the shared identity to the electronic device 100. In this way, the electronic device 100 can implement account login 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.

[0142] 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.

[0143] Since the gallery icon 902 can be used to trigger the opening of the gallery application and select the QR code saved 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 on other devices saved in the gallery. In this case, the electronic device 200 can send the QR code of the digital identity to the electronic device 100 through short-distance communication methods such as Bluetooth, WiFi, and sharing methods such as instant messaging applications.

[0144] Figure 4B The user interface 30 corresponding to the digital identity of the system account in the setting application provided in the embodiment of the present application, for a specific description of the user interface 30, please refer to the aforementioned Figure 2B-2C The relevant content will not be repeated here.

[0145] In addition, Figure 2CThe difference is that 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 personalized data associated with the system account in the electronic device 100, as well as personalized data associated with the system account in the electronic device 200.

[0146] For example, Figure 4B As shown, the user interface 30 originally displays Figure 2C The QR code 301 shown 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.

[0147] In addition, the user interface 30 may also include a close option 306, which can be used to switch the shared identity under the system account back to the original digital identity, and stop 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. Exemplarily, the electronic device 100 can detect a user operation acting on the close option 306, such as a click operation, and in response to the operation, the electronic device 100 can update the QR code 305 to Figure 2C The QR code 301 shown ends the sharing of the digital identity of the electronic device 200. In this way, after the electronic device 100 uses the system account to log in to the application, the content recommendation can be realized using only the personalized data associated with the system account of the electronic device 100.

[0148] In some embodiments, the user interface 30 may also display a QR code of the original digital identity, for example Figure 2C The QR code 301 shown, and the QR code of the shared identity, e.g. Figure 4B The QR code 305 is shown. The electronic device 100 can choose to use the original digital identity or the shared identity when logging into the system account on the application based on the user operation.

[0149] Understandably, Figure 4C-4D Taking the music application as an example again, the following illustrates the relevant user interfaces involved when the electronic device 100 logs into the system account on the music application after obtaining the digital identity shared by other devices. 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.

[0150] like Figure 4C As shown, the user interface 70 can be used to display the account login page of the music application. For a detailed description of the user interface 70, please refer to the aforementioned Figure 3A-3B In addition, Figure 4C As shown, since the electronic device 100 obtains the digital identity shared by the electronic device 200, the user interface 70 also displays a sharing prompt information 704, and the sharing prompt information 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 the pushed content based on the personalized data associated with the system accounts on the electronic devices 100 and 200.

[0151] Optionally, the electronic device 100 can detect the selection operation of the user on the sharing prompt information 704 to select whether to open or close the identity sharing of the system account "User_1". Exemplarily, if the sharing prompt information 704 is in a selected state, for example, the dots in the sharing prompt information 704 are black dots, the electronic device 100 can use the shared identity of the system account to log in to the application, and if the sharing prompt information 704 is in an unselected state, for example, the dots in the sharing prompt information 704 are white dots, the electronic device 100 can use the original digital identity of the system account to log in to the application.

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

[0153] like Figure 4D As shown, 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 server, and the manufacturer 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 selects 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 Figure 4DAs shown, 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.

[0154] from Figure 4A-4D It can be seen that 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 of multiple users.

[0155] It is understandable that the above Figure 4A-4D 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 of 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 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.

[0156] Figure 5 A schematic diagram of the hardware structure of the electronic device 100 is shown.

[0157] 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 special restrictions on the specific type of the electronic device.

[0158] 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.

[0159] It is to be understood that the structure illustrated in the embodiment 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 in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0160] 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 processor (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), etc. Different processing units may be independent devices or integrated into one or more processors.

[0161] 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. Further, the processor 110 may also 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.

[0162] 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.

[0163] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0164] 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.

[0165] 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 the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0166] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., 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.

[0167] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent 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 the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a 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.

[0168] 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 integrating 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, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0169] 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 the network and other devices through wireless communication technology. The wireless communication technology 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).

[0170] 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 login information of the system account to the application server 400, receive application push content returned by the application server 400, and so on.

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

[0172] 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.

[0173] 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 the content recommended by the application, such as text, pictures, videos, audio, etc., in the user interface of the application.

[0174] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

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

[0176] 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 .

[0177] 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.

[0178] 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 .

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

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

[0181] Figure 6 It is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention.

[0182] The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely the application layer, the application framework layer, the Android runtime and the system libraries, and the kernel layer.

[0183] The application layer may include a series of application packages.

[0184] Such as Figure 6 shown, the application packages may include recommended applications, settings applications, cameras, galleries, calendars, calls, maps, navigation, WLAN, Bluetooth, text messages and other applications.

[0185] Among them, the recommended application can 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 according to the user's interests and hobbies. Among them, the recommended application may include: e-commerce applications, video applications, music applications, and so on.

[0186] Taking the video application as an example, the video application can collect the user's browsing records of videos during the process of the user browsing videos, analyze the types of videos preferred by the user according to the browsing frequencies of the user for different types of videos, so as to increase the pushing frequency of videos of this type. For example, if the user has a high browsing frequency for food-related videos, the video application can increase the pushing frequency of food-related videos.

[0187] In addition, in the embodiment of the present application, the electronic device 100 can log in to the system account on the recommended application, and the personalized data from one or more applications is collected in this account. Then, during the process of the electronic device 100 running the recommended application, the recommended application can analyze the user's interests and hobbies based on the personalized data of these one or more applications, and selectively display content that matches the user's interests and hobbies.

[0188] Taking the e-commerce application as an example, if the electronic device 100 logs in to the system account on the e-commerce application, the e-commerce application can analyze the user's interests and hobbies based on the personalized data of each application collected under this system account. For example, through the user's high browsing frequency for food-related videos in the video application, it is analyzed that the user has a greater interest in food-related products. Therefore, the e-commerce application can increase the pushing frequency of food-related products.

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

[0190] In addition, in the embodiment of the present application, the electronic device 100 can manage the system account by setting up an application to 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.

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

[0192] like Figure 6 As shown, 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:

[0193] 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.

[0194] The data analysis module can be used to clean and structure the personalized data and convert it into structured data. For details about the structuring of data, please refer to the subsequent content, which will not be expanded here.

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

[0196] 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.

[0197] It is understandable that the data analysis module and the feature coding module are optional modules. After the electronic device 100 collects the personalized data through the data collection module, it can also directly send the unprocessed personalized data to the server through the data reporting module. However, by comparison, the processing of the personalized data by the data analysis module and the feature coding 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 to process the data.

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

[0199] 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.

[0200] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

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

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

[0203] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0204] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0205] 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.

[0206] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0207] The system library may 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.

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

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

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

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

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

[0213] The following is an illustrative description of the workflow of the software and hardware of the electronic device 100 in conjunction with capturing a photo scene.

[0214] 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, timestamp of the touch operation, 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 static images or videos through the camera 193.

[0215] Figure 7 A hardware structure diagram of an electronic device 500 provided in an embodiment of the present application.

[0216] like Figure 7 As shown, the 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. Figure 7 Take bus connection as an example.

[0217] 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.

[0218] In some embodiments of the present application, the transmitter 205 and the receiver 206 can be regarded 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 the transmitter 205 and the receiver 206 can be one or more. The antenna 208 can be used to convert the electromagnetic energy in the transmission line into electromagnetic waves in the free space, or to convert the electromagnetic waves in the free space into electromagnetic energy in the transmission line. The coupler 207 can be used to divide the mobile communication signal into multiple paths and distribute it to multiple receivers 206. It can be understood that the antenna 208 of the electronic device 500 can be implemented as a large-scale antenna array.

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

[0220] 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.

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

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

[0223] 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 and sent by the electronic device 100 .

[0224] 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.

[0225] 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 the personalized data associated with the system account to the application server 400 so that the application server 400 can make content recommendations based on the personalized data.

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

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

[0228] 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 .

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

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

[0231] It can be understood 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 is not limited to this.

[0232] Figure 8 A software structure diagram of the manufacturer server 300 provided in an embodiment of the present application.

[0233] like Figure 8 As shown, the manufacturer server 300 may include but is not limited to the following multiple software modules: feature generation module 301, digital identity generation module 302, life cycle management module 303, identity verification module 304. Among them:

[0234] 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.

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

[0236] The lifecycle management module 303 may be used to manage operations such as authorization, withdrawal, and data deletion of system accounts.

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

[0238] 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.

[0239] Fig. 9 A software structure diagram of the application server 400 provided in an embodiment of the present application.

[0240] like Fig. 9 As shown, the application server 400 may include but is not limited to the following multiple software modules: digital identity access protocol 401, recommendation system 402. Among them:

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

[0242] In a specific implementation, when the electronic device 100 logs in to the system account in the application, the application can specify the format of the personalized data sent to the application server 400 through the digital identity access protocol 401, as well as relevant standards such as the data encryption algorithm, so that the manufacturer server 300 can convert the personalized data into a vector of a specified format before sending the personalized data, and then encrypt the personalized data in the vector format according to the specified data encryption algorithm, and then send it to the application server 400. It can be seen that using the digital identity access protocol 401 to receive personalized data can achieve low-cost docking between the application and the system account, reduce the amount of calculation of the application server 400 as much as possible, and reduce the difficulty of adaptation of the application server 400 in this solution.

[0243] 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.

[0244] It is understandable that the application server 400 may also include more or fewer software modules, and the embodiments of the present application are not limited to this.

[0245] Fig.10 A flowchart of an account management method provided in an embodiment of the present application.

[0246] like Fig.10 As shown, the account management method provided in the embodiment of the present application may mainly include the following steps:

[0247] S101. The electronic device 100 sends personalized data of a first application and a 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 preference when browsing application content. The personalized data is associated with the first account logged in on the electronic device 100.

[0248] The first account may refer to a system account logged in on the electronic device 100. The system account refers to an account used to log in and manage electronic devices and related services. The account is an identity authentication tool provided by the device manufacturer. Users can log in to their own devices through the account, and can use the account to manage cloud services, backup and recovery, and other functions.

[0249] A system account can be used to uniquely identify a user, and the first account can be regarded as a "label" for the user to use the electronic device 100. When the user uses the electronic device 100, the electronic device 100 can upload the generated data, including photos, contacts, videos, files, etc., to the manufacturer server 300, and bind the data to the first account. In this way, even if the user changes the device, the data generated when the electronic device 100 is used in the past can be viewed by logging into the first account on other devices.

[0250] Exemplarily, the electronic device 100 may log in the system account when used for the first time. Specifically, the electronic device 100 may display the system account login page, and complete the login of the first account after the electronic device 100 detects that the user inputs the login information of the first account.

[0251] 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.

[0252] 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 records, personal information input by the user during the use of the application, and the like.

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

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

[0255] Exemplarily, the electronic device 100 may collect personalized data in the following situations:

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

[0257] That is to say, the electronic device 100 can trigger the collection of personalized data collected by various applications at regular intervals.

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

[0259] 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.

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

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

[0262] In some implementations, in order to improve the processing efficiency of the manufacturer server 300 for personalized data, 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 personalized data with the adjusted format, the manufacturer server 300 may directly use the personalized data to determine the push content, thereby speeding up the speed at which the electronic device 100 displays the recommended content and reducing the amount of computation of the manufacturer server 300.

[0263] For example, the electronic device 100 may 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. For a detailed description of how the electronic device 100 adjusts the format of the personalized data, please refer to the following Fig.11 The relevant content in will not be expanded here.

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

[0265] Exemplarily, after detecting a user operation of using the first account to log in to the third application, 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.

[0266] The third application may refer to a recommendation application installed in the electronic device 100 , which may analyze the interests of the user according to the user's personalized data, and selectively display content that matches the user's interests to the user according to the user's interests.

[0267] The developer of the third application may be different from the developer of the first application and the developer of the second application. In this way, the personalized data of the application can be circulated between applications developed by different developers, solving the problem that the personalized data between applications of different manufacturers cannot flow, and realizing data sharing between applications.

[0268] For example, Figure 3A-3C For example, the third application may refer to a music application, and the user operation of using the first account to log in to the third application may refer to Figure 3B User operations acting on account login option 701 are shown.

[0269] 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.

[0270] In some embodiments, since the application server 400 uses a recommendation model, personalized data is input into the recommendation model to filter out content that meets the user's interests 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 application servers corresponding to different applications.

[0271] In order to reduce the amount of calculation required by the application server to adjust the data format, the manufacturer server 300 may convert the data format of the personalized data into a data format that is adapted to the recommendation model before sending the personalized data. The digital identity access protocol stipulates the network layer structure in the recommendation model, and the manufacturer server 300 may convert the personalized data into a vector dimension corresponding to the network layer structure in the recommendation model according to the relevant parameters stipulated in the digital identity access protocol, and then send the converted personalized data to the application server 400.

[0272] 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 fuses a preference feature vector and an identity vector, wherein 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 the adapted format, the vector fusion method used by the manufacturer server 300 when fusing the identity vector and the preference feature vector. In this way, after obtaining the personalized feature vector, the application server 400 may 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.

[0273] Furthermore, the digital identity access protocol may also stipulate a data encryption algorithm, and 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.

[0274] It is understandable that, in addition to directly sending the personalized data associated with the first account to the application server 400, the manufacturer server 300 can 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 can send the personalized data associated with the first account to the electronic device 100, and the electronic device 100 then sends it to the application server 400 of the third application.

[0275] 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.

[0276] The application server 400 can analyze the interests and hobbies of the user based on the personalized data associated with the first account, and filter out the content that matches the interests and hobbies of the user from the content provided by the third application according to the interests and hobbies of the user. The content may refer to information such as pictures, videos, audio, news, articles, etc. For example, if the third application is a music application, the first content may refer to songs, and for another example, if the third application is a video playback application, the first content may refer to videos.

[0277] 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 the recommended content based on the personalized data based on the status.

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

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

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

[0281] Exemplarily, the first content may refer to Figure 3C The content in the recommended content display area 801.

[0282] 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 the application logged in to the first account.

[0283] It is understandable that the electronic device 100 may log in the first account on the third application before step S102, or log in the first account on the third application before step S106. That is to say, the electronic device 100 may first log in the system account on the application, and then send a message to the manufacturer server 300 requesting to obtain the personalized data associated with the system account, so as to display the push content filtered based on the personalized data on the application, or the electronic device 100 may first send a message to the manufacturer server 300 requesting to obtain the personalized data associated with the system account, and then log in the system account on the application, and display the push content filtered based on the personalized data on the application.

[0284] 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 matches 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 for browsing application content, and avoiding the user spending a lot of time searching for content that matches their interests in the content pushed by the application.

[0285] In order to improve the convenience of sharing digital identities between accounts, an identification code of the digital identity of the system account (hereinafter referred to as the identity code of the system account) can be generated based on the account information and the personalized data associated with the account. The identity code is used to represent the personalized digital identity of the user. The electronic device 100 can share the digital identity of the system account with other accounts through the identification code, which is convenient for transferring digital identities between users. In addition, the personalized data between users is transferred through the identification code, which can protect the user's data privacy as much as possible and reduce the risk of information leakage.

[0286] In one implementation, 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 of the system account according to the personalized data, and the manufacturer server 300 returns the identity code to the electronic device 100 for display. For example, the identity code may refer to Figure 2E QR code 501 is shown.

[0287] It is understandable that, since the identity code is used to indicate the personalized data associated with the system account, after the electronic device 100 obtains the identity code, if the electronic device 100 detects a user operation of logging into the system account on an application, such as a third application, the electronic device 100 can send the personalized data associated with the system account to the application server 400, and the application server 400 selects the push content according to the personalized data and returns it to the electronic device 100 for display. In this way, the intervention of the manufacturer server 300 can be avoided, and the speed at which the application server 400 obtains the personalized data can be accelerated.

[0288] Combine the following Figure 6 The software structure diagram of the electronic device 100 is shown, and Figure 8 The software structure diagram of the manufacturer server 300 shown in FIG. 1 describes in detail the principle of generating the identity code of the system account.

[0289] Fig.11 A module interaction diagram for generating an identity code for a system account provided in an embodiment of the present application.

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

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

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

[0293] The electronic device 100 can clean and process the personalized data, and 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.

[0294] Table 1

[0295]

[0296] 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.

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

[0298] Exemplarily, vectorizing the processed personalized data means transforming the processed personalized data into a high-dimensional space using a representation learning method to obtain a preference feature vector.

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

[0300] That is, the electronic device 100 can send the personalized data after format adjustment, that is, 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.

[0301] 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.

[0302] 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 by the personalized data sent by the electronic device 100.

[0303] For example, Fig.12 A schematic diagram of the generation principle of the personalized feature vector provided in the embodiment of the present application.

[0304] like Fig.12 As shown, the feature generation module can convert each piece of information in the account information into a vector, wherein the account information includes: account identification, nickname, avatar, gender and other information, wherein the account identification can refer to user identification (UID) or device identification (DID). After vectorizing the account identification, an ID vector can be obtained, and after vectorizing n other information in the account information, an attribute vector 1-n can be obtained. After that, the attribute vector 1-n is dot-multiplied with the ID vector to obtain the identity vector, and finally the identity vector is fused with the preference feature vector using the vector fusion method to obtain a personalized feature vector.

[0305] 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, Fig.13 A schematic diagram of the principle of generating an identity code of a system account based on a personalized feature vector provided in an embodiment of the present application.

[0306] like Fig.13 As shown, generating the identity code of the system account may include the following steps:

[0307] Step 1: Use a QR code generator to randomly generate an identification code (eg, a QR code).

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

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

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

[0311] 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.

[0312] Understandably, Fig.13 It is only an example of a method for 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, the identity code can also store indication information of the personalized feature vector. 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.

[0313] In some implementations, after the manufacturer server 300 generates the identity code, it can 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 of resetting the identity code, the electronic device 100 can send an instruction message of resetting the identity code to the manufacturer server 300, and the manufacturer server 300 can re-collect the personalized data uploaded by the electronic device 100, and generate the identity code using the re-collected personalized data.

[0314] Fig.14 A flowchart of a digital identity sharing process provided in an embodiment of the present application.

[0315] like Fig.14 As shown, 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:

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

[0317] 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 (eg, the second identity code) of the system account (ie, the second account) logged in on the electronic device 200.

[0318] The identity code of the second account is used to indicate the personalized data associated with the second account. The specific principle of generating the identity code can be found in the above content, which will not be repeated here.

[0319] It is understandable 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" the electronic device 100. The embodiments of the present application are not limited to this.

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

[0321] For example, after detecting a user operation of logging into a fourth application using a first account, the electronic device 100 may send a second message to the manufacturer server 300, where the second message is used to request the personalized data associated with the first account and the personalized data associated with the second account. In this way, through the second message, the manufacturer server 300 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 application, so that the application can recommend content based on the personalized data associated with multiple accounts.

[0322] 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 the embodiment of the present application.

[0323] For example, Figure 4C-4D For 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 Figure 4C User operations acting on account login option 701 are shown.

[0324] In some implementations, the electronic device 100 may send the manufacturer server 300 indication information that the electronic device 200 shares the personalized data after acquiring the personalized data shared by the electronic device 200 and before sending the second message to the manufacturer server 300. In this way, the manufacturer server 300 may update the identity code of the first account in combination with the personalized data associated with the second account, obtain the shared identity code, and return the shared identity code to the electronic device 100, after which the electronic device 100 may 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.

[0325] Exemplarily, the shared identity code may refer to Figure 4B The QR code 305 is shown.

[0326] In a specific implementation, after the manufacturer server 300 obtains the indication information that the electronic device 200 shares the personalized data with the electronic device 100, the manufacturer server 300 can find the personalized feature vector corresponding to the first account stored locally (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), do a dot product of personalized feature vector 1 and personalized feature vector 2, obtain shared feature vector 3, and finally generate a shared identity code through the shared feature vector 3. For a specific description of generating an identity code based on a feature vector, please refer to the aforementioned Fig.13 The relevant content will not be repeated here.

[0327] Further, the user operation of using the first account to log in to the fourth application detected by the electronic device 100 may refer to a user operation of scanning the shared identity code on the fourth application.

[0328] 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.

[0329] 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.

[0330] 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.

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

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

[0333] It is understandable that the contents of steps S303-S306 are similar to those of the above steps S103-S106, and the contents not described in steps S303-S306 may be referred to in correspondence with 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, while in steps S303-S306, since 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, and 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.

[0334] 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 Figure 4D The content in the recommended content display area 801 is shown.

[0335] It can be seen from steps S301-S306 that 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.

[0336] 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.

[0337] That is, in step S303, the manufacturer server 300 can send the personalized data associated with the second account to the application server 400 of the fourth application in response to the second message, and in step S304, the application server 400 can filter out 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 the content pushed according to the interests of the user of the electronic device 200.

[0338] 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 operation of logging into a system account on an application, such as the fourth application, the electronic device 100 can 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, and the application server 400 screens out 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. In this way, the intervention of the manufacturer server 300 can be avoided, and the speed at which the application server 400 obtains the personalized data can be accelerated.

[0339] In some implementations, since the second content matches the interests of the user corresponding to the first account and the user corresponding to the second account, the electronic device 100 can also switch the second content to content that only matches the interests of the user corresponding to one of the accounts based on the user operation. Exemplarily, the electronic device 100 can update the second content to the third content based on the user operation, and the third content is the push content that the application server of the fourth application selects 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. In this way, content that meets the user's requirements can be selected to meet the user's personalized browsing needs.

[0340] In some implementations, after the electronic device 100 obtains the digital identity shared by the electronic device 200, the electronic device 100 may also receive instruction information sent by the electronic device 200 to cancel the sharing of personalized data, or detect a user operation to cancel the sharing of personalized data, and switch the shared identity of the first account back to the original digital identity. Afterwards, if the electronic device 100 logs in to the system account on the application again, the application can use the personalized data associated with the first account for content recommendation, and no longer combine the personalized data associated with the second account for content recommendation.

[0341] Exemplarily, if the electronic device 100 detects a user operation of logging in to the first account on the fifth application after canceling sharing, the electronic device 100 can send a third message to the manufacturer server 300, and 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 to the first account. The fourth content is the push content that the application server of the fifth application filters out from the content provided by the fifth application based on the personalized data associated with the first account.

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

[0343] 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, the second account), or cancel sharing with other accounts.

[0344] Exemplarily, the first interface may refer to Figure 2E In the user interface 50 shown, the first control may include Figure 2E Icon 502A and icon 502B are shown.

[0345] 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.

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

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

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

[0349] 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.

[0350] It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in a processor or by instructions in the form of software. 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.

[0351] 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; the processor may be used to call the computer program in the memory, so that the electronic device executes 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.

[0352] 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.

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

[0354] The chip system may be composed of the chip, or may include the chip and other discrete devices.

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

[0356] Optionally, the memory in the chip system may also be one or more. The memory may be integrated with the processor or may be separately arranged with the processor, which is not limited in the embodiments of the present application. Exemplarily, 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 may be arranged on different chips respectively. The embodiments of the present application do not specifically limit the type of memory and the arrangement of the memory and the processor.

[0357] Exemplarily, the chip system can 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.

[0358] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a 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-mentioned embodiments.

[0359] The present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program (also referred to as code or instruction). 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.

[0360] It should be understood that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (digitalsignal processor, DSP), an application specific integrated circuit (AP 800plication specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined to perform. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0361] In addition, an embodiment of the present application further provides a device. The device may be a component or a module, and the device may include one or more processors and a memory connected to each other. The memory is used to store a computer program. When the computer program is executed by one or more processors, the device executes the method in each of the above method embodiments.

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

[0363] The various implementation modes of the present application can be combined arbitrarily to achieve different technical effects.

[0364] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can 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. The available medium can 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 disk (SSD)), etc.

[0365] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

[0366] In short, the above description is only an embodiment of the technical solution of the present invention, and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention shall be included in the protection scope of the present invention.

Claims

1. An account management method, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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